Also, there is nothing preventing signing of homeserver data, it can be done at app level, or client level, or indexer level, or server level, because all you need to do is delegate keys, or identity-bind them. These are only possible because of the pkdns aspects.
We already have a noise lib, and working on identity-binding, so Pubky will also have signing, private data, private message, etc.
Replies (2)
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.
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.
