GDPR requires you to request consent for any cookies the “could” be used to identify you, which makes them personal information.
So if you want to use cookies to link a user’s sessions on your own website together (without actually identifying them) so every request doesn’t look like a totally anonymous, opaque request, then you must show a cookie banner.
You could (presumably) do this through browser fingerprinting and not require consent (since you don’t actually enrich/link the browser fingerprint to be become user data) but you need a cookie banner if you do it with a cookie.
I’m thinking of the opposite of a DNT header. Websites would be very happy to respect it because it’s like auto-accepting a cookie banner. You would need to manage your own cookies.
Most entrepreneurs believe that visibility over how your visitors are using your website is “strictly necessary” for running a functional/secure/performant website and surviving as a business, but GDPR disagrees. Hence, cookie banners everywhere.
Not deemed “strictly necessary” > “Statistics cookies — Also known as “performance cookies,” these cookies collect information about how you use a website, like which pages you visited and which links you clicked on. None of this information can be used to identify you. It is all aggregated and, therefore, anonymized. Their sole purpose is to improve website functions.”
> attempt by companies to make people associate cookie popups with GDPR
I think GDPR is generally good for individuals and the internet but if someone hates cookie banners, isn’t it fair to place the blame on GDPR?
Why can’t websites accept a special header which automatically accepts all cookies? I would enable it and handle clearing/retaining cookies myself through a browser feature/extension.
I share your optimism, but I think a lot of the OP’s concern here is in response to a generic non-medical LLM “passing” a medical exam. In that case I think it is fair to compare it to a medical “colleague”, at least for now.
I had serious neck problems for years then one change almost completely relieved them: going from multiple monitors to a single monitor. The horizontal neck swivel motion is very nasty.
Yes that slows the rate of change, but the rate of change adjusts based on the times (and hopefully it’s reasonably optimal but that would be hard to measure objectively because it’s a complicated risk-vs-reward, explore-vs-exploit trade-off). Eg Historical revolutions usually saw rapid changes in many areas like politics, art, culture, technology. Societies (like organisms and ecosystems) are extremely complicated so there are serious risks to evolving too fast so slow isn’t automatically bad.
Do simple hello-world HTML pages render ok? I found that rendering was slow-ish but totally acceptable for reasonably heavy HTML pages, so long as we weren't flooding page re-renders (eg by using React without any optimisation of render calls)