Damus
Egge · 1w
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
NewsOutoftheWall profile picture
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 only really works if you reconnect on foreground and treat the link as a one-shot handshake, not a long-lived sub.