I’ve enjoyed using Connect but I’ve got no clue how it got this big.
I’ve posted about it before, but I think the app should have a No-Thumbnail/No-Predownload option like RiF had. Most of the data it uses up I never make use of. It’s a big waste.
No thumbnail and pre download as an option while on data was awesome with RiF. I’m on a 2 GB data plan on my phone so every little bit counts.
Connect has a no preload option. Not sure if it works but the toggle is there.
The whole cache buildup has been an issue since it started. I have gotten in the habit of clearing the cache anytime the app seems to slow down. Around once a month or so.
To be fair lots of other apps have a cache buildup issue as well but nothing as severe as connect.
I’ve never cleared mine and just checked it, 1.04gb. I use the app an embarrassing amount, so I wonder if there’s one specific thing that takes up a bunch of space.
How long have you been using it?
A little over a year now. I switched over to Lemmy when the API stuff was happening on Reddit, but was on a different app for the first month or two.
That’s still around 7-8 months of thumbnails if you haven’t cleared it out. It’s too bad there isn’t a limit setting in the app.
Or it’s something else. That is a lot.
Apps have to download the thumbnails and whatever you actually click on.
Though that is a shitload.
Get SDMaid. Even the free version makes cleanup a lot easier.
I think the app needs to have a regular cash wipe build in, it causes Crashes for me.
Yeah, mine freezes on open sometimes which I suspect is the cache.
It should have an upper limit with the oldest access time items being evicted first.
It should be capped at 750mb it doesn’t need more and it wouldn’t be a problem if it just deletes the oldest stuff when its not needed anymore.
Yeah, that’s what I mean. But it needs to be done by access time, not oldest item, as you don’t want frequently used things to be evicted.
True, didn’t think about that, but yeah shure, your own PFP, banner and some community icons should probably stay in.
It’s standard practice to cache images when displaying, as an image viewed once is likely to be viewed again, and then it’s good to save on the data and latency by loading it from disk (or even memory).
However, it’s also standard practice to have an upper size boundary on this cache and to implement an eviction mechanism for the cache once it has reached its capacity.
This is probably a case of misconfiguration or something overlooked during implementation.
SDMaid actually open source (GPLv3) now!
The dev rebuilt the app for modern Android and made it open source
Mines up to 20gb. Searched the settings the other day to set cache size but couldn’t find anything.
I just checked and my cache was over 5GB. I agree that cache wiping should occur once in a while. Oh well, doing it manually worked well enough.
Pretty sure all the content you’re reading and watching is what’s in there. Do you watch a lot of videos?
