from Hacker News

Web page service workers bypass ad-blockers after Chrome 72 upgrade?

by ikisusi on 2/17/19, 5:38 PM with 51 comments

  • by nicoburns on 2/17/19, 6:38 PM

    It might sound dramatic, but if they do block or cripple ad blockers, then I think that could represent a turning point in Chrome's popularity. Even my non-technical friends use an ad blocker, and it's also one of the best defenses from viruses on the modern web, so people who do family tech support are likely to be pretty proactive in ensuring that the computers they look after are running browsers with ads blocked.
  • by strict9 on 2/17/19, 7:15 PM

    Even if this is chalked up to something inadvertent, it's only a matter of time before it happens for good. Google will likely win this arms race, at least within Chrome.

    The browser from the mega company that gets nearly all revenue from ads will eventually close that hole.

    I switched to Firefox about a year ago in anticipation of this specific change, and haven't missed a thing.

  • by coffekaesque on 2/17/19, 8:03 PM

    In the past few months several services I (used to) use, one of them being paid Spotify, started to crack down on adblockers and anti-adblockers killers. I don't feel this is just a coincidence, together with Chrome changes.

    I'm pretty happy about this as I want the ad companies to start getting desperate and throwing punches. It's like people won't see how bad the situation is until you they get shit almost literally thrown in their faces. Tracking, data collection and malware are too invisible for people to care.

  • by cronix on 2/17/19, 8:50 PM

    It sounds like ad blockers need to work on the os level now and not a browser extension. Just block all requests from the machine to the ips.
  • by verdverm on 2/17/19, 6:46 PM

    DNS based blocking still works :]
  • by greymeister on 2/17/19, 11:56 PM

    Stop. Using. Chrome.
  • by 50656E6973 on 2/17/19, 6:44 PM

    The Twitter thread ends in "submitted a bug report"...this is a feature not a bug, right?