Oddbean new post about login | logout Why is nak the only NIP-46 app that actually works? Runner-up is Amber which mostly works but still a bit finicky. nsecBunker requires payment and then the app is unusable. nsec.app uses an obscure link-clicking flow then only works half the time. nak works perfectly every time, but it's a command line tool. We need to make Amber great.
I've been using Amber for a week or so on Android. Seems to be working fine, but I don't do anything lightning wallet of bitcoin.
nostr:nevent1qqstc9xf90t2fasdgc48j8z5ytdla8zjxc8h5syh5fpzmyf00kcygmcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qq3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnwsxpqqqqqqzpekyk4
I love nak! I started to use it after your blog post a couple weeks ago to sync relay profile data. I have never used the bunker with it though. I exclusively use Amber and don't have any issues with that. I run my own nsecBunker, well I used to before I had problems with it and generally liked it up until I had an issue. nsec.app is a bit confusing because of the pop-ups, but I've had medium success with it. All in all, we need better UX for these things.
Nsec.app's flow is not obscure, it's in the nip. And it will work reliably if you enable push notifications on it in the browser
It should not be in the NIP. That's crazy. It barely works as it is and we've loading new features on top of it. As a developer it's frustrating. I don't want to implement this special flow just for an app that only works half the time.
It doesn’t work on safari iOS … doesn’t use existing Nip05 addresses … and the onboarding flow is definitely “obscure”. I had to write my own local key encryption and storage, implementing Nip49, cause nostr-login just won’t work for my onboarding client. nostr:note1re253kvltqg7rh6l425a26w07g7uwt9yfgxtz3hsewtvf6e0gelqtmds5d
This works perfectly well https://github.com/blackcoffeexbt/hardware-nostr-connect-device
Never seen that one, cool!