/philosophy/who-does-that-server-really-serve.html-diff

<!--#include virtual="/server/header.html" -->
(追記) <!-- Parent-Version: 1.98 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="essays cultural ns" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> (追記ここまで)
<title>Who Does That Server Really Serve?
- GNU Project - Free Software (削除) Foundation (FSF)</title> (削除ここまで) (追記) Foundation</title> (追記ここまで)
<!--#include virtual="/philosophy/po/who-does-that-server-really-serve.translist" -->
<!--#include virtual="/server/banner.html" -->
(追記) <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.html" -->
<div class="article reduced-width"> (追記ここまで)
<h2>Who (削除) does that server really serve?</h2>
<p>by <strong>Richard Stallman</strong></p>
<p>(First published by <a href="http://bostonreview.net/BR35.2/stallman.php">
Boston Review</a>.)</p>
<p><strong>On (削除ここまで) (追記) Does That Server Really Serve?</h2>
<address class="byline">by Richard Stallman</address>
<div class="introduction">
<p><em>On (追記ここまで) the Internet, proprietary software isn't the only way to
lose your (追記) computing (追記ここまで) freedom. (削除) Software (削除ここまで) (追記) Service (追記ここまで) as a (削除) Service (削除ここまで) (追記) Software Substitute, or SaaSS, (追記ここまで) is
another way to (削除) let (削除ここまで) (追記) give (追記ここまで) someone else (削除) have (削除ここまで) power over your (削除) computing.</strong></p> (削除ここまで) (追記) computing.</em></p>
</div>
<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
running 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. And they talk
about “delivering a program by offering a service to run
it.” 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 (削除ここまで)
(追記) href="https://www.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 (削除ここまで) (追記) gives (追記ここまで) 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 (削除) face a
new threat (削除ここまで)
(追記) offered another tempting way (追記ここまで) to (削除) our (削除ここまで) (追記) cede (追記ここまで) control over our computing: (削除) Software (削除ここまで)
(追記) Service (追記ここまで) as a (削除) Service. (削除ここまで) (追記) Software Substitute (SaaSS). (追記ここまで) For our freedom's sake, we
have to reject that too.</p>
(削除) <h3>How (削除ここまで)
(追記) <h3>What Does Service as a (追記ここまで) Software (追記) Substitute Look Like?</h3>
<p>Service (追記ここまで) as a (削除) Service Takes Away Your Freedom</h3>
<p>Software (削除ここまで) (追記) Software Substitute (SaaSS) means using a service (追記ここまで) as a (削除) Service (SaaS) (削除ここまで)
(追記) substitute for running your copy of a program. Concretely, it (追記ここまで) means
that someone sets up a network server that does certain computing (削除) tasks—running spreadsheets,
word processing, (削除ここまで)
(追記) activities—for instance, modifying a photo, (追記ここまで) translating text into
another language, etc.—then invites users to (削除) do their computing on (削除ここまで) (追記) let (追記ここまで) that (削除) server.
Users (削除ここまで) (追記) server do
<em>their own computing</em> for them. As a user of the server, you
would (追記ここまで) send (削除) their (削除ここまで) (追記) your (追記ここまで) data to the server, which does (削除) their (削除ここまで) (追記) that (追記ここまで) computing
(追記) activity (追記ここまで) on the data thus provided, then sends the results back
(追記) to you (追記ここまで) or (追記) else (追記ここまで) acts (追記) directly on your behalf.</p>
<h3>To Which Activities Is the Issue of SaaSS Applicable?</h3>
<p>The issue of SaaSS-or-not-SaaSS is meaningful for a computing
activity that is <em>your own</em> computing. What does that mean,
precisely? It means that no one else is inherently involved in the
activity. To clarify the meaning of “inherently
involved,” we present a thought experiment in which we focus (追記ここまで) on
(追記) one unspecified imaginary computing activity.</p>
<p>Suppose that all parts of the activity are implemented in free
software and you have copies, and you have whatever data you might
need, as well as computers of whatever speed, functionality and
capacity might be required. Could you (if given those prerequisites)
do this particular computing activity entirely within those computers,
not communicating with anyone else's computers?</p>
<p>If you could, then the activity is <em>essentially your own</em>.
Therefore, for your freedom's sake, you deserve to control it.
The concept of SaaSS is applicable to such activities and not to other
activities.</p>
<p>For such an activity, if you carry it out by running your copies of
free programs, you do control it. That protects the freedom you
deserve. However, doing it via someone else's service would give that
someone else control over part of your computing activity. That
denies you the control you deserve, so we say it is unjust. We call
that scenario SaaSS.</p>
<p>By contrast, if due to the inherent nature of the computing to be
done you couldn't possibly do that activity entirely in your own
computers, then the activity isn't entirely your own, so the issue of
SaaSS is not applicable to that activity. In general, these
activities involve communication with others, so the others must be
included in it. Buying something from a store is a typical example of
an activity that needs to include some other party (the store).</p>
<p>If a certain activity is essentially your own, then maintaining
your full control over it requires that you do it using your copies of
free programs, running (追記ここまで) them
(削除) directly.</p>
<p>These (削除ここまで) (追記) on computers you control. Doing it in any
other way is SaaSS because it denies you the control you deserve.
This is independent of your reasons for doing it in some other way.
If you choose some other way because of some convenience, it is SaaSS.
If it is because you can't obtain the free programs or the computer
you'd need to keep control, that is still SaaSS.</p>
<h3>Using SaaSS Compared with Running Nonfree Software</h3>
<p>SaaSS (追記ここまで) 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
(削除) for programmers (削除ここまで) 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 (削除) SaaS, (削除ここまで) (追記) SaaSS, (追記ここまで) the users do not have even the executable (削除) file: (削除ここまで) (追記) file that
does their computing: (追記ここまで) it is on
(削除) the (削除ここまで) (追記) 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, (削除) SaaS (削除ここまで) (追記) SaaSS (追記ここまで) automatically leads to (削除) harmful (削除ここまで) consequences equivalent
to the malicious features of certain proprietary (削除) software. (削除ここまで) (追記) 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. (削除ここまで) (追記) activities</a>. (追記ここまで)
Microsoft Windows sends information about users' activities to
Microsoft. Windows Media Player (削除) and RealPlayer report (削除ここまで) (追記) reports (追記ここまで) what each user watches or
listens (削除) to.</p> (削除ここまで) (追記) 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, (削除) SaaS (削除ここまで) (追記) SaaSS (追記ここまで) does not require covert code to
obtain the user's data. Instead, (追記) its structure requires (追記ここまで) users (削除) must (削除ここまで) (追記) to (追記ここまで) send
their data to the server in order to use it. This has the same effect
as spyware: the server operator gets the (削除) data. He gets it with (削除ここまで) (追記) data—with (追記ここまで) no special
effort, by the nature of (削除) SaaS.</p> (削除ここまで) (追記) 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="https://slate.com/technology/2013/09/privacy-facebook-kids-dont-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. Also, snooping is only one
among the secondary injustices of SaaSS.</p> (追記ここまで)
<p>Some proprietary (削除) programs can mistreat users under remote command. (削除ここまで) (追記) 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. (削除) The Amazon Kindle e-book
reader (whose name suggests it's intended to burn people's books) has
an Orwellian (削除ここまで) (追記) Nearly all portable
phones have them, too. Some proprietary applications also have
universal (追記ここまで) back (削除) 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 (削除ここまで) (追記) doors; for instance, (追記ここまで) the (削除) users had purchased from Amazon.</p>
<p>SaaS inherently gives (削除ここまで) (追記) Steam client for GNU/Linux
allows the developer to remotely install modified versions.</p>
<p>With SaaSS, (追記ここまで) the server operator (削除) the power to (削除ここまで) (追記) can (追記ここまで) change the software in (削除) use, or (削除ここまで) (追記) use on (追記ここまで)
the (削除) users' data being operated on. Once again, no
special code is needed (削除ここまで) (追記) server. Person ought to be able (追記ここまで) to do (削除) this.</p>
<p>Thus, SaaS (削除ここまで) (追記) this, since it's per 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>It is common for SaaSS dis-services to charge a monthly fee for
use. Usually one SaaSS site does not substitute for another, so if
users become unhappy with one dis-service provider it is no easy
matter to switch to another. When users become dependent on
one, <a href="https://www.theguardian.com/business/2023/nov/05/cloud-service-provider-consumer-prices-netflix-microsoft">it
can gouge them at will with repeated small price increases that over
time add up to a lot</a>. We view the loss of freedom inherent in
SaaSS as worse than the cost in money, but when a dis-service has you
over a barrel, the cost can be painful. Thus, even users who don't
see deeper than the bottom line should beware of SaaSS.</p>
<p>SaaSS (追記ここまで) is equivalent to (削除) total (削除ここまで) (追記) running proprietary software with (追記ここまで)
spyware and a (削除) gaping wide (削除ここまで) (追記) universal (追記ここまで) back
(削除) door, and (削除ここまで) (追記) door. It (追記ここまで) gives the server operator
unjust power over the (削除) user. We
can't accept that.</p>
<h3>Untangling (削除ここまで) (追記) user, and unjust 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>SaaS (削除ここまで)
(追記) <p>SaaSS (追記ここまで) and proprietary software lead to similar harmful results, but
the (削除) causal (削除ここまで) mechanisms are different. With proprietary software, the
(削除) cause (削除ここまで)
(追記) mechanism (追記ここまで) is that you have and use a copy which is difficult (削除) or (削除ここまで) (追記) and/or (追記ここまで)
illegal to change. With (削除) SaaS, (削除ここまで) (追記) SaaSS, (追記ここまで) the (削除) cause (削除ここまで) (追記) mechanism (追記ここまで) is that you (削除) use a copy you (削除ここまで) don't
(削除) have.</p> (削除ここまで) (追記) 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 or (削除ここまで) (追記) nontrivial, (追記ここまで) even large JavaScript
programs (削除) temporarily (削除ここまで) into your browser without informing
you. <a href="/philosophy/javascript-trap.html">When these JavaScript
programs are nonfree</a>, they (削除) are as bad (削除ここまで) (追記) cause the same sort of injustice (追記ここまで) as any
other nonfree software. Here, however, we are concerned with the (削除) problem (削除ここまで)
(追記) issue (追記ここまで) of (追記) using (追記ここまで) the
(削除) server software (削除ここまで) (追記) service (追記ここまで) itself.</p>
<p>Many free software supporters assume that the problem of (削除) SaaS (削除ここまで) (追記) 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 (削除) owners (削除ここまで) (追記) developers/owners (追記ここまで) have power over the
server. That's unfair to the (追記) server (追記ここまで) operator, and doesn't help (削除) you (削除ここまで) (追記) the
server's users (追記ここまで) at all. But if the programs on the server are free,
that doesn't protect (削除) you <em>as the (削除ここまで) (追記) <em>the (追記ここまで) server's (削除) user</em> (削除ここまで) (追記) users</em> (追記ここまで) from the effects of (削除) SaaS. They give freedom to (削除ここまで)
(追記) SaaSS. These programs liberate (追記ここまで) the (追記) server (追記ここまで) operator, but not (削除) to you.</p> (削除ここまで) (追記) the
server's users.</p> (追記ここまで)
<p>Releasing the server software source code does benefit the
community: (追記) it enables (追記ここまで) suitably skilled users (削除) can (削除ここまで) (追記) to (追記ここまで) set up similar
servers, perhaps changing the
software. (削除) But (削除ここまで) (追記) <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.
The rest would (削除ここまで) (追記) 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 (削除) SaaS. SaaS (削除ここまで) (追記) SaaSS for you. SaaSS (追記ここまで)
always subjects you to the power of the server operator, and the only
remedy is, <em>Don't use (削除) SaaS!</em> (削除ここまで) (追記) 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="https://opendefinition.org/ossd/">“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 (削除) SaaS (削除ここまで) (追記) SaaSS (追記ここまで) from Other Network Services</h3>
(削除) <p>Does avoiding SaaS mean (削除ここまで)
(追記) <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 (削除) refuse (削除ここまで)
(追記) 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? Not at all. (削除ここまで) (追記) you. (追記ここまで) Most servers (削除) do (削除ここまで) (追記) are (追記ここまで) not (削除) raise this
issue, (削除ここまで) (追記) SaaSS (追記ここまで) because the (削除) job you (削除ここまで)
(追記) jobs they (追記ここまで) do (追記) are some sort of communication (追記ここまで) with (削除) them isn't your (削除ここまで) (追記) visitors, rather than
each visitor's (追記ここまで) own (削除) computing
except in a trivial sense.</p> (削除ここまで) (追記) computing.</p> (追記ここまで)
<p>The original (削除) purpose (削除ここまで) (追記) idea (追記ここまで) of web servers wasn't to do computing for you, (追記) a
visitor; (追記ここまで) it was to publish information for you to access. Even today
this is what most web sites do, and it doesn't (削除) pose (削除ここまで) (追記) raise (追記ここまで) the (削除) SaaS problem, (削除ここまで) (追記) SaaSS issue, (追記ここまで)
because accessing someone's published information (追記) on a web site (追記ここまで) isn't
a matter of (削除) doing (削除ここまで) your own computing. Neither is (削除) publishing your own materials via (削除ここまで) (追記) use of (追記ここまで) a blog site (追記) to
publish your own works, (追記ここまで) or (追記) using (追記ここまで) a microblogging service such as (削除) Twitter (削除ここまで)
(追記) Mastodon, or StatusNet, or Ex-Twitter. (These services may (追記ここまで) or (削除) identi.ca. (削除ここまで) (追記) may not
have other problems, depending on details.) (追記ここまで) The same goes for (追記) other (追記ここまで)
communication not meant to be private, such as chat
(削除) groups. Social (削除ここまで) (追記) groups.</p>
<p>In its essence, social (追記ここまで) networking (削除) can extend into SaaS; however, at root it (削除ここまで) is (削除) just (削除ここまで) a (削除) method (削除ここまで) (追記) form (追記ここまで) of communication and
publication, not (削除) SaaS. If you
use the (削除ここまで) (追記) SaaSS. However, a service whose main facility is
social networking can have features or extensions which are SaaSS.</p>
<p>If a (追記ここまで) service (削除) for minor editing of what you're going to communicate,
that (削除ここまで) is not (追記) SaaSS, that does not mean it is OK. There are
other ethical issues about services. For instance, Facebook requires
running nonfree JavaScript code, and it gives users (追記ここまで) a (削除) significant (削除ここまで) (追記) misleading
impression of privacy while luring them into baring their lives to
Facebook. Those are important issues, but distinct 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
(削除) SaaS. (However, (削除ここまで)
(追記) SaaSS. However, (追記ここまで) using someone else's (削除) search engine (削除ここまで) (追記) server (追記ここまで) to implement a search
facility for your own site <em>is</em> (削除) SaaS.)</p>
<p>E-commerce (削除ここまで) (追記) SaaSS.</p>
<p>Purchasing online (追記ここまで) is not (削除) SaaS, (削除ここまで) (追記) SaaSS, (追記ここまで) because the computing
isn't (削除) solely yours; (削除ここまで) (追記) <em>your own</em> activity; (追記ここまで) rather, it is done jointly (追記) by and (追記ここまで)
for you and (削除) another party. So there's no
particular reason why you alone should expect to control that
computing. (削除ここまで) (追記) the store. (追記ここまで) The real issue in (削除) e-commerce (削除ここまで) (追記) online shopping (追記ここまで) is whether
you trust the other party with your money and (追記) other (追記ここまで) personal (削除) information.</p>
<p>Using a joint project's servers isn't SaaS because the computing
you do in this way isn't yours personally. For instance, if you edit
pages on Wikipedia, you are not doing (削除ここまで)
(追記) information (starting with (追記ここまで) your (削除) own computing; rather, you
are collaborating in Wikipedia's computing.</p>
<p>Wikipedia controls its own servers, but groups can face the problem
of SaaS if they do their group activities on someone else's server.
Fortunately, development hosting (削除ここまで) (追記) name).</p>
<p>Repository (追記ここまで) 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 someone
else's 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, (削除ここまで) (追記) not
inherently SaaSS, (追記ここまで) 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 (削除ここまで) (追記) repository's job (追記ここまで) 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 (削除ここまで) (追記) publication (追記ここまで) of (削除) your own computing
with it too, that computing is SaaS even if the communication is
not.</p> (削除ここまで) (追記) data
supplied to it.</p> (追記ここまで)
<p>Some sites offer multiple services, and if one is not (削除) SaaS, (削除ここまで) (追記) SaaSS, (追記ここまで)
another may be (削除) SaaS. (削除ここまで) (追記) SaaSS. (追記ここまで) For instance, the main service of Facebook is
social networking, and that is not (削除) SaaS; (削除ここまで) (追記) SaaSS; (追記ここまで) however, it supports
third-party applications, some of which (削除) may be SaaS. (削除ここまで) (追記) are SaaSS. (追記ここまで) Flickr's main
service is distributing photos, which is not (削除) SaaS, (削除ここまで) (追記) SaaSS, (追記ここまで) but it also has
features for editing photos, which is (削除) SaaS.</p>
<p>Some sites whose main service (削除ここまで) (追記) SaaSS. Likewise, using
Instagram to post a photo (追記ここまで) is (削除) publication and communication
extend (削除ここまで) (追記) not SaaSS, but using (追記ここまで) it (削除) with “contact management”: keeping track (削除ここまで) (追記) to transform the
photo is SaaSS.</p>
<p>Google Docs shows how complex the evaluation (追記ここまで) of (追記) a single service
can become. It invites (追記ここまで) people (削除) you have relationships with. Sending mail (削除ここまで) to (削除) those people (削除ここまで) (追記) edit a document by running a
large <a href="/philosophy/javascript-trap.html">nonfree JavaScript
program</a>, clearly unjust, but not SaaSS. However, it offers an API (追記ここまで)
for
(削除) you (削除ここまで) (追記) uploading and downloading documents in standard formats. A free
software editor can do so through this API. (Whether it is possible
to get an account for Google Docs without running some nonfree
JavaScript code, we don't know.) Anyway, this usage scenario (追記ここまで) is not (削除) SaaS, but keeping track of (削除ここまで)
(追記) SaaSS, because it uses Google Docs as a mere repository. Handing (追記ここまで) your (削除) dealings with them, if
substantial, (削除ここまで)
(追記) work data to a company (追記ここまで) is (削除) SaaS.</p>
<p>If (削除ここまで) (追記) bad, but that is a matter of privacy, not
SaaSS; depending on (追記ここまで) a service (追記) for access to your data (追記ここまで) is (削除) not SaaS, (削除ここまで) (追記) bad, but (追記ここまで) that (削除) does not mean it (削除ここまで)
is (削除) OK. There are (削除ここまで) (追記) a matter of risk, not SaaSS.</p>
<p>On the (追記ここまで) other (削除) bad things (削除ここまで) (追記) hand, using Google Docs for converting document
formats <em>is</em> SaaSS, because it's something you could have done
by running (追記ここまで) a (削除) service can do. For instance, Facebook distributes
video (削除ここまで) (追記) suitable program (free, one hopes) (追記ここまで) in (削除) Flash, which pressures users to run (削除ここまで) (追記) your own
computer.</p>
<p>Using Google Docs through a free editor is rare, of course. Most
often, people edit their Google Docs documents with the (追記ここまで) nonfree (削除) software, and (削除ここまで)
(追記) JavaScript program (追記ここまで) it
(削除) gives users a misleading impression (削除ここまで) (追記) sends, which is bad like any nonfree program.
This scenario might involve SaaSS, too; that depends on what part (追記ここまで) of (削除) privacy. Those are important
issues too, (削除ここまで)
(追記) the editing is done in the JavaScript program and what part in the
server. We don't know, (追記ここまで) but (削除) this article's concern (削除ここまで) (追記) since SaaSS and proprietary software do
similar wrong to the user, we can judge the whole scenario morally
without knowing which part is which.</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 (削除) issue (削除ここまで) (追記) text</em> (追記ここまで) of (削除) SaaS.</p> (削除ここまで) (追記) 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 (削除) considering (削除ここまで) (追記) 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 (削除) SaaS and it includes nearly
everything else. (削除ここまで) (追記) 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 (削除) only lends itself (削除ここまで) (追記) leads people (追記ここまで) to (削除) uselessly broad
statements.</p>
<p>The real meaning of (削除ここまで)
(追記) generalize about practices they ought to judge separately.</p>
<p>If (追記ここまで) “cloud computing” (追記) has a meaning, it (追記ここまで) is (削除) to suggest (削除ここまで) (追記) not a way of
doing computing, but rather a way of thinking about computing: (追記ここまで) a
devil-may-care approach (削除) towards your computing. It (削除ここまで) (追記) which (追記ここまで) says, “Don't ask (削除) questions, just trust every business without hesitation. (削除ここまで) (追記) 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.” (削除ここまで) (追記) it.
Trust companies without hesitation.” (追記ここまで) In other words, (削除) “Think like (削除ここまで) (追記) “Be (追記ここまで) a
sucker.” (削除) I prefer (削除ここまで) (追記) A cloud in the mind is an obstacle (追記ここまで) to (追記) clear thinking.
For the sake of clear thinking about computing, let's (追記ここまで) avoid the (削除) term.</p> (削除ここまで) (追記) term
“cloud.”</p>
<div class="announcement comment" role="complementary">
<p>In 2008, Stallman warned that <a 
href="https://web.archive.org/web/20130825032356/https://www.theguardian.com/technology/2008/sep/29/cloud.computing.richard.stallman">“cloud computing” is a trap</a>.
After that, he further developed his <a 
href="/philosophy/words-to-avoid.html#CloudComputing">analysis of the term</a>.</p>
</div>
<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>
<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>
<h3>When the User Is a Collective Activity Or an Organization</h3>
<p>So far we have explained how SaaSS applies to an individual's
computing. For those cases, we have clarified the concept of SaaSS
pretty thoroughly. SaaSS is also an issue for computing done by a
group activity, which may be informal (such as developing a free
program often is), or formal (a charity like the FSF or a business).
It is basically the same concept, but we have not clarified the
boundaries for all sorts of situations.</p>
<p>Here are some lines we have drawn so far.</p>
<p>The collective activity is likely to have web pages, which will be
hosted on some web server. That server's treatment of visitors to its
pages raises the usual moral issues: if they send nonfree JavaScript
code, that is an injustice, and if they offer to do the visitor's
computing, that is SaaSS.</p>
<p>However, the web server's own operations can also raise the issue
of SaaSS with the collective activity as victim. A web server often
offers visitors a way to search through the web pages; how does it
implement that? If the collective activity runs a free program on its
own computer to find the matches for the search string, the collective
activity has control of this, as it should. But if it asks Google (or
any other search engine) where the matches are and displays what is
found, the collective activity is relying on SaaSS and forfeiting its
freedom.</p>
<p>Using a joint project's servers to work on that project isn't SaaSS
because the computing you do in this way isn't your own—it is
the project's computing. 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>Use of simple software repositories is not SaaSS because most of
the actual work (as distinguished from redistribution) is done in the
contributors' computers. However, when the repository starts doing
other kinds of computing work for the users, such as running tests,
that starts to cross the line. When the users are contributing to the
project, so the work is the project's work rather than the
contributor's work, that still is not SaaSS for the users. But it may
be SaaSS for the project. However, if the testing means running the
programs that the project develops, it is not SaaSS because the
project does control the crucial software being run.</p> (追記ここまで)
<h3>Dealing with the (削除) SaaS (削除ここまで) (追記) SaaSS (追記ここまで) Problem</h3>
<p>Only a small fraction of all web sites do (削除) SaaS; (削除ここまで) (追記) 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.</p>
<p>But what (削除ここまで) (追記) 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? (削除ここまで) (追記) 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 (削除) one, (削除ここまで) (追記) 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. (削除) Police (削除ここまで) (追記) The state (追記ここまで) can subpoena
your data from the company (追記) along (追記ここまで) with
(削除) less basis than required (削除ここまで) (追記) everyone else's, as Obama has
done (追記ここまで) to (削除) subpoena them from you, (削除ここまで) (追記) 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”. (削除ここまで) (追記) 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 (削除) SaaS. (削除ここまで) (追記) SaaSS. (追記ここまで) Don't buy or
install “thin (削除) clients”, (削除ここまで) (追記) 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 (削除) work (削除ここまで) (追記) own computing (追記ここまで) with your own copy of a free
program, for your freedom's sake.</p>
(削除) <h3>See also:</h3>
<p><a (削除ここまで)
(追記) <div class="announcement comment" role="complementary">
<p>See also:
<a (追記ここまで) href="/philosophy/bug-nobody-allowed-to-understand.html">The
Bug Nobody is Allowed to Understand</a>.</p>
</div>
(追記) <div class="infobox extra" role="complementary">
<hr />
<p>The first version of this article was published
in the <cite><a
href="https://www.bostonreview.net/articles/what-does-that-server-really-serve/">
Boston Review</a></cite>.</p>
</div>
</div>
</div><!-- for id="content", starts in the include above --> (追記ここまで)
<!--#include virtual="/server/footer.html" -->
<div (削除) id="footer">
<p>
Please (削除ここまで) (追記) id="footer" role="contentinfo">
<div class="unprintable">
<p>Please (追記ここまで) send (追記) general (追記ここまで) FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.
(削除) <br />
Please send broken (削除ここまで) (追記) Broken (追記ここまで) links and other corrections or suggestions (追記) can be sent (追記ここまで)
to <a (削除) href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.
</p>
<p>Please (削除ここまで) (追記) href="mailto:webmasters@gnu.org"><webmasters@gnu.org></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:web-translators@gnu.org">
 <web-translators@gnu.org></a>.</p>
 <p>For information on coordinating and contributing 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 (削除ここまで) (追記) contributing (追記ここまで) 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 (削除ここまで) (追記) 2010, 2013, 2015, 2016, 2018, 2020, 2021, 2023, 2024, 2026 (追記ここまで) Richard (削除) Stallman
<br />
This (削除ここまで) (追記) Stallman</p>
<p>This (追記ここまで) page is licensed under a <a rel="license"
(削除) href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative (削除ここまで)
(追記) href="http://creativecommons.org/licenses/by-nd/4.0/">Creative (追記ここまで)
Commons (削除) Attribution-NoDerivs 3.0 United States License</a>.
</p> (削除ここまで) (追記) Attribution-NoDerivatives 4.0 International License</a>.</p> (追記ここまで)
<!--#include virtual="/server/bottom-notes.html" -->
(削除) <p>Updated: (削除ここまで)
(追記) <p class="unprintable">Updated: (追記ここまで)
<!-- timestamp start -->
$Date: 2026年06月19日 07:31:41 $
<!-- timestamp end -->
</p>
</div>
(削除) </div> (削除ここまで)
(追記) </div><!-- for class="inner", starts in the banner include --> (追記ここまで)
</body>
</html>