Global Feed Post Login
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.

Avatar
ManiMe 2y ago

I may have gone too far… but I just sent the opening salvo on NIP bloat.

#FreeTheOtherStuff

https://github.com/nostr-protocol/nips/issues/864

https://github.com/nostr-protocol/nips/issues/862

https://github.com/nostr-protocol/nips/issues/863

nostr:note1seckzhrntq3zlmpfqcl8atwu7ptjq4k4zs74a9lpd6mm3w046alqa96urt

Reply to this note

Please Login to reply.

Discussion

Avatar
STERRY 2y ago

If you're serious make them PRs and I'll put them here. Embrace the bloat offensive! https://codeberg.org/nostr/nip-index

Avatar
ManiMe 2y ago

Imma get there… after chance for “community” feedback. Lol.

(That’s why I posted this note here… cause the GH review process tends to be top heavy.)

Thread collapsed
Thread collapsed