Nostr has too many NIPs. It’s time to seriously consider if this is the right path.
#nostrdev #nostr
Nostr has too many NIPs. It’s time to seriously consider if this is the right path.
#nostrdev #nostr
Maybe you should organize a meeting, a conference for devs focusing mainly on the cleaning the protocol. Any idea?
Faxx 📠
No there can never be enough
What do you want instead? Conflicting specs with no interoperability?
I think it could be similar to when IEEE/ISO delegates discuss the RFCs. So only the invited people can connect to the event.
Or - more closer - BIP discussions (i think it will not lead to soft/hard fork :-) ).
It’s not really a critique—based on my own experience, after a few years, any project benefits from introspection to reassess whether its structure is sustainable over time.
Without referencing any specific NIP, as my goal isn’t to offer unwarranted criticism, I believe that some could be considered non-essential and lack practical use.
I think this is a healthy debate.
Can someone post a link to the NIP list?