Erik MoellerDec 16, 2023

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
Show threadErik MoellerDec 16, 2023

I like that option for our server, social.coop, and it's the one we voted to implement earlier this year.

We know that Threads already hosts bad actors (e.g., LibsOfTikTok). We know some reasonable folks have set up shop there and will continue to flee there from X.

This option makes it clear that Threads is not a safe space, while allowing limited connections.

Every instance will implement the option that makes sense to them, of course.

Show thread๐Ÿฆ‡๐•ญ๐–†๐–™๐Ÿฆ‡Dec 18, 2023
@eloquence If there is nothing in the federated timeline from threads, then where/how is "discovery" handled?
Show threadErik Moeller

@Batronyx

In general, "limiting" is bad for discovery - you won't see such accounts unless you explicitly search for them & follow them. Even then it gives you a warning you have to click through.

mastodon.social (the server you're on) has chosen to neither limit nor suspend, so you won't encounter those issues there.

Dec 18, 2023 at 5:06pmWeb