3 ms·
As somebody who tried to build code respecting "Do Not Track" preferences, I have to say that feature, while well-intended, is a complete farce. Chrome, Safari
by pwenzel 10y ago
As somebody who tried to build code respecting "Do Not Track" preferences, I have to say that feature, while well-intended, is a complete farce.
Chrome, Safari, Firefox, IE9, IE10, and IE11 all use different APIs for Do Not Track [1], so a front-end developer has to do a lot of extra leg work to check if the user has the preference set.
I find it highly unlikely that most companies would go through the effort of respecting Do Not Track.
[1] https://developer.mozilla.org/en-US/docs/Web/API/Navigator/doNotTrack https://developer.mozilla.org/en-US/docs/Web/API/Navigator/d...
- cpeterso 10y agoWow. I am surprised at how many different ways Firefox, Safari, and IE9/10/11 implement an API as simple as navigator.doNotTrack.
- amelius 10y agoThis almost seems like a case of defective by design.
- minitech 10y agoThe main behaviour is to add the DNT: 1 HTTP header. The JavaScript APIs are just a bonus to perhaps avoid sending unnecessary information. (But yes, it’s still a silly feature, because having to go out of your way at all to respect DNT isn’t really worth it.)