cross-posted from: https://poptalk.scrubbles.tech/post/3263324

Sorry for the alarming title but, Admins for real, go set up Anubis.

For context, Anubis is essentially a gatekeeper/rate limiter for small services. From them:

(Anubis) is designed to help protect the small internet from the endless storm of requests that flood in from AI companies. Anubis is as lightweight as possible to ensure that everyone can afford to protect the communities closest to them.

It puts forward a challenge that must be solved in order to gain access, and judges how trustworthy a connection is. For the vast majority of real users they will never notice, or will notice a small delay accessing your site the first time. Even smaller scrapers may get by relatively easily.

For big scrapers though, AI and trainers, they get hit with computational problems that waste their compute before being let in. (Trust me, I worked for a company that did “scrape the internet”, and compute is expensive and a constant worry for them, so win win for us!)

Anubis ended up taking maybe 10 minutes to set up. For Lemmy hosters you literally just point your UI proxy at Anubis and point Anubis to Lemmy UI. Very easy and slots right in, minimal setup.

These graphs are since I turned it on less than an hour ago. I have a small instance, only a few people, and immediately my CPU usage has gone down and my requests per minute have gone down. I have already had thousands of requests challenged, I had no idea I was being scraped this much! You can see they’re backing off in the charts.

(FYI, this only stops the web requests, so it does nothing to the API or federation. Those are proxied elsewhere, so it really does only target web scrapers).

  • Scrubbles@poptalk.scrubbles.techOPEnglish
    3·
    17 days ago

    See this message would have been better at the beginning of this thread, could have been a much better dialogue between us.

    I see in your script your doing the filtering at Anubis:

    request.path.startsWith("/api/")

    I did the opposite approach, I filter at my proxy/nginx and then only send web traffic to Anubis. With Lemmy since they’re 2-containers for web/api it looks like this:

                    set $proxpass "http://anubis:8080/"; # this was the webui, but now it handles web traffic, passing into lemmy downstream
                if ($http_accept ~ "^application/.*$") {
                  set $proxpass "http://lemmy:8536/"; #api
                }
                if ($request_method = POST) {
                  set $proxpass "http://lemmy:8536/"; #api
                }

    This way everything that goes to Anubis is 100% okay for it to handle. Then also if there are endpoints that may not work (someone called out oauth flow), you can filter those out to go directly the the UI.

    For PieFed, even if you don’t have a proxy in front now (which honestly would surprise me), I think it’d be better to add one then filter at that level. Let Anubis do what it does best, let Traefik/nginx/caddy/whatever do what it does best and route traffic.

    For safety you could do the reverse - allow everything and cut endpoints one by one.