The whole concept of DNT is just stupid. It's misleading users and won't work. By telling users you have better privacy simply because your browser adds a random header tag onto requests you're misleading them. Sites have no obligation to obey it and it will give users a false sense of security. We already have proven, well defined method of DNT already: private browsing. This works by simply removing resources after…
IE10's 'Do-Not-Track' Default Dies Quick Death
11–20 of 67 posts
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#12Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#13Turning on DNT by default is a great way to ensure it will be utterly ignored. So I quite support the requirement that people explicitly enable it. Remember the DNT is voluntary - but if everyone does it by default, then there is nothing left to track, so websites will have no interest in paying attention to the flag.
Isn't that the whole point? Websites may not have interest in tracking disabling policies, but a lot of people do. Maybe these advertising companies ought to incentivize users to opt-in to sell their data instead of the other way around.
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#14The whole concept of DNT is just stupid. It's misleading users and won't work. By telling users you have better privacy simply because your browser adds a random header tag onto requests you're misleading them. Sites have no obligation to obey it and it will give users a false sense of security. We already have proven, well defined method of DNT already: private browsing. This works by simply removing resources after…
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#15The whole concept of DNT is just stupid. It's misleading users and won't work. By telling users you have better privacy simply because your browser adds a random header tag onto requests you're misleading them. Sites have no obligation to obey it and it will give users a false sense of security. We already have proven, well defined method of DNT already: private browsing. This works by simply removing resources after…
> Sites have no obligation to obey it and it will give users a false sense of security. Until appropriate legislation comes into play. It worked reasonably well with the Do Not Call lists.
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#16Turning on DNT by default is a great way to ensure it will be utterly ignored. So I quite support the requirement that people explicitly enable it. Remember the DNT is voluntary - but if everyone does it by default, then there is nothing left to track, so websites will have no interest in paying attention to the flag.
> then there is nothing left to track Isn't that the whole point? Websites may not have interest in tracking disabling policies, but a lot of people do. Maybe these advertising companies ought to incentivize users to opt-in to sell their data instead of the other way around.
I can see Google fully implementing DNT on the basis that users don't care, and for the few that do they're happy to comply
But making it default to on, especially if no one gives a damn is the death knell to the whole business model
Suddenly you have to pay for everything.
Although I would be interested in using DNT if out had more granular control to block certain entities
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#17The whole concept of DNT is just stupid. It's misleading users and won't work. By telling users you have better privacy simply because your browser adds a random header tag onto requests you're misleading them. Sites have no obligation to obey it and it will give users a false sense of security. We already have proven, well defined method of DNT already: private browsing. This works by simply removing resources after…
> Sites have no obligation to obey it and it will give users a false sense of security. Until appropriate legislation comes into play. It worked reasonably well with the Do Not Call lists.
Catching up is a matter of when, not if.
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#18Web developers might hate it, but DNT could be potentially good for end-users who want to make privacy claims. It's just one extra header. A few extra bytes. Meanwhile things like XML and JSON, which add considerable bloat to web responses, are accepted without any complaint.
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#19Turning on DNT by default is a great way to ensure it will be utterly ignored. So I quite support the requirement that people explicitly enable it. Remember the DNT is voluntary - but if everyone does it by default, then there is nothing left to track, so websites will have no interest in paying attention to the flag.
> then there is nothing left to track Isn't that the whole point? Websites may not have interest in tracking disabling policies, but a lot of people do. Maybe these advertising companies ought to incentivize users to opt-in to sell their data instead of the other way around.
Re: IE10's 'Do-Not-Track' Default Dies Quick Death
#20Now imagine if Chrome made incognito browsing the default and you had to access a submenu to get a cookie keeper. Disrupt the web!