News for hackers. Stuff that matters.

A comment on Cookie Warning Shenanigans Have Got to Stop. Parent comment

Re:Cookie Warning Shenanigans Have Got to Stop by scrollaway on Wednesday March 13, 2019 @04:14PM (#19383263)
"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.

[ Parent | on HN ]
Re:Cookie Warning Shenanigans Have Got to Stop by joemi on Wednesday March 13, 2019 @04:55PM (#19383655)
> So a cookie such as "gdpr_response=ok" has ZERO effect on GDPR compliance.

I wouldn't be so certain about that. Before now, most people were pretty certain that an accept/decline warning was enough and that they had the right to refuse service to people who did not click OK on the warning.

[ Parent | on HN ]
Re:Cookie Warning Shenanigans Have Got to Stop by gnud on Wednesday March 13, 2019 @05:38PM (#19384133)
If anyone believed that, they did not research more than 10 minutes.

This comes up in _every_ discussion about GDPR.

I honestly worry - are we as developers just extra stupid, or are other occupations (electricians, ship captains, architects) equally lax when it comes to reading and following regulations?

[ Parent | on HN ]
Re:Cookie Warning Shenanigans Have Got to Stop by kd5bjo on Thursday March 14, 2019 @04:03AM (#19387286)
Those other occupations have been regulated for a long time, so the training and verification practices have had time to mature. This is still the early days of software development regulation, so there's not much history or tradition to fall back on -- I'm pretty sure that all the other industries had similar problems when their first regulations were enacted.
[ Parent | on HN ]