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:

https://github.com/brave/brave-browser/issues/17846

https://github.com/brave/brave-browser/issues/29986

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

https://github.com/duckduckgo/Android/pull/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.

[ferromint]

@uazo First of all, I very much appreciate and support your considerations for improving the browser in various aspects such as the suppression of cookie banners!

Especially because of this and based on the fact that your initiative of continuing/taking over the development means a lot of work around the maintenance of such a project, I fear that investing time into "baking in" specific technology into the browser

• provides less flexibility / freedom of choice of the most suitable solution for the users than the concept of extensions
• consumes a relevant part of your precious (development) time for tasks already being solved by readily available and stable extensions

For me, extensions are the main reasons why I use Firefox both on Desktop as well as on Android. On Android only FF Nightly has still the full range of extensions installable since the major change in FF Android some years ago. The stable version artificially limited the number of hundreds/thousands to a few and also disabled the about:config page.

Why reinvent the wheel for something which already exists and works?

Don't you think that supporting the installation of extensions would be a much more important feature which immediately makes the browser much more versatile?

[ferromint]

I am puzzled why you suppressed/hid my previous comment from users which are not signed into GitHub, and for those who are, made it harder to see by marking it as off-topic and thereby being collapsed by default.

What is to be considered as off-topic about the fact that existing extensions already solve the problem/task that you want to achieve and are only usable if you enable the support for extensions in the browser in general?

[uazo]

nothing personal, simply would like us to stick to the topic, No intention to offend anyone. Simply I don't feel you have added anything already known to the discussion (and I hate long issues :) OT simply because there is not a more specific item in the "hide" menu. there is another issue about extensions, if you want to write it there, but your position is already clear.

[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