3 ms·

From what I've understood, it's not recommended to run Ungoogled Chromium: https://qua3k.github.io/ungoogled-chromium https://qua3k.github.io/ungoogled-chromium

by justaj 5y ago

jlokier 5y ago
In interesting article. Personally I use Ungoogled Chromium on my Mac occasionally, for things Firefox doesn't do well, but mostly I use Firefox and Safari. In that article there's something I disagree with having tried: > Most of the functionality of the patches are either in the best case minimally beneficial or can be reproduced with either a setting, a flag, or a switch, Some years ago, on Linux, I tried finding all the command line flags necessary to use Chrome without having it talk back to Google. Unfortunately despite hunting for every option I could find (and there are a surprisingly large number of undocumented options), including with "strings", nothing I tried completely suppressed traffic to Google while using Chrome on sites not connected with Google. My motivation at the time was to run my own local applications using Chrome as the UI, the way Electron is used now. It didn't work out because I failed to find a way to confidently suppress traffic to Google. That experience is why I run Ungoogled Chromium now when I need Chrome functionality.
hulitu 5y ago
"third parties contribute prebuilt binaries, so there is no central party to trust." For me Google _is_ a third party. And taken into account its behavior it receives 0 (null) trust from me. What i really don't understand is this blind trust in everything google does.
wzdd 5y ago
For the Chromium-relevant configuration changes applied automatically by Ungoogled Chromium: I would never have discovered them all by myself, and, now that I know about this article, I'm not convinced that I would be able to stay on top of any future switches and configuration changes in future versions of Chromium. That said, the "binaries built by anyone" thing is pretty suspect.
smoldesu 5y ago
Even as someone who doesn't use Ungoogled Chromium, those are pretty dumb reasons not to use the browser. The biggest draw (to me) is having the telemetry digitally stripped out before being compiled, so that Google can't remotely activate any tracking, fingerprinting or identification.

From what I've understood, it's not recommended to run Ungoogled Chromium: https://qua3k.github.io/ungoogled-chromium https://qua3k.github.io/ungoogled-chromium

by justaj 5y ago

From what I've understood, it's not recommended to run Ungoogled Chromium: https://qua3k.github.io/ungoogled-chromium https://qua3k.github.io/ungoogled-chromium

jlokier 5y ago

In interesting article. Personally I use Ungoogled Chromium on my Mac occasionally, for things Firefox doesn't do well, but mostly I use Firefox and Safari. In that article there's something I disagree with having tried: > Most of the functionality of the patches are either in the best case minimally beneficial or can be reproduced with either a setting, a flag, or a switch, Some years ago, on Linux, I tried finding all the command line flags necessary to use Chrome without having it talk back to Google. Unfortunately despite hunting for every option I could find (and there are a surprisingly large number of undocumented options), including with "strings", nothing I tried completely suppressed traffic to Google while using Chrome on sites not connected with Google. My motivation at the time was to run my own local applications using Chrome as the UI, the way Electron is used now. It didn't work out because I failed to find a way to confidently suppress traffic to Google. That experience is why I run Ungoogled Chromium now when I need Chrome functionality.

hulitu 5y ago

"third parties contribute prebuilt binaries, so there is no central party to trust." For me Google _is_ a third party. And taken into account its behavior it receives 0 (null) trust from me. What i really don't understand is this blind trust in everything google does.

wzdd 5y ago

For the Chromium-relevant configuration changes applied automatically by Ungoogled Chromium: I would never have discovered them all by myself, and, now that I know about this article, I'm not convinced that I would be able to stay on top of any future switches and configuration changes in future versions of Chromium. That said, the "binaries built by anyone" thing is pretty suspect.

smoldesu 5y ago

Even as someone who doesn't use Ungoogled Chromium, those are pretty dumb reasons not to use the browser. The biggest draw (to me) is having the telemetry digitally stripped out before being compiled, so that Google can't remotely activate any tracking, fingerprinting or identification.