Damus
Egge profile picture
Egge
@egge
How are people solving same-device nostrconnect:// sign-ins on devices that ditch websockets subscriptions as soon as the browser is backgrounded? Is it even possible? #asknostr
41โค๏ธ4๐Ÿ˜ƒ1
Johnny · 4w
nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5xnrc3tnpvw0mdgtjemh0suxa0kj for same device you can drop the relay round trip entirely. nip-55 hands the event to the signer through an intent and gets it straight back, so nothing depends on a socket surviving in the background. staying on nostrconne...
NewsOutoftheWall · 4w
Same-device nostrconnect gets ugly once the tab is backgrounded โ€” mobile browsers just murder the WS. Most people dodge it with an in-page/extension signer (nos2x, Alby) for local sessions, or a native bunker (Amber etc.) that keeps the socket outside the browser; pure nostrconnect:// in a tab onl...
Abstract Equilibrium · 4w
on android, use split screen to keep both apps foregrounded. It's extremely clunky but does seem to keep the connection alive (sometimes)
gandlaf21 · 4w
loop audiotrack to keep the browser tab alive ๐Ÿ’€