Live data from Hacker News

Blocking Threads won't be enough to protect privacy once they join the Fediverse

privacy.thenexus.today

11–20 of 458 posts

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#11
post #5

What an asinine concern. Don’t want your data on threads? Don’t use threads.

Even if you don't use Threads, when they eventually add ActivityPub support, Mastodon users' data will inevitably be harvested. Instance admins have been signing a pact[1] to defederate with Meta for this reason, in addition to the fact that they don't trust Meta to moderate their instance well enough for it to be safe to federate with.

[1] https://fedipact.online/

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#13
post #11
post #5

What an asinine concern. Don’t want your data on threads? Don’t use threads.

Even if you don't use Threads, when they eventually add ActivityPub support, Mastodon users' data will inevitably be harvested. Instance admins have been signing a pact[1] to defederate with Meta for this reason, in addition to the fact that they don't trust Meta to moderate their instance well enough for it to be safe to federate with. [1] https://fedipact.online/

What stops them from harvesting Mastodon users' data after they're defederated?

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#14
What's the point of joining a decentralized federated platform if you don't want other instances or people to see what you post?

Meta scraping your name and doing other shenanigans is a different subject and obviously bad, but the rest is like complaining joining a public torrent tracker and being mad about leaking your ip address to its peers.

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#15
post #5

What an asinine concern. Don’t want your data on threads? Don’t use threads.

Specifically addressed in the article.

"Even if I only make followers-only posts, which aren't public and can't be boosted, if somebody who's following me replies, any of their followers on Threads will see my account name and instance" and also "If somebody on another instance who follows me boosts one of my public or unlisted posts, people on Threads who are following them may be able to see everything I've said in the post"

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#16

The best way to handle it is to make a "minimum viable" account and do absolutely nothing with it, ever, except login and logout annually. Set up a spam filter to trash every single notice from the company.

Can you help me understand why this is preferable to never joining in the first place? What is the goal? Controlling the entry for my email/auth of choice?

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#17

"Decentralized access for everyone, unless it gets popular enough that somebody actually wants to interop with it" I understand the Meta hate, but joining a very explicitly public and intentionally republishable service and then being unhappy that your data is public and intentionally republishable is bizarre to me.

This reaction has shades of nimbyism: Yes we care about climate change + housing affordability + are in favor of increasing immigration. No we can't have those evil developers building big apartment buildings in my neighborhood! How dare you insinuate these things are related in any way!

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#18
post #11
post #5

What an asinine concern. Don’t want your data on threads? Don’t use threads.

Even if you don't use Threads, when they eventually add ActivityPub support, Mastodon users' data will inevitably be harvested. Instance admins have been signing a pact[1] to defederate with Meta for this reason, in addition to the fact that they don't trust Meta to moderate their instance well enough for it to be safe to federate with. [1] https://fedipact.online/

Thanks. I was going to point out that this was an existing problem in the Fediverse (there are instances that are 'unsafe' because they are either explicitly _for_ hate speech or just don't do enough to moderate it) and that the standard approach is to not federate with those instances, nor with any instance that chooses to federate with them. It's not universally popular (some people don't like the idea of 'guilt by federation') but it's necessary if your goal is to prevent your users from coming into contact with nazis.

Re: Blocking Threads won't be enough to protect privacy once they join the Fediverse

#20

"Decentralized access for everyone, unless it gets popular enough that somebody actually wants to interop with it" I understand the Meta hate, but joining a very explicitly public and intentionally republishable service and then being unhappy that your data is public and intentionally republishable is bizarre to me.

This reaction has shades of nimbyism: Yes we care about climate change + housing affordability + are in favor of increasing immigration. No we can't have those evil developers building big apartment buildings in my neighborhood! How dare you insinuate these things are related in any way!

Just being pedantic, but none of that first sentence is requisite for NIMBYism. I know plenty of NIMBYs who disagree with the first sentence.
Post reply on HN