Live data from Hacker News

uBlock Origin CNAME uncloaking now supports filtering by IP address

github.com

111–120 of 133 posts

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#111

Earlier quoted context omitted.

For those unaware, what is uBO and how would it affect most extensions?

Maybe it’s a telling sign of the new wave of HN users, but I’m genuinely surprised to read that you don’t know what uBlock is..

I'm happy youngsters still use this ol' forum

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#112
post #4

The title seems to be wrong, uBlock Origin supported it for many years at this point (only on Firefox). This seems to be a refactor of that code, not a whole new feature.

It sounds to me like more than just a refactor, it now allows blocking based on ip earlier, before the request is actually made. Although, that isn't perfect because it doesn't know which ip address the browser will choose if there are multiple ips for a single domain.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#113
post #3

Earlier quoted context omitted.

Yes. Ads and analytics providers have started doing this to get around third-party cookie protections.

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.

Well, it's just a question of priorities. What do you care about more, security on your site, or getting your ads past ad-blockers?

I'm not surprised there are people who prioritize the latter, especially for small sites where they may not have someone who fully understands the risks.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#114
post #63

Earlier quoted context omitted.

I run all the time with first-party cookies disabled. Most of the web works. Anything that does not, and I care about, gets blessed. The only content I allow by default, even in low-security browser profiles, and even from first-party domains, are HTML, CSS, and images. I consider the occasional broken page to be a successful test of my configuration. If I care, I adjust permissions.

What do you use to enforce this? Is it something that's going to break with Manifest V3?

I use uMatrix. On Firefox, so no current concerns about MV3.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#115

Earlier quoted context omitted.

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]

Thank you for providing the video length, it is the factor that made me click.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#116
post #73

Earlier quoted context omitted.

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.

Is there a public list of known legit, whitelisted scripts?

None that I'm aware of but I've not looked either.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#117
post #35

What is the uBI status on Brave, Edge and Opera?

I don't care about the two proprietary browsers you've mentioned, but Brave is going to (partially) support manifest v2 and maintain uBO compatibility for as long as they're able to: https://brave.com/blog/brave-shields-manifest-v3/ Not that you really need it as Brave has its own very capable built-in ad blocker with -- last time I checked -- higher performance than uBO (since it's compiled into native code) and ful…

and brave/shield supports CNAME uncloaking

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#118
post #78

Earlier quoted context omitted.

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 guess I'm curious what "as long as they can" actually means. If it means they can't pull upstream Blink without losing v2 support, that's bad. I think Firefox is the only viable solution to continue using UBO at this point.

I seem to recall they said as long as it was technically AND economically feasible. It depends on how much google attempts to spread the cancer of mv3 throughout their code base. Eventually brave won’t have the manpower to hack v2 in is the likely result without going bankrupt if google really wants to go down that path.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#119

Earlier quoted context omitted.

Maybe it’s a telling sign of the new wave of HN users, but I’m genuinely surprised to read that you don’t know what uBlock is..

I'm happy youngsters still use this ol' forum

It’s good that we are still getting Youngbloods who see the superiority of text in communications rather than one sided talking head videos.

Re: uBlock Origin CNAME uncloaking now supports filtering by IP address

#120

uBlock Origin is what makes Firefox even greater and definitely one big reason I use Firefox over Chrome etc. It make the Internet browsable.

Honestly I’ve used brave and Firefox and don’t see a huge difference. I still prefer Firefox though because of its philosophy and status as coming from a nonprofit. Brave is a quality project too though, and is my back up, although sometimes I throw Vivaldi in the mix because of its windows splitting and much superior tab management.
Post reply on HN