Ask HN: Shouldn't Cookie tracking request popups be converted to HTTP Headers?
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?
6 comments
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.
There is no reason why a website should be able to track from the first second that easily
There is no reason why a website should be able to track from the first second that easily
> There is no reason why a website should be able to track from the first second that easily
There's one big reason for that: The world's most popular browser and search engine both make their money by tracking you from the first second to the last
There's one big reason for that: The world's most popular browser and search engine both make their money by tracking you from the first second to the last
That was already tried: https://en.wikipedia.org/wiki/Do_Not_Track
Most advertisers/tracking companies/websites using such products simply ignored it (due to their fears of revenue loss) and it withered on the vine.
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: https://en.wikipedia.org/wiki/Do_Not_Track
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.
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.
It’s the expected result cause GDPR creators are living under an effing rock. Working in peoples interest and being completely clueless are orthogonal things.
Would have been useful to include that reuirement in the statute, i.e., a non-interactive method for indicating denial of consent,