5 ms·

I'm running Chromium with HTTPS everywhere, uBlock Origin, Wappalyzer (curiosity purpose) & Bitwarden (password manager). It's the best setup I found regarding

by m_b 8y ago

I'm running Chromium with HTTPS everywhere, uBlock Origin, Wappalyzer (curiosity purpose) & Bitwarden (password manager). It's the best setup I found regarding performances & energy consumption for my GNU/Linux laptops.

moystard 8y ago
It might be in terms of performance and energy consumption, but it is clearly not when it comes to privacy.
- amelius 8y ago
  Could you explain, what privacy issues exist with Chromium?
  - vetinari 8y ago
    From https://www.chromium.org/developers/how-tos/api-keys https://www.chromium.org/developers/how-tos/api-keys: > Some features of Chromium use Google APIs, and to access those APIs, either an API Key or a set of OAuth 2.0 tokens is required. Setting up API keys is optional. If you don't do it, the specific APIs using Google services won't work in your custom build, but all other features will run normally. From experience, running without API key means that the browser will nag you at every start. If it doesn't, you do have them and then the browser uses APIs mentioned on the page.
  - morganvachon 8y ago
    This was one of the more egregious ones from a few years ago; since fixed, but as far as I'm concerned the trust was permanently broken (what's to stop them from doing something similar and hiding it better, after all this made it past the package maintainer until a user complained). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909
    - dvfjsdhgfv 8y ago
      By the way, I think this comment [0] sums it up well for many HN folks: > As a web developer, I like chrome. As a private person, I uninstalled it. You might call it a feature or a core extension, most people consider this spyware. [0] https://bugs.chromium.org/p/chromium/issues/detail?id=491435#c12 https://bugs.chromium.org/p/chromium/issues/detail?id=491435...

by m_b 8y ago

moystard 8y ago

It might be in terms of performance and energy consumption, but it is clearly not when it comes to privacy.

amelius 8y ago
Could you explain, what privacy issues exist with Chromium?
- vetinari 8y ago
  From https://www.chromium.org/developers/how-tos/api-keys https://www.chromium.org/developers/how-tos/api-keys: > Some features of Chromium use Google APIs, and to access those APIs, either an API Key or a set of OAuth 2.0 tokens is required. Setting up API keys is optional. If you don't do it, the specific APIs using Google services won't work in your custom build, but all other features will run normally. From experience, running without API key means that the browser will nag you at every start. If it doesn't, you do have them and then the browser uses APIs mentioned on the page.
- morganvachon 8y ago
  This was one of the more egregious ones from a few years ago; since fixed, but as far as I'm concerned the trust was permanently broken (what's to stop them from doing something similar and hiding it better, after all this made it past the package maintainer until a user complained). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786909
  - dvfjsdhgfv 8y ago
    By the way, I think this comment [0] sums it up well for many HN folks: > As a web developer, I like chrome. As a private person, I uninstalled it. You might call it a feature or a core extension, most people consider this spyware. [0] https://bugs.chromium.org/p/chromium/issues/detail?id=491435#c12 https://bugs.chromium.org/p/chromium/issues/detail?id=491435...