Threads’ plan is to implement the ActivityPub protocol, the one the fediverse is based on.
In theory threads could then be federated with other ActivityPub servers (Mastodon and Lemmy for example).
In practice, many instance admins saw it as meta’s way to invade that space with their own proprietary bullshit on top of it so they can progressively take control of it. So many decided to block threads as soon as it would be able to federate with their instance.
Technically it was a mastodon clone
i’m curious: what makes it a mastodon clone over a twitter clone?
They could federate with servers if only they had servers that wanted to federate with them.
Threads’ plan is to implement the ActivityPub protocol, the one the fediverse is based on.
In theory threads could then be federated with other ActivityPub servers (Mastodon and Lemmy for example).
In practice, many instance admins saw it as meta’s way to invade that space with their own proprietary bullshit on top of it so they can progressively take control of it. So many decided to block threads as soon as it would be able to federate with their instance.
Of course the community blocked it. They didn’t even try to disguise their EEE attempt (Embrace, Extend, Extinguish). Duh.
And this isn’t the first time. Back in the day Facebook messenger was actually fully XMPP federation compatible! But they pulled the plug on that.
Sure. They targeted Fediverse apps like Mastodon and Bluesky.