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 reason we need to block threads at instance level is to prevent users/Meta itself from data collecting and harassment

@mybarkingdogs

I agree that suspending is the most effective solution against data making its way to Threads via ActivityPub.

Can you say more about the harassment cases you're thinking about? Limiting does seem to go a long way to mitigate that concern, no?