The end of uBlock origin for Google Chrome?
ghacks.net
ghacks.net
And before you even begin to complain about it being "too slow", "slower than Chrome", <other statement of the month>, tell us that after you're running Chrome without an ad-blocker.
And even if it really is still slower by some miracle - this is a community containing world-class software engineers. Donate some of your time to bring it up to speed. Pun intended.
If you do decide on using it, I recommend editing the browser so it doesn't display tabs on top, so the tree style tabs is the only place your tabs are located.
I cannot emphasize enough how big an improvement this has been to my browser experience, once I got proffecient with it.
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
That was undeniably true, though ages ago. Probably those thinking along these lines didn't run Firefox for some time.
A ton of code has changed in the two products and since about two years Firefox has filled the gap then surpassed Chrome. And BTW even if Firefox wasn't faster than Chrome (it is), I would happily trade say a 20% loss in speed with a close to 100% gain in privacy.
Sadly they don't seem to have world-class managers
But yeah as a Firefox user it still lags behind safari and chrome for speed. I don’t use Adblock either...
One thing Firefox recently did was overhaul their GPU acceleration code (webrender) - it makes a massive difference in rendering speed and is faster than Chrome in many situations, though it needs to be manually enabled on some machines.
Autofilling. Chrome is just so much better and it's something I have to do a lot for my business. I'm always buying random parts from random places and a lot of them don't have the best-designed forms. Chrome handles them much better. There's just so much friction removed when you don't have to type all your info, especially on a phone, or pull out your credit card. I now have my credit card number memorized thanks to having to do so so much with Firefox. I had the same credit card for years, but with chrome I so rarely had to actually pull it out that I couldn't have told you more than the last 4 digits.
Chrome's built in password management is just better at picking up logins and passwords too when forms aren't designed really well.
I get a lot more performance issues with Firefox. I have to force close it sometimes. Never happened with chrome. It's not super frequent by any means but it happens.
Lot of websites don't work in Firefox and I have to open them in Chrome which is likely not Firefox's fault the majority of the time, just developers not testing in Firefox, but still quite annoying to me.
In addition to the issues above, I noticed terrible battery performance on my laptop and the fans would frequently spin up even with a single tab open.
[0] https://addons.mozilla.org/en-US/firefox/addon/twitch_5/
Two finger pinch zooming on a Macbook stutters enormously in Firefox and is much smoother on Chrome.
I use this feature all the time and it's made switching to Firefox difficult.
Another example:
I'm not a fan at all of how Firefox handles displaying huge amounts of tabs. Tiny arrows to scroll your tabs left and right is really a disorienting nuisance and I much prefer Chrome's system of making tabs smaller. I'm sure there's a way to change this, but I'd rather stay on the default path that they're actively iterating on and improving.
[1] http://hints.macworld.com/article.php?story=2011032210281240...
I run Brave without an adblocker and have found it to be much faster than Firefox (with adblocker and pi-hole).
Also, as someone whose startup has both Chrome and Firefox extensions, I have to say the Firefox reviewers (who review releases and hold up the process — not end user reviewers) can be hugely annoying, and we deploy there as infrequently as possible. As a result, our Firefox customers don’t get all the latest bells and whistles. Wish it weren’t that way, but the process takes months!
Edit: clarified the annoying reviewers are not end users reviewers, but the people who suck up months of time for every minor update, making confused complaints about our code, and even UI implementation.
Maybe, just maybe, they're sick of you because you ignore their platform?
I don't think I could use the modern web without it.
And for the record, I used Firefox for decades, up until last year. I just spend too much time in my browser to use anything other than Brave, given how much time it saves me.
The last sentence of the article starts with words "While it is certainly possible that the stable extension update would be allowed by Google".
I do sometimes just leave the site instead of clicking the single "I Agree" option.
So far, I've not missed any features of Chrome except opening accidentally closed tab again. You might want to change few settings though: "show full urls" and "show favicons".
Apple Pay also works remarkably well, just click "Pay with Apple", and the authentication request pops up on your iPhone, requesting Touch ID / Face ID.
I've not seen anyone implement the new "Sign in with Apple", which automatically generates burner email addresses, but that's another reason to switch to Safari.
Also, one feature which I like is the automatic generation of strong passwords.
I do personally think this lends some plausibility to Google's assertions that they're doing it for performance reasons rather than to make adblockers worse. It's not like Apple's doing it for the ad revenue.
I don’t know that I buy this.
Chrome has a bunch of restrictions that Safari doesn’t, which make ad-blocking in particular impractical.
Safari has, iirc, a hard 100,000 rule limit per blocker rule list. 1Blocker splits itself into 7 such lists to have enough room for all of the rules needed to be effective.
Chrome has a hard global limit of 150,000 across all extensions. Multiple adblock authors have indicated that’s probably too tight.
Safari also lets content blockers reconfigure rules on the fly, so I can add a rule or make an exception for a site as I browse as a user.
Chrome requires the lists to be totally static and pre-approved by reviewers. Change a rule requires resubmitting the extension for reapproval.
All-in-all it looks to me like Chrome’s changes are designed to look like what Safari does on the surface, while actually adding onerous new conditions that effectively cripple the effectiveness and usefulness of adblockers.
shims/redirects some known trackers for their benign versions
rewrites incoming resource on the fly
injects custom javascript
injects/modifies CSS on the fly
Neither Safari, nor manifest v3 allow that.> shims/redirects some known trackers for their benign versions
Well, all content blockers for Safari that I have used block trackers.
> rewrites incoming resource on the fly
Pure interest, may I ask why it's needed?
> injects custom javascript
> injects/modifies CSS on the fly
AFAIK injecting custom JS & CSS is available for Safari extensions, it's just that Safari Content blockers don't have them. (So that you can just only use content blockers, or you can opt-in to enable the ones that also inject JS. 1Blocker uses injected JS/CSS to add custom rules by pointing to DOM elements in-browser.) And that's a good thing(TM) IMO, so that non-technical users can't get faked by malicious extensions that injects malicious scripts.
However, I think most of that debate surrounds Manifest v3 is misleading. I’m not a huge fan of Manifest v3s limitations, but it’s basically the same limitations as Safari as far as I understand, and the justification does make some sense. So I am hoping that things will work out. I don’t know about any other things that would impact adblocking on Chrome.
Personally, I am happy with Firefox on desktop, and Safari on iPhone, and I don’t think there are any threats, perceived or actual, towards adblocking on those platforms.
If Gorhill needed to, some of that extra functionality could be moved out into a separate extension. uBlock has done this before with uBlock Origin Extra[2]. Most of the extra features (eg. remote font blocking) aren't a huge deal, in my opinion.
[1] https://blog.chromium.org/2013/12/keeping-chrome-extensions-...
[2] https://chrome.google.com/webstore/detail/ublock-origin-extr...
I shouldn’t need separate extensions to each block css, JavaScript, fonts, cookies, pixels, etc.
Remote fonts can be used for tracking and fingerprinting (hence why private browsing modes aren’t private).
Am I missing something here?
Isn't it the reverse, local fonts can be used for fingerprinting?
(There are some snags with remote fonts — rendering bugs/exploits — but they're not exactly low hanging fruit anymore)
EDIT: I see what you mean by tracking. If the fonts are loaded with a third party script, this is indeed a problem. If the font files are served by a third party directly (without some intermediate script), this could be remedied with an extension that strips headers. It would obviously run afoul of this only do one thing rule from Google, the company that once attached Google+ to its search results.
It wouldn’t surprise me if it were a hidden vector of some sort, but I haven’t put effort into digging into it.
All and every were very very aware how adblocks can block double digits of their revenue with each new release, and it was considered an issue of existential importance. C-levels had weekly conference calls on dealing with adblocks.
In one of those companies, a senior was calling Google, and was pretty much receiving directions like "you can get around this block if you randomise this part of URL," "next months we will change this and that API, this will give you some breathing room."
Google is well aware of UBO, and for years tried to covertly subvert it.
> Hey all, I'm Simeon, the developer advocate for Chrome extensions. This morning I heard from the review team; they've approved the current draft so next publish should go through. Unfortunately it's the weekend, so most folks are out, but I'm planning to follow up with u/gorhill4 with more details once I have them.
The functionality of the advertising browser is a bundling of functionality as well: one one hand the browser functionality to let the user browse and view what he wants, and on the other hand the functionality that lets advertisements and trackers function on the user's browser willy nilly.
So we have a functionality bundler (Chrome) demanding a lower level unbundler plug-in (uBO) stop bundling it's unbundling features together, while the only reason the latter exists is because of the organised bundling at a higher level...
Even if I am a Firefox user I don't see a sense in using Chrome. The 'features' that Chrome can but Chromium cannot are these that we everyone love:
* DRM * Centralized extension managment
I hope this is a mistake, since I can't imagine browsing the web without uBlock Origin.
I used to use Chromium and Firefox side by side but stopped doing so when they started acting up in this way. When I need to test with Blink I use Vivaldi (which still supports uBlock Origin), Firefox otherwise.