Re:NSA uses Google cookies to pinpoint targets for hacking
by gorhill on Wednesday December 11, 2013 @01:47AM
(#6886293)
> "look to be first parties serving content for the page"
"look to be"? How would javascript code know that?
I measured something, and that is the result of my measurement. People can make an informed decision with proper information. I found that the page served well without all the extra requests that Ghostery and Disconnect allowed.
Given the results, I am quite surprise you would say "look to be first parties serving content for the page".
> "If you go to the Guardian, you're going to be tracked by the Guardian"
Now you focused on the Guardian, how about the two other cases I measured?
I'm sure you don't like the result, but this is what came out when I decided to audit. Your response: You don't think it is a problem. That is settled.
"look to be"? How would javascript code know that?
I measured something, and that is the result of my measurement. People can make an informed decision with proper information. I found that the page served well without all the extra requests that Ghostery and Disconnect allowed.
Given the results, I am quite surprise you would say "look to be first parties serving content for the page".
> "If you go to the Guardian, you're going to be tracked by the Guardian"
* facebook-web-clients.appspot.com * guardian-notifications.appspot.com * related-info-hrd.appspot.com * static-serve.appspot.com * cdnjs.cloudflare.com * ajax.googleapis.com * discussion.guardianapis.com * s.ophan.co.uk
Aside `discussion.guardianapis.com`, others are clearly 3rd-parties.
It's seems my definition of "3rd party" aligns more with that of the EFF: https://www.eff.org/deeplinks/2013/06/third-party-resources-...
Now you focused on the Guardian, how about the two other cases I measured?
I'm sure you don't like the result, but this is what came out when I decided to audit. Your response: You don't think it is a problem. That is settled.