181–190 of 227 posts
I usually just toggle Firefox's reading mode whenever a dickover like this pops up and they magically go away, allowing me to continue reading in peace.
I have a theory that about 97% of developers and managers completed the cookie consent (or whatever) on their own product 5 years ago and hence never see it again, and they have no idea how bad the experience for new customers actually is. So the developers and bosses all think they're doing a great job and they've got a carefully curated homepage, even though the regular users get a cloudflare captcha, then a cookie…
Best ones, when refusing, ask again on the next page. Perhaps they don't know what a functional cookie is? Maybe the marketing vocabulary only has YES?
I have a theory that about 97% of developers and managers completed the cookie consent (or whatever) on their own product 5 years ago and hence never see it again, and they have no idea how bad the experience for new customers actually is. So the developers and bosses all think they're doing a great job and they've got a carefully curated homepage, even though the regular users get a cloudflare captcha, then a cookie…
Earlier quoted context omitted.
Best ones, when refusing, ask again on the next page. Perhaps they don't know what a functional cookie is? Maybe the marketing vocabulary only has YES?
REI threw a dickover on top of my checkout page just before I could pay. Dismissing the dickover cleared the checkout page.
Checkout is sacred. Have they not learned from their A/B testing?
Thank you, I got a good laugh out of that. My experience was probably exactly as intended. Click on the "What is a dickover?" link trying to come up with things that it might be. And a brief moment after the page loaded (this little pause is crucial) I am hit in the face with a big annoying popup saying "This is a Dickover" followed by immediate understanding. Now at least I know what to call it the next time I visit…
Earlier quoted context omitted.
Or your company could respect its users and only use cookies for essential site functions. Then you don't need a dickover.
We wouldn't need a dickover at all if governments didn’t regulate it either.
I have a theory that about 97% of developers and managers completed the cookie consent (or whatever) on their own product 5 years ago and hence never see it again, and they have no idea how bad the experience for new customers actually is. So the developers and bosses all think they're doing a great job and they've got a carefully curated homepage, even though the regular users get a cloudflare captcha, then a cookie…
uBlock Origin. Right-click, Block Element, click "Create", done.
Earlier quoted context omitted.
We use a third party cookie consent service. It shows different things depending on your location (and allows disabling different types of cookies depending on your local laws). Lawyers mandate it. It's easier than having to figure out the laws everywhere on our own. To me it shows a banner that stays out of the way. But I couldn't tell you for sure it doesn't cover the whole page to other people.
Have you considered just not violating anyone's privacy? Cookie banners aren't a force of nature. They are required solely because you want to track people. Not tracking people? No need for a cookie banner!
Which ironically are the same tools you’d need to find out if your users are experiencing unintentional dickovers.