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.

I do fear for a future were even Firefox ends up caving in. Ladybird browser might be our only hope until something legal comes along to block functionality.

Poor little Google doesn't have the resources to support mv2.

In what way? I've never noticed a difference.

One time setup, it’s synced to Mozilla account for later reinstalls

And then there's still Firefox and all of its forks.

Best of luck to Big Tech as people will move on elsewhere.

> https://about.google/company-info/philosophy/

> 1. Focus on the user and all else will follow.

> 6. You can make money without doing evil.

I'm tired of all the (mostly technical) people whining that they need Chrome, and only Chrome can browse the internet. Then you ask them for a site that doesn't work and conveniently "it was some time back and I don't remember the details".

I've been using FF since before it was called Firefox. In the last 10 years I've not come across any site that doesn't work with Firefox - online shopping, social media, banking, custom line-of-business internal apps, ERP apps... you name it.

And, TBH, if I did, I'd just visit that one site with Chrome, and still use FF daily.

But that was before LLM-driven development, I think that now the game has changed, and maybe Google hasn't got the leverage it thinks it has.

Any other browser with uBlock Origin: Chrome is dead.

Unfortunately sometimes my Intel Arc B580 has a driver quirk where all the windows freeze and unlike Chromium based browsers I can't open Task Manager and kill the GPU Process and have it restart and have everything keep working, but rather have to kill the whole browser and restart it and hope the tabs load back correctly - thankfully haven't had many issues with losing those (only once or twice in the past year, but those were fucking annoying).

Either way, I explored both Edge as my daily driver for a year or so and also Safari on my Mac - both are actually fine as far as the user experience is concerned, but in the end I still come back to Firefox. It's a browser, it doesn't feel user hostile, it does its job well enough. Also personally I like its devtools more.

People just like to rage against Google.

https://chromewebstore.google.com/detail/ublock-origin-lite/...

It's even available on iOS, I have it running in Safari

Only need Firefox ESR for a handful of websites giving me no option when specifying a Linux/Mozilla user agent instead of the native one for those doesn't work.

Here is the guy who builds the browser I use https://www.stoutner.com/about/

git https://gitweb.stoutner.com/?p=PrivacyBrowserAndroid.git;a=s...

download https://www.stoutner.com/privacy-browser-android/changelog/

This change is good for the majority of users, but is actually bad for large enterprise customers and highly-regulated customers. It puts more control and onus of responsibility on to Google, rather than the end-user. So, we will expect to see better enforcement of controls from Google for the lowest-hanging-fruit that some aspects of MV2 exposed.

What's that, you say? MV2 changes? Well there's 3 things.

1. Remote code execution. The ability for someone to just yeet commands into your browser. A little harder to do directly.. Still very possible, just with extra steps.

2. Removing the ability for extensions to access network requests directly, which is what adblockers often relied on. It also means malicious extensions could snoop on your requests. They still can, just with extra steps.

3. Background persistence, an extension could stay alive, maintain state, run timers, keep connections open, and coordinate across tabs. So this shuts off the "background persistence" piece -- but helps with ensuring better isolation. Still possible, but now requires yeeting your data to an external provider instead of keeping the state contained locally.

Those 3 changes are incredibly powerful, and will impact many, many Enterprise security tools. Tools that now instead will result in products like "Island Browser", and "Enterprise Chrome" being rolled out to supplement the functionality that MV2 gave us.

This change goes against the US and Australian government's hardening advice, and reduces the overall efficacy of security controls we're able to implement within our web browsers natively.

CISA's own guidance on this is pretty straightforward (aptly named Securing Web Browsers and Defending Against Malvertising for Federal Agencies): https://www.cisa.gov/sites/default/files/2023-09/CISA%20CEG%...

Here's the Australian Government's control relating to it:

> Control: ISM-1485; Revision: 1; Updated: Sep-21; Applicable: NC, OS, P, S, TS; Essential 8: ML1, ML2, ML3 > Web browsers do not process web advertisements from the internet.

And if you're wondering about what incentives there are that led to this change, you can read this letter written to the Chairman of the FTC by a US Senator back in 2020. This letter is linked to from the same CISA document I shared earlier.

You should read it in full, and consider what incentives the Senator was referring to -- and how they also apply in this scenario.

https://www.wyden.senate.gov/imo/media/doc/011420%20Wyden%20...

Those Enterprise Chrome products I mentioned earlier? Chrome's change has now put some of this functionality which was previously possible with an extension, behind the Enterprise Chrome Premium SKU: https://chromeenterprise.google/products/chrome-enterprise-p...

You know what else is a security concern? Ads. The amount of mental gymnastics is insane. It's honestly insulting.

smiling smugly from planet firefox