6 ms·
The Web is going to get DRM one way or another. Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with pr
by bitwize 13y ago
The Web is going to get DRM one way or another.
Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with proprietary plug-ins that only work in Windows and Internet Explorer.
- kunai 13y ago> The Web is going to get DRM one way or another Why should it have to?
- betterunix 13y ago"The Web is going to get DRM one way or another." Says who?
- vetinari 13y agoAnd the difference between your two options is exactly what? Except that the first one is blessed by W3G?
- mikeash 13y agoI vote for the hard way.
- w1ntermute 13y agoSo do I. That way will mean that I will probably never be able to use it on my (Linux) laptop, but that's fine, because I don't want to use something with DRM anyway. Torrents work just fine until the movie industry learns what the music industry learned the hard way.
- icebraining 13y agoThe DRM proposals required binary blobs too for the actual decryption, so you'd probably be unable to use it on Linux either way.
- w1ntermute 13y agoRight, and so I'd rather see the W3C not compromise its integrity.
- sbuk 13y agoThe minute you suggest torrenting media is the minute you lose the moral high-ground. You aren't owed this stuff, neither are you entitled to it. If you don't agree with the way media is distributed, don't consume it. By torrenting the media, you are playing into the proponents of DRMs hands.
- lucian1900 13y agoI still think it's irrelevant. DRM doesn't stop casual copyright infringement anyway. It's only ever used to control distributors (in this case the likes of Netflix), but that doesn't make much sense to me anyway, since they have expensive-to-breach contracts with them.
- sbuk 13y agoA downvote? Care to explain?
- nitrogen 13y agoMoral high ground -- closely related to the tu quoque fallacy.
- sbuk 13y agoThat'd be Argumentum ad logicam. The 'Torrents work just fine until the movie industry learns what the music industry learned the hard way.' approach is bordering on a two wrongs make a right fallacy itself.
- ivanca 13y agoIf those are the only options I vote for proprietary plugins; those are way easier to block.
- wmf 13y agoTo be clear, EME is not really a standard agreed upon across vendors. It's more of a meta-standard. There will be no CDM that works in 90% of browsers, so EME would lead to fragmentation just as bad or worse than what we have today.
- lambda 13y agoThe Web has DRM, implemented in proprietary plugins: Flash (and to a lesser degree, Silverlight). And this proposal involves DRM implemented with proprietary plugins (known as CDMs). There is no requirement that CDMs be available across platforms, on open operating systems, available to license by any vendor. The CDMs are the new proprietary plugins, they just happen to do less than Flash, leaving more of it up to the browser. Is it really so much better to trade one proprietary form of DRM for another? What does that actually get us? More crappy services, where Hollywood decides on a month by month basis which particular services get to offer its content, so you need to sign up for 5 different services just to watch all of the content that you watch? And each one of them supports different set-top boxes, doesn't work on open platforms, and restricts you from backing up media that you have bought? This isn't improvement; this is just wanting to get browser vendors to implement anti-features that users object to, instead of getting Adobe to do it.
- Drakim 13y agoThe worst part is that Flash and Java aren't going to go away anytime soon either. You basically have to have both, and the web will be a lot harder to navigate on anything but a Windows machine.
- yzhengyu 13y agoI am skeptical of any value in having "standards" agreed for this for consumers which would be any different from having third party plugins. If you want your content to be protected, fine, you can go back to using third party plugins. Then users will have a clear choice on whether to consume your content.
- belorn 13y agoDRM: Software with the intent to take control with force over someones else computer. Sorry but there is nothing intrinsic valuable about DRM in the web, in the exact same way that any other form of malware is not intrinsic valuable to the web. Just because its current legal to offer media products with malware embedded, doesn't make it a logical choice to include in a web standard that describes an open web of cooperating nodes.
- duncan_bayne 13y agoThe EME proposal by the W3C is specifically intended to enable just what you describe: proprietary plug-ins that only work in particular browsers. One of the primary sponsors of the EME proposal is Netflix, who are already building exactly what you describe. I've addressed this issue - a misconception that at least some on the W3C hold - in detail here: http://www.w3.org/QA/2013/05/perspectives_on_encrypted_medi.html#c4843118 http://www.w3.org/QA/2013/05/perspectives_on_encrypted_medi....
- mtgx 13y agoThe DRM will change nothing about platform interoperability. If anything, it will probably make the situation worse. For DRM to work, someone needs to control that DRM (which means plugins) - preferably as few people as possible. You can't really have "open DRM" or anything like that, which means "HTML5 DRM5" is completely inconsistent and conflictual with the values of the web, and what W3C is supposed to stand for. The reason there even seems to be a side that is "pro HTML5 DRM" is because they think: 1) it will make Netflix and such really cross-platform 2) you won't have to use "nasty plugins" like Flash or Silverlight But none of the two is really true. You will have plugins, they will just be at the OS level, and good luck getting Netflix to work on new operating systems such as Ubuntu Touch, Sailfish, FF OS, Tizen, and so on - unless the company behind them can make partnerships with the content companies or content distributors like Netflix.
- shmerl 13y ago> The Web is going to get DRM one way or another. Wrong. The Web already has DRM - Silverlight and other junk. The subject is about not dragging this garbage into the HTML standard. > Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with proprietary plug-ins that only work in Windows and Internet Explorer. EME won't make DRM "easier" for users - it will still require closed source black box modules which will never work with open source browsers. It might make it easier for Netflix and co. who push this idiocy onto the web. But it's their problem, users and the Web should not oblige them with comfortable proliferation of unethical approaches. If anything it should be made harder, to give more incentives to avoid it.
- vy8vWJlco 13y agoYou've hit it: standardization speeds proliferation, and there's no reason at all for the W3C to speed the proliferation of lock-in, effectively supporting a digital arms race. There may be rationalizations for DRM by certain individuals or companies, just as there are "reasons" from warlords to expand their empires, but none of them necessarily benefit everyone justly. For that matter, there are straight-forward arguments that DRM cannot benefit everyone justly (for example, DRM prevents users from controlling their equipment, or it prevents innovation thereby distorting the market), and if it can't: why on earth is it worth promoting? Saying DRM should be in HTML 5 is like saying the freedom to murder should be a human right. IMHO, both cross a line that make them (clearly) no longer objectively in the public interest. The ability to embed plugins is as close to that line as necessary - and that has already been standardized. There is no reason to go farther than that and to proliferate a tool that is not in the public interest (for all intents and purposes a "weapon" against the public).
- fafner 13y agoWe can NOT do this the easy way! Please read the W3C proposal. The proposal is NOT an alternative to proprietary plug-ins but rather a proposal to introduce proprietary plug-ins into HTML5. DRM can't be free software because you could simply change it to write the data to your disk and recompile it. This proposal is turning HTML5 into "New Flash" because the CDM will have to do the decoding and rendering of frames. This is not only dangerous to freedom but this is dangerous to all the achievements and advances in HTML5 and the web stack. https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
- jlgreco 13y agoProprietary plugins sounds good to me. Working with nastier code will be their penance.
- duncan_bayne 13y agoThat's incorrect. The proposed EME standard merely specifies the interop between Javascript and the CDM. The CDM will in almost all cases be a platform-specific, proprietary, closed-source binary blob. _Please_ do not buy in to the idea that including EME in HTML5 will reduce the platform dependence of DRM solutions.
- miles 13y agoReminds me of this exchange between Dwight and Ryan on The Office: --- Dwight: Okay, I’m going to need to search your car. Give me your keys. Ryan: I am not giving you my keys. Dwight: Don’t make me do this the hard way. Ryan: What’s the hard way? Dwight: I go down to the police station on my lunch break. I tell the police officer — I know several — what I suspect you may have in your car. He requests a hearing from a judge and obtains a search warrant. Once he has said warrant, he will drive over here and make you give him the keys to your car, and you will have to obey him. Ryan: Yeah, let’s do it that way. --- Note to Hollywood: Yeah, let's do it the hard way.
- GhotiFish 13y agothat second way? that's the way I want. I want that second way to hurt, alot. Alot alot. I want the way DRM gets onto the web to be the same vector malware gets onto computers. I want this to suck for DRM, it should suck. It should be painful to give up your rights. It SHOULD hurt.