Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Back for a limited time - Get 15% off sitewide on Slashdot Deals with coupon code "BLACKFRIDAY" (some exclusions apply)". ×

Submission + - What's actually wrong with DRM in HTML5? (

kxra writes: The Free Culture Fondation has posted a thorough response to the most common and misinformed defenses of the W3C's Extended Media Extensions (EME) proposal to inject DRM into HTML5. They join the EFF and FSF in a call to send a strong message to the W3C that DRM in HTML5 undermines the W3C’s self-stated mission to make the benefits of the Web “available to all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability.” The FCF counters the three most common myths by unpacking some quotes which explain that 1. DRM is not about protecting copyright. That is a straw man. DRM is about limiting the functionality of devices and selling features back in the form of services. Second, that DRM in HTML5 doesn’t obsolete proprietary, platform-specefic browser plug-ins; it encourages them. And third, that the Web doesn’t need big media; big media needs the Web.
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

What's actually wrong with DRM in HTML5?

Comments Filter:

At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.