W3C to recommend allowing companies with whom users show an “intention to interact”, like a Facebook login, to track them, weakening “Do Not Track” efforts
Fred B. Campbell Jr / New York Times :
Context & Ripple Effects
Five years after 'Do Not Track' stalled as a standard nobody was forced to honor, the W3C is set to recommend an explicit carve-out: companies with whom a user shows an 'intention to interact' — the canonical example being a Facebook login button — may track that user. That would formalize exactly the social-plugin tracking path browsers later moved to block.
The aftermath in related coverage reads as a rebuke of that compromise: Apple upgraded Safari's fingerprinting and share-button tracking protections in 2018, Google's Chrome team proposed its own anti-fingerprinting controls for marketers in 2019, and by 2021 Protocol was reporting open warfare inside the W3C between browser engineers and companies that depend on tracking.
First-order effects
- Facebook and other social platforms get standards-body cover for their login/share-button tracking, since any user who clicks those widgets has by definition shown an intention to interact.
- Users relying on the Do Not Track signal lose most of its practical meaning — the exception swallows the rule for precisely the third parties, like embedded social buttons, that DNT was meant to reach.
Second-order effects
- Browser vendors are forced to make privacy a product feature rather than wait on the W3C: Apple ships Safari tracking protections aimed squarely at Facebook's buttons and device fingerprinting, and Google follows with its own anti-fingerprinting standard proposals.
- Ad-tech firms and publishers face a fragmented regime where compliance depends on which browser a user runs, pushing measurement toward first-party relationships and away from shared standards.
Third-order effects
- If the pattern holds, web privacy governance migrates from consensus bodies to whoever controls the dominant browsers — the dynamic Protocol documented inside the W3C, where engineers at browser makers now sit across the table from the companies whose revenue depends on tracking.
The trend: Web tracking governance is shifting from stalled W3C compromise toward browser-enforced defaults, with Apple and Chrome dictating what the standard-setters could not.