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).
Uh-huh. Which uses Mozilla’s renderer. So, all those upstream commits in Libewolf’s code base are coming from where, exactly?
bad changes aren’t really happening in the renderer, are they?
No, but Librewolf and Iceweasel and all the other forks are ultimately wholly dependent on Mozilla and Firefox continuing to exist. If Mozilla techbros themselves into imploding entirely and goes bankrupt, for instance, all of those other fork projects are also by association toast.