"Not loading" doesn't make sense in the case where the ad is inline in the response body (i.e. "part of the site", like Facebook's ads are.) Which is the case where this ad-blocker uniquely shines.

Besides which, the algorithm involved is a computer-vision one, so the ad needs to be rendered before the algorithm can recognize it as an ad.

The best solution here, if you want maximum privacy, would be to use a traditional ad-blocker as a first-line defence, and this algorithm as a second-line, for the ads which make it past regular ad-blocking (and which are therefore probably inline-content ads anyway.)

I agree, it's a limitation of the perceptual blocker, as it needs to `see` the ads to detect them. However, combined with a regular ad blocker to catch the ads that the regular ad blocker missed, it seems like a reasonable solution.

But the whole point of this approach (as I understand it) is that companies may be able to deliver the ads in the same HTTP response as the content, they may render the whole page as a <canvas>, they may go to crazy lengths, but by sitting on top of all of that, this software can still block pixels that look like an ad.

The chrome extension file (.crx) is a zip file (with meta data). Just unzip it and you'll find the files, including the 'utils.js'.