:hacker_f::hacker_s::hacker_e:
There are some minor slowness issues; the pipe is clogged. Abnormally high request volume for a Saturday night. One of the issues is boring: we're getting flooded with deletes because Mastodon is retarded about deletes, and three users that have a lot of posts (names aren't similar but they might all be the same person) have decided to delete their accounts (or they got banned), so that's one delete per user. Most instances this floods pretty badly; some instances have had to reject deletes during deletestorms because it is expensive to do this one at a time, swamps the DB. (If you are getting a lot of deletes, you might want to consider temporarily ignoring them.)
The other issue is we're getting flooded with requests from someone's attempt to scrape a handful of Poast accounts via FSE. They're doing this via Tor, so the fix is based on behavior rather than traffic source. All of those accounts were on the previous list of accounts from the last time this kind of scraping happened; it's been at least several months since this specific guy cropped up, I think at least a year. (Other accounts on the list included their Gab accounts, associated accounts, etc.) I suspect it's the same guy as last time, because it's the same accounts and their bot is also too goddamn stupid to notice errors, it's still hitting those accounts even after I turned the screws on the rate-limiting for that. I don't know why anyone would hammer my server to get all of the posts by these guys, but that guy can go fuck himself.
The deletes shouldn't affect anyone here, but some Poast accounts' pages will be inaccessible for a while. The accounts will still be visible, you will be able to interact with them like normal, but if you try to view their pages, you will get errors. It looks like there weren't any 5xx errors that resulted from that, but it has jammed up the pipes a bit.
There's also some other weird shit going on at the moment that should make a bit more sense once that noise is cleared up.