People who press on cookie banners anything except “agree” – why do you do that?
101–110 of 265 posts
Re: People who press on cookie banners anything except “agree” – why do you do that?
#102Earlier quoted context omitted.
>No, they're asking for consent to track because the EU demanded it. Given that you can completely block cookies and other tracking in the browser, why on earth did they bother? I despise bureaucrats writing laws when they don't understand technology.
I despise engineers writing code when they don't understand laws. Yes, we can play the tracker-removal cat-and-mouse game, but that involves a lot of time and effort, projected forever . This battle is going to be won by whoever has the most time and money to waste, and, spoiler alert: it's not the adblock vendors. It's Google. In the specific case of cookies, you need those to authenticate to web services, so you ca…
Re: People who press on cookie banners anything except “agree” – why do you do that?
#103The "privacy banners" have become a clear signal to me that the given web site is (at best) too lazy to fix their site or (at worst) deliberately hostile to my privacy. The banner's presence is an easy up-front filter: I just click away and go to a different site. I usually don't care enough about your content to go through and click off a bunch of switches. Switches that you only have to show because you won't fix y…
Restaurants have strict rules not to serve bad food. There are however no rule against serving bad solutions.
Re: People who press on cookie banners anything except “agree” – why do you do that?
#104Even sites with full-page overlays usually load the actual page behind the overlay, so you can just delete the node if you really want to keep using the site.
Re: People who press on cookie banners anything except “agree” – why do you do that?
#105Re: People who press on cookie banners anything except “agree” – why do you do that?
#106Earlier quoted context omitted.
Essential cookies that are necessary for the website to run do not need a permission from the user. For example, if you want to use cookies to save a selection or a language setting, you don't need to ask for permission.
Yep - but to clarify, the cookies must really be NECESSARY - i.e. your site or app would be unusable without the feature they implement. A cookie that saves, for instance, a preference may not be considered essential but a "Functional Cookie" that adds extra features, because your app is usable without it, and then you do need permission for it.
Now, there was a different directive preceeding the GDPR that tried to address the rampant abuse of cookies for tracking by regulating cookies directly. The intention of that directive was good, but the implementation really bad. I think this is where this distinction comes from. I don't think I've seen a case where someone who was not doing blatantly shady things with cookies got into trouble with that directive, though.
It doesn't have to be obnoxious either - if you have a preferences page, you could add something like "we'll save these preferences in a cookie on your computer, okay?"
Re: People who press on cookie banners anything except “agree” – why do you do that?
#107Earlier quoted context omitted.
At least in the EU most sites seem to automatically disable nonessential cookies if you don't click Accept. The American equivalents all force you to manually uncheck everything
And if someone wrote a browser extension that hides those popups (or makes them scrollable instead of sticky), the user would not need to do anything to reject cookies.
GDPR fundamentally changes the default of whether tracking is allowed to occur or not. If a user browses the web automatically blocking (just deleting/blocking the element, not automatically clicking accept) every consent pop-up, the website is not allowed to track them nor is it allowed to block the user from using the website.
If you had such a browser extension, and if websites were actually conforming to the law, all EU users could browse the web without ever seeing any popup and without ever getting tracked.
Re: People who press on cookie banners anything except “agree” – why do you do that?
#108Earlier quoted context omitted.
Yep - but to clarify, the cookies must really be NECESSARY - i.e. your site or app would be unusable without the feature they implement. A cookie that saves, for instance, a preference may not be considered essential but a "Functional Cookie" that adds extra features, because your app is usable without it, and then you do need permission for it.
Well, what does unusable mean? If my app offers a feature and the cookie is necessary for it to work, then it's essential. For example, a cart feature in an ecommerce app. Could you shop without a cart? Sure, still I would consider this cookie essential.
If you are setting the cookie in direct response to a user initiated action, for functionality, that doesn't require consent.
[1] https://ico.org.uk/for-organisations/guide-to-pecr/guidance-...
Re: People who press on cookie banners anything except “agree” – why do you do that?
#109The more aggressive and dark-UX the banner is, the more likely I am to spend time figuring out how to reject everything or to just close the tab right away. If it doesn't try to trick me into accepting things, I sometimes actually consider doing that. Why don't I just accept them all? No idea. Out of spite? Principles? Because I have too much time? Because my mind is too eager to get distracted with the popup? The fa…
I do right-click -> inspect element and then delete the pop-up element in the browser source viewer thing on chrome. Sometimes I have to find where it says “overflow” and set it to “overflow: visible” or something like that. Remarkable how often that works.
Re: People who press on cookie banners anything except “agree” – why do you do that?
#110https://en.wikipedia.org/wiki/P3P was the standard for this, and was implemented in IE for many years.
However, back then there were no legal consequences to tracking without consent, so no sites bothered providing the metadata; and the support in user agents was dropped.