Hot Take uBlock Stripped - Dynamic Filtering is available on the webstore

@Jan Willy

Never-Consent isn't Ghostery's own detection engine — it wraps an open-source library originally created by Ghostery/Cliqz and now maintained by DuckDuckGo. But here is the problem, to make it work under Mv3 restrictions it uses an EVAL()-bridge to inject the script into every page into MAIN-WORLD (normally scripts run in ISOLATED-WORLD). When the open source DDG code which now causes to click on REJECT turns bad, you are running it with same rights as the javascript on that page 😱

Edit 1: this former left handed 67 year old forced to write right handed has a different look at solving problems. I think I might found a way to use DDG consent mechanisme in a safe way, stay tuned :cool:

Edit 2: yes found away to implement without using EVAL bridge 🙃 @Jan Willy are you willing to test it after I tested it? (can you send me a PM, so we iron out this in private)?
 
Last edited:
That's not the case for me, but it doesn't matter,it was just an experiment out of curiosity.;):)
Perhaps it has something to do with the spot on the screen where the popup appears. On my laptop it's close to the bottom of the screen. Maybe just outside your screen?

cookie.jpg
 
Perhaps it has something to do with the spot on the screen where the popup appears. On my laptop it's close to the bottom of the screen. Maybe just outside your screen?

View attachment 299494

I assume that this feature of the extension doesn't always work with all websites.
But this is just my guess, and I could be wrong.;)
 
@Sampei.Nihira

I Found the cause, when cookie consent starts it has to wait (max a sec) for the page to render and show the cookie prompt (Cookie Management Platforms sometimes add a delay, so that adblockers using scriptlets inject an anti cookie wall script before the actual cookie prompt script is loaded, making the anti- cookie wall mis the target).

Github version should contain the fix (and a new beta function Jan Willy is testing to implement similar functionality as Ghostery never consent)
 
I now also encountered a situation that I needed to click 3 times before it started.
Same here.
I Found the cause, when cookie consent starts it has to wait (max a sec) for the page to render and show the cookie prompt (Cookie Management Platforms sometimes add a delay, so that adblockers using scriptlets inject an anti cookie wall script before the actual cookie prompt script is loaded, making the anti- cookie wall mis the target).
Ah ha!
 
Is anyone else having an issue with the cosmetic filtering? I can create rules, blocking elements, then if I refresh that same site the elements I just blocked are back. I'm not sure why that's happening, but it seems to be that way on about eight sites now.
When you block elements with a random name or number in it, after refreshing this ad gets a different (generated randomized name). Tell me what website it is (in this thread or PM and I have a look).

This is usually the reason, unless I made a mistake and changed something I should not do (I used a change all to rename something).
 
When you block elements with a random name or number in it, after refreshing this ad gets a different (generated randomized name). Tell me what website it is (in this thread or PM and I have a look).

This is usually the reason, unless I made a mistake and changed something I should not do (I used a change all to rename something).

There are many, but:

https://www.wilderssecurity.com - The cookie notification at the bottom keeps reappearing.
Arizona Sports 98.7: The Local Sports Leader! - div.leaderboard-container

Basically every site I go to. It makes me think that maybe there's a bug?
 
Last edited:
@n8chavez

When you login to Wilders Security it is better to use the cookie-clicker to deal with the consent prompt
1. Select Cookie consent clicker
1787212528782.png

2. Read the explanation popup
1787212552037.png


3. Select the accept button
1787212601011.png

4. Save the consent rule
1787212722255.png

5. Now the accept is automated
1787212800550.png



Because the cookie-consent-clicker waits until page is loaded, there might be delay (cookie-clicker not showing), it is solved in next version.
Also I will try to position the rule creation popup a little higher.
 
@Morro, thanks a lot I will investigate. When other members have websited on which it does not work, please post them when they are privacy sensitive.

@Morro good and bad news,

The good news ING has defenses in place removing stuff third-parties inject on that page. Bad news is that when we would bypass it, you would probably be marked as suspicious (and some banks block your account to defend your money). I had that once when I was on a business trip in a far away country. After three transactions my card was blocked and my employer had to wire in money in the old fashioned way.
 
Last edited:
Some (exiting) news with the help of @Jan Willy 👍👍👍 we managed to get a Ghostery like ¨Never Consent" working. The idea is to enable it for 0, 30 or 60 minuted when you do random surfing.

Rules created with the automate Cookie-consen-clicker have priority over the "never consent" When you want to test it by side loading the version from Github
1787249246704.png


The credits may seem a little weird but Ghostery used the DDG never consent scripts using an EVAL bridge 🤢 to escape from the RESTRICTED WORLD to the MAIN WORLD. Currently I am not willing to use these practices, because using AdGuards innovative approach with large chunks it can be done within the RESTRICTED WORLD also. Never say never (uBO developer also refused to use scriptlets requiring trust but after AdGuard offered to trust imported filter list, the My Filters in UBO Mv2 now also has an option to allow scriptlets requiring trust, same with uBO-lite which should be a permission less Adblocker only using DNR, but now also supports cosmetic filters, procedural filters and scriptlets :-) ).

NB1: Thanks to feedback of @Morro (y)I added an explicit recommendation to not use Never Consent when doing on-line transaction :-)

NB2: I am using same DDG never consent library, but because I am not using the hack saw approach of Ghostery (keeping everything in restricted world), I need to apply additional heuristics: there are around 90 Cookie Management Platforms and in version 8.2.23 we (JW an me) have only confirmed succesful auto-decline/never consent with 10 CMP's, while Ghostery applies 90 and uses annoyances anti-cookie filters, so my guess is that we cover 50% maximum of the websites of Ghostery never consent at the moment.

NB3: I am not striving for 100% coverage, meaning the never consent will always be scriptlet library based and NOT use additional filters. Like 3P-Matrix running in level 3 (easy medium) mode halves the internet attack surface while providing 95% and higher website compability (worry free browsing), this feature is intended to reduce the annoyances of cookie consent while maintaining website functionality.
 
Last edited:
On behalf of Kees I'm honored to present the changelog of the upcoming version 8.3.
- updated filter list
- auto deny/never consent implemented for 25 Cookie Management Platforms (to lower annoyance level for 10/30/60 random surfing)
- automated cookie consent rules for specific websites have prevalence
My contribution was very modest. Kees earnes all the credits. He does an excellent job.
 
Interesting.(y);)
What I'm curious about now with this new version is:
How does the extension behave on more complex websites that use both Consent Cookies + Age Verification?
 
  • Like
Reactions: 7Oz-64