Hacker News Reader

Domain-based ad blocking rules cannot be bypassed this way in Chrome if you are running a development build of Adblock Plus (https://adblockplus.org/en/development-builds) on Chrome, which makes use of Chrome's new WebRequest extension API.

View on HN

This troubles me. If ad blocking can not intercept HTTP calls, why even bother hide them?

The point of ad blocking is saving bandwidth and speed up page browsing dramatically.

I am going to block all thirdparty javascript with WebRequet extension API.

The whole reason I block ads is to let me focus on the content of a site, not fifty flashing boxes around it. Bandwidth saving and speed increases are pleasant side effects.

All the Android ad blockers work by modifying the hosts file and null routing ad servers.

Requires rooting and it blocks ads in everything not just the browser.

Not really requires rooting if you have a customized DNS server.

I've always (well, for 5~6 years) used domain-based ad blocking (in Opera) and was quite satisfied. I don't even use prepared filters, so by default I see all ads. I just block annoying/distracting ads and ads on sites I visit frequently. I also don't care about text ads.

Reply on news.ycombinator.com