2 ms·
Strictly speaking, Widevine isn't a standard - the web standards tracks really don't allow for it. Hell, they couldn't even agree on a single baseline video sta
by kmeisthax 6y ago
Strictly speaking, Widevine isn't a standard - the web standards tracks really don't allow for it. Hell, they couldn't even agree on a single baseline video standard. The only part of web standards that even covers DRM is EME, which just specifies a way for JavaScript to negotiate content decryption with a DRM plugin. It specifies no standard DRM, and it can't do that, because DRM by it's very nature is not standardizable - or, more specifically, standardized DRM is ineffective. You can totally write video DRM in JavaScript using Media Source Extensions. You'll just have no actual technical control over where the video goes after it's been decrypted; that's why they want compiled binaries that have to be distributed as browser plugins.
- Wowfunhappy 6y agoWhoops, I was getting Widevine and EME confused! Thank you for the correction, I've edited my comment.
- est31 6y ago> It specifies no standard DRM The w3c spec does specify the clearkey DRM plugin as mandatory to implement, but as the name says, the encryption keys are not hidden in any fashion from users, so most deployments use one of the proprietary plugins.