Hacker News Reader

Comment by one2know | Hacker News Reader

How does this stop facebook from tracking you? I'm fairly certain that on facebook, google, everyone, etc tracking is largely through processing request logs to gstatic.com or fbcdn.net for example with a referrer header saying what site you are visiting, your source IP and various other things to fingerprint the request.

View on HN

> various other things to fingerprint the request

Isn't this exactly how it prevents FB from tracking you? Those "various other things" that it uses will all be different between different containers. I think the source IP thing is a valid point, which is why other commenters have pointed out that you can force your FB container to connect through a proxy, while your other containers don't.

Timestamps, IP, and user agent are probably enough to reconstruct the user visit. Chrome is now sending a browser generated fingerprint x-client-data to all Google's domains while of course they will be trying to end use of referer header for everyone else. They are shameless and think people are dumb.

Mobile carriers are injecting their own fingerprint headers into outgoing http requests as well if not using https.

TIL about x-client-data. It looks even worse than user-agent, it's completely unique per user.

I think you mean user-agent rather than referer?

I have the same question and I agree. Combination of IP, timestamp, fonts, user-agent, screen-size ... can identify you so only advantage I see is that if you have multiple accounts you could log to all of them. Correct?

Reply on news.ycombinator.com