[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www licenses/gpl-howto.de.html licenses/po/gpl-...
|
From: |
GNUN |
|
Subject: |
www licenses/gpl-howto.de.html licenses/po/gpl-... |
|
Date: |
Tue, 29 May 2018 22:01:39 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 18/05/29 22:01:38
Modified files:
licenses : gpl-howto.de.html
licenses/po : gpl-howto.de-diff.html
philosophy : javascript-trap.it.html javascript-trap.uk.html
who-does-that-server-really-serve.it.html
who-does-that-server-really-serve.ja.html
who-does-that-server-really-serve.nl.html
who-does-that-server-really-serve.uk.html
philosophy/po : javascript-trap.uk-diff.html
Added files:
philosophy/po : javascript-trap.it-diff.html
who-does-that-server-really-serve.it-diff.html
who-does-that-server-really-serve.ja-diff.html
who-does-that-server-really-serve.nl-diff.html
who-does-that-server-really-serve.uk-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.de.html?cvsroot=www&r1=1.52&r2=1.53
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-howto.de-diff.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/javascript-trap.it.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/javascript-trap.uk.html?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.it.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.ja.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.nl.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.uk.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/javascript-trap.uk-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/javascript-trap.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.ja-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.nl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.uk-diff.html?cvsroot=www&rev=1.1
Patches:
Index: licenses/gpl-howto.de.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.de.html,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -b -r1.52 -r1.53
--- licenses/gpl-howto.de.html 18 Mar 2018 00:57:59 -0000 1.52
+++ licenses/gpl-howto.de.html 30 May 2018 01:59:09 -0000 1.53
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-howto.de.po">
+ https://www.gnu.org/licenses/po/gpl-howto.de.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-howto.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-howto.de-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-howto.en.html" -->
<!--#include virtual="/server/header.de.html" -->
<!-- Parent-Version: 1.84 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
<!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/server/outdated.de.html" -->
<h2>GNU-Lizenzen: Tipps zur Verwendung</h2>
<p>Dies ist eine kurze Erläuterung dessen, wie man ein Programm unter <b><a
@@ -389,7 +395,7 @@
<p class="unprintable"><!-- timestamp start -->
Letzte Ãnderung:
-$Date: 2018/03/18 00:57:59 $
+$Date: 2018/05/30 01:59:09 $
<!-- timestamp end -->
</p>
Index: licenses/po/gpl-howto.de-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-howto.de-diff.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- licenses/po/gpl-howto.de-diff.html 24 Jan 2018 03:59:36 -0000 1.2
+++ licenses/po/gpl-howto.de-diff.html 30 May 2018 01:59:44 -0000 1.3
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: <span
class="removed"><del><strong>1.77</strong></del></span> <span
class="inserted"><ins><em>1.84</em></ins></span> -->
+<!-- Parent-Version: 1.84 -->
<title>How to use GNU licenses for your own software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/licenses/po/gpl-howto.translist" -->
@@ -20,16 +20,12 @@
<p>This is a brief explanation of how to place a program under the <a
href="/licenses/gpl.html">GNU General Public License</a>, <a
-<span
class="removed"><del><strong>href="/licenses/lgpl.html">Lesser</strong></del></span>
-<span class="inserted"><ins><em>href="/licenses/lgpl.html">GNU
Lesser</em></ins></span> General Public License</a>, or <a
-<span
class="removed"><del><strong>href="/licenses/agpl.html">Affero</strong></del></span>
-<span class="inserted"><ins><em>href="/licenses/agpl.html">GNU
Affero</em></ins></span> General Public License</a>. For the
+href="/licenses/lgpl.html">GNU Lesser General Public License</a>, or
<a
+href="/licenses/agpl.html">GNU Affero General Public License</a>.
For the
<a href="/licenses/fdl.html">GNU Free Documentation License</a>,
we have
a <a href="/licenses/fdl-howto.html">separate page</a>.</p>
-<span class="removed"><del><strong><p>If you are looking for more
detailed</strong></del></span>
-
-<span class="inserted"><ins><em><p>For further</em></ins></span>
information, <span class="removed"><del><strong>consider
perusing</strong></del></span> <span
class="inserted"><ins><em>see</em></ins></span> our list
+<p>For further information, see our list
of <a href="/licenses/gpl-faq.html">frequently asked questions about
our licenses</a>.</p>
@@ -39,16 +35,14 @@
article explains why it may be better to use the ordinary GPL instead,
and how we would make the decision.</p>
-<span class="removed"><del><strong><p>Whichever
license</strong></del></span>
-
-<span class="inserted"><ins><em><p>Here's a brief summary of
what</em></ins></span> you <span
class="removed"><del><strong>plan</strong></del></span> <span
class="inserted"><ins><em>need</em></ins></span> to <span
class="removed"><del><strong>use,</strong></del></span> <span
class="inserted"><ins><em>do to release a program
+<p>Here's a brief summary of what you need to do to release a program
under one of our licenses:</p>
<ul>
<li>Get a copyright disclaimer from your employer or school.</li>
<li>Give each file the proper copyright notices. Make
sure <a href="/licenses/identify-licenses-clearly.html">to clearly
-identify which versions of</em></ins></span> the <span
class="removed"><del><strong>process</strong></del></span> <span
class="inserted"><ins><em>license users can use</a>.</li>
+identify which versions of the license users can use</a>.</li>
<li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
<li>Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
use that.</li>
@@ -57,16 +51,19 @@
<li>(If using the AGPL) make the program offer copies of its source
code.</li>
</ul>
-<p>This</em></ins></span> involves adding two elements to each source
file of your
+<p>This involves adding two elements to each source file of your
program: a copyright notice (such as “Copyright 1999 Terry
Jones”), and a statement of copying permission, saying that the
program is distributed under the terms of the GNU General Public
-License (or the Lesser <span class="inserted"><ins><em>GPL, or the
Affero</em></ins></span> GPL).</p>
+License (or the Lesser GPL, or the Affero GPL).</p>
+
+<h3>The copyright disclaimer</h3>
-<span class="inserted"><ins><em><h3>The copyright disclaimer</h3>
+<span class="removed"><del><strong><p>To avoid possible legal
complications later,</strong></del></span>
-<p>To avoid possible legal complications later, it's wise to ask your
-employer or school, if any, to sign a copyright disclaimer for your
+<span class="inserted"><ins><em><p>If you are an individual, and you
have an employer or study in
+a school,</em></ins></span> it's wise to ask your
+employer or <span class="removed"><del><strong>school, if
any,</strong></del></span> <span
class="inserted"><ins><em>school</em></ins></span> to sign a copyright
disclaimer for your
program, so it cannot later claim that the copyright belongs to it
and that you had no right to release the program at all. This really
has nothing to do with the GNU GPL—it applies no matter which
@@ -94,14 +91,13 @@
<p>If you work, the best time to negotiate permission to release free
software is <em>when negotiating your employment
agreement</em>.</p>
-<h3>The copyright notice</h3></em></ins></span>
+<h3>The copyright notice</h3>
<p>The copyright notice should include the year in which you finished
preparing the release (so if you finished it in 1998 but didn't post
it until 1999, use 1998). You should add the proper year for each
-<span class="inserted"><ins><em>past</em></ins></span> release; for example,
“Copyright 1998, 1999 Terry
-Jones” if some
-<span class="removed"><del><strong>versions</strong></del></span> <span
class="inserted"><ins><em>releases</em></ins></span> were finished in 1998 and
some were
+past release; for example, “Copyright 1998, 1999 Terry
+Jones” if some releases were finished in 1998 and some were
finished in 1999. If several people helped write the code, use all
their names.</p>
@@ -117,51 +113,37 @@
languages. The copyright symbol “©” can be included if
you wish (and your character set supports it), but it's not necessary.
There is no legal significance to using the three-character sequence
-“(C)”, <span
class="removed"><del><strong>although</strong></del></span> <span
class="inserted"><ins><em>but</em></ins></span> it does no harm.</p>
+“(C)”, but it does no harm.</p>
-<span class="inserted"><ins><em><p>If you have copied code from other
programs covered by the same
+<p>If you have copied code from other programs covered by the same
license, copy their copyright notices too. Put all the copyright
notices for a file together, right near the top of the file.</p>
-<h3>The license files</h3></em></ins></span>
+<h3>The license files</h3>
<p>You should also include a copy of the license itself somewhere in the
distribution of your program. All programs, whether they are released
under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the
-text version of the GPL</a>. In GNU programs <span
class="inserted"><ins><em>we conventionally put</em></ins></span> the
-license <span class="removed"><del><strong>is usually</strong></del></span> in
a file called COPYING.</p>
+text version of the GPL</a>. In GNU programs we conventionally put the
+license in a file called COPYING.</p>
-<p>If you are releasing your program under the <span
class="removed"><del><strong>LGPL,</strong></del></span> <span
class="inserted"><ins><em>GNU AGPL,
+<p>If you are releasing your program under the GNU AGPL,
use <a href="/licenses/agpl.txt">the text version of the GNU
AGPL</a>
instead of the GNU GPL.</p>
-<p>If you are releasing your program under the Lesser
GPL,</em></ins></span> you should also
+<p>If you are releasing your program under the Lesser GPL, you should
also
include <a href="/licenses/lgpl.txt">the text version of the
LGPL</a>,
usually in a file called COPYING.LESSER. Please note that, since the
-LGPL is a set of additional permissions on top of the GPL, it's <span
class="removed"><del><strong>important</strong></del></span> <span
class="inserted"><ins><em>crucial</em></ins></span>
+LGPL is a set of additional permissions on top of the GPL, it's crucial
to include both licenses so users have all the materials they need to
understand their rights.</p>
-<span class="removed"><del><strong><p>If you are releasing your program
under the GNU AGPL, you only need to
-include <a href="/licenses/agpl.txt">the text version of the GNU
-AGPL</a>.</p>
-
-<p>If you have copied code from other programs covered by the same
-license, copy their copyright notices too. Put all the copyright
-notices together, right near the top of each file.</p>
+<h3>The license notices</h3>
-<p>It is very important for practical reasons to include contact
-information for how to reach you, perhaps in the README file, but this
-has nothing to do with the legal issues of applying the license.</p>
-
-<p>The</strong></del></span>
-
-<span class="inserted"><ins><em><h3>The license notices</h3>
-
-<p>Each file's</em></ins></span> copying permission statement <span
class="inserted"><ins><em>(also called the license notice)</em></ins></span>
-should come right after <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>its</em></ins></span> copyright notices. For a
one-file
-program, the statement (for the GPL) should look like <span
class="removed"><del><strong>this:</p></strong></del></span> <span
class="inserted"><ins><em>this, to use
-GPL version 3 or later:</p></em></ins></span>
+<p>Each file's copying permission statement (also called the license
notice)
+should come right after its copyright notices. For a one-file
+program, the statement (for the GPL) should look like this, to use
+GPL version 3 or later:</p>
<pre>
This program is free software: you can redistribute it and/or modify
@@ -197,13 +179,12 @@
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
- along with <span class="removed"><del><strong>Foobar. If not, see
<http://www.gnu.org/licenses/>.
-</pre></strong></del></span> <span class="inserted"><ins><em>Foobar. If
not, see <http://www.gnu.org/licenses/>.
+ along with Foobar. If not, see <http://www.gnu.org/licenses/>.
</pre>
<p>To use a different set of GPL versions, you would modify the end of
the first long paragraph. For instance, to license under version 2 or
-later, you would replace “3” with
“2”.</p></em></ins></span>
+later, you would replace “3” with “2”.</p>
<p>This statement should go near the beginning of every source file,
close to the copyright notices. When using the Lesser GPL, insert the
@@ -212,7 +193,7 @@
word “Affero” before “General” in <em>all
three</em> places.</p>
-<span class="inserted"><ins><em><h3>Why license notices?</h3>
+<h3>Why license notices?</h3>
<p>The purpose of a free software license is to give certain rights to
all users of a program. If it is not clear what rights you have given
@@ -232,14 +213,14 @@
license is, then moving it into another context eliminates all trace
of that point. This invites confusion and error.</p>
-<h3>The startup notice</h3></em></ins></span>
+<h3>The startup notice</h3>
<p>For interactive programs, it is usually a good idea to make the
-program <span class="removed"><del><strong>print out</strong></del></span>
<span class="inserted"><ins><em>display</em></ins></span> a brief notice about
copyright and copying permission
+program display a brief notice about copyright and copying permission
when it starts up. See <a href="/licenses/gpl-3.0.html#howto">the end
of the GNU GPL</a> for more information about this.</p>
-<span class="inserted"><ins><em><h3>The Affero
notice</h3></em></ins></span>
+<h3>The Affero notice</h3>
<p>If you are releasing your program under the GNU AGPL, and it can
interact with users over a network, the program should offer its source to
@@ -249,50 +230,34 @@
that you can choose a method that's suitable for your specific
program—see section 13 for details.</p>
-<span class="inserted"><ins><em><h3>Miscellaneous</h3>
+<h3>Miscellaneous</h3>
<p>It is very important for practical reasons to include contact
information for how to reach you, perhaps in the README file, but this
-has nothing to do with the legal issues of applying the
license.</p></em></ins></span>
+has nothing to do with the legal issues of applying the license.</p>
<p>There is no legal requirement to register your copyright with anyone;
-simply <span class="removed"><del><strong>distributing</strong></del></span>
<span class="inserted"><ins><em>writing</em></ins></span> the program makes it
copyrighted. However, <span class="inserted"><ins><em>for the
US,</em></ins></span>
-it is a
-<span class="removed"><del><strong>very</strong></del></span> good idea to
register the copyright with the US Registry of
+simply writing the program makes it copyrighted. However, for the US,
+it is a good idea to register the copyright with the US Registry of
Copyrights, because that puts you in a stronger position against anyone
who violates the license in the US. Most other countries have no system
of copyright registration.</p>
-<span class="removed"><del><strong><p>It's wise to ask your employer or
school, if any, to sign a
-copyright disclaimer for the work, so they cannot claim to hold it
-later. Below is a sample copyright disclaimer; just alter the names
-and program description as appropriate:</p>
-
-<blockquote><p>Yoyodyne, Inc., hereby disclaims all copyright
interest
-in the program “Gnomovision” (which makes passes at
-compilers) written by James Hacker.</p>
-
-<p><signature of Moe Ghoul>, 1 April 1989<br />
- Moe Ghoul, President of
Vice</p></blockquote></strong></del></span>
-
<p>We would like to list all free software programs in the Free
Software Directory, including all programs licensed under the GPL (any
-version). <span class="inserted"><ins><em>So please submit an entry for your
program, when it has
-reached the point of being useful.</em></ins></span> Please see
+version). So please submit an entry for your program, when it has
+reached the point of being useful. Please see
the <a href="http://directory.fsf.org/">Directory web page</a> for
information and an online submission form.</p>
<p>It is also possible to make your program a GNU package, a part of the
-GNU Project. <span class="removed"><del><strong>(That's if we like the
program—we have to look at it
-first, and decide.)</strong></del></span> If you might be interested in
joining up with the
+GNU Project. If you might be interested in joining up with the
GNU Project in this way, please see our <a
href="/help/evaluation.html">GNU software evaluation page</a> for more
-information and a short <span
class="removed"><del><strong>questionnaire.</p>
-
-<p>But you</strong></del></span> <span
class="inserted"><ins><em>questionnaire. We will respond and discuss the
+information and a short questionnaire. We will respond and discuss the
matter with you.</p>
-<p>You</em></ins></span> are welcome to use any of our licenses even if
your program
+<p>You are welcome to use any of our licenses even if your program
is not a GNU package; indeed, we hope you will. They're available to
everyone. If you'd like to advertise your use of a particular license,
feel free to use <a href="/graphics/license-logos.html"
@@ -330,7 +295,7 @@
<!-- 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 <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> Please do NOT change or
remove this
+ 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
@@ -345,19 +310,18 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2001, 2007, 2008, 2009, 2013, <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2017, 2018</em></ins></span>
+<p>Copyright © 2001, 2007, 2008, 2009, 2013, 2014, 2017, 2018
Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
-<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
-<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
-Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+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: 2018/01/24 03:59:36 $
+$Date: 2018/05/30 01:59:44 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/javascript-trap.it.html
===================================================================
RCS file: /web/www/www/philosophy/javascript-trap.it.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- philosophy/javascript-trap.it.html 25 Jan 2018 21:30:52 -0000 1.11
+++ philosophy/javascript-trap.it.html 30 May 2018 02:00:54 -0000 1.12
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/philosophy/javascript-trap.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/javascript-trap.it.po">
+ https://www.gnu.org/philosophy/po/javascript-trap.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/philosophy/javascript-trap.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/javascript-trap.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE" value="/philosophy/javascript-trap.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.84 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/philosophy/po/javascript-trap.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>La trappola JavaScript</h2>
<p>di <a href="http://www.stallman.org/";>Richard Stallman</a></p>
@@ -281,7 +287,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo Aggiornamento:
-$Date: 2018/01/25 21:30:52 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/javascript-trap.uk.html
===================================================================
RCS file: /web/www/www/philosophy/javascript-trap.uk.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- philosophy/javascript-trap.uk.html 3 Feb 2018 10:36:19 -0000 1.12
+++ philosophy/javascript-trap.uk.html 30 May 2018 02:00:54 -0000 1.13
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/philosophy/javascript-trap.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/javascript-trap.uk.po">
+ https://www.gnu.org/philosophy/po/javascript-trap.uk.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/philosophy/javascript-trap.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/javascript-trap.uk-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE" value="/philosophy/javascript-trap.en.html" -->
<!--#include virtual="/server/header.uk.html" -->
<!-- Parent-Version: 1.84 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/philosophy/po/javascript-trap.translist" -->
<!--#include virtual="/server/banner.uk.html" -->
+<!--#include virtual="/server/outdated.uk.html" -->
<h2>ÐаÑÑка JavaScript</h2>
<p><a href="http://www.stallman.org/";>Ð ÑÑаÑд СÑолмен</a></p>
@@ -280,7 +286,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðновлено:
-$Date: 2018/02/03 10:36:19 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/who-does-that-server-really-serve.it.html
===================================================================
RCS file: /web/www/www/philosophy/who-does-that-server-really-serve.it.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/who-does-that-server-really-serve.it.html 18 Nov 2016
07:32:52 -0000 1.10
+++ philosophy/who-does-that-server-really-serve.it.html 30 May 2018
02:00:54 -0000 1.11
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/who-does-that-server-really-serve.it.po">
+ https://www.gnu.org/philosophy/po/who-does-that-server-really-serve.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/philosophy/who-does-that-server-really-serve.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/who-does-that-server-really-serve.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.79 -->
@@ -8,6 +13,7 @@
<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Quel server in realtà a chi serve?</h2>
<p>di <strong>Richard Stallman</strong></p>
@@ -491,7 +497,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2016/11/18 07:32:52 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/who-does-that-server-really-serve.ja.html
===================================================================
RCS file: /web/www/www/philosophy/who-does-that-server-really-serve.ja.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- philosophy/who-does-that-server-really-serve.ja.html 18 Nov 2016
07:32:52 -0000 1.19
+++ philosophy/who-does-that-server-really-serve.ja.html 30 May 2018
02:00:54 -0000 1.20
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/who-does-that-server-really-serve.ja.po">
+ https://www.gnu.org/philosophy/po/who-does-that-server-really-serve.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/philosophy/who-does-that-server-really-serve.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/who-does-that-server-really-serve.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
<!--#include virtual="/server/header.ja.html" -->
<!-- Parent-Version: 1.79 -->
@@ -8,6 +13,7 @@
<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
<h2>ãã®ãµã¼ãã¯ãã£ãã誰ã«ãµã¼ãããã®ã?</h2>
<p><strong>ãªãã£ã¼ãã»ã¹ãã¼ã«ãã³</strong>è</p>
@@ -232,7 +238,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2016/11/18 07:32:52 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/who-does-that-server-really-serve.nl.html
===================================================================
RCS file: /web/www/www/philosophy/who-does-that-server-really-serve.nl.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/who-does-that-server-really-serve.nl.html 14 Jan 2017
14:58:43 -0000 1.3
+++ philosophy/who-does-that-server-really-serve.nl.html 30 May 2018
02:00:54 -0000 1.4
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/who-does-that-server-really-serve.nl.po">
+ https://www.gnu.org/philosophy/po/who-does-that-server-really-serve.nl.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/philosophy/who-does-that-server-really-serve.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/who-does-that-server-really-serve.nl-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
<!--#include virtual="/server/header.nl.html" -->
<!-- Parent-Version: 1.79 -->
@@ -9,6 +14,7 @@
<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.nl.html" -->
+<!--#include virtual="/server/outdated.nl.html" -->
<h2>Wie dient die server eigenlijk echt?</h2>
<p>door <strong>Richard Stallman</strong></p>
@@ -495,7 +501,7 @@
<p class="unprintable"><!-- timestamp start -->
Bijgewerkt:
-$Date: 2017/01/14 14:58:43 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/who-does-that-server-really-serve.uk.html
===================================================================
RCS file: /web/www/www/philosophy/who-does-that-server-really-serve.uk.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/who-does-that-server-really-serve.uk.html 18 Nov 2016
07:32:52 -0000 1.10
+++ philosophy/who-does-that-server-really-serve.uk.html 30 May 2018
02:00:54 -0000 1.11
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/who-does-that-server-really-serve.uk.po">
+ https://www.gnu.org/philosophy/po/who-does-that-server-really-serve.uk.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/philosophy/who-does-that-server-really-serve.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/who-does-that-server-really-serve.uk-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2018-03-31" --><!--#set
var="ENGLISH_PAGE"
value="/philosophy/who-does-that-server-really-serve.en.html" -->
<!--#include virtual="/server/header.uk.html" -->
<!-- Parent-Version: 1.79 -->
@@ -9,6 +14,7 @@
<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.uk.html" -->
+<!--#include virtual="/server/outdated.uk.html" -->
<h2>Ðого наÑпÑÐ°Ð²Ð´Ñ Ð¾Ð±ÑлÑговÑÑ ÑеÑвеÑ? </h2>
<p><strong>Ð ÑÑаÑд СÑолмен</strong></p>
@@ -482,7 +488,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðновлено:
-$Date: 2016/11/18 07:32:52 $
+$Date: 2018/05/30 02:00:54 $
<!-- timestamp end -->
</p>
Index: philosophy/po/javascript-trap.uk-diff.html
===================================================================
RCS file: /web/www/www/philosophy/po/javascript-trap.uk-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/po/javascript-trap.uk-diff.html 19 May 2017 14:29:08 -0000
1.1
+++ philosophy/po/javascript-trap.uk-diff.html 30 May 2018 02:01:06 -0000
1.2
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.79 -->
+<!-- Parent-Version: 1.84 -->
<title>The JavaScript Trap</title>
<!--#include virtual="/philosophy/po/javascript-trap.translist" -->
<!--#include virtual="/server/banner.html" -->
@@ -23,27 +23,26 @@
<p><strong>You may be running nonfree programs on your computer
every
day without realizing it—through your web
browser.</strong></p>
-<span class="inserted"><ins><em><!-- any links that used to point to the
appendices should point to
+<!-- any links that used to point to the appendices should point to
free-your-javascript.html instead. -->
<blockquote>
<p>Webmasters: there are
<a href="/software/librejs/free-your-javascript.html">several
ways</a>
to indicate the license of JavaScript programs in a web site.</p>
-</blockquote></em></ins></span>
+</blockquote>
-<p>In the free software community, the idea that nonfree programs
-mistreat their users is familiar. Some of us <span
class="removed"><del><strong>refuse entirely to
-install</strong></del></span> <span class="inserted"><ins><em>defend our
freedom by
-rejecting all</em></ins></span> proprietary <span
class="removed"><del><strong>software, and many</strong></del></span> <span
class="inserted"><ins><em>software on our computers. Many</em></ins></span>
others <span class="removed"><del><strong>consider
nonfreedom</strong></del></span>
-<span class="inserted"><ins><em>recognize nonfreeness as</em></ins></span> a
strike against the <span class="removed"><del><strong>program.
Many</strong></del></span> <span class="inserted"><ins><em>program.</p>
-
-<p>Many</em></ins></span> users are aware that this issue applies to the
plug-ins that
-browsers offer to install, since they can be free or <span
class="removed"><del><strong>nonfree.</p>
-
-<p>But</strong></del></span> <span class="inserted"><ins><em>nonfree.
But</em></ins></span>
-browsers run other nonfree programs which they don't ask you
-<span class="removed"><del><strong>about</strong></del></span> <span
class="inserted"><ins><em>about,</em></ins></span> or
+<p>In the free software community, the idea that
+<span class="inserted"><ins><em><a
href="/philosophy/free-software-even-more-important.html">
+any</em></ins></span> nonfree <span class="removed"><del><strong>programs
+mistreat their users</strong></del></span> <span
class="inserted"><ins><em>program mistreats its
users</a></em></ins></span> is familiar. Some of us
+defend our freedom by rejecting all proprietary software on our
+computers. Many others recognize nonfreeness as a strike against the
+program.</p>
+
+<p>Many users are aware that this issue applies to the plug-ins that
+browsers offer to install, since they can be free or nonfree. But
+browsers run other nonfree programs which they don't ask you about, or
even tell you about—programs that web pages contain or link to.
These programs are most often written in JavaScript, though other
languages are also used.</p>
@@ -51,11 +50,12 @@
<p>JavaScript (officially called ECMAScript, but few use that name)
was once used for minor frills in web pages, such as cute but
inessential navigation and display features. It was acceptable to
-consider these as mere extensions of HTML markup, rather than as true <span
class="removed"><del><strong>software; they
-did not constitute a significant</strong></del></span>
-<span class="inserted"><ins><em>software, and disregard the</em></ins></span>
issue.</p>
+consider these as mere extensions of HTML markup, rather than as true
+software, and disregard the issue.</p>
+
+<span class="removed"><del><strong><p>Many</strong></del></span>
-<p>Many sites still use JavaScript that way, but some use it for major
+<span class="inserted"><ins><em><p>Some</em></ins></span> sites still
use JavaScript that way, but <span
class="removed"><del><strong>some</strong></del></span> <span
class="inserted"><ins><em>many</em></ins></span> use it for major
programs that do large jobs. For instance, Google Docs tries to download into
your machine a JavaScript program which measures half a megabyte, in a
compacted form that we could call Obfuscript because it has no
@@ -67,7 +67,13 @@
<p>In addition to being nonfree, many of these programs are malware
because
they <a
href="http://github.com/w3c/fingerprinting-guidance/issues/8">snoop
-on the user</a>.</p>
+on the <span
class="removed"><del><strong>user</a>.</p></strong></del></span>
<span class="inserted"><ins><em>user</a>. Even nastier, some sites use
services which record
+<a
href="https://freedom-to-tinker.com/2017/11/15/no-boundaries-exfiltration-of-personal-data-by-session-replay-scripts/">all
+the user's actions while looking at the page</a>. The services
+supposedly “redact” the recordings to exclude some
+sensitive data that the web site shouldn't get. But even if that
+works reliably, the whole purpose of these services is to give the web
+site other personal data that it shouldn't get.</p></em></ins></span>
<p>Browsers don't normally tell you when they load JavaScript
programs. Some browsers have a way to turn off JavaScript entirely,
@@ -137,7 +143,7 @@
only the issue of the client-side software. We are addressing the
server issue separately.</p>
-<p>In practical terms, how can we deal with the problem of nonfree
+<p>In practical terms, how can we deal with the problem of nontrivial
nonfree
JavaScript programs in web sites? The first step is to avoid running
it.</p>
@@ -169,10 +175,9 @@
</li>
</ul>
-<p>How do we tell whether the JavaScript code is free? <span
class="removed"><del><strong>At the end of
-this article</strong></del></span> <span class="inserted"><ins><em>In a <a
-href="/licenses/javascript-labels.html">separate
article</a>,</em></ins></span>
-we propose a <span
class="removed"><del><strong>convention</strong></del></span> <span
class="inserted"><ins><em>method</em></ins></span> by which a nontrivial
JavaScript
+<p>How do we tell whether the JavaScript code is free? In a <a
+href="/licenses/javascript-labels.html">separate article</a>,
+we propose a method by which a nontrivial JavaScript
program in a web page can state the URL where its source code is
located, and can state its license too, using stylized comments.</p>
@@ -208,96 +213,19 @@
site. Please don't hesitate to enable JavaScript temporarily to do
that—but remember to disable it again afterwards.</p>
-<span class="removed"><del><strong><p><strong>Thank
you</strong></del></span>
-
-<span class="inserted"><ins><em><!-- any links that used to point to the
appendices should point to
+<!-- any links that used to point to the appendices should point to
free-your-javascript.html instead. -->
<blockquote>
<p>Webmasters: there are
-<a href="/software/librejs/free-your-javascript.html">several
ways</a></em></ins></span>
-to <span class="inserted"><ins><em>indicate the license of JavaScript programs
in a web site.</p>
+<a href="/software/librejs/free-your-javascript.html">several
ways</a>
+to indicate the license of JavaScript programs in a web site.</p>
</blockquote>
-<p><strong>Acknowledgements:</strong> I
thank</em></ins></span> <a href="/people/people.html#mattlee">Matt
Lee</a>
+<p><strong>Acknowledgements:</strong> I thank <a
href="/people/people.html#mattlee">Matt Lee</a>
and <a href="http://ejohn.org">John Resig</a> for their help in
-defining our proposed criterion, and <span
class="removed"><del><strong>to</strong></del></span> David Parunakian for
-<span class="removed"><del><strong>helping to make me aware of the
problem.</strong></p>
-
-<h3 id="AppendixA">Appendix A: a convention for releasing free
JavaScript programs</h3>
-
-<p>For references to corresponding source code, we recommend</p>
-<pre dir="ltr">
-
- // @source:
-
-</pre>
-
-<p>followed by the URL. This satisfies the GNU GPL's requirement to
-distribute source code. If the source is on a different site, you
-must take care
-to <a href="/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites">
-handle that properly</a>. Source code is necessary for the program to
-be free.
-</p>
-
-<p>To indicate the license of the JavaScript code embedded in a page, we
-recommend putting the license notice between two notes of this form:</p>
-<pre dir="ltr">
-<!--TRANSLATORS: Do not translate these license notices. The <pre>
- elements have dir="ltr" explicitly set to cater for RTL languages.-->
- @licstart The following is the entire license notice for the
- JavaScript code in this page.
- ...
- @licend The above is the entire license notice
- for the JavaScript code in this page.
-
-</pre>
-<p>Of course, all of this should be contained in a multiline
comment.</p>
-
-<p>The <a href="/licenses/gpl.html">GNU GPL</a>, like many
other free
-software licenses, requires distribution of a copy of the license with
-both source and binary forms of the program. However, the GNU GPL is
-long enough that including it in a page with a JavaScript program can
-be inconvenient. You can remove that requirement, for code that you
-have the copyright on, with a license notice like this:</p>
-<pre dir="ltr">
-
- Copyright (C) YYYY Developer
-
- The JavaScript code in this page is free software: you can
- redistribute it and/or modify it under the terms of the GNU
- General Public License (GNU GPL) as published by the Free Software
- Foundation, either version 3 of the License, or (at your option)
- any later version. The code is distributed WITHOUT ANY WARRANTY;
- without even the implied warranty of MERCHANTABILITY or FITNESS
- FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
-
- As additional permission under GNU GPL version 3 section 7, you
- may distribute non-source (e.g., minimized or compacted) forms of
- that code without the copy of the GNU GPL normally required by
- section 4, provided you include this license notice and a URL
- through which recipients can access the Corresponding Source.
-
-</pre>
-
-<p>I thank Jaffar Rumith for</strong></del></span>
-bringing <span class="removed"><del><strong>this issue</strong></del></span>
<span class="inserted"><ins><em>the problem</em></ins></span> to my
attention.</p>
-
-<span class="removed"><del><strong><h3 id="AppendixB">Appendix B:
Publishing free JavaScript programs as
- a webmaster</h3>
-
-<p>If you're a webmaster deploying free JavaScript software
- on your site, clearly and consistently publishing information about
- those files' licenses and source code helps your visitors make
- sure that they're running free software, and help you comply with
- license conditions.</p>
-
-<p>One method of stating the licenses is the one described above in
- <a href="#AppendixA">Appendix A</a>. A second
- method, <a href="/licenses/javascript-labels.html"> JavaScript
- license web labels</a>, can be more convenient for libraries of
- minified JavaScript code, especially when you didn't write
them.</p></strong></del></span>
+defining our proposed criterion, and David Parunakian for
+bringing the problem to my attention.</p>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
@@ -346,7 +274,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2009-2013, <span
class="removed"><del><strong>2016</strong></del></span> <span
class="inserted"><ins><em>2016, 2017</em></ins></span> Richard
Stallman</p>
+<p>Copyright © 2009-2013, 2016, 2017, 2018 Richard
Stallman</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
@@ -356,7 +284,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/05/19 14:29:08 $
+$Date: 2018/05/30 02:01:06 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/javascript-trap.it-diff.html
===================================================================
RCS file: philosophy/po/javascript-trap.it-diff.html
diff -N philosophy/po/javascript-trap.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/javascript-trap.it-diff.html 30 May 2018 02:01:05 -0000
1.1
@@ -0,0 +1,294 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/javascript-trap.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+<title>The JavaScript Trap</title>
+<!--#include virtual="/philosophy/po/javascript-trap.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>The JavaScript Trap</h2>
+
+<p>by <a href="http://www.stallman.org/">Richard
Stallman</a></p>
+
+<p><strong>You may be running nonfree programs on your computer
every
+day without realizing it—through your web
browser.</strong></p>
+
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+
+<blockquote>
+<p>Webmasters: there are
+<a href="/software/librejs/free-your-javascript.html">several
ways</a>
+to indicate the license of JavaScript programs in a web site.</p>
+</blockquote>
+
+<p>In the free software community, the idea that
+<span class="inserted"><ins><em><a
href="/philosophy/free-software-even-more-important.html">
+any</em></ins></span> nonfree <span class="removed"><del><strong>programs
+mistreat their users</strong></del></span> <span
class="inserted"><ins><em>program mistreats its
users</a></em></ins></span> is familiar. Some of us
+defend our freedom by rejecting all proprietary software on our
+computers. Many others recognize nonfreeness as a strike against the
+program.</p>
+
+<p>Many users are aware that this issue applies to the plug-ins that
+browsers offer to install, since they can be free or nonfree. But
+browsers run other nonfree programs which they don't ask you about, or
+even tell you about—programs that web pages contain or link to.
+These programs are most often written in JavaScript, though other
+languages are also used.</p>
+
+<p>JavaScript (officially called ECMAScript, but few use that name)
+was once used for minor frills in web pages, such as cute but
+inessential navigation and display features. It was acceptable to
+consider these as mere extensions of HTML markup, rather than as true
+software, and disregard the issue.</p>
+
+<span class="removed"><del><strong><p>Many</strong></del></span>
+
+<span class="inserted"><ins><em><p>Some</em></ins></span> sites still
use JavaScript that way, but <span
class="removed"><del><strong>some</strong></del></span> <span
class="inserted"><ins><em>many</em></ins></span> use it for major
+programs that do large jobs. For instance, Google Docs tries to download into
+your machine a JavaScript program which measures half a megabyte, in a
+compacted form that we could call Obfuscript because it has no
+comments and hardly any whitespace, and the method names are one
+letter long. The source code of a program is the preferred form for
+modifying it; the compacted code is not source code, and the real
+source code of this program is not available to the user.</p>
+
+<p>In addition to being nonfree, many of these programs are malware
+because
+they <a
href="http://github.com/w3c/fingerprinting-guidance/issues/8">snoop
+on the <span
class="removed"><del><strong>user</a>.</p></strong></del></span>
<span class="inserted"><ins><em>user</a>. Even nastier, some sites use
services which record
+<a
href="https://freedom-to-tinker.com/2017/11/15/no-boundaries-exfiltration-of-personal-data-by-session-replay-scripts/">all
+the user's actions while looking at the page</a>. The services
+supposedly “redact” the recordings to exclude some
+sensitive data that the web site shouldn't get. But even if that
+works reliably, the whole purpose of these services is to give the web
+site other personal data that it shouldn't get.</p></em></ins></span>
+
+<p>Browsers don't normally tell you when they load JavaScript
+programs. Some browsers have a way to turn off JavaScript entirely,
+but even if you're aware of this issue, it would take you considerable
+trouble to identify the nontrivial nonfree programs and block them.
+However, even in the free software community most users are not aware
+of this issue; the browsers' silence tends to conceal it.</p>
+
+<p>It is possible to release a JavaScript program as free software, by
+distributing the source code under a free software license. If the
+program is self-contained—if its functioning and purpose are
+independent of the page it came in—that is fine; you can copy it
+to a file on your machine, modify it, and visit that file with a
+browser to run it. But that is an unusual case.</p>
+
+<p>In the usual case, JavaScript programs are meant to work with a
+particular page or site, and the page or site depends on them to
+function. Then another problem arises: even if the program's source
+is available, browsers do not offer a way to run your modified version
+instead of the original when visiting that page or site. The effect
+is comparable to tivoization, although in principle not quite so hard
+to overcome.</p>
+
+<p>JavaScript is not the only language web sites use for programs sent
+to the user. Flash supports programming through an extended variant
+of JavaScript; if we ever have a sufficiently complete free Flash
+player, we will need to deal with the issue of nonfree Flash programs.
+Silverlight seems likely to create a problem similar to Flash, except
+worse, since Microsoft uses it as a platform for nonfree codecs. A
+free replacement for Silverlight does not do the job for the free
+world unless it normally comes with free replacement codecs.</p>
+
+<p>Java applets also run in the browser, and raise similar issues. In
+general, any sort of applet system poses this sort of problem. Having
+a free execution environment for an applet only brings us far enough
+to encounter the problem.</p>
+
+<p>It is theoretically possible to program in HTML and CSS, but in
+practice this capability is limited and inconvenient; merely to make
+it do something is an impressive hack. Such programs ought to be
+free, but CSS is not a serious problem for users' freedom as of
+2016.</p>
+
+<p>A strong movement has developed that calls for web sites to
+communicate only through formats and protocols that are free (some say
+"open"); that is to say, whose documentation is published and which
+anyone is free to implement. With the presence of programs in web
+pages, that criterion is necessary, but not sufficient. JavaScript
+itself, as a format, is free, and use of JavaScript in a web site is
+not necessarily bad. However, as we've seen above, it also isn't
+necessarily OK. When the site transmits a program to the user, it is
+not enough for the program to be written in a documented and
+unencumbered language; that program must be free, too. “Only free
+programs transmitted to the user” must become part of the criterion
+for proper behavior by web sites.</p>
+
+<p>Silently loading and running nonfree programs is one among several
+issues raised by "web applications". The term "web
+application" was designed to disregard the fundamental
+distinction between software delivered to users and software running
+on a server. It can refer to a specialized client program running
+in a browser; it can refer to specialized server software; it can
+refer to a specialized client program that works hand in hand with
+specialized server software. The client and server sides raise
+different ethical issues, even if they are so closely integrated that
+they arguably form parts of a single program. This article addresses
+only the issue of the client-side software. We are addressing the
+server issue separately.</p>
+
+<p>In practical terms, how can we deal with the problem of nontrivial
nonfree
+JavaScript programs in web sites? The first step is to avoid running
+it.</p>
+
+<p>What do we mean by "nontrivial"? It is a matter of
+degree, so this is a matter of designing a simple criterion that gives
+good results, rather than finding the one correct answer.</p>
+<p>
+Our tentative policy is to consider a JavaScript program nontrivial
if:</p>
+
+<ul>
+ <li>it makes an AJAX request or is loaded along with scripts that make
+ an AJAX request,</li>
+
+ <li>it loads external scripts dynamically or is loaded along with
+ scripts that do,</li>
+
+ <li>it defines functions or methods and either loads an external script
+ (from html) or is loaded as one,</li>
+
+ <li>it uses dynamic JavaScript constructs that are difficult to analyze
+ without interpreting the program, or is loaded along with scripts
+ that use such constructs. These constructs are:
+ <ul>
+ <li>using the eval function,</li>
+ <li>calling methods with the square bracket notation,</li>
+ <li>using any other construct than a string literal with
+ certain methods (Obj.write, Obj.createElement, ...).</li>
+ </ul>
+ </li>
+</ul>
+
+<p>How do we tell whether the JavaScript code is free? In a <a
+href="/licenses/javascript-labels.html">separate article</a>,
+we propose a method by which a nontrivial JavaScript
+program in a web page can state the URL where its source code is
+located, and can state its license too, using stylized comments.</p>
+
+<p>Finally, we need to change free browsers to detect and block
+nontrivial nonfree JavaScript in web pages. The program
+<a href="/software/librejs/">LibreJS</a> detects nonfree,
+nontrivial JavaScript in pages you visit, and blocks it. LibreJS is
+included in IceCat, and available as an add-on for Firefox.</p>
+
+<p>Browser users also need a convenient facility to specify JavaScript
+code to use <em>instead</em> of the JavaScript in a certain page.
+(The specified code might be total replacement, or a modified version
+of the free JavaScript program in that page.) Greasemonkey comes close
+to being able to do this, but not quite, since it doesn't guarantee to
+modify the JavaScript code in a page before that program starts to
+execute. Using a local proxy works, but is too inconvenient now to be
+a real solution. We need to construct a solution that is reliable and
+convenient, as well as sites for sharing changes. The GNU Project
+would like to recommend sites which are dedicated to free changes
+only.</p>
+
+<p>These features will make it possible for a JavaScript program included
+in a web page to be free in a real and practical sense. JavaScript
+will no longer be a particular obstacle to our freedom—no more than
+C and Java are now. We will be able to reject and even replace the
+nonfree nontrivial JavaScript programs, just as we reject and replace
+nonfree packages that are offered for installation in the usual way.
+Our campaign for web sites to free their JavaScript can then begin.</p>
+
+<p>In the mean time, there's one case where it is acceptable to run a
+nonfree JavaScript program: to send a complaint to the website
+operators saying they should free or remove the JavaScript code in the
+site. Please don't hesitate to enable JavaScript temporarily to do
+that—but remember to disable it again afterwards.</p>
+
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+
+<blockquote>
+<p>Webmasters: there are
+<a href="/software/librejs/free-your-javascript.html">several
ways</a>
+to indicate the license of JavaScript programs in a web site.</p>
+</blockquote>
+
+<p><strong>Acknowledgements:</strong> I thank <a
href="/people/people.html#mattlee">Matt Lee</a>
+and <a href="http://ejohn.org">John Resig</a> for their help in
+defining our proposed criterion, and David Parunakian for
+bringing the problem to my attention.</p>
+
+</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2009-2013, 2016, 2017, 2018 Richard
Stallman</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: 2018/05/30 02:01:05 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: philosophy/po/who-does-that-server-really-serve.it-diff.html
===================================================================
RCS file: philosophy/po/who-does-that-server-really-serve.it-diff.html
diff -N philosophy/po/who-does-that-server-really-serve.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/who-does-that-server-really-serve.it-diff.html 30 May
2018 02:01:06 -0000 1.1
@@ -0,0 +1,486 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/who-does-that-server-really-serve.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software Foundation</title>
+
+<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Who does that server really serve?</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(The first version was published
+in <a
href="http://www.bostonreview.net/richard-stallman-free-software-DRM">
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>On the Internet, proprietary software isn't the only
way to
+lose your freedom. Service as a Software Substitute, or SaaSS, is
+another way to give someone else power over your
computing.</strong></p>
+
+<p>The basic point is, you can have control over a program someone else
+wrote (if it's free), but you can never have control over a service
+someone else runs, so never use a service where in principle a program
+would do.</p>
+
+
+<p>SaaSS means using a service implemented by someone else as a
+substitute for running your copy of a program. The term is ours;
+articles and ads won't use it, and they won't tell you whether a
+service is SaaSS. Instead they will probably use the vague and
+distracting term “cloud”, which lumps SaaSS together with
+various other practices, some abusive and some ok. With the
+explanation and examples in this page, you can tell whether a service
+is SaaSS.</p>
+
+<h3>Background: How Proprietary Software Takes Away Your
Freedom</h3>
+
+<p>Digital technology can give you freedom; it can also take your
+freedom away. The first threat to our control over our computing came
+from <em>proprietary software</em>: software that the users cannot
+control because the owner (a company such as Apple or Microsoft)
+controls it. The owner often takes advantage of this unjust power by
+inserting malicious features such as spyware, back doors, and <a
+href="http://DefectiveByDesign.org">Digital Restrictions Management
+(DRM)</a> (referred to as “Digital Rights Management” in
+their propaganda).</p>
+
+<p>Our solution to this problem is developing <em>free
software</em>
+and rejecting proprietary software. Free software means that you, as
+a user, have four essential freedoms: (0) to run the program as
+you wish, (1) to study and change the source code so it does what
+you wish, (2) to redistribute exact copies, and (3) to
+redistribute copies of your modified versions. (See
+the <a href="/philosophy/free-sw.html">free software
+definition</a>.)</p>
+
+<p>With free software, we, the users, take back control of our
+computing. Proprietary software still exists, but we can exclude it
+from our lives and many of us have done so. However, we are now
+offered another tempting way to cede control over our computing:
+Service as a Software Substitute (SaaSS). For our freedom's sake, we
+have to reject that too.</p>
+
+<h3>How Service as a Software Substitute Takes Away Your
Freedom</h3>
+
+<p>Service as a Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program. Concretely, it means
+that someone sets up a network server that does certain computing
+tasks—for instance, modifying a photo, translating text into
+another language, etc.—then invites users to do computing via
+that server. A user of the server would send her data to the server,
+which does <em>her own computing</em> on the data thus provided,
then
+sends the results back to her or acts directly on her behalf.</p>
+
+<p>The computing is <em>her own</em> because, by assumption,
she
+could, in principle, have done it by running a program on her own
+computer (whether or not that program is available to her at
+present). In cases where this assumption is not so, it isn't SaaSS.</p>
+
+<p>These servers wrest control from the users even more inexorably
+than proprietary software. With proprietary software, users typically
+get an executable file but not the source code. That makes it hard to
+study the code that is running, so it's hard to determine what the
+program really does, and hard to change it.</p>
+
+<p>With SaaSS, the users do not have even the executable file that
+does their computing: it is on someone else's server, where the users
+can't see or touch it. Thus it is impossible for them to ascertain
+what it really does, and impossible to change it.</p>
+
+<p>Furthermore, SaaSS automatically leads to consequences equivalent
+to the malicious features of certain proprietary software.</p>
+
+<p> For instance, some proprietary programs are “spyware”:
+the program <a href="/philosophy/proprietary-surveillance.html">
+sends out data about users' computing activities</a>.
+Microsoft Windows sends information about users' activities to
+Microsoft. Windows Media Player reports what each user watches or
+listens to. The Amazon Kindle reports which pages of which books the
+user looks at, and when. Angry Birds reports the user's geolocation
+history.</p>
+
+<p>Unlike proprietary software, SaaSS does not require covert code to
+obtain the user's data. Instead, users must send their data to the
+server in order to use it. This has the same effect as spyware: the
+server operator gets the data—with no special effort, by the
+nature of SaaSS. Amy Webb, who intended never to post any photos of
+her daughter, made the mistake of using SaaSS (Instagram) to edit
+photos of her. Eventually
+<a
href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html">
they
+leaked from there</a>.
+</p>
+
+<p>Theoretically, homomorphic encryption might some day advance to the
+point where future SaaSS services might be constructed to be unable to
+understand some of the data that users send them. Such
+services <em>could</em> be set up not to snoop on users; this does
not
+mean they <em>will</em> do no snooping.</p>
+
+<p>Some proprietary operating systems have a universal back door,
+permitting someone to remotely install software changes. For
+instance, Windows has a universal back door with which Microsoft can
+forcibly change any software on the machine. Nearly all portable
+phones have them, too. Some proprietary applications also have
+universal back doors; for instance, the Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS, the server operator can change the software in use on
+the server. He ought to be able to do this, since it's his computer;
+but the result is the same as using a proprietary application program
+with a universal back door: someone has the power to silently impose
+changes in how the user's computing gets done.</p>
+
+<p>Thus, SaaSS is equivalent to running proprietary software with
+spyware and a universal back door. It gives the server operator
+unjust power over the user, and that power is something we must
+resist.</p>
+
+<h3>SaaSS and SaaS</h3>
+
+<p>Originally we referred to this problematical practice as
+“SaaS”, which stands for “Software as a
+Service”. It's a commonly used term for setting up software on a
+server rather than offering copies of it to users, and we thought it
+described precisely the cases where this problem occurs.</p>
+
+<p>Subsequently we became aware that the term SaaS is sometimes used for
+communication services—activities for which this issue is not
+applicable. In addition, the term “Software as a Service”
+doesn't explain <em>why</em> the practice is bad. So we coined
the term
+“Service as a Software Substitute”, which defines the bad
+practice more clearly and says what is bad about it.</p>
+
+<h3>Untangling the SaaSS Issue from the Proprietary Software
Issue</h3>
+
+<p>SaaSS and proprietary software lead to similar harmful results, but
+the mechanisms are different. With proprietary software, the
+mechanism is that you have and use a copy which is difficult and/or
+illegal to change. With SaaSS, the mechanism is that you don't have
+the copy that's doing your computing.</p>
+
+<p>These two issues are often confused, and not only by accident. Web
+developers use the vague term “web application” to lump
+the server software together with programs run on your machine in your
+browser. Some web pages install nontrivial, even large JavaScript
+programs into your browser without informing
+you. <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they cause the same sort of injustice as any
+other nonfree software. Here, however, we are concerned with the
+issue of using the service itself.</p>
+
+<p>Many free software supporters assume that the problem of SaaSS will
+be solved by developing free software for servers. For the server
+operator's sake, the programs on the server had better be free; if
+they are proprietary, their developers/owners have power over the
+server. That's unfair to the server operator, and doesn't help the
+server's users at all. But if the programs on the server are free,
+that doesn't protect <em>the server's users</em> from the effects
of
+SaaSS. These programs liberate the server operator, but not the
+server's users.</p>
+
+<p>Releasing the server software source code does benefit the
+community: it enables suitably skilled users to set up similar
+servers, perhaps changing the
+software. <a href="/licenses/license-recommendations.html"> We
+recommend using the GNU Affero GPL</a> as the license for programs
+often used on servers.</p>
+
+<p>But none of these servers would give you control over computing you
+do on it, unless it's <em>your</em> server (one whose software load
+you control, regardless of whether the machine is your property). It
+may be OK to trust your friend's server for some jobs, just as you
+might let your friend maintain the software on your own computer.
+Outside of that, all these servers would be SaaSS for you. SaaSS
+always subjects you to the power of the server operator, and the only
+remedy is, <em>Don't use SaaSS!</em> Don't use someone else's
server
+to do your own computing on data provided by you.</p>
+
+<p>This issue demonstrates the depth of the difference between
+“open” and “free”. Source code that is open
+source <a href="/philosophy/free-open-overlap.html">is, nearly always,
+free</a>. However, the idea of
+an <a href="http://opendefinition.org/software-service">“open
+software” service</a>, meaning one whose server software is open
+source and/or free, fails to address the issue of SaaSS.</p>
+
+<p>Services are fundamentally different from programs, and the ethical
+issues that services raise are fundamentally different from the issues
+that programs raise. To avoid confusion,
+we <a href="/philosophy/network-services-arent-free-or-nonfree.html">
+avoid describing a service as “free” or
+“proprietary.”</a></p>
+
+<h3>Distinguishing SaaSS from Other Network Services</h3>
+
+<p>Which online services are SaaSS? The clearest example is a
+translation service, which translates (say) English text into Spanish
+text. Translating a text for you is computing that is purely yours.
+You could do it by running a program on your own computer, if only you
+had the right program. (To be ethical, that program should be free.)
+The translation service substitutes for that program, so it is Service
+as a Software Substitute, or SaaSS. Since it denies you control
+over your computing, it does you wrong.</p>
+
+<p>Another clear example is using a service such as Flickr or
+Instagram to modify a photo. Modifying photos is an activity that
+people have done in their own computers for decades; doing it in a
+server you don't control, rather than your own computer, is SaaSS.</p>
+
+<p>Rejecting SaaSS does not mean refusing to use any network servers
+run by anyone other than you. Most servers are not SaaSS because the
+jobs they do are some sort of communication, rather than the user's
+own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to publish information for you to access. Even today this is what
+most web sites do, and it doesn't pose the SaaSS problem, because
+accessing someone's published information isn't doing your own
+computing. Neither is use of a blog site to publish your own works,
+or using a microblogging service such as Twitter or StatusNet. (These
+services may or may not have other problems, depending on details.)
+The same goes for other communication not meant to be private, such as
+chat groups.</p>
+
+<p>In its essence, social networking is a form of communication and
+publication, not SaaSS. However, a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a service is not SaaSS, that does not mean it is OK. There are
+other ethical issues about services. For instance, Facebook
+distributes video in Flash, which pressures users to run nonfree
+software; it requires running nonfree JavaScript code; and it gives
+users a misleading impression of privacy while luring them into baring
+their lives to Facebook. Those are important issues, different from
+the SaaSS issue.
+</p>
+
+<p>Services such as search engines collect data from around the web
+and let you examine it. Looking through their collection of data
+isn't your own computing in the usual sense—you didn't provide
+that collection—so using such a service to search the web is not
+SaaSS. However, using someone else's server to implement a search
+facility for your own site <em>is</em> SaaSS.</p>
+
+<p>Purchasing online is not SaaSS, because the computing
+isn't <em>your own</em> activity; rather, it is done jointly by and
+for you and the store. The real issue in online shopping is whether
+you trust the other party with your money and other personal
+information (starting with your name).</p>
+
+<p>Repository sites such as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p>
+
+<p>Using a joint project's servers isn't SaaSS because the computing
+you do in this way isn't your own. For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's computing. Wikipedia controls its own
+servers, but organizations as well as individuals encounter the
+problem of SaaSS if they do their computing in someone else's
+server.</p>
+
+<p>Some sites offer multiple services, and if one is not SaaSS,
+another may be SaaSS. For instance, the main service of Facebook is
+social networking, and that is not SaaSS; however, it supports
+third-party applications, some of which are SaaSS. Flickr's main
+service is distributing photos, which is not SaaSS, but it also has
+features for editing photos, which is SaaSS. Likewise, using
+Instagram to post a photo is not SaaSS, but using it to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation of a single service
+can become. It invites people to edit a document by running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong. However, it offers an API for uploading
+and downloading documents in standard formats. A free software editor
+can do so through this API. This usage scenario is not SaaSS, because
+it uses Google Docs as a mere repository. Showing all your data to a
+company is bad, but that is a matter of privacy, not SaaSS; depending
+on a service for access to your data is bad, but that is a matter of
+risk, not SaaSS. On the other hand, using the service for converting
+document formats <em>is</em> SaaSS, because it's something you
could
+have done by running a suitable program (free, one hopes) in your own
+computer.</p>
+
+<p>Using Google Docs through a free editor is rare, of course. Most
+often, people use it through the nonfree JavaScript program, which is
+bad like any nonfree program. This scenario might involve SaaSS, too;
+that depends on what part of the editing is done in the JavaScript
+program and what part in the server. We don't know, but since SaaSS
+and proprietary software do similar wrong to the user, it is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues, but publishing through Google Docs has a special problem: it
+is impossible even to <em>view the text</em> of a Google Docs
document
+in a browser without running the nonfree JavaScript code. Thus, you
+should not use Google Docs to publish anything—but the reason
+is not a matter of SaaSS.</p>
+
+<p>The IT industry discourages users from making these distinctions.
+That's what the buzzword “cloud computing” is for. This
+term is so nebulous that it could refer to almost any use of the
+Internet. It includes SaaSS as well as many other network usage
+practices. In any given context, an author who writes
+“cloud” (if a technical person) probably has a specific
+meaning in mind, but usually does not explain that in other articles
+the term has other specific meanings. The term leads people to
+generalize about practices they ought to consider individually.</p>
+
+<p>If “cloud computing” has a meaning, it is not a way of
+doing computing, but rather a way of thinking about computing: a
+devil-may-care approach which says, “Don't ask questions. Don't
+worry about who controls your computing or who holds your data. Don't
+check for a hook hidden inside our service before you swallow it.
+Trust companies without hesitation.” In other words, “Be a
+sucker.” A cloud in the mind is an obstacle to clear thinking.
+For the sake of clear thinking about computing, let's avoid the term
+“cloud.”</p>
+
+<h3 id="renting">Renting a Server Distinguished from SaaSS</h3>
+
+<p>If you rent a server (real or virtual), whose software load you
+have control over, that's not SaaSS. In SaaSS, someone else decides
+what software runs on the server and therefore controls the computing
+it does for you. In the case where you install the software on the
+server, you control what computing it does for you. Thus, the rented
+server is virtually your computer. For this issue, it counts as
+yours.</p>
+
+<p>The <em>data</em> on the rented remote server is less
secure than
+if you had the server at home, but that is a separate issue from
+SaaSS.</p>
+
+<span class="inserted"><ins><em><p>This kind of server rental is
sometimes called “IaaS,”
+but that term fits into a conceptual structure that downplays the issues
+that we consider important.</p></em></ins></span>
+
+<h3>Dealing with the SaaSS Problem</h3>
+
+<p>Only a small fraction of all web sites do SaaSS; most don't raise
+the issue. But what should we do about the ones that raise it?</p>
+
+<p>For the simple case, where you are doing your own computing on data
+in your own hands, the solution is simple: use your own copy of a free
+software application. Do your text editing with your copy of a free
+text editor such as GNU Emacs or a free word processor. Do your photo
+editing with your copy of free software such as GIMP. What if there
+is no free program available? A proprietary program or SaaSS would
+take away your freedom, so you shouldn't use those. You can contribute
+your time or your money to development of a free replacement.</p>
+
+<p>What about collaborating with other individuals as a group? It may
+be hard to do this at present without using a server, and your group
+may not know how to run its own server. If you use someone else's
+server, at least don't trust a server run by a company. A mere
+contract as a customer is no protection unless you could detect a
+breach and could really sue, and the company probably writes its
+contracts to permit a broad range of abuses. The state can subpoena
+your data from the company along with everyone else's, as Obama has
+done to phone companies, supposing the company doesn't volunteer them
+like the US phone companies that illegally wiretapped their customers
+for Bush. If you must use a server, use a server whose operators give
+you a basis for trust beyond a mere commercial relationship.</p>
+
+<p>However, on a longer time scale, we can create alternatives to
+using servers. For instance, we can create a peer-to-peer program
+through which collaborators can share data encrypted. The free
+software community should develop distributed peer-to-peer
+replacements for important “web applications”. It may be
+wise to release them under
+the <a href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>,
since
+they are likely candidates for being converted into server-based
+programs by someone else. The <a href="/">GNU project</a> is
looking
+for volunteers to work on such replacements. We also invite other
+free software projects to consider this issue in their design.</p>
+
+<p>In the meantime, if a company invites you to use its server to do
+your own computing tasks, don't yield; don't use SaaSS. Don't buy or
+install “thin clients”, which are simply computers so weak
+they make you do the real work on a server, unless you're going to use
+them with <em>your</em> server. Use a real computer and keep your
+data there. Do your own computing with your own copy of a free
+program, for your freedom's sake.</p>
+
+<h3>See also:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">The
+Bug Nobody is Allowed to Understand</a>.</p>
+
+</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2010, 2013, 2015, <span
class="removed"><del><strong>2016</strong></del></span> <span
class="inserted"><ins><em>2016, 2018</em></ins></span> Richard
Stallman</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: 2018/05/30 02:01:06 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: philosophy/po/who-does-that-server-really-serve.ja-diff.html
===================================================================
RCS file: philosophy/po/who-does-that-server-really-serve.ja-diff.html
diff -N philosophy/po/who-does-that-server-really-serve.ja-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/who-does-that-server-really-serve.ja-diff.html 30 May
2018 02:01:06 -0000 1.1
@@ -0,0 +1,486 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/who-does-that-server-really-serve.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software Foundation</title>
+
+<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Who does that server really serve?</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(The first version was published
+in <a
href="http://www.bostonreview.net/richard-stallman-free-software-DRM">
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>On the Internet, proprietary software isn't the only
way to
+lose your freedom. Service as a Software Substitute, or SaaSS, is
+another way to give someone else power over your
computing.</strong></p>
+
+<p>The basic point is, you can have control over a program someone else
+wrote (if it's free), but you can never have control over a service
+someone else runs, so never use a service where in principle a program
+would do.</p>
+
+
+<p>SaaSS means using a service implemented by someone else as a
+substitute for running your copy of a program. The term is ours;
+articles and ads won't use it, and they won't tell you whether a
+service is SaaSS. Instead they will probably use the vague and
+distracting term “cloud”, which lumps SaaSS together with
+various other practices, some abusive and some ok. With the
+explanation and examples in this page, you can tell whether a service
+is SaaSS.</p>
+
+<h3>Background: How Proprietary Software Takes Away Your
Freedom</h3>
+
+<p>Digital technology can give you freedom; it can also take your
+freedom away. The first threat to our control over our computing came
+from <em>proprietary software</em>: software that the users cannot
+control because the owner (a company such as Apple or Microsoft)
+controls it. The owner often takes advantage of this unjust power by
+inserting malicious features such as spyware, back doors, and <a
+href="http://DefectiveByDesign.org">Digital Restrictions Management
+(DRM)</a> (referred to as “Digital Rights Management” in
+their propaganda).</p>
+
+<p>Our solution to this problem is developing <em>free
software</em>
+and rejecting proprietary software. Free software means that you, as
+a user, have four essential freedoms: (0) to run the program as
+you wish, (1) to study and change the source code so it does what
+you wish, (2) to redistribute exact copies, and (3) to
+redistribute copies of your modified versions. (See
+the <a href="/philosophy/free-sw.html">free software
+definition</a>.)</p>
+
+<p>With free software, we, the users, take back control of our
+computing. Proprietary software still exists, but we can exclude it
+from our lives and many of us have done so. However, we are now
+offered another tempting way to cede control over our computing:
+Service as a Software Substitute (SaaSS). For our freedom's sake, we
+have to reject that too.</p>
+
+<h3>How Service as a Software Substitute Takes Away Your
Freedom</h3>
+
+<p>Service as a Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program. Concretely, it means
+that someone sets up a network server that does certain computing
+tasks—for instance, modifying a photo, translating text into
+another language, etc.—then invites users to do computing via
+that server. A user of the server would send her data to the server,
+which does <em>her own computing</em> on the data thus provided,
then
+sends the results back to her or acts directly on her behalf.</p>
+
+<p>The computing is <em>her own</em> because, by assumption,
she
+could, in principle, have done it by running a program on her own
+computer (whether or not that program is available to her at
+present). In cases where this assumption is not so, it isn't SaaSS.</p>
+
+<p>These servers wrest control from the users even more inexorably
+than proprietary software. With proprietary software, users typically
+get an executable file but not the source code. That makes it hard to
+study the code that is running, so it's hard to determine what the
+program really does, and hard to change it.</p>
+
+<p>With SaaSS, the users do not have even the executable file that
+does their computing: it is on someone else's server, where the users
+can't see or touch it. Thus it is impossible for them to ascertain
+what it really does, and impossible to change it.</p>
+
+<p>Furthermore, SaaSS automatically leads to consequences equivalent
+to the malicious features of certain proprietary software.</p>
+
+<p> For instance, some proprietary programs are “spyware”:
+the program <a href="/philosophy/proprietary-surveillance.html">
+sends out data about users' computing activities</a>.
+Microsoft Windows sends information about users' activities to
+Microsoft. Windows Media Player reports what each user watches or
+listens to. The Amazon Kindle reports which pages of which books the
+user looks at, and when. Angry Birds reports the user's geolocation
+history.</p>
+
+<p>Unlike proprietary software, SaaSS does not require covert code to
+obtain the user's data. Instead, users must send their data to the
+server in order to use it. This has the same effect as spyware: the
+server operator gets the data—with no special effort, by the
+nature of SaaSS. Amy Webb, who intended never to post any photos of
+her daughter, made the mistake of using SaaSS (Instagram) to edit
+photos of her. Eventually
+<a
href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html">
they
+leaked from there</a>.
+</p>
+
+<p>Theoretically, homomorphic encryption might some day advance to the
+point where future SaaSS services might be constructed to be unable to
+understand some of the data that users send them. Such
+services <em>could</em> be set up not to snoop on users; this does
not
+mean they <em>will</em> do no snooping.</p>
+
+<p>Some proprietary operating systems have a universal back door,
+permitting someone to remotely install software changes. For
+instance, Windows has a universal back door with which Microsoft can
+forcibly change any software on the machine. Nearly all portable
+phones have them, too. Some proprietary applications also have
+universal back doors; for instance, the Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS, the server operator can change the software in use on
+the server. He ought to be able to do this, since it's his computer;
+but the result is the same as using a proprietary application program
+with a universal back door: someone has the power to silently impose
+changes in how the user's computing gets done.</p>
+
+<p>Thus, SaaSS is equivalent to running proprietary software with
+spyware and a universal back door. It gives the server operator
+unjust power over the user, and that power is something we must
+resist.</p>
+
+<h3>SaaSS and SaaS</h3>
+
+<p>Originally we referred to this problematical practice as
+“SaaS”, which stands for “Software as a
+Service”. It's a commonly used term for setting up software on a
+server rather than offering copies of it to users, and we thought it
+described precisely the cases where this problem occurs.</p>
+
+<p>Subsequently we became aware that the term SaaS is sometimes used for
+communication services—activities for which this issue is not
+applicable. In addition, the term “Software as a Service”
+doesn't explain <em>why</em> the practice is bad. So we coined
the term
+“Service as a Software Substitute”, which defines the bad
+practice more clearly and says what is bad about it.</p>
+
+<h3>Untangling the SaaSS Issue from the Proprietary Software
Issue</h3>
+
+<p>SaaSS and proprietary software lead to similar harmful results, but
+the mechanisms are different. With proprietary software, the
+mechanism is that you have and use a copy which is difficult and/or
+illegal to change. With SaaSS, the mechanism is that you don't have
+the copy that's doing your computing.</p>
+
+<p>These two issues are often confused, and not only by accident. Web
+developers use the vague term “web application” to lump
+the server software together with programs run on your machine in your
+browser. Some web pages install nontrivial, even large JavaScript
+programs into your browser without informing
+you. <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they cause the same sort of injustice as any
+other nonfree software. Here, however, we are concerned with the
+issue of using the service itself.</p>
+
+<p>Many free software supporters assume that the problem of SaaSS will
+be solved by developing free software for servers. For the server
+operator's sake, the programs on the server had better be free; if
+they are proprietary, their developers/owners have power over the
+server. That's unfair to the server operator, and doesn't help the
+server's users at all. But if the programs on the server are free,
+that doesn't protect <em>the server's users</em> from the effects
of
+SaaSS. These programs liberate the server operator, but not the
+server's users.</p>
+
+<p>Releasing the server software source code does benefit the
+community: it enables suitably skilled users to set up similar
+servers, perhaps changing the
+software. <a href="/licenses/license-recommendations.html"> We
+recommend using the GNU Affero GPL</a> as the license for programs
+often used on servers.</p>
+
+<p>But none of these servers would give you control over computing you
+do on it, unless it's <em>your</em> server (one whose software load
+you control, regardless of whether the machine is your property). It
+may be OK to trust your friend's server for some jobs, just as you
+might let your friend maintain the software on your own computer.
+Outside of that, all these servers would be SaaSS for you. SaaSS
+always subjects you to the power of the server operator, and the only
+remedy is, <em>Don't use SaaSS!</em> Don't use someone else's
server
+to do your own computing on data provided by you.</p>
+
+<p>This issue demonstrates the depth of the difference between
+“open” and “free”. Source code that is open
+source <a href="/philosophy/free-open-overlap.html">is, nearly always,
+free</a>. However, the idea of
+an <a href="http://opendefinition.org/software-service">“open
+software” service</a>, meaning one whose server software is open
+source and/or free, fails to address the issue of SaaSS.</p>
+
+<p>Services are fundamentally different from programs, and the ethical
+issues that services raise are fundamentally different from the issues
+that programs raise. To avoid confusion,
+we <a href="/philosophy/network-services-arent-free-or-nonfree.html">
+avoid describing a service as “free” or
+“proprietary.”</a></p>
+
+<h3>Distinguishing SaaSS from Other Network Services</h3>
+
+<p>Which online services are SaaSS? The clearest example is a
+translation service, which translates (say) English text into Spanish
+text. Translating a text for you is computing that is purely yours.
+You could do it by running a program on your own computer, if only you
+had the right program. (To be ethical, that program should be free.)
+The translation service substitutes for that program, so it is Service
+as a Software Substitute, or SaaSS. Since it denies you control
+over your computing, it does you wrong.</p>
+
+<p>Another clear example is using a service such as Flickr or
+Instagram to modify a photo. Modifying photos is an activity that
+people have done in their own computers for decades; doing it in a
+server you don't control, rather than your own computer, is SaaSS.</p>
+
+<p>Rejecting SaaSS does not mean refusing to use any network servers
+run by anyone other than you. Most servers are not SaaSS because the
+jobs they do are some sort of communication, rather than the user's
+own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to publish information for you to access. Even today this is what
+most web sites do, and it doesn't pose the SaaSS problem, because
+accessing someone's published information isn't doing your own
+computing. Neither is use of a blog site to publish your own works,
+or using a microblogging service such as Twitter or StatusNet. (These
+services may or may not have other problems, depending on details.)
+The same goes for other communication not meant to be private, such as
+chat groups.</p>
+
+<p>In its essence, social networking is a form of communication and
+publication, not SaaSS. However, a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a service is not SaaSS, that does not mean it is OK. There are
+other ethical issues about services. For instance, Facebook
+distributes video in Flash, which pressures users to run nonfree
+software; it requires running nonfree JavaScript code; and it gives
+users a misleading impression of privacy while luring them into baring
+their lives to Facebook. Those are important issues, different from
+the SaaSS issue.
+</p>
+
+<p>Services such as search engines collect data from around the web
+and let you examine it. Looking through their collection of data
+isn't your own computing in the usual sense—you didn't provide
+that collection—so using such a service to search the web is not
+SaaSS. However, using someone else's server to implement a search
+facility for your own site <em>is</em> SaaSS.</p>
+
+<p>Purchasing online is not SaaSS, because the computing
+isn't <em>your own</em> activity; rather, it is done jointly by and
+for you and the store. The real issue in online shopping is whether
+you trust the other party with your money and other personal
+information (starting with your name).</p>
+
+<p>Repository sites such as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p>
+
+<p>Using a joint project's servers isn't SaaSS because the computing
+you do in this way isn't your own. For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's computing. Wikipedia controls its own
+servers, but organizations as well as individuals encounter the
+problem of SaaSS if they do their computing in someone else's
+server.</p>
+
+<p>Some sites offer multiple services, and if one is not SaaSS,
+another may be SaaSS. For instance, the main service of Facebook is
+social networking, and that is not SaaSS; however, it supports
+third-party applications, some of which are SaaSS. Flickr's main
+service is distributing photos, which is not SaaSS, but it also has
+features for editing photos, which is SaaSS. Likewise, using
+Instagram to post a photo is not SaaSS, but using it to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation of a single service
+can become. It invites people to edit a document by running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong. However, it offers an API for uploading
+and downloading documents in standard formats. A free software editor
+can do so through this API. This usage scenario is not SaaSS, because
+it uses Google Docs as a mere repository. Showing all your data to a
+company is bad, but that is a matter of privacy, not SaaSS; depending
+on a service for access to your data is bad, but that is a matter of
+risk, not SaaSS. On the other hand, using the service for converting
+document formats <em>is</em> SaaSS, because it's something you
could
+have done by running a suitable program (free, one hopes) in your own
+computer.</p>
+
+<p>Using Google Docs through a free editor is rare, of course. Most
+often, people use it through the nonfree JavaScript program, which is
+bad like any nonfree program. This scenario might involve SaaSS, too;
+that depends on what part of the editing is done in the JavaScript
+program and what part in the server. We don't know, but since SaaSS
+and proprietary software do similar wrong to the user, it is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues, but publishing through Google Docs has a special problem: it
+is impossible even to <em>view the text</em> of a Google Docs
document
+in a browser without running the nonfree JavaScript code. Thus, you
+should not use Google Docs to publish anything—but the reason
+is not a matter of SaaSS.</p>
+
+<p>The IT industry discourages users from making these distinctions.
+That's what the buzzword “cloud computing” is for. This
+term is so nebulous that it could refer to almost any use of the
+Internet. It includes SaaSS as well as many other network usage
+practices. In any given context, an author who writes
+“cloud” (if a technical person) probably has a specific
+meaning in mind, but usually does not explain that in other articles
+the term has other specific meanings. The term leads people to
+generalize about practices they ought to consider individually.</p>
+
+<p>If “cloud computing” has a meaning, it is not a way of
+doing computing, but rather a way of thinking about computing: a
+devil-may-care approach which says, “Don't ask questions. Don't
+worry about who controls your computing or who holds your data. Don't
+check for a hook hidden inside our service before you swallow it.
+Trust companies without hesitation.” In other words, “Be a
+sucker.” A cloud in the mind is an obstacle to clear thinking.
+For the sake of clear thinking about computing, let's avoid the term
+“cloud.”</p>
+
+<h3 id="renting">Renting a Server Distinguished from SaaSS</h3>
+
+<p>If you rent a server (real or virtual), whose software load you
+have control over, that's not SaaSS. In SaaSS, someone else decides
+what software runs on the server and therefore controls the computing
+it does for you. In the case where you install the software on the
+server, you control what computing it does for you. Thus, the rented
+server is virtually your computer. For this issue, it counts as
+yours.</p>
+
+<p>The <em>data</em> on the rented remote server is less
secure than
+if you had the server at home, but that is a separate issue from
+SaaSS.</p>
+
+<span class="inserted"><ins><em><p>This kind of server rental is
sometimes called “IaaS,”
+but that term fits into a conceptual structure that downplays the issues
+that we consider important.</p></em></ins></span>
+
+<h3>Dealing with the SaaSS Problem</h3>
+
+<p>Only a small fraction of all web sites do SaaSS; most don't raise
+the issue. But what should we do about the ones that raise it?</p>
+
+<p>For the simple case, where you are doing your own computing on data
+in your own hands, the solution is simple: use your own copy of a free
+software application. Do your text editing with your copy of a free
+text editor such as GNU Emacs or a free word processor. Do your photo
+editing with your copy of free software such as GIMP. What if there
+is no free program available? A proprietary program or SaaSS would
+take away your freedom, so you shouldn't use those. You can contribute
+your time or your money to development of a free replacement.</p>
+
+<p>What about collaborating with other individuals as a group? It may
+be hard to do this at present without using a server, and your group
+may not know how to run its own server. If you use someone else's
+server, at least don't trust a server run by a company. A mere
+contract as a customer is no protection unless you could detect a
+breach and could really sue, and the company probably writes its
+contracts to permit a broad range of abuses. The state can subpoena
+your data from the company along with everyone else's, as Obama has
+done to phone companies, supposing the company doesn't volunteer them
+like the US phone companies that illegally wiretapped their customers
+for Bush. If you must use a server, use a server whose operators give
+you a basis for trust beyond a mere commercial relationship.</p>
+
+<p>However, on a longer time scale, we can create alternatives to
+using servers. For instance, we can create a peer-to-peer program
+through which collaborators can share data encrypted. The free
+software community should develop distributed peer-to-peer
+replacements for important “web applications”. It may be
+wise to release them under
+the <a href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>,
since
+they are likely candidates for being converted into server-based
+programs by someone else. The <a href="/">GNU project</a> is
looking
+for volunteers to work on such replacements. We also invite other
+free software projects to consider this issue in their design.</p>
+
+<p>In the meantime, if a company invites you to use its server to do
+your own computing tasks, don't yield; don't use SaaSS. Don't buy or
+install “thin clients”, which are simply computers so weak
+they make you do the real work on a server, unless you're going to use
+them with <em>your</em> server. Use a real computer and keep your
+data there. Do your own computing with your own copy of a free
+program, for your freedom's sake.</p>
+
+<h3>See also:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">The
+Bug Nobody is Allowed to Understand</a>.</p>
+
+</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2010, 2013, 2015, <span
class="removed"><del><strong>2016</strong></del></span> <span
class="inserted"><ins><em>2016, 2018</em></ins></span> Richard
Stallman</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: 2018/05/30 02:01:06 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: philosophy/po/who-does-that-server-really-serve.nl-diff.html
===================================================================
RCS file: philosophy/po/who-does-that-server-really-serve.nl-diff.html
diff -N philosophy/po/who-does-that-server-really-serve.nl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/who-does-that-server-really-serve.nl-diff.html 30 May
2018 02:01:06 -0000 1.1
@@ -0,0 +1,486 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/who-does-that-server-really-serve.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software Foundation</title>
+
+<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Who does that server really serve?</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(The first version was published
+in <a
href="http://www.bostonreview.net/richard-stallman-free-software-DRM">
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>On the Internet, proprietary software isn't the only
way to
+lose your freedom. Service as a Software Substitute, or SaaSS, is
+another way to give someone else power over your
computing.</strong></p>
+
+<p>The basic point is, you can have control over a program someone else
+wrote (if it's free), but you can never have control over a service
+someone else runs, so never use a service where in principle a program
+would do.</p>
+
+
+<p>SaaSS means using a service implemented by someone else as a
+substitute for running your copy of a program. The term is ours;
+articles and ads won't use it, and they won't tell you whether a
+service is SaaSS. Instead they will probably use the vague and
+distracting term “cloud”, which lumps SaaSS together with
+various other practices, some abusive and some ok. With the
+explanation and examples in this page, you can tell whether a service
+is SaaSS.</p>
+
+<h3>Background: How Proprietary Software Takes Away Your
Freedom</h3>
+
+<p>Digital technology can give you freedom; it can also take your
+freedom away. The first threat to our control over our computing came
+from <em>proprietary software</em>: software that the users cannot
+control because the owner (a company such as Apple or Microsoft)
+controls it. The owner often takes advantage of this unjust power by
+inserting malicious features such as spyware, back doors, and <a
+href="http://DefectiveByDesign.org">Digital Restrictions Management
+(DRM)</a> (referred to as “Digital Rights Management” in
+their propaganda).</p>
+
+<p>Our solution to this problem is developing <em>free
software</em>
+and rejecting proprietary software. Free software means that you, as
+a user, have four essential freedoms: (0) to run the program as
+you wish, (1) to study and change the source code so it does what
+you wish, (2) to redistribute exact copies, and (3) to
+redistribute copies of your modified versions. (See
+the <a href="/philosophy/free-sw.html">free software
+definition</a>.)</p>
+
+<p>With free software, we, the users, take back control of our
+computing. Proprietary software still exists, but we can exclude it
+from our lives and many of us have done so. However, we are now
+offered another tempting way to cede control over our computing:
+Service as a Software Substitute (SaaSS). For our freedom's sake, we
+have to reject that too.</p>
+
+<h3>How Service as a Software Substitute Takes Away Your
Freedom</h3>
+
+<p>Service as a Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program. Concretely, it means
+that someone sets up a network server that does certain computing
+tasks—for instance, modifying a photo, translating text into
+another language, etc.—then invites users to do computing via
+that server. A user of the server would send her data to the server,
+which does <em>her own computing</em> on the data thus provided,
then
+sends the results back to her or acts directly on her behalf.</p>
+
+<p>The computing is <em>her own</em> because, by assumption,
she
+could, in principle, have done it by running a program on her own
+computer (whether or not that program is available to her at
+present). In cases where this assumption is not so, it isn't SaaSS.</p>
+
+<p>These servers wrest control from the users even more inexorably
+than proprietary software. With proprietary software, users typically
+get an executable file but not the source code. That makes it hard to
+study the code that is running, so it's hard to determine what the
+program really does, and hard to change it.</p>
+
+<p>With SaaSS, the users do not have even the executable file that
+does their computing: it is on someone else's server, where the users
+can't see or touch it. Thus it is impossible for them to ascertain
+what it really does, and impossible to change it.</p>
+
+<p>Furthermore, SaaSS automatically leads to consequences equivalent
+to the malicious features of certain proprietary software.</p>
+
+<p> For instance, some proprietary programs are “spyware”:
+the program <a href="/philosophy/proprietary-surveillance.html">
+sends out data about users' computing activities</a>.
+Microsoft Windows sends information about users' activities to
+Microsoft. Windows Media Player reports what each user watches or
+listens to. The Amazon Kindle reports which pages of which books the
+user looks at, and when. Angry Birds reports the user's geolocation
+history.</p>
+
+<p>Unlike proprietary software, SaaSS does not require covert code to
+obtain the user's data. Instead, users must send their data to the
+server in order to use it. This has the same effect as spyware: the
+server operator gets the data—with no special effort, by the
+nature of SaaSS. Amy Webb, who intended never to post any photos of
+her daughter, made the mistake of using SaaSS (Instagram) to edit
+photos of her. Eventually
+<a
href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html">
they
+leaked from there</a>.
+</p>
+
+<p>Theoretically, homomorphic encryption might some day advance to the
+point where future SaaSS services might be constructed to be unable to
+understand some of the data that users send them. Such
+services <em>could</em> be set up not to snoop on users; this does
not
+mean they <em>will</em> do no snooping.</p>
+
+<p>Some proprietary operating systems have a universal back door,
+permitting someone to remotely install software changes. For
+instance, Windows has a universal back door with which Microsoft can
+forcibly change any software on the machine. Nearly all portable
+phones have them, too. Some proprietary applications also have
+universal back doors; for instance, the Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS, the server operator can change the software in use on
+the server. He ought to be able to do this, since it's his computer;
+but the result is the same as using a proprietary application program
+with a universal back door: someone has the power to silently impose
+changes in how the user's computing gets done.</p>
+
+<p>Thus, SaaSS is equivalent to running proprietary software with
+spyware and a universal back door. It gives the server operator
+unjust power over the user, and that power is something we must
+resist.</p>
+
+<h3>SaaSS and SaaS</h3>
+
+<p>Originally we referred to this problematical practice as
+“SaaS”, which stands for “Software as a
+Service”. It's a commonly used term for setting up software on a
+server rather than offering copies of it to users, and we thought it
+described precisely the cases where this problem occurs.</p>
+
+<p>Subsequently we became aware that the term SaaS is sometimes used for
+communication services—activities for which this issue is not
+applicable. In addition, the term “Software as a Service”
+doesn't explain <em>why</em> the practice is bad. So we coined
the term
+“Service as a Software Substitute”, which defines the bad
+practice more clearly and says what is bad about it.</p>
+
+<h3>Untangling the SaaSS Issue from the Proprietary Software
Issue</h3>
+
+<p>SaaSS and proprietary software lead to similar harmful results, but
+the mechanisms are different. With proprietary software, the
+mechanism is that you have and use a copy which is difficult and/or
+illegal to change. With SaaSS, the mechanism is that you don't have
+the copy that's doing your computing.</p>
+
+<p>These two issues are often confused, and not only by accident. Web
+developers use the vague term “web application” to lump
+the server software together with programs run on your machine in your
+browser. Some web pages install nontrivial, even large JavaScript
+programs into your browser without informing
+you. <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they cause the same sort of injustice as any
+other nonfree software. Here, however, we are concerned with the
+issue of using the service itself.</p>
+
+<p>Many free software supporters assume that the problem of SaaSS will
+be solved by developing free software for servers. For the server
+operator's sake, the programs on the server had better be free; if
+they are proprietary, their developers/owners have power over the
+server. That's unfair to the server operator, and doesn't help the
+server's users at all. But if the programs on the server are free,
+that doesn't protect <em>the server's users</em> from the effects
of
+SaaSS. These programs liberate the server operator, but not the
+server's users.</p>
+
+<p>Releasing the server software source code does benefit the
+community: it enables suitably skilled users to set up similar
+servers, perhaps changing the
+software. <a href="/licenses/license-recommendations.html"> We
+recommend using the GNU Affero GPL</a> as the license for programs
+often used on servers.</p>
+
+<p>But none of these servers would give you control over computing you
+do on it, unless it's <em>your</em> server (one whose software load
+you control, regardless of whether the machine is your property). It
+may be OK to trust your friend's server for some jobs, just as you
+might let your friend maintain the software on your own computer.
+Outside of that, all these servers would be SaaSS for you. SaaSS
+always subjects you to the power of the server operator, and the only
+remedy is, <em>Don't use SaaSS!</em> Don't use someone else's
server
+to do your own computing on data provided by you.</p>
+
+<p>This issue demonstrates the depth of the difference between
+“open” and “free”. Source code that is open
+source <a href="/philosophy/free-open-overlap.html">is, nearly always,
+free</a>. However, the idea of
+an <a href="http://opendefinition.org/software-service">“open
+software” service</a>, meaning one whose server software is open
+source and/or free, fails to address the issue of SaaSS.</p>
+
+<p>Services are fundamentally different from programs, and the ethical
+issues that services raise are fundamentally different from the issues
+that programs raise. To avoid confusion,
+we <a href="/philosophy/network-services-arent-free-or-nonfree.html">
+avoid describing a service as “free” or
+“proprietary.”</a></p>
+
+<h3>Distinguishing SaaSS from Other Network Services</h3>
+
+<p>Which online services are SaaSS? The clearest example is a
+translation service, which translates (say) English text into Spanish
+text. Translating a text for you is computing that is purely yours.
+You could do it by running a program on your own computer, if only you
+had the right program. (To be ethical, that program should be free.)
+The translation service substitutes for that program, so it is Service
+as a Software Substitute, or SaaSS. Since it denies you control
+over your computing, it does you wrong.</p>
+
+<p>Another clear example is using a service such as Flickr or
+Instagram to modify a photo. Modifying photos is an activity that
+people have done in their own computers for decades; doing it in a
+server you don't control, rather than your own computer, is SaaSS.</p>
+
+<p>Rejecting SaaSS does not mean refusing to use any network servers
+run by anyone other than you. Most servers are not SaaSS because the
+jobs they do are some sort of communication, rather than the user's
+own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to publish information for you to access. Even today this is what
+most web sites do, and it doesn't pose the SaaSS problem, because
+accessing someone's published information isn't doing your own
+computing. Neither is use of a blog site to publish your own works,
+or using a microblogging service such as Twitter or StatusNet. (These
+services may or may not have other problems, depending on details.)
+The same goes for other communication not meant to be private, such as
+chat groups.</p>
+
+<p>In its essence, social networking is a form of communication and
+publication, not SaaSS. However, a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a service is not SaaSS, that does not mean it is OK. There are
+other ethical issues about services. For instance, Facebook
+distributes video in Flash, which pressures users to run nonfree
+software; it requires running nonfree JavaScript code; and it gives
+users a misleading impression of privacy while luring them into baring
+their lives to Facebook. Those are important issues, different from
+the SaaSS issue.
+</p>
+
+<p>Services such as search engines collect data from around the web
+and let you examine it. Looking through their collection of data
+isn't your own computing in the usual sense—you didn't provide
+that collection—so using such a service to search the web is not
+SaaSS. However, using someone else's server to implement a search
+facility for your own site <em>is</em> SaaSS.</p>
+
+<p>Purchasing online is not SaaSS, because the computing
+isn't <em>your own</em> activity; rather, it is done jointly by and
+for you and the store. The real issue in online shopping is whether
+you trust the other party with your money and other personal
+information (starting with your name).</p>
+
+<p>Repository sites such as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p>
+
+<p>Using a joint project's servers isn't SaaSS because the computing
+you do in this way isn't your own. For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's computing. Wikipedia controls its own
+servers, but organizations as well as individuals encounter the
+problem of SaaSS if they do their computing in someone else's
+server.</p>
+
+<p>Some sites offer multiple services, and if one is not SaaSS,
+another may be SaaSS. For instance, the main service of Facebook is
+social networking, and that is not SaaSS; however, it supports
+third-party applications, some of which are SaaSS. Flickr's main
+service is distributing photos, which is not SaaSS, but it also has
+features for editing photos, which is SaaSS. Likewise, using
+Instagram to post a photo is not SaaSS, but using it to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation of a single service
+can become. It invites people to edit a document by running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong. However, it offers an API for uploading
+and downloading documents in standard formats. A free software editor
+can do so through this API. This usage scenario is not SaaSS, because
+it uses Google Docs as a mere repository. Showing all your data to a
+company is bad, but that is a matter of privacy, not SaaSS; depending
+on a service for access to your data is bad, but that is a matter of
+risk, not SaaSS. On the other hand, using the service for converting
+document formats <em>is</em> SaaSS, because it's something you
could
+have done by running a suitable program (free, one hopes) in your own
+computer.</p>
+
+<p>Using Google Docs through a free editor is rare, of course. Most
+often, people use it through the nonfree JavaScript program, which is
+bad like any nonfree program. This scenario might involve SaaSS, too;
+that depends on what part of the editing is done in the JavaScript
+program and what part in the server. We don't know, but since SaaSS
+and proprietary software do similar wrong to the user, it is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues, but publishing through Google Docs has a special problem: it
+is impossible even to <em>view the text</em> of a Google Docs
document
+in a browser without running the nonfree JavaScript code. Thus, you
+should not use Google Docs to publish anything—but the reason
+is not a matter of SaaSS.</p>
+
+<p>The IT industry discourages users from making these distinctions.
+That's what the buzzword “cloud computing” is for. This
+term is so nebulous that it could refer to almost any use of the
+Internet. It includes SaaSS as well as many other network usage
+practices. In any given context, an author who writes
+“cloud” (if a technical person) probably has a specific
+meaning in mind, but usually does not explain that in other articles
+the term has other specific meanings. The term leads people to
+generalize about practices they ought to consider individually.</p>
+
+<p>If “cloud computing” has a meaning, it is not a way of
+doing computing, but rather a way of thinking about computing: a
+devil-may-care approach which says, “Don't ask questions. Don't
+worry about who controls your computing or who holds your data. Don't
+check for a hook hidden inside our service before you swallow it.
+Trust companies without hesitation.” In other words, “Be a
+sucker.” A cloud in the mind is an obstacle to clear thinking.
+For the sake of clear thinking about computing, let's avoid the term
+“cloud.”</p>
+
+<h3 id="renting">Renting a Server Distinguished from SaaSS</h3>
+
+<p>If you rent a server (real or virtual), whose software load you
+have control over, that's not SaaSS. In SaaSS, someone else decides
+what software runs on the server and therefore controls the computing
+it does for you. In the case where you install the software on the
+server, you control what computing it does for you. Thus, the rented
+server is virtually your computer. For this issue, it counts as
+yours.</p>
+
+<p>The <em>data</em> on the rented remote server is less
secure than
+if you had the server at home, but that is a separate issue from
+SaaSS.</p>
+
+<span class="inserted"><ins><em><p>This kind of server rental is
sometimes called “IaaS,”
+but that term fits into a conceptual structure that downplays the issues
+that we consider important.</p></em></ins></span>
+
+<h3>Dealing with the SaaSS Problem</h3>
+
+<p>Only a small fraction of all web sites do SaaSS; most don't raise
+the issue. But what should we do about the ones that raise it?</p>
+
+<p>For the simple case, where you are doing your own computing on data
+in your own hands, the solution is simple: use your own copy of a free
+software application. Do your text editing with your copy of a free
+text editor such as GNU Emacs or a free word processor. Do your photo
+editing with your copy of free software such as GIMP. What if there
+is no free program available? A proprietary program or SaaSS would
+take away your freedom, so you shouldn't use those. You can contribute
+your time or your money to development of a free replacement.</p>
+
+<p>What about collaborating with other individuals as a group? It may
+be hard to do this at present without using a server, and your group
+may not know how to run its own server. If you use someone else's
+server, at least don't trust a server run by a company. A mere
+contract as a customer is no protection unless you could detect a
+breach and could really sue, and the company probably writes its
+contracts to permit a broad range of abuses. The state can subpoena
+your data from the company along with everyone else's, as Obama has
+done to phone companies, supposing the company doesn't volunteer them
+like the US phone companies that illegally wiretapped their customers
+for Bush. If you must use a server, use a server whose operators give
+you a basis for trust beyond a mere commercial relationship.</p>
+
+<p>However, on a longer time scale, we can create alternatives to
+using servers. For instance, we can create a peer-to-peer program
+through which collaborators can share data encrypted. The free
+software community should develop distributed peer-to-peer
+replacements for important “web applications”. It may be
+wise to release them under
+the <a href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>,
since
+they are likely candidates for being converted into server-based
+programs by someone else. The <a href="/">GNU project</a> is
looking
+for volunteers to work on such replacements. We also invite other
+free software projects to consider this issue in their design.</p>
+
+<p>In the meantime, if a company invites you to use its server to do
+your own computing tasks, don't yield; don't use SaaSS. Don't buy or
+install “thin clients”, which are simply computers so weak
+they make you do the real work on a server, unless you're going to use
+them with <em>your</em> server. Use a real computer and keep your
+data there. Do your own computing with your own copy of a free
+program, for your freedom's sake.</p>
+
+<h3>See also:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">The
+Bug Nobody is Allowed to Understand</a>.</p>
+
+</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2010, 2013, 2015, <span
class="removed"><del><strong>2016</strong></del></span> <span
class="inserted"><ins><em>2016, 2018</em></ins></span> Richard
Stallman</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: 2018/05/30 02:01:06 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: philosophy/po/who-does-that-server-really-serve.uk-diff.html
===================================================================
RCS file: philosophy/po/who-does-that-server-really-serve.uk-diff.html
diff -N philosophy/po/who-does-that-server-really-serve.uk-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/po/who-does-that-server-really-serve.uk-diff.html 30 May
2018 02:01:06 -0000 1.1
@@ -0,0 +1,486 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/who-does-that-server-really-serve.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software Foundation</title>
+
+<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Who does that server really serve?</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<blockquote><p>(The first version was published
+in <a
href="http://www.bostonreview.net/richard-stallman-free-software-DRM">
+Boston Review</a>.)</p></blockquote>
+
+<p><strong>On the Internet, proprietary software isn't the only
way to
+lose your freedom. Service as a Software Substitute, or SaaSS, is
+another way to give someone else power over your
computing.</strong></p>
+
+<p>The basic point is, you can have control over a program someone else
+wrote (if it's free), but you can never have control over a service
+someone else runs, so never use a service where in principle a program
+would do.</p>
+
+
+<p>SaaSS means using a service implemented by someone else as a
+substitute for running your copy of a program. The term is ours;
+articles and ads won't use it, and they won't tell you whether a
+service is SaaSS. Instead they will probably use the vague and
+distracting term “cloud”, which lumps SaaSS together with
+various other practices, some abusive and some ok. With the
+explanation and examples in this page, you can tell whether a service
+is SaaSS.</p>
+
+<h3>Background: How Proprietary Software Takes Away Your
Freedom</h3>
+
+<p>Digital technology can give you freedom; it can also take your
+freedom away. The first threat to our control over our computing came
+from <em>proprietary software</em>: software that the users cannot
+control because the owner (a company such as Apple or Microsoft)
+controls it. The owner often takes advantage of this unjust power by
+inserting malicious features such as spyware, back doors, and <a
+href="http://DefectiveByDesign.org">Digital Restrictions Management
+(DRM)</a> (referred to as “Digital Rights Management” in
+their propaganda).</p>
+
+<p>Our solution to this problem is developing <em>free
software</em>
+and rejecting proprietary software. Free software means that you, as
+a user, have four essential freedoms: (0) to run the program as
+you wish, (1) to study and change the source code so it does what
+you wish, (2) to redistribute exact copies, and (3) to
+redistribute copies of your modified versions. (See
+the <a href="/philosophy/free-sw.html">free software
+definition</a>.)</p>
+
+<p>With free software, we, the users, take back control of our
+computing. Proprietary software still exists, but we can exclude it
+from our lives and many of us have done so. However, we are now
+offered another tempting way to cede control over our computing:
+Service as a Software Substitute (SaaSS). For our freedom's sake, we
+have to reject that too.</p>
+
+<h3>How Service as a Software Substitute Takes Away Your
Freedom</h3>
+
+<p>Service as a Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program. Concretely, it means
+that someone sets up a network server that does certain computing
+tasks—for instance, modifying a photo, translating text into
+another language, etc.—then invites users to do computing via
+that server. A user of the server would send her data to the server,
+which does <em>her own computing</em> on the data thus provided,
then
+sends the results back to her or acts directly on her behalf.</p>
+
+<p>The computing is <em>her own</em> because, by assumption,
she
+could, in principle, have done it by running a program on her own
+computer (whether or not that program is available to her at
+present). In cases where this assumption is not so, it isn't SaaSS.</p>
+
+<p>These servers wrest control from the users even more inexorably
+than proprietary software. With proprietary software, users typically
+get an executable file but not the source code. That makes it hard to
+study the code that is running, so it's hard to determine what the
+program really does, and hard to change it.</p>
+
+<p>With SaaSS, the users do not have even the executable file that
+does their computing: it is on someone else's server, where the users
+can't see or touch it. Thus it is impossible for them to ascertain
+what it really does, and impossible to change it.</p>
+
+<p>Furthermore, SaaSS automatically leads to consequences equivalent
+to the malicious features of certain proprietary software.</p>
+
+<p> For instance, some proprietary programs are “spyware”:
+the program <a href="/philosophy/proprietary-surveillance.html">
+sends out data about users' computing activities</a>.
+Microsoft Windows sends information about users' activities to
+Microsoft. Windows Media Player reports what each user watches or
+listens to. The Amazon Kindle reports which pages of which books the
+user looks at, and when. Angry Birds reports the user's geolocation
+history.</p>
+
+<p>Unlike proprietary software, SaaSS does not require covert code to
+obtain the user's data. Instead, users must send their data to the
+server in order to use it. This has the same effect as spyware: the
+server operator gets the data—with no special effort, by the
+nature of SaaSS. Amy Webb, who intended never to post any photos of
+her daughter, made the mistake of using SaaSS (Instagram) to edit
+photos of her. Eventually
+<a
href="http://www.slate.com/articles/technology/data_mine_1/2013/09/privacy_facebook_kids_don_t_post_photos_of_your_kids_on_social_media.html">
they
+leaked from there</a>.
+</p>
+
+<p>Theoretically, homomorphic encryption might some day advance to the
+point where future SaaSS services might be constructed to be unable to
+understand some of the data that users send them. Such
+services <em>could</em> be set up not to snoop on users; this does
not
+mean they <em>will</em> do no snooping.</p>
+
+<p>Some proprietary operating systems have a universal back door,
+permitting someone to remotely install software changes. For
+instance, Windows has a universal back door with which Microsoft can
+forcibly change any software on the machine. Nearly all portable
+phones have them, too. Some proprietary applications also have
+universal back doors; for instance, the Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS, the server operator can change the software in use on
+the server. He ought to be able to do this, since it's his computer;
+but the result is the same as using a proprietary application program
+with a universal back door: someone has the power to silently impose
+changes in how the user's computing gets done.</p>
+
+<p>Thus, SaaSS is equivalent to running proprietary software with
+spyware and a universal back door. It gives the server operator
+unjust power over the user, and that power is something we must
+resist.</p>
+
+<h3>SaaSS and SaaS</h3>
+
+<p>Originally we referred to this problematical practice as
+“SaaS”, which stands for “Software as a
+Service”. It's a commonly used term for setting up software on a
+server rather than offering copies of it to users, and we thought it
+described precisely the cases where this problem occurs.</p>
+
+<p>Subsequently we became aware that the term SaaS is sometimes used for
+communication services—activities for which this issue is not
+applicable. In addition, the term “Software as a Service”
+doesn't explain <em>why</em> the practice is bad. So we coined
the term
+“Service as a Software Substitute”, which defines the bad
+practice more clearly and says what is bad about it.</p>
+
+<h3>Untangling the SaaSS Issue from the Proprietary Software
Issue</h3>
+
+<p>SaaSS and proprietary software lead to similar harmful results, but
+the mechanisms are different. With proprietary software, the
+mechanism is that you have and use a copy which is difficult and/or
+illegal to change. With SaaSS, the mechanism is that you don't have
+the copy that's doing your computing.</p>
+
+<p>These two issues are often confused, and not only by accident. Web
+developers use the vague term “web application” to lump
+the server software together with programs run on your machine in your
+browser. Some web pages install nontrivial, even large JavaScript
+programs into your browser without informing
+you. <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they cause the same sort of injustice as any
+other nonfree software. Here, however, we are concerned with the
+issue of using the service itself.</p>
+
+<p>Many free software supporters assume that the problem of SaaSS will
+be solved by developing free software for servers. For the server
+operator's sake, the programs on the server had better be free; if
+they are proprietary, their developers/owners have power over the
+server. That's unfair to the server operator, and doesn't help the
+server's users at all. But if the programs on the server are free,
+that doesn't protect <em>the server's users</em> from the effects
of
+SaaSS. These programs liberate the server operator, but not the
+server's users.</p>
+
+<p>Releasing the server software source code does benefit the
+community: it enables suitably skilled users to set up similar
+servers, perhaps changing the
+software. <a href="/licenses/license-recommendations.html"> We
+recommend using the GNU Affero GPL</a> as the license for programs
+often used on servers.</p>
+
+<p>But none of these servers would give you control over computing you
+do on it, unless it's <em>your</em> server (one whose software load
+you control, regardless of whether the machine is your property). It
+may be OK to trust your friend's server for some jobs, just as you
+might let your friend maintain the software on your own computer.
+Outside of that, all these servers would be SaaSS for you. SaaSS
+always subjects you to the power of the server operator, and the only
+remedy is, <em>Don't use SaaSS!</em> Don't use someone else's
server
+to do your own computing on data provided by you.</p>
+
+<p>This issue demonstrates the depth of the difference between
+“open” and “free”. Source code that is open
+source <a href="/philosophy/free-open-overlap.html">is, nearly always,
+free</a>. However, the idea of
+an <a href="http://opendefinition.org/software-service">“open
+software” service</a>, meaning one whose server software is open
+source and/or free, fails to address the issue of SaaSS.</p>
+
+<p>Services are fundamentally different from programs, and the ethical
+issues that services raise are fundamentally different from the issues
+that programs raise. To avoid confusion,
+we <a href="/philosophy/network-services-arent-free-or-nonfree.html">
+avoid describing a service as “free” or
+“proprietary.”</a></p>
+
+<h3>Distinguishing SaaSS from Other Network Services</h3>
+
+<p>Which online services are SaaSS? The clearest example is a
+translation service, which translates (say) English text into Spanish
+text. Translating a text for you is computing that is purely yours.
+You could do it by running a program on your own computer, if only you
+had the right program. (To be ethical, that program should be free.)
+The translation service substitutes for that program, so it is Service
+as a Software Substitute, or SaaSS. Since it denies you control
+over your computing, it does you wrong.</p>
+
+<p>Another clear example is using a service such as Flickr or
+Instagram to modify a photo. Modifying photos is an activity that
+people have done in their own computers for decades; doing it in a
+server you don't control, rather than your own computer, is SaaSS.</p>
+
+<p>Rejecting SaaSS does not mean refusing to use any network servers
+run by anyone other than you. Most servers are not SaaSS because the
+jobs they do are some sort of communication, rather than the user's
+own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to publish information for you to access. Even today this is what
+most web sites do, and it doesn't pose the SaaSS problem, because
+accessing someone's published information isn't doing your own
+computing. Neither is use of a blog site to publish your own works,
+or using a microblogging service such as Twitter or StatusNet. (These
+services may or may not have other problems, depending on details.)
+The same goes for other communication not meant to be private, such as
+chat groups.</p>
+
+<p>In its essence, social networking is a form of communication and
+publication, not SaaSS. However, a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a service is not SaaSS, that does not mean it is OK. There are
+other ethical issues about services. For instance, Facebook
+distributes video in Flash, which pressures users to run nonfree
+software; it requires running nonfree JavaScript code; and it gives
+users a misleading impression of privacy while luring them into baring
+their lives to Facebook. Those are important issues, different from
+the SaaSS issue.
+</p>
+
+<p>Services such as search engines collect data from around the web
+and let you examine it. Looking through their collection of data
+isn't your own computing in the usual sense—you didn't provide
+that collection—so using such a service to search the web is not
+SaaSS. However, using someone else's server to implement a search
+facility for your own site <em>is</em> SaaSS.</p>
+
+<p>Purchasing online is not SaaSS, because the computing
+isn't <em>your own</em> activity; rather, it is done jointly by and
+for you and the store. The real issue in online shopping is whether
+you trust the other party with your money and other personal
+information (starting with your name).</p>
+
+<p>Repository sites such as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p>
+
+<p>Using a joint project's servers isn't SaaSS because the computing
+you do in this way isn't your own. For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's computing. Wikipedia controls its own
+servers, but organizations as well as individuals encounter the
+problem of SaaSS if they do their computing in someone else's
+server.</p>
+
+<p>Some sites offer multiple services, and if one is not SaaSS,
+another may be SaaSS. For instance, the main service of Facebook is
+social networking, and that is not SaaSS; however, it supports
+third-party applications, some of which are SaaSS. Flickr's main
+service is distributing photos, which is not SaaSS, but it also has
+features for editing photos, which is SaaSS. Likewise, using
+Instagram to post a photo is not SaaSS, but using it to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation of a single service
+can become. It invites people to edit a document by running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong. However, it offers an API for uploading
+and downloading documents in standard formats. A free software editor
+can do so through this API. This usage scenario is not SaaSS, because
+it uses Google Docs as a mere repository. Showing all your data to a
+company is bad, but that is a matter of privacy, not SaaSS; depending
+on a service for access to your data is bad, but that is a matter of
+risk, not SaaSS. On the other hand, using the service for converting
+document formats <em>is</em> SaaSS, because it's something you
could
+have done by running a suitable program (free, one hopes) in your own
+computer.</p>
+
+<p>Using Google Docs through a free editor is rare, of course. Most
+often, people use it through the nonfree JavaScript program, which is
+bad like any nonfree program. This scenario might involve SaaSS, too;
+that depends on what part of the editing is done in the JavaScript
+program and what part in the server. We don't know, but since SaaSS
+and proprietary software do similar wrong to the user, it is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues, but publishing through Google Docs has a special problem: it
+is impossible even to <em>view the text</em> of a Google Docs
document
+in a browser without running the nonfree JavaScript code. Thus, you
+should not use Google Docs to publish anything—but the reason
+is not a matter of SaaSS.</p>
+
+<p>The IT industry discourages users from making these distinctions.
+That's what the buzzword “cloud computing” is for. This
+term is so nebulous that it could refer to almost any use of the
+Internet. It includes SaaSS as well as many other network usage
+practices. In any given context, an author who writes
+“cloud” (if a technical person) probably has a specific
+meaning in mind, but usually does not explain that in other articles
+the term has other specific meanings. The term leads people to
+generalize about practices they ought to consider individually.</p>
+
+<p>If “cloud computing” has a meaning, it is not a way of
+doing computing, but rather a way of thinking about computing: a
+devil-may-care approach which says, “Don't ask questions. Don't
+worry about who controls your computing or who holds your data. Don't
+check for a hook hidden inside our service before you swallow it.
+Trust companies without hesitation.” In other words, “Be a
+sucker.” A cloud in the mind is an obstacle to clear thinking.
+For the sake of clear thinking about computing, let's avoid the term
+“cloud.”</p>
+
+<h3 id="renting">Renting a Server Distinguished from SaaSS</h3>
+
+<p>If you rent a server (real or virtual), whose software load you
+have control over, that's not SaaSS. In SaaSS, someone else decides
+what software runs on the server and therefore controls the computing
+it does for you. In the case where you install the software on the
+server, you control what computing it does for you. Thus, the rented
+server is virtually your computer. For this issue, it counts as
+yours.</p>
+
+<p>The <em>data</em> on the rented remote server is less
secure than
+if you had the server at home, but that is a separate issue from
+SaaSS.</p>
+
+<span class="inserted"><ins><em><p>This kind of server rental is
sometimes called “IaaS,”
+but that term fits into a conceptual structure that downplays the issues
+that we consider important.</p></em></ins></span>
+
+<h3>Dealing with the SaaSS Problem</h3>
+
+<p>Only a small fraction of all web sites do SaaSS; most don't raise
+the issue. But what should we do about the ones that raise it?</p>
+
+<p>For the simple case, where you are doing your own computing on data
+in your own hands, the solution is simple: use your own copy of a free
+software application. Do your text editing with your copy of a free
+text editor such as GNU Emacs or a free word processor. Do your photo
+editing with your copy of free software such as GIMP. What if there
+is no free program available? A proprietary program or SaaSS would
+take away your freedom, so you shouldn't use those. You can contribute
+your time or your money to development of a free replacement.</p>
+
+<p>What about collaborating with other individuals as a group? It may
+be hard to do this at present without using a server, and your group
+may not know how to run its own server. If you use someone else's
+server, at least don't trust a server run by a company. A mere
+contract as a customer is no protection unless you could detect a
+breach and could really sue, and the company probably writes its
+contracts to permit a broad range of abuses. The state can subpoena
+your data from the company along with everyone else's, as Obama has
+done to phone companies, supposing the company doesn't volunteer them
+like the US phone companies that illegally wiretapped their customers
+for Bush. If you must use a server, use a server whose operators give
+you a basis for trust beyond a mere commercial relationship.</p>
+
+<p>However, on a longer time scale, we can create alternatives to
+using servers. For instance, we can create a peer-to-peer program
+through which collaborators can share data encrypted. The free
+software community should develop distributed peer-to-peer
+replacements for important “web applications”. It may be
+wise to release them under
+the <a href="/licenses/why-affero-gpl.html"> GNU Affero GPL</a>,
since
+they are likely candidates for being converted into server-based
+programs by someone else. The <a href="/">GNU project</a> is
looking
+for volunteers to work on such replacements. We also invite other
+free software projects to consider this issue in their design.</p>
+
+<p>In the meantime, if a company invites you to use its server to do
+your own computing tasks, don't yield; don't use SaaSS. Don't buy or
+install “thin clients”, which are simply computers so weak
+they make you do the real work on a server, unless you're going to use
+them with <em>your</em> server. Use a real computer and keep your
+data there. Do your own computing with your own copy of a free
+program, for your freedom's sake.</p>
+
+<h3>See also:</h3>
+<p><a href="/philosophy/bug-nobody-allowed-to-understand.html">The
+Bug Nobody is Allowed to Understand</a>.</p>
+
+</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 & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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 © 2010, 2013, 2015, <span
class="removed"><del><strong>2016</strong></del></span> <span
class="inserted"><ins><em>2016, 2018</em></ins></span> Richard
Stallman</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: 2018/05/30 02:01:06 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www licenses/gpl-howto.de.html licenses/po/gpl-...,
GNUN <=