Meta just announced that they are trying to integrate Threads with ActivityPub (Mastodon, Lemmy, etc.). We need to defederate them if we want to avoid them pushing their crap into fediverse.
If you’re a server admin, please defederate Meta’s domain “threads.net”
If you don’t run your own server, please ask your server admin to defederate “threads.net”.
Yeah, because it is all “slippery slope” and paranoia. So what that they federate? How are they going to force developers to implement ads? How will they force their unethical business model on you?
https://mastodon.online/@mastodonmigration/111585528118111249
Zuck has been refining his unethical business model for decades, they aren’t joining activitypub to be a team player.
Is there a way to technically deliver an unbroken user experience to a thread user without privacy issues?
Not really that I can think of, which is why I don’t think anyone should federate with them. I agree it’s instance operator and users choice but I feel like the default shouldn’t be “sign your privacy away, block them if you want to have privacy again (which you likely already lost some of from being federated with them)”
deleted by creator
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.
deleted by creator
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.