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
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)
It's bumpy for now, agreed. But this is whats on the horizon https://www.flare.pub/w/naddr1qqt45cts94kk2ttzv938jttyv4kk7tfjd45hxa33qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqppdmzmfqkz
This is awesome, certainly the right direction, but still doesn't explain a dang thing about a huge part of this, and that's nsecbunker, lol. That's my big stumbling block, ATM....
I don't think that should be a stumbling block. Ideally, we are all using nsecbunker (or a variant) without event knowing it. When a user clicks "Sign in with Google" 99% of them have no idea what is going on, but it just works. Like OAuth providers, there will be nsecbunker providers, and some technical folks may choose to roll their own. But for most users, they just have the simple experience that they have grown accustomed to.