ffupdater VS brave-core

FFUpdater (version 78.3.0): Updater for privacy friendly browsers

I've never tried Kiwi Browser but had similarly come across it while searching. The dev interestingly refers to them ads[1] (2022), though prior to being accepted properly into Bing's referral program Kiwi redirected all search queries through their own servers[2][3] (2021) (the original Kiwi repo's issues tab has been deleted since).

Tbf dev always sounds reasonable in their responses but was a little off-putting initially so I kinda understand the GP's post.

[1] https://github.com/kiwibrowser/src.next/issues/91#issuecomme...

[2] https://github.com/Tobi823/ffupdater/issues/35

[3] https://web.archive.org/web/20210605191305/https://github.co...

For "Chrome", you can use Kiwi Browser or Yandex Browser. Both are a bit controversial: https://github.com/Tobi823/ffupdater/issues/35 and the other one is Yandex Browser. But both support add-ons. You can use mobile Beta/Nightly Firefox/Fennec instead with custom addon collection like in this example: https://github.com/octonezd/oldlander#firefox

But there is FFUpdater which includes IceRaven.

Plus à ce sujet

on Android I saw Privacy Browser in FFUpdater

Actually there was a conflict between Fulguris and Styx. But It resolved nicely between two devs. The dev of Styx deleted the repo. After migrating to Fulguris base, Styx reappeared again. Probably that's why IzzyOnDroid showing this anti-feature.

Updating apps is a pita for me: Firefox has its own updater app: https://f-droid.org/en/packages/de.marmaro.krt.ffupdater

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