Oddbean new post about | logout
▲ ▼
hzrd149 | 11 months ago (raw) | export | reply | flag +10 
 Still cant figure this NIP-46 thing out... the nip says I should use a nostrconnect:// URI generated by the app itself, snort.social wants a bunker:// URI and nsecbunker gives me a npub with a # after it. whats going on here? do we even have a standard?
▲ ▼
Gigi | 11 months ago (raw) | root | parent | reply | flag 
 #asknostr 

nostr:nevent1qqsff4apzlykh8ry44379tw7qp9e7xtqyhynxye48wzkh8vxy80g5qqpz9mhxue69uhkummnw3ezuamfdejj7q3qye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjsxpqqqqqqz9jl8h5
▲ ▼
The Fishcake🐶🐾 | 11 months ago (raw) | root | parent | reply | flag 
 I tried to figure it out too, and gave up myself. 🐶🐾🫂
▲ ▼
hodlbod | 11 months ago (raw) | root | parent | reply | flag +2 
 I gave up and added NDK as a dependency just for this one thing. Someday I'll reverse engineer it and create my own implementation, but apparently today is not that day 😂
▲ ▼
hzrd149 | 11 months ago (raw) | root | parent | reply | flag +1 
 At this point I think we have at least 3+ working implementations. Just need to figure out if they are compatible and then update the NIP accordingly
▲ ▼
brugeman | 11 months ago (raw) | root | parent | reply | flag 
 nostrconnect is for app to redirect to signer, bunker is Pablo's invention for signer to app, and npub or token are nsecbunker-specific non standard ideas.
▲ ▼
hzrd149 | 11 months ago (raw) | root | parent | reply | flag 
 that's my thinking. but I don't know of any signer apps that work with nostrconnect:// 😞