Yes frustrating that no one adds a link to the damn page
Instances that didn't block facebooks- thread.net
Submitted 11 months ago by Yoz@lemmy.world to mildlyinfuriating@lemmy.world
https://lemmy.sambands.net/post/178933
Comments
the_post_of_tom_joad@sh.itjust.works 11 months ago
Ugh, we’re federated with threads? There goes the neighborhood
GONADS125@lemmy.world 11 months ago
Voice your opposition before the decision is implemented. I know I’m jumping ship if Threads ends up being federated with.
the_post_of_tom_joad@sh.itjust.works 11 months ago
Absolutely same
Cheradenine@sh.itjust.works 11 months ago
What the actual fuck?
tun@lemm.ee 11 months ago
Like mastondon.social admin said, you can always block the threads.net at user level.
The instance itself will wait and see.
bionicjoey@lemmy.ca 11 months ago
“Wait and see” for what though? Meta is already a known bad actor in social media. Why give them the benefit of the doubt?
GONADS125@lemmy.world 11 months ago
If anyone is interested in the very long list of unethical and illegal practices of Meta, here’s some of their rampant inexcusable and repeated shitty practices!
HeartyBeast@kbin.social 11 months ago
Wait a see what they actually do. Mad idea, I know.
GONADS125@lemmy.world 11 months ago
This does not stop user comments from Threads. They will still be visible throughout lemmy.world/federated instances, where they can spread more misinformation and radicalism.
Yoz@lemmy.world 11 months ago
Lol so funny- will wait and see…🤣🤣🤣
tun@lemm.ee 11 months ago
Wait and see is my usage. I added the text from the original toot.
misk@sopuli.xyz 11 months ago
What an infuriating UI design, red for federated and green for blocked?
Either way, thanks for a useful link since my instance admin blocked Threads for whatever reason and I need to find a new one. Cheers!
LufyCZ@lemmy.world 11 months ago
It’s because the dev behind the website pushes his anti-threads agenda onto you.
Red means bad.
TheEntity@kbin.social 11 months ago
I mean, what do you expect from Fedipact? The dev doesn't push anything onto you, you willingly visit a list that got created for the very purpose of going against Threads. There is no hidden agenda.
IWantToFuckSpez@kbin.social 11 months ago
Maybe they Chinese? In Chinese stock markets red is up green down.
DarkThoughts@kbin.social 11 months ago
No. Federated = bad, thus it is red.
twack@lemmy.world 11 months ago
Embrace < you are here
Extend
Extinguish
Dadifer@lemmy.world 11 months ago
Technically, aren’t we at Extend?
Firefly7@lemmy.blahaj.zone 11 months ago
No. Extend is the part where they add their own proprietary features to the protocol that create interoperability problems with the rest of the services using the protocol.
igordsmelo@mastodon.social 11 months ago
@Yoz as long as users can block Threads themselves 🤷🏽♂️ it seems there is an intersection between those most interested in blocking Threads and the tech/privacy-savvy portion of the Fediverse.
They'll probably be able to go through the steps of blocking Threads, which differ in the various services, but on Mastodon is relatively easy.
Eventually it may be necessary to make this process even easier, by prompting the users or something. But rn, it seems enough
GONADS125@lemmy.world 11 months ago
Blocking Threads on the instance user level does not block Threads users from commenting and spreading radicalism/misinformation throughout federated instances. It’s a half-measure. To actually block Threads, it requires the instance to defederate.
I’m ethically opposed to federation because it is with a platform plagued by hate, radicalism, and misinformation. [1] Including being a hotbed for Israel-Palestine misinformation. [2]
I think it’s hypocritical to defederate from exploding heads and to then federate with Threads which harbors the same harmful content and toxic userbase.
If lemmy.world goes through with federating with Threads, I’m out of here and my donations to the instance are too.
LilB0kChoy@midwest.social 11 months ago
I agree with you in being ethically opposed to Threads but I can’t fault any instance that wants to wait for Threads to violate their policies before defederating.
I know some instances have chosen to preemptively defederate and that’s their perogative, I just don’t think all of the vitriol I’ve seen towards instances that haven’t is fair at this point.
Korne127@lemmy.world 11 months ago
So the instances which can’t access Facebook content but can still be seen by Facebook… that will show 'em
possiblylinux127@lemmy.zip 11 months ago
The key is to not let Threads content overtake all other content. Threads is big so it could overwhelm everyone on the fediverse
netburnr@lemmy.world 11 months ago
Yeah the people pushing this agenda don’t seem to grasp that whatever you post goes to threads. They still get your data no matter what. And so does Google and every other web scraping technology.
GONADS125@lemmy.world 11 months ago
What’s more concerning is the hate, extremism, and misinformation that will be coming from Threads.
That is the actual problem and where the level of concern and majority disinterest in Threads federation stems from.
possiblylinux127@lemmy.zip 11 months ago
I don’t think it has anything to do with data (this is the public internet). Its about Embrace, Extend, Extinguish.
possiblylinux127@lemmy.zip 11 months ago
In the short run it probably doesn’t matter. However Threads is do big that it could theoretically crush us
MeatsOfRage@lemmy.world 11 months ago
Can someone ELI5 here. So Lemmy.world is a Reddit like site, Threads is a Twitter like site. What does it mean when they’re federated?
Yoz@lemmy.world 11 months ago
Your IP, comments, username , liked post, disliked post and other identifiers will be shared with facebook.
Korne127@lemmy.world 11 months ago
Defederating doesn’t stop that, it just stops that their IP gets shared with us.
misk@sopuli.xyz 11 months ago
With FB and every other instance. Are you vetting who has controlling stake in every instance you federate with?
dan@upvote.au 11 months ago
You do realise that your account on here is public, right? Anyone can collect data like comments, and it’s likely already being used to train AI models just like Reddit data was.
The only way to avoid data being sent to other servers is by having a private account and never interacting with content from other servers. I don’t think it’s even possible to have a private Lemmy account.
TunaLobster@lemmy.world 11 months ago
Content and data is shared between instances.
akilou@sh.itjust.works 11 months ago
But what does that mean? How would I see content from one on the other?
possiblylinux127@lemmy.zip 11 months ago
That’s means that I can see your content from lemmy.zip
GONADS125@lemmy.world 11 months ago
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.
Meta/FB/Instagram also have a strong history of facilitating the spread of misinformation and extremism, which contributed to the January 6th insurrection attempt. [8]
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).
massive_bereavement@kbin.social 11 months ago
Your honor, I would also like to present their role in Myanmar's genocide
GONADS125@lemmy.world 11 months ago
Ah yes, how could I have forgotten!?
They are seriously comic-book villain level evil, and I find it mind-boggling that federation with Threads is even a consideration, let alone the plan…
GONADS125@lemmy.world 11 months ago
I wanted to add that repetition is key in the process with which people are radicalized. It typically involves an individual who is in a vulnerable state (job loss, interpersonal hardship, injury) and the individual is exposed to repeated misinformation/extremism, and this is then reinforced by the radical in-group. [1]
Radicalism spreads through a social contagion effect, and social media (including lemmy and reddit) can act as a catalyst which facilitates the spread of extremism. [1]
This information is covered in this article I published on my blog explaining how people become radicalized. (I have ads turned off and do not benefit in any way from my blog. It’s purpose is to share information.)
I wrote that article partly selfishly to wrap my head around family I have lost to Far-Right radicalism. It is essentially a literature review, and it’s well-cited and thoroughly explains the process of radicalization. I’ll also add that this is in my field of study/career, and I’m working on my Master’s in Clinical Counseling.
It is very relevant here, as the federation with Threads will allow for the extremism permeating Threads to seep into our instance, even if the individual user blocks them. (Remember, blocking Threads won’t stop Threads users’ comments from being displayed here.)
This opens the doorway for vulnerable individuals in our instance to have their rationality chipped away until they lose their self-identity and experience identity fusion with a radical group. [2]
If instances federate with Threads, they are deciding to put their users at risk, and hold culpability in the loss of self-identities, fractured families, extremism, and real-world consequences that could subsequently result from federation with Threads.