Mastodawn

clifff Jan 10, 2025

Shakedown folks (and only Shakedown folks please) - let's talk defederating with threads.net. Meta's recent policy changes explicitly allow homophobic, sexist and transphobic content https://www.theverge.com/2025/1/7/24338471/meta-hate-speech-hateful-conduct-policy-moderation

This makes their moderation policies directly contradictory to ours. Normally we'd handle this by blocking the server in question, and I don't see any reason why Threads would be different.

Does this move make sense to people? Any arguments for staying connected?

#stateOfShakedown

Here are some of the horrible things that you can now say on Instagram and Facebook

Meta’s policy changes around hate speech have sharply changed the content that’s banned or allowed when it’s based on gender, sexual orientation, and the coronavirus.

The Verge

Show thread

Chop Jan 10, 2025

@clifff I differ from the opinions of others here. I think you harm Shakedown users who are looking for avenues to more mainstream content way more than you harm Threads. I’d rather see us take a wait-and-see approach on whether Threads toxicity penetrates our server. Then if it does, block without remorse.

Show thread

Chop Jan 10, 2025

@clifff Part of my reasoning is the ability to access Threads content is a big benefit of being on Mastodon. The only content I see from Threads is positive content that I want in my timeline. I don’t even know if it’s possible for troublesome Threads accounts to integrate with Masto without being “invited.” As much as I’m disgusted by Meta, we’d be spiting ourselves and harming the Masto experience. I’d rather take a pragmatic approach.

Show thread

Byron

@chopaganda @clifff this is pretty much my feeling. I follow the threads accounts I choose. I don't think I've ventured out of home or local to the federated stream in ages. which I assume the federated is where you'd be most likely see something toxic.