LXer: BBC Attacks the Open Web, GNU/Linux in Danger
Syndicated Linux NewsThis forum is for the discussion of Syndicated Linux News stories.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
LXer: BBC Attacks the Open Web, GNU/Linux in Danger
Published at LXer:
The Web is one of the most dramatic demonstrations of the power of openness, alongside free software, which not coincidentally runs most of it and the rest of the Internet. At the heart of that openness lies HTML, a completely open way of sharing information. So what would be a really stupid thing you could do to try to throttle that openness and innovation? Why, yes: adding DRM to HTML so that you can lock down Web page elements:
With HTML5 replacing Flash this was to be expected, the content industry wants to have DRM and I doubt that we can do much to prevent that.
But instead of hoping that someone starts a petition, why don't you make the first move and start it? I also would sign it.
This specification does not define a content protection or Digital Rights Management system. Rather, it defines a common API that may be used to discover, select and interact with such systems as well as with simpler content encryption systems. Implementation of Digital Rights Management is not required for compliance with this specification: only the simple clear key system is required to be implemented as a common baseline.
I will wait until they make a move to actually mandate DRM be included in the standard.
I know that even having the ability to include it is not that good, but they will want it, so I don't think I can stop that.
Last edited by H_TeXMeX_H; 02-16-2013 at 11:45 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.