the instance is going down for a bit at 8 AM GMT on November 12th to finally put us behind iocaine, which should hopefully reduce or eliminate the amount of 503 errors we’re seeing (since all of them are scrapers pushing over the instance) and expose some metrics for admins trying to keep track of how our instance is performing
I’m also working on a bit of a treat for our regulars who’ve been putting up with the 503s for a while. that will probably be announced a bit after the downtime completes.
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!
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
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