Hello Fediverse admins, Meta's platform Threads has now switched to a new domain so it's time to add this to your defederation list:
threads.com
Here's how to defederate a server from the Mastodon admin interface: https://fedi.tips/how-to-defederate-fediblock-a-server-on-mastodon
(via @TechCrunch at https://techcrunch.com/2025/04/24/threads-officially-moves-to-threads-com-and-updates-its-web-app)
p.s. Okay, this is very odd, the article definitely existed as I read it before posting and TC's post about it exists. It said Threads would start redirecting from threads.net to threads.com (instead of other way round) as part of a refresh of Threads' web interface.
Whatever the situation, Meta definitely owns the domain threads.com so it's worth defederating in any case:
https://www.whois.com/whois/threads.com
You can see part of the article if you search for "threads.com" on DDG:
p.p.s. The opening of the article was as follows:
"Threads, Meta's newest social network and X competitor, is officially relocating from the website Threads.net to Threads.com. The transition will coincide with a handful of quality-of ..."
I've attached a screenshot of the post as well, which has now been deleted.
p.p.p.s. ...and now the article is back up again!
https://techcrunch.com/2025/04/24/threads-officially-moves-to-threads-com-and-updates-its-web-app/
Thanks @Crazypedia for pointing this out.
@homegrown LOL this article is such a ridiculous PR soup. Did they just copy paste from a press release? How could a anyone believe that «The change gives Meta a more prominent and better-remembered URL [...] The rebrand of sorts may allow the app to better compete with its rival».
I have no idea why they're making the change but clearly this can't be the reason.
@homegrown looks like the articles is still up on tech crunch itself
https://techcrunch.com/2025/04/24/threads-officially-moves-to-threads-com-and-updates-its-web-app/
That's weird, it was up, then gone, now it's back up... Something strange.
Hmm... this is weird, the post is still there but it now links to a 404:
https://mstdn.social/@TechCrunch/114393612744022019
I wonder if this was under an embargo and they published too early?
The story that was there was saying they were moving to threads.com and redirecting threads.net there, plus also saying the web client was being overhauled. So, it sounds like it was part of some kind of relaunch/refresh of the platform?
Threads.com definitely belongs to Meta in any case:
@homegrown @spiezmaestro @TechCrunch@mstdn.social
It's odd: For the article, I get the 404 error, too (their website), but the #TechCrunch account on Mastodon above doesn't work! Did they come into some Thread-blocking Mastodon mill??
Edit: It was definitively *not* me blocking the instance mstdn.social, I also can't find it via search: @Mastodon @staff - did you know what happened? It's an important official media account! How can you suspend it!?
Yeah, think it might be worth asking mastodon.online why they've suspended it, as it's a genuine account. They even link to it at the bottom of the page on techcrunch.com
Whaaat? The account isn't suspended on mstdn.social and it's verified as genuine on techcrunch.com
Something weird going on at your server if they've suspended that account?
The direct link should work?
It's not suspended on mastodon.social, which is the same admins as mastodon.online, so perhaps this is some kind of mistake by the admins?
The 404 error is something different I think, I'm guessing Tech Crunch pressed "publish" too early and weren't supposed to release the info yet?
@homegrown Yes, the 404 error is on their website.
But you can ask @TechCrunch@mstdn.social personally, why.
And attention, don't confuse mstdn.social with mastodon.social!
BTW, TechCrunch has a very active Threads-Account on Mastodon and a lot of instances block Threads already.
The link is at https://mstdn.social/@TechCrunch/114393612744022019 and the post for it still exists. The article existed (I read it before posting) but for whatever reason TechCrunch just took it down.
The article said Meta would start to redirect threads.net to threads.com (instead of the other way round) and that the Threads website interface was being refreshed.
Either way, it's probably a good idea to defederate it as it is definitely owned by Meta:
Our instance was one of the first ones being blocked by threads ;)
The problem isn't the users, it's Meta.
Meta has a horrific track record on moderation (https://www.thebureauinvestigates.com/stories/2022-02-20/facebook-accused-of-letting-activists-incite-ethnic-massacres-with-hate-and-misinformation-by-survivors-in-ethiopia/) and they are now deliberately allowing hate posts on Threads (https://fortune.com/2025/01/10/staffers-fury-meta-change-hate-policy-mark-zuckerberg/).
Allowing hate to spread is really dangerous for vulnerable minorities (https://social.chinwag.org/@FediThing/112581263140051643).
If people want to join the Fediverse, there are thousands of non-Meta servers they can join instead.
It's unclear to be honest.
I'm mainly aiming the post at admins as a precautionary measure. The domain is definitely owned by Meta so blocking it doesn't cause any harm.
@homegrown @TechCrunch
The article seems to be up again. Archive.today seems to have caught the 404-ification of the webpage, too.
Did they figure we noticed?
https://archive.is/EMZnA
Grow Your Own Services 🌱
Nemo_bis 🌈
Scott M. Stolz
🌬️
Shadow Heart
Octavia Con Amore 
Sander Meijer
Petra van Cronenburg
BrownIsBeautiful
Phoenix Paulina Schmid
Stomata
𝚜𝚎𝚕𝚎𝚊 
Mark Davis
Bart Allen
MOULE (in Rouge!) #RedInstead
Fifo™
River, the Andean Puppy
sztupy
Mark Wyner Won’t Comply 
Stage name Jay Peach
mat 
Sabine Hiller