2 ms·

Looks like this is accessing "chrome.system.cpu" API, which any extension can access (given the "system.cpu" permissions). https://developer.chrome.com/docs/ex

Looks like this is accessing "chrome.system.cpu" API, which any extension can access (given the "system.cpu" permissions). https://developer.chrome.com/docs/extensions/reference/api/system/cpu https://developer.chrome.com/docs/extensions/reference/api/s... You can see all the permissions requested by this extension here: https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/resources/hangout_services/manifest_v3.json;l=23-31 https://source.chromium.org/chromium/chromium/src/+/main:chr...

kelnos 2y ago
Yes, and that's the issue: Google is bundling an extension into Chrome that is unrelated to the operation of the browser itself, which gives another one of its products (Hangouts) privileged access that no other videoconferencing app has, at least not without the big step of getting users to manually install another extension.