2 ms·
This is correct. Bad UX with modal popups and very ambiguous/deliberately vague verbose language designed to make you click some ok button are a choice not a le
by jillesvangurp 4y ago
This is correct. Bad UX with modal popups and very ambiguous/deliberately vague verbose language designed to make you click some ok button are a choice not a legal requirement. Being deliberately obnoxious is of course a weird choice if you are trying to actually get people to engage with your website.
The more obnoxious the UX, the less you should trust websites to do the right things when it comes to your privacy and rights. If someone puts a "reject all" button in the cookie thing, I click it on principle. Every time. I go out of my way to find it and click it. The harder websites try to hide that button, the harder I try to find it and click it. It's usually there.
But you have to wade through a lot of bullshit and deal with some offensively stupid UX to get to that button. I'm not going to mico-manage all the various ways you want to sell my data / abuse me. Does anyone actually do that? The engagement on UI like that must be absolutely terrible. What does that say about your brand if you are trying to be deliberately misleading, manipulative, and offensive like that? It's not a good look.
Advertising your web design incompetence and malice/corporate stupidity like that is a choice. A bad and odd choice. But it's a choice. The more visually offensive the cookie experience, the less likely I am to provide consent and the more annoyed I get. It's that simple. Maybe I'm weird. Or maybe lots of people are exactly like me and don't provide consent either. So why even bother with this level of abuse?
I also have an ad blocker (I don't even remember the web before ad blockers), I use firefox containers, and firefox cleans up cookies and blocks trackers really aggressively. So, not only is this stupid. It's also futile.
- Nextgrid 4y agoDark patterns aren't actually a valid approach of complying with the regulation - if you do that, you may as well just track and collect data without consent, because any consent obtained by misleading or annoying the user does not count as valid anyway. Here's what the UK legislation has to say (which is still identical to the EU GDPR as far as I know, though subject to change post-Brexit): https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/lawful-basis-for-processing/consent/ https://ico.org.uk/for-organisations/guide-to-data-protectio... > Consent requires a positive opt-in. Don’t use pre-ticked boxes or any other method of default consent. > Explicit consent requires a very clear and specific statement of consent. > Keep your consent requests separate from other terms and conditions. > Be specific and ‘granular’ so that you get separate consent for separate things. Vague or blanket consent is not enough. > Be clear and concise. > Make it easy for people to withdraw consent and tell them how. > Avoid making consent to processing a precondition of a service.
- pdpi 4y ago> The harder websites try to hide that button, the harder I try to find it and click it. It's usually there. These days, if I can't find it within a few seconds, I just bounce and find some other less obnoxious site to use instead.
- nonethewiser 4y agoI don’t even get that far. I just close websites with cookie banners if I can help it.