Live data from Hacker News

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

privacy.thenexus.today

41–50 of 458 posts

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

#41
post #33

Earlier quoted context omitted.

the only problem is lack of critical thinking and victimization. You're joining a centralized netowrk its pretty obvious.

Isn't ActivityPub specifically about decentralisation?

protocol to centralize decenteralized activity. The blog starts with an issue on facebooks centralization and then goes into issue on centralization on this decentralized network. It's all very stupid imo. Edit sorry for my spelling

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

#42
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…

Isnt this a core way that ActivityPub works though? Like this isn't a Meta issue. It is the technical functionality of the protocol these federated services are built on. If you transmit data using the AP protocol, your content isnt private.

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

#43

"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.

They're not unhappy about their data being intentionally republishable. C'mon. On the contrary, they are saying that when the product gets successful, they will pull the rug. Like facebook did before, and like twitter did with the API and now again.

Even if this happens it won't make any difference to how these instances operate, will it? It'll just reduce traffic to them, right?

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

#44
>Mastodon (and most other fediverse software) wasn't designed with privacy and user safety in mind

this is the real problem. Mastodon and lemmy share way more information than they actually need to (like lemmy shares a list of usernames who upvoted or downvoted a post, not just a count), and if you're using one of those services you should expect that all your data and interactions are public. that's the actual threat here, not the possibility that facebook might suck up that data. Blocking Threads from federating is just a short-term patch over mastodon's bad privacy controls.

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

#45
post #6

Earlier quoted context omitted.

Yeah, this article reads more like a critique of the way ActivityPub and Mastodon work. None of this is particular to Meta.

The odd thing is that even the biggest fedi promoters don't seem to get it. I thought "mastodon.social" was based in Germany, heart of GDPR country but there is no consent theater, no harassment by cookie popups, certainly no controls over data. I really don't mind, but there is some serious cognitive dissonance there.

There's no consent theatre because mastodon isn't doing anything that requires consent under the GDPR.

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

#46
post #6

Earlier quoted context omitted.

Yeah, this article reads more like a critique of the way ActivityPub and Mastodon work. None of this is particular to Meta.

The odd thing is that even the biggest fedi promoters don't seem to get it. I thought "mastodon.social" was based in Germany, heart of GDPR country but there is no consent theater, no harassment by cookie popups, certainly no controls over data. I really don't mind, but there is some serious cognitive dissonance there.

Because almost none of that is actually required if you are not collecting data outside of the actual usage of the application.

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

#47

Hunting down your personal details and publishing them is a crime¹, isn't it? 1 - I mean on the US where Meta really cares about. It's probably one on most countries where Meta has revenue, but that won't send anybody to jail.

The story is almost certainly untrue or a misunderstanding. Facebook has no reason to scrape individuals personal information and then forcefully update their Facebook profile.

There are various processes at Meta that do require identification to be submitted and in some cases that information will be published. For example, to be verified on Instagram you must have your name be published. Likewise, certain Facebook pages must publish their operators identities.

Most likely the person in question submitted their identity documents to Facebook (perhaps their account got locked) and they didn’t realise they were agreeing to that information being put on their profile.

The concern is valid — Facebook has information users might not want public — but the cause isn’t nefarious. Facebook is not finding an anonymous sex workers identity and then intentionally outing them.

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

#48
ActivityPub has a problem of laying all data out, nicely structured, just waiting to be scraped and mined and machine-processed, in perpetuity by default, as if it was something people inherently need when communicating. Is it, though?

It does look like something idealistically-minded early techies would justifiably find really cool.

It may indeed be desirable for, say, Dutch government (and perhaps any government that wants to be transparent).

However, I’d argue it may be from suboptimal to harmful for regular people.

Regular people may have to worry about future governments, which may or may not end up less transparent to hostile towards them, as well as other powerful adversaries. Regular people may want to be careful and value features like transience, privacy, and plausible deniability.

Perhaps we can do better and come up with a protocol that combines openness and those values. Whether Facebook enters the Fediverse with its new product or not, ActivityPub in its current shape and implementation seems to be a liability.

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

#49

If you have personal information you do not wish bad actors to see, do not publish it using an open protocol explicitly designed to allow anyone to read said information. Defederating from Meta as a solution is stupid - Meta can (and will if they actually care enough) just rejoin undercover. Furthermore, when it comes to the fediverse, Meta is actually one of the more trusted actors compared to whatever else is on th…

I think the point they're making is that Meta is in a special place, where by using their unusually vast amounts of personal data and photos, they are somehow (?) going to dox anonymous users by publishing their real names, based on matching their profiles in some way. At least that is the implication based on the quoted tweet right at the top of the post (which is lacking any real detail how exactly Meta got this person's real name matched up with an online alias).

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

#50
This reminds me of the "embrace, extend, extinguish" strategies Microsoft used extensively with Linux and open source software in the 90s. From [1]: "a phrase that the U.S. Department of Justice found that was used internally by Microsoft to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences in order to strongly disadvantage its competitors."

[1] https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extingu...

Post reply on HN