As nostr becomes fragmented and lineages diverge, the definitive NIP repository will be the developer circle you are a part of. There is nothing wrong with that. Be interoperable with your friends or just use your own relays.
Login to reply
Replies (2)
This is all by design in a decentralized, permissionless infrastructure. The github nips repo works for a circle of developers, of which many take influence, and would like to contribute but doing so on a permissioned platform is getting annoying.
There is nothing wrong using it as the defacto repository or a model for "The Nostr" local to everyone that wants to take influence. The problem is that nostr is too good and using any other system is starting to get painful (damn you developers! โ).
Just let the ideas compete with other specs. Make a whitelist relay where you and others curate and incubate the ideas. Others could fork on their own relays, but no one needs to listen - unless it actually makes sense for the client.
Ultimately, its a public announcement of "i'm using this spec" and you don't need to leave nostr to be part of the "official" conversation.
I basically agree, but I don't think people are spending the necessary time on making sure consensus works. Fragmentation is ok, but the target is maximum interoperability, not maximum fragmentation. Everyone making up their own specs is an unbalanced approach, just as running everything through one permissioned source is unbalanced. Of the two, I personally prefer the github model, because it's proven to work, while the bizarre bazar is untested. But I'm willing to participate in experimentation with a middle ground.