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 threadChris Alemany🇺🇦🇨🇦🇪🇸Dec 16, 2023
@eloquence can you explain how you have implemented this limiting exactly? #mastoAdmin #selfhosting #selfhosted
Show threadErik Moeller

@chris

If you're an admin, it's done on the "New domain blocks" page (/admin/domain_blocks/new). See https://docs.joinmastodon.org/admin/moderation/#server-wide-moderation

Moderation actions - Mastodon documentation

Features to assist in managing your community.

Dec 16, 2023 at 7:53amWeb