117
Why just blocking Meta's Threads won't be enough to protect your privacy once they join the fediverse
(privacy.thenexus.today)
this post was submitted on 13 Jul 2023
117 points (98.3% liked)
Technology
4 readers
1 users here now
Talk about anything tech related!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Anyone wanna give the tldr?
There's a cookie in it for ya ๐ช
Even if you and the instance you are using is blocking Threads your information still becomes visible to Threads if someone on an instance that isn't blocking Threads interacts with you. The interaction can come in the form of following, boosting, or mentioning your name.
Then the fear, according of the article, is for hate groups going out of their way to harass vulnerable groups.
And it's worth mentioning that the article has specific cases of that happening already.
They don't even need to go through a middle third party instance, they just have to have a ghost instance that nobody know it belongs to them and this one will federate with everybody else
For example if you go to FMHY federated instances, there is one called evil.social , that could be from Meta or Google or NSA... nobody knows
Threads has an influx of bad actors (right-extremist, anti-LGBT racists and any permutation) who intentionally target vulnerable groups on the FV.
You can't rely on individual blocks, including for the whole Threads "instance". If Threads ends up in a federation, everything else on that federation is now compromised because that's simply how public content works on AP. There's no real way around this without keeping Threads out of federation.
tldr: Its no use.
I dont remember the reason but that was basically it.