4 ms·
quotemstr was talking about the infrastructure that they control. It's true that they can track visitors server-side if they want to.
by p4bl0 7y ago
quotemstr was talking about the infrastructure that they control. It's true that they can track visitors server-side if they want to.
- jefftk 7y agoWith what WebKit describes here GitHub won't be able to tell the difference between: A: a browser visits both foo.github.io and bar.github.io B: one browser visits foo.github.io, another visits bar.github.io Both should look identical to github.io, client side and server side. (This is not the case today, but my reading of the policy is that they consider all the ways in which it is not the case to need fixing.)
- p4bl0 7y agoWhat about the IP address and the other information that leaks at network levels that are lower in the stack than what the browser controls?
- jefftk 7y agoMany people are behind NATs and so share IPs. This can be millions of people; see Wikipedia's documentation on IP banning: https://en.wikipedia.org/wiki/Wikipedia:Blocking_IP_addresses https://en.wikipedia.org/wiki/Wikipedia:Blocking_IP_addresse... What are you thinking other than IPs? Everything else should be under the browser's control.
- p4bl0 7y agoI don't know. I just suppose that it's not that simple. It is never a good idea to assume something is safe for good. The TTL of the packet could also be used maybe? Also, there are also many people that are not behind a NAT. I've always had a public IP address at home, for example. Plus NAT may become less used because insert rant about NAT and IPv6. Anyway, it's good that browsers make all they can to ensure privacy :).