- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
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).
Teams calls for example :( I have chromium on my Debian only for teams.
Teams works in Firefox, I sadly have to use it almost every day interacting with clients who use teams for comms.
One of my company’s customers is a DoD contractor that uses the government version of Teams, which does require Chromium, unfortunately. Or at least, I haven’t found a way to make it work on Firefox yet.
But you can’t turn on camera with Teams on Firefox iirc
idk what to tell you, calls have no sound.
I’ll try again, though.
I’ve not had either of those issues on my laptop, using teams through Firefox. I wonder if there is something else going on there.