undefined | Better HN

story

0 pointsantisthenes6y ago0 comments

> You can't say use a browser API to set a global setting for them, because GDPR explicitly requires that every website must get the user consent for them.

I can see why that prevents a browser from auto-accepting all cookies, but how in the world does this logic apply to me if I want to deny consent to 100% of the websites to use cookies?

Set the default on the browser to deny all consent, and show the cookie notification somewhere unobtrusive, the same way it was done for notifications.

0 comments

efreak6y ago

The browser already has logic/settings controlling which cookies are accepted (first party, all, none). These settings have existed in most browsers for years. It's unfortunate that the cookie law didn't build on this in some way.

kuschku6y ago

The cookie law is very flexible. It considers any and all ways in which the user makes their intent explicit as good enough.

The issue is that websites want to annoy users until they finally maybe actually say yes to get the site to shut up.

Legally, tracking has to be off by default, tracking may not change the usability of the site, and tracking has to be purely optional, and the "no" has to be simpler, larger, and easier to use than the "yes".

The point of the GDPR, over the course of the next years, is to utterly destroy online advertising as a business model, and any and all tracking solutions with it.

afiori6y ago

I suspect that it would be far to expensive to make it work on the hard 20% of websites and brittle on the easy 80%.

As a personal confession I cannot sympathize for this animosity towards banners. Apps usually have a worse onboarding experience than websites.

My only considerations of GDPR notices is to note how many of them manage to be uncompliant and wonder if archiving services can bypass them.

j / k navigate · click thread line to collapse