W3C abandons consensus, standardizes DRM, EFF resigns

Re:W3C abandons consensus, standardizes DRM, EFF resigns by eridius on Tuesday September 19, 2017 @04:04AM (#15282627)

But it is in the interests of the common user. It's absolutely beneficial for browsers to have a standardized API for this stuff instead of non-standard plugin hell. People like you seem to think that if the W3C rejected DRM then sites would stop using it (and hence this being for the benefit of the user). But that belief is hopelessly naive. Sites like Netflix are never going to stop using DRM. They're contractually obligated to use it. Without EME, Netflix has to rely on plugins like Silverlight. With EME, Netflix can ship an HTML5 experience that works everywhere. That's good for users.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by bzbarsky on Tuesday September 19, 2017 @09:50AM (#15284553)

The EFF wasn't pushing for "don't standardize EME". It was pushing for "add a clause to the EME standard that prevents it being abused in certain specific user-hostile ways". In particular, it would prevent it being abused to prevent actions by users that are perfectly legal under existing copyright law.

This is a complex topic with a lot of nuance to discuss, but I don't see how misrepresenting the EFF's position helps the discussion in any way.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by ctrl-j on Tuesday September 19, 2017 @10:40AM (#15285034)

> People like you seem to think that if the W3C rejected DRM then sites would stop using it (and hence this being for the benefit of the user).

When did I say that? Specifically? Why did you assume I'm ignorant of the way corporations operate?

That's on you. Not me.

> It's absolutely beneficial for browsers to have a standardized API for this stuff instead of non-standard plugin hell.

Except the standard that they adopted is not friendly to the end-user. So "Non standard plugin hell" becomes "standard DRM hell."

A while back Widevine stopped working for me after an update. Uninstalling and reinstalling didn't work. End result? Almost no video played in my browser. You know what still would have worked? Pirate Bay.

You can spin it however you want. DRM is good for content providers. It's not good for users.

If Netflix requires DRM - so be it. They've got good engineers, they can provide a DRM plugin that you have to use. Or a standalone player. If a service doesn't have good engineering, their service will suffer.

It doesn't need to be a part of the open web standard.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by Furmark on Wednesday September 20, 2017 @09:21AM (#15293408)

> A while back Widevine stopped working for me after an update. Uninstalling and reinstalling didn't work. End result? Almost no video played in my browser.

You were doing something wrong perhaps. I have never installed widevine, yet all videos online worked for me. Try uninstalling it completely.

[ Parent | on HN ]