Nostr Web Client

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.

TKay 1y ago

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?

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

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.

Tha Brainer 1y ago

which stack do you use to build Damus iOS? Do you use Cordova by any chance?

jb55 1y ago

Damus ios is swiftui