There has been significant discussion in recent weeks regarding Meta/Threads. We would like to express our disappointment with the negative and threatening tone of some of these discussions. We kindly ask everyone to engage in civil discourse and remember that not everyone will share the same opinions, which is perfectly acceptable.
When considering whether or not to defederate from Threads, we’re looking for a decision based on facts that prioritize your safety. We strive to remain neutral to make an informed choice.
First, there seem to be some misconceptions about how the Fediverse operates based on several posts. We’ve compiled some resource links to help explain the details and address any misunderstandings.
Fed Tips , Fediverse , ActivityPub
Initial Thoughts:
It seems unlikely that Meta will federate with Lemmy. When/if Meta adopts ActivityPub, it will likely affect Mastodon only rather than Lemmy, given Meta’s focus on being a Twitter alternative at the moment.
Please note that we have a few months before Threads will even federate with Mastodon, so we have some time to make the right decision.
Factors to Consider:
Factors to consider if Meta federates with Lemmy:
Privacy - While it’s true that Meta’s privacy settings for the app are excessive, it’s important to note that these settings only apply to users of the official Threads app and do not impact Lemmy users. It’s worth mentioning that Lemmy does not collect any personal data, and Meta has no means of accessing such data from this platform. In addition, when it comes to scraping data from your post/comments, Meta doesn’t need ActivityPub to do that. Anyone can read your profile and public posts as it is today.
Moderation - If a server hosts a substantial amount of harmful content without performing efficient and comprehensive moderation, it will create an excessive workload for our moderators. Currently, Meta is utilizing its existing Instagram moderation tools. Considering there were 95 million posts on the first day, this becomes worrisome, as it could potentially overwhelm us and serve as a sufficient reason for defederation.
Ads - It’s possible if Meta presents them as posts.
Promoting Posts - It’s possible with millions of users upvoting a post for it to trend.
Embrace, extend, and extinguish (EEE) - We don’t think they can. If anyone can explain how they technically would, please let us know. Even if Meta forks Lemmy and gets rid of the original software, Lemmy will survive.
Instance Blocking - Unlike Mastodon, Lemmy does not provide a feature for individual users to block an instance (yet). This creates a dilemma where we must either defederate, disappointing those who desire interaction with Threads, or choose not to defederate, which will let down those who prefer no interaction with Threads.
Blocking Outgoing Federation - There is currently no tool available to block outgoing federation from lemmy.world to other instances. We can only block incoming federation. This means that if we choose to defederate with our current capabilities, Threads will still receive copies of lemmy.world posts. However, only users on Threads will be able to interact with them, while we would not be able to see their interactions. This situation is similar to the one with Beehaw at the moment. Consequently, it leads to significant fragmentation of content, which has real and serious implications.
Conclusion:
From the points discussed above, the possible lack of moderation alone justifies considering defederation from Threads. However, it remains to be seen how Meta will handle moderation on such a large scale. Additionally, the inability of individuals to block an instance means we have to do what is best for the community.
If you have any added points or remarks on the above, please send them to @[email protected].
Good points, I’ll mainly respond to your last line. Isn’t that the whole point of the fediverse? Does it make sense for platforms to keep to themselves instead? Mastodon only to mastodon, Lemmy to Lemmy, kbin to kbin? You could probably make exceptions for some platforms since kbin has parts of mastodon and Lemmy in it, so maybe it can talk to both, but I mean that would solve a lot of these questions, only allow federation to similar software. I feel like it defeats the point of the fediverse and would hurt other things like pixelfeed or peertube as I only really see those posts on my mastodon feed, but to be fair, it is pretty confusing trying to figure out what posts from what platforms will show, like when I see a peertube post on mastodon, I assume it’s like a tweet linking to the video, not the ACTUAL video.
I think the cat is out of the bag already with doing it that way, with the fediverse existing as different open source apps commonly used together but separately rather than an interconnected mess of posts we’re kinda working our way towards. But it would be an interesting and, dare I say, almost better way to handle this, as thread is its own type of server, if it was made Public, it WOULDN’T be Mastodon, so why would anyone assume thread posts should show up together.
Basically I agree with your last line, that leaving them seperate may be better, even if it’s alittle counter to what the fediverse is
I do see what you are saying and I think this point is really the only one that has any validity to it, because the idea of this thing is that it should be as open as possible. I would of course say Lemmy, Kbin, Mastodon, they should federate with one another despite being technically different sites.
But the issue doesn’t lay with Threads itself. Take Meta out of the equation and i’m up to federate with it. I think it might really change things with there suddenly have 10’s of millions of users suddenly here, but I couldn’t assume it would be for the worse.
The issue lies with the ruthlessness of the company itself, and its history of awful behavior. As soon as it becomes more profitable to screw over Lemmy (this will happen, you are always going to be more profitable if everyone is using your platform, plain and simple), they will. In my eyes it is not a matter of if, but when. Everyone at Meta involved with threads could have good intentions for it, I can’t say they don’t, but staff changes, and a company’s attitude towards projects shifts.
Meta has the resources to create whatever they want. They could develop something much more feature-rich than anyone could ever want, without ever involving or needing the Fediverse at all. They would own the entire thing, and would not need to deal with outside forces at all. So we have to ask ourselves, what do they look to gain from federating with us?