this post was submitted on 17 Feb 2026
42 points (100.0% liked)
Fediverse
40470 readers
395 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, 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)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's complicated.
You could federate with millions of instances if the people using them are not doing very much. But a handful of instances could theoretically overwhelm the whole network if they had malicious bots spamming like crazy.
The instance that hosts a community is responsible for sending copies of everything to all following instances, so most of the load is on those instances that host lots of popular communities. All other instances just need to be powerful enough to keep up with what they receive, which is 100x less work.
So even more important than spreading users out among instances, is spreading communities out among instances. Communities cause most of the load.
In other words, it's better to have multiple of the same communities among different instances, and not too big either?
Generally I think duplication isn't great because it means people subscribe to all of them and cross-post in all of them. A lot of client apps don't deal with this well, yet.
I mean just have a community for cats on instance 1 and a community for dogs on instance 2.