This open-ended set up is why barely anyone gets it at first glance, I think.
Nostr enforces signing JSON and sending/getting from relays. Which is in comparison, obviously, easier to grasp.
But being easy to understand, doesn't mean it auto-magically fits every web use case. The "simple" upfront constraints of websockets, JSON and needing signatures for everything require quite the set of complex of work around for 90% of things here, lol.
Replies (3)
Being easy to grasp is what gets so many devs on board and the ver common desire for interoperability results in simple rules. In the end, nostr might have the critical simplicity needed to spark an explosion of projects that pubky so far has not managed to inspire.
And maybe nostr will end up being more complex than pubky by necessity from its limitations, yet had it started out with that complexity, it would never have reached any adoption at all.
Well, they are also trained to act like some sort of auto-immune disease instead of actually believe other designs can exist or be better.
Yes, Nostr is "simple" by omission of required protocol, not by elegance.
Have you read the message? He was suggesting that "better" might not be a timeless property. A protocol can fail because it fails to inspire because the "marketing team" is literally one narcissistic nerd.
