Hi everyone, I’m having trouble finding a Lemmy instance that works well for me. The main instance I use is down, and most others are too slow. I’m wondering if there’s a way to choose an instance based on latency and the least blocked users. I found two relevant issues on the awesome-lemmy-instances GitHub page: issue #12 about choosing an instance based on latency and issue #17 about choosing an instance with the least blocked users. However, I’m not sure how to implement these into the main script to generate a readme with a few recommended instances. Does anyone have any advice or tips on how to choose a Lemmy instance based on these criteria? Thanks in advance for your help!

  • Jeena@jemmy.jeena.net
    link
    fedilink
    English
    arrow-up
    17
    ·
    1 year ago

    For those two specifically I’d suggest to host one yourself. You then are 100% in control over blocking users/instances and the latency is super short because you’re the only one on the server. That’s what I’m doing.

    • RxBrad@lemmings.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      What kind of storage requirements are there?

      It feels like you’d eat up a lot of storage, fast. Especially if you subscribe to anything video/photo-related.

      • Jeena@jemmy.jeena.net
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 year ago

        With Mastodon yes because it caches everything on your server, but with Lemmy no, because it hot-links media from the other server without caching it.

        jeena@Abraham:~/lemmy/volumes$ du -sh *
        8.0K	lemmy-ui
        5.2G	pictrs
        2.8G	postgres
        

        I’m subscribed to around 50 communities for about 2 months.

        • RxBrad@lemmings.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Huh. That’s surprisingly light.

          I self-host my own Mastodon server and relay about 50 hashtags (no full servers). Even with media getting flushed every 3 days, it still hovers around 20GB.

          I’m probably gonna do it now, because of course I will.