5 ms·

Yes just like their WiFi probing thing that they got in trouble for and blamed it on a rogue developer...

• taligent 14y ago
  And their abuse of the Safari Do Not Track setting.
• abraham 14y ago
  You could always read the source: http://git.chromium.org/gitweb/?p=chromiumos/platform/assets.git;a=tree;f=chromeapps/hterm http://git.chromium.org/gitweb/?p=chromiumos/platform/assets...
  • meaty 14y ago
    As other people have said: Chromium is not Chrome...
    • DannyBee 14y ago
      This is basically false. As I've said, at least on desktop platforms, if you were to remove the extra shipped plugins from Chrome, you should end up with something you can build from chromium source
• ChrisClark 14y ago
  And we would never know that the wifi program they used had kept logs unless they told us. The very first mention of the problem was a press release by Google. In the same press release they said they fixed the problem and would be deleting the logs, but many governments quickly stopped them from deleting the logs so they could investigate. That's probably why they announced they would delete them before they actually did. And the investigations found that Google was not at fault for accidentally recording unencrypted publicly transmitted data. ;)