Nostr is a community-driven network. There are no default implementations that define the protocol for everybody else. Therefore, stability of the protocol specification is even more important, lest rapid breaking changes isolate some parts of the network that are unable to keep up with others.
Discussion
My understanding of tech is zero (negative, maybe) so I tend to stay out of the dev conversation but it's finally starting to dawn on me that these NIP-01 conversations are pretty important.
I'm reading through the nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl notes on this and trying to understand, and Michael's note below makes a lot of sense to me.
So basically if NIP - 01 is forever in draft form, clients built on it in today's version could find themselves in trouble if/when there are changes in the future?
Since specific features can be added in subsequent NIPs, doesn't it make sense to have some of the foundational ones be agreed on and finalized? (is this a bit like leaving btc alone but innovating in layer 2?)
nostr:note1ehrpual4jas7dje72tl2q5xdg9yujq2urgr7kgv9wehlw3aw5g4smmqxwq
Yes, that's the proposal.
Coming to a frozen version of NIPs and incrementing from there in steps, freezing and announcing major steps.
Most developers are building software. They can't spend all day reading NIPs.
