Live data from Hacker News

W3C abandons consensus, standardizes DRM, EFF resigns

boingboing.net

1–10 of 1001 posts

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#3
post #2

So this is how the open web dies. Can we fork the W3C into a non-corporate puppet now?

We should simply start doing new standards through other organizations. There's no fundamental reason to float new standards through W3C rather than some other organization.

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#4
Basically, unless you are writing a browser with decent marketshare, you defacto have no voice in making the standards. Basically, the only voices that matter are Mozilla (Firefox), Apple (Safari), Google(Chrome), and Microsoft (Edge/Explorer). Despite what any standard says, web developers are going to go by the behavior of the browsers do. The only company on the list of browser makers that really has any desire to try to exclude DRM is Mozilla, and unfortunately, if they do that, the users will switch to the browser that makes watching Netflix easiest.

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#5

Basically, unless you are writing a browser with decent marketshare, you defacto have no voice in making the standards. Basically, the only voices that matter are Mozilla (Firefox), Apple (Safari), Google(Chrome), and Microsoft (Edge/Explorer). Despite what any standard says, web developers are going to go by the behavior of the browsers do. The only company on the list of browser makers that really has any desire to…

I would suggest not underestimating Mozilla's market influence.

It would be possible to create a browser that displays DRM content and ignores DRM. The only thing that content publishers could do is ban that browser. And then it would adapt to disguise itself as other browsers.

DRM on the web can only happen if all of the major players (that is, browser publishers) agree to play along.

I am very excited about this news, this is probably the most important news in weeks, and could impact the Internet for years to come.

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#6

Basically, unless you are writing a browser with decent marketshare, you defacto have no voice in making the standards. Basically, the only voices that matter are Mozilla (Firefox), Apple (Safari), Google(Chrome), and Microsoft (Edge/Explorer). Despite what any standard says, web developers are going to go by the behavior of the browsers do. The only company on the list of browser makers that really has any desire to…

This is really the issue. If we could convince media rightsholders that DRM is harmful and unnecessary then all of this heartache wouldn't be necessary.

I don't expect this to happen in my lifetime. Any slight glimmer of hope from Apple ditching DRM on iTunes has died as nobody else shows the slightest interest in following their lead.

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#8

Basically, unless you are writing a browser with decent marketshare, you defacto have no voice in making the standards. Basically, the only voices that matter are Mozilla (Firefox), Apple (Safari), Google(Chrome), and Microsoft (Edge/Explorer). Despite what any standard says, web developers are going to go by the behavior of the browsers do. The only company on the list of browser makers that really has any desire to…

I would suggest not underestimating Mozilla's market influence. It would be possible to create a browser that displays DRM content and ignores DRM. The only thing that content publishers could do is ban that browser. And then it would adapt to disguise itself as other browsers. DRM on the web can only happen if all of the major players (that is, browser publishers) agree to play along. I am very excited about this ne…

Wouldn't publishers just refuse to distribute keys to said browser?

Re: W3C abandons consensus, standardizes DRM, EFF resigns

#10
post #2

So this is how the open web dies. Can we fork the W3C into a non-corporate puppet now?

DRM was coming to browsers with or without the W3C’s blessing. In fact, it was already there via plugins and wasn’t going away. This has changed nothing except where the implementation is documented.

The hysteria over this is just ridiculous.

Post reply on HN