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.
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.
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.
@Dee_Imaginarium @giallo I wish most Mastodon instances were planning to defederate from Meta by default but sadly that's not the case. Meta reached out to the admins of some of the big instances and a whole bunch of them don't plan to. One of the admins shared this — https://fosstodon.org/@kev/110592625692688836
Some admins are going for a "trust but verify" approach. These are the only instances which have agreed to defederate from the start —https://fedipact.online/
Attached: 1 image Yeah, that's gonna be a hard pass from me thanks, Rachel. Zero interest in having a conversation with #Meta "off the record" or otherwise. Sharing this purely to be as transparent as possible with our members.