I look forward to reading everyone's calm and measured reactions
My primary concern is that they appear to be allowing Thread content to be pulled into other Fedi clients, but not the inverse. So Threads content on Mastodon, but no Mastodon content on Threads. That’s not super great for Mastodon exposure.
Also, given the vast differences in daily active users, wouldn’t Mastodon become flooded, and eventually dependent, on Threads content?
You know what, I was very confused why they would add Fedi integration but unidirectional integration makes a ton of sense from a corporate scumbag POV.
Just defederate them and move on.
Jfc sounds like they're just paving over the community with a giant ad of themselves
Also, given the vast differences in daily active users, wouldn’t Mastodon become flooded, and eventually dependent, on Threads content?
Servers only pull subscribed user content, so it's not like the option is nothing or The Firehose. Meta can't push content into the Fediverse.
I think it's important to note that Meta doesn't have more power than anyone else here. They're just a large instance. They have the same forces keeping them honest as anyone else and their size doesn't change the incentives for mods and admins. Mods don't have an interest in working for Meta for free. If they're spending too much of their time moderating that content, Threads will be limited or defederated.
Given Meta's size and history it's understandable to be concerned. At the end of the day though, they'll either play nice or get bounced. I think we'll be fine either way.
People on Mastodon are preemptively blocking federation. What can I say 🤷
Just a nice high five for them not falling for corporate embrace and extinguish bullshit when it is in the embrace phase!
Me too! Just keep calm and scroll!
I honestly forgot Threads even existed.
I'm constantly reminded of it by instagram when they insert the most unhinged incendiary thread posts on my feed. Quite a way to advertise. "Hey, do you like to be angry and argue with strangers? Come join Threads!"
“Hey, do you like to be angry and argue with strangers? Come join Threads!”
Didn't most of the fediverse preemptively de-federate them already?
Mastodon.social, the biggest instance ran by Mastodon devs didn't and encourages wait and see approach.
I'm on that server and that's how I feel too.
If it goes poorly, then it can be blocked, but to not try seems silly to me.
Is there a list of instance somewhere that we can pick from? I thought someone was putting together a list.
https://fedipact.veganism.social/ lists instances with their decision.
Hi everyone, I am collecting preemptive pikachu faces for when meta inevitably attempts to screw the fediverse over. Please put them in replies to this comment so we don't clutter up the rest of the comments.
N.B.: The delays in the timeline were copied over verbatim. Historical conditions have to be taken into account, as the popular adoption of internet began in the late 2000s. So it is likely for the "extinguish" phase of Mastodon to happen much faster. I give it 5 years tops. And by 2030, we will all remember it as we now remember XMPP.
Embrace extend extinguish
Don't federate with corps, it will only end badly
Pretty cool. I keep saying that this is a win for open standards and Meta probably does this to appease EU regulators. It's no surprise that this happens as Threads launches In Europe.
Yep, can't wait to be able to personally defederate from them, I hope that option comes soon.
I see it as an opportunity to tell people on Threads to leave Threads and use an open platform, such as Mastodon, instead. Then eventually Threads will shut down, because everyone moved :D
Won't they have control over their instance though? I'm sure they're going to run it like Reddit and shadow ban the shit out of their users and also not let them see certain stuff.
no
I wouldn't be too worried about Threads joining the fediverse.
They had the perfect opportunity to dethrone X with a superior app but have given users the most barebones piece of shit that doesn't even have support for hashtags or trending topics.
Mastodon has this functionality.
Last time I booted up Threads, my feed was flooded with e-girls posting twerking videos. I don't follow any such accounts on Threads nor Instagram and I don't like it when my social media feels like a softcore porn platform.
I wish they wouldn't. Stay a walled garden.
I know this is an unpopular opinion, but I think this is actually a great thing for Mastodon. The truth is the majority of people are just never going to sign up for a Mastodon server as they stand today. The majority of people want algorithmic feeds run by a central entity. I know the people here don’t want that, but that’s what the majority of people do want. Will I use Threads? No but if this breathes more life into Mastodon and exposes more people to the concept then that is a good thing. Being able to use a client of your choice to interact with people on something like Threads is also a very good thing. The alternative is a completely closed social network like Twitter.
I know, I know “embrace, extend, extinguish”, but literally this is the best that we can hope for unfortunately. The alternative is everyone goes and uses a closed system.
Google the history of xmpp. This is exactly the same.
It's not a good thing.
I don't see the issue. For all those concerned about privacy: you know you are posting in public space? Anyone can scrape the posts however they want. Which is a key aspect of openness btw.
On the other hand, by leaving Threads in would show other companies the concept of a global community instead of multple closed groups. The companies could save on moderation costs Reddit-Style that way, but open.
You need to learn your Internet history. It wasn't so long ago that we had a diverse, interoperable community of instant messaging platforms based on XMPP, an open, federated protocol. Anybody could host their own XMPP server, and communicate with any other XMPP server. Then in 2006, Google added XMPP support to their Talk app and integrated it into the Gmail web interface. But there were problems:
First of all, despites collaborating to develop the XMPP standard, Google was doing its own closed implementation that nobody could review. It turns out they were not always respecting the protocol they were developing. They were not implementing everything. This forced XMPP development to be slowed down, to adapt. Nice new features were not implemented or not used in XMPP clients because they were not compatible with Google Talk (avatars took an awful long time to come to XMPP). Federation was sometimes broken: for hours or days, there would not be communications possible between Google and regular XMPP servers. The XMPP community became watchers and debuggers of Google’s servers, posting irregularities and downtime (I did it several times, which is probably what prompted the job offer).
And because there were far more Google talk users than "true XMPP" users, there was little room for "not caring about Google talk users". Newcomers discovering XMPP and not being Google talk users themselves had very frustrating experience because most of their contact were Google Talk users. They thought they could communicate easily with them but it was basically a degraded version of what they had while using Google talk itself. A typical XMPP roster was mainly composed of Google Talk users with a few geeks.
Only a few years later, Google would discontinue Google Talk, migrated all their users to Hangouts, and decimated the XMPP community in an instant. Most of the Google users never noticed, outside of some invalid contacts in their list.
That's why everyone distrusts Meta. Even with Threads being a relatively unsuccessful platform by commercial social media standards, its active userbase still dwarfs the entire Fediverse combined. There's absolutely nothing stopping Meta from running the exact same playbook:
Add ActivityPub support, but only partially
Add new features to ActivityPub without consulting with the rest of the Fediverse or documenting the extensions, degrading the experience for everyone not using Threads
Entice Fediverse users to migrate to Threads--after all, why use Mastodon or Lemmy when 95%+ of ActivityPub traffic originates from Threads?
Deprecate ActivityPub support after most of the Fediverse is on Threads, leaving it smaller and more fragmented than if Threads had never federated at all, while forcing everyone who migrated from another Fediverse platform to Threads into an impossible choice between abandoning the vast majority of their contacts or subjecting themselves to Meta's policies, tracking, and moderation
Meta cant be trusted. Ever.
I was here when EEE started!
Ok, so what is actually the main argument people have to preventatively defederate with Threads? I perhaps haven't thought about it much, but I don't personally see the problem if my instances would federate with them. I'm mentally comparing this to email. If I ran my own email service, or used someone else's, why would I want to block Gmail, or icloud, or Hotmail/Outlook?
Of course if they don't have effective admin/moderation policies and actions then, yeah they should be blocked or limited. The same holds true with email federation.
The owner of the server I'm on wrote a nice post describing his reasoning https://about.scicomm.xyz/doku.php?id=blog:2023:0625_meta_on_the_fediverse_to_block_or_not_to_block
Thanks, that's actually precisely what I was interested in reading. That admin team totally rocks for motivating their decision with such a comprehensive argument.
That post is outstanding and is a wonderful writeup that highlights the danger of associating with a company as morally bankrupt as Meta.
There is concern that Threads will use embrace, extend, extinguish to depreciate the ActiviyPub protocol. Essentially, they adopt the open standard, expand on it with proprietary additions, then when everyone is using the modified standard they drop support for the open standard and now everyone has to play ball by their rules.
This is a most excellent place for technology news and articles.
