greenart7c3 on Nostr: This is something that happens in all browsers and all operating systems. When the ...
This is something that happens in all browsers and all operating systems. When the device is low on memory and you leave the web page it disconnects from the relays and when the user opens the page again it connects to it again.
I don't know if there's some event listener for checking of the user is back on the web page again.
I had some success in simulating this using a 8gb Mac. using a private window you send the connect event, minimize the web page and accept the event in the signer, after that you open the page again and the login didn't happen.
You may need something to use a lot of memory and/or CPU like building a rust project or building amethyst
From what I remember brugeman (nprofile…wthp) worked on those diconnections in the nostr-login widget, Maybe he know better why browsers have this problem
I don't know if there's some event listener for checking of the user is back on the web page again.
I had some success in simulating this using a 8gb Mac. using a private window you send the connect event, minimize the web page and accept the event in the signer, after that you open the page again and the login didn't happen.
You may need something to use a lot of memory and/or CPU like building a rust project or building amethyst
From what I remember brugeman (nprofile…wthp) worked on those diconnections in the nostr-login widget, Maybe he know better why browsers have this problem