The Chromium Security Paradox
island.ioThis seems to make some odd claims:
"Chromium has developed and pioneered several security architectures such as: HTTPS for encrypted communication."
https is more than a decade older the Chromium.
The whole thing is an attempt to sell their "enterprise browser" and "by embedding enterprise-grade IT, security, network controls, data protections, app access, and productivity enhancements directly into the browser itself"
They pushed hard for its adoption, for example with the "Not secure" indicator: https://aboutssl.org/how-to-fix-the-https-not-secure-message...
There are other, not less important players, such as Let's Encrypt.
So while they didn't develop or pioneer HTTPS per se, they played an important role.
We really need to move from "user accounts" to "application accounts".