Is this really that hard on amber?

Step 1 create an app in amber for the application requesting a bunker

Step 2 copy the url from the app to the site/service

Step 3: approve permission.

This isn't that different from current ux when adding 2fa on mobile devices.

Reply to this note

Please Login to reply.

Discussion

There are 2 bunker formats and no way to even know which you’re supposed to use. It’s insanity.

That seems weird. The format I'm familiar with and use is bunker://?relay=&secret=

Just checked the nips docs now and you are right. I would imagine the second format (nostrconnect://) is something the client needs to generate for users to copy and paste in their signer while the first format (bunker://) is purely generated by the signer and pasted on the client.

Ideally IMO, the nostrconnect format from a ux standpoint should be abstracted away into a button which signers can react to on mobile (deep-linking)