Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Anyone who wasn't able to predict these annoying popups after HTML5 and GDPR, is seriously blind.

Have you read the GDPR, though? Because in no way does it require "cookie consent", incidentally, neither did the previous "cookie law". The consent forms I've seen so far are all willfull misinterpretation, dark patterns, or both.

95% (if not more) of non-shady uses of cookies do not require consent, and thus don't need a consent popup. If you do implement one on your website it means one of several things:

1) You did not actually read or understand when/why you need consent

2) You did read it/don't understand, but are unable to figure out where all the stuff on your site is actually coming from and are thus unsure about the implications

3) You actually need consent (in case you are hosed anyway, you can't predicate usage on consent, so there's 0 motivation for users to ever consent)

4) Your purposely trying to annoy EU residents in hopes they will lobby against GDPR back in the EU

5) You're blindly copying what other people are doing, because thinking is hard.



Ah, I see you've never talked with a legal team.

1. Is there risk?

2. Does adding a consent screen reduce or remove risk?

3. Is the risk reduction from 2 less than the cost?

Congrats, now every website in the world gets a cookie consent screen even if not technically required.


The problem is probably that it’s a European-style law, being read by U.S. lawyers. Those lawyers interpret every word strictly and worry about what the most negative interpretation might mean, and assign risk accordingly. European lawyers know that the spirit and guidelines are what matter, and say “as long as you can plausibly show that you made a good-faith effort to comply with the stated intention of the law, you’re fine.”


See, I'd be with you with this interpretation, were it not for the fact that a solid >70% of consent screens I've seen blatantly violate the GDPR in a number of ways, so if this process is what happened, legal done fucked up.

Not "subtly getting a minor detail wrong", but "doing something that is explicitly mentioned as not allowed" levels of wrong.


Unfortunately I had to read it for my own website, and have applied it properly. But I'm technical and can actually understand it.

But 99% of businesses owners went to full panic mode and went straight to your point 5. "Our website needs such a popup".

Do you think the general public now understand cookies? Of course they don't.

Seemed all pretty obvious to me.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: