Voyager doesn’t explicitly store much. Less than a few MB. The rest is Safari cache (which is inside the Voyager app container).
Lots of it is probably Safari caching pictures and video. But, Safari is pretty good at cache management and will clear this out as storage is getting constrained. Just like RAM, if there’s not much memory pressure, caching is more aggressive and takes advantage of the space.
Overall, it’s a good thing. It means your device won’t try to fetch the same picture many times over, which adds cost in data transfer to Lemmy administrators.
But again, the caching mechanisms are designed by Apple and shouldn’t interfere with device storage, because iOS will clear caches if the device is more constrained on storage.
Knowing iOS lumps web apps into a global safari cache is helpful. That means we can’t get a very accurate measure on iOS unfortunately. I can file a PR with Apple but that’s just never going to get made.
Still, I cleared out 600MB in just a few days. It all seems very suss based on my usage patterns.
Why would Voyager need 1GB of storage???
Voyager doesn’t explicitly store much. Less than a few MB. The rest is Safari cache (which is inside the Voyager app container).
Lots of it is probably Safari caching pictures and video. But, Safari is pretty good at cache management and will clear this out as storage is getting constrained. Just like RAM, if there’s not much memory pressure, caching is more aggressive and takes advantage of the space.
Overall, it’s a good thing. It means your device won’t try to fetch the same picture many times over, which adds cost in data transfer to Lemmy administrators.
But again, the caching mechanisms are designed by Apple and shouldn’t interfere with device storage, because iOS will clear caches if the device is more constrained on storage.
Knowing iOS lumps web apps into a global safari cache is helpful. That means we can’t get a very accurate measure on iOS unfortunately. I can file a PR with Apple but that’s just never going to get made.
Still, I cleared out 600MB in just a few days. It all seems very suss based on my usage patterns.
Because you view a lot of content. And for avoid to load it each time, the app keep it cached.
I know how cache works and that’s not it. But thanks.
You should open a ticket on the github. You would got answer directly from the devs.