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).
We’re going to have a serious problem on our hands soon with compatibility. I’m a software dev and I’m already seeing a few issues here and there where Chrome is being treated as the default expected browser and features don’t work on Firefox.
Firefox doesn’t support a fair few Chrome features because of security and privacy reasons, such as WebHID, WebUSB, etc.
Devs, please stop using those features. I know it’s tempting, but they’re basically bribes to encourage you to sell out to Google. Don’t do it.
It’s basically IE6 and ActiveX all over again.
Most “Chrome-only” web applications I have to use I can get around just by changing my user agent string and everything works fine. I try not to use that stuff when I can, though.
This is my experience. They are just taking your default agent and throwing up a message because they can’t be assed to do minimal testing in FF.
Some of the older stuff is indeed that way, but there are more and more features which Firefox can’t support. Web-based custom keyboard configuration tools, tools to flash phone firmware, and one niche MiniDisc tool all are chrome-only things I’ve had to open Chrome to use
we are really really better off without features that grant any website such deep access to our systems just by a single click, trust me. this is a security nightmare, especially looking at people who don’t understand computers and those who instant allow permissions by reflex.
Yep. Forgot I had to use Chrome on Windows to flash GrapheneOS.
you don’t have to, there’s no need for that. they have a normal flashing tool too
Wait is this real? That’s hilarious
https://grapheneos.org/install/web#prerequisites
Technically it works on Linux, but I didn’t feel like installing a Chromium browser to do it at the time.
I’m very serious about my opinion that we are better off without them. If the feature does not exist, it cannot be activated by a bug in the permission system, and also the lesser technically inclined people won’t allow them by reflex/accident
I’m using Firefox as my only browser. If everything works in Firefox that’s fine for me.
That’s the best advantage of only making websites / web applications for fun (for friend groups, video games, family etc)
Yeah, but that’s my point, not everything works in Firefox now - even though admittedly it’s relatively niche stuff - and my prediction is that if we continue on our current course Firefox will either have to compromise their commitment to privacy and security or will become more and more unusable.
I saw this quote a while back “if you only make code that works in chrome you aren’t a web developer, you are a google developer.”
I just don’t use services that don’t work with Firefox. Easy.
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.