-
I don't know why they went with patch files instead of forking chromium and rebasing the changes via git.
They document how developers should "rebase" chromium:
https://github.com/brave/brave-browser/wiki/Chromium-rebases...
And it looks like way more work than doing it with git via
git rebase chromium/master -
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
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/
-
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/
-
If ads, in particular on YouTube, are the problem, anything Chromium-based is probably only going to get worse and worse (see [1] and [2]). So that basically leaves you with Firefox and Safari.
I work for Mozilla (speaking for myself, of course), so I'll leave you to guess which I'd recommend :P
[1] https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
[2] https://arstechnica.com/gadgets/2023/09/googles-widely-oppos...
-
brave-core
Core engine for the Brave browser for mobile and desktop. For issues https://github.com/brave/brave-browser/issues
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
