[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy who-does-that-server-really-serv...
|
From: |
GNUN |
|
Subject: |
www/philosophy who-does-that-server-really-serv... |
|
Date: |
Mon, 05 Aug 2013 16:58:57 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 13/08/05 16:58:57
Modified files:
philosophy : who-does-that-server-really-serve.hr.html
Added files:
philosophy/po : who-does-that-server-really-serve.hr-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/who-does-that-server-really-serve.hr.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/who-does-that-server-really-serve.hr-diff.html?cvsroot=www&rev=1.1
Patches:
Index: who-does-that-server-really-serve.hr.html
===================================================================
RCS file: /web/www/www/philosophy/who-does-that-server-really-serve.hr.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- who-does-that-server-really-serve.hr.html 7 May 2013 21:58:33 -0000
1.2
+++ who-does-that-server-really-serve.hr.html 5 Aug 2013 16:58:56 -0000
1.3
@@ -10,6 +10,13 @@
<!--#include
virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.hr.html" -->
+<!--#set var="PO_FILE"
+ value='<a
href="http://www.gnu.org/philosophy/po/who-does-that-server-really-serve.hr.po";>
+ http://www.gnu.org/philosophy/po/who-does-that-server-really-serve.hr.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.hr-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2013-06-06" -->
+ <!--#include virtual="/server/outdated.hr.html" -->
<h2>Koga taj poslužitelj stvarno poslužuje?</h2>
<p><strong>Richard Stallman</strong></p>
@@ -325,7 +332,7 @@
<p><!-- timestamp start -->
Zadnji put promijenjeno:
-$Date: 2013/05/07 21:58:33 $
+$Date: 2013/08/05 16:58:56 $
<!-- timestamp end -->
</p>
Index: po/who-does-that-server-really-serve.hr-diff.html
===================================================================
RCS file: po/who-does-that-server-really-serve.hr-diff.html
diff -N po/who-does-that-server-really-serve.hr-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/who-does-that-server-really-serve.hr-diff.html 5 Aug 2013 16:58:56
-0000 1.1
@@ -0,0 +1,533 @@
+<!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" -->
+<span class="inserted"><ins><em><!-- Parent-Version: 1.75
--></em></ins></span>
+<title>Who Does That Server Really Serve?
+- GNU Project - Free Software <span class="removed"><del><strong>Foundation
(FSF)</title></strong></del></span> <span
class="inserted"><ins><em>Foundation</title></em></ins></span>
+
+<!--#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>
+
+<span class="removed"><del><strong><p>(First</strong></del></span>
+
+<span class="inserted"><ins><em><blockquote><p>(The first version
was</em></ins></span> published <span
class="removed"><del><strong>by</strong></del></span>
+<span class="inserted"><ins><em>in</em></ins></span> <a <span
class="removed"><del><strong>href="http://bostonreview.net/BR35.2/stallman.php"></strong></del></span>
<span
class="inserted"><ins><em>href="http://www.bostonreview.net/richard-stallman-free-software-DRM"></em></ins></span>
+Boston <span
class="removed"><del><strong>Review</a>.)</p></strong></del></span>
<span
class="inserted"><ins><em>Review</a>.)</p></blockquote></em></ins></span>
+
+<p><strong>On the Internet, proprietary software isn't the only
way to
+lose your freedom. <span
class="removed"><del><strong>Software</strong></del></span> <span
class="inserted"><ins><em>Service</em></ins></span> as a <span
class="removed"><del><strong>Service</strong></del></span> <span
class="inserted"><ins><em>Software Substitute, or SaaSS,</em></ins></span> is
+another way to let someone else have power over your
+computing.</strong></p>
+
+<span class="inserted"><ins><em>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.</em></ins></span>
+
+<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 now face a
+new threat to our control over our computing: <span
class="removed"><del><strong>Software</strong></del></span> <span
class="inserted"><ins><em>Service</em></ins></span> as a <span
class="removed"><del><strong>Service.</strong></del></span> <span
class="inserted"><ins><em>Software
+Substitute (SaaSS).</em></ins></span> For our freedom's sake, we have to
reject that
+too.</p>
+
+<h3>How <span
class="removed"><del><strong>Software</strong></del></span> <span
class="inserted"><ins><em>Service</em></ins></span> as a <span
class="removed"><del><strong>Service</strong></del></span> <span
class="inserted"><ins><em>Software Substitute</em></ins></span> Takes Away Your
Freedom</h3>
+
+<span class="removed"><del><strong><p>Software</strong></del></span>
+
+<span class="inserted"><ins><em><p>Service</em></ins></span> as a <span
class="removed"><del><strong>Service (SaaS)</strong></del></span> <span
class="inserted"><ins><em>Software Substitute (SaaSS) means using a service as a
+substitute for running your copy of a program. Concretely,
it</em></ins></span> means
+that someone sets up a network server that does certain computing <span
class="removed"><del><strong>tasks—running spreadsheets,
+word processing,</strong></del></span>
+<span class="inserted"><ins><em>tasks—for instance, modifying a
photo,</em></ins></span> translating text into
+another language, etc.—then invites users to do <span
class="removed"><del><strong>their</strong></del></span> computing <span
class="removed"><del><strong>on</strong></del></span> <span
class="inserted"><ins><em>via</em></ins></span>
+that server.
+<span class="removed"><del><strong>Users</strong></del></span> <span
class="inserted"><ins><em>A user of the server would</em></ins></span> send
<span class="removed"><del><strong>their</strong></del></span> <span
class="inserted"><ins><em>her</em></ins></span> data to the server,
+which does <span class="removed"><del><strong>their
computing</strong></del></span> <span class="inserted"><ins><em><em>her
own computing</em></em></ins></span> on the data thus provided, then
+sends the results back <span class="inserted"><ins><em>to
her</em></ins></span> or acts <span
class="inserted"><ins><em>directly</em></ins></span> on <span
class="removed"><del><strong>them
+directly.</p></strong></del></span> <span class="inserted"><ins><em>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). When this assumption is not so, it isn't
SaaSS.</p></em></ins></span>
+
+<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
+<span class="removed"><del><strong>for programmers</strong></del></span> 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 <span class="removed"><del><strong>SaaS,</strong></del></span>
<span class="inserted"><ins><em>SaaSS,</em></ins></span> the users do not have
even the executable <span
class="removed"><del><strong>file:</strong></del></span> <span
class="inserted"><ins><em>file that
+does their computing:</em></ins></span> it is on
+<span class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>someone else's</em></ins></span> 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, <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> automatically leads to <span
class="removed"><del><strong>harmful</strong></del></span> consequences
equivalent
+to the malicious features of certain proprietary <span
class="removed"><del><strong>software.</strong></del></span> <span
class="inserted"><ins><em>software.</p>
+
+<p></em></ins></span> For instance, some proprietary programs are
“spyware”:
+the program sends out data about users' computing activities.
+Microsoft Windows sends information about users' activities to
+Microsoft. Windows Media Player <span class="removed"><del><strong>and
RealPlayer report</strong></del></span> <span
class="inserted"><ins><em>reports</em></ins></span> what each user watches or
+listens <span class="removed"><del><strong>to.</p></strong></del></span>
<span class="inserted"><ins><em>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></em></ins></span>
+
+<p>Unlike proprietary software, <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> 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 <span class="removed"><del><strong>data. He gets it
with</strong></del></span> <span
class="inserted"><ins><em>data—with</em></ins></span> no special effort,
by
+the nature of <span
class="removed"><del><strong>SaaS.</p></strong></del></span> <span
class="inserted"><ins><em>SaaSS.</p></em></ins></span>
+
+<p>Some proprietary <span class="removed"><del><strong>programs can
mistreat users under remote command.</strong></del></span> <span
class="inserted"><ins><em>operating systems have a universal back door,
+permitting someone to remotely install software changes.</em></ins></span> For
+instance, Windows has a <span
class="inserted"><ins><em>universal</em></ins></span> back door with which
Microsoft can
+forcibly change any software on the machine. <span
class="removed"><del><strong>The Amazon Kindle e-book
+reader (whose name suggests it's intended to burn people's books) has
+an Orwellian</strong></del></span> <span class="inserted"><ins><em>Nearly all
portable
+phones have them, too. Some proprietary applications also have
+universal</em></ins></span> back <span class="removed"><del><strong>door that
Amazon used in 2009
+to <a
href="http://www.nytimes.com/2009/07/18/technology/companies/18amazon.html";
+>remotely delete</a> Kindle copies of Orwell's books
<cite>1984</cite> and
+<cite>Animal Farm</cite> which</strong></del></span> <span
class="inserted"><ins><em>doors; for instance,</em></ins></span> the <span
class="removed"><del><strong>users had purchased from Amazon.</p>
+
+<p>SaaS inherently gives</strong></del></span> <span
class="inserted"><ins><em>Steam client for GNU/Linux
+allows the developer to remotely install modified versions.</p>
+
+<p>With SaaSS,</em></ins></span> the server operator <span
class="removed"><del><strong>the power to</strong></del></span> <span
class="inserted"><ins><em>can</em></ins></span> change the software in <span
class="removed"><del><strong>use, or</strong></del></span> <span
class="inserted"><ins><em>use on</em></ins></span>
+the <span class="removed"><del><strong>users' data being operated on. Once
again, no
+special code is needed</strong></del></span> <span
class="inserted"><ins><em>server. He ought to be able</em></ins></span> to do
<span class="removed"><del><strong>this.</p>
+
+<p>Thus, SaaS</strong></del></span> <span
class="inserted"><ins><em>this, since it's his computer;
+but the result</em></ins></span> is <span
class="removed"><del><strong>equivalent to total spyware
and</strong></del></span> <span class="inserted"><ins><em>the same as using a
proprietary application program
+with</em></ins></span> a <span class="removed"><del><strong>gaping
wide</strong></del></span> <span
class="inserted"><ins><em>universal</em></ins></span> back
+<span class="removed"><del><strong>door, and gives</strong></del></span> <span
class="inserted"><ins><em>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</em></ins></span> the server
operator
+unjust power over the <span class="removed"><del><strong>user. We
+can't accept that.</p>
+
+<h3>Untangling</strong></del></span> <span
class="inserted"><ins><em>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</em></ins></span> the <span
class="inserted"><ins><em>term</em></ins></span> SaaS <span
class="inserted"><ins><em>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</em></ins></span> Issue from the Proprietary
Software Issue</h3>
+
+<span class="removed"><del><strong><p>SaaS</strong></del></span>
+
+<span class="inserted"><ins><em><p>SaaSS</em></ins></span> and
proprietary software lead to similar harmful results, but
+the <span class="removed"><del><strong>causal</strong></del></span> mechanisms
are different. With proprietary software, the
+<span class="removed"><del><strong>cause</strong></del></span>
+<span class="inserted"><ins><em>mechanism</em></ins></span> is that you have
and use a copy which is difficult <span
class="removed"><del><strong>or</strong></del></span> <span
class="inserted"><ins><em>and/or</em></ins></span>
+illegal to change. With <span
class="removed"><del><strong>SaaS,</strong></del></span> <span
class="inserted"><ins><em>SaaSS,</em></ins></span> the <span
class="removed"><del><strong>cause</strong></del></span> <span
class="inserted"><ins><em>mechanism</em></ins></span> is that you <span
class="removed"><del><strong>use a copy you</strong></del></span> don't
+<span class="removed"><del><strong>have.</p></strong></del></span> <span
class="inserted"><ins><em>have
+the copy that's doing your computing.</p></em></ins></span>
+
+<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 <span class="removed"><del><strong>nontrivial
or</strong></del></span> <span
class="inserted"><ins><em>nontrivial,</em></ins></span> even large JavaScript
+programs <span class="removed"><del><strong>temporarily</strong></del></span>
into your browser without informing
+you. <a href="/philosophy/javascript-trap.html">When these JavaScript
+programs are nonfree</a>, they are <span class="removed"><del><strong>as
bad</strong></del></span> <span class="inserted"><ins><em>the same sort of
problem</em></ins></span> as any
+other nonfree software. Here, however, we are concerned with the
+problem of the server software itself.</p>
+
+<p>Many free software supporters assume that the problem of <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> 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 owners have power over the server. That's
+unfair to the operator, and doesn't help <span
class="removed"><del><strong>you</strong></del></span> <span
class="inserted"><ins><em>the users</em></ins></span> at all. But if the
+programs on the server are free, that doesn't protect <span
class="removed"><del><strong>you <em>as the</strong></del></span> <span
class="inserted"><ins><em><em>the</em></ins></span> server's <span
class="removed"><del><strong>user</em></strong></del></span>
+<span class="inserted"><ins><em>users</em></em></ins></span> from the
effects of <span class="removed"><del><strong>SaaS. They give freedom
to</strong></del></span> <span class="inserted"><ins><em>SaaSS. These programs
liberate</em></ins></span> the
+<span class="inserted"><ins><em>server</em></ins></span> operator, but not
<span class="removed"><del><strong>to you.</p></strong></del></span>
<span class="inserted"><ins><em>the server's users.</p></em></ins></span>
+
+<p>Releasing the server software source code does benefit the
+community: <span class="inserted"><ins><em>it enables</em></ins></span>
suitably skilled users <span
class="removed"><del><strong>can</strong></del></span> <span
class="inserted"><ins><em>to</em></ins></span> set up similar
+servers, perhaps changing the
+software. <span class="removed"><del><strong>But</strong></del></span> <span
class="inserted"><ins><em><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</em></ins></span> none of these servers would give you control
over computing you
+do on it, unless it's <em>your</em> server.
+<span class="removed"><del><strong>The rest would</strong></del></span> <span
class="inserted"><ins><em>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,</em></ins></span> all
+<span class="inserted"><ins><em>these servers would</em></ins></span> be <span
class="removed"><del><strong>SaaS. SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS for you. SaaSS</em></ins></span> always
subjects you to
+the power of the server operator, and the only remedy is, <em>Don't
+use <span class="removed"><del><strong>SaaS!</em></strong></del></span>
<span class="inserted"><ins><em>SaaSS!</em></em></ins></span> Don't use
someone else's server to do your own
+computing on data provided by you.</p>
+
+<h3>Distinguishing <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> from Other Network
Services</h3>
+
+<span class="removed"><del><strong><p>Does avoiding SaaS mean you refuse
to use any network servers run
+by anyone other than you? Not at all. Most servers do not raise this
+issue, because the job</strong></del></span>
+
+<span class="inserted"><ins><em><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</em></ins></span> you <span
class="removed"><del><strong>do with them isn't your own</strong></del></span>
<span class="inserted"><ins><em>is</em></ins></span> computing
+<span class="removed"><del><strong>except in a trivial sense.</p>
+
+<p>The original purpose of web servers wasn't to</strong></del></span>
<span class="inserted"><ins><em>that is purely yours.
+You could</em></ins></span> do <span class="removed"><del><strong>computing
for you,</strong></del></span> it <span class="removed"><del><strong>was
to</strong></del></span> <span class="inserted"><ins><em>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 instead of 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 not the user's own computing.</p>
+
+<p>The original idea of web servers wasn't to do computing for you, it
+was to</em></ins></span> publish information for you to access. Even today
this is what
+most web sites do, and it doesn't pose the <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> problem, because
+accessing someone's published information isn't <span
class="removed"><del><strong>a matter of</strong></del></span> doing your own
+computing. Neither is publishing your own materials via a blog site
+or a microblogging service such as Twitter or <span
class="removed"><del><strong>identi.ca.</strong></del></span> <span
class="inserted"><ins><em>StatusNet. (These
+services may have other problems, of course.)</em></ins></span> The same goes
for <span class="inserted"><ins><em>other</em></ins></span>
+communication not meant to be private, such as chat
+<span class="removed"><del><strong>groups. Social</strong></del></span> <span
class="inserted"><ins><em>groups.</p>
+
+<p>In its essence, social</em></ins></span> networking <span
class="removed"><del><strong>can extend into SaaS; however, at root
it</strong></del></span> is <span
class="removed"><del><strong>just</strong></del></span> a <span
class="removed"><del><strong>method</strong></del></span> <span
class="inserted"><ins><em>form</em></ins></span> of communication and
+publication, not <span class="removed"><del><strong>SaaS. If you
+use the</strong></del></span> <span class="inserted"><ins><em>SaaSS. However,
a service whose main facility is
+social networking can have features or extensions which are SaaSS.</p>
+
+<p>If a</em></ins></span> service <span class="removed"><del><strong>for
minor editing of what you're going to communicate,
+that</strong></del></span> is not <span class="inserted"><ins><em>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</em></ins></span> a <span class="removed"><del><strong>significant
issue.</p></strong></del></span> <span
class="inserted"><ins><em>misleading impression of privacy while luring them
into baring
+their lives to Facebook. Those are important issues, different from
+the SaaSS issue.
+</p></em></ins></span>
+
+<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
+<span class="removed"><del><strong>SaaS. (However,</strong></del></span>
+<span class="inserted"><ins><em>SaaSS. However,</em></ins></span> using
someone else's <span class="removed"><del><strong>search
engine</strong></del></span> <span
class="inserted"><ins><em>server</em></ins></span> to implement a search
+facility for your own site <em>is</em> <span
class="removed"><del><strong>SaaS.)</p>
+
+<p>E-commerce</strong></del></span> <span
class="inserted"><ins><em>SaaSS.</p>
+
+<p>Purchasing online</em></ins></span> is not <span
class="removed"><del><strong>SaaS,</strong></del></span> <span
class="inserted"><ins><em>SaaSS,</em></ins></span> because the computing
+isn't <span class="removed"><del><strong>solely yours;</strong></del></span>
<span class="inserted"><ins><em><em>your
own</em>;</em></ins></span> rather, it is done jointly <span
class="inserted"><ins><em>by and</em></ins></span> for you and <span
class="removed"><del><strong>another party. So there's no
+particular reason why you alone should expect to control that
+computing.</strong></del></span>
+<span class="inserted"><ins><em>the store.</em></ins></span> The real issue
in <span class="removed"><del><strong>e-commerce</strong></del></span> <span
class="inserted"><ins><em>online shopping</em></ins></span> is whether you
trust the
+other party with your money and <span
class="inserted"><ins><em>other</em></ins></span> personal <span
class="removed"><del><strong>information.</p></strong></del></span> <span
class="inserted"><ins><em>information (starting
+with your name).</p>
+
+<p>Repository sites such as as Savannah and SourceForge are not
+inherently SaaSS, because a repository's job is publication of data
+supplied to it.</p></em></ins></span>
+
+<p>Using a joint project's servers isn't <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> because the computing
+you do in this way isn't <span class="removed"><del><strong>yours
personally.</strong></del></span> <span class="inserted"><ins><em>your
own.</em></ins></span> For instance, if you edit pages on
+Wikipedia, you are not doing your own computing; rather, you are
+collaborating in Wikipedia's <span
class="removed"><del><strong>computing.</p>
+
+<p>Wikipedia</strong></del></span> <span
class="inserted"><ins><em>computing. Wikipedia</em></ins></span> controls its
own
+servers, but <span class="removed"><del><strong>groups can
face</strong></del></span> <span class="inserted"><ins><em>organizations as
well as individuals encounter</em></ins></span> the
+problem of <span class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> if they do their <span
class="removed"><del><strong>group activities on someone else's server.
+Fortunately, development hosting sites such as Savannah and
+SourceForge don't pose the SaaS problem, because what groups do there
+is mainly publication and public communication, rather than their own
+private computing.</p>
+
+<p>Multiplayer games are a group activity carried out
on</strong></del></span> <span class="inserted"><ins><em>computing
in</em></ins></span> someone else's <span class="removed"><del><strong>server,
which makes them SaaS. But where the data involved is
+just the state of play and the score, the worst wrong the operator
+might commit is favoritism. You might well ignore that risk, since it
+seems unlikely and very little is at stake. On the other hand, when
+the game becomes more than just a game, the issue changes.</p>
+
+<p>“Backend as a Service”, or BaaS, is a kind of SaaS,
because it
+involves running your own web service on top of software that you
+can't control. If you set up a service using BaaS, the BaaS platform
+may well collect information about your users as well as you.</p>
+
+<p>Which online services are SaaS? Google Docs is a clear example.
+Its basic activity is editing, and Google encourages people to use it
+for their own editing; this is SaaS. It offers the added feature of
+collaborative editing, but adding participants doesn't alter the fact
+that editing on the server is SaaS. (In addition, Google Docs is
+unacceptable because it installs a
+large <a href="/philosophy/javascript-trap.html"> nonfree JavaScript
program</a>
+into the user's browser.) If using a service for communication or
+collaboration requires doing substantial parts of your own computing
+with it too, that computing is SaaS even if the communication is
+not.</p></strong></del></span>
+<span class="inserted"><ins><em>server.</p></em></ins></span>
+
+<p>Some sites offer multiple services, and if one is not <span
class="removed"><del><strong>SaaS,</strong></del></span> <span
class="inserted"><ins><em>SaaSS,</em></ins></span>
+another may be <span class="removed"><del><strong>SaaS.</strong></del></span>
<span class="inserted"><ins><em>SaaSS.</em></ins></span> For instance, the
main service of Facebook is
+social networking, and that is not <span
class="removed"><del><strong>SaaS;</strong></del></span> <span
class="inserted"><ins><em>SaaSS;</em></ins></span> however, it supports
+third-party applications, some of which <span class="removed"><del><strong>may
be SaaS.</strong></del></span> <span class="inserted"><ins><em>are
SaaSS.</em></ins></span> Flickr's main
+service is distributing photos, which is not <span
class="removed"><del><strong>SaaS,</strong></del></span> <span
class="inserted"><ins><em>SaaSS,</em></ins></span> but it also has
+features for editing photos, which is <span
class="removed"><del><strong>SaaS.</p>
+
+<p>Some sites whose main service</strong></del></span> <span
class="inserted"><ins><em>SaaSS. Likewise, using
+Instagram to post a photo</em></ins></span> is <span
class="removed"><del><strong>publication and communication
+extend</strong></del></span> <span class="inserted"><ins><em>not SaaSS, but
using</em></ins></span> it <span class="removed"><del><strong>with
“contact management”: keeping track</strong></del></span> <span
class="inserted"><ins><em>to transform the
+photo is SaaSS.</p>
+
+<p>Google Docs shows how complex the evaluation</em></ins></span> of
<span class="inserted"><ins><em>a single service
+can become. It invites</em></ins></span> people <span
class="removed"><del><strong>you have relationships with. Sending
mail</strong></del></span> to <span class="removed"><del><strong>those
people</strong></del></span> <span class="inserted"><ins><em>edit a document by
running a
+large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
+program</a>, clearly wrong. However, it offers an API</em></ins></span>
for
+<span class="removed"><del><strong>you</strong></del></span> <span
class="inserted"><ins><em>uploading
+and downloading documents in standard formats. A free software editor
+can do so through this API. This usage scenario</em></ins></span> is not
<span class="removed"><del><strong>SaaS, but keeping track
of</strong></del></span> <span class="inserted"><ins><em>SaaSS, because
+it uses Google Docs as a mere repository. Showing all</em></ins></span> your
<span class="removed"><del><strong>dealings with them, if
+substantial,</strong></del></span> <span class="inserted"><ins><em>data to a
+company is bad, but that</em></ins></span> is <span
class="removed"><del><strong>SaaS.</p>
+
+<p>If</strong></del></span> <span class="inserted"><ins><em>a matter of
privacy, not SaaSS; depending
+on</em></ins></span> a service <span class="inserted"><ins><em>for access to
your data</em></ins></span> is <span class="removed"><del><strong>not
SaaS,</strong></del></span> <span class="inserted"><ins><em>bad,
but</em></ins></span> that <span class="removed"><del><strong>does not mean
it</strong></del></span> is <span class="removed"><del><strong>OK. There are
+other bad things</strong></del></span> a <span
class="inserted"><ins><em>matter of
+risk, not SaaSS. On the other hand, using the</em></ins></span> service <span
class="removed"><del><strong>can do. For instance, Facebook distributes
+video</strong></del></span> <span class="inserted"><ins><em>for converting
+document formats <em>is</em> SaaSS, because it's something you
could
+have done by running a suitable program (free, one hopes)</em></ins></span> in
<span class="removed"><del><strong>Flash,</strong></del></span> <span
class="inserted"><ins><em>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,</em></ins></span>
which <span class="removed"><del><strong>pressures users to
run</strong></del></span> <span class="inserted"><ins><em>is
+bad like any</em></ins></span> nonfree <span
class="removed"><del><strong>software,</strong></del></span> <span
class="inserted"><ins><em>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</em></ins></span>
+and <span class="inserted"><ins><em>proprietary software do similar wrong to
the user,</em></ins></span> it
+<span class="removed"><del><strong>gives users a misleading impression of
privacy. Those are important
+issues too,</strong></del></span> <span class="inserted"><ins><em>is not
+crucial to know.</p>
+
+<p>Publishing via someone else's repository does not raise privacy
+issues,</em></ins></span> but <span class="removed"><del><strong>this
article's concern</strong></del></span> <span
class="inserted"><ins><em>publishing through Google Docs has a special problem:
it</em></ins></span>
+is <span class="inserted"><ins><em>impossible even to
<em>view</em></ins></span> the <span
class="removed"><del><strong>issue</strong></del></span> <span
class="inserted"><ins><em>text</em></em></ins></span> of <span
class="removed"><del><strong>SaaS.</p></strong></del></span> <span
class="inserted"><ins><em>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></em></ins></span>
+
+<p>The IT industry discourages users from <span
class="removed"><del><strong>considering</strong></del></span> <span
class="inserted"><ins><em>making</em></ins></span> 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 <span class="removed"><del><strong>SaaS and it includes
nearly
+everything else.</strong></del></span> <span class="inserted"><ins><em>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.</em></ins></span> The term <span
class="removed"><del><strong>only lends itself</strong></del></span> <span
class="inserted"><ins><em>leads people</em></ins></span> to <span
class="removed"><del><strong>uselessly broad
+statements.</p>
+
+<p>The real meaning of</strong></del></span>
+<span class="inserted"><ins><em>generalize about practices they ought to
consider individually.</p>
+
+<p>If</em></ins></span> “cloud computing” <span
class="inserted"><ins><em>has a meaning, it</em></ins></span> is <span
class="removed"><del><strong>to suggest</strong></del></span> <span
class="inserted"><ins><em>not a way of
+doing computing, but rather a way of thinking about
computing:</em></ins></span> a
+devil-may-care approach <span class="removed"><del><strong>towards your
computing. It</strong></del></span> <span
class="inserted"><ins><em>which</em></ins></span> says, “Don't ask <span
class="removed"><del><strong>questions, just trust every business without
hesitation.</strong></del></span> <span
class="inserted"><ins><em>questions.</em></ins></span> 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
+<span class="removed"><del><strong>it.”</strong></del></span> <span
class="inserted"><ins><em>it.
+Trust companies without hesitation.”</em></ins></span> In other words,
<span class="removed"><del><strong>“Think like</strong></del></span>
<span class="inserted"><ins><em>“Be</em></ins></span> a
+sucker.” <span class="removed"><del><strong>I
prefer</strong></del></span> <span class="inserted"><ins><em>A cloud in the
mind is an obstacle</em></ins></span> to <span class="inserted"><ins><em>clear
thinking.
+For the sake of clear thinking about computing, let's</em></ins></span> avoid
the <span class="removed"><del><strong>term.</p></strong></del></span>
<span class="inserted"><ins><em>term
+“cloud.”</p></em></ins></span>
+
+<h3>Dealing with the <span
class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> Problem</h3>
+
+<p>Only a small fraction of all web sites do <span
class="removed"><del><strong>SaaS;</strong></del></span> <span
class="inserted"><ins><em>SaaSS;</em></ins></span> 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 <span
class="removed"><del><strong>GIMP.</p>
+
+<p>But what</strong></del></span> <span class="inserted"><ins><em>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</em></ins></span> about collaborating with other <span
class="removed"><del><strong>individuals?</strong></del></span> <span
class="inserted"><ins><em>individuals as a group?</em></ins></span> It may
+be hard to do this at present without using a <span
class="inserted"><ins><em>server, and your group
+may not know how to run its own</em></ins></span> server. If you use <span
class="removed"><del><strong>one,</strong></del></span> <span
class="inserted"><ins><em>someone else's
+server, at least</em></ins></span> 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. <span
class="removed"><del><strong>Police</strong></del></span> <span
class="inserted"><ins><em>The state</em></ins></span> can subpoena
+your data from the company <span
class="inserted"><ins><em>along</em></ins></span> with
+<span class="removed"><del><strong>less basis than
required</strong></del></span> <span class="inserted"><ins><em>everyone else's,
as Obama has
+done</em></ins></span> to <span class="removed"><del><strong>subpoena them
from you,</strong></del></span> <span class="inserted"><ins><em>phone
companies,</em></ins></span> 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 <span
class="removed"><del><strong>SaaS.</strong></del></span> <span
class="inserted"><ins><em>SaaSS.</em></ins></span> 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 <span
class="removed"><del><strong>work</strong></del></span> <span
class="inserted"><ins><em>own computing</em></ins></span> 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>
+<span class="removed"><del><strong></div></strong></del></span>
+
+<span class="inserted"><ins><em></div><!-- for id="content", starts
in the include above --></em></ins></span>
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<span class="removed"><del><strong><p>
+Please</strong></del></span>
+
+<span class="inserted"><ins><em><p>Please</em></ins></span> send <span
class="inserted"><ins><em>general</em></ins></span> 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.
+<span class="removed"><del><strong><br />
+Please send broken</strong></del></span> <span
class="inserted"><ins><em>Broken</em></ins></span> links and other corrections
or suggestions <span class="inserted"><ins><em>can be sent</em></ins></span>
+to <a <span
class="removed"><del><strong>href="mailto:address@hidden"><address@hidden></a>.
+</p>
+
+<p>Please</strong></del></span> <span
class="inserted"><ins><em>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</em></ins></span> see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+
+<span class="inserted"><ins><em><!-- Regarding copyright, in general,
standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 3.0 US. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. --></em></ins></span>
+
+<p>Copyright © <span
class="removed"><del><strong>2010</strong></del></span> <span
class="inserted"><ins><em>2010, 2013</em></ins></span> Richard <span
class="removed"><del><strong>Stallman
+<br />
+This</strong></del></span> <span class="inserted"><ins><em>Stallman</p>
+
+<p>This</em></ins></span> page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States <span
class="removed"><del><strong>License</a>.
+</p></strong></del></span> <span
class="inserted"><ins><em>License</a>.</p></em></ins></span>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2013/08/05 16:58:56 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
- www/philosophy who-does-that-server-really-serv...,
GNUN <=