How to handle key management on mobile, other than:
- nsecbunker (buggy)
- installing a new browser and an extension (ux black hole)
Genuinely curious what the options are
I think this leaves us with 2 options.
Either A) We educate new users about the basics of Nostr, to get them aqcuatented with key managment and how things will work.
B) We abstract away as much as we can initially so users just think they are using a normal web app until they leter realize what makes Nostr different.
I think that route B is easier for board adoption, but, it will be very important to build things in such a way so users can
"Opt-out" of custodial key managment solutions once they have spent the time to get a better understanding of how nostr works. What nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has been working on will help onboarding immensely imo.
Discussion
Everything is buggy at first. I think the nsecbunker flow is the right direction, we just need to keep ironing things out until it's seemless. Very do-able imo
Agreed, which is why we've gone ahead and implemented it (nsecbunker), but the source code for it (the admin interface) is not available, unless am mistaken?
Would love to see a UX akin to a lightning payment, where (by clicking a link) my preferred signing app (wallet) will open automatically, then broadcast a signed message on approval
nsec bunker is confusing AF. I've been here 1 year, paid the sats for nsec bunker and it sits like a brick paperweight. I've set up plenty of sites, wallets, etc, but UX for nsec bunker must be for coders, not average peeps with an affinity to explore. zero help available, as well.
When it works, it's a dream. Just approve the kinds in the dashboard, set & forget.
Problems can arise if you don't approve in time (signing requests disappear or time out)
Try Amber.
I wish Amber had a "default reject" policy though so I can prevent Amethyst from using it to decrypt things and whatnot.