Earlier quoted context omitted.
It's not if. It's when. It has been 'when' since 2020. It is coming. It is not going to not come. It will be here in mere releases. Get ready.
You're probably right, but FWIW it's not unheard of for google to announce, continually delay, and eventually completely backtrack on things like this, like third party cookie deprecation.
uBlock Origin CNAME uncloaking now supports filtering by IP address
71–80 of 133 posts
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#72Earlier quoted context omitted.
I am switching family over to Brave. They don’t even notice the difference and I’m more confident the browser will continue to support user centric content filtering.
Is that going to help? Brave is still blink. They might have some filtering baked in but I’m not sure if it’s as powerful (or can be) as UBO.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#73As an example of what CNAME cloaking is, let's say that a SAAS provider A wants to provide you, company Q, with fancy ad tracking software. In the olden days, they'd tell you to embed a script at e.g. https://A-ads-tracking.example into your website at address https://q-company.example To block those ads, blocklists that uBlock Origin use have rules then that say "block requests being made to the domain name A-ads-tr…
And this is a good reason to block all JavaScript in unlock advanced and slowly whitelist the scripts you see until the site works properly. Slow and error prone but once you get used to it it's a breeze. And you're completely immune to this sort of shittery.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#74This a good example of why manifest v3 sucks. By definition, it can't do anything like this...no live code hueristics are possible. It's a war of escalation with advertisers. Google is the arms dealer to both sides. They won't give you what you would need to win.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#75Earlier quoted context omitted.
You're probably right, but FWIW it's not unheard of for google to announce, continually delay, and eventually completely backtrack on things like this, like third party cookie deprecation.
This time it affects their bottom line in a profound way so wishful thinking is probably not going to work unfortunately.
Something around 8% of total digital ad spend.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#76This a good example of why manifest v3 sucks. By definition, it can't do anything like this...no live code hueristics are possible. It's a war of escalation with advertisers. Google is the arms dealer to both sides. They won't give you what you would need to win.
Technically manifest v3 has nothing to do with APIs that the browser makes available to extensions. On firefox manifest v3 is supported with blocking web request[1], which is the filtering api prior to "manifest v3". Therefore the statement that it certain functionality "by definition" is false.
[1] https://blog.mozilla.org/addons/2022/05/18/manifest-v3-in-fi...
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#77uBlock Origin is what makes Firefox even greater and definitely one big reason I use Firefox over Chrome etc. It make the Internet browsable.
I moved many years ago to this combo, and never saw a single reason to switch away. Same for android phone, the only usable mobile web experience I've seen. Those few sites over a decade that had some display issues had issues also under chrome. Plus I personally consider ads a cancer of modern society. White and not so white lies, manipulation... nothing respectable regardless (or because ) of tremendous money circu…
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#78Earlier quoted context omitted.
Is that going to help? Brave is still blink. They might have some filtering baked in but I’m not sure if it’s as powerful (or can be) as UBO.
Brave will keep Manifest V2 compatibility as long as they can, specifically focusing on "AdGuard AdBlocker, NoScript, uBlock Origin, and uMatrix". https://brave.com/blog/brave-shields-manifest-v3/
I think Firefox is the only viable solution to continue using UBO at this point.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#79CNAME cloaking? Does this mean an ad site may use a randomly generated subdomain pointing to a wildcard record?
That's part of it. Normally when you visit contentsite.com which serves ads from adsite.com. Adblocker rules can just block adsite.com and the ads won't be shown. CNAME cloaking would have the main site have a subdomain like adsite.contentsite.com point to adsite.com, now the adblockers have the impossible task of blocking millions of subdomains that seemingly belong to legit sites, this also allows the legit sites t…
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#80This a good example of why manifest v3 sucks. By definition, it can't do anything like this...no live code hueristics are possible. It's a war of escalation with advertisers. Google is the arms dealer to both sides. They won't give you what you would need to win.
>This a good example of why manifest v3 sucks. By definition, it can't do anything like this... Technically manifest v3 has nothing to do with APIs that the browser makes available to extensions. On firefox manifest v3 is supported with blocking web request[1], which is the filtering api prior to "manifest v3". Therefore the statement that it certain functionality "by definition" is false. [1] https://blog.mozilla.or…