@kirby @blockbot If I leave something out, I keep switching between fedi and acme and I hit "^W" to erase a word and instead it closed the tab, so I am retyping it and sometimes this makes a feller think he has mentioned something but instead, he has said nothing because history has been erased.

> the ip in the first snippet [84.239.12.133] actually belongs to a vps company

Yeah, a lot of VPNs just lease cheap VPSs. It's not Tor, Mullvad, Cloudflare, or ProtonVPN, and those are the only ones I have in my "tell me some shit about this address" script. This one looks like it's from privateinternetaccess.com, which is a paid VPN service.

> is this actually an approach they could've taken?

I don't know. I don't even know if it works. There are a lot of accidental DoSs, it's network code and the network got huge, but the dev teams didn't get more time, and people are always yelling "FEATURES FEATURES" and no one sponsors "Fix the holes" or "Can we make this not absurdly slow" or anything like that.

> is this someone that actually probably is not dumb but is doing dumb shit for some reason

They don't seem dumb, but I don't know why they have decided to try to DoS the pedo instances. It's a moderately clever attack but it's really noisy and it's easy to stop completely and the execution is really lazy.

Pedos have lots of websites, and you can't really remove someone from a decentralized network. I can understand why that might happen if the pedos were doing cop-bait shit and the admin was going out of his way to agitate, but they went after DRC, which is not a pedo instance (maybe confused DRC's Alice with someone on one of the other instances, there are a few people named that on those servers), so it can't be a response to anything they were actively doing, or this person would have started with whoever was actually causing trouble. Bored kid got a wild hair up his ass, no idea.
babyfuck.png