Live data from Hacker News

Cookie Warning Shenanigans Have Got to Stop

troyhunt.com

161–170 of 509 posts

Re: Cookie Warning Shenanigans Have Got to Stop

#161

In The Netherlands the Data Protection Authority announced this month that websites are no longer allowed to block access when people click "NO" in the cookie warning; Clicking 'no' should still allow people to view the website, but without placing any tracking cookies. Source (in Dutch): https://autoriteitpersoonsgegevens.nl/nl/nieuws/websites-moe...

Which doesn’t mean they have to provide access for free, they are most likely allowed to ask a fee for that.

From the same website you link [1]: “Does anyone refuse tracking cookies? Then you still need to give this person access to your website or app, for example after payment.” (google translated)

[1]: https://autoriteitpersoonsgegevens.nl/nl/onderwerpen/interne...

Re: Cookie Warning Shenanigans Have Got to Stop

#162

Is it possible to write a browser extension that has the browser request access to store cookies just like it does for microphone or location access?

You don't need an extension. You set cookies to deny all. Then you look at the list of blocked cookies when you on a website, and you can individually allow cookies on a per domain basis.

Re: Cookie Warning Shenanigans Have Got to Stop

#163
post #145

In The Netherlands the Data Protection Authority announced this month that websites are no longer allowed to block access when people click "NO" in the cookie warning; Clicking 'no' should still allow people to view the website, but without placing any tracking cookies. Source (in Dutch): https://autoriteitpersoonsgegevens.nl/nl/nieuws/websites-moe...

So websites are supposed to just absorb the cost? That seems like a ridiculous stance.

Yes absolutely! Websites need to find revenue models that don’t depend on violating the privacy of their users. That stance makes a lot of sense to me.

Re: Cookie Warning Shenanigans Have Got to Stop

#164
post #145

Earlier quoted context omitted.

So websites are supposed to just absorb the cost? That seems like a ridiculous stance.

Well, saying it's ridiculous isn't an argument. it's expensive and maybe non-viable for many websites. But it's not like all websites need to exist? There was a world wide web before cookies.

>There was a world wide web before cookies.

I like to think of that time as a great time too, but oh man so much we couldn't do.... I get what you're saying generally, but man I'd hate "before cookies" to be the standard.

Re: Cookie Warning Shenanigans Have Got to Stop

#165

This shows utter incompetence and detachment from reality by European legislators. Maybe it seemed like good idea in theory but the only practical significant impact is that browsing the web has become more annoying. Surely there are solutions that don't require a popup on every webpage you visit? For example enforcing no tracking by default for advertising purposes?

How do you remember that a customer has responded to a popup if you don't give them a cookie? Even a cookie as a session identifier.

"Cookies" are mentioned only once in GDPR, in a long list of examples. They're not targeted specifically.

The law talks about information that can be used to identify a person.

So a cookie such as "gdpr_response=ok" has ZERO effect on GDPR compliance.

Re: Cookie Warning Shenanigans Have Got to Stop

#166
post #114

Earlier quoted context omitted.

It kind of feels like Prop 65 here in California. So many things have a 'this could cause cancer' tag that it is ignored 100% of the time, the exact opposite of its intent.

Amusingly I actually just added a ton of Prop 65 warnings to a ton of things because someone got tired of thinking about if it should be applied to every third thing. So now it is on everything .... That was kinda vauge as I don't want to get into specifics as it is job related, but man it was timely ;)

Don't forget to apply a sticker to the roll of stickers themselves. You never really know what's in that adhesive, after all...

Re: Cookie Warning Shenanigans Have Got to Stop

#168

This shows utter incompetence and detachment from reality by European legislators. Maybe it seemed like good idea in theory but the only practical significant impact is that browsing the web has become more annoying. Surely there are solutions that don't require a popup on every webpage you visit? For example enforcing no tracking by default for advertising purposes?

How do you remember that a customer has responded to a popup if you don't give them a cookie? Even a cookie as a session identifier.

You'll need to use fingerprinting and other much more intrusive tracking methods to track the cookie preferences of any user that refuses cookies.

Re: Cookie Warning Shenanigans Have Got to Stop

#169
post #64

Earlier quoted context omitted.

Cookies are data that is placed on the visitor's computer. Tracking pixels are software instructions placed on the visitor's computer. The tracking that is akin "remembering a face" is user agent and ip address tracking. In my mind, a store that uses facial recognition software to track my movement within the store and purchasing habbits is still incredibly creepy and highly invasive of my privacy.

The government has automated license plate readers that do much the same thing. Their justification is, you're in a public place, you have no expectation of privacy. I'm a little more concerned about that. If I don't want to be tracked, I can choose to shop at a different store. But I can't live in a system of underground tunnels.

In Germany, your privacy is protected in public places as well. A German court just recently ordered a German state to turn off an automated license plate reader: http://www.spiegel.de/auto/aktuell/b6-streckenradar-verwaltu... (only available in German)

Re: Cookie Warning Shenanigans Have Got to Stop

#170
post #139
post #133

Earlier quoted context omitted.

How would that solve anything? The comment you are replying to doesn't want to be asked for permission for cookies. The commentor wants all the cookie requests to be accepted automatically.

He's suggesting making the decision once, per-browser, not per-website, whether or not to allow cookies. Then the browser can include this information in the HTTP header, so the website never needs to ask you.

I mean, making the decision per-website is fine as well if that's what you prefer.

Most importantly though a browser can remember you declined cookies.

Post reply on HN