Skip Navigation

Meta's upcoming AcitivityPub-enabled app Threads will only come with an "import from Mastodon" option. The new network won't federate on day one.

mastodon.social Alex Heath (@alexeheath@mastodon.social)

Attached: 1 image Some more reporting on the Fediverse aspect of this app:

Alex Heath (@alexeheath@mastodon.social)

Full report is on The Verge.

3
3 comments
  • I'm confused by this - there are various things Meta might want from the Fediverse (free content, more data, more people to serve ads to), but new users can't be one of them. No one from Mastodon is likeky to migrate to Meta's platform; the people who want to use Meta are already there.

  • Anyone operating an instance should defederate from this shit immediately. This is exactly the kind of corporate overreach that isn’t welcome here. This will end very poorly for the fediverse I think.

  • Before everyone freaks out, this has zero impact on our communities. Chill.

    They can already do this by bringing content from Mastodon to Meta platforms via links and screen grabs, this only speeds up the process.

    Personally, I love that they're not federating day one. Because I don't want any instances I use to federate with them, I don't want to be connected to a Meta platform unless I deliberately go to a Meta platform to use it.

    To expedite the process, Mastodon instances should just defederate from them entirely. Don't let them access that data through ActivityPub. They can build their own platform on the Fediverse and we can have our network of smaller connected instances.

    Them doing this does not affect our communities unless we let it. Defederate from them and we can go on our merry way and they can have their own ad laden instance that's not connected.

    Everyone, relax. Continue building your communities here and ignore Meta in their unconnected instances.