This is a little bit of a wall of text but I hope it will be a nice sample for such a setup.

    • AYO_Official@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      The principle is pretty simple : use a little bit of compute. If you’re a bot and want to visit many sites the cost will add up, if you are a human going to a website the 1 second cost for the initial page is not a big deal.

      Also notice the difference with the extremely annoying cloudflare checkbox asking if you are a human that became ubiquitous lately. I’d rather wait a second.

  • Taasz/Woof@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I feel like a simple rate limit set to what your server can handle without issues is a better solution. Or combine it with Anubis at least.

    • AYO_Official@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      This seems to be exactly the content of the post: rate limit + Anubis.

      The main point is more about “How to setup Anubis” rather than “Should we use Anubis” as I documented how I did my setup so I will not forget and at the same time sharing the resource. I am also using fail2ban but I didn’t feel a post about how to set ip up would be as useful as documentation and guides seems already there.