I am nostr noob. I like some ideas presented by Steward. I think npub abstraction is all we need but we also need way to send generic structured data (eg rpc messages). One way i see is to stringify everything into content and pick some unused ephemeral kind (i dont like it for obvious reasons). Nip01 also describes potential extensions of event object with new attributes but problem i see there is that those are not included in signature calculation. Btw is there any place where i can shoot this kind of stupid questions?
BREAKING NEWS!
New episode of Nostrovia is out now!
Stewart Mackenzie is working to build a world where State controlled address centric networking protocols like TCP/IP are made obsolete by information centric protocols.
In this episode of Nostrovia, he explains what information centric networking is, how it's resistant to attack by the State, and why he thinks the current architecture of nostr is fundamentally flawed as a censorship resistant network.
Listen now!
Preview:
https://podcasts.apple.com/hk/podcast/nostrovia-the-nostr-podcast/id1678531266?l=en
https://open.spotify.com/show/3FKrua9rST5DDKv0WeAqWn
Full episode:
If you have problems with zapstr, contact the platform's generalissimo: nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
Discussion
You can use tags for this, and they are included in the signature calculation.
Thanks, yeah, i think that is still not ideal but has nice properties where you can basically subscribe to different rpc calls by different method names or even parameters. Having full expressiveness of json for both request and response would be great though. Was there any discussion about this? What confuses me is wording of nip01 (“New NIPs may add new optional (or mandatory) fields and messages and features to the structures and flows described here.”).
Anyway, in comming days i will hack something together. I like the idea of having dedicated nostr rpc relay.
Have a look at how I'm doing it in github.com/nostrocket/engine using opcodes.