Skip Navigation

Meta can rage farm Mastodon without controlling it

Meta can introduce their signature rage farming to the Fediverse. They don't need to control Mastodon. All they have to do is introduce it in their app. Show every Threads user algorithmically filtered content from the Fediverse precisely tailored for maximum rage. When the rage inducing content came from Mastodon, the enraged Thread users will flood that Mastodon threads with the familiar rage-filled Facebook comment section vomit. This in turn will enrage Mastodon users, driving them to engage, at least in the short to mid term. All the while Meta sells ads in-between posts. And that's how they rage farm the Fediverse without EEE-ing the technology. Meta can effectively EEE the userbase. The last E is something Meta may not intend but would likely happen. It consists of a subset of the Fediverse users leaving the network or segregating themselves in a small vomit-free bubble.

Some people asked what EEE is:

You're viewing a single thread.

93 comments
  • So many knee-jerk reactions.

    This is an open protocol with complete freedom to create apps and scripts. If this becomes an issue users could block certain interactions in a granular manner, for example block replies from certain instances.

    XMPP being thrown around as an example makes me think people who do it weren't there to witness it. XMPP by itself wasn't really used by many but there were also many more popular messaging platforms at the time. XMPP wasn't killed because it wasn't ever alive other than short golden era when it was mostly a way to open itself to third party clients (Gaim, Trillian, Adium etc) which was very nice.

    Next year EU is going to make all tech giants open in this way again. Mastodon can EEE Threads too by being a better implementation. It has no commercial pressure and Activity Pub and formatting tweets is not as complex as a web browser engine or a word processor document format which are way better examples of successful EEE.

    If you defederate you'll end up exactly where XMPP is.

    • I agree with the sentiment, I'm not a fan of preemptively blocking meta on instance level, especially when everyone was touting about how the fediverse is corporation resistant and by design it is resilient because of it's horizontal nature, but at the first sign of threat they resort to the nuclear option.

      Having said that, Lemmy specifically lacks tools on the user level, especially blocking instances. If a user doesn't want to associate at all that is understandable (privacy concerns, not wanting to interact with hate groups, etc) but right now they can only block communities and users individually, which would make it impossible to block meta.

      Lastly, I feel there are avenues that haven't been properly explored, like forcing them to open source if they want to federate. (On the grounds of privacy concerns and security) In practice that would be the same as blocking them, but it would laid out a good foundation for new companies that want to enter the space without having to discriminate on a case by case basis.

      Problem is that blocking is the nuclear option and everyone blovking before something comes out, which no one knows the danger yet like a hate speach platform would entail, goes against the spirit of the fediverse.

    • Ok WTF does "EEE" mean? I've seen people throw it around as if it's some totally common abbreviation. Even if I google for it, all I find is some horse virus.

      • Embrace, extend, extinguish.

        Embrace an open standard by using it yourself, start extending it at a pace competitors can't (preferably obfuscating how it works), leave everyone behind.

        A good example is Microsoft Internet Explorer back in the day. Web technologies like HTML and CSS are open standards and at the time fairly straightforward. Once Microsoft hit critical mass by bundling IE with Windows they took leadership from Netscape and started adding more and more proprietary crap like ActiveX which some sites opted to use because everyone was using IE anyway and people using other browsers were forced to use IE. This was also a major issue for Linux users at the time.

        It took years of regulatory / antitrust pressure, tremendous effort from Mozilla and their browsers, as well as big players like Google and Apple embracing KHTML (later forked into WebKit and then Blink engines) to unscrew humanity from that depressing era of internet history.

        Web browsers working slightly differently is still an issue without anyone breaking compatibility on purpose. It was just so much worse when someone did it maliciously.

    • Next year EU is going to make all tech giants open in this way again

      Can you expand on that?

93 comments