Heard it was DDoS attacks, which seems pretty likely.
Another benefit to using a smaller instance (or hosting your own), you don’t have to worry about this stuff
Hopefully they don’t try to mess with Beehaw, y’all are too nice :)
Heard it was DDoS attacks, which seems pretty likely.
Another benefit to using a smaller instance (or hosting your own), you don’t have to worry about this stuff
Hopefully they don’t try to mess with Beehaw, y’all are too nice :)
Large instances need to get Cloudflare DDoS protection because it will only get worse.
This does wonders at keeping the instance up, but breaks the mobile apps and federation functionality sadly ☹️
My instance is using Cloudflare and has no issues with federation or mobile apps (I sent this reply with Connect).
Assuming a standard caching configuration, those services should not break under Cloudflare.
Sorry I should have been clearer in my original comment - the DDoS mitigation features of Cloudflare specifically affect the apps and federation, so as long as you aren’t under attack it’s business as usual
Ah fair enough, I think most would be fine with that compromise tbh
Oh Damn. So the community still needs to figure it out…
But you can still DDoS with federation. I’m not sure how we’d avoid breaking the idea that anyone can make a server and start federating immediately. Federation naturally is an automated task, so can’t get past this protection.