Why Nostr? What is Njump?
2025-03-05 15:57:28
in reply to

The Beave on Nostr: The nips are a mess. This needs to be rectified. The first step needs to be a ...

The nips are a mess. This needs to be rectified. The first step needs to be a community effort to GTFO github. Documentation and pass fail tests need to be standardized for all accepted nips and a policy of full documtation and pass/fail testing before a nip is formally accepted needs to be enforced. Basically, before things get out of hand, the nips need to get tidied up as there is a lot... Non-clarity.

The current relays can't scale. See and and and others for solutions and suggestions.

Interoperability is barely there. Sure, it kinda works, but, just about every client is broken for basic expected functionality. (Though, to your credit, amethyst is the king of all nostr clients.)

AUTH. Now. This is non-negotiable. It's exceptionally stupid that this isn't standard yet.

The mindset of trumpeting about new features while ignoring the broken mess that's surrounding the core simplicity of what the nostr protocol should be (and is meant to be, IMO) also needs to stop.

New methods of revenue generation are also necessary. The VC BS needs to stop as it is distorting the market incentives and only makes the stupid feature creep and fragmentation worse since it decouples devs from the market and lets them write really crappy code without consequences.
Author Public Key
npub1q6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqhtt3sh