News for hackers. Stuff that matters.
Re:The W3C's plan for DRM in HTML5 is a betrayal for all web... by MatthewPhillips on Wednesday April 24, 2013 @07:27AM (#5600877)
> Take away what functionality? The ability to download audio/video?

The ability to download audio/video already exists in computers. DRM prevents you from doing what you want with the bits that are sent to you; hence it restricts native computer functionality.

> To be fair, this isn't. EME is just a way for people to create addons that leverage native encryption. The same is true of the current plugin system.

This is a red herring; EME only exists to facilitate DRM. EME was designed specifically with DRM in mind. There is no other use case. It's a convenient way for EME supporters to ignore the real issues, but it's valid to talk about a technology's real world uses when discussing its validity.

Re:The W3C's plan for DRM in HTML5 is a betrayal for all web... by cleverjake on Thursday April 25, 2013 @09:11PM (#5610934)
>>The ability to download audio/video already exists in computers.

Thank you for clarifying. I wasn't sure what you meant.

>> It's a convenient way for EME supporters to ignore the real issues, but it's valid to talk about a technology's real world uses when discussing its validity.

To be clear, I am not a supporter. I don't want it in the browser either. However, I don't understand how it is a red herring. Everything that is being proposed in EME is already possible in Flash and Silverlight, and those features only exist in those plugins for the same reason. Neither of them need file encryption in order to work as a platform - it is a feature so that people that want to have encrypted/licensed material on the internet can do so. You can write applications without them. But yet no one seems to care about it. I am wondering why that is