Google Chrome got caught!

Summary

In this video, Eric discusses a controversy surrounding Google Chrome, which has been found to have a hidden extension that collects CPU usage data and other system information, functioning exclusively on Google sites for over a decade. This feature, initially added for debugging purposes, raises concerns about anti-competitive practices and privacy. While some argue its utility for telemetry and debugging, others see it as a violation of browser neutrality and the Digital Markets Act. The video explores the implications, how it works, and its presence in various Chromium-based browsers, including Brave, which plans to remove it.

Takeaways

• 🔍 Google has been caught in controversy due to a hidden feature in Chrome that has been present for 11 years.
• 🛠️ In October 2013, Google added a feature to Chrome to facilitate debugging of Hangouts, which created a hidden extension.
• 🚫 This extension only works on google.com and is not available on other Google sites like YouTube.
• 🤔 The feature raises anti-competitive concerns because it provides Google with an advantage over other sites.
• 💻 The feature allows execution of 'chrome.runtime.sendMessage' and 'cpu.getInfo', revealing CPU usage and other system details.
• 🔑 It can detect virtual machines and show processor time, which is useful for debugging but also raises privacy issues.
• 🗨️ Google's own comments suggest that the feature is mundane and intended for troubleshooting in Google Meet.
• 🤖 The feature is considered by some as giving Google an unfair competitive advantage in the browser market.
• 📜 The Digital Markets Act (DMA) in the EU could see this feature as a violation of equal capabilities for all websites.
• 👀 The source code for the Hangout Services extension is available in the open-source Chromium, not just in Chrome.
• 🛡️ While the feature is present in many Chromium-based browsers, Brave allows users to disable it through settings.

Q & A

What is the controversy Eric discusses in the video?

The controversy is about Google's Chrome browser having a hidden functionality that has been present for 11 years, which allows Google sites to access detailed CPU information and system telemetry, potentially giving Google an unfair competitive advantage.

When did Google add the functionality that is now under controversy?

Google added the controversial functionality in October 2013 to make debugging Hangouts easier.

What specific information can Google sites access due to this functionality?

Google sites can access the number of processors, CPU time, processor features, and potentially temperatures, although the latter might only work on Chromebooks.

Is this functionality available on all Google sites or only specific ones?

This functionality is specifically available on google.com. Eric tried it on YouTube and blog.google but it seems to be limited to google.com.

What does Eric demonstrate in the video to show the functionality in action?

Eric demonstrates the functionality by executing 'chrome.runtime.sendMessage' with the extension's ID and 'cpu.getInfo', which returns the CPU information.

How does this functionality potentially violate privacy?

The functionality potentially violates privacy because it collects and exposes detailed system information, which could be used without the user's explicit consent or knowledge.

What is the DMA and how might this functionality violate it?

The DMA, or Digital Markets Act, is an EU regulation that requires browser vendors to not give preference to their websites over others. This functionality could be seen as a violation because it exposes system information only to Google properties.

How is this functionality implemented in the open-source Chromium?

The functionality is implemented in the open-source Chromium through a hidden Hangout Services extension with methods like 'getCPUInfo' and others for logging and telemetry.

Can users disable this functionality in Chrome or Chromium-based browsers?

Users cannot disable this functionality in Chrome, but some Chromium-based browsers like Brave allow users to disable it through settings.

What is Brave's stance on this functionality, and can it be disabled in Brave?

Brave allows this functionality to be disabled through its settings under extensions. Brave CEO Brandon Ike acknowledges the functionality and has shared his thoughts on it.

How do other Chromium-based browsers handle this functionality?

Most Chromium-based browsers, including Edge, have the functionality intact and do not allow users to disable it. However, the controversy might lead to changes in how these browsers handle the feature.