ungoogled-chromium VS brave-browser

Chromium is Chrome with "less" (but, still substantial) Google. ungoogled-chromium[1] is Chromium with no Google.

[1] https://github.com/ungoogled-software/ungoogled-chromium

What's the best next choice if I don't want to move away from a Chrome-like experience?

(Old habits die hard)

There's https://github.com/ungoogled-software/ungoogled-chromium - is it a sound choice nowadays?

https://github.com/ungoogled-software/ungoogled-chromium/blo...

I think you want:

https://github.com/ungoogled-software/ungoogled-chromium

Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.

ungoogled-chromium addresses these issues in the following ways:

* - Remove all remaining background requests to any web services while building and running the browser*

* - Remove all code specific to Google web services*

* - Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.*

* - Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).*

Cromite[0] is the best on Android, it's a privacy-oriented open source patchset on top of Chromium.

Cromite has a desktop build, but it's a bit more experimental than the mobile build, so you can use Ungoogled Chromium[1] instead. Ungoogled is also a privacy-oriented open source patchset on top of Chromium. Check the beta flags to enable some more interesting features like getClientRect anti-fingerprinting measures (unfortunately breaks some React-based sites that go into infinite re-render loop).

Both of these browsers selectively include patches from Brave, but they are community-oriented builds so imo more trustworthy than Brave, which continues to package various shady anti-features and always will because it's backed by a for-profit company.

LibreWolf[2] is the nicest Firefox-based one for desktop, I think. It's pretty hardcore, though, I most only use it to visit mainstream social media sites.

I tried a bunch of the Firefox-based ones on mobile and none of them clicked for me. Cromite is just too slick on Android. Put the address bar at the bottom and off you go. Only downside is no online syncing of tabs and bookmarks, but meh. You can save all open tabs to bookmark bar in one hit then export your bookmarks, send the file through whatever E2EE channel you want to your other device and import then reopen them again.

[0] https://github.com/uazo/cromite

[1] https://github.com/ungoogled-software/ungoogled-chromium

[2] https://librewolf.net/

For those that like Chromium but want to remove any integration with Google, there's Ungoogled Chromium

https://github.com/ungoogled-software/ungoogled-chromium

If you're entirely partial to Chromium browsers, use Ungoogled Chrome https://github.com/ungoogled-software/ungoogled-chromium

what about https://github.com/ungoogled-software/ungoogled-chromium

Separate reply that ritual impurity or blind black-box rejection of open source Chromium/Blink seems also to suffer from emotionalism over reason. See

https://github.com/brave/brave-browser/wiki/Deviations-from-...

This is a choice we made. As I wrote in my last reply, I think we would have died trying to get Gecko/Graphene with a Web front end up to competitive scratch vs. Chrome (nm Firefox).

A Firefox fork would have gone over badly with some potentially large number of Mozilla/Firefox fans, and we'd still lack key elements not part of the Mozilla open source (at the time, e.g., Adobe's CDM for HTML5 DRM). On the upside we'd have more UX customizability.

But our choice of Chromium/Blink (via Electron, so we had Web front end upside without Firefox extensions) was not a slam dunk choice. It involved trade-offs, as all engineering does. The downside is we have to audit and network-test for leaks and blunders, which often come from Chromium upstream:

https://x.com/BrendanEich/status/1898529583546421322

6. Brave

[2] https://github.com/brave/brave-browser/issues/10808

At the very least, I do not trust a browser that was putting affiliate links to unsuspecting users' urls [0]. Plus I tbh I am really sick of everything tending to be chromium-derivatives nowadays and I think it is good to have greater diversity, to exactly avoid situation susch as the one here.

https://github.com/brave/brave-browser/issues/10134

Not so. The Chromium bits have the native tracking goo we neutralize, see https://github.com/brave/brave-browser/wiki/Deviations-from-....

One example was an issue in the Brave Browser project to add a policy for disabling a feature. The documentation provided clear instructions, so I decided to give it a try. After cloning the repositories, one for the whole project and the other containing the actual browser code which is a fork of chromium (it was HUGE). I installed the necessary tools (like depot_tools) and packages needed by Chromium. Despite realizing early on that the project was massive, I decided to give it a shot.

I install: Discord, Brave, [Telegram(https://desktop.telegram.org/) and VSCode, which then I sync with my github profile to pull down my settings.

Ignorance is bliss, I'm here to bring enlightenment:

https://github.com/brave/brave-browser/wiki/Deviations-from-...

https://brave.com/privacy-updates

Firefox and Brave Browser