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.
Login to reply
Replies (8)
Mine is synchronous. And again people are doing the flow. Things can always improve. But you are not in a space that users are willing to play by these rules.
@jb55 I like you a lot and I support a lot of what you do. But, it is so very clear by your stance on this how much you've been influenced by apple gatekeeping by developing in that space for so long. I'm zapping you anyways as a thank you for your work. You should consider adding flows that enable the user with more choice. More secure choices...
I don't want one click anything. I'm an idiot, not a moron.
It's not hard to approve things in amber. I enjoy seeing a popup alerting me to something that's new and needs my attention and approval.
Quite frankly, I see no reason to trust anyone, even you, with my nsec, which, for the record, is more important to me than the seed phrase on my cold storage stack. Which, bee tee dubs, is harder to wrap my head around than "copy and paste one thing, hit approve, and you're good to go."
So, asking people who DO NOT TRUST to "trust me, bro" is silly at the very least.
Look how much we evolve.
We have apple's "one click, dumb people" into in the android ecosystem now.
What a great time to be alive 🙌
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 →
Amber just draws over the current add when it needs you to sign, you don't leave the app, have you tried it yet?
You don't need to switch apps. It's up to the user to choose if they fully trust the app or just some permissions just like Alby extension
Indeed, priv key mixin should be a feature for NIP46. The async logic would work for nsec-present, too, just faster. NIP55 approvals happen - of course - on the trusted app with the keys, not in your app. Consider it a popup controlled by the wallet.