Difference between revisions of "Do Not Track"

From IDESG Wiki
Jump to: navigation, search
(Solutions)
(Problem)
 
Line 8: Line 8:
 
The W3C is dominated by commercial interests that have blocked standardization of this well-known, and well-regarded (non)standard.
 
The W3C is dominated by commercial interests that have blocked standardization of this well-known, and well-regarded (non)standard.
  
==Solutions==* [https://globalprivacycontrol.org/#faq Global Privacy Control]
+
==Solutions==
 +
* [https://globalprivacycontrol.org/#faq Global Privacy Control]
 
* [https://transcend.io/blog/ccpa-gpc-update CCPA update: Businesses must immediately support the Global Privacy Control (GPC) signal] 2021-07-21
 
* [https://transcend.io/blog/ccpa-gpc-update CCPA update: Businesses must immediately support the Global Privacy Control (GPC) signal] 2021-07-21
  

Latest revision as of 01:16, 4 August 2021

Full Title

Tracking Preference Expression (DNT) W3C Candidate Recommendation (2017-10-19)

Context

The Abstract from the standard states it best:

This specification defines the DNT request header field as an HTTP mechanism for expressing a user's preference regarding tracking, an HTML DOM property to make that expression readable by scripts, and APIs that allow scripts to register exceptions granted by the user. It also defines mechanisms for sites to communicate whether and how they honor a received preference, including well-known resources for retrieving preflight tracking status, a media type for representing tracking status information, and the Tk response header field for confirming tracking status.

Problem

The W3C is dominated by commercial interests that have blocked standardization of this well-known, and well-regarded (non)standard.

Solutions

REFERENCES

More information about Do Not Track can be found at these links: