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
    3
    ·
    1 year ago

    Actually, I’d say “let them use TREDZ and destroy themselves if they want, problem solved.” In this day and age nobody wants a proprietary image format, and if Threads won’t display in a browser they’ve just blown one of their legs off.

    This is a general problem with trying to make Threads depend on proprietary formats, they can’t do that and still have it work in an ordinary web browser.

    • Lvxferre@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      Most people don’t even know what’s a proprietary image format. From their PoV it would be “shitty broken Mastodon doesn’t show images properly”. And they would still pressure Mastodon users to switch.

      if Threads won’t display in a browser they’ve just blown one of their legs off.

      I’m not sure but I think that a similar strategy could work for browsers, using a web plugin.

      But even if Meta decided that Threads is unavailable from browsers, it wouldn’t be blowing one of Threads’ legs off. There are far more mobile than desktop users nowadays; and if they want to EEE the Fediverse, they need numbers for that.