Indeed. Although I'm a little surprised that CPU access isn't one of the features denied through simple anti-fingerprinting measures.
Edit: After a brief search there (thankfully) doesn't appear to be such a straightforward way to measure CPU load. Which of course makes it that much harder to block.
It often missed what should have been exact matches. You could copy and paste a variable name or a string from the repo and the search would not find it.
You can deny push notifications by default in your browser settings and never be prompted again. They can still be manually allowed on the sites where you actually want them. Same goes for location requests and other "site settings".
Aside, I've been waiting years for a favicon API, which Chrome has had from the start. It's a pretty glaring hole for any extension that displays bookmarks or history.
The Decentraleyes[1] and LocalCDN[2] extensions aim to do this in part. But the effectiveness is limited since they only have a handful of libraries and most sites bundle their javascript.
I still miss my BlackBerry, not just for the keyboard; the trackpad was far more precise and comfortable than a touch screen. No awkward reaching for controls at the top of the screen, no fat-fingering the wrong link.
I honestly think their biggest mistake was the BlackBerry-specific data plan requirement, not the slow entry to the touchscreen market.
At the time the data plan was a very useful feature. It worked globally without any additional costs for email. That's much like Google Fi today. I think that it was a major selling point. If BlackBerrys were sold without the plan than eventually it would need to compete with much cheaper devices. I think it is very similar to the model of iPod + iTunes at the time.
