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?
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
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
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.
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.
