Wait... Hold up, again.
If I can use Nostr to document Nostr protocol specs...
Can I also use Nostr to document Nostr implementation specs? 🤔
Discussion
I could, couldn't I? I could put feature roadmaps and unit stories and etc. into long-form articles. Those are just markdown files published on Internet 2.0, right?
nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr I could just link to the notes from the ReadMe.md or something, right? Or do you have a kind for that?
nip54 - wikifreedia is probably a better model than git for nips.
In git each commit id contains an entire state, which is not always desirable for nips. still, I'm not sure it is a perfect fit.
I'm not sure what you mean about the readme.md? It would be nice if gitworkshop displayed nostr-refs in readme files as embedded events. Is that what you mean?
Yes. Why not?
Amazing how long it took me to think of doing that, tho. But I think I'm still the first one to think of doing it, so yay go me. 😂
Yes! You did it! No one else bothered to think about it. That's what annoys me most about many of the devs. They are easy too comfy with the current dev stack and aren't really trying to build the foundation of something better.
Something something house built on sand something something....
It's like Rust. The Rust compiler is written in Rust, so it literally builds itself. If you're thinking it's a chicken and egg type scenario, you're right. The first version was make in C++.
Nostr makes nostr documented.