#Admin #IndiewebSocial #Threads

Tim Chambers

IMPORTANT: New Policy... A few days ago, I expressed concern over Meta’s new fact-checking and content moderation policies. When Threads announced its move to the Fedi over a year ago, we chose not to take preemptive action. Instead, we saw that we had all the tools needed for proportional responses to potential threats to keep our folks safe. And as we stated then, we would treat Threads.net like any other Fediverse server.

(1 of 2)

https://www.timothychambers.net/2025/01/10/moderating-threads-at-a-server.html

Tim Chambers

(2 of 2) #IndiewebSocial #Threads #Admin

Although we haven’t received any moderation tickets from Threads users, not a single ticket, Meta’s updated content policy changes are, in our view, an action that by itself warrants a server level response.

Effective Immediately: Limiting Threads at Indieweb.Social At A Server Level

For more read the full statement here: and am very up for any good faith comments or questions in the comments.

Full statement here:

https://www.timothychambers.net/2025/01/10/moderating-threads-at-a-server.html

Annelies Kamran, Ph.D.

@tchambers Fair. Thank you.

Tim Chambers

@akamran Thank you, Annelies ….

Evert Pot

@tchambers Sensible!

Alwyn Soh :mastodonsg:

@tchambers are there plans to limit other instances who choose not to limit/block threads?

Tim Chambers

@alwynispat Do not foresee that being needed. But always looking at what we need to do based on changing circumstances.

Tim Chambers

@evert Thank you!

Aulia Masna

@tchambers I think this is the sensible take, at least for the time being because as you said, limiting instead of blocking allows for individual choice instead of slamming down the ban hammer for everyone whether they like it or not. Most people aren’t on Masto/Fedi but may be on Threads while the other, more likelier option than switching to the Fedi is to jump to Bluesky which doesn’t federate with this place without a bridge.

Tim Chambers

@aulia Thank you, Aulia…