archive.today and archive.ph (also .is, .md, .fo, .li, .vn) could be Russian assets.

  • 10 Posts
  • 1.13K Comments
Joined 9 months ago
cake
Cake day: March 5th, 2025

help-circle


  • The only non-lemmy.world account: Melon Husk™@sh.itjust.works
    Banned in some community because: Widely reported as a likely unmarked bot using an LLM to generate engagement bait
    (Profile not deleted)

    telokic, sededor, pali, Yecoh, vanes, henaw2, kogito @lemmy.world: gone

    All post sorta normal news stories as “YSK”.

    As others probably pointed out already, this is likely somebody playing with LLM bots (unmarked). Good riddance. Not sure about the first one though.











  • If crowdsec works for you thats great but also its a corporate product

    It’s also fully FLOSS with dozens of contributors (not to speak of the community-driven blocklists). If they make money with it, great.

    not exactly a pure self hosted solution.

    Why? I host it, I run it. It’s even in Debian Stable repos, but I choose their own more up-to-date ones.

    Allow me to expand on the problem I was having. It wasnt just that I was getting a knock or two, its that I was getting 40 knocks every few seconds scraping every page and searching for a bunch that didnt exist that would allow exploit points in unsecured production vps systems.

    • Again, a properly set up WAF will deal with this pronto
    • You should not have exploit points in unsecured production systems, full stop.

    On a computational level the constant network activity of bytes from webpage, zip files and images downloaded from scrapers pollutes traffic. Anubis stops this by trapping them in a landing page that transmits very little information from the server side.

    • And instead you leave the computations to your clients. Which becomes a problem on slow hardware.
    • Again, with a properly set up WAF there’s no “traffic pollution” or “downloading of zip files”.

    Anubis uses a weighted priority which grades how legit a browser client is.

    And apart from the user agent and a few other responses, all of which are easily spoofed, this means “do some javascript stuff on the local client” (there’s a link to an article here somewhere that explains this well) which will eat resources on the client’s machine, which becomes a real pita on e.g. smartphones.

    Also, I use one of those less-than-legit, weird and non-regular browsers, and I am being punished by tools like this.

    All the self hosters in my internet circle started adopting anubis so I wanted to try it. Anubis was relatively plug and play with prebuilt packages


    edit: I feel like this part of OP’s argument needs to be pointed out, it explains so much:

    All the self hosters in my internet circle started adopting anubis so I wanted to try it. Anubis was relatively plug and play with prebuilt packages


  • IMO this is largely Debian-specific: this distro seems to hold backward comaptibility in very high regard, so any problem is bound to have a multitude of solutions. In addition, the Debian Wiki is not as well maintained as you-know-whose.

    I see nothing untoward here.

    Except maybe that last sentence, what “s” are you talking about (fwiw, the man page that comes with an installed package should™ be the ultimate authority)?



  • At the time of commenting, this post is 8h old. I read all the top comments, many of them critical of Anubis.

    I run a small website and don’t have problems with bots. Of course I know what a DDOS is - maybe that’s the only use case where something like Anubis would help, instead of the strictly server-side solution I deploy?

    I use CrowdSec (it seems to work with caddy btw). It took a little setting up, but it does the job.
    (I think it’s quite similar to fail2ban in what it does, plus community-updated blocklists)

    Am I missing something here? Why wouldn’t that be enough? Why do I need to heckle my visitors?

    Despite all that I still had a problem with bots knocking on my ports spamming my logs.

    By the time Anubis gets to work, the knocking already happened so I don’t really understand this argument.

    If the system is set up to reject a certain type of requests, these are microsecond transactions of no (DDOS exception) harm.