Live data from Hacker News

"Localhost tracking" explained. It could cost Meta €32B

zeropartydata.es

121–130 of 286 posts

Re: "Localhost tracking" explained. It could cost Meta €32B

#121

Very impressive but not surprising coming from Meta. They have an history of doing this kind of things. Back in the early 2010s, they found a way to spy on HTTPS traffic on the iOS App Store to monitor which apps were getting popular. That's what allowed them to know WhatsApp and Instagram were good acquisition targets. At this point, I think the race for Zuckerberg is, can Meta survive long enough for the next platf…

> They have an history of doing this kind of things.

They have a history because the punishment has never dissuaded anyone from being repeat offender.

Re: "Localhost tracking" explained. It could cost Meta €32B

#122
If this fine is collected. Will I get the money?

Serious question. I don't generally mind paying taxes and all that. But in this case I feel I am the person offended and I should get some kind of compensation. I'd say €1-2000 would make me feel somewhat compensated.

Re: "Localhost tracking" explained. It could cost Meta €32B

#123

Previous discussion: Covert web-to-app tracking via localhost on Android (341 comments): https://news.ycombinator.com/item?id=44169115

NB. Comment totals may still be increasing as discussion continues

Washington Post's Privacy Tip: Stop Using Chrome, Delete Meta Apps (and Yandex) (328 comments)

https://news.ycombinator.com/item?id=44210689

Meta found 'covertly tracking' Android users through Instagram and Facebook (95 comments)

https://news.ycombinator.com/item?id=44182204

Meta pauses mobile port tracking tech on Android after researchers cry foul (28 comments)

https://news.ycombinator.com/item?id=44175940

Covert web-to-app tracking via localhost on Android (6 comments)

https://news.ycombinator.com/item?id=44169314

Covert Web-to-App Tracking via Localhost on Android (6 comments)

https://news.ycombinator.com/item?id=44169314

Meta and Yandex Spying on Your Android Web Browsing Activity

https://news.ycombinator.com/item?id=44177637

New research highlights privacy abuse involving Meta and Yandex

https://news.ycombinator.com/item?id=44171535

Meta and Yandex exfiltrating tracking data on Android via WebRTC (3 comments)

https://news.ycombinator.com/item?id=44176697

Re: "Localhost tracking" explained. It could cost Meta €32B

#124
This system was designed and implemented by engineers who committed code in a source control system with their name attached, and the changes were requested by product managers in tickets in the ticketing system with their name attached. Those engineers and product managers should be personally liable for an equivalent % of their annual salary as Facebook is liable for a % of its annual revenue.

Re: "Localhost tracking" explained. It could cost Meta €32B

#125

Sounds like you're affected if you have either Facebook or Instagram app installed on an Android phone, you're signed into your account, and you don't have anything set up to block tracking pixels and the like (though that last part I'm not as sure of). Getting through VPNs and incognito mode are the most egregious parts of this offense, though. I think some people are under the impression that's a way to act like yo…

> I think some people are under the impression that's a way to act like you're in total privacy... but it's not. It should be for the average person. VPN and private browsing should be enough for what most people use it for. I don’t think it’s fair to expect people to think that the browser is secretly communicating with apps on their phone, tying all behavior to their identity.

I mean, I think that Google (or Apple) have full visiblity to everything on my Android (or iPhone). Why wouldn't they? Just because they say they don't?

Re: "Localhost tracking" explained. It could cost Meta €32B

#127
post #81

What's funny is that the engineers who implemented this are probably one of us here on HN. I don't think Zuck implemented this himself

AND, whenever you suggest here that engineers should consider the morals or ethics of what they are being asked to work on, you often get lots of push back in the comments. "I just want to work on cool tech! It's my company's problem what they use it for!" and "Hey, I'm just a code monkey, don't blame me! If my manager tells me to build the Torment Nexus, I build the Torment Nexus!"

no https://en.wikipedia.org/wiki/Engineer%27s_Ring for programmers

Re: "Localhost tracking" explained. It could cost Meta €32B

#128

I'm just confused why Meta needed to do this. Isn't fingerprinting good enough to not risk building this? All I can think is they use something like this to prove out their other tracking tech is working (this is the test set effectively). It is obvious that they really have several of these types of tracking technologies so that if one gets found out/patched they can switch it off and say 'look we stopped' all while…

Sociopathic people are running the company. You tell them they can't do something, they take it as a challenge and try to do it without getting caught.

Re: "Localhost tracking" explained. It could cost Meta €32B

#129

This system was designed and implemented by engineers who committed code in a source control system with their name attached, and the changes were requested by product managers in tickets in the ticketing system with their name attached. Those engineers and product managers should be personally liable for an equivalent % of their annual salary as Facebook is liable for a % of its annual revenue.

How would the EU fine American engineers who live and are paid in America?

Re: "Localhost tracking" explained. It could cost Meta €32B

#130

So I am seeing two issues here. 1. Android allows apps to open ports without permissions. And apps to communicate with each other without permissions. 2. The browsers allow random domains to access services on the localhost. Without notifying the user. We have seen vulnerabilities in the past accessing dev services running on localhost. Something should be done there.

There is a proposal to restrict sites from accessing a users' local network without permission: https://github.com/explainers-by-googlers/local-network-acce...
Post reply on HN