I think we can do just as good in the clients with proper local db support, no need to centralized around custom relays.
Discussion
heavy caching in native clients is one thing, but what about web/pwa? less consistency and duration there means they’ll have to fall back to making a bajillion REQs over websocket(s).
it pains me to see the data tx most clients are doing. the general idea bundling data (similar to primals cache) at the protocol level is interesting.
You can do all of these same techniques in web/pwa
disclaimer: not a webdev and have not built a pwa, but heard this from a friend recently regarding ios. maybe someone here with more experience can debunk.
“If your PWA or any website for that matter, goes unused for a few days (we think it is roughly 14 days, it is not documented) the device will remove all cached assets associated with the origin. This includes IndexedDB, service worker cache, localStorage, etc.”
Agree. I am preparing to have a heavy db in the app. I think I am going to do something crazy:
