Adding an optional anubis config by dessalines · Pull Request #285 · LemmyNet/lemmy-ansible
github.com
This adds an optional anubis, which stands in front of lemmy-ui only. It doesn't block or impede federation, or apps, only the lemmy-ui front end. I tested this via a fresh server, and it worked.

I’ve recently added anubis to lemmy.ml, and it seems to be working well.

I have a PR to add anubis to lemmy-ansible (our main installation method), and I could use some help tweaking / optimizing its botPolicy.yaml config, for federated services.

Anyone with experience running anubis, this would be much appreciated.

    • Björn@swg-empire.deEnglish
      10·
      1 day ago

      I regularly encounter images not loading from quock.au. No idea if they’ve got that under control now but that is the most visible issue every instance fights with. Gonna be great when we have a recommended configuration for Lemmy.

      • Dessalines@lemmy.mlOPEnglish
        7·
        1 day ago

        Yep, essentially the botPolicy.yaml there could be a collectively developed anubis config, based on what works best.

      • Otter@lemmy.caEnglish
        4·
        1 day ago

        We are not running Anubis, although we do block a large number of AI/LLM companies through IP addresses. Each time we block a new one, it makes a noticeable difference in the performance graphs.