It turns out Google Chrome ships a default, hidden extension that allows code on `*.google.com` access to private APIs, including your current CPU usage
You can test it out by pasting the following into your Chrome DevTools console on any Google page:
chrome.runtime.sendMessage(
"nkeimhogjdpnpccoofpliimaahmaaome",
{ method: "cpu.getInfo" },
(response) => {
console.log(JSON.stringify(response, null, 2));
},
);
More notes here: https://simonwillison.net/2024/Jul/9/hangout_servicesthunkjs/
Did you use normal chromium or Ungoogled Chromium? I tried it on the Arc Browser (which is based on Chromium), and it worked, but it didn’t work on Ungoogled Chromium.
Cannot reproduce on chromium. Has anyone reproduced it?
yeah:
{ "value": { "archName": "arm64", "features": [], "modelName": "Apple M2", "numOfProcessors": 8, "processors": [ { "usage": { "idle": 10841460, "kernel": 611796, "total": 13342920, "user": 1889664 } },...Did you use normal chromium or Ungoogled Chromium? I tried it on the Arc Browser (which is based on Chromium), and it worked, but it didn’t work on Ungoogled Chromium.
Neither. I use a chromium package from my linux distribution.
It has many patches on top of the upstream chromium. That probably explain why that unwanted feature isn’t there.
This issue appear on Google Chrome for Windows on my other machine. Just uninstalled it, never used it anyway.
Reproduced here, Chromium on Linux Mint desktop. You need to have open a Google.com site for it to work though.