ungoogled-chromium VS brave-core

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

Firefox or Ungoogled Chromium (needs to update uBlock manually) in Incognito window with unchanged vanilla uBlock Origin with lists updated and no other plugins and without YouTube account. Works perfectly. Also FreeTube.

Ungoogled Chromium is a Chromium-based browser with Google services stripped out.

- Project and source: https://github.com/ungoogled-software/ungoogled-chromium

- Binaries: https://ungoogled-software.github.io/ungoogled-chromium-bina...

Using these sort of downstream patch set browsers is rarely a good idea. If it has multiple full-time developers from a respected org dedicated to it, then it can be justifiable (Tor Browser, Brave), but take a look at the gaps in time for these two pages:

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

https://metadata.ftp-master.debian.org/changelogs//main/c/ch...

There's often days you're going without security patches. If you want a browser without Google tracking, Firefox is a much better choice.

Unrelated but about Brave and interesting to me: I recently found myself having a large upstream project that I need to maintain some custom patches for, and there's a need for deeper customizations and I worry that my rudimentary system of applying .patch files will turn into an unmaintainable nightmare of merge conflicts after every rebase. I was thinking about possible solutions, and it occurred to me that Brave being Chromium-based must have this same challenge but an order of magnitude more difficult, so I looked for their code to see how they solved this issue.

It's pretty interesting! They do basically the same thing for core Chromium, applying a (big) set of patches[1].

Incidentally, I'd be interested to hear any ideas/approaches to this problem. I'm guessing if there was something clearly better, Brave would be doing it, but it seems like there should be a better way even if I can't think of one.

[1] https://github.com/brave/brave-core/tree/master/patches

https://github.com/brave/brave-core/pull/13737

(Incidentally, that PR number is not quite elite. :)

I disagree that it's lip service Brave has a ton of engine level privacy patches https://github.com/brave/brave-core/tree/master/patches

To my understanding you can't match it with just js extensions.

Only firefox on the highest security mode comes close I think?

Or ungoogled chromium? (brave has most of their patches IIRC)

Are there other options that have this number of patches?

Chromium is not 100% Google's forever and always, though they do currently lead the way, and with the most used/backed fork.

https://github.com/brave/brave-core/pull/19476

They have much more changes than just compile flags. Here's the repo where they maintain their patch set: https://github.com/brave/brave-core/tree/master/patches

Brave Private Ads toggle controls just Push Notification ads at this time. So, if you are still seeing Push Notification ads, that would be incorrect. However, it's normal to still see New Tab Page image ads, and/or other ad formats. We are introducing a new UI that helps you better toggle on/off specific ad units, and removing the "Brave Private Ads" toggle that can be confusing: https://github.com/brave/brave-core/pull/18938

Yes, being fixed. Github at https://github.com/brave/brave-core/pull/18922