"Do Not Track" HTTP header supported by IE, Opera, FF, Safari but not Chrome

Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by rmc on Sunday May 20, 2012 @07:08PM (#4000453)

This is misleading. The important actors in the "who supports Do Not Track" is not browsers but websites. "Browser support" just means "we'll tell the website that you'd rather not be tracked". If every browser sent this header, and every website ignored it, it would be a complete failure.

So what, if any, websites support the "Do Not Track" header?

[ Parent | on HN ]

Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by leocassarani on Sunday May 20, 2012 @07:34PM (#4000529)

Twitter, for one: http://www.theregister.co.uk/2012/05/18/twitter_signs_do_not...

[ Parent | on HN ]

Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by bzbarsky on Monday May 21, 2012 @09:40AM (#4002751)

The key part is not the websites but the services (ads, analytics, etc) that sites use.

For those, quoting from http://donottrack.us/implementations :

3PMobile, AdInsight, AdOcean, AdTruth, AP News Registry, Blue Cava, BlueKai, BrightTag, Chitika, Effective Measure, eXelate, Jumptap, m6d, Mochi Media, TagMan, Tealium, TruEffect, Ensighten, Twitter.

Note absence of Google with their advertiser hat on, as well as Facebook.

[ Parent | on HN ]

Re:"Do Not Track" HTTP header supported by IE, Opera, FF, Sa... by recoiledsnake on Sunday May 20, 2012 @08:43PM (#4000742)

Well, websites are the ones to lose with this, not browsers(except ones with conflict of interest like Google and Microsoft). So websites can say "Hey, a popular browser like Chrome doesn't support it, so why should we?". That's why it's important for all browsers to support it so that there will be more pressure on websites to support it.

[ Parent | on HN ]