Hacker News Reader

Sounds like the thing about "ad blocker sabotage" is about replacing the Web Request API with something called declarativeNetRequest. I've been sifting through documentation but have had trouble seeing why this is any kind of a downgrade for ad blockers. Can someone explain?

View on HN

It removes the ability to run custom logic to decide whether a net request should be allowed to go through, switching Chrome to a system like Safari's where you can only declaratively specify what you would like blocked.

While Google claims it is a change they are making for security and performance, a lot of people are worried that it is actually intended to make ad blocking harder.

Reply on news.ycombinator.com