The Fediverse has a DDoS problem
The Fediverse has a DDoS problem
The Fediverse has a problem with accidentally DDoS-ing remote service. What can we do about it?
I was recommended to share this article I wrote a few days ago on here, too; so here we are!
The TL;DR is "link embed fetching communes" as a partial "fix" to the issue (pretty buzzwordy, sorry for that)
-
The proposed solution of an intermediate server caching embeds is needlessly complex. The first server a link is posted to can fetch the embed, then push it out to every server receiving the post.
-
Actually an interesting point. My immediate concern with that idea is that it would open the door for disguising things for what they aren't. The solution was made from the general caution of not trusting remote servers regarding content they not necessarily control.
But yes, that would definitely be a solution, too.
-
-
How is this not a caching issue on the linked server? Serving the same info up over and over from memory should be incredibly fast.
Are their pages dynamic and filled with ads and stuff or something that makes this a problem?
-
If you’ve skimmed over the original publication, it is actually worse: it is a non problem. Other users have pointed out already: ~100MB served over 5 minutes period is quite literally nothing for even one small VPS serving the content independently, let alone a site with CloudFlare in front like they claim to have.
-