like, it's my opinion the easiest way to fix most of these problems is simply to create new network encodings, then you can put the fixes in them, and then it's just a matter of getting a few clients to adopt the new transport, and adding some small new parts that create requests that line up with the new changes

honestly, the biggest flaw in nostr is the REQ envelope, but maybe almost as big is the entire "envelope" nonsense, which should be changed to use an actual normal API

i think it would be easy to add a QUIC/HTTP/3 with JSONRPC2 and this would make it mesh better with apps that already work with bitcoin nodes as well