81–90 of 265 posts
The banners are required by data privacy legislation and are often dark patterns that make it easy to agree to "all" but usually hide "only necessary" behind a couple additional clicks.
If you don't respect me enough to give me a one-click "only necessary" button, then I'm going out of my way to give you as little data as possible. I already block ads and many trackers at my router.
The more aggressive and dark-UX the banner is, the more likely I am to spend time figuring out how to reject everything or to just close the tab right away. If it doesn't try to trick me into accepting things, I sometimes actually consider doing that. Why don't I just accept them all? No idea. Out of spite? Principles? Because I have too much time? Because my mind is too eager to get distracted with the popup? The fa…
Remarkable how often that works.
>those in charge of the cookie banners really believe that they protect the interests of the user No, they're asking for consent to track because the EU demanded it. The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. They're aggressive because they don't want their data spigot turned off - hence the work-to-rule nonsense. You should not infer any benevolenc…
What if there's back-end only analytics? Does that require a banner?
No need to click anything nor be tracked across the web! I Don't Care About Cookies [0] combined with Cookie AutoDelete [1] will hide all cookie consent popups, deny permission/not click if possible, and auto-accept if required to use the site. IDCAC alone will hide all popups, but in cases where you must click accept to browse it will do so invisibly & the cookies will linger. CAD solves this problem by purging ever…
>those in charge of the cookie banners really believe that they protect the interests of the user No, they're asking for consent to track because the EU demanded it. The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. They're aggressive because they don't want their data spigot turned off - hence the work-to-rule nonsense. You should not infer any benevolenc…
At least in the EU most sites seem to automatically disable nonessential cookies if you don't click Accept. The American equivalents all force you to manually uncheck everything
They have been well-advised by their lawyers. Anything else is just a bomb waiting to explode on you.
Earlier quoted context omitted.
Yep - but to clarify, the cookies must really be NECESSARY - i.e. your site or app would be unusable without the feature they implement. A cookie that saves, for instance, a preference may not be considered essential but a "Functional Cookie" that adds extra features, because your app is usable without it, and then you do need permission for it.
Well, what does unusable mean? If my app offers a feature and the cookie is necessary for it to work, then it's essential. For example, a cart feature in an ecommerce app. Could you shop without a cart? Sure, still I would consider this cookie essential.
>those in charge of the cookie banners really believe that they protect the interests of the user No, they're asking for consent to track because the EU demanded it. The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. They're aggressive because they don't want their data spigot turned off - hence the work-to-rule nonsense. You should not infer any benevolenc…
> The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. What if there's back-end only analytics? Does that require a banner?
>those in charge of the cookie banners really believe that they protect the interests of the user No, they're asking for consent to track because the EU demanded it. The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. They're aggressive because they don't want their data spigot turned off - hence the work-to-rule nonsense. You should not infer any benevolenc…
> The easiest way to avoid having a banner on your site is to... just not have an analytics package on your site. What if there's back-end only analytics? Does that require a banner?
Earlier quoted context omitted.
I use separate and fresh isolated firefox (running within podman container) to make fingerprinting a bit more difficult, it's still fingerprintable and probably this new fingerprint can be easily associated with the other but I like to imagine I make it more difficult to track me. Every little helps :)
Test it here: https://coveryourtracks.eff.org/ its amazing how unique your surfing is :)
Which means that they calculate there are 21x more people that have a $5k XDR display than use macOS Safari. Which seems... unlikely.
(anyway, tracking via IP address is a pretty accurate way to track across browsers and cookie resets, until you're behind a large NAT / proxy.)