cool, is there any docs on how bunker:// url works. I noticed login.nostrapps.org gives a URI with a relay and nsecbunker gives a URI with a hex code hash
I guess bunker://pubkey-in-bunker?relay=x was the original url Pablo came up with, but then he simplified it to just npub of pubkey in bunker (assuming app connects to his relay). And then Pablo invented a token that is nsecbunker specific thing, a pre-approved set of permissions. I would say you could go with bunker:// url, while we figure out a better oauth like ux.
I just want to tell coracle which relay to use for nip46, bunker: url allows that. See nostr:nevent1qqsphc9rv7820h4hqchyg86h45q4hyvpsecscadpfwjx94pcuksjthcppamhxue69uhkummnw3ezumt0d5pzqv6kmesm89j8jvww3vs5pv46hqm7pqgvpm63twlf9hszfqzqhz7aqvzqqqqqqy86wtkn
Highly interested in this, but I'm not really up to speed, and I wasn't able to figure out the protocol when I last tried. This is high on my list, will probably put it together in January — I'm bullish on the OAuth workflow. If you want to open an issue or PR on coracle, that would make me very happy.
Here it is, sending from Coracle signing with nip46 https://github.com/coracle-social/coracle/pull/205
Highly interested in this, but I'm not really up to speed, and I wasn't able to figure out the protocol when I last tried. This is high on my list, will probably put it together in January — I'm bullish on the OAuth workflow. If you want to open an issue or PR on coracle, that would make me very happy.
Here it is, sending from Coracle signing with nip46 https://github.com/coracle-social/coracle/pull/205