NIP Bloat.
- Implementation possibilities are specd with less and less consideration for each other.
- many overlap in functionality but none are removed or deprecated for “backwards compatibility”.
- Some old school devs pull weight and don’t wanna change.
- some younger devs have no patience for discussion and “patient” integration of “good” ideas.
- devs are burnt out with the “bureaucracy” of maintaining a swamp of standards.
- nips are treated as standalone “islands” serving single use cases.
- inconsistency and inoperability creep across clients and relays, as gate keepers “give up”.
- Users become disillusioned with “the dream” of decentralized cooperation, as nostr dies a slow death due to dwindling adoption.
Login to reply
Replies (8)
So, like, the collapse of any wide scale organization. I can see this happening.
That sums it up
Nostr is going to Tower of Babel itself then. No need for government intervention.
Sounds quite possible
View quoted note →
Death by 1000 NIPS
View quoted note →
I understand your points but I don't think to a user, interoperability is that big a concern, unless it messes up basic TL big time.
Even now, threads are a mess across clients & NIP 94 images created on Amethyst are not seen on many clients & it's not caused a hullabaloo 🤷
I'm guessing most people will try out maybe 2-3 clients & stick with the ones they like.
If you are honestly concerned, take a look at the proposal below to define a process. I have some experience here as an early editor in the fediverse's FEP process. There FEP-a4ed defined a process that handles proposals from submission to deprecation.
It might be interesting to collaborate on a submission process tailored to issues and challenges of the current NIP space.
Issue (which looking at all the NIP-XXs in the repo seems to have uptake):
Pull request: 
GitHub
NIP-XX: NIP proposal process · Issue #545 · nostr-protocol/nips
As a newcomer I find it confusing to follow the various NIPs and ideas that have been proposed. The README.md doesn't give any guidance on process ...
GitHub
Add submission process by weex · Pull Request #560 · nostr-protocol/nips
Update the README.md to include a new NIP submission process.
Addresses #545
I may have gone too far… but I just sent the opening salvo on NIP bloat.
#FreeTheOtherStuff
View quoted note →
GitHub
Open Architecture for Content Types · Issue #864 · nostr-protocol/nips
This issue now lives as an article on nostr for additional discussion and refinement. Thank you for participating. https://yakihonne.com/article/na...
GitHub
Client-Relay Handshake (Bidirectional Information Documents) · Issue #862 · nostr-protocol/nips
In an effort to open up (unbloat) the nostr protocol by freeing clients and relays to tailor their implementations, there emerges a need for client...
GitHub
Standardized Tag for Expirable (ephemeral and replaceable) Events · Issue #863 · nostr-protocol/nips
NIP-1 outlines a convention for defining replaceable, ephemeral, and parameterized replaceable events based on the value of the event kind numeric ...