7 ms·
DRM encryption is a browser standard.
by shadowgovt 7y ago
DRM encryption is a browser standard.
- jachee 7y agoAren't "proprietary" and "standard" mutually exclusive?
- saagarjha 7y agoNope. You can have standardized proprietary technology: you may not be able to implement it, but a group of companies might.
- shadowgovt 7y agoExample; Z-Wave protocol.
- anoncake 7y agoPlease stop repeating that propaganda. The point of standards is to facilitate interoperability. DRM does the opposite so it can never be standardized, no matter what capitalist-run "standards" organizations say
- shadowgovt 7y agoYou can call it "propaganda," but it's documented right here. [https://www.w3.org/TR/encrypted-media/ https://www.w3.org/TR/encrypted-media/]. If Oauth2 is a standard without defining how authentication servers are implemented and requiring the implementation be disclosed, it's hard to claim EME is not also a standard in the same sense. A standard we don't like isn't propaganda.
- anoncake 7y agoHaving the EME specification distributed by the W3C appears to be a very effective method of propaganda. > A standard we don't like isn't propaganda. A "standard" that doesn't even attempt to fulfil the purpose of a standard is not a standard.
- shadowgovt 7y agoWhat purpose is it failing to fulfill? It outlines how to indicate media is encrypted and how decryptors can be surfaced by the user-agent. It doesn't indicate how decryption must happen, but OAuth2 doesn't indicate what standard an authorization server should use to authorize that a client matches a resource owner either.
- anoncake 7y ago> What purpose is it failing to fulfill? Here you are: > The point of standards is to facilitate interoperability. > but OAuth2 isn't the topic.
- shadowgovt 7y agoIt facilitates interoperability between content providers and user agents to convey and display encrypted media (without the need for one company to own both sides if that pipe, like in the Flash era). Much as OAuth2 facilitates authorization handshakes between services owned by different companies.
- anoncake 7y agoFacilitating DRM, which runs counter to interoperability, is exactly why EME isn't a standard. And please stop spamming your OAuth2 nonsense, it's off topic.
- shadowgovt 7y agoI keep bringing up OAuth2 because it's in a similar domain to EME. Authorization restricts access to resources that users are not supposed to be accessing (for whatever reason, be it privacy or they simply haven't paid to access it). Similarly, encryption restricts usage of resources in ways users are not supposed to use them (including having not paid for the privilege). It's not "counter to interoperability" that Google Drive won't fork over your documents to anyone who requests them without the right token. Your frustration isn't the technology, it's what it's used for. If you want to claim EME isn't a standard, clarify how it differs from OAuth2.