The only nip46 implementation that seems to always work is nak by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
This proves it can work but I can't be telling people to run a CLI program.
One of the biggest technical hurdles for Nostr is finding a way sign events on web apps without browser extensions and without sharing the nsec with the web.
The browser is your enemy...
As soon as there is any meaningful growth in user base, let's say the next adoption cycle "and nsec gone"
Sure, nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft created NSECBunker, but there has not been any adoption or alternatives coming up.
Discussion
nsec.app works well for me
It's buggy, and uses an alternative flow that was shoehorned into the nips and almost impossible for clients like Ditto to support.​
You don’t have to use the OAuth flow. I login with the bunker connection string with some apps. Haven’t noticed any issues yet, but I don’t use it every day.
The problem is the part where you have to open a link to nsec.app as part of the login flow. This really should not be in the nips. It's a hacky workaround for the fact it's a PWA, and very difficult to surface to the user in some situations (like Ditto where this is happening in a backend as part of an http request).
Do you mean to approve the connection? I usually just keep my nsec.app dashboard open on the initial connection. I use the bunker connection string with my app notacomment which is a node.js app and has no frontend.
Here’s my bunker connection flow:
I want an “nsec.app” like app on my Umbrel. It will be a little slow, but it makes sense.
Did you try amber again recently?