Dear @Gargron,

A fediverse server called Threads is violating mastodon.social’s second server rule:

“2. No racism, sexism, homophobia, transphobia…
Transphobic behavior such as intentional misgendering and deadnaming is strictly prohibited.”

https://glaad.org/smsi/report-meta-fails-to-moderate-extreme-anti-trans-hate-across-facebook-instagram-and-threads/

Can you please defederate from this server to protect the trans people on mastodon.social?

Thank you.

PS. It’s run by these guys: https://techcrunch.com/2024/03/26/facebook-secret-project-snooped-snapchat-user-traffic/

#mastodonSocial #fediblock #threads #meta #mastodon #transphobia

Report – Unsafe: Meta Fails to Moderate Extreme Anti-trans Hate Across Facebook, Instagram, and Threads | GLAAD

GLAAD’s Social Media Safety Program reported the following anti-trans hate content across Instagram, Facebook, and Threads; Meta deemed all of it non-violative or did not take action on it.

GLAAD | GLAAD rewrites the script for LGBTQ acceptance.

@aral @Gargron of all the pro-meta blog posts in the past six months, I have never read anything to the tune of "Threads is bound by Mastodon's terms of service like any other instance."

Hundreds of thousands of published words and none formed a sentence close to that. Not even in the form of a question. Odd.

@fromjason @aral @Gargron I wonder if Mastodon is the right platform to develop an approach to #Threads. The micro posts don't give enough space. Every other post is about someone who has blocked someone.

In fighting Internet offences like copyright infringements, CSAM, etc. I understood the best approach is to tackle the source. Why not here?

I also wonder if Threads is bound by other servers' TOS. I doubt it. If so, it would apply both ways. Difficult to manage in an open federated network.