932
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Dec 2023
932 points (78.8% liked)
Fediverse
27732 readers
70 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
You don't have privacy in public, that's the difference between public and private. If meta wanted to they could scrape the entirety of the fediverse every weekend without anyone being federated with an instance of theirs. So that isnt a good reason for defederating.
Fear of EEE is a more reasonable argument, but given that it can be done at any point I dont see any reason to do it pre-emptively rather than take a wait and see approach.
I literally said that: "There’s this weird argument that our data is public so privacy violation is okay."
It doesn't matter if it's public, they use their server for data mining and we can prevent that. Someone may collect our data secretely but it doesn't make more open approach to data mining any better or more ethical.
The longer users on your instance interact with content on Threads, the harder it will be to defederate (people will get angy about losing their content and their reach).
My point was that you cant have your privacy violated in public as you don't have privacy in public. That's what being in public means, a place that isnt private. Being federated or not has zero impact on whether Meta can ingest all the public data they like from the fedivese because its all public.