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].
It’s always the XMPP response… but is there any data out there that XMPP before Google/Facebook was better off than after it?
Because from my point of view XMPP stagnated, got adopted by Google and Facebook which technologically was a huge rise of course, but in practice changed very little for 99.99% of people, and the inverse happened when Google and Facebook left, which was irrelevant for 99.99% of people and XMPP continued to stagnate.
I’d really love some comparison from popular XMPP server Traffic (or monthly active users) before, during and after the Google/Facebook era.
That’s my take on the whole thing. Google adopted a small OSS framework, used it with some of their apps and then as google does they killed their apps. They never did anything to the framework.
It feels like people on this site have this notion that without Google stepping in XMPP would have huge, widespread adoption. The reality is that the average person isn’t interested in federation or anything else remotely technical. They want an easy to use client that abstracts as much as possible, and those tend to be centralized and corporate.