> You probably had trouble accessing #Fosstodon for the last few hours. That's because we have (and still are) the target of a DDoS attack. Fosstodon was the target, but other Masto.Host customers were impacted because of it (sorry about that, folks!)
> Unfortunately, we've had to take the decision to put Fosstodon behind #Cloudflare to mitigate the attacks. I don't like it either, but we need to do what we can to keep the lights on.
So the DDoS attack took out a central Mastodon hosting provider, knocking down many instances at once? So decentralized! /s
Even worse. None of that remotely helps given that many instances under the umbrella of Masto.host got DDoS'd and knocked straight down and had to re-centralize to Cloudflare as a so-called 'mitigation'.
Once Cloudflare goes down, so does every other instance using it. If they are not using Cloudflare, then they easily get DDoS'd just like the other vulnerable instances.
Another failure and abandoning of such systems to refrain from the re-centralization of the web. As expected.
> You probably had trouble accessing #Fosstodon for the last few hours. That's because we have (and still are) the target of a DDoS attack. Fosstodon was the target, but other Masto.Host customers were impacted because of it (sorry about that, folks!)
> Unfortunately, we've had to take the decision to put Fosstodon behind #Cloudflare to mitigate the attacks. I don't like it either, but we need to do what we can to keep the lights on.
So the DDoS attack took out a central Mastodon hosting provider, knocking down many instances at once? So decentralized! /s
Solution? Re-centralizing back to Cloudflare.
[0] https://fosstodon.org/@kev/109953654645367614