How to remove cookie banners? Is it correct to remove them?

[uazo]

But can anything be done?

• check "I don't care about cookies" adblock subscription

[ferromint]

In my main browser (Firefox) I switched from a good extension which was sold to "evil" Avast to a similar one developed by people from the Aarhus University in Denmark:

Consent-O-Matic
https://github.com/cavi-au/Consent-O-Matic/

It works as intended on (subjectively estimated based on my browsing preferences) for ~90% of the websites.

For me this extension/addon is especially important for Firefox as I automatically delete cookies using Cookie AutoDelete when I navigate to a different domain (much stricter than deleting cookies upon closing the browser). Having to click on "reject" or "only strictly necessary cooies" each time I visit the same website over and over again every day would otherwise be an unbearable situation.

[huuhaa]

I'm not a dev, but afaik Brave has now option to block those, didn't find actal pull request butt adding at least some links:

brave/brave-browser#17846

brave/brave-browser#29986

And might not be usable for chromium based browser, but duckduckgo browser also got Cookie prompt management:

duckduckgo/Android#3097

But like said, I'm not a dev so those might be useless & you probably knew about those already...

[uazo]

Consent-O-Matic

is a good solution, I thought it was only possible via javascript.
I was thinking of some alternative that worked directly on cookies, but it is interesting to know that it is possible to group banners types into groups.

@huuhaa Fanboy Annoyances List may already be added, but I saw no difference in my navigation.
Regarding duckduckgo, I will take a look at their code, thanks

[antonok-edm]

In case it's helpful information - EasyList Cookie List (which is contained in Fanboy Annoyances List) primarily uses cosmetic filtering to remove banners. Bromite's adblocker only uses the Chromium subresource filter (see here for more info) which isn't capable of doing any cosmetic filtering.

[uazo]

Bromite's adblocker only uses the Chromium subresource filter (see here for more info) which isn't capable of doing any cosmetic filtering.

about bromite you are right. this browser does support cosmetic filters thanks to the integration of adblock plus.

@huuhaa thanks to the links you put up, I saw that there is a standard promoted by the IAB Transparency and Consent Framework relating to the communication of user consents, and that standard is followed by some (perhaps even all) frameworks relating to web consent management, like:

• google https://support.google.com/admanager/answer/9681920 https://support.google.com/admanager/answer/9461778
• cookiepro https://community.cookiepro.com/s/article/UUID-1e75fb0d-bb79-2af8-cb85-f905d16f1220?language=en_US
• avacy https://docs.avacysolution.com/docs/iab-docs/overview
• consentmanager https://help.consentmanager.net/books/cmp/page/using-the-iab-tcf-in-your-cmp
• comscore https://direct-support.comscore.com/hc/en-us
• cookiebot https://www.cookiebot.com/en/cookie-consent-solution/

just a few that I found.

but the thing I like best is that it is possible, depending on the cmp used, to exploit its API, so:

• cookiepro -> OneTrust.RejectAll();
• avacy -> AVACY.triggerOptOut()
• consentmanager -> __cmp('setConsent', 0);

so theoretically it would be possible to make a userscript which, based on the cmp, would delete the banner when the page loads.

[uazo]

interesting thing: https://groups.google.com/a/chromium.org/g/chromium-dev/c/gXafFNfKQkk/m/OAWL-5tIAgAJ

[mrx23dot]

in Firefox I use https://github.com/OhMyGuus/I-Still-Dont-Care-About-Cookies
it hides more than Consent-O-Matic