I still think that EME were a mistake for web standards to implement. I disable them by default and yet see widevine requests as part of analytics, the occasional bot captcha, and other inappropriate locations all the time. I really just wish the whole thing would bog off - its anti consumer and approving the standard was I think a really foolish mistake. At least Firefox has an "off" button. Would that it was off by default.
>its anti consumer and approving the standard was I think a really foolish mistake.
The alternative is that Netflix et. al can't be played on firefox and you need to install chrome just to watch it, which weakens firefox's market share even more.
And until today, it would've meant having to boot macOS or Windows to watch Netflix on an aarch64 device, regardless of browser choice. (In practice it has been possible for longer, due to workarounds that were largely only possible due to the standardised EME interface)
I still think that EME were a mistake for web standards to implement. I disable them by default and yet see widevine requests as part of analytics, the occasional bot captcha, and other inappropriate locations all the time. I really just wish the whole thing would bog off - its anti consumer and approving the standard was I think a really foolish mistake. At least Firefox has an "off" button. Would that it was off by default.
>its anti consumer and approving the standard was I think a really foolish mistake.
The alternative is that Netflix et. al can't be played on firefox and you need to install chrome just to watch it, which weakens firefox's market share even more.
And until today, it would've meant having to boot macOS or Windows to watch Netflix on an aarch64 device, regardless of browser choice. (In practice it has been possible for longer, due to workarounds that were largely only possible due to the standardised EME interface)