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.

  • Knusper@feddit.de
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    There is an HTTP Header, called “Do Not Track”, but unfortunately, it has been broken.
    The idea was that even under legislations that allow assuming users want to be tracked, this header being set by explicit user action would have been clear evidence that this assumption is wrong in this case.

    Unfortunately, Google and Facebook refused to comply outright and with their tracking software running on pretty much all webpages, compliance was never an option for all those webpages.

    And Microsoft killed it off completely, by setting it per default in Internet Explorer. Might sound like a good thing, but it meant that the header could be there, even if that particular user actually fucking loves being tracked, which meant it was pretty much legally void.