There's a common false dichotomy about #Threads: cut them off, or leave it to user choice.

I can't speak to other software, but Mastodon offers a third option: limiting Threads. This can be done for all users of a server.

- You can follow Threads accounts after clicking through a warning.

- You have to manually approve followers _from_ Threads.

Note, however, that boosted posts will continue to appear in your home timeline:

https://github.com/mastodon/mastodon/issues/26301#issuecomment-1868240966

Silenced users' content can appear on home timeline via boosts · Issue #26301 · mastodon/mastodon

Steps to reproduce the problem Preconditions: Have account Y status on local instance be Limited, or, account Y is on server Z which has a server-wide Limit in place on your local instance. Follow ...

GitHub

@eloquence
The gatekeeping is nuts here

People talk about how ActivityPub and open SocialProtocols are the future and wish for them to be implemented everywhere, only then for when it actually happens to cut off those people like a disease...

Really sad to see, imagine the backlash we would give Threads if they were doing this

@zav_ @eloquence While I agree that some instances are way too gatekeepy (mastodon.art is a prime example), not federating with Meta is not about gatekeeping, but about preservation.

Meta is not joining to "expand possibilities for their users" or to give choice. Nothing of that fits in their business model.

What they hope to achieve is only left to speculations, but every possible way that they do business makes it clear that this is NOT going to be good for fediverse.

You illustrate how current servers can limit Meta, but forget that Meta can also defederate, and use this as a tool to control.

You don't think they will? You don't think that can be a severe blow to many servers unless other servers band together against this?