Language Selection

English French German Italian Portuguese Spanish

W3C Condemned Over DRM

Filed under
Web
  • HTML5 DRM finally makes it as an official W3C Recommendation

    The World Wide Web Consortium (W3C), the industry body that oversees development of HTML and related Web standards, has today published the Encrypted Media Extensions (EME) specification as a Recommendation, marking its final blessing as an official Web standard. Final approval came after the W3C's members voted 58.4 percent to approve the spec, 30.8 percent to oppose, with 10.8 percent abstaining.

  • Electronic Frontier Foundation Resigns From W3C Over Encrypted Media Extensions DRM

    [...] The W3C is a body that ostensibly operates on consensus. Nevertheless, as the coalition in support of a DRM compromise grew and grew — and the large corporate members continued to reject any meaningful compromise — the W3C leadership persisted in treating EME as topic that could be decided by one side of the debate. In essence, a core of EME proponents was able to impose its will on the Consortium, over the wishes of a sizeable group of objectors — and every person who uses the web. The Director decided to personally override every single objection raised by the members, articulating several benefits that EME offered over the DRM that HTML5 had made impossible.

  • An open letter to the W3C Director, CEO, team and membership

    Despite the support of W3C members from many sectors, the leadership of the W3C rejected this compromise. The W3C leadership countered with proposals — like the chartering of a nonbinding discussion group on the policy questions that was not scheduled to report in until long after the EME ship had sailed — that would have still left researchers, governments, archives, security experts unprotected.

    The W3C is a body that ostensibly operates on consensus. Nevertheless, as the coalition in support of a DRM compromise grew and grew — and the large corporate members continued to reject any meaningful compromise — the W3C leadership persisted in treating EME as topic that could be decided by one side of the debate. In essence, a core of EME proponents was able to impose its will on the Consortium, over the wishes of a sizeable group of objectors — and every person who uses the web. The Director decided to personally override every single objection raised by the members, articulating several benefits that EME offered over the DRM that HTML5 had made impossible.

    But those very benefits (such as improvements to accessibility and privacy) depend on the public being able to exercise rights they lose under DRM law — which meant that without the compromise the Director was overriding, none of those benefits could be realized, either. That rejection prompted the first appeal against the Director in W3C history.

    [...]

    We will renew our work to battle the media companies that fail to adapt videos for accessibility purposes, even though the W3C squandered the perfect moment to exact a promise to protect those who are doing that work for them.

  • World Wide Web Consortium abandons consensus, standardizes DRM with 58.4% support, EFF resigns

    In July, the Director of the World Wide Web Consortium overruled dozens of members' objections to publishing a DRM standard without a compromise to protect accessibility, security research, archiving, and competition.

  • EFF quits W3C over decision to accept EME as Web standard

    The Electronic Frontier Foundation has resigned from the World Wide Web Consortium after the latter announced it was accepting the published Encrypted Media Extensions as a Web standard.

  • Christopher Allan Webber: DRM will unravel the Web

    I'm a web standards author and I participate in the W3C. I am co-editor of the ActivityPub protocol, participate in a few other community groups and working groups, and I consider it an honor to have been able to participate in the W3C process. What I am going to write here though represents me and my feelings alone. In a sense though, that makes this even more painful. This is a blogpost I don't have time to write, but here I am writing it; I am emotionally forced to push forward on this topic. The W3C has allowed DRM to move forward on the web through the EME specification (which is, to paraphrase Danny O'Brien from the EFF, a "DRM shaped hole where nothing else but DRM fits"). This threatens to unravel the web as we know it. How could this happen? How did we get here?

    Like many of my generation, I grew up on the web, both as a citizen of this world and as a developer. "Web development", in one way or another, has principally been my work for my adult life, and how I have learned to be a programmer. The web is an enormous, astounding effort of many, many participants. Of course, Tim Berners-Lee is credited for much of it, and deserves much of this credit. I've had the pleasure of meeting Tim on a couple of occasions; when you meet Tim it's clear how deeply he cares about the web. Tim speaks quickly, as though he can't wait to get out the ideas that are so important to him, to try to help you understand how wonderful and exciting this system it is that we can build together. Then, as soon as he's done talking, he returns to his computer and gets to hacking on whatever software he's building to advance the web. You don't see this dedication to "keep your hands dirty" in the gears of the system very often, and it's a trait I admire. So it's very hard to reconcile that vision of Tim with someone who would intentionally unravel their own work... yet by allowing the W3C to approve DRM/EME, I believe that's what has happened.

More in Tux Machines

GIMP, More Awesome Than I Remember

For what seems like decades, GIMP (Graphic Image Manipulation Program) has been the de facto standard image editor for Linux. It works well, has many features, and it even supports scripting. I always have found it a bit clumsy, however, and I preferred using something else for day-to-day work. I recently had the pleasure of sitting at a computer without an image editor though, so I figured I'd give GIMP another try on a non-Linux operating system. See, the last time I tried to use GIMP on OS X, it required non-standard libraries and home-brew adding. Now, if you head over to the GIMP site, you can download a fully native version of GIMP for Windows, OS X and Linux. Read more

Linux 4.13.9

I'm announcing the release of the 4.13.9 kernel. All users of the 4.13 kernel series must upgrade. The updated 4.13.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.13.y and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-st... Read more Also: Linux 4.9.58 Linux 4.4.94 Linux 3.18.77

Linux 4.14-rc6

So rc6 is delayed, not because of any development problems, but simply because the internet was horribly bad my usual Sunday afternoon time, and I decided not to even try to fight it. And by delaying things, I got a couple more ull requests in from Greg. Yay, I guess? rc6 is a bit larger than I was hoping for, and I'm not sure whether that is a sign that we _will_ need an rc8 after all this release (which wouldn't be horribly surprising), or whether it's simply due to timing. I'm going to leave that open for now, so just know that rc8 _may_ happen. Read more Also: Linux 4.14-rc6 Released: Linux 4.14 Kernel Final In 2~3 Weeks

What Will the Ubuntu 18.04 Name ‘B’?