EFF Makes Formal Objection to DRM in HTML5
1–10 of 280 posts
Re: EFF Makes Formal Objection to DRM in HTML5
#2Here's a radical idea: If you don't want DRM on your website, don't put DRM on your website.
They are not making anyone use DRM against their will.
Re: EFF Makes Formal Objection to DRM in HTML5
#3The only true solution to the problem of DRM is to kill Hollywood. It's unlikely to happen, though. Many others have reiterated on this point, so I'm not going to waste my time iterating yet once more.
Re: EFF Makes Formal Objection to DRM in HTML5
#4The Web is going to get DRM one way or another.
Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with proprietary plug-ins that only work in Windows and Internet Explorer.
Re: EFF Makes Formal Objection to DRM in HTML5
#5Here's a radical idea: If you don't want DRM on your website, don't put DRM on your website. They are not making anyone use DRM against their will.
That's extremely narrow-minded.
First of all, the DRM is proprietary. Those using open-source browsers like Firefox or Chromium won't be able to view any sites that push DRM at their will; especially if it's integrated INTO the web standard itself. It doesn't only affect web developers, it affects users, and the fact that you can't see that is astonishing. I don't know whether to be appalled or amazed, to be honest.
Normally, when DRM is implemented, it has been done so through plugins and other proprietary solutions, but the core technologies in the web -- HTML, CSS, and JavaScript -- have been open, and they should stay open. Implementing proprietary DRM in an open standard is a slap in the face for Mozilla and Google, who want an open Web. And everyone else wants an open Web too, not just the big organizations.
And third, let's just face it -- DRM fucking sucks.
Re: EFF Makes Formal Objection to DRM in HTML5
#6The Web is going to get DRM one way or another. Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with proprietary plug-ins that only work in Windows and Internet Explorer.
> The Web is going to get DRM one way or another
Why should it have to?
Re: EFF Makes Formal Objection to DRM in HTML5
#7Here's a radical idea: If you don't want DRM on your website, don't put DRM on your website. They are not making anyone use DRM against their will.
This is kind of like saying, "The DVD CSS system is fine! You are not forced to use this DRM when you make a video DVD!" Why should the users be forced to deal with more of this nonsense?
The issue is not about websites it is about us. I do not want DRM on my computer, and I do not want to be excluded from the web as a result of that choice.
Re: EFF Makes Formal Objection to DRM in HTML5
#8Here's a radical idea: If you don't want DRM on your website, don't put DRM on your website. They are not making anyone use DRM against their will.
And equally you can use it even if it isn't in the standard.
Re: EFF Makes Formal Objection to DRM in HTML5
#9The Web is going to get DRM one way or another. Now we can do this the easy way, with standards that are agreed upon across vendors -- or the hard way, with proprietary plug-ins that only work in Windows and Internet Explorer.
"The Web is going to get DRM one way or another."
Says who?
Re: EFF Makes Formal Objection to DRM in HTML5
#10This objection, does a solution not help make.