This is a most excellent place for technology news and articles.
XMPP did not exist on its own outside of nerd circles, while ActivityPub enjoys the support and brand recognition of Mastodon.
Jabber was widely used in the early 2000s and not just among "nerds." But Rochko would have only been 7+ years old at the time so how would he know that.
The "brand recognition of Mastodon" part makes me think this has to be a joke... right?
This reads as incredibly condescending, naive and duplicitous, filled with hubris.
For starters, the whole “yeah sure XMPP got EEE’d but who cares, only nerds cared about that, lol” is not only false (e.g. Jabber), but also does nothing to quell concerns.
Here’s an account by someone who was in the XMPP trenches when Google started adopting it.
Notice something? The “omg so cool!”, this is exactly the same as Rochko.
It’s the hubris when you’re a FOSS maintainer who toiled away for years without recognition and now a $700B+ corporation is flattering him by wanting to use/interact with his work.
The blog is a far cry from the anti-corporate tone in the informational video from 2018.
Then there’s the fact that Rochko is extremely tight lipped about the off the record meeting with Meta and consistently refuses to deny having received funds from Meta and refuses to pledge not to accept any funds from Meta.
There’s also the unsatisfactory answer he gave to people who started questioning some dubious sponsors and the fact that he rushed to lock the thread, killing any further discussion.
I genuinely think the dude is just so hyped for the perceived recognition, that he lost the thread.
So much so that he thinks Mastodon is untouchable.
And it’s extremely naive to think that Meta has benevolent motives here or that Mastodon will survive any schemes Meta might have.
What’s more realistic is that Mastodon will die because people will flock to Threads if their social graph has moved over.
Similarly these lofty and naive ideas that people on Threads will make the switch to Mastodon once they get a taste of what it has to offer.
So now all of a sudden the “difficulty” to get started in Mastodon, that is keeping people who want a polished corporate experience away isn’t going to be an issue?
Especially when in the “extinguish” phase Meta will have siloed off from Mastodon and its portability function, having to leave their social graph behind?
It’s all so increasingly naive, one can’t help but wonder if it’s intentional sabotage at this point.
Mark my words, this’ll be the end of Mastodon especially when Meta can outspend Mastodon all day every day to add proprietary functionality.
Sure perhaps years from now a few hundred to a few thousand people might still use it, but it will be as irrelevant as XMPP is to most people, and Rochko with it.
@remindme@mstdn.social in 2 years.
Excellent post, and it is truly heartbreaking stuff. We know Eugen signed an NDA with Meta which just seals the deal for me given the other refusals to answer basic questions. I think he is probably a person who is finding validation for something he's worked on for a very long time, and Meta is blinding him. But that's what they do. They are emotional manipulators by trade.
Mark my words, this’ll be the end of Mastodon especially when Meta can outspend Mastodon all day every day to add proprietary functionality
This is exactly what happened with RCS. Sure, it is an open standard. But Google EEE'd it by adding proprietary functionality using their near unlimited budget and influence, then built it all around their own proprietary middleware, like Jive, to lock out others. Some of the most popular messaging apps, including Signal, had been begging Google for RCS access for years. Google refuses, because they firmly control it now. Only a handful of partners get to access the supposedly "open" standard which Google has co-opted. Sure, you could pour resources into the old, unmaintained RCS standard from over a decade ago. Before Google essentially killed it by moving proprietary and snuffing it out. But then it wouldn't work with Google's RCS, and Google's RCS is what people know as RCS at this point.
Meta will do the same thing with ActivityPub specifically, and decentralized social media in general. They will EEE their way to the finish line. They will wall it all off and prevent account portability and cross-communication outside of a preferred partner network. I could see them walling it off to the Meta-owned properties as they seek ways to further tie Facebook, Instagram, and Whatsapp together under a common protocol which they've EEE'd.
Only a handful of partners get to access the supposedly “open” standard which Google has co-opted.
This is why God invented GPL. With GPL, you don't get to do that.
For example, right now, IBM is in the process of learning very hard lessons why they don't get to do that.
I read your comment before I read the blog post and I have to say, I am finding it hard to align it with what's in the blog.
Aside from the hand-waving comment about XMPP, he does a great job of explaining how everything works, and based on my understanding of the fediverse and its architecture, its all true.
I dont understand what people think should happen here. If a large corporation wants to join, then there is nothing anyone can do to stop them. Its an open protocol. If you want to use Threads, join. If you dont, don't. If you want your server to defederate, tell your admin or join a defederated instance. If you want to federate, tell your admin or join an instance that's federated. If you want to control your own destiny completely, self-host.
There is tons of choice here and the way it's architected, several layers of protection. I dont get this moral panic everyone has. This is quite literally the point of a decentralized social network.
At the end of the day, if a large corporation joining the network, kills it, then it was destined to be destroyed from the beginning.
The sanest comment here.
What we know
Threads is a separate app from Facebook, WhatsApp, and Instagram. This means Threads’ user base will be separate from their existing platforms.
Well that aged like milk…
don't know about you folks but this sounded so arrogant to me:
There was a time when users of Facebook and users of Google Talk were able to chat with each other and with people from self-hosted XMPP servers, before each platform was locked down into the silos we know today. What would stop that from repeating? Well, even if Threads abandoned ActivityPub down the line, where we would end up is exactly where we are now. XMPP did not exist on its own outside of nerd circles, while ActivityPub enjoys the support and brand recognition of Mastodon.
We kept losing, and will keep losing, because billionaire megacorps simply have the money to move worlds if doing so aligns with their ‘interests’ (ie money). This hasn’t changed, and won’t change now either; the Fediverse is done for.
Fuck Facebook for ruining another good thing.
ActivityPub won't ever "truly" die, it might lose the chance of becoming "the salvation from mega corporations running the internet" though. We'll always have the possibility of running small-ish, tight-knit instances.
But agreed, fuck Zuckerberg and his cronies.
Damn you're depressing
There's a long term silver lining though. People keep learning. Constant exposure to manipulation makes us more resistent to it. Consider how much the Internet has trained you to recognize scammers, salesmen, trolls, instigators, demagogues and so on.
Why are people mad at this? Being able to communicate with Threads users from mastodon servers, is good? Right?
I think there is a risk that Threads will be massive, and so people will think that the way to get on Mastodon is Threads, and eventually that Threads is Mastodon. C/f Google Groups and Usenet.
I can see the argument that Meta wants to kill the fediverse but I am kinda excited that we could possibly still get content from feeds that would not consider a mastodon account, even if that is a disagreeable attitude. Looking at Threads it already looks like brands "autosport, financial times" etc have setup regular posting schedules on threads so it really could be the Twitter killer.
