I put all this work into asynchronous batch handling of NIP-07 requests, and nostr clients just `await window.nostr.doSomething()` one request at a time.
It's actually pretty crazy that clients behave like this. This old and busted synchronous request paradigm needs to change, especially for:
* Primal, which requires signing of multiple events with each page refresh, all of them blocking.
* Nostrudel, which has a "decrypt all" button, but then decrypts events one at a time.
Does nos2x support asynchronous handling of requests? I didn't notice anything blocking, so I want to say yes (assuming you have permissions set).
If a client makes requests to a signing device, and those requests have a) permissions and b) no dependencies, then they shouldn't block other requests. Let the requests flow freely!
