TechEcho

I mean, it's the same three or four possible fields over and over... can't we just set a default and pass it as a header on every request?

My solution would be to simply ignore all cookies from any new website and only allow once a button has been pressed by the user in the address bar.<p>There is no reason why a website should be able to track from the first second that easily

That was already tried: <a href="https://en.wikipedia.org/wiki/Do_Not_Track" rel="nofollow">https://en.wikipedia.org/wiki/Do_Not_Track</a><p>Most advertisers/tracking companies/websites using such products simply ignored it (due to their fears of revenue loss) and it withered on the vine.

This already exists: <a href="https://en.wikipedia.org/wiki/Do_Not_Track" rel="nofollow">https://en.wikipedia.org/wiki/Do_Not_Track</a><p>Eliminating popups and observing DNT would defeat the primary purpose of cookie popups: to annoy the user and lead them to believe that GDPR et al. are not in their interest.

Would have been useful to include that reuirement in the statute, i.e., a non-interactive method for indicating denial of consent,

I mean, it's the same three or four possible fields over and over... can't we just set a default and pass it as a header on every request?

Would have been useful to include that reuirement in the statute, i.e., a non-interactive method for indicating denial of consent,

Ask HN: Shouldn't Cookie tracking request popups be converted to HTTP Headers?

4 comments

Ask HN: Shouldn't Cookie tracking request popups be converted to HTTP Headers?

4 comments