brave-browser VS thorium

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

Brave seems to remove these parameters from links. Discussion (and links to examples/docs): https://github.com/brave/brave-browser/issues/35094

Brave - Privacy-focused browser with ad-blocking.

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-....

I'll wait for Ladybird to be more mature.

Until then, I'm more than happy with Thorium:

https://thorium.rocks/

So far, the only complain is it doesn't support Netflix (usual DRM stuff):

https://github.com/Alex313031/thorium/issues/523

[Thorium](https://thorium.rocks/) is a fork of Chromium that maintains a patchset that reverses functional and UI regressions introduced by Google (such as the tabs and menu styling from the 2023 refresh). The author has committed to maintain manifest V2 support for as long as possible.

the original plan was to self-host my blog and write there but lot of stuff happend and i still haven't created a self-hosted blog. so i will stick to dev.to for my next posts as my good old waterfox classic browser was killed by "overjavascriptification" from all sides. now i am on a browser mix of my good old waterfox, librewolf and ungoogled chromium. i will evaluate thorium and mercury next. why don't i use the regular firefox? because i really don't like the direction mozilla is going to. the last wtf was the implemenation of some kind of tracking which is opt-out and not opt-in.

> Firefox is eons more private than Chrome - or any of it's based browsers - can ever be

Some progress is made though...

Brave: https://brave.com

Thorium: https://github.com/Alex313031/thorium

I found the original commit [1] since the other Github link in the thread shows the removal. I'm not entirely sure what the process was around adding to begin with

[1] https://github.com/Alex313031/thorium/commit/26655c920b6a9e4...

I'm dissuaded from using Thorium after the news of the developer including... questionable material in their builds[0], and checked into CVS no less.

[0]: https://github.com/Alex313031/thorium/issues/147