Skip Navigation
277 comments
  • 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.

    • 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 problems I personally have with Meta are:

        1. Data scraping Meta is an ad company and tries to collect as much data from anyone. They are known to make shadow graphs of people not even in their network to try and know as much about as many people possible. This is their business model so they will do it to the fedi.
        2. Moneyed interests They are going to compensate instances that federate with them, which turns people that run instances from volunteers into business owners. From there they can try and dilute admins further into showing ads etc.
        3. Sucking users from the fediverse They will make it easy to get in (import with history when mastodon does not support it), hard to get out (if you go, you can't take your posts) and will hold your connections hostage against you (we will stop fedarating with the other instances now, so if you want to connect to your friends you have to have a threads account, sorry not sorry).

        That and basically all the shit big corps do like make people angry and hacking people's brains to stay on the site for as long as fucking possible. Which they are 100% going to try to do here regardless of our intentions.

      • Aside from the hand-waving comment about XMPP

        “Aside” is doing a lot of the heavy lifting here, it reeks of a nauseating amount of hubris and makes one wonder if they’re suitable to maintain the project at all if they’re so oblivious to potential threats to the project.

        I don’t understand what people think should happen here

        Not roll out the red carpet for starters, and not engage with the company under NDA would be a good second.

        Especially for a FOSS project that receives a healthy amount of contributions from others and likes to tout that it's co-owned by all contributors, it could be argued that it's highly objectionable for one person to engage, essentially as a representative, in non-transparent dealings that are sealed under NDA.

        It really isn't rocket science, here's how the admin of the Fosstodon instance handled it.
        Notice the lack of red carpet, the unwillingness to participate in an "off the record" event and the abundance of transparency towards the people he's responsible for.

        I'm not saying that Rochko should've adopted the same abrasive "lol, get rekt" tone, its up to him if he's comfortable with that, but the points I'm hammering on about above can be achieved in respectful manner as well.

        There is tons of choice here and the way it’s architected, several layers of protection.

        There is no protection. As I've stated in a different comment, t doesn’t take more than 2 seconds of thinking to see how empty the words are that Mastodon is not at risk.

        1. Threads federates with Mastodon instances
        2. Threads uses its massive engineering resources to implement proprietary functionality that’s incompatible with Mastodon instances
        3. A non-trivial number of Mastodon users jump over to Threads, this is the first wave of people that leave Mastodon
        4. Threads drops support for federation and silos itself off
        5. The majority of the remainder of people on Mastodon jump over to Threads because they want to be able to continue to interact with the people that jumped over to Threads and/or because they want to be able to continue to interact with normies now that they’re used to that
        6. Mastodon is effectively dead, safe for a select few that stick to their guns

        3 and 5 will happen in a cascading manner, the more people switch to Threads, the more others will also want to switch.

        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.

        Perhaps it is destined to be destroyed.

        The concerns and ramifications of a large corporation, or any entity that vastly overshadows the "organic" Mastodon user base in orders of magnitude for that matter, federating with Mastodon have been brought up numerous times by many parties, with the goal of looking for a solutions.

        These concerns weren't only brought up in light of a possible EEE strategy that lead to the death of Mastodon, but also in light of a more Google-esque play where the market share isn't necessarily used to outright kill, but instead to exert control1.

        Every single time it fell on deaf ears (i.e. Rochko ignored it, if not outright killing the discussion), often shrugged off matter of factly that it isn't a risk.

        Also make no mistake, we're talking about a layered issue here.

        A network that can destroy Mastodon against its will due to its sheer size is bad enough.
        Mastodon, by virtue of Rochko, facilitating this from within, adds an entirely new dimension to this.

        1 Google famously bypasses standardization bodies and simply implements their in-house developed standards, leaving other browser engines to get with the program and implement what Google wants, or become irrelevant

      • The sanest comment here.

    • 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.

    • The whole XMPP was used by nerds thing really showed how full of hubris he is, agreed.

      This is going to end in a disaster, and this blog post from him will be linked at for decades to come to try and warn the next generation the next time we need to do something like this.

      And the cycle will repeat.

  • For me, I don't need new fancy features to communicate. I don't need video chat rooms. I don't need constant notifications. I just need a simple place to post my social expressions and read other people's social expressions. I don't want my experience to be shaped by algorithms designed to keep me engaged and present. For me, social media is like going down to the pub and talking with some regular friends. The BIGGER a platform is, the less it's about being social, and it's more about promotion. Promotion of self, events, clubs, companies, etc.

    Threads will take away people from Mastodon, but that's a good thing. Because it will appeal to people who desire a different social media experience. They can take the foam off the top, leaving us with a smaller group that prefers a simpler, less invasive, social media. I don't have to share all my contacts, my browsing history, my health data or my financial data to Mastodon (or any service in the Fediverse) in order to use it. You cannot say the same about Thread.

    I will always side with something like Mastodon over Thread. That doesn't mean I don't believe Mastodon cannot fail. It certainly can. But it won't be Thread that kills it.

  • 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…

    • Aged? The article is recent.

      It is a pretty dumb comparison, though. Dude should have done his homework.

      • Which corroborates Eugen either being really damn naive or a paid shill.

  • That is so naive thinking I’m my opinion. They probably gonna use that in the long run to connect only their apps (like you can comment on Facebook from IG). Why would they want people outside of their ecosystems to connect with them? I deleted all their apps and I’m gonna do it with every Fediverse app that federate with them. I know that data in Fediverse is public but I wanted to join community-driven ecosystem outside of Meta.

    • The apps for the fediverse aren't responsible for federating with Meta, the instances (servers) are.

      If my instance (lemmy.world) federates with Meta, I need only to switch servers (say, to lemmy.ml or lemm.ee), not stop using the current app I use (mostly Jerboa, but also Thunder and LiftOff).

  • Rochko has demonstrated to be either foolish or naive, and both are bad.

    I'm not betting on him to having been bought, out of a minimum of trust, but it wouldn't surprise me if that's the case.

    • XMPP did not exist on its own outside of nerd circles, while ActivityPub enjoys the support and brand recognition of Mastodon.'

      Is he foolish? I can't tell, mastodon is massive. Look at mastodon.social, there's already plenty of people here.'

    • Mets is not different than any other person entering the fediverse. They are ultimately a company and will do what they need to be profitable. Ultimately they advertise social connection, and that's their business model.

      Why is everyone acting like meta is different than anyone else, they're not special.

      • Because decentralized social networks don't need to be profitable. That's the whole point of this. Spread out, smaller instances, there is absolutely no need to for an instance to become so massive that it requires profitability to continue.

      • I see meta no different than the company behind mastodon

  • 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.

  • Da heck? Do we have a FB shill?

    • That or a starry-eyed optimist who hasn't heard of XMPP and thinks Mark "they 'trust me', dumb fucks" Zuckerberg is really engaging with ActivityPub on anything resembling a good-faith basis.

    • Can you elaborate what you mean?

    • Want to ask how? I see meta no different than any other company or person joining the fediverse. They ultimately get no special treatment and are subject to each instances moderation.

  • Of course it's a shit product name that uses a generic commonly used term. :/

277 comments