Live data from Hacker News

uBlock Origin CNAME uncloaking now supports filtering by IP address

github.com

31–40 of 133 posts

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

#31

Earlier quoted context omitted.

What are the implications?

Presumably that adblockers (or rather their users) would object to blocking domains that folks might actually want to load content from. I can’t imagine “domain” is the only signal one could use to identify ads, though. To truly befuddle them you’d make advertisements truly indistinguishable from content. This is not trivial.

Not entirely true. If you lower the quality of your content enough the advertisements are in fact indistinguishable. I often enjoy reading the "chumbox" at the bottom of the news article more than the reporting itself

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

#32

Earlier quoted context omitted.

Before I get too alarmed someone would have to tell me how an adsite.com cookie is being sent to adsite.example.com. This workaround seems to let adsite.com profile me as well as example.com already can, but it loses the ability to correlate my activity across example2.com and example.com with a single cookie. (I guess ad providers have gotten good enough to not need cookies? Like they know my browser window size, in…

Browser profiling has been a thing for at least a decade if I'm not mistaken.

Makes sense. "I am session abcdef12345" always seemed significantly guaranteed to me, but in a world with ad blockers and third-party cookie restrictions, using heuristics is the only way forward.

It's somewhat scary how much information our browsers leak to unknown parties.

(I don't really take sides on this. I use an ad blocker and am very anti-ad, but am impressed when ad companies come up with tech to thwart them. The cat-and-mouse game is entertaining to read about.)

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

#34
post #25

It 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.

Yeah, hence why I started already migrating, slowly.

I have a simple tab organizer extension and some greasemonkey scripts that should work perfectly fine on Firefox without any changes.

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

#36
post #33

It did not hit me yet, but I'm already rewriting my extensions to firefox to switch if Chrome really axes uBO

It's already axed in canary release

I'm still at the "This extension may soon no longer be supported" warning

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

#37
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 full support for same ad lists.

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

#38

It 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.

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

#39
post #17

Earlier 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.

[deleted]

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

#40
post #17

Earlier 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.

Particularly with the reams of evidence that fraud is rampant, both in advertising content and in claimed click/view rates.
Post reply on HN