Replying to Avatar ManiMe

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.
04
சாரு-秋陽 2y ago

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.

Reply to this note

Please Login to reply.

Discussion

Avatar
ManiMe 2y ago

Nostr IS Interoperability.

The value ADD of Nostr on the social internet is only its contribution to decentralized interoperability. It has nothing more ATM that it does well. As long as this interoperability is (appropriately) transparent to the (currently targeted) end user, with zero friction to discover and leverage novel use cases, then nostr wins.

Otherwise (death of a thousand NIPS) if clients and relays loose sight of interoperability (like: for the sake of new features?) nostr’s one super power will fade away.

“maybe 2-3 clients” is losing sight of the forest for the trees.

nostr:note1ze08vg0m3q7c3spykkge3gn3mrc6zsa588req7uucvlmm3jc0naqcs53tw