Yes, that was kind of what my point was “if it ain't broke, don't fix it”. As #nostr devs, we shouldn’t have to deal with the underlying transport, we just use libraries that abstract that from us. I believe most languages have a WebSockets library. In my case, when I started with Nostr, it took me a week to find a good C++ library that I was happy with, but now I just use it and don’t care what happens under the hood. And because there was no Nostr C++ API, I made one. Check it out https://pedro-vicente.net/nostr/nostr.html
That doesn't justify making the protocol a much more complicated thing for everybody. WebSockets are simple, simpler than HTTP and REST, to be fully honest. If you don't like them that means you're just not used to them. You can use a Nostr library that abstracts that for you.
If you want a curl-like experience on the CLI, use https://github.com/fiatjaf/nak
Discussion
No replies yet.