I see many people purporting that users blocking Threads on an individual basis as a solution, but it’s not… Blocking Threads will not prevent Threads users’ comments in federated instances from showing up.
Even if you block Threads, you will still see hateful, harassing, and extremist content and misinformation.
Furthermore, even if it did block Threads engagement entirely on an individual blocking basis, it is still a failure on the instance admins to adequately protect their users and cultivate a healthy community.
.world admins defederated with exploding heads due to hate, harassment, and extremism/misinformation. Why would they then federate with Threads which harbors the same toxic users?
It’s a move to bring more users into the Fediverse, but it comes with costs and risks that do not justify the short-sighted gain of more users and inching towards becoming mainstream.
Threads has been subject to mass amounts of radicalizing, extremist content, and there have also been instances of users having personal information doxxed on Threads due to Meta’s information-harvesting practices. [1]
Threads was marketed to be open to ‘free speech’ (read: hate speech and misinformation) and encouraged the Far-Right movement to join, who have spread extremism, hate, and harassment on Threads already. [2] Threads has been a hotbed of Israel-Palestine misinformation/propaganda. [3]
They fired fact-checkers just prior to Threads’ launch [1], however they claim they will have 3rd party fact-checkers next year. [4]
Meta/FB/Instagram has a rampant history of illegal and unethical practices, including running experiments on their users which affected their moods and induced depression in many uninformed, non-consenting subjects. [5] Such unethical experiments could affect federated users as well.
(Edit: As @massive_bereavement reminded me, Meta also assisted in genocide! [6])
Meta/FB/Instagram also have a strong history of facilitating the spread of misinformation and extremism, which contributed to the January 6th insurrection attempt. [7]
If exploding heads was defederated with because of this sort of toxic extremism, why would they want to federate with a platform plagued by that same content? One known for shortcomings moderating it? And one which comes from a company with a long history of unethical and illegal practices regarding users?
I have donated to the .world instance since my first week here, but should they continue with federating with Threads, I will be cancelling my donations and finding an instance that won’t undermine the safety and well-being of their users for a boost of (largely toxic) new users and an inch towards being mainstream.
The gains are immediate but minimal, and come at great costs which do not warrant federating with Threads (IMO).
I see many people purporting that users blocking Threads on an individual basis as a solution, but it’s not… Blocking Threads will not prevent Threads users’ comments in federated instances from showing up.
Even if you block Threads, you will still see hateful, harassing, and extremist content and misinformation.
Furthermore, even if it did block Threads engagement entirely on an individual blocking basis, it is still a failure on the instance admins to adequately protect their users and cultivate a healthy community.
.world admins defederated with exploding heads due to hate, harassment, and extremism/misinformation. Why would they then federate with Threads which harbors the same toxic users?
It’s a move to bring more users into the Fediverse, but it comes with costs and risks that do not justify the short-sighted gain of more users and inching towards becoming mainstream.
Threads has been subject to mass amounts of radicalizing, extremist content, and there have also been instances of users having personal information doxxed on Threads due to Meta’s information-harvesting practices. [1]
Threads was marketed to be open to ‘free speech’ (read: hate speech and misinformation) and encouraged the Far-Right movement to join, who have spread extremism, hate, and harassment on Threads already. [2] Threads has been a hotbed of Israel-Palestine misinformation/propaganda. [3]
They fired fact-checkers just prior to Threads’ launch [1], however they claim they will have 3rd party fact-checkers next year. [4]
Meta/FB/Instagram has a rampant history of illegal and unethical practices, including running experiments on their users which affected their moods and induced depression in many uninformed, non-consenting subjects. [5] Such unethical experiments could affect federated users as well.
(Edit: As @massive_bereavement reminded me, Meta also assisted in genocide! [6])
Meta/FB/Instagram also have a strong history of facilitating the spread of misinformation and extremism, which contributed to the January 6th insurrection attempt. [7]
If exploding heads was defederated with because of this sort of toxic extremism, why would they want to federate with a platform plagued by that same content? One known for shortcomings moderating it? And one which comes from a company with a long history of unethical and illegal practices regarding users?
Due to these issues and Meta’s rampant history of unethical and illegal business practices, there should be no federation with Threads for the well-being of the users in this instance.
I have donated to the .world instance since my first week here, but should they continue with federating with Threads, I will be cancelling my donations and finding an instance that won’t undermine the safety and well-being of their users for a boost of (largely toxic) new users and an inch towards being mainstream.
The gains are immediate but minimal, and come at great costs which do not warrant federating with Threads (IMO).
Your honor, I would also like to present their role in Myanmar’s genocide