3 ms·
You don't see in what sense forcing the implementation of DRM into an open standard (HTTP in a broad sense, which includes HTML, JS, etc.), that has been develo
by pikzen 10y ago
You don't see in what sense forcing the implementation of DRM into an open standard (HTTP in a broad sense, which includes HTML, JS, etc.), that has been developed for the past decades in a rather open way so your company can keep making profits could be "freeloading"? Not to mention setting it up in such a way that their part of the web is broken if for some reason you do not have their blessing for their DRM.
Netflix came in and screwed over everyone, in a way that is just as bad as Flash.
Sure, use the TCP/IP stack. Send your data over the internet. Make your own software based on that, it's just a transport layer and it screws no one else. Except they seem to be pretty damn awful at it, considering how comically bad all their desktop apps are.
- tptacek 10y agoNo, I don't. Can you help me understand? Netflix isn't preventing you from using any of the open standards already implemented in a browser.
- pikzen 10y agoNo, they're not. However, the standard itself is now tainted with this. By forcing their way into the standard with EME, yes, they did. You cannot implement the full standard without getting their blessing. They profited from the entire work done by hundreds of persons on an open standard, and implemented a proprietary solution on top of it. And made it part of the standard.