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.
Reposting this discussion for posterity
Big takeaways, emphasis preserved from the original:
Threads is entering a space in the fediverse which is dominated by Mastodon, so it’s Mastodon and other fediverse microblogging services (including, to some extent, /kbin) which will most heavily feel the impact of Threads.
Defederating another server means your instance will stop requesting content from that server. … Defederation is about what data comes in, not what goes out. … Defederation doesn’t make you invisible, it doesn’t block anybody else from seeing you, it doesn’t protect your content, it only means you never have to see their content.
Firstly, the fediverse is a drop in the ocean compared to Threads (104 million registered users). Obviously, Meta wants everybody, but their specific goals in terms of user-poaching are far more likely to center around the ~350 million active Twitter users than the ~12 million fediverse users (~3.5 million active). The threadiverse [Lemmy, Kbin, et al] is smaller again, at something like 100,000 active users.
“Threads will overwhelm the fediverse with their inferior content and culture.” Like the EEE fears, this one is legitimate but once again something that will primarily be felt by microblogging providers (/kbin included). Toxic users, advertisers, etc. can push garbage into feeds all day, but they will largely not be targeting the threadiverse because there’s some 100 million sets of eyes to put that crap in front of on the microblogging side and it will be difficult-to-impossible for them to push that content into Lemmy/kbin threads from their interface that was never made to interact with the threadiverse.
Is there any chance Meta has good intentions? No. But it might have intentions that are both self-serving and fediverse-neutral. The absolute best intention I can possibly ascribe to Meta is that joining the fediverse is a CYA (cover your ass) mechanism to head off regulations, especially in the EU, [e.g.] the newly-applicable Digital Markets Act …
Defederation is about what an instance allows in, not what an instance allows out. Defederation stops you seeing the defederated instance’s content, but it does not stop them seeing your instance’s content.
Threads poses some danger to the fediverse, in particular the portion of it centered around microblogging (mostly Mastodon, but also Pleroma, parts of /kbin, etc.), but very little risk to the threadiverse.
The worst thing about the fediverse is all the fondue, but you don’t have to eat it.
Emphasis from the original post.
This is a detailed summary, thank you for linking.
I have also read some other POVs here; my fears are not totally allayed and I still think Meta is only engaing with Activity Pub to prevent new, potential competitors arising from it.
I hope the OP is right about it being very little risk to the Threadiverse. The good news is that Threads is focused enitrely on microblogging and not the Threadiverse. Perhaps that means Kbin and Lemmy users will be able to sit on the sidelines and see how it plays out for a bit, idk. Mastodon users will be seeing the most change.
Either way, I remain a skeptic.
To put my own skin in the game, I quite like the microblogging side of kbin. I like that I can swap between the thread and blog sides, I like that I can combine them into one view if I choose, and I like that I don’t need a separate account to use either service. Using kbin’s microblog was the first time I ever blogged, period. I’d hate to see that stream be overwhelmed by Threads users.
Exactly one of the reasons why I remain a skeptic.
I don’t want sound too much like I’m complaining about “Eternal September” but I quite like how kbin’s microblog is right now. Having millions of threads users suddenly flood it with random… crap… would change it forever.
I haven’t used instagram in more than half a decade. When I hopped on to see what it was like recently, I hardly recognized it and all the content was completely irrelevant. I would hate to see that happen to the microblog.
The issue is that this does affect Kbin because Kbin is a microblogging platform. It’s also a thread aggregator, but it has microblog functionality that some people do actually use. Should we not defederate, stuff from Threads will flood the microblogs of Kbin. If your home page is set to use the All Content feed (like mine is), you’ll see microblogs from Threads there. This doesn’t have as much of an effect as it does on a purely microblogging-focused platform like Mastodon, but it does still affect a big way that Kbin is used.
Right, and that’s part of why I remain a skeptic. Kbin’s microblog being overtaken by Thread’s content could very well limit kbin’s growth and viability as a microblogging platform - especially if Meta pulls the plug later.
But, I have also seen the opinion that not having Threads content could make kbin unappealing as a microblogging platform. (I’m not sure if I agree with this, but I have seen it mentioned.)
I guess the questions are, Can Kbin grow with Threads content? And, Will the lack of Threads content make it unappealing to new users?
Also, another problem I think is that kbin might not have the userbase and content yet to be self-sustaining when faced with a goliath company like Meta; if we produced as much content as Threads will (or enough to the point that defederating kbin would hurt Threads) then there wouldn’t be much of a concern.
Idk, Threads is ultimately the one forcing the situation (probably intentionally) where federating with them is risky but also refusing to do so could be self-isolating. I still maintain that they’re doing it now while the fediverse is still young for a reason, and that is so they can grab so much of the “fondue” that everyone comes to them anyway.
I would like to see kbin succeed, and I don’t trust Meta. Whatever kbin decides to do I will be here for it, but I’m definitely a Meta skeptic.
I’ll just leave this here
I don’t want to see or serve a single Meta ad ever. What I love most about KBin is the lack of ads.
I would like to make a few counterpoints to yours from the opposite perspective.
To your first point: Nearly everyone here came from Reddit’s API fiasco. We all already left the place that housed the vast majority of the content and went somewhere much slower and quieter. If Threads were to abandon ActivityPub in the future, we would still have the same users who are here now, and if returning the fediverse to it’s current level of activity is to be considered a death sentence for it, wouldn’t that mean we’re already doomed? Things are stable right now though and we have enough activity to sustain a social network as is, so the loss of Threads content wouldn’t be our downfall unless a majority of our current users decide its too quiet without them. However, I wouldn’t expect the group who left all of Reddit’s content behind to be the type who would also abandon their accounts here just because the Threads users aren’t here again.
As for the second and third points, the beauty of ActivityPub is that it allows users to choose the services they want to use in order to access the same content across the fediverse, and it wouldn’t be right for us to try to dictate how others choose to access an open protocol. If someone who is interested in joining the network decides to do so through Threads, that should be their choice to make, even though I personally think its the wrong one. In all likelihood though, someone making an account on Threads wouldn’t have consciously joined the wider fediverse of their own volition anyway. Once they’re on though and have a chance to maybe learn a little about these “third party services” they see, they’ll make their way to these places instead. Exposure to the fediverse is the best way to understand it from my experience. There have also been a whole host of people who already signed up for Mastodon accounts without understanding a thing about what a federated network entails, they just wanted out of Twitter.
I don’t think its right to view ActivityPub as competition to mainstream social media networks, it’s a tool meant to help build a better unified social media network. If we limit who can use the tool, we’ll only be hindering the growth of the fediverse.
Thanks for the alternate perspective! However, it doesn’t really alleviate my concerns much:
Firstly, the claim “Nearly everyone here came from Reddit’s API fiasco.” isn’t necessarily true, as the fediverse consists of more than Lemmy and the threads section on Kbin. Threads primarily concerns microblogging, which includes platforms like Mastodon, Misskey, Firefish, Friendica, and Kbin. Even so, you could say that all of these people came from similar situations — they all could’ve chose Twitter or what have you and instead chose the smaller platforms on the fediverse. But does that really mean that they’ll stay here? This whole situation is showing that people are desperate for activity, even if that activity means relying on a corporation with interests that go against ours. People have already left following drops in activity — during Ernest’s hiatus, the number of active Kbin users plummeted (yes, it was always going to down after the initial rise from the Reddit migration, but Kbin went down a lot, especially compared to Lemmy) and hasn’t recovered. Those people, who have tried it and said, “Yeah, this isn’t really working,” are really hard to get back.
Now, imagine if everyone here got used to the large amount of microblog content provided by Threads, interacted with it a bunch, followed a bunch of Threads accounts, etc. like people are expressing plans to do. If Threads quits federating, thereby making all of that content and connection inaccessible to the rest of the fediverse, do you think people will stick around after that much of an activity drop? No, tons of people are going to follow the 99% of activity and flock to Threads, leaving the open fediverse in a position worse than right now. If you want to give Meta the chance to kill the fediverse’s chance of growing to become a legitimate competitor, this is how you do it.
What you say about people having choice is true. If people want to access the fediverse through Threads, that is absolutely their choice. However, another beauty of ActivityPub is that we have the choice over whether we accept interaction with Threads or not. We don’t have to become dependent on Meta to carry the fediverse — we can shut them out immediately and grow slowly but surely. If someone wants to join Threads, we aren’t under any obligation to show them our content. Instead, saying, “Hey, if you want interaction with us, head over to something that cares about an open fediverse like a Mastodon or Kbin instance,” is going to be much better for us long-term.
I don’t think its right to view ActivityPub as competition to mainstream social media networks,
No matter how we view it, Meta views ActivityPub as competition to Threads and rightfully so. The values we currently hold on the fediverse — transparency from moderators & developers, no one instance having control, people having lots of choice, etc. — are values that directly go against Meta’s profit whether they join ActivityPub or not. It is in Meta’s best interest to pull as many users from here as possible and to nip the fediverse in the bud before it grows. Zuckerberg is not here to play nice, and I can’t fathom how anyone would believe so. He does not care about a decentralized, open fediverse. He wants to get as many people on his platform as possible and to make potential competitors less viable, and this is how he can do it.
I came to the Threadiverse because Reddit was closing its APIs and building the walls higher around its garden.
I will be supremely disappointed if the Threadiverse collectively turns around and does the same thing.
Instances should be defederated when they do something harmful. Preemptively defederating is counterproductive, it gives Meta no incentive to do things right.
Yep, the Reddit metaphor really backfired. If Reddit joined the fediverse I would happily consume their content. It would actually be a wonderful compromise where reddit wouldn’t have to provide direct app support and instead just publish out via ActivityPub and people could build third party clients through that.
I left Twitter because they killed Tweetbot and I left Reddit because they killed Apollo. I genuinely hate the experience of those sites with their native apps, and I use these kinds of services almost exclusively on my phone.
While I also hate Elon Musk and Spez, I strongly dislike most tech CEOs so while a motivator, it wasn’t the biggest factor for me. It’s important to remember we’re not all here for the same reason, and user-level instance blocking is the real solution here.
You don’t like some fediverse member? Then block them at the user level and move on, or start your own server and block them there. Don’t force everyone else on your server to not even have the option just for you.
I came to the Threadiverse because Reddit was closing its APIs and building the walls higher around its garden. I will be supremely disappointed if the Threadiverse collectively turns around and does the same thing.
So instances on the fediverse have some obligation to let entities who (A) will control 99% of the content, against our values of a decentralized, more evenly distributed fediverse; (B) have zero interest in an open fediverse; and © have all the incentive in the world to prevent its growth and get more people on their own platform to ensure profit? As usually hesitant as I am about preemptive defederation, if the fediverse is to preserve its values of openness and ensure its growth, it can’t let in for-profit corporations that will control most of the activity and that go directly against those values of openness we care about so much. Just as tolerance doesn’t mean letting in those who are intolerant, an unwalled fediverse can and should put its guards up against those who want to take everything for themselves.
it gives Meta no incentive to do things right
Meta already has zero incentive to do things right. In fact, they have negative incentive, as people being on Mastodon or Kbin instead of Threads actively harms them. You will never see Mark Zuckerberg suggest that people spread out to other instances so that no one gains too much control, but you will see him try to get as many people from the other instances on Threads as possible. We are talking about making our activity dependent on a for-profit tech corporation. If we were way larger so that Threads wouldn’t control such a massive portion of activity, I wouldn’t be as concerned, but as things stand now, we’re letting our content pool be dominated by a company that has interests in direct opposition with ours. I can’t see a scenario where any of this ends well.
what makes this time special that facebook wont cause problem
facebook already habe no incentive to do things right
Nothing makes it special. My point is not that I think Facebook will do no wrong, my point is that it’s counterproductive to defederate from them before they’ve done something wrong.
is it because removes incentive
if facebook had incentive in first place they wouldn’t be genocide enabler
Uh… huh. Okay, I’m going to count that as a Godwin and leave it at that.
._.
All I’ll say is that it’s not much of a “fediverse” if you just preemptively defederate from anyone trying to grow it because you’re scared of what might change. More of a “fediclub” at that point.
Really kills the “it’s like email!” metaphor when you defederaters are constantly trying to break that interoperability by stirring up FUD and blocking instances for theoretical stuff they haven’t even done yet.
It’s like email except your server admin might decide one day they don’t want you to talk to anyone who has an @gmail.com address because they don’t like Google. What fun!
@ThatOneKirbyMain2568 I made a post that actually covers some of the popular user conserns regarding Threads federating
I see what you’re saying, but I really don’t see what Meta stands to gain in the long run from an open fediverse. It just doesn’t seem compatible with their business model to allow users who aren’t on their platform to interact with content created on their platform. They need data so they can sell it to advertisers, and I don’t see how that works when your users can just jump to another instance with no advertisments and access all the same content.
What do you think Meta stands to gain from Activity Pub, and why wouldn’t they just make their own closed protocol? (I am asking in good faith, because I do not really know.)
As I understand it, they’re joining precisely because they’d gain little. By flooding it with their content, any new user would think Fediverse=Threads.
I’ve seen the acronym EEE (Embrace, Expand, Extinguish) thrown a lot in these discussions because it’s a 3-word summary of their presumed strategy.
I feel the post doesn’t really address my concerns.
Really? You think Threads will take over and rule Mastodon? Threads is its own platform, users on the fediverse can still join Mastodon #servers of their choice and leave. I expect we’l see plenty of anti #threads Mastodon servers pop up. If Threads were to somehow get an influence in Mastodon, just switch to #lemmy switch to #pixelfed switch to #firefish So many choices.
This seems to not really understand the risk Threads poses. Threads is its own platform, yes, but it will dominate the visible content of any instance that federates with it. It’s very dangerous to depend on a massive, profit-driven corporation for activity on the fediverse, as the things we value on the fediverse (decentralization, transparency, even distribution of content between instances, etc.) go against the corporation’s motives. Meta does not stand to benefit from any of the things we value, and most of the Threads userbase (i.e. casual Instagram users) probably won’t notice or care about federation. Meta does benefit if everyone depends on them for content, as then they can pull people to Threads just by defederating. People will choose to go to Threads where the amount of activity is what they’re used to over staying on their Mastodon instance after activity has plummeted and they can’t see most of the people they follow.
This is a big one. Meta might capture the mainstrean fediverse. Lets just be real the average regular internet user wasn’t going to join Mastodon in the first place. Not that they wouldn’t want to it just isn’t on their list next to #facebook #instagram #tiktok #youtube #discord or even #twitter . Actually I take what Meta is doing as a compliment to the fediverse. Remember Twitter at one time under #elon #elonmusk banned the talk of Mastodon or something like that. Threads might not have our interests at heart but they are already mainstream so why should they not allow their users be federated with us?
Yes, there are definitely a lot of people that the fediverse is just never going to appeal to. But of those who are interested in the fediverse, more will be inclined to join Threads due to it having most of the content & just requiring an Instagram login. There is a pool of people out there who will try out the fediverse if they’re introduced to it — that’s how we all got here — and if people can interact with the big Mastodon, Kbin, etc. instances from Threads, many will choose to do that when they wouldn’t have otherwise.
@ThatOneKirbyMain2568 @rob299 Yes. But also Meta’s screwed-up moderation systems will be brought to bear against fedi instances. The latter will essentially have to endure a shitty AI-generated smear campaign.
“If #Threads were to somehow get an influence in #Mastodon, just switch to #lemmy switch to #pixelfed switch to #firefish So many choices”
This exposes how little (if anything) the writer understands about any of those #Fediverse distributions
Mastodon is not interchangeable with Lemmy
Mastodon is not interchangeable with Pixelfed
Mastodon is not interchangeable with Firefish
Period
cc @rob299
@FinchHaven @ThatOneKirbyMain2568 what I meant by that section you quoted from the post was, if Meta were to influence the development of Mastodon. If you switch to Firefish or others mentioned, you would probably have a more preferred dev team then what could happen to Mastodon with Meta.
I don’t think “the development” is what is claimed to be at stake here.
OP is not talking about the software, they’re talking about the content. And the content model from Mastodon is not interchangeable with the one from Lemmy, Pixelfed, etc. they serve different purposes and have different models. In fact that’s the main interoperatibility barrier between them.
It’s like saying that if most people use gmail for email you will switch from email to audio calls to avoid communicating with google’s service. As if real time audio were the same thing as sending a message (or as if google was unable to add compatibility with that call service too if they wanted).
One thing you could argue is, instead of switching services, switching to an instance that does defederate if you dont want threads content. But that same argument can be said as well towards those wanting threads federation…
But dont think the point is what does the individual want (if that were the case, just use the option to block threads content for your user, without defederating), the point is what’s best for the fediverse. I think people are afraid that something similar to what happened with “google talk” and their embrace of xmpp will repeat.
Personally, I think there’s no reason to jump the gun this early… all of this post is based on a lot of weak assumptions. I dont believe that threads content would overwhelm the feeds, and if that were to happen then the software could be tweaked so the contribution of each instance to the feeds can be weighted and made more customizable, for example.
is mainstream influence good
@sour depends on how you see it.
My question is, what has Threads done to influence Mastodon development so far in a bad way.
lets Say threads is just the mainstream platform of the fediverse. The protocol is all open source, and every one is in control of their servers. If it is federated whats the worse that could happen?
Plus you can always switch to lemmy, firefish, and etc. to try to avoid threads platform wide.
Counterpoint, what has Meta done to gain even the tiniest bit of the semblance of the doubt. If someone’s punched you in the face every time you’ve knocked on their door, are you really going to knock on it a 15th time? You’d be a fool to expect that time to be any different.
Just like you’d be a fool to expect the overall impact of Meta having their fingers in the Fediverse to be anything other than harmful.
Kbin defederating from Threads would be an own goal of hilarious proportions. The only entity that would be harmed is Kbin.
I wouldn’t say kbin would be harmed necessarily even if maybe just a tiny bit. A good amount of the users on Lemmy (can’t say much about kbin hadn’t tried it yet) *hate* threads. So as an alternative to Mastodon, that would actually more likely score them points not detract from a user perspective.
Most likely, for a user to be on kbin or Lemmy you either come from Reddit, or you come from Mastodon so the users would had likely made up their mind on separating themselfs from major platforms, that likely includes threads.
parent company have bad track record
is all evidence you need
fediverse doesn’t get in mainstream because is decentralized
deleted by creator
I have already done my part on my Mastodon account.
My main concern is the awful moderation of Meta’s services. Bullying, celebration of loss of rights and violence committed towards of protected minorities; and outright misinformation are allowed. All while the very same people duped the moderation AI to flag any criticism of said hate speech as the real hate speech because false reportings. Facebook, instagram, etc. are notorious for letting big far-right accounts get away with hate speech and defamation, and I don’t really think it’ll be different on Threads for very long.
EDIT: In the meanwhile, I remembered screenshots of showing this exact moderation problem already happening on Threads, but to a way lesser degree, than on Facebook so far. Maybe this will make them getting booted from even the instances that didn’t originally plan to defederate them.
fediverse is considered safe place for minorities
On the Lemmy and Kbin Magazine side of things, Threads won’t be a huge threat as most discussion will stay on existing communities/magazines, and most of the same users will be there with some interaction from Threads users.
On the Mastodon and the microblog side of things Threads will be interesting and I think the healthiest option is some server disconnect from Threads and others don’t. What you don’t want is ALL the discussion happening on threads and within threads, Threads should be set up as a gateway to the rest of the Fediverse despite the size difference.
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.
If Threads federates… it’s part of the fediverse.
Even if you don’t accept that tautology, sure, maybe the fediverse (not including Threads, which is also fediverse at that point, but ok whatever) doesn’t do great, but kbin will definitely suffer if it defederates from Threads, once Threads
becomes part of the fediversefederatesdoes whatever you think it’ll be doing that’s not exactly the same thing as joining the fediverse and therefore becoming part of the thing that you think will become non-viable after the most viable piece of it joins. Kbin will become an also-ran within the fediverse, because most users will want to use tools that allow them to interact with the most people.I guess what I’m saying is you can’t in one breath say that “Threads will join the fediverse” and then in the next breath say “the fediverse will become non-viable” as if Threads isn’t part of the fediverse in the second breath. Let’s not do “separate but equal” with social media, please. It’s silly.
If Kbin defederates from Threads, it’ll be Kbin that suffers.
Kbin will become an also-ran within the fediverse, because most users will want to use tools that allow them to interact with the most people.
I’m not sure this holds. Surely if it was the primary factor in deciding which social media everyone chose, Kbin would already be dead at the hands of Twitter? Federation doesn’t really change that argument if it’s only about interacting with the most people.
That said I do agree that we need enough instances to defederate from Threads for this to work. If Threads overwhelms every other instance with volume and kills them, Kbin is alone and not really better off for having defederated. But as a pretty big instance, Kbin doing this is a major part of ensuring that the fediverse does not just become a collection of quirky alternative interfaces for Threads.
as if Threads isn’t part of the fediverse in the second breath.
If Threads puts out so much more content as to effectively make other federated entities irrelevant, the character of the Fediverse changes such that it is no longer what it is today. Federation is meaningless if 99.9% of content comes from one place. Kbin would wind up as effectively just a weird third party interface for threads in that situation.
Let’s not do “separate but equal” with social media, please. It’s silly.
Is it meaningfully different to any other instance of defederation? Many of which I would say are generally beneficial to Kbin.
If Threads puts out so much more content as to effectively make other federated entities irrelevant, the character of the Fediverse changes such that it is no longer what it is today.
A fun time to bring up the concept of Eternal September.
This may be an issue of poor wording on my part. The idea I’m trying to get across is that if Kbin, Mastodon, & other microblog platforms that are currently on the fediverse don’t defederate from Threads, the users on those platforms will become dependent on Meta for activity. If Meta then leaves the fediverse, activity will drop down to what we have now, only with people used to the activity brought by Threads and having all of the connections they made with Threads accounts. This will pull tons of people from Kbin, Mastodon, etc. and essentially kill the open fediverse with very little hope of it growing again.
And to be clear, Meta has tons of incentive to do this. Meta is a profit-driven company. They want as many people as possible on their platforms, not on Mastodon or on Kbin or on Firefish or on Misskey. The open, widely distributed fediverse that we strive for goes against Meta’s motives. Just as they’d have everyone on the Metaverse if he could, Zuckerberg will absolutely pull people from Kbin onto Threads if he gets the chance, and he will get that chance if we decide to put the content pool in the hands of Meta for the sake of trying to get activity as quickly as possible.
Defederate.
