this post was submitted on 08 Jul 2023
111 points (100.0% liked)
Fediverse
28216 readers
123 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This seems like a more viable argument than much of the EEE stuff, in regards to Threads v Mastodon.
But I simply don't understand the ins-and-outs of how Threads stuff gets federated, and how much toll it would actually put on other servers.
My (limited) understanding of ActivityPub is that it functions on a publish-subscribe model. If you and I both ran instances and federated with each other, every time a message was posted to my instance I'd send a message to you and vice-versa. Now, let's say a new person comes along with their own instance and they want to federate with us, but they have 1000x more users than we do. If we federate with this new instance, we now both have to handle 1000x more traffic.
This is effectively a Denial Of Service attack.
Threads currently (supposedly) has 70 million users. If only 0.001% of those users are interacting with federated content every second, that's still 1000 messages every second. Smaller instances are likely not configured or tuned to handle this level of traffic on top of their existing traffic.