Until your instance defederated from big instances

Do you realize that fediverse is not one single project? For example Lemmy and Mastodon has different implementation and developers. The only thing that connecting them is ActivityPub, which is owned by W3C, not the community. So basically Meta created their own implementation for Threads (so it’s already propertiary), and theoretically already able to pressure W3C to change the ActivityPub without even joining fediverse

So they have already reaching OP’s first point without doing anything

I think I miss something, the ActivityPub protocol is not owned or maintained by Mastodon devs. Isn’t this just standard communication like an extension of HTTP? something like GraphQL (that created by Facebook itself). Quick google mentioned that ActivityPub is maintained by W3C.

So Meta can (and I think currently uses) ActivityPub, and all of your points already been possible without needing to federates with any other instances. For example, they already can say that ActivityPub doesn’t work on some cases, and push W3C to do some changes on the standard

Let’s say all of mastodon instances not federating Threads. What stopping Meta to do EEE on ActivityPub? That protocol is not owned by mastodon creator or other devs. It’s handled by W3C afaik