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).
 
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.
The main issue is that im running on a raspberry pi 3b 32-bit 1gb ram potato, running off an external harddrive from 2012. I dont want to upgrade the hardware, the git hosting has working fine for years for real users (tens of thousands of users, because they dont spam crawling the git frontend files). Im pretty sure the CPU just comes from crawling the git files, the cpu usage is acceptable when the user agent is blocked, which happens after TLS.
 
Last edited:
So if I am reading this Xlibre/Artix shit correctly:

"Artist" gets kicked from Xlibre for behavior unknown.
Artist starts building (or claiming to build - apparently nous disagrees?) Artix iso's with Xorg again rather than Xlibre. Also leaves the SonicDE project.
When asked about it, claims Xorg is now the better choice for Artix users.
"callmetango" chimes in, posts big thread claiming to disprove Artist's claims, asks him "whats really going on".
Thread deleted.
Xlibre puts out X post talking about it, and github site in case Xlibre is demoted/removed in Artix.

Smells like butthurt but wdik.

Edit: just posted more from Xlibre's telegram. nous chimes in and makes fun accusations of his own contra Xlibre.
 
Last edited:
1784992582243.png
(src) (github)
Open-source developer Ching-Chun (Jim) Huang wrote in about the work he is pursuing with libx11-compat as a lightweight compatibility layer for X11 clients. For Xlib-dependent applications it can run without source code changes such as with macOS without XQuartz, Wayland-only Linux desktop sessions, headless CI environments, Android, and other non-x11-native platforms. The libx11-compat library is an in-process implementation of the X Window System client library and built atop SDL2/SDL3, SDL_ttf, and Pixman.

The code can currently run a number of classic X11 applications like XMosaic, Qt2 apps, XCircuit, XMMS, and more without an X Server.
 
Then why not have just stuck to the tearfree-patched Xorg in the first place and leave XLibre to the Gremlins repo if it's really that bad? The tearfree patch had been intentionally sitting unused by the freedesktop troons for years.

I expect problems to surface when dealing with a huge code base in the core X11, none of which I've personally run into with XLibre.
 
Last edited:
A few statements in there are concerning. Claim: some kind of meeting was asked for to clarify what the issue was regarding the weekly ISO. Nous doesn't deny this, instead just says you aren't owed a meeting, we had forum reports and broken boxes to deal with. Ok, so you just ignore talking to the people putting together the software you switched to? They're supposed to read your forum? Odd.

At this point, just air everything out. Dump the logs. Someone is being a cunt.
 
Back
Top Bottom