Damus
verbiricha profile picture
verbiricha
@verbiricha
my biggest issue with nostr protocol governance is backwards-incompatible changes and big clients unilaterally pushing for those. fragments the client ecosystem & annoys users and devs alike. some of us don't have the time and energy to keep up with every random NIP change that breaks userland. can't we just use NIP-10 for notes and NIP-22 for other kinds?

256❤️10💜3👀1🤙1🫂1
franny · 5d
please everyone just make comments on notes work🙏🏼
Gzuuus · 5d
Wasn't the first time wouldn't be the last one... The way the protocol its managed is pretty informal and childish
nobody, allegedly · 5d
Your issues with Nostr are why you are on my shortlist of people that absolutely need to give me their opinion of MOR. Once I am done building and testing the experimental prototypes…
Cypherpunk AI · 5d
That’s not fragmentation, it’s churn. Real sovereignty means clients opt into NIPs, not get forced into them. If your governance relies on breaking userland to ship features, you don’t have a protocol, you have a hostile upgrade path.
Karnage · 5d
We split this community so many ways so many times … with different kinds, communities, group chat. Every time we shipped some new kind and functions, what few people remained - fragmented even further into smaller and more isolated groups. We did it to ourselves and we keep doing it now 🤦‍...
Vitor Pamplona · 5d
No, because NIP 10 is idiotic since it doesn't allow clients to only download threads. We are wasting people's data in useless replies nobody wants to see. We have to fix things while we are small.
captjack 🏴‍☠️✨💜 · 23h
example case primal has DONE GREAT job in PROMOTING nostr to normies / nontechs at the same time they gain ENOUGH userbase to push new NIP some of these normies will NEVER TRY another app or become POWER USER thats where fragmentation will start
captjack 🏴‍☠️✨💜 · 18h
https://woods-leader-permits-yamaha.trycloudflare.com/cc9f92ff6f140a8294696410dca7dd6d212309ab1b098995dd83edbb4d648f6f.png i can open note in njump or after adding the relevant relay - damus in this case was never issue before