It is expected to be 2-3 months before Threads is ready to federate (see link). There will, inevitably, be five different reactions from instances:
-
Federate regardless (mostly the toxic instances everyone else blocks)
-
Federate with extreme caution and good preparation (some instances with the resources and remit from their users)
-
Defederate (wait and see)
-
Defederate with the intention of staying defederated
-
Defederate with all Threads-federated instances too
It’s all good. Instances should do what works best for them and people should make their home with the instances that have the moderation policies they want.
In the interests of instances which choose options 2 or 3, perhaps we could start to build a pre-emptive block list for known bad actors on Threads?
I’m not on it but I think a fair few people are? And there are various commentaries which name some of the obvious offenders.
Would be funny, if major instances are choosing option 5, making many communities divided and useless, right before Meta announces, that they don’t plan on federating with Lemmy instances. And that Threads will only federate with Tumblr lol
Seriously tho, how will Threads impact Lemmy anyways? They don’t have communities there, right? Their posts will probably not show up here regardless of federated or defederated, if I understand correctly.
You can follow Lemmy communities from Mastodon.
But have you actually tried it? Here’s a sample. Go take a look. (EDIT: My link is worthless unless you are logged in to mas.to. Go look up username fediverse@lemmy.world in your Mastodon client of choice)
It’s a completely unmanageable firehose of comments, spewed only in chronological order.
Honestly, the link between incompatible types of social media like Lemmy and Mastodon could be severed in my opinion, because it’s mostly just novel with little benefit.
If you’re not on mas.to that link will just collapse back to a lemmy.world view.
You’re totally right. Edited.
It looks like you snipped some of your original comment in the process. It just ends mid sentence now.
We need to think this through from the standpoint of an instance admin who is trying to figure out how to use Threads to make their instance grow. That’s really the only motivation I can think of to federate with Threads. Otherwise it’s just all downside. As a corporate social media entity, they are entirely opposed to everything Lemmy stands for philosophically, and their scale is a massive threat to the culture and operations of the much smaller fediverse. Why would anyone ever want to federate with them? Because they see it as an opportunity. To ride the dragon, thinking it can be controlled. This is madness. Choice 4 all the way and if it becomes necessary, 5.
The beauty of the Fediverse is you do not need to make everyone else agree with you. It is important that mods know what you want; what you think other people should want is irrelevant.
No, you don’t need to go around making other people agree with you, on the fediverse or anywhere, really.
But if you are going to enter into a mutual risk/benefit relationship with another party, it does help to understand what their motivations are, so you can figure out if they’re going to line up with your own, or lead to conflict.
My post is about trying to understand those parties’ motivations. Not make everyone agree with me.
4 is honestly my preference. I don’t see the need to defederate from instances that federate with Threads. But I do want to see a list of instances that federate with Threads so I can personally never comment or post there. I don’t like the idea of comments and posts I make being used to generate ad revenue for Facebook.
100%. It boggles my mind that we’re even considering this.
deleted by creator
Everyone is talking about defederating preemptively because of XMPP and EEE. But the very fact that we know about EEE means that it’s much less likely to succeed.
Zuck is seeing the metaverse crash and burn and he knows he needs to create the next hot new thing before even the boomers left on facebook get bored with it. Twitter crashing and burning is a perfect business opportunity, but he can’t just copy Twitter - it has to be “Twitter, but better”. So, doing what any exec does, he looks for buzzwords and trends to make his new product more exciting. Hence the fediverse.
From Meta’s standpoint, they don’t need the Fediverse. Meta operates at a vastly different scale. Mastodon took 7 years to reach ~10M users - Threads did that in a day or two. My guess is that Zuck is riding on the Fediverse buzzword. I’m sure whatever integration he builds in future will be limited.
TL;DR below:
So why is it important to not federate (or block) with Thread? Asking seriously. I read the article and while those are valid and real concerns. What is the net gain of that action? How does it help the fediverse? I cant see any way that it helps and lots of ways it hurts. At this point it seems like a lot of what ifs.
Edit:
If you need the reasons why to block Threads (meta) I think the answers below explain it better than most!
Choice 2. 5 is ridiculous and more harmful to the fediverse than the worst case of EEE.
- Make your own instance, defederate from everyone, make 20 accounts, disable account registration, post from 2 or 3 accounts, upvote from the rest and make conversations.
/j on the 5… cuz it’s a bit extreme.
I hate to say it but we already need a better Twitter and Reddit alternative than what the fediverse has to offer, then. Each time a big company comes in, the communities will get thrown into disarray, eat eachother, and generally make the original ‘vision’ of the fediverse smaller and smaller. People will use what is easy, not what is best for their interests (at least for the vast majority). The solution is still open source, community managed and driven content, but it doesn’t look like the fediverse is a long-term answer.
5, except fully neutral-ground instances (private ones used as personal access points or government instances for example)
