41–50 of 529 posts
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
I generally wanted web 1.0 simplicity, lots of contrast, but also a soft gentle colours and modern vibe. I also have a general design for use in dashboards/apps etc: https://frost-e.com/design-system/
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
It’s an EU law, but it impacts us all in America as well… because you know, every fucking website
Actually big tech is to blame: https://killthecookiebanner.eu/
Loaded way too fast and is way too responsive. Also when I checked NoScript, it's only loading js from lxe.github.io I expect there to be at minimum 8 domains, but often 12-18.
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
The EU said "you have to ask for permission before forcefully sodomizing your users", and webdevs thought "let's ask for permission" rather than "let's not forcefully sodomize our users". Of course, the law could have said "don't forcefully sodomize users", but it seems the west is still under the impression that some people will do the right thing, just because, sometimes. ( maybe 20 years ago they would have, just…
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
It’s only broken to the extent that it collided with a messed up world where websites track even when they don’t need to and then send that to 2000 partners for more profit extraction on top of what the website does commercially.
Something is deeply fucked up there and it’s not the EU part. They just make a good scapegoat because the banner is what users see
Loaded way too fast and is way too responsive. Also when I checked NoScript, it's only loading js from lxe.github.io I expect there to be at minimum 8 domains, but often 12-18.
The cookie thing, I assume it's EU-only, is an example of the EU policy making process being fundamentally broken in some way. If you create a flawed policy and don't fix it many years after it's very visibly obvious that it's a bad policy, something is really wrong.
it's an example of malicious compliance by some, and herd mentality by others. I had a discussion with my CFO about removing the cookie banner from our website (because we don't set any tracking cookies, and cookies for things like login are exempted) and he said "yeah, but it makes the site seem less legitimate.
One of the best indicators that something was not spam was the unsubscribe button.