4 ms·
but attempting to add DRM to an open standard is!
by chii 10y ago
but attempting to add DRM to an open standard is!
- yrro 10y agoBlame the content producers who insist that distributors 'protect' their content with DRM. Distributors aren't going to leave that money on the floor.
- syshum 10y agoWhy not blame both, as both are to blame. W3C is more to blame that all of them, as they have violated their mission statement with EME and DRM
- yrro 10y agoI guess I just don't see the harm. If EME standardization did not take place at W3C, I think it would take place at another standards organization, or privately between content distributors and browser developers. Either way, it still happens and nothing is materially different.
- syshum 10y agoIf I go to a site that is "HTML5 Compatible" I should not have to worry if my "HTML5 Browser" has all the proper binary blobs and approvals to support the content. If something is standard complaint it should work for all platforms that support the standard not just the Billion dollar corporations that paid to get their technology included into the standard
- lima 10y ago"Lesser of two evils". I prefer a nicely sandboxed and secured EME plugin over the insecure and clunkly silverlight pipelight trickery that was necessary before. Blame the media industry for forcing it.
- throwaway2048 10y agoOr we can blame google for gleefully going along too.
- mrighele 10y agoGoogle _is_ part of the media industry.
- chippy 10y agoIt's part of the advertising industry who's clients include the media industry.
- mrighele 10y agoTrue, but I was thinking more about the part where they sell music streaming services (Google Play Music, YouTube Red). Maybe I am wrong since they are not producers, but I considered this as being part of the media industry.
- hlandau 10y agoI don't think so. If Google was only implementing DRM to tick boxes, they wouldn't be implementing "extracurriculars" like hardware-based DRM on ChromeOS devices. They wouldn't own the very DRM company whose product they're peddling, a company which advertises to the very industry which is supposedly forcing Google's hand. http://www.widevine.com/ http://www.widevine.com/ Take a look at this page and search for 'HW_SECURE_ALL': http://www.widevine.com/product_news.html http://www.widevine.com/product_news.html Now, what exactly is the point in implementing a more secure DRM variant (which as far as I can tell uses remote attestation) if content remains available to more 'vulnerable' platforms? We even have a potential lockin motive by Google here, too. I can see it now: "Only available on ChromeOS."
- Buge 10y agoDid you know that Netflix only supports up to 720p on Chrome and Firefox? Because the DRM in those is easy to circumvent. People want higher than 720p, so browsers implement better DRM.