New Update uBLOCK DYNAMIC - (smart and safe) AD BLOCKER

Thread details

LinuxFan58

Level 25
Verified
Top Poster
Well-known
@Mods major update deserves a new thread. Pushed version 11 to the Chrome Web Store (will be available in a few days).


With version 11 a few new feature are added (Ad left over cleaner) and the user interface has a simple and an advanced option. I use the simple version on my wife's laptop. The simple mode is intended for house admins who value security over the occasional empty placeholder on a website (because of the Less is More philosophy of the extension). A lot of blocking capabilities were added, only done in the less-is-more way and done smartly to provide a seamless browsing experience.

1795158634946.png



Differences with other adblockers (which only advanced power users will grasp), it does not require user script permission and drops scriptlets processing raw javascript and long parameters (reason see this post). uBD blocks advertisements and trackers. Your browser stays fast and does this without requiring user script permissions. Secure by default. Want to know what happens behind the scenes of a website. Tick "I am an advanced user" in Options to show the power tools. It brings AdGuard's power with the speed of uBlock Origin Lite. And it adds tools you won't find in other adblockers. Seamless surfing, Ad leftover cleaner, Cookie consent clicker, DNR tracking filter and Fingerprint Inspector.


SEAMLESS SURFING
Seamless surfing tries to click away cookie banners for you and turns on extra anti-tracking filters. It is on from the start. You choose the answer: accept, decline, or accept where it can and decline everywhere else. Inspired by Ghostery's Never-Consent.
1795159098771.png



COOKIE CONSENT CLICKER
Did a cookie prompt slipped through? Click its button once. The extension remembers. Next visit, the cookie prompt is gone. Inspired by Consent-O-Matic and uses the same point and click user interface as the cosmetic element picker.
1795159158351.png



AD LEFTOVER CLEANER
Blocked advertisements can leave empty boxes behind. Ad leftover cleans them with one clock. See what it removed. Undo it, or keep it for that site. Powered by the general hiding rules of EasyList and AdGuard only applied smart per website.
1795159281310.png



COSMETIC ELEMENT PICKER
uBlock Origin's element picker (only with a better explanation at start). Point at anything annoying. Hide empty ad place holders missed by the adblock filters and Ad leftover cleaner.
1795159396189.png



DNR TRACKING FILTER
Decide which third parties a site may load. To help you decide, it shows whether this domain is listed in the DuckDuckGo tracker databas. Block or allow everything third-party from a domain, or only its third-party scripts and frames. One switch shows what is blocked and what is allowed. Inspired by uBlock Origin's Mv2 classic (dynamic filtering) matrix.
1795159477987.png



FINGERPRINT INSPECTOR
See how a site tries to fingerprint you. Block each technique with one click, or pick a level: low breakage risk, medium or all. Inspired by the work of the JShelter project, only applied on-demand per domain to prevent undesired by effects (and keep browsing fast).
1795159525139.png



IMPORT ABP RULES
Paste your own filter rules, up to 5,000. Works with uBlock Origin Lite and AdGuard scriptlets, EXCEPT scriptlets requiring trust, accepting raw javascript or long input parameters (can all be misused). Modelled on AdGuard's user rules (and recently this mechanism was copied by uBOL :-)).
1795159689817.png



What is also new is that uBD now also has rules for popups and popunders and shows a block screen when a popup/popunder is stopped (only once)
1795159828121.png



MANAGE CUSTOM RULES
All the rules created by the power tools in one place: hiding cosmetic elements, cookie clicks, DNR tracking filter and fingerprint blocks. Type a domain to see only its rules.
1795160238987.png


FILTER (BLOCK) LISTS
Only well maintained lists from several sources are used to provide best coverage with lowest website breakage risk and lowest number of rules (less is more). Country lists from AdGuard and EasyList are combined and switch on automatically to match your browser's language (a feature inspired by AG Mv2, but recently also copied by uBOL Mv3 :-) ). Note that uBD combines EL and AG lists, to provide you with the best of both and offers more European language specific filters. The reason for splitting filters (less is more) is to reduce the number of filter rules as much as possible. Add or remove them as you like.

1795172659405.png

Note: language filters are not limited to top 1 million websites, that is why uBD has an English language filter list (this is to advantage of other languages because the base filter is stripped from English language domains, you probably never vist: Less is more!).


ALLOW (WHITE) LIST
Trust a site? Paste its domain. Filtering stops there. Based on AdGuard's allowlist. This used to be an advantage over uBOL (which had seperate cosmetic and DNR and no sciptlets), but recently this mechanism was copied by uBOL Mv3 (uBD is open source and build on uBOL while adding AG functionality and coding standards, see thread on best coding practices)

1795160985160.png



OPTIONS
Clear history, cookies and more at browser startup. When you clear cookies on start and block third-party cookies in your browser, you don´t need to worry about tracking through cookies anymore.
1795161036357.png


As always, I made this extension for myself after I was told to !@#$%^& by uBOL mods and develop my own. It is not intended for average users. The recent additional features were requested by the company who sponsored my next holiday to Easter island (that also caused the mysterious increase up to 9000 users and drop of this extension). When you want to put uBD on you relatives PC's as house admin. Run it with advanced features. Check the websites bookmarked for empty place holder leftovers, use seamless mode in accept, else deny. Remove any leftovers manually with Cosmetic element picker and Cookie consent clicker and disable ¨I am an advanced power user¨ in options.

Open source: GitHub - Kees1958/uBol-stripped: a stripped version of uBO-lite, replacing stripped with AdGuard Mv3 capabilites
3P-licenses: uBol-stripped/THIRD_PARTY_LICENSES.md at main · Kees1958/uBol-stripped
 
Last edited:
You are right on both disputed points.

  • Cookie default: I conflated “privacy-first” with “lowest breakage.” For the house-admin/simple-mode use case you described, recommending blanket Decline was wrong. Accept is the lowest-breakage choice; the mixed mode is the compromise; Decline is for someone knowingly prioritising privacy over compatibility. uBD’s refusal to permit trusted scriptlets also means it cannot safely simulate every site’s rejection state. uBO’s own cookie-notice rules contain numerous trusted-click-element, trusted-set-cookie and trusted storage rules, including an explicit example where site functionality fails unless necessary cookies are accepted. Your compatibility point is well founded.
  • Fingerprint Inspector: You never claimed it made users invisible. You described inspection, per-site blocking and three levels with stated breakage risk. My “mitigation rather than invisibility” sentence corrected a claim you had not made, so I withdraw that criticism.

I still stand by one separate qualification: clearing cookies at startup while blocking third-party cookies substantially reduces persistent cookie tracking, but it does not eliminate all cookie-based or first-party tracking. That wording issue does not justify my incorrect deployment recommendation or the unnecessary fingerprint comment.
Again I did not post it eliminates all cookie based first-party tracking. You have been drinking again

This is what chatgpt answers

1795164291275.png

1795164376413.png
 
Last edited:
Again I did not post it eliminates all cookie based first-party tracking. You have been drinking again This is what chatgpt answers


You did not write that it “eliminates all first-party cookie tracking.” My previous sentence did not attribute those words to you; it expressly presented non-elimination as a separate qualification to the broader “don’t need to worry about tracking through cookies anymore” wording.

The screenshots support low or minimal practical exposure under several assumptions, not absence of cookie tracking. The second screenshot even limits “minimal” to conventional web tracking.

Technically:

  • Clearing cookies at startup removes persistent identifiers at the next startup, but first-party cookies can still track activity during the current session.
  • Blocking third-party cookies does not block first-party cookies.
  • Firefox’s partitioning isolates cross-site cookie jars while deliberately leaving first-party cookies operational, including for analytics (Mozilla).
  • GPC is an opt-out signal, not a cookie blocker; its specification explicitly says it does not address collection or targeting within the same context (W3C).
  • Anti-tracking lists substantially reduce known tracking requests, but they are not a universal guarantee.

So the defensible formulation is: startup cookie clearing, third-party-cookie blocking, partitioning and anti-tracking lists can reduce conventional persistent cookie tracking to a low—arguably minimal—level. That is compatible with your intended practical point. It is not the same as saying there is no remaining cookie-based tracking to consider.

Sources
 
@Bot

And for other forms of tracking uBD offers Fingerprint inspector and DNR tracking filter, features which other Mv3 adblockers don´t have!, but only apply this on website in which you never log in to (because when you login you comply with the websites rules and you make yourself know, making anti-tracking and anti-fingerprinting useless while only breaking stuff)!

Botty also choose to not answer to the practice of other adblockers to silently allow cookies when they can´t block it WITHOUT informing their users NOR go into the risks of needing TRUSTED scriptlets to accomplish deny cookie prompts.
 
@Bot And for other forms of tracking uBD offers Fingerprint inspector and DNR tracking filter, features which other Mv3 adblockers don´t have!, but only apply this on website in which you never log in to (because when you login you comply with the websites rules and you make yourself know, making anti-tracking and anti-fingerprinting useless while only breaking stuff)! Botty also choose to not answer to the practice of other adblockers to silently allow cookies when they can´t block it WITHOUT informing their users NOR go into the risks of needing TRUSTED scriptlets to accomplish deny cookie prompts.


That criticism is fair. I mentioned the trusted scriptlets, but I did not directly address either silent consent choices or the security trade-off.

The evidence shows that this happens on specific sites. The current uBO Cookie Notices list contains, among many rejection/necessary-only rules:

  • a trusted-click-element rule targeting Bloomberg’s “Accept All” button;
  • a consent cookie for ekstrabladet.dk with preferences, statistics and marketing all enabled;
  • other rules that write consent cookies or storage values without displaying the site’s prompt.

Ordinary users are not given a per-site notification saying that the list accepted something for them. The rules are public and can be inspected, but at the point of action, “silent” is a fair description.

One qualification matters: hiding or blocking a cookie banner does not always mean accepting cookies. Some filters merely remove the banner or block its consent-management code. The source proves individual cases of automatic acceptance; it does not establish a universal policy of “if rejection fails, accept everything.”

Why trusted scriptlets matter​


“Trusted” scriptlets are predefined extension functions, not necessarily arbitrary downloaded JavaScript. Nevertheless, they have deliberately powerful capabilities:

  • trusted-click-element can activate a selected page control on the user’s behalf.
  • trusted-set-cookie and trusted storage scriptlets can manufacture a consent state.
  • A stale or overly broad selector can press the wrong control after a website changes.
  • Users must trust both the extension and the maintainers of every privileged list update.

Restricting those scriptlets to trusted built-in lists is a meaningful safeguard, but it does not remove accidental actions or the filter-list supply-chain trust involved. Raw-JavaScript processing would create an even larger capability boundary.

Therefore, uBD refusing trusted, raw-JavaScript and long-parameter rules is a real reduction in attack surface, not merely a marketing distinction. The cost is equally real: uBD cannot reproduce every complicated “necessary only” or rejection state. That is precisely why Accept is the sensible lowest-breakage default, while mixed mode is the privacy/compatibility compromise.

Fingerprinting and logged-in sites​


Your conservative deployment advice is reasonable for Fingerprint Inspector: use its active blocking mainly on sites where the user has no account and test per site, because fingerprint interference can break authentication, payments, media or other functionality.

But logging in does not make all anti-tracking useless. It makes the user known to that first party and allows activity to be linked to the account. It does not make every embedded third-party tracker harmless, nor does it prevent those third parties from linking visits across sites. A login is an identifier, not a magic amnesty for every tracker on the page.

So I would separate the tools:

  • Fingerprint blocking: often limited value against the logged-in service itself and potentially higher breakage—your conservative rule is sensible.
  • DNR third-party control: can remain useful even while logged in, because it can stop unrelated analytics, advertising and embedded tracking domains.

Finally, uBD’s documented combination of a per-site DNR matrix, DuckDuckGo tracker identification and an inspect-then-block fingerprinting interface is certainly unusual among mainstream MV3 ad blockers. I would describe that exact combination as distinctive. “No other MV3 extension has anything similar” is broader than the evidence supports, especially since DNR filtering itself is standard MV3 machinery.

Sources
 
@Bot :)(y)

You got me there: I stand corrected. When I said anti-tracking is useless, I should have made an exclusion for Global privacy Control and blocking third-party cookies and deleting cookies (and other website data) at startup. But that was my assumption when I claimed minimal impact of allowing first party cookies.


About DNR tracking filter, no other adblocker has something similar in terms of transparancy (showing whether a 3P is in the DDG tracker data base) and ease of use (just click on 3P-all or 3P-code to block all third-party or only 3P scripts and frames). Adguard's Mv3 also has a monitor option that shows in detail what attributes are blocked by which rules and what filters AND allows you to construct a block or allow rule, but that is a complex detailed list and it does not tell you it is a known tracker. So I stand corrected AG Mv3 has similar functionality.

1795167680621.png
 
Last edited:
It’s interesting to note that, based on this thread:

What's your favorite Ad Blocker? | Page 5 | MalwareTips

There are some forum members who could try uBlock Dynamic—ad blocker,but probably don’t for specific reasons.:unsure:
Perhaps you’d be interested in knowing what those reasons are.

Here’s the situation:

  • AdGuard AdBlocker (7 users)
  • uBlock Origin Lite (16 users)
  • Ghostery (3 users)
Most of these users,excluding those who use Firefox-based browsers,would, in my opinion, benefit greatly from switching.
 
Hi @LinuxFan58, uBD is so Euro-centric. Can you support Asian language filters (CJKV) pls?
Thanks.
Yes it was first EU+ and 5eyes only, recently added mid en south America. I had added South Korea and Japan, but the filters I selected (EL + AG + filters mentioned as good language filters and available on Github) had some sort of character replacement feature which Google perceived as external code.

..... and for external code the extensions needs ..... user script permissions :-(
Other non-latin language have the same issues. That is a result of first computers being developed in 19th century in UK + US + some EU countries.


Coming weeks I am busy with account management course development, then I will be on holiday. When I come back, I will investigate how much effort it is to create a separate extension which only supports (besides the top 1 million most visited websites) non-latin language (e.g. Arab, Chinese, Cyrillic, Hindi, Japanese, Malay, Vietamese, etc). This 'east' version would require user script permissions, while 'west' version would stick to 'less is more' principle.
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,680 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top