Thijs

@thijs I wonder if that’s even legal (in the EU)

@thomasfuchs It probably is because it’s not a cookie.

@thijs @thomasfuchs The law is specifically about sites "storing information" on a "user's equipment", so yeah, this totally gets around it.

@peterc @thomasfuchs Yup, that’s what you get when you write law to cover implementation rather than effect or intent.

@thijs I dunno, I'm not so bothered by this. When we get IPv6 (ha!) technically your address should also be a GUID of sorts.

@peterc If you’d read a print newspaper, would you want to be required to show ID and have it photocopied by the ad placement company?

@thomasfuchs No, but that's because it's inconvenient. If I paid for it on credit card, it's already theoretically knowable who I am though.

@thijs: 1. Can you file a bug? https://code.google.com/p/chromium/issues/entry?template=Privacy%20issue … 2. I assume you don't see this in Safari (e.g. it's Chrome, and not the ISP)?

@mikewest Chrome only. Not an ISP thing. Also see my other tweets. Sorry, but I’m not interested in filing a bug report for this.

@thijs: Filed http://crbug.com/355541  for you. I'll let you know what I find out.

@thijs can someone from @ChromiumDev or @googlechrome comment on this?

@altryne Already happening: https://twitter.com/mikewest/status/448075223330721792 … / @ChromiumDev @googlechrome

@thijs @altryne: @thijs: In short, it's an unfortunate side-effect of the way we bind requests to UIWebViews. Folks are looking into a fix.

@mikewest Yup, already read through the updated ticket. Thanks for having this looked into.

@thijs Seems like the reason would be to uniquely track the device... maybe to get around DNT? @JohnBristowe

@dermike Hmm… can we get confirmation on that? Doesn’t sound great. +@thijs

@aral @dermike Seehttps://twitter.com/thijs/status/448110361112485888 …