4 ms·
I'd wager that very few P3P headers used in the wild are an accurate and complete representation of the privacy policy of the site. Most are either deliberately
by eli 15y ago
I'd wager that very few P3P headers used in the wild are an accurate and complete representation of the privacy policy of the site. Most are either deliberately confusing IE (as you put it) or copied from a tutorial by a developer who just needed to fix the damn login button for stupid IE users.
Creating an accurate P3P header that captures the nuances of different ways data can be used is somewhere between difficult and impossible (I've tried).
- cooldeal 15y ago>I'd wager that very few P3P headers used in the wild are an accurate and complete representation of the privacy policy of the site. So now the standard of comparison for Google is shady warez sites that flout every possible standard for maximum gain? I'd wager that there are a lot of exploits that install spyware in the wild. That doesn't excuse Google does it.
- azylman 15y agoAs has already been discussed in numerous places, Google, Facebook, Amazon and even Microsoft have broken P3P implementations in several places. That's hardly "shady warez sites". I love you you jumped straight to that conclusion, though. Shows your biases coming through...
- cooldeal 15y agoBroken implementations are different from intentionally subverted ones. If FB is doing this, they deserve blame too. The argument I was responding to seems to be that P3P is a gentleman's agreement and thus is doomed to fail. However, I expect more from Google than I would from random sites on the internet. So Google flouting a gentleman's agreement is very different from a warez site doing it. After all, you don't expect Google to read your mail in Gmail versus the site admins of warez-mail.com reading your email. Or do you?
- eli 15y agoBut it's a gentleman's agreement between Microsoft and... no one. The user didn't ask to have their cookies blocked and Google certainly didn't ask to be a part of this scheme. It's not really an agreement when only one party has agreed to it.
- eli 15y agoShady warez sites? Huh? P3P as a solution to protecting privacy on the Internet is an utter failure. The whole approach is bogus. I realize this is a judgement call, but I don't view sending bogus P3P headers as bogus. You want your site to work the same in a default Firefox install as in a default IE install and the only way to do that in this case is sending the bogus header.
- ootachi 15y agoWhy are you giving Google, of all companies, a pass because they just "copied from a tutorial"? Google is probably the least deserving company in the entire world of the engineering ignorance defense. Think about it: Google knows enough about the inner workings of IE to create Chrome Frame. How in the world is not knowing enough about how P3P works in IE an excuse?
- eli 15y agoGoogle said it isn't possible to create an accurate P3P header that describes how they use cookies. Having previously tried to parse the standard document, I'm inclined to believe them.
- ceejayoz 15y agoIf that's the case, the responsible course of action is not to send a P3P header at all. Sending a deliberately false one to circumvent third-party cookie restrictions is simply not cool.
- eli 15y agoSure. Though of course that means some functionality will be broken for all IE users with default privacy settings.
- ceejayoz 15y agoSure, but in a fixable manner. I can always turn on third-party cookies if I like. A faked P3P header breaks IE's privacy settings in a nonfixable manner.
- Pheter 15y agoFixable for technical people, sure. Not for the average user. The user who uses the default web browser. The user who uses IE.