"ActivityPub with Meta extensions"
If there are more Threads users than non-Threads users then non-Threads instance admins have to choose between adapt or risk emigration. EEE is a consolidation tactic after all.
If there are more Threads users than non-Threads users then non-Threads instance admins have to choose between adapt or risk emigration. EEE is a consolidation tactic after all.
Mastodon admins might find that law applies to them too.
It's the realm of pure fantasy to envision a world where the EU bans an original community project to force everyone into a Meta-designed fork. Mastodon users should be safe as long as they're free to run their own server and client software.
My point is that this really doesn't matter. If they use ActivityPub as-written, both clients and servers can stop Meta content from reaching their feed. If you just find Threads content annoying, you long-press the post and tap "Block Instance". If you're a site admin and have been given a legitimate reason to block Meta for API abuse (eg. poorly-moderated content, spam, advertisement) then you can exercise your defederation power and be within your right.
Further, interoperability concerns messaging apps, not social media apps.
Explain how a peer that is >100x the size of the Fediverse needs it at all.