Meta has launched a twitter alternative called "Threads". The application allows Instagram accounts and followers to be migrated directly. From what I can find, there are already over 90 million users using threads.[1] It is Meta's plan to allow Threads to interact via ActivityPub with other platforms in the fediverse.
Mander has a generally open federation policy. I don't want to prevent users from accessing specific content through the fediverse purely on ideological grounds, nor do I want to block our information from being accessed. There is a very strong argument to be made to remain federated with Threads in the spirit of having an open and accessible network.
But, after seeing the rushed, non-transparent, and non-EU compliant way that Threads is being deployed, it is obviously not wise to remain federated during the deployment phase. I would be willing to re-federate once it is proven that we can federate with them safely, it is demonstrated that a good amount of value to the users is added by doing so, and that at least a portion of the users is interested in doing so.
Reasons to defederate:
-
The fediverse already lives in a legal gray zone in many respects. Threads was not released into the EU due to regulatory concerns.[2] My server is based in the Netherlands. It appears like no one is sure about what the legal implications are, but I consider federating interactions with Threads to present a new liability with a larger amount of risk. The added risk is related to the fact that Meta is often being looked at by regulators, and instances could be pulled into a Meta-related investigation. A hypothetical example - and I don't know if this is accurate or not - federated comments from EU users that end up saved in Meta's servers could be construed as a GDPR violation due to the transfer of EU user data. These are risks that are already present in the fediverse, but interacting with Meta may increase the likelyhood of being pulled into a Meta-related legal problem.
-
Threads is being released in a very hurried manner to capitalize on the unpopularity of Twitter at the moment. They are deploying these tools at random times without first informing the world about how they work. As far as I can tell, they have told us nothing about how they will actually use ActivityPub. All that we know is that suddenly hundreds of millions of people will be able to take actions that in some way interact with our servers. A likely scenario is that this will be similar to mastodon, their users will be able to make comments to a Lemmy server, and this won't cause a problem. But they may choose to do something differently, or they can make a mistake in their implementation. A mistake at the scale of hundreds of millions of users would easily deal catastrophic damage to a small instance.
-
The developers of Lemmy have strongly encouraged instance admins to defederate with threads. They develop this platform and know it much better than I do. I respect them and trust their judgement, so a strong encouragement coming from them is something that I take very seriously.
-
Most users who have commented on this topic here and in other instances want to defederate. While I do prefer to take a stance in favor of a more open federation policy, I do think that the case of a giant corporate entity deploying a potentially destructive platform into the fediverse is a special case.
Generally I prefer to assume good faith and only defederate as a last resort in response to a practical problem. In this case, we are dealing with a commercial for-profit entity that has a strong record of not acting in good faith. The massive scale of this thing is such that we could lose the luxury of being able to easily respond to a sudden practical problem.
I don't love Meta, and they are most likely not joining the space because they are passionate about helping us create privacy-centric decentralized social networks in which profit and growth are not the motives. But this is an opinion. In the future, if users actually want that, I am committed to re-assessing and potentially re-federating once the dust settles. But I can't justify taking this level of risk at this time.
If no one asks for it, I wouldn't actively try to re-federate.