Could nostr be soft-forked to support binary data structures and a restful API?
Curious whether you think that we'll ever see bigger changes in how it works.
Could nostr be soft-forked to support binary data structures and a restful API?
Curious whether you think that we'll ever see bigger changes in how it works.
What stops you from using binary JSON (don’t recall the name) and a restful api now? blastr already has restful api for publishing notes 🐶🐾🫡
oh better don't mention HTTP 😉
did you see our http-nostr tool?
Agree,Nostr and Cashu for M2M protocols
The hash and signatures are based on the JSON structures and string encodings (hex, base64, bech32, etc) instead of the raw binary. Which means, even if you do run everything in binary, you end up going back to the text protocol to do everything.
But one could create a parallel spec with binary payloads in mind. Clients could offer both as long as they use the same crypto primitives.
bech32 describes the nsec-npub key format right?
Does the format generally allow to create one time derivation keys, similar to eg. the WebAuthn keys, in a reasonably easy way?
Could bech32 keys practically conventional identifiers like phone numbers and IP addresses, would it make sense to "bech32 all the things"?
A parallel signing convention could cover both binary and JSON. The JSON and the binary could carry both signatures, so no matter the format in which it arrives, you always have a valid signature. This doubles the work for signers, but it might be useful for better systems compatibility, security, data volume, etc.
There's only 1 Bitcoin wallet that can load my wallets and it uses a rest API, even sparrow struggles loading the wallets.
One day I'll try to make a client that uses rest API and I'm 100% sure it will work better than any client.
You will see that nostr devs will start crying that I broke nostr or something like that, just like they always cry when they see samourai wallet
Most just don't want to admit that they software can be improved with this simple change to the protocol
Nostr and REST can cohabit peacefully. There is no reason to be a Nostr maximalist. See Blossom, for example. It works *together with* Nostr rather than trying to mutate Nostr into what it is not.
not really