UPDATE: @SDF@lemmy.sdf.org has responded
It is temporary as lemmy.world was cascading duplicates at us and the only way to keep the site up reliably was to temporarily drop them. We’re in the process of adding more hardware to increase RAM, CPU cores and disk space. Once that new hardware is in place we can try turning on the firehose. Until then, please patient.
ORIGINAL POST:
Starting sometime yesterday afternoon it looks like our instance started blocking lemmy.world: https://lemmy.sdf.org/instances
This is kind of a big deal, because 1/3rd of all active users originate there!
Was this decision intentional? If so, could we get some clarification about it? @SDF@lemmy.sdf.org
What happened on mastodon.social?
It’s an absolutely massive instance that’s a net negative for the Fediverse. It completely defeats the purpose of federation. The Mastodon devs used to drive people to smaller instances but decided they wanted to be /the/ instance. They made themselves a default in the app. At around the same time other instances started getting a crap ton of spam from them that ate up a bunch of moderator’s time on smaller instances. The Fediverse only works in regards to moderation because there is less users per admin, but mastodon.social doesn’t have that advantage. A bunch of people defederated from them as a result which was a good thing for the instances that did it. They failed pretty hard at communicating during this time as well.
Having one instance hold a large part of the network is bad for everybody involved. Defederating from monoliths is a healthy thing for networks to do. Building your own web beats any algorithm, can’t do that if you’re already federating with 99% of people.
It’s the biggest instance by far, to the point of being virtually non-viable to defederate from. If they ever sell out or make decisions other instances don’t like, tough cookies.
Already happened.