The fediverse is discussing if we should defederate from Meta’s new Threads app. Here’s why I probably won’t (for now).
(Federation between plume and my lemmy instance doesn’t work correctly at the moment, otherwise I would have made this a proper crosspost)
How does that even make sense? They’re completely different types of content.
If Threads is just another Mastodon instance why does anyone care?
If everything is just decentralised instances what are kbin and Lemmy, exactly? They’re not instances in themselves, are they?
@koberulz @murphys_lawyer
Threads isn’t just another Mastodon instance. Threads uses a similar format to Mastodon, and they may communicate with each other, but the similarities stop there. Threads will probably have some proprietary features to make it “stand out” from the others. Also, if many people jump on board Threads, the thing is that Meta will then have a monopoly on the Fediverse, which is the exact thing the Fediverse is trying to extinguish: Monopolies controlled by corporations.
The “monopoly on the Fediverse” argument is something that I explicitly wanted to counter in my post. The fact is, Threads will become one of the largest if not the largest instance in the Fediverse, if we federate with them or not. Their users don’t sign up to Threads to talk to us, they sign up because it’s the hot new thing from Meta. If we defederate right away, they become their own bubble, their users never know we’re there and they can do to their platform whatever they want.
But if we federate with them as long as they play (relatively) nice, their users will get used to being able to talk to us which gives us leverage. They will be bound to use the same protocol as us or their users will complain about not being able to talk some of their friends anymore and maybe even migrate to an open alternative. And if they still want to go through with a change we don’t like, we can still refuse to implement it.
Our choice is not between Meta having a monopoly on the Fediverse and everything being as we want it. It’s between them having an alternative to the fediverse that will overtake us within weeks and having a slim chance at being treated as equals.
While I agree that it is probably better to not defederate them right from the start, I believe that the Fediverse might not have that much leverage. This recent blog post about the history of XMPP describes it pretty well: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Of course it’s different because this is social media and not just 1:1 privat messages. But for us to actually have some leverage/impact we have to generate a lot of (good) content so that Threads users will actually notice and complain if that content “vanishes”. And at the same time we must not become too dependent on their content
This is more of a warning against monopolies than access. Businesses applying resources to the Fediverse can only help it grow as long as it does not completely take over. Competition, whether it be individuals, businesses, or government, can help keep it healthy and guard against anticompetitive behaviors.
As I said elsewhere: this would still have been the case if Google hadn’t used XMPP in the first place. All those people you have lost when Google defederated either wouldn’t have been on XMPP at all or care enough about privacy and open source to have both. It’s not like you have lost anyone who had been there before Google started using XMPP. Same with Threads. Every single user who is on the fediverse today will still be here if they defederate (unless they leave for other, unrelated reasons of course). Considering our existing userbase’s interests, I don’t see many people giving up their existing accounts in favor of a Threads account.
Mostly answered in my other comment but for visibility and completeness, I’ll try to answer it here again.
The content may look different on the surface but that’s mostly because the different applications present them differently. Under the hood, it’s almost identical. Users create posts, other users can reply or like. What differs is the details. Mastodon posts are by default limited to 500 characters, Lemmy/kbin posts can be a few thousand, Plume posts can be even longer. Mastodon and Plume only have likes, Lemmy and kbin add dislikes (downvotes). Posts and comments that come from a different application may look a bit weird in whatever you use but at least they show up in your feed and you have the option to click a link to see them in their original form. In facht, @[email protected]’s reply to your comment came from a Mastodon instance and they will see my reply in their Mastodon feed.
As for the difference between kbin and Lemmy, they’re two different pieces of software that interact with the Fediverse in a very similar way. When someone wants to setup a Reddit-like fediverse instance, they can freely choose between them based on personal preference (I chose Lemmy for my instance because kbin is harder to install and update). Imagine them like being able to choose between a phone by Apple, Samsung, Huawei or Nokia. All those phones have their own specific pros and cons but because they communicate through the same protocols, they can still talk to each other. An instance would be analogous to your Samsung phone or my Apple phone or my partner’s Nokia phone. There are many fediverse instances that use Lemmy as their software same as there are many Samsung phones in the world. The fact that most of them have very unimaginative names (looking at you, https://lemmy.ml/ and https://lemmy.world/) doesn’t help but as positive examples like https://beehaw.org and https://feddit.de. Both use Lemmy and can talk to any other Lemmy instance but their names make it clear that they are their own thing.