It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO
For those unaware, what is uBO and how would it affect most extensions?
"uBO" is an abbreviation of "uBlock Origin".
uBlock Origin CNAME uncloaking now supports filtering by IP address
51–60 of 133 posts
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#52Is chrome going to block uBO im never up to date on the latest. I do know theyre allowing 3rd party cookies now... so maybe theres a chance
Not updating your browser is also hazardous - much better to switch to FF, and have a browser that gets updates and also fully supports uBO.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#53It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO
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.
Which is fine so long as what they have built into the browser is all you need (and so long as Google does not sabotage those efforts). If ever you might need more such as what uBO offers, though, Brave is also subject to whatever changes Google makes (such as Manifest V3).
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#54Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#55CNAME cloaking? Does this mean an ad site may use a randomly generated subdomain pointing to a wildcard record?
Yes. Ads and analytics providers have started doing this to get around third-party cookie protections.
Randomly generated domains are a major red flag for abuse and malware detection, and seems to have become a rather large part of how the domain industry manage abuse. Domain "credit score" is also something that is used in the email industry to score links and thus spam values. A large part of providing score values is behind security companies that offer their service as a paid services, but as with a lot of this stuff there are a lot of movement to offer it for free similar to spam block lists.
It will be interesting when this kind of technology moves down to browser add-ons.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#56Earlier quoted context omitted.
I always find this development curious. About a decade ago I worked in this space. When someone brought up ad blockers I just said "put the analytics on our main domain. No one is going to block the entire website". The answer I got was "no one would ever do that because of the implications of serving advertising from your main domain". Yet, here we are.
News payers used to all serve their own ads including in house sales and design. Frankly with how key advertising is I don't understand why anyone would out source it.
Advertisers trust other advertisers not to lie but not the content providers. well except Google they trust Google. So you have to use these hella shady and networks that are fly by night and security and privacy nightmares across many domains. Instead of many walled gardens of ads like you're saying.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#57Don't some DNS servers implement something that acts like a server-resolved CNAME, where the admin puts in a record that points to some other DNS name but the client just sees an A (out AAAA) record?
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#58It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO
For those unaware, what is uBO and how would it affect most extensions?
uBO (uBlock Origin) is a popular open source ad blocker. There is a change coming to the way Google Chrome and some other browsers host extensions called manifest v3, which for (stated) security and privacy purposes limits a lot of the functionality that makes ad blockers work the way they do. There are workarounds but they are suboptimal. This has been an ongoing fight for years and there are plenty of accusations that Google is doing this because they want to cripple ad blockers since they make so much money from advertising. Firefox has explicitly stated they will not force these changes on extension developers, and thus a lot of people have been threatening to move to Firefox whenever Google finally makes this change for real.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#59It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO
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.
Re: uBlock Origin CNAME uncloaking now supports filtering by IP address
#60Earlier quoted context omitted.
i used to use ublock origin. i still do, but i used to, too
There must have been some Monty Python... ah you get it.
I believe that is a reference to Mitch Hedberg R.I.P. [1]
[1] - https://www.youtube.com/watch?v=VqHA5CIL0fg [video][10 seconds]