The Linux Thread - The Autist's OS of Choice

How do you guys deal with AI crawlers on your home server? I got anubis, but some other bots are bypassing it. I had to block windows and macos user agents, but the other day I saw some using android user agent instead. Soon I'll have to block everyone except linux desktop users from accessing my server to make it usable.
The AI crawlers kill my server, making all cores run at 100% which results in the server timing out requests.
I've mitigated things somewhat by blocking most of the far east and india, but I'm currently getting raped by dutch IP addresses. I'm probably going to shut off http for a while until I can figure it out.
 
I've mitigated things somewhat by blocking most of the far east and india, but I'm currently getting raped by dutch IP addresses. I'm probably going to shut off http for a while until I can figure it out.
There's a lot of foreign-owned hardware in Dutch datacenters. If it's a home server, does it need to be accessible to every Tom, Dick and Harry in the first place? Routing your personal connections over Tailscale or an alt-net like CJDNS/Yggdrasil could work.
 
Canonical are a bunch of niggers.
t. Tried updating to kernel 7.0.0-28
 
And Artist deleted the post, an indictment against my expectations of a "based distro" being too high to not screenshot and archive.
Xlibre has a guide to install their own repo of xlibre for artix here if anyone is interested: https://github.com/xlibre-artix/xlibre-artix

Dont know why a bleeding edge distro like artix is still running a older, although still maintained, version of Xlibre. 25.2 is in beta and artix packages are still using 25.0 instead of 25.1.
 
How do you guys deal with AI crawlers on your home server? I got anubis, but some other bots are bypassing it. I had to block windows and macos user agents, but the other day I saw some using android user agent instead. Soon I'll have to block everyone except linux desktop users from accessing my server to make it usable.
The AI crawlers kill my server, making all cores run at 100% which results in the server timing out requests.
Do you know what the cause is of the CPU usage? If you're just hosting static files it's likely from the TLS cryptography routines, blocking based on user agents won't help in that case I think. You would have to upgrade the hardware or become HTTP-only (which is totally fine).
With dynamic content (like your git frontend I suppose) you need some caching strategy. When nobody is purposefully DDOSing you, blocking is very niggerlicious.
 
Dont know why a bleeding edge distro like artix is still running a older, although still maintained, version of Xlibre. 25.2 is in beta and artix packages are still using 25.0 instead of 25.1.

How about Artist clears the air on what the fuck is actually going on between Artix and XLibres upstream? Because at least one person who witnessed the aforementioned exchange is already assuming that this could lead to a demotion of the xlibre packages from first-class to AUR-only like upstream Arch Linux.
 
There's a lot of foreign-owned hardware in Dutch datacenters. If it's a home server, does it need to be accessible to every Tom, Dick and Harry in the first place? Routing your personal connections over Tailscale or an alt-net like CJDNS/Yggdrasil could work.
It's a VPS. Niche forum, self-hosted e-mail, bunch of parked domains and a nameserver.

people are using http?

letsencrypt is free and easy
If I was talking about encryption, I'd say so. HTTP in this context is a shorthand for the server stack on ports 80 and 443 (and whatever else it might be serving).
 
Back
Top Bottom