Earlier quoted context omitted.
Substack’s dubious practices aren’t as bad as their dubious politics. https://www.theguardian.com/media/2026/feb/07/revealed-how-s...
Thanks for linking to a cookie banner
Dickover. It is called a Dickover.
201–210 of 227 posts
Earlier quoted context omitted.
We wouldn't need a dickover at all if governments didn’t regulate it either.
But then sites could spy fn users without consent.
Instead we are presented with some lukewarm have it both ways BS where the only solution to truly give you safe harbor is present the cookie acknowledgment. Good corporate lawyers will demand the dickover even if you do not use cookies at all just to cover the company’s ass.
Earlier quoted context omitted.
We wouldn't need a dickover at all if governments didn’t regulate it either.
Even with the regulations, we don't need a dickover. The dickover is purely spite from the websites.
No, it’s a legal CYA that provides safe harbor in case you are accused of the behavior. If a law says you need to inform, your lawyers will demand you inform even if zero cookies are used on the site.
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?
Almost! Your options are "yes" and "maybe later"...
(... and "add yet another custom filter to Ublock Origin".)
Earlier quoted context omitted.
>modal I think you mean dickover,sir.
Very accurate terminology for things that are equally as welcome as the developer sending each user a surprise popup pic of their dickover and over again. Each time they visit the website. Ad infinitum.
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…
Did you know that a Substack's author can turn the annoying popup off? Go to dashboard -> settings, and then it's "Enable subscribe prompts on post page" under "Growth." It's the first thing I did. Recommended.
He nailed it. But please increase the font size.
Earlier quoted context omitted.
Even with the regulations, we don't need a dickover. The dickover is purely spite from the websites.
> The dickover is purely spite from the websites. No, it’s a legal CYA that provides safe harbor in case you are accused of the behavior. If a law says you need to inform, your lawyers will demand you inform even if zero cookies are used on the site.
How is not bothering to understand your business, using it as an excuse to hassle your customers in the worst way they have so far conceived and blaming a law that doesn't talk about cookie banners NOT spite?
One of criteria for inclusion into Kagi Small Web [1] is no dickovers. Thanks for naming it properly John. [1] https://kagi.com/smallweb
Could you or someone working on this make it easier to share the original link for a small web post? It’s difficult to the point of making me think you’re trying to force me to share the Kagi version of the url.