|
|
|
|
|
|
by adlwalrus
5004 days ago
|
|
|
I don't think there's a need to discuss it as some kind of frightening black box that nobody's too sure about, either. As far as is known, I believe Chrome - Chromium == Branding, MP3 codecs, Pepperflash, Foxit PDF reading libs. With flash, they have some kind of special arrangement with Adobe; with the other three, it seems like it amounts to licensing bullshit that's keeping their hands tied. There used to be that RLZ usage tracking thingy, but IIRC it got taken out. I'm sure there's other stuff like auto-update and usage statistics-gathering components added to the Chrome build as well. If I missed anything, please do point it out. By the way, my goal isn't to warm people up to the proprietary Chrome build. My point is more to make people feel less like they're missing out by ditching it for the freer Chromium. It definitely has to be acknowledged that from a security perspective, it must be assumed that Chrome contains back doors and "innocently neglected" security vulnerabilities for big brother in all his various incarnations. So use Chromium, damnit! |
|
|
In any case, Google Chrome Helper makes me trust Chrome even less. Your comment made me curious about it, and it turns out that once activated, it's perpetually open in the background, often maxing out the processor, and it can't be quit without uninstalling Chrome. Supposedly it's related to Google Cloud Print and/or Flash, but I had both disabled and the above was still true.
Makes the caution about potential backdoors/vulnerabilities seem that much more reasonable.