stux⚡
After close consideration we have come to the decision to block Threads.net instance wide on all related instances
(mstdn.social, masto.ai, mastodon.coffee, pixey.org, gram.social)
The new Meta policy goes against much we stand for and we will not allow to let it spill over to the Fediverse
I just checked the numbers and it seems Threads is the biggest 'loser' here
On all instances combined we lose just under 100 followers spread across all instances
Threads will lose over 13K total
NeonPurpleStar :heart_bi:
stux⚡
Some people may wonder why it's now and not before and I would like to try and explain as good as I can
We are a relative large instance in the Fediverse so that comes with a lot of responsibility in making decisions. One of our main goals is safety but we also want to be open and connective until a certain point
Threads promised to be different and we always kept it with a grain of salt but did let the people decide if they wanted to block or not
The new policy is just far over the fine line
stux⚡
I understand it's rough to lose accounts you follow from Threads but unfortunately it is not worth the risk
Hopefully people on Threads will realize the true origin of the company running their platform and will make the decision to join us here in the Fediverse ❤️ :fediverse:
I really really tried making this work but I cannot go any further
Mark Zuckerberg is a person I cannot and will not with with in any way. Sorry not sorry
Jan Wildeboer 😷:krulorange:
@stux Thank you for this clear decision and thank you for explaining the reasons in this open and transparent way for all federate to see. It is (IMHO) the absolute right decision.
NeonPurpleStar :heart_bi:
parallel unstable lean :OwOid:
Femme Malheureuse
@stux Thanks, stux, fully support you. I had filtered Threads accounts and blocked the domain but this makes it more reliable. I don't want Meta harvesting my personal info or posts because a Threads account crossed the streams.
It's not as if folks can't go to Threads and follow accounts there by other methods.
Aurora 🐌
@stux well done!
Aral Balkan
@stux Thank you. Better late than never.
Now let’s see what the biggest Mastodon instance does. Is this enough to tip them over the line? Amazing that this level of unabashed fascist policy is what it has to take for the so-called ethical alternatives to block an entity that has literally fueled a genocide and whose business model has always been based on exploiting people. Maybe next time folks will act sooner and deny them their social capital to begin with.
stux⚡
The hammer has done it's work :banhammer:
Rich Felker
@stux Not just saying "we're going to loosen up our moderation" but explicitly "transphobia is fine now, and here are explicit examples of how you can frame it to avoid being moderated" is WAY OVER THE LINE.
Thanks for doing the right thing here.
And kudos on waiting to let Zuck cross the line so flagrantly that there will be strong consensus this is the right thing to do.
Rich Felker
@stux @cainmark @ivor We can federate with them on bsky if they activate the bridge, and wait around for bsky to fuck up so bad they move here. In the long game we always win. Because capitalism always enshittifies things. It can't stop itself.
stux⚡
@cainmark @ivor From one centralized platform to the next! What could go wrong :blobcatgiggle:
Cainmark Does Not Comply 🚲
My spouse and her groups are all moving to Bsky. Couldn't get them to understand Mastodon or the fediverse and everyone they know jumped to bluesky because it seemed more familiar and most people they already knew were on it. There doesn't seem to be an equivalent to the "marketplace" there though, one of the main things they use it for.
Ivor Hewitt
@stux indeed, although I expect anyone on threads unhappy with the choices will instead move to bluesky. 🤷♂️
The majority remaining just won't care.
Libby
@stux building consensus can be a long process, especially when there is a large group of people involved and it is a good thing the fediverse is not a hive mind. A clear red line has been crossed now and thankfully all involved see it now. When things are really clear, consensus becomes easy. Thanks a lot, to all involved in this decision.
SocProf
@stux A good and perfectly understandable decision. I believe it was the right decision to allow threads initially. It's also the right decision to reverse that now.
Rich Felker
@ThaMunsta @stux The announcement of new policy was basically a tutorial on "here's how you can do transphobic hate now and not get banned".
Mike Johnston
@stux Hey if you read this and have time to - is there a line (or lines) in particular from the new policy that stood out to you? It may help smaller instances like myself make a call on what to do. Thanks!
Edit: I see your earlier post with Marks video - this makes sense. I didn't realize the meta changes making news obviously cause issues with threads and fedi.
Rich Felker
@exiltoaster @stux They issued a policy statement that explicitly told people transphobia is welcome, and gave tips on how to frame it.
Instances that explicitly welcome and encourage hate speech (i.e. the "naziverse") are generally defederated from decent instances.
exiltoaster :breadified:
@stux Isn’t it too early for this step? As a user, I have not yet noticed anything negative from threads here. Was this because of your good work or because there were hardly any interactions with threads?
Rich Felker
@exiltoaster @stux Yes. They explicitly advised calling transness "a mental illness" and using religion as an excuse to attack trans people. IN THE POLICY ANNOUNCEMENT.
exiltoaster :breadified:
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.