Google Chrome disables uBlock Origin for some in Manifest v3 rollout
-
What issues do people even have with firefox? Its a browser, it seems fast enough. Isn't that all most people need from a browser
Security and sandboxing are important, weak points on the android implementation.
-
Would you happen to know whether this is something that a UserAgent spoofer would suffice to get around?
At one particular point it was, if I recall correctly, though Chrome also (mis)implements some standards its own way, so Google might also use that as a form of attack against anyone who implements them properly, much like Microsoft did in the bad old IE6 days...
It's all a silly arms race, though, with Google coming up with new ways to enshittify the web for anyone not using Chrome or using ad blockers and Mozilla and ad blocker (and alternative YouTube frontend) developers trying to figure out what they broke this time and how to fix it, so what worked yesterday might not work today and work again tomorrow.
It's all a profoundly stupid waste of everyone's time and resources (all for a few more ad views) which will hopefully end up with Google losing their monopoly position on the web like the Internet Explorer bullshit did for Microsoft, but will keep being a major hassle for everyone until it does.
-
Main reason I don't is cuz:
Avoid Gecko-based browsers like Firefox as they're currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn't have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox's sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn't happening for their Android browser yet.
This only applies to android, not desktop use, and you couldn’t use uBlock on mobile chrome anyway so it is simply not relevant.
-
This post did not contain any content.
What is everyone's thoughts on duckduckgo browser? I'm on grapheme os and have always used Firefox on my desktop
-
30+ years!
.....fuck off, '94 wasn't 30.... counts on fingers several times
.....Shit.....
I know... Jurassic Park is 33 years this year. It would be like watching a movie from the 60' when it was released.
We're old, friend.
-
Main reason I don't is cuz:
Avoid Gecko-based browsers like Firefox as they're currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn't have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox's sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn't happening for their Android browser yet.
I use Firefox as my main browser on Android, and all apps that invoke a WebView do so using Firefox's rendering engine, with uBlock Origin and Dark Reader working seamlessly. So, maybe this info about Firefox for Android lacking WebView support is outdated?
Exemple after clicking a link on Twitter/X:
-
They're developed separately. It's a hard fork so I consider them different.
Man I haven’t been around that long but I feel like some of my knowledge is outdated and I have to start with “a long time ago in a galaxy far far away” because I stopped paying attention
-
They're developed separately. It's a hard fork so I consider them different.
That's also hugely in part because Apple develops Webkit at a snails pace. Some say they gimp their own rendring engine so that it isn't competitive with native applications from the App Store. This way, there's less incentive for developers to make web-apps to avoid the 30% app store tax.
-
Security and sandboxing are important, weak points on the android implementation.
would Vivaldi on android be better? I really like having extensions on my browser and that's the only other android one I know of that has them.
Edit: I was wrong apparently Vivaldi does not support extensions on mobile which is a bummer.
-
I'm one of those complaining about the UI. Used the TabMixPlus extension to adjust the UI to my liking. FF killed it. So, I started customizing the UI CSS. Every few versions, Mozilla changed the browser enough to invalidate my changes. After a while, I got tired of thiz and switched to Vivaldi, which is Chromium based.
Honestly I'm probably heading to Vivaldi after reading a lot of these things.
-
This only applies to android, not desktop use, and you couldn’t use uBlock on mobile chrome anyway so it is simply not relevant.
Other security implications are stilp valid.
-
Chrome? A browser that's easily replaceable with any other browser? Huh... Didn't see that one coming.
/S
I'm saying this as a 2 year convert Firefox user: mostly easily replaceable. Sure, I can browse pretty much every page that I can on chrome. However, a few sites don't work the same way - sometimes because of the site's conscious decision, sometimes because of Firefox.
Take Facebook, for example. On desktop, I can't make voice calls anymore from the desktop site. For a while it was possible with non encrypted chats, but now pretty much all of them are encrypted, and FF is not compatible with that. I also can't watch h265 videos in my chats anymore. I'm still sticking with FF, but I just can't easily say that FF is just as good for everything (I'm still not going back to chrome).
-
Other security implications are stilp valid.
They're completely irrelevant to the average person.
If you want absolute perfection then sure, stick with Chrome but implying Firefox on GrapheneOS is insecure is misinformation.
-
What is everyone's thoughts on duckduckgo browser? I'm on grapheme os and have always used Firefox on my desktop
duckduckgo browser is based on Chromium (as nearly every other "alternative" browser is) and therefore will use Manifest v3 and neuter uBlock.
-
No horizontal tab grouping. Tab groups on Chrome are perfect, and the Firefox tab extensions all suck in comparison.
That said, I'm still using Firefox today because the internet is unusable without a good ad blocker.
I still use the full screen tab groups feature that they removed from the core. I don't like scrolling tabs, so I can just hit a button and click on the exact tab I want. I do probably have too many tabs open tbh.
-
I'm saying this as a 2 year convert Firefox user: mostly easily replaceable. Sure, I can browse pretty much every page that I can on chrome. However, a few sites don't work the same way - sometimes because of the site's conscious decision, sometimes because of Firefox.
Take Facebook, for example. On desktop, I can't make voice calls anymore from the desktop site. For a while it was possible with non encrypted chats, but now pretty much all of them are encrypted, and FF is not compatible with that. I also can't watch h265 videos in my chats anymore. I'm still sticking with FF, but I just can't easily say that FF is just as good for everything (I'm still not going back to chrome).
Yeah I'm a 20-some year FF user and when it started you had to have IE as a backup because not everything was compatible. In the late 2000s through late 2010s everything worked everywhere, then with chromes dominance places have stopped testing or supporting certain things in FF and it feels like history is repeating itself. Unfortunately you need a chromium-based backup realistically for certain sites, but 99.5% of things work totally fine in FF.
-
I use Firefox as my main browser on Android, and all apps that invoke a WebView do so using Firefox's rendering engine, with uBlock Origin and Dark Reader working seamlessly. So, maybe this info about Firefox for Android lacking WebView support is outdated?
Exemple after clicking a link on Twitter/X:
That's not a webview, it's a separate api with fewer abilities. Custom tabs I believe.
You can see for example that it always opens as a fullscreen overlay in your app and that it always has that bottom or in your case top bar. -
Yeah I'm a 20-some year FF user and when it started you had to have IE as a backup because not everything was compatible. In the late 2000s through late 2010s everything worked everywhere, then with chromes dominance places have stopped testing or supporting certain things in FF and it feels like history is repeating itself. Unfortunately you need a chromium-based backup realistically for certain sites, but 99.5% of things work totally fine in FF.
A lot of websites are broken on Firefox which is a shame. I can’t even scroll down on some news sites. What a shame…
-
This post did not contain any content.
I switched to Firefox the morning they disabled uBlock Origin.
-
Mainly that Google intentionally makes its sites (like YouTube or Google Docs) slower and less useable when they detect you're using Firefox, and/or ad blockers (which you need Firefox to use, so same difference).
It's mostly fixable with add-ons and userscripts (and eventually, one hopes, with an antitrust lawsuit), but it's still a hassle.
Unfortunately, with the FTC rolling back net neutrality protections, I don’t see an antitrust lawsuit happening, or succeeding, anytime soon
