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.

  • thenexusofprivacy@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    3
    ·
    1 year ago

    Sure, Meta – and Google, and Microsoft – is good about funding open-source projects when it suits their interest. Given where they are relative to Open AI and Google, releasing LLaMA as open source made a lot of sense for them. If they decide to seriously invest in fediverse compatibiilty they might well do something like release an open source client toolkit that would provide full functionality on Threads, whatever subset of Threads functionality Mastodon and maybe a couple of other platforms suppport, and has adaptors so that the community can support other platforms. Right now there isn’t a good solution (nobody uses the AP C2S standard, Mastodon’s API is the defacto standard but there are compatibility problems and quirks) so it benefits the community. And, it would have support for Threads functionality that other platforms don’t support, so it benefits Meta more than everybody else.

    But we were specifically talking about why they’d make it easy for people to move away from Threads to other platforms. Do you think that’s in their business interest?