Request for Mozilla Position on an Emerging Web Specification Specification Title: Web Environment Integrity API Specification or proposal URL (if available): https://rupertbenwiser.github.io/Web-E...
They try to present it as “detecting abuse”, but it’s literally just “allow servers to block non-verified browers”(in other words google blocking access to their services for non-chrome users(the people proposing it work for google)).
And as always these types of asshats always shit all over anyone using accessbility tools(or don’t even consider them in the first place, which amounts to the same thing).
pretty much yes to keys and hashes. Just think HDCP and HDMI
That said, I imagine it’ll have to be easier to hack software that isn’t embedded in hardware. but it’s also easier to issue revocation lists when you don’t have to worry about bricking everyone’s hardware. So I have no idea which way that balance tilts.
They try to present it as “detecting abuse”, but it’s literally just “allow servers to block non-verified browers”(in other words google blocking access to their services for non-chrome users(the people proposing it work for google)).
And as always these types of asshats always shit all over anyone using accessbility tools(or don’t even consider them in the first place, which amounts to the same thing).
i personally don’t understand why companies overlook accessbility, is it to save profits?
why did you waste your time asking that question when you already knew the answer?
It’s always the profits!!!
Removed by mod
pretty much yes to keys and hashes. Just think HDCP and HDMI
That said, I imagine it’ll have to be easier to hack software that isn’t embedded in hardware. but it’s also easier to issue revocation lists when you don’t have to worry about bricking everyone’s hardware. So I have no idea which way that balance tilts.
Very much the latter.
“Listen, if we didn’t think about it, it’s clearly not important.”