3 ms·
> I don’t know why decades later after this law came into play, nobody at Mozilla or Chrome teams thought of pushing that as a web standard, it just seems so o
by IshKebab 5y ago
> I don’t know why decades later after this law came into play, nobody at Mozilla or Chrome teams thought of pushing that as a web standard, it just seems so obvious to me: if it’s something every website has to build it over and over again, let’s make it a standard. This way the browser itself could handle it, and so much better
They did. There was the do-not-track header. Of course nobody used it. Sites don't want to make it so you can automatically opt out of cookies. The only way they'll use some standard system that allows that is if the law forces them to.
I did vaguely hear that that may happen. Presumably the bureaucrats that wrote that bit of the GDPR (apparently without consulting anyone who knew anything about the web) do use the web and they must have noticed how annoying it is.
- contravariant 5y agoI think it's pretty clear that whomever wrote the cookie consent law didn't know the first thing about cookies. Though I'm not completely discounting the possibility that ad companies are deliberately obtuse. Why law makers decided people should be warned about the websites storing data client-side with users having full control over the content and who it gets shared with, is something I will never quite understand. Though I do recognise that some of the blame lies with most user-agents storing these cookies indefinitely and sharing them without question, by default, to this day.
- dspillett 5y ago> Though I'm not completely discounting the possibility that ad companies are deliberately obtuse. They are definitely being deliberately obtuse. Nothing in the relevant legislation requires anything like the party of dark patterns we see in many sites, in fact many of the consent forms are not conformant with the legislation at all anyway.
- Nextgrid 5y agoPlease read my other comment in this thread - the vast majority of cookie consent modals aren’t actually compliant with the GDPR. The problem is that there’s been zero enforcement.
- emptysongglass 5y agoIt really doesn't matter. It wasn't written to be enforced at the protocol level and that was its biggest mistake. The amount of life it has extracted from me is worth far more than the abuse of the data.
- Nextgrid 5y ago> Presumably the bureaucrats that wrote that bit of the GDPR (apparently without consulting anyone who knew anything about the web) do use the web and they must have noticed how annoying it is. The GDPR mandates that non-functionally-essential tracking (regardless of whether it’s done via cookies or other means) should be strictly opt-in and the consent process shouldn’t annoy or trick the users into opting in. Pre-ticked checkboxes or making the opt-in button more prominent than the decline button aren’t allowed. The problem is that up until now enforcement has been non-existent. Thankfully this seems to be changing - the Internet Advertising Bureau’s “consent” framework has recently been ruled non-compliant so hopefully there’s going to be some financial pressure (in the form of fines that everyone has been fear-mongering about) to fix this properly.
- IshKebab 5y ago> the consent process shouldn’t annoy or trick the users into opting in. Pre-ticked checkboxes or making the opt-in button more prominent than the decline button aren’t allowed. I wish that was true but the GDPR doesn't actually say that as far as I know. There's official advice to that effect, but it's not written in the law. IIRC it just says it must be a "fee choice" which is way more open to interpretation.