- Jun 21, 2020
- 363
That particular test, don't work for me anyway. Links that it says aren't blocked, are actually, in fact blocked on other sites and services (real world results)...
Yes, testing ad- and tracker blockers and filterlists works better in a real world scenario. I use for this, tracking sites that are listed on WhoTracks.me - Bringing Transparency to Online TrackingThat particular test, don't work for me anyway. Links that it says aren't blocked, are actually, in fact blocked on other sites and services (real world results)...
This is a good reference for filter lists for use in all user modes:
The explanations about the respective filterlists certainly make it a good reference. However, without intending to sound rude, I have some serious question marks at the combination of it all... Either the user is too paranoid and needs to learn to use/create userscripts and manage as well as host his own dns/firewall server and TOR node on top of it. And that is just the beginning, or the user misunderstood lots of things regarding the purposes of those respective filterlists.This is a good reference for filter lists for use in all user modes:
GitHub - yokoffing/filterlists: Collection of blocklists to fill in the gaps
Collection of blocklists to fill in the gaps. Contribute to yokoffing/filterlists development by creating an account on GitHub.github.com
and it was only offered as a reference, not advice to use every list.The explanations about the respective filterlists certainly make it a good reference.
That's not a big problem for uBO, that can handle this well. On the site GitHub - yokoffing/filterlists: Collection of filters to fill in the gaps you can see that from the list oisd full 85157 rules are not used because they are covered by other lists.And I'm still not referring to the sheer amount of overlap of quite a few of those lists.
From my perspective, Its not about Firefox's ability nor uBlock Origin's ability to be able to handle it. It's more about efficiency vs bandwidth ratio. If that makes any sense, since majority of his filters overlap waay to much.That's not a big problem for uBO, that can handle this well. On the site GitHub - yokoffing/filterlists: Collection of filters to fill in the gaps you can see that from the list oisd full 85157 rules are not used because they are covered by other lists.
View attachment 270296
You sure that's the latest list?For people who belong to or are oriented on the western world I highly recommend next filterlist:
And let's not forget the possibilities of uBO medium - and hard mode. Often more effective than filterlists. But greater chance to break websites.
you can see that from the list oisd full 85157 rules are not used because they are covered by other lists.
There are several versions. See GitHub - Kees1958/W3C_annual_most_used_survey_blocklist: This blocklist is based on published surveys of most used advertising and tracking technologyYou sure that's the latest list?
Mine is version 2022.07.06
I understand. I'm not a fan of so many filterlists. Observing the uBO log has learned me a little bit to choose the most effective filterlists. It depends much of the sites you visit. It's rather subjective.From my perspective, Its not about Firefox's ability nor uBlock Origin's ability to be able to handle it. It's more about efficiency vs bandwidth ratio. If that makes any sense, since majority of his filters overlap waay to much.
Edit: Example from the built-in filters being enabled on both Adguard annoyances+social and Fanboy annoyances, or 1Hosts-Pro and OISD Full (not limited to). While either example serves the same purpose as the filter they are compared with. Plus, it would make it more manageable for the user/admin whether they are on uBlock or other services using hosts file lists (e.g. dns ad blocking). Just my 2cents though.
Thanks. Just updated to the latest with version: 2022.10.27There are several versions. See GitHub - Kees1958/W3C_annual_most_used_survey_blocklist: This blocklist is based on published surveys of most used advertising and tracking technology
Edit: some minutes ago there was an update:
First mentioned site says about the update frequency:
View attachment 270312
Release notes
Mainly just a release with the latest changes to filter lists.
Refer to log.txt to see filters which could not be converted due to MV3 incompatibility. At the moment not all discarded filters are necessarily reported in there
Release notes
Fixed not injecting scriptlets et al. in embedded frames, which could prevent uBOL from properly defusing many cases of anti-blockers.
Side note: In general, anti-blockers should be properly defused when using Optimal filtering mode, as the Complete mode may be more likely to cause detection by anti-blocker mechanisms. If you are using Complete mode and an anti-blocker is triggered, try lowering to Optimal mode, this can be done on a per-site basis from the popup panel.
Refer to log.txt to see filters which could not be converted due to MV3 incompatibility. At the moment not all discarded filters are necessarily reported in there
Release notes
Added support for csp= filters.
Refer to log.txt to see filters which could not be converted due to MV3 incompatibility. At the moment not all discarded filters are necessarily reported in there
Release notes
Refer to log.txt to see filters which could not be converted due to MV3 incompatibility. At the moment not all discarded filters are necessarily reported in there
- Do not merge rules with errors (doing so caused valid rules to be erroneously discarded).
Fixes
- Try to inject scriptlets at onResponseStarted() time
- Harden scriptlet injections
- Might fix "ublock origin not blocking ads in the sidebar of Opera GX while using youtube music", to be confirmed
- Fix improperly detecting ruleset changes re. dynamic URL filtering
- Add new scriptlet: xml-prune
- New cosmetic filter parser using CSSTree library
- Breaking change: filter list authors, please read the commit message
- Add support to report/filter SVG image elements in element picker
- Add original Firefox-authored google-ima shim script
- element-picker: Declare we support both light and dark color-schemes by @emilio
- Redesign document-blocked page
- Make popup panel reflect state of the actual blocked page
- Unescaped escaped commas in regex-based removeparam values
- Fix redundant calls to extract image data
- Extend matches-css() to support any pseudo-element