Oddbean new post about | logout
▲ ▼
verbiricha | 7 months ago (raw) | root | parent | reply | flag 
 yeah, gotta bug the devs so they prioritise it. i don't use mobile clients anymore but have wanted this since forever.
▲ ▼
The: Daniel⚡️ | 7 months ago (raw) | root | parent | reply | flag +4 
 Bugging them!

@Vitor Pamplona @jb55 @miljan
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag 
 Are we talking nip46 server in Damus/Amethyst/Primal? Or them being nip46 clients?
▲ ▼
verbiricha | 7 months ago (raw) | root | parent | reply | flag +1 
 The terminology is a bit confusing. I mean mobile apps acting as signers. A nostr website could show a QR code for logging in with your mobile app, you scan it with Amethyst/Damus/Primal and you are logged in. No need to install another app like Amber but have this functionality on mobile clients. Maybe I'm misunderstanding something but `nostrconnect` URLs enable this flow, no?
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag +1 
 Terminology is confusing, your ask is nip46 server in Damus/Amethyst/Primal, nostrconnect as QR scanned by the mobile app-signer should work, I think.
▲ ▼
verbiricha | 7 months ago (raw) | root | parent | reply | flag 
 +1, would be great UX imo. I haven't seen support for nostrconnect URL QRs in clients that support NIP-46 login tho.
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag 
 Well I guess mostly that's bcs there are no mobile apps with access to camera that could scan the QR, nsec.app could do that theoretically, but I haven't seen any demand yet
▲ ▼
verbiricha | 7 months ago (raw) | root | parent | reply | flag +1 
 well, OP in this thread is demanding it 😁
▲ ▼
armstrys | 7 months ago (raw) | root | parent | reply | flag 
 Not to hijack the conversation, but I would like to see more mobile wallets be nip-46 clients. Or do some already support it? I like trying new clients and it now seems standard on web clients, but mobile clients always want your private key (except for maybe amethyst?)
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag 
 Mobile nostr apps don't want to be nip46 clients, mainly for performance reasons.
▲ ▼
armstrys | 7 months ago (raw) | root | parent | reply | flag +1 
 That sure makes sense. Probably an issue for low connectivity as well. I guess NIP-7 is probably the preferred path for mobile
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag +1 
 No, native mobile apps can't use nip07. Web apps (mobile or not) could use nip07 extensions, but could also use remote signing nip46 (nsec.app etc).
▲ ▼
humphries | 7 months ago (raw) | root | parent | reply | flag 
 Interesting! Can you explain the benefits of using nip07 extensions for web apps compared to remote signing nip46? #webdevelopment #mobileapps
▲ ▼
armstrys | 7 months ago (raw) | root | parent | reply | flag +1 
 Wow I hadn’t realized nip-07 was specific to web browsers. I made a bad assumption since there were apps like nostore that you install straight on iOS. So we don’t really have any way to handle mobile native event signing across apps on a device? Is that just because it would require a specific spec for each platform?
▲ ▼
brugeman | 7 months ago (raw) | root | parent | reply | flag 
 There is Amber on android and a similar thing for apple named Keystache, not much support of those though
▲ ▼
armstrys | 7 months ago (raw) | root | parent | reply | flag +1 
 Thanks for the conversation on this! I hadn’t heard of keystache yet and haven’t broken out my old android since amber was released. Will have to take a look