I’ve enjoyed using Connect but I’ve got no clue how it got this big.

  • BearOfaTime@lemm.ee
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    14 days ago

    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.

      • Chris@feddit.uk
        link
        fedilink
        English
        arrow-up
        4
        ·
        14 days ago

        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.

        • BonerMan@ani.social
          link
          fedilink
          arrow-up
          1
          ·
          14 days ago

          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.

          • Chris@feddit.uk
            link
            fedilink
            English
            arrow-up
            3
            ·
            14 days ago

            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.

            @kuro_neko@lemmy.ca

            • BonerMan@ani.social
              link
              fedilink
              arrow-up
              2
              ·
              14 days ago

              True, didn’t think about that, but yeah shure, your own PFP, banner and some community icons should probably stay in.

    • GissaMittJobb@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      14 days ago

      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.