Well DNT indeed did not made it, but there is global privacy control header that is nowadays required as explicit opt-out mechanism by CCPA and some other states legislation. I always implement support for GPC in my products.
Well DNT indeed did not made it, but there is global privacy control header that is nowadays required as explicit opt-out mechanism by CCPA and some other states legislation. I always implement support for GPC in my products.
Never seen this offered to be set by any browsers, though.
Firefox offers it: https://support.mozilla.org/en-US/kb/global-privacy-control
They don't seem to call it GPC, but their "ask websites not to track" feature now uses it instead of GPC.
I wonder how many websites use that header as part of their fingerprint mechanism.
Yes ok, and Firefox was also the only browser that offered DNT, which is why it pretty much died.
It's the complete opposite. What killed DNT is Microsoft adding it to their browser and set it to true by default, pretending they cared about their users. Doing so, it was not the expression of the users anymore and so web developers ignored it, and so it died.
Sorry, that does seem like a reasonable default. This is the fault of web developers to not respect it, not Microsoft. Nice cope.
It died because companies had no incentive to respect it. The writers of the GDPR could have easily added a single line saying you had to respect the DNT header, but they chose not to.
It's set on by default in "privacy browsers" like Brave or Zen, but off by default in most mainstream ones -- user needs to set it on explicitly via about:config