This might be just EU thing, but is there an effective way to deal with endless “accept/reject cookies” dialogues?
Regardless of the politics behind, I think we can all agree that current state of practice around these dialogues is …just awful.
Basically every site seems to use some sort of common middleware to create the actual dialogue and it’s rare case when they are actually useful and user friendly — or at least not trying to “get you”. At least for me, this leads to being more likely to look for “reject all” or even leave, even if my actual general preference is not that. I’ve just seen too many of them where clicking anything but “accept all” will lead to some sort of visual punishment.
Moreover, the fact that the dialogues are often once per domain, and by definition per-device and per-browser, they are just … darn … everywhere, all the frickin’ time.
Question: What strategy have you developed over time to deal with these annoying flies? Just “accept all” muscle memory? Plugins? Using just one site (lemmy.world, obviously) and nothing else? Something better?
Bonus, question (technical take): is there a perspective that this could be dealt on browser technical level? To me it smells like the kind of problem that could be solved in a similar way like language – ie. via HTTP headers that come from browser preferences.
The dialogues are not primarily about cookie consent but consent handling personal data. With that in mind, my primary concern is not giving that consent unnecessarily. I’m not interested in any personalized tracking when they could do enough usage statistic without consent and without sharing personal data with other parties. (That’s why I won’t use browser extensions that simply accept everything with the primary purpose of the consent dialogs not showing up.)
Consent-O-Matic is a browser extension that will decline any consent as far as possible.
It doesn’t work on every website but that’s better than auto-accepting - because I don’t want to give consent.
Sometimes, when the barrier is not too high, I use decline all or open choices and save (verifying defaults are off). Depends on what it is though; often times it’s not worth it to me to invest just to read their content. (Especially when it’s regurgitated from other sources.)
If I can’t use a website without consenting to personalized tracking I leave.
Another alternative is using alternate frontends to websites/services or the web archive.
My general view is that any service they could want to provide would be able to be served without consent requests. Ads can be served without personalized tracking (and can still be contextual to content). Visitor and usage tracking/stats can be done in a way without sharing that information to third parties and without individual user tracking. Legitimate interest and handling data to service (according to terms/contract) do not need consent. So really, there is no need for any consent.
/edit: I will be trying out ublock origin’s hiding and reading up on Firefox automatic rejection mentioned in other comments. I expect them to behave better than the Consent-O-Matic delay of it going through all settings.