Click. Ugh. Another one.
You know the drill. You land on a new website, eager to read an article or check a product price, and before the page even finishes loading, it appears: the dreaded cookie banner. A pop-up, a slide-in, a full-screen overlay demanding you “Accept All,” “Manage Preferences,” or navigate a labyrinth of toggles designed by a corporate lawyer.
But what about the small blogger, the local restaurant, or the indie developer? For them, it’s another technical and legal headache, forcing them to install clunky, site-slowing plugins just to avoid a potential lawsuit.
As a small time developer, just no. Why would I be installing spyware on my small websites and importing a ton of third-party shit instead of doing things the right way from the beginning? Imagine tracking people to the extreme that you’ve got to resort to fucking popups and having that kind of web property tied to your name.
tyler@programming.dev 5 days ago
Who the fuck would do this when there’s a “Reject All” button right there. Like, if a contract allows you to opt out of something you should pretty much always do it.
cmnybo@discuss.tchncs.de 5 days ago
Or just install Consent-O-Matic. By default, it’s set to automatically reject all cookies.
undefined@lemmy.hogru.ch 5 days ago
The Reject All button is only there in jurisdictions that require it.
tyler@programming.dev 4 days ago
Not in any case I’ve ever seen. The reject all button started showing up for US users immediately after GDPR was passed and it’s only gotten more prevalent since then. Trying to figure out a person’s location is pointless cause they could be using a VPN and that won’t absolve you from following the law.