Why was IceCat removed in favor of Brave? #380

New Issue

2017-12-23T16:38:48Z

angela-d commented

2017-12-23 16:38:48 +00:00

(Migrated from github.com)

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

While submitting PR https://github.com/privacytoolsIO/privacytools.io/pull/379 I seen IceCat was previously listed and then removed, with seemingly no explanation. ![icecat-removed](https://user-images.githubusercontent.com/33108490/34321037-87ea8250-e7fd-11e7-8186-108967a40c43.png) (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](https://en.wikipedia.org/wiki/Brave_(web_browser)) are greater champions of privacy than [IceCat](https://en.wikipedia.org/wiki/GNU_IceCat), though. What's the deal with the switch? *** Another curious removal (albeit unrelated): ![csp](https://user-images.githubusercontent.com/33108490/34321201-341bc748-e801-11e7-8d2f-9f9b27a581e3.png) 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 commented

2017-12-23 16:51:18 +00:00

(Migrated from github.com)

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

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

👎 2

angela-d commented

2017-12-23 17:01:43 +00:00

(Migrated from github.com)

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.

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 commented

2017-12-23 20:44:10 +00:00

(Migrated from github.com)

I think ungoogled chromium beats both.

beerisgood commented

2017-12-23 21:12:07 +00:00

(Migrated from github.com)

@Shifterovich it is up2date and without any telemetry?

Atavic commented

2017-12-25 16:19:02 +00:00

(Migrated from github.com)

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

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](https://www.ghacks.net/2016/10/05/ungoogled-chromium-removes-google-traces-from-chromium/)

kewde commented

2018-01-19 19:09:27 +00:00

(Migrated from github.com)

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

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

😆 1

angela-d commented

2018-01-19 19:27:26 +00:00

(Migrated from github.com)

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

kewde commented

2018-02-11 12:30:52 +00:00

(Migrated from github.com)

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.

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.

This repo is archived. You cannot comment on issues.