4 ms·
> Why can't you just have a browser wide setting to accept or deny GDPR in force. Because that's what was tried before GDPR, and it has proven to be a conclusi
by majewsky 4y ago
> Why can't you just have a browser wide setting to accept or deny GDPR in force.
Because that's what was tried before GDPR, and it has proven to be a conclusive failure. https://en.wikipedia.org/wiki/Do_Not_Track https://en.wikipedia.org/wiki/Do_Not_Track
- thiht 4y agoIt’s not the same thing. I’d love something like <meta> tags where the websites declare their cookies, with a standardized set of metadata. We could have a browser native permission system like we have for microphone, camera, geolocation, and the possibility to allow or disallow cookies in a unified way. Blocking the undeclared/disallowed cookies would then be done at the browser level, so there would be no need to trust that the websites actually respect the settings
- fomine3 4y agoYeah it was by Microsoft https://en.wikipedia.org/wiki/P3P https://en.wikipedia.org/wiki/P3P
- extraduder_ire 4y agoI'd like something like an <ad> tag to go along with it, where the contents are sandboxed by the browser separate from the rest of the page. Mainly as a cudgel against sites which are very anti-adblocker.
- wkat4242 4y agoIt was only a failure because it was not mandatory to obey it. GDPR missed a big chance to do that.