pull down to refresh

Yes, for example when I add another key and change to that key and for instance, I take stacker.news which was already loggedin with previous key still persists in the changed key also.
My expected behaviour is that I get a new profile, like a instance in where I can login simultaneously with the new key without being logged out from the previous key i had. I THINK I MADE IT MORE CLEAR TO YOU.
Then after , if i change to the first key I had it should be persisted with the the logins I made with that key.
Multiple browser instances and sessions which can be persisted for multiple keys is what I am expecting.
Presently when I logged in to nostr with one key and switch to another key and try to post a thing on nostr you can find that the nostr profile will be with the first key and the permission request will come with the swithched key and if we click approval it will post successfully in the nostr profile with the switched key while you are inside the nostr profile with first key. Its a buggy behaviour.
And while you are on it, another one I noticed is there is no folder delete option in the home screen also would be appreciated.
Ah yes, 100% agree with you - I also expect different browser instances/sessions with different keys. This is currently very non-trivial to implement, but it's on the roadmap.
The delete folder button noted, will add asap.
Thank you!
reply
And there is nothing for key backup for generated keys inside the app.
reply
True. That's intentional and temporary. We don't have any onboarding yet, and generated keys are meant for testing only. As soon as we figure out how to onboard people properly we'll allow backups etc.
reply
reply