it's up! this time it went smoothly enough that it's been up for a bit as I've finished a few last bits and pieces. so far it looks like everything's holding steady enough, but I'm keeping an eye on things for now. the treat I mentioned is in the oven.
this post was submitted on 11 Nov 2025
10 points (91.7% liked)
important instance shit
165 readers
1 users here now
founded 2 years ago
MODERATORS
ignore that hiccup that was me
👏 👏👏
🎉
who here has money on this site being intentionally targeted by scrapers because we're Public AI Enemy No 1? 😉
Good luck with the update!
I think it's just incompetence (on the part of the scrapers) - been keeping an eye on and having to deal with it for other infra for a while now, and you get a strong impression of very yolo value setting in code-side control: terrible pause/resume flow control logic, fuckall in the way of actual load spread, fuckall sensible backoffs, etc
I'm reasonably certain that a lot of it is written in the lowest-effort ways possible with extremely shit implementation quality, because their focus is purely on getting as much data as quickly as possible and they don't give a single fuck to be good netizens
lemmy falls over at some pitifully low number of hits per second, it's just scraper shitheads
spammers are stupid
hard this, on both counts
Thanks for all the hard work! Running like a champ for me.
Just an fyi, www.awful.systems is giving me a 421 error at the moment. Maybe the dns record for the subdomain needs updating (or hasn't propagated yet)?
Apologies in advance if i'm being a goober.
Edit: it works!
ah, 421 is what iocaine returns when the request isn't garbage but there's no endpoint to handle it, so I might just need to configure an explicit redirect from www.awful.systems to awful.systems in nginx
a most wonderful stanza:
server_name ...;
rewrite ^ https://$server_name$request_uri? redirect;
not strictly applicable in this case ofc (it specifically is for https upgrade while keeping all other bits), but I just figured I'd put it here so other people can crib it
(the amount of god-awful regex matching I've seen for that before....)
lol I didn't even know that subdomain existed
421 is part of the defense check, probably just an unhandled fqdn in the config
e: records match, so yeah probably just unhandled fqdn. have pinged @self
I think this should be fixed now! for me in both firefox and curl, www.awful.systems now redirects to awful.systems.
Thanks for the hard work!