dickover — a modal panel, popover, or curtain presented by a website or app, deliberately obscuring its own content to frustrate the user with an unwanted, unnecessary, mandatory interaction; e.g. asking the user to accept “cookies”, subscribe to a newsletter, install the website’s mobile app, agree to terms of service, or anything else that the user couldn’t give two shits about.
Cookie questions unfortunately are required by law in the EU so don’t meet Gruber’s own definition.
That said the EU needs to force browser makers to respect a set of more granular “do not tracks” settings and then just read the “necessary/functional/settings/marketing” acceptance from there.
As far as I know (and I’m not 100 % sure), no. You don’t even need to inform users that you use functional cookies. Most likely because these work for the person using your website, not against them (persisting the session, settings, and so on).
Cookie questions unfortunately are required by law in the EU so don’t meet Gruber’s own definition.
That said the EU needs to force browser makers to respect a set of more granular “do not tracks” settings and then just read the “necessary/functional/settings/marketing” acceptance from there.
Meanwhile you can use the Consent-O-Matic extension. You set your preference once and auto applies to the all websites.
Yeah it sort of works.
Cookie banners are not required if all you use are actually necessary cookies instead of sharing data with 395 of your partners.
But functional cookies also need approval, no?
As far as I know (and I’m not 100 % sure), no. You don’t even need to inform users that you use functional cookies. Most likely because these work for the person using your website, not against them (persisting the session, settings, and so on).
I looked it up; you are right. Strictly necessary cookies do not need consent.
The law doesn’t require cookie questions to be dickovers.
No, the dark patterns are terrible.