Hacker News new | past | comments | ask | show | jobs | submit login

As long as major content providers want it, there is going to be DRM one way or the other. It is not in fact within W3C's power to prevent that.

The only influence W3C has on DRM is the form it takes: is it implemented through (somewhat) standardized means, using the building blocks of web technology provided by browser vendors, or is it implemented through black-box plugins that we know, after 15+ years of experience, end-users will install.

I have never really understand the role W3C is supposed to play as a pressure point for DRM.




> As long as major content providers want it, there is going to be DRM one way or the other.

It's not so simple. Content providers want to distribute on the web. Yes, they have the ability to just pull out and avoid that space entirely, but that's not good for them. The web needs their content, but they also need the web.

In other words, the W3C saying no to DRM would apply pressure in the right direction.

That suggests positions can be shifted. And we have seen them shift before, with music downloads, which used to be DRM'ed, but no longer are.


Except the web doesn't really need their content. The web exists and will continue to flourish regardless of the availability of commercial hollywood films and television on it. It got this far without ruining open standards, and the MAFIAA lobby forced DRM bullshit upon it because they fear for their long term viability.

That is a sign they were losing the battle, and they absolutely were with the rise of youtube, facebook video, twitch, etc - alternative video sources were / are starting to get professional, with many major youtube channels having production crew and proper film / showmaking.

The web would have been absolutely fine without them, but they knew they would not survive without the web long term, especially internationally.


In exactly what way would the W3C "saying no to DRM" apply any pressure at all? The W3C cannot ban plugins.


I have never really understood why people continue to instist that EME is not filled with "black box plugins"

EME is enabling black box plugins, simply calling them "extensions" does not magically make them something other than a Black Box binary blobs loaded by the browser.

Functionally they are really no different than the Flash or Silverlight plugin, they simply contain less stuff and are more specialized

W3C is suppose to be promoting the Open Web, that means open regardless of Operating System, Browser Choice, or Nation

EME violates all 3 of those by locking you down to only commercial, or commercially supported browsers (no open source EME, even Mozilla had to pay Adobe to create them a Commercial non-free plugin for FF)

Free/Libre Operating Systems are Excluded from the new w3c vision of the web

EME/DRM enables Geo-fencing of content

In short the EME is a complete bastardization of the w3c mission




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: