Thread

Why do we need a second bad browser and a dumb standard when we already have proper browsers and W3 standards? The key word here is "why". What does "dumb" Nostr with its buggy, useless clients actually give us? The moment it steps onto a field where "grown-up" standards operate, it not only contributes nothing β€” it outright loses. In speed, in integration, and in purpose. You're literally saying that JSON with tags can be used for something serious, even when clients are forced to duplicate the letter case of tags because people are somehow even dumber than Nostr itself. Nostr only works well for the very thing its name refers to. And I don’t see anything like "and also a great tool for standalone solutions" in there.

Replies (2)

Good rant! Agree nostr is the best tool in the box for a pretty limited range of use cases, mainly when you need an API that does its thinking out loud. When nostr tries to be what it isn't, that's when it gets super buggy and crashy. Like this idea of using nostr for the backend of a high-throughput video streaming platform with client-side proof generation, what on earth?