Princeton’s Ad-Blocker May Put an End to the Ad-Blocking Arms Race

Re:Princeton’s Ad-Blocker May Put an End to the Ad-Blocking ... by derefr on Friday April 14, 2017 @05:15PM (#14117468)

"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.)

[ Parent | on HN ]

Re:Princeton’s Ad-Blocker May Put an End to the Ad-Blocking ... by the8472 on Friday April 14, 2017 @07:45PM (#14118361)

> where the ad is inline in the response body

That only applies to the HTML, which generally is fairly lightweight. They still load additional images, videos, do XHRs for tracking etc.

[ Parent | on HN ]

Re:Princeton’s Ad-Blocker May Put an End to the Ad-Blocking ... by SomeStupidPoint on Friday April 14, 2017 @05:30PM (#14117594)

You could feed back the visually blocked ads to a system that profiles their HTML/etc and then generates new rules for the first line blocking (which is usually itself a combination of not loading and not rendering).

[ Parent | on HN ]

Re:Princeton’s Ad-Blocker May Put an End to the Ad-Blocking ... by visarga on Friday April 14, 2017 @11:57PM (#14119308)

There's a big chance that the AD blocking AI would consume much more power than the AD scripts and make browsing slower.

[ Parent | on HN ]