www/server/staging/proprietary proprietary-frau...

[Félicien PILLOT]

CVSROOT:        /web/www
Module name:    www
Changes by:     Félicien PILLOT <felandral>    19/08/15 12:44:18

Added files:
        server/staging/proprietary: proprietary-fraud.html 
                                    proprietary-obsolescence.html 

Log message:
        Add new pages in staging area:
        proprietary/proprietary-fraud.html (www-discuss 2019-08-07)
        .proprietary/proprietary-obsolescence.html (www-discuss 2019-08-09)

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/proprietary/proprietary-fraud.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/proprietary/proprietary-obsolescence.html?cvsroot=www&rev=1.1

Patches:
Index: proprietary-fraud.html
===================================================================
RCS file: proprietary-fraud.html
diff -N proprietary-fraud.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ proprietary-fraud.html      15 Aug 2019 16:44:18 -0000      1.1
@@ -0,0 +1,108 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.87 -->
+<!-- 
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+                  Please do not edit <ul class="blurbs">!
+    Instead, edit /proprietary/workshop/mal.rec, then regenerate pages.
+           See explanations in /proprietary/workshop/README.md.
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-->
+<!-- 4. [Software] Update the actual information according to your project,
+           such as mailing lists, project locations, and maintainer's name.
+        [Article]  Replace everything between </h2> and
+           </div><!-- for id="content" with the text of the article, making
+           sure it follows the stylesheet guidelines:
+           https://www.gnu.org/server/standards/gnu-website-guidelines.html -->
+
+<!-- 5. Check that the text you added is XHTML-1.0 compliant (<br /> rather
+        than <br>, <p> rather than <P>, "&amp;" rather than "&", etc.)
+        In doubt, please refer to the W3C recommendations:
+        https://www.w3.org/TR/xhtml1 -->
+
+<!-- 6. If you'd like to use HTML5-specific features such as <video>,
+        replace the top line with
+        <!--#include virtual="/server/html5-header.html" -->
+
+<!-- 7. Delete the present instructions. -->
+
+<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
+<title>Proprietary Fraud - GNU Project - Free Software Foundation</title>
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary Fraud</h2>
+
+<p><em>Description to add…</em></p>
+
+<ul class="blurbs">
+  <li>
+    <p>A game published on
+      Facebook <a 
href="https://www.revealnews.org/article/so-your-child-racked-up-unwanted-credit-card-charges-playing-video-games-now-what/";>encourages
+      children to spend</a> large amounts of money without this being
+      explicitly understandable to them.</p>
+  </li>
+</ul>
+
+</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
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- 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 4.0.  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; 2019 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/08/15 16:44:18 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: proprietary-obsolescence.html
===================================================================
RCS file: proprietary-obsolescence.html
diff -N proprietary-obsolescence.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ proprietary-obsolescence.html       15 Aug 2019 16:44:18 -0000      1.1
@@ -0,0 +1,110 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.87 -->
+<!-- 
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+                  Please do not edit <ul class="blurbs">!
+    Instead, edit /proprietary/workshop/mal.rec, then regenerate pages.
+           See explanations in /proprietary/workshop/README.md.
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-->
+<title>Proprietary Obsolescence - GNU Project - Free Software 
Foundation</title>
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary Obsolescence</h2>
+
+<p><a href="/proprietary/proprietary.html">Other examples of proprietary 
malware</a></p>
+
+<p>Nonfree (proprietary) software is very often malware (designed to
+  mistreat the user). Nonfree software is controlled by its
+  developers, which puts them in a position of power over the
+  users; <a href="/philosophy/free-software-even-more-important.html">that
+  is the basic injustice</a>. The developers often exercise that power
+  to the detriment of the users they ought to serve.</p>
+
+<p>As in any human activity, informatics has an environmental
+  impact. When the software is proprietary, it is even more harmful to
+  the planet because it encourages the user to change devices when
+  they are no longer updated, or to buy back other components when
+  they are no longer supported, or to discard a defective one that, if
+  it was free, would be repairable.</p>
+
+<p>Here are examples of proprietary software designed to reduce the
+  ordinary life span of the devices with which they are associated or
+  to make them irreparable. Users cannot avoid this constraint and is
+  forced to replace the material because they have no control over
+  it.</p>
+
+<ul class="blurbs">
+  <li id="M201908150">
+    <p>Apple is putting DRM on iPhone batteries, and the system
+      proprietary
+      software <a 
href="https://www.vice.com/en_us/article/59nz3k/apple-is-locking-batteries-to-specific-iphones-a-nightmare-for-diy-repair";>turns
+      off certain features when batteries are replaced other than by
+      Apple.</a></p>
+  </li>
+</ul>
+
+</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
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- 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 4.0.  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; 2019 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2019/08/15 16:44:18 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>