I just mentioned it because switching accounts for writing wouldn’t be much code. Switching it and have all of your timeline and views refreshed would be a lot more code. This problem was originally what set me off to make a local relay (nostrdb), since switching accounts would be really data intensive otherwise.
I mean if people are doing that anyway by logging out and in, i guess we can just do it and take the data hit until we have nostrdb queries fully integrated.
Ah! This makes sense. I don’t think people switch now. Which I think is a lost opportunity. I use other apps to manage my other accounts.
How do you manage your own account and nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 on a separate dedicated phone? Or do you log in and out every time you need to use it?
Is a second instance of an app allowed with iOS? With separate memory and all.
I just use notedeck since it fully jntegrates nostrdb and has efficient (0 network data) account switching, i don’t switch accounts in damus iOS or have alts, so it’s never been a personal priority.
Damus iOS is open source and anyone can add it, but we don’t seem to get many contributors.
After I fix our web profile pages, add zaps and android support to notedeck, i will circle back to damus iOS to hook up nostrdb and account switching if noone gets to it before me.
Thanks.
Yeah, #notedeck handles this very nicely. Hot swaps in less than a second.
I’ll settle for posting from an alt then for now if that is something we can add. Because from what it seems, this might be a late 2025/ early 2026 thing.
If I knew how to code, I’ll write it my self.
One solution I (as an individual) could do is to fork Damus and side load it with a different name 🤣
Yes you could lol, would be efficient! Just not storage efficient
Its possible i will get to the nostrdb thing in iOS sooner, or else nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 will kill me since he wants it for implementing stuff 😅
In that case, your suggestion of switching accounts just for writing is good enough. It would mean one of the accounts would be the “main” account where we have our timelines and views and then the secondary account that we would just switch into to write a quick note and then come back to the main one.
If that’s what you mean. I’m ok with that! That’s progress. But the end goal would still be to be able to switch accounts and timelines. Thank you for your work!
Coding aside, is it only a data bandwidth issue?
I don’t see why it’s a data hit? I’m already downloading the new/extra data through another app.
Do you need to keep clearing the data every time the accounts change?
Damus iOS is insanely inefficient bandwidth wise, it has to download everything everytime you open the app from scratch, because it’s not talking to the local relay for queries yet. So when you switch accounts it would have to redownload everything. Any user ui action needs to be cached if we want good performance. Switching accounts back and forth would nuke your data. Local query model fixes all this, because switching only ever queries locally, and you only need to fetch whats new.
I know it would take a NIP (unless there is one already) but i have wondered why the idea of deterministic npubs are not a thing. Like HD wallets in Bitcoin.
@TKay's client sees his xpub-npub (xnpub?)... And can feed his timeline based on that. But he can post using any active npub (personal, work, marketing, memes, shitposting, disposable address?) under that xnpub.
And like bitcoin again , this would not stop people from using discrete keypairs as before. It will just allow him to bundke his 'personas' under a single master key as well as allow the client to (if desired) use a single feed locked to the master key.
Could be stupid? Lots to unpack.
