I have recently had to implement some of these banners. Here’s what I learned: click reject.
The way America’s version of the cookie banner law (not sure about EU) works is that cookies are default allowed. They are set before the banner even shows. Rejecting the cookies then sets a cookie that you’d like cookies rejected. The cookies remain, but the banner’s scripts block tracking requests based on those cookies on subsequent requests.
So if a site uses GA and you reject cookies, you still get and keep a GA cookie. But the cookie banner later turns GA’s javascript into “text/plain” so your browser doesn’t execute it. This is what [at least some of] the banners mean by “reject cookies”.
Yes it’s stupid and confusing. Possibly on purpose.
But there is not such thing as a "cookie banner law".
A law that leads to cookie banners -> cookie banner law. We all know exactly what I meant.
But yes on my personal site I solved the problem by not tracking visitors because there’s no need. General traffic numbers are good enough for me.
As an anti-tracking measure, Firefox could put them into a global pool (shared with all other users), then randomly sample from the pool whenever making a request to the offending site.
The effect would be severe breakage for any sites that set unauthorized cookies.
That doesn't say much. Even the GDPR allows for some cookies to be stored without consent.
>Strictly necessary cookies — These cookies are essential for you to browse the website and use its features, such as accessing secure areas of the site. Cookies that allow web shops to hold your items in your cart while you are shopping online are an example of strictly necessary cookies. These cookies will generally be first-party session cookies. While it is not required to obtain consent for these cookies, what they do and why they are necessary should be explained to the user.