Thread - Nostr Hypermedia

Why can't we all just agree on a single field instead of polluting everybody's kind0, increasing bandwidth usage of everybody and making the logic of every client much more complex? The only point of having a standard is not having to support every different bizarre implementation people come up with. View quoted note →

↑ Parent

Replies (4)

Vitor Pamplona _@vitorpamplona.com 2 years ago

The truth is that in Nostr you have to support what everyone else does otherwise the UX is just terrible. This is just one of the 1000s of little things we need to do to support interoperabilty in the protocol.

2 replies ↓

Vitor Pamplona _@vitorpamplona.com 2 years ago

But, more importantly, we can't have a protocol where people can do "whatever they want" without running into these little issues.

1 replies ↓

pjv _@pjv.me 2 years ago

Sorry, but welcome to the other side of "embrace the chaos". Personally, I favor tighter specs throughout. Discipline is the paradoxical path to freedom.

1 replies ↓

pjv _@pjv.me 2 years ago

Exactly. Perfectly said on both. Most especially the parts about keeping the protocol as simple as possible. I worry that nostr is getting too fat too fast. I also favor you, as nostr CEO, running rampant through the existing NIPs and sprinkling in a lot more MUST and MUST NOT.