3 ms·
I think this is a good analogy and I agree that the intent of the law was not to force websites to have a cookie banner, it was just the side effect. What I th
by onel 3y ago
I think this is a good analogy and I agree that the intent of the law was not to force websites to have a cookie banner, it was just the side effect.
What I think we are missing is a browser option/API that lets the user choose the acceptable tracking level. Similar to the do not track header but more fine grained.
As we are missing that, extensions are doing a good job ATM
https://chromewebstore.google.com/detail/consent-o-matic/mdjildafknihdffpkfmmpnpoiajfjnjd?pli=1 https://chromewebstore.google.com/detail/consent-o-matic/mdj...
https://addons.mozilla.org/ro/firefox/addon/consent-o-matic/ https://addons.mozilla.org/ro/firefox/addon/consent-o-matic/
I found pretty late about Consent-o matic and it saved me a ton of time handling banners. It's exactly what we should have built-in the browser.
- bmicraft 3y agoWe have that, it's called DNT. Unfortunately companies argue that: - it's not really a user choice when some browsers set it by default and therefore ignore it - it's set globally for a browser but a user might want to give away their privacy to my specific site ... and show the banner anyway