26 karma · joined February 10, 2015
There's been a lot of new tech introduced through Chrome and eventually widely adopted and available everywhere. Without requiring user consent.
QUIC + HTTP/3, WebP, Service Workers / PWAs, WASM, WebRTC, View Transitions API
This feels like just another step of "make this new capability widely available so developers can adopt it if they want."
This one seems to be all on-device local capabilities. Not calling additional APIs or sending data off-device.
Is the argument just around "Don't use 4gb of drive space without asking me first"? What other issues does this introduce?
Practical built-in AI with Gemini Nano in Chrome
So I've started using the browser dev tools to just look over the list of cookies that are sent and stored to my browser even after selecting "Reject All" or whatever the closest option is, in the cookie consent banner.
Turns out I usually still see a flood of marketing and ad related cookies. A few sites I've reported as a bug back to the site owner, with a reponse of "thanks for surfacing this, we'll work on it.."
Curious what other people are noticing. And in general, is cookie consent a real thing, or are these consent banners just part of normal UX now and people include them without really implementing the corresponding app behaviors?
If you don't mind going vintage, this is one I used many years ago, it's for building 3D games similar to DOOM, for DOS. You might need a dos emulator to run it in if your OS is too new to support it. Fun to play with though.