Patience, AI crash bubble burst will be soon.
this post was submitted on 08 Jun 2025
151 points (97.5% liked)
Fuck AI
3020 readers
1083 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
founded 1 year ago
MODERATORS
๐ค
Just cache. Read only traffic should add negligible load to your server. Or you're doing something horriy wrong
They are 1 cpu and 1 gb of ram pods, postgres goes to 100% cpu on 500 requests per minute, after i put the NGINX extension, it reduced to at max 10%. On weaker servers, these bots make hell on earth, not the config.
If it's hitting postgres it's not hitting the cache. Do you have a caching reverse proxy in front of your web application?
You can either use Cloudflare(proprietary) or anubis (Foss)
Don't do this
Why?
Cloudflare has pretty good protection against this, but I totally understand not wanting to use Cloudflare
Haha, just wait when you get ddosed by anonymous user agents. I have been there.
I'm talking 40k requests per 5 seconds.
You can enable Private Instance in your admin settings, this will mean only logged in users can see content. This will prevent AI scrapers from slowing down your instance as all they'll see is an empty homepage, so no DB calls. As long as you're on 0.19.11, federation will still work.
Same for Mbin.
Enabled, thanks for the tip!
At some point they're going to try to evade detection to continue scraping the web. The cat and mouse game continues except now the "pirates" are big tech.
They already do. ("They" meaning AI generally, I don't know about Claude or ChatGPT's bots specifically). There are a number of tools server admins can use to help deal with this.
See also:
these solutions have the side effect of making the bots stay on your site longer and generate more traffic. it's not for everyone.
Use Anubis. That's pretty much the only thing you can do against bots that they have no way of circumventing.
Yeah, going to install it this week, but the nginx extension seemed to solve the issue.
Which extention are you using if I may ask?