Thread · 3 tweets · 8 Oct 2020

As a rule, one thing that worries me with that type of “give the user power” proposal is that it ends up being “make the user do the work.” It’s like Chrome’s same-site cookies idea: you can go delete tracking cookies and log-in ones. Cool but: who does that?

Put differently: how do you avoid that becoming AdChoices in the browser? One value I see is that, with machine-readable consent info, you could automate consent removal and have the browser withdraw consent for you on a regular basis by calling all those .well-knowns.

But then… why not do that sooner and signal that withdrawal at the source? :)