cross-posted from: https://lemmy.world/post/9799372
What's Meta up to?
-
Embrace ActivityPub, , Mastodon, and the fediverse
-
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
-
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.
Can mastadon hosts just refuse to federate with activepub? (I'm probably misunderstanding everything here but hopefully you get my drift).
Assuming you mean "Can Mastodon instances defederate with Threads?": Yes. Mastodon (and similar services) run on the ActivityPub protocol, which allows them to decide who they do and do not federate with. Many instances have chosen to preemptively block Threads, many have chosen not to. Pick what works for you.