Clearly, Google is serious about trying to oust ad blockers from its browser, or at least those extensions with fuller (V2) levels of functionality. One of the crucial twists with V3 is that it prevents the use of remotely hosted code – as a security measure – but this also means ad blockers can’t update their filter lists without going through Google’s review process. What does that mean? Way slower updates for said filters, which hampers the ability of the ad-blocking extension to keep up with the necessary changes to stay effective.
(This isn’t just about browsers, either, as the war on advert dodgers extends to YouTube, too, as we’ve seen in recent months).
At any rate, Google is playing with fire here somewhat – or Firefox, perhaps we should say – as this may be the shove some folks need to get them considering another of the best web browsers out there aside from Chrome. Mozilla, the maker of Firefox, has vowed to maintain support for V2 extensions, while introducing support for V3 alongside to give folks a choice (now there’s a radical idea).
I kinda have to at work. Our classroom computers reset between classes and Chrome is the only browser installed. I might ask IT about that, moving forward, given uBlock getting neutered soon.
when you ask them, don’t only mention ublock, but the privacy aspects of only allowing the browser of the largest data collection fueled ad company
Honestly, our IT peeps aren’t idiots. They’d probably agree with me. It’s admin who make the overall decisions. I might be able to swing “also Firefox” to be included when they inevitably update the repo.