I think fediverse servers should adopt a set of sustainable limits for themselves, one of which should be: do not maintain more than X active users. If they have over that amount, they should shut down signups. If they don’t shut down signups, everyone else should defederate them until they cooperate.
What instance hasn’t defederated from threads honestly
Fucking Mastodon
Fosstodon had the balls to not sell out
Also Meta has not federated yet but said they will in the future so any “defederation” from instances is just a declaration of future plans since there is nothing to cut off yet
Honestly one needs to look at the economic ensentives in order to understand metas goals.
Meta does not make any money from content on the federverse. Therefore, they have no reason to support its growth or future. In fact I would go as far as to say that they actually are going to try and EEE.
They aren’t going to try to EEE. ActivityPub was just an easy protocall to build off of quickly. They don’t care about the fediverse. They have almost zero incentive to waste effort trying to destroy it, plus it’s open source, so worst case we just fork it and move on.
ActivityPub was just an easy protocall to build off of quickly
If they didn’t want to federate, they wouldnt have a need for ActivityPub or any kind of similar protocol.
EEE means embrace, extend, extenguish. It’s to say they’ll start using it, extend it so they are required to continue using it, then stop supporting it or actively kill it. It has nothing to do with federation, whether they do or don’t.
I know that, but if that’s not the goal, then what else do they hope to achieve by implementing ActivityPub? It means they plan to federate with the larger fediverse, and you can bet that there’s a carefully calculated business reasoning behind it.
They likely used it because most of the work is already done. They could quickly turn around a new app as they notice Twitter fucking up, rather than starting from scratch. It already exists, works, and is tested.