What’s Meta up to?

  1. Embrace ActivityPub, , Mastodon, and the fediverse

  2. Extend ActivityPub, Mastodon, and the fediverse with a very-usable app that provides additional functionality (initially the ability to follow everybody you’re following on Instagram, and to communicate with all Threads users) that isn’t available to the rest of the fediverse – as well over time providing additional services and introducing incompatibilities and non-standard improvements to the protocol

  3. Exploit ActivityPub, Mastodon, and the fediverse by utilizing them for profit – and also using them selfishly for Meta’s own ends

Since the fediverse is so much smaller than Threads, the most obvious ways of exploiting it – such as stealing market share by getting people currently in the fediverse to move to Threads – aren’t going to work. But exploitation is one of Meta’s core competences, and once you start to look at it with that lens, it’s easy to see some of the ways even their initial announcement and tiny first steps are exploiting the fediverse: making Threads feel like a more compelling platform, and reshaping regulation. Longer term, it’s a great opportunity for Meta to explore – and maybe invest in – shifting their business model to decentralized surveillance capitalism.

  • FaceDeer@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    What specific features do you have in mind that could be implemented in a closed-source manner that couldn’t be reverse-engineered and implemented by open-source instance software too? It’s not easy to come up with such a thing, and it’s unclear what benefit it would serve Meta that they can’t accomplish by just not joining the Fediverse in the first place.

    If Threads implements asymmetric federation, I’ll shrug and ignore them because I’ll never see their content and it won’t ever affect me.

    Doesn’t Threads already have a bullshit terms of service? That’s my default assumption for any website, really. But even if they don’t, ActivityPub is an open protocol and so of course my data is being collected by who-knows-how-many organizations already. Meta doesn’t need to do anything new at all to get access to it.

    • Lvxferre@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Sorry for the wall of text.

      What specific features do you have in mind that could be implemented in a closed-source manner that couldn’t be reverse-engineered and implemented by open-source instance software too?

      The features don’t need to be impossible to reverse engineer; they could be costly enough to do so, rely on other FB/Meta platforms, or demand server capabilities past what you’d expect from typical Mastodon instances. For example:

      • implementing some data format that is decoded by the front-end
      • allowing you to access content from FB/IG/WhatsApp from Threads
      • “we now allow big arse videos”.

      and it’s unclear what benefit it would serve Meta that they can’t accomplish by just not joining the Fediverse in the first place.

      Killing a bird and a baby mammoth with a single stone, before they grow and invade your turf.

      On one side you have Twitter/X; it bleeds money and Musk is an idiot, but he has enough money to throw at the problems until they go away, and he has a “vishun” about an “errything app” that would clearly compete with FB/IG/WhatsApp. On another you have the Fediverse; it’s small and negligible but it has potential for unrestricted growth, and already includes things like Matrix (that competes with WhatsApp) and Friendica (that competes with FB).

      From Meta’s point of view, Twitter/X is by far the biggest threat. It could be addressed without federation, but by doing so would feed Mastodon, and a stronger Mastodon means a stronger Fediverse and this power would put Matrix, Friendica etc. in a better position. With federation however they can EEE one while killing another, and still advertise the whole thing as “I don’t understand, why you say that we have a monopoly over online communication? We’re even part of a federation? Meta plays nice with competitors. I’m so confused~”.

      • FaceDeer@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        “Some data format” is still a pretty vague handwave, IMO. What would they implement that other Fediverse users would need to care about? Some kind of proprietary image or video format? I don’t see how that would gain traction.

        Fediverse users can already link to FB/IG/WhatsApp content. Are you suggesting embedding it somehow? I’m not sure how that could be done in a proprietary manner that other implementations couldn’t copy.

        “We now allow big arse videos” is definitely not a feature that couldn’t be reverse engineered. Instances can already do their own hosting, or not, depending on the resources the host wants to dedicate.

        I’m sure that Meta would just love to be able to push a button that made all their competitors die. Everyone wants that button. Look around threads like this and count how many users would love to push that button themselves and wipe Meta out with it. But I’m just not seeing how Meta is going to do that by federating. As long as everyone keeps on their toes about how their resources are being used and what extensions they’re adding to ActivityPub - something that they should be doing regardless of whether Meta is involved - the Fediverse seems pretty solid against attack to me.

    • thenexusofprivacy@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      11 months ago

      Here’s five examples that they’be already done:

      1. Signing up with an Instagram account
      2. Automatically following everybody you follow on Instagram
      3. The ability to follow a thread on Threads
      4. Seeing content from anybody on Threads in your app
      5. Communicating with people on Threads who haven’t opted in to federation

      (Edited for formatting)