Privacytools.io: Why was IceCat removed in favor of Brave?

[angela-d]

While submitting PR https://github.com/privacytoolsIO/privacytools.io/pull/379 I seen IceCat was previously listed and then removed, with seemingly no explanation.

(this is modified code from the PR, so the line #s in the current master repo won't be exact)

I have nothing against Brave, I think it's fantastic there's an additional alternative among the Chrome and Firefox's of the world.
Someone will be hard-pressed to suggest that Brave are greater champions of privacy than IceCat, though.

What's the deal with the switch?

---

Another curious removal (albeit unrelated):

Why was the CSP removed?
There's a lot of sloppy inline on index.html; to prevent it from breaking the page, 'unsafe-inline' (or stop using inline css, ideally) is all that had to be added. (I am inquiring to see if there's another reason for its disabling before I go through and modify the pages)

Update:
CSP cause: https://github.com/privacytoolsIO/privacytools.io/issues/302

[beerisgood]

IceCat is not up2date.
Brave is shit. Just a chromium fork with own telemetry

[angela-d]

Point taken about IceCat, the last ESR (IceCat's upstream) vulnerability is from 12/7: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox-esr/

No disagreement about Brave! Though for users who prefer Chromium for whatever reason, Brave is a substantially better choice for privacy than Chrome.

[ghost]

I think ungoogled chromium beats both.

[beerisgood]

@Shifterovich it is up2date and without any telemetry?

[Atavic]

Latest release is 62.0.3202.94-2

Eloston did the following:

Disable or remove offending services and features that communicate with Google or weaken privacy
Strip binaries from the source tree, and use those provided by the system or build them from source
Add, modify, or disable features that inhibit control and transparency (these changes are minor and do not have significant impacts on the general user experience)

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

Review

[kewde]

The CSP was something I was toying with, I had initially merged, suspecting it wouldn't cause much harm.
It broke a lot of things however, and I haven't had the chance to get back to it.
Thanks for bringing this up, I completely forgot about it too :P

[angela-d]

The CSP is definitely useful (when it doesn't break things)

[kewde]

I'm also more a fan of ungoogled chromium.

---

I have been working the past few weeks with the electron fork of Brave (also known as Muon) and I've really grown to like it. If one day we make a privacytools.io for programmers with a list of good libraries and frameworks then Muon from Brave deserves the top spot over electron in the NodeJS realm.

One of the reasons why I don't truly like advertising the usage of Brave is that the npm package system is a complete disaster and Brave loads quite a few packages.