With Meta beginning to test federation, there’s a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don’t think those are the main issues. Imo, Threads presents a serious danger to the long-term viability of the fediverse if we become dependent on it for content, and our best bet at avoiding that is defederation.
Let’s start with these three statements, which should hopefully seem pretty reasonable:
- It’s dangerous for one entity to dominate the activity pool. If, say, one person’s instance contributes 95% of the content, then the rest of the fediverse becomes dependent on that instance. Should that instance defederate, everyone else will have to either live with 1/20 of the content or move to that instance, and good luck getting the fediverse to grow after that. By making everyone dependent on their instance for content, that one person gains the power to kill the fediverse by defederating.
- Profit-driven media should not be the primary way people interact with the fediverse. Open source, non-corporate instances should be able to grow, and that growth will be stunted if most people who want to interact with the fediverse are deciding to go to corporate, profit-driven instances. Furthermore, lots of people went to the fediverse to avoid the influence of these large corporations on social media, and it should still uphold this purpose.
- People should enter the fediverse with an idea of its purpose. If someone’s on the fediverse, they should be aware of that fact and aware of the fediverse’s goal of decentralized media. People should think of the fediverse as every instance contributing to a decentralized pool of content, not other instances tapping in to their instance as the main pool.
Now, let’s apply these to federating with Threads:
- This point alone is more than enough reason to defederate from Threads. Threads has millions more active users than all of the fediverse combined, and it’s in much better of a position to grow its userbase due to its integration with Instagram. If we federate with Threads, it will dominate content. And that’s not mentioning all of the company accounts on Threads that people have expressed an interest in following. While all of this new activity may seem like a good thing, it puts everyone in a position of dependence on Threads. People are going to get used to the massive increase in content from Threads, and if it ever defederates, tons of people on other instances are going to leave with it. Essentially, Zuckerberg will eventually be able to kill the fediverse’s growth prospects when he wishes and nab a bunch of users in the process, both of which he has incentive to do.
- If we federate with Threads, Threads is undoubtedly going to seem like the easiest way to access our pool of content (at least on the microblog side of things). Newcomers already get intimidated by having to choose a Mastodon instance; give them access via essentially just logging into their Instagram account, and they’ll take that over the non-corporate alternatives. Federation with Threads means that most of the people who want to see the content we make are going to go to Threads, meaning platforms like Mastodon & Kbin will be less able to grow.
- When people go to Mastodon, Kbin, Lemmy, Firefish, Misskey, etc., they do so knowing they’re going to the fediverse. When people go to Threads, most do so because they have an Instagram account. I’d bet that when Threads gets federation up and running, most people on Threads won’t have a clue that they’re on the fediverse. Those who do know will probably think of it as all of these small, niche platforms that are kinda offshoots of Threads. That’s not the mentality that should pervade the fediverse.
I think that all of this is makes defederating from Threads a no-brainer. If we don’t, we’ll depend on Meta for activity, platforms that aren’t Threads won’t grow, and the fediverse will be primarily composed of people who don’t have even a vague idea of the purpose behind it. I want more activity as much as the next guy, but that activity being beholden to the corporations most of us want to avoid seems like the worst-case scenario.
“But why not defederate later?”
If we don’t defederate now, I don’t think we’re ever going to defederate. Once the fediverse becomes dependent on Threads for most of its content, there’s no going back. If anything, it’d get worse as Threads outpaces the rest of the fediverse in growth and thus makes up a larger and larger share of activity. Look at how desperate everyone is for activity — even if it means the fediverse being carried by Meta — right now, when we’re not used to it. Trying to get instances to defederate later will be nigh impossible.
“Why not just block Threads yourself?”
Even if that were a feature, it completely ignores the problem. I don’t dislike the people on Threads, and I don’t think their content will necessarily be horrendous. The threat is people on non-corporate fediverse platforms becoming dependent on Daddy Zuck for content, and that’s something that can only be fought with defederation.
To close, imagine if Steve Huffman said that Reddit was going to implement ActivityPub and federate with Lemmy & Kbin. Would you want the fediverse to be dependent on Reddit for activity? Would you trust Huffman, who has all the incentive in the world to pull the plug on federation once everyone on Lemmy & Kbin is hooked to Reddit content? This is the situation we’re in, just with a different untrustworthy corporation. The fediverse should not be at the mercy of Threads, Reddit, The Site Formerly Known as Twitter, or any other corporate platform. It’s better to grow slowly but surely than to put what we have in the hands of these people.
Let’s look at the strings
That’s all true. But that’s not really a string - it’s just a fact of any for-profit organisation that sets up an instance
But he can do that anyway. And in fact people who who want to interact with the 140million ish Threads users currently have one option - join Threads. With federation I can communicate with Threads users without joining Threads. That needs to be factored in.
Correct, and it’s a fact that’s horrendously bad for an organization that’s going to harbor a vast majority of the content on the fediverse.
The people who are at currently at this point have already gone to Threads. The main issue I see is everyone getting used to the 50x boost in activity that Threads provides and then Meta removing that by defederating, pulling people to Threads when they wouldn’t have gone there otherwise. Allowing ourselves to become dependent on Meta lets them get users they wouldn’t have before and kill the growth prospects of platforms like Mastodon, both of which they have incentive to do.
You say: The people who are at currently at this point have already gone to Threads. Then you say that if traffic from Threads is subsequently withdrawn, all the people who haven’t already gone to Threads will… go to Threads.
You are basing it on the idea that Threads federating is a temporary move designed to advertise Threads. It’s a theory. But seems unlikely. If Threads goes away again, I suspect that the current Fediverse userbase will, by and large still be here.
Let me clarify. When I say, “The people who are currently at this point…,” I mean the people who right now feel that they need to interact Threads. If they do, they’re probably there. My issue is that if people are dependent on Threads for the vast majority of microblog activity, more people will feel that they need to keep that interaction with Threads. I’m not seeing how this is some far fetched theory more than it is straight up inevitable. If activity increases by 50x because 98% of the content is now coming from Threads and most of whom people are following are on Threads, more people will feel the need to stay connected. I don’t see how it could be otherwise. This means that if an instance wanted to defederate from Threads for any reason or if Threads defederated themselves (which they have tons of incentive to do later down the line), tons of people would leave.
To give you an example, imagine if kbin.social was to defederating from lemmy.world and lemmy.ml due to unhappiness with their moderation. Obviously, defederating from any instance is going to lose you some users, but those two instances harbor a massive portion — probably a large majority — of the content on the threadiverse. Tons of people would leave kbin.social for the simple reason that most all of the activity that they were used to would be gone otherwise.
Now, with Threads, there is some resistance in the fact that Meta is a massive for-profit corporation. Many people won’t move to Threads on principle. However, this is countered by the extremely strong pull factor of the sheer percentage of activity Threads would harbor. If people get used to all of that activity based on Threads and are following mostly Threads accounts, tons of those people will leave an instance should that instance defederate later on or jump ship from the fediverse to Threads should Meta cease federation. And among those who don’t leave, there will likely be a lot less motivation to post after such a drop in activity and interaction.
I don’t see how dependency on Meta for the vast majority microblog content could possibly be a good idea. If Kbin were to implement a silencing feature like what Mastodon apparently has, where Threads content would be invisible outside of Threads users that you’ve followed, I think that’d be fine. That way, people could intearct with a few Threads accounts they’re especially interested in as opposed to the public microblog feeds being 99% Threads and us being dependent on Threads to maintain the activity of those feeds. But just letting them flood our microblogs seems like an extremely dangerous idea that’s wholly unnecessary, and I haven’t been convinced otherwise.