- cross-posted to:
- google@lemmy.world
- technology@lemmy.world
- cross-posted to:
- google@lemmy.world
- technology@lemmy.world
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 understand where you’re coming from. It’s never happened to me, but if a website didn’t work with Firefox, I would just assume it’s a shit site ran by rookies who know nothing, and move on to a different site. I understand most people don’t have that kind of principle though.
It’s not that the site doesn’t work in FF, it’s that casting the stream from that site to a remote TV in the house is only possible in chromium, at least with my current device setup. If I just watch on my computer, I watch in FF.
Ah, you did say that. I’m sorry for my misunderstanding. I’ve never tried that, and you’re the first I’ve seen to mention it. I concede to your argument.
I’m in the slow process of replacing devices with HTPCs then I won’t need to cast anything. Unfortunately computers and time don’t grow on trees.