Nostr Web Client

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!

brugeman 9mo ago

Alby extension didn't allow parallel requests last time I checked, probably others too. It's not clients fault.

Reply to this note

Please Login to reply.

Discussion

René Aaron 9mo ago

Alby uses sequential processing as we want to prevent clients opening 10 prompts at a time.

nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyy2wzruqsr27rhfzjx0shd6t4l20xwxa33fnj900hwf46y4z9l7gxv93nl Is there a particular problem that you see with that?

cmd 9mo ago

it makes UX slow and ugly for remote signing

you make a good point that opening 10 prompts at a time is also bad

there needs to be a method for the client to fetch the user's signer permissions in advance, so the client knows which requests are pre-authorized and can be done async

otherwise remote signing will suck more and more as new protocols develop and demand more background signing

brugeman 9mo ago

Alby should just queue requests that require a prompt and open them one by one.

Asking what is pre authorised is not great bcs signer might dynamically decide if the prompt is needed i.e. if client is trying to erase the contact list etc

René Aaron 9mo ago

Alby queues all requests and processes them one by one in the same order the NIP07 calls were executed.

The extension also only knows whether to display a prompt or not after checking the site-specific permissions, blocklists, etc.

brugeman 9mo ago

It used to throw an error on a concurrent request iirc, not that's changed? If so then clients should be safe to send parallel requests, right? Those won't be executed in parallel but at least it won't crash.