Stories
Slash Boxes
Comments

SoylentNews is people

posted by takyon on Tuesday September 19 2017, @12:37AM   Printer-friendly
from the community-consensus dept.

Submitted via IRC for boru

Dear Jeff, Tim, and colleagues, In 2013, EFF was disappointed to learn that the W3C had taken on the project of standardizing "Encrypted Media Extensions," an API whose sole function was to provide a first-class role for DRM within the Web browser ecosystem. By doing so, the organization offered the use of its patent pool, its staff support, and its moral authority to the idea that browsers can and should be designed to cede control over key aspects from users to remote parties.

[...] 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.

[...] We believe they will regret that choice. Today, the W3C bequeaths an legally unauditable attack-surface to browsers used by billions of people. They give media companies the power to sue or intimidate away those who might re-purpose video for people with disabilities. They side against the archivists who are scrambling to preserve the public record of our era. The W3C process has been abused by companies that made their fortunes by upsetting the established order, and now, thanks to EME, they'll be able to ensure no one ever subjects them to the same innovative pressures.

[...] Effective today, EFF is resigning from the W3C.

Thank you,

Cory Doctorow
Advisory Committee Representative to the W3C for the Electronic Frontier Foundation

Source: https://www.eff.org/deeplinks/2017/09/open-letter-w3c-director-ceo-team-and-membership


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Tuesday September 19 2017, @09:35AM

    by Anonymous Coward on Tuesday September 19 2017, @09:35AM (#570126)

    So, you'd rather stuff Verisigns coffers than the MAFIAAs?

    FSM No!
    If people want to be fleeced royally for a 'chain of mistrust' certificate for encrypted traffic for commerce etc then they stick to the current web and browsers.

    Unless you propose to make DANE a requirement - the current EME supporting browsers refuse to support DANE

    What I'm thinking is we fork a browser codebase anyway, strip all the crap out of it, so DANE would be a solution, at least, short term.
    The point is, we fork..and end up with (crudely) what is now a commercial WWW and browsers capable of accessing that content, and a forked browser sans DRM etc capable of accessing a seperate non-commercial WWW..same protocol, same html, same server software, different port number. Yes it means running two browsers, but some of us already run more than that thanks to the way content on some sites borks depending on which browser you use. If, after this creation, there's a divergence between the way the commercially driven W3C web develops and the FTW3C web develops, then all the better.

    Of course, there is nothing we can do to stop them trying to pollute any new scheme with their crap, nature of the beast I'm afraid.

    (And no, let's encrypt is not an answer..)

    Tell me about it!, cumbersome isn't the word, don't think there is a word in the english language invested with enough invective to sum up my feelings about the process...

    As I've avoided any serious network related jiggery-pokery for a couple of decades now, I think I'll have a trawl through the current browser lists and codebases for inspiration.