Look, we're having a good time on Firefox since November 9, 2004. Come join us!
I never went back to Firefox after they killed the Pimpzilla theme.
Chrome is looking to permanently drop MV2 extension
331–340 of 480 posts
Re: Chrome is looking to permanently drop MV2 extension
#332Why are people on HN still using Chrome? (or Edge, or Opera…)
uBlock Origin Lite works perfectly, so I have no complaints?
It doesn't protect from important tracking cases and will eventually allow ads, as the advertisers adjust: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
Re: Chrome is looking to permanently drop MV2 extension
#333PM of Orion here. Orion ( https://orionbrowser.com ) is a WebKit-based browser for Mac, Linux, iPadOS and iOS that supports both Chrome and Firefox extensions natively ⟩ including uBlock Origin. We have no plans to drop extension support. Content blocking is a feature, not a loophole, and we think users should have full control over what runs in their browser.
[flagged]
Re: Chrome is looking to permanently drop MV2 extension
#334Earlier quoted context omitted.
How many extensions do you use on laggy FF?
Not using many extensions on my case, but Google meet remains unusable for a long time, sound is horrible during meetings. Chrome on the other hand works fine
So use Chrome for Google services
and Firefox for everything else?
Re: Chrome is looking to permanently drop MV2 extension
#335Look, we're having a good time on Firefox since November 9, 2004. Come join us!
Firefox did similar 10 years ago when they discontinued XPCOM and XUL
Re: Chrome is looking to permanently drop MV2 extension
#336Earlier quoted context omitted.
This isn't the gotcha you think it is. Every time I try Vivaldi I am right back at Firefox and I am surely not alone. I have never understood the obsession with tree style tabs or vertical tabs. I don't need to customise my browser at all and I like supporting engine diversity.
The motivation for vertical tabs is pretty straightforward, screens are mostly wider than they are tall, browsers are often used in fullscreen mode, yet much of the web does not use much of the screen's width. So it's a better use of screen space to put tabs on the side than on top.
[dead]
Re: Chrome is looking to permanently drop MV2 extension
#337Earlier quoted context omitted.
I use Firefox mobile pretty much exclusively. I haven't noticed any meaningful performance difference between it & Chrome. It also seems to perform fine on my Fedora laptop.
Mobile is different. I rarely even use mobile. I do however use a lot of tabs on desktop, and Firefox is found very wanting in the performance department. I don't even think its about number of tabs. Just yesterday and today, Mullvad browser takes minutes to load a set of about 7 pinned tabs (with no other tabs) on startup, whereas Helium (which is based on Chromium) loads in a second or two close to a hundred tabs.
My Firefox currently has 33 tabs open (way more than usual). It opens in seconds on my 9 year old i7-7700k desktop.
Re: Chrome is looking to permanently drop MV2 extension
#338Re: Chrome is looking to permanently drop MV2 extension
#339Why are people on HN still using Chrome? (or Edge, or Opera…)
I use Firefox for everything on Windows, macOS, and Android.
I do have to keep Chrome around on desktop due to VirusTotal + reCaptcha setup to be purposely onerous for non-Chrome users. I'll get caught in loops trying to scan files after only scanning a few where I'll get like 5 absurdly vague captchas in a row. You must solve all of them in a row or it starts over from the beginning. It does this even if I'm logged into Google, logged into VirusTotal, and have uBlock Origin disabled on VirusTotal.com. It appears to be by design. So, to ensure I get to scan all my PortableApps.com releases, I have to use Chrome.
Re: Chrome is looking to permanently drop MV2 extension
#340Wouldn't it be possible to write some kind of local proxy server with MITM for HTTPS that modifies scripts and supplies the missing functionality for ublock origin?
partially, but it couldn't replicate all functionally. A lot of uBO rules apply to elements on the DOM. Like hiding a div with ID "#ads". That div often isn't sent as pure HTML, but is instead added to the page via JS code executing. At the MITM-level you won't be able to have rules that apply to the rendered DOM.
That said, selector based ad-blocking is still supported in MV3. So might be possible to get most of the functionality with both a MITM-level blocker and an MV3 selector based blocker.