[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/philosophy proprietary-drm.html

From: Richard M. Stallman
Subject: www/philosophy proprietary-drm.html
Date: Fri, 21 Mar 2014 12:54:08 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       14/03/21 12:54:08

Added files:
        philosophy     : proprietary-drm.html 

Log message:
        Initial version.


Index: proprietary-drm.html
RCS file: proprietary-drm.html
diff -N proprietary-drm.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ proprietary-drm.html        21 Mar 2014 12:54:07 -0000      1.1
@@ -0,0 +1,157 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.76 -->
+<title>Proprietary DRM - GNU Project - Free Software Foundation</title>
+<!--#include virtual="/philosophy/po/proprietary-sabotage.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary DRM</h2>
+<p>Here are examples of proprietary programs and systems that
+implement <em>digital restrictions management</em> (<acronym>DRM</acronym>):
+functionalities designed intentionally to restrict what users can do.
+These functionalities are also called <em>digital handcuffs</em>.
+<p>DRM is reinforced by
+censorship laws</a> that ban software (and hardware) that can break
+the handcuffs.  Instead of these laws, DRM ought to illegal.  Please
+support our campaign
+to <a href="http://DefectiveByDesign.org/";>abolish DRM</a>.
+<p><a href="http://science.opposingviews.com/kindle-drm-17841.html";>
+The Amazon Kindle has DRM</a>.  That article is flawed in that it
+fails to treat DRM as an ethical question; it takes for granted that
+whatever Amazon might do to its users is legitimate.  It refers to DRM
+as digital &ldquo;rights&rdquo; management, which is the spin term
+used to promote DRM.  Nonetheless it serves as a reference for the
+We refer to that product as the
+<a href="/philosophy/why-call-it-the-swindle.html"> Amazon Swindle </a>
+because of this and <a href="/philosophy/ebooks.html">
+other malicious functionalities</a>.
+<p><a href="http://arstechnica.com/apple/2007/08/aacs-tentacles/";>DRM
+in Windows</a>, introduced to cater to <a href="#bluray">Bluray</a>
+disks.  (The article talks about how the same malware would later be
+introduced in MacOS.  That had not been done at the time, but it was
+done subsequently.)
+in MacOS</a>.  This article focuses on the fact that a new model of
+Macbook introduced a requirement for monitors to have malicious
+hardware, but DRM software in MacOS is involved in activating the
+hardware.  The software for accessing Itunes is also responsible.
+<p><a href="https://www.eff.org/deeplinks/2008/02/adobe-pushes-drm-flash";>
+DRM in Flash Player</a>.
+DVDs and <a name="bluray">Bluray</a> disks have DRM</a>.
+<p>That page uses spin terms that favor DRM,
+including <a href="/philosophy/words-to-avoid.html#DigitalRightsManagement">
+digital &ldquo;rights&rdquo; management</a>
+and <a 
+and it claims that &ldquo;artists&rdquo; (rather than companies) are
+primarily responsible for putting digital restrictions management into
+these disks.  Nonetheless, it is a reference for the facts.
+<p>Every Bluray disk (with few, rare exceptions) has DRM &mdash; so
+don't use Bluray disks!
+DRM in Cars Will Drive Consumers Crazy</a>.
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2014 Free Software Foundation, Inc.</p>
+<p>This page is licensed under a <a rel="license"
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+<!--#include virtual="/server/bottom-notes.html" -->
+<p></p><p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2014/03/21 12:54:07 $
+<!-- timestamp end -->

reply via email to

[Prev in Thread] Current Thread [Next in Thread]