-
seil
Do you guys have any suggestions for caching messages on a web client? I don't want to sync the entire message history on log in, just fetch however much is needed. My current solution involves attempting to sync all message history and storing it in indexeddb, but that solution does not really work and is prone to failure depending on user available disk space
-
MattJ
You could look into whatever Converse.js does
-
seil
This repo is very hard to navigate
-
seil
They use indexeddb though
-
seil
(last time i checked*^)
-
singpolyma
Sync everything is what I'm doing in snikket SDK. It is needed if it's going to be a daily driver especially if e2ee is used. For temporary logins eg at library store nothing is better and e2ee is useless in that context. Not sure when "store some but not everything" matches user need?
-
seil
> Sync everything is what I'm doing in snikket SDK. It is needed if it's going to be a daily driver especially if e2ee is used. For temporary logins eg at library store nothing is better and e2ee is useless in that context. Not sure when "store some but not everything" matches user need? Lazy loading basically ↺
-
seil
The older your account is, the more history has to be loaded
-
seil
not good for bandwidth and storage
-
singpolyma
Oh, sure, I only load 30 days on first login if that's what you meae
-
singpolyma
Load more as you scroll back if needed