The first paragraph of this is so true.
Non-dev people or ppl who haven't tried to bring a nostr app to MVP level don't understand how complex it could get to deal with async signing and encryption.
E.g. you have an ecash wallet that synchronizes state (encrypted tokens) to relays as a backup and publishes nutzaps(signing). Now consider ALL possible footguns when new #ecash tokens are minted and #Amber connection gets flaky or lost.
Good luck.
there are many reasons. It makes the code signing path asynchronous which greatly increases complexity in all of our code paths.
Not being able to mix in data into nsec in different ways prevents us from integrating our one click setup wallet.
The ux flow for signing seems pretty bad, needing to switch apps to approve things, when this could be done within the app instead.
View quoted note →
