I think there is a fundamental contradiction in the idea of decentralizing the nostr NIPs. If it were truly decentralized we would have multiple NIPs repositories that did not agree. A protocol doesn't work well when there are different variations on the different NIPs. As much as it is anthetical to our very natures, I think it has to be centralized and that we have to fall in line as subservient to the people with merge access. At least it is not a govenment, it is just a protocol specification. And at least it isn't just one person, it is many. And clearly they don't like this state of affairs either but there is nothing to be done about it. Seriously I see no way to truly decentralize it without a long period of nostr-wars where clients and relays only become "eventually compatible" based on what people actually code, and things that happen that way tend to accumulate crap over time (not that nostr doesn't have it's share of accumulated crap for other reasons).

It's great to have a decentralization ideal. But sometimes for practical reasons ideals cannot be achieved and pragmatism needs to overrule. And we cannot all have merge access.

I had merge access once but I revoked my own permissions. Then I got them back somehow. Then they went away again somehow. Generally I wasn't using them because I don't want the responsibility. It's fine to complain about a merge you don't like, but anybody who wants merge access automatically becomes suspicious in my book.

Isn't it just a protocol though? Anyone can chose to what degree they interact with it. Not unlike Bitcoin. I understand it as a bit of a democracy in that regard.

If you don't like full replace by fee, don't run it on your node. If you don't like a certain NIP, don't run it on your relay.

I really don't see the problem. Maybe I don't understand what you are saying, I am not a dev. You are, and I really am amazed by all the work you have done with Gossip. I use it every day, and thank you.

I could be wrong, but I think at its core nostr is really nothing more than passing json info over websockets to defy censorship. Anyone can do it however they want. Who cares?

Reply to this note

Please Login to reply.

Discussion

You are right. In the final analysis, anybody can do it however they want.

But there is a github repo people have been arguing about recently that specifies NIPs. Those are not commandments, but they are seen as the correct version of nostr and clearly are the NIPs most developers will aim at. Therefore, there is some kind of power if you get to specify them and others don't... even if it is a soft power.