@mitch On by default, works only on Google properties,...

@mitch On by default, works only on Google properties, and "works around" the limits of the web platform *that we put in place to meaningfully safeguard user battery and storage and bandwidth*. At least it's not buried in `chrome://system` like the CPU monitoring extension is, but no less self-preferencing for it.

Like 9 July at 22:12 | Wall-to-wall | Open on toot.cafe

2 comments

Alex Russell

@mitch The tragedy in both instances is that the teams that dropped turds in Chrome have faced no pressure to move to open, interoperable APIs, meaning other browsers (including other Chromium ecosystem browsers) feel forced to include them to make sure that Google's very popular web properties "work right".

This also keeps web APIs from advancing because teams that would push them forward already have theirs, Jack. It's not Android levels of bad, but it's bad.

9 July at 22:16 | Open on toot.cafe

Mitch Effendi (ميتش أفندي)

@slightlyoff woah. Thanks for sharing. I was aware of the volume size b/c of my runaway cache at work but the rest was news to me.

9 July at 22:55 | Open on posts.dumb.stuff.donaberger.xyz