There’s been a lot of speculation around what Threads will be and what it means for Mastodon. We’ve put together some of the most common questions and our responses based on what was launched today.
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.
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.
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.
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.
Could you explain more about IBM? I’m not as tech literate and I’ve been barely keeping up with the conversations about federation and EEE, what’s going on with IBM?
IBM bought RedHat, and recently decided to take ther code repos for RedHat Enterprise Linux semiprivate. They still have to offer the source code to people they give the compiled product to, but they don’t have to give it publically, even though it is open source. Their claim is that they didn’t like others profiting off their work by rebuilding the source an selling it. Of course RedHat seems to now be ignoring the rather large amount of open source code they didn’t write that they are selling, like the Linux kernel.
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.
@[email protected] 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.
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.
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.
Could you explain more about IBM? I’m not as tech literate and I’ve been barely keeping up with the conversations about federation and EEE, what’s going on with IBM?
IBM bought RedHat, and recently decided to take ther code repos for RedHat Enterprise Linux semiprivate. They still have to offer the source code to people they give the compiled product to, but they don’t have to give it publically, even though it is open source. Their claim is that they didn’t like others profiting off their work by rebuilding the source an selling it. Of course RedHat seems to now be ignoring the rather large amount of open source code they didn’t write that they are selling, like the Linux kernel.