What Does That Server Really Serve?
March 18, 2010
Mar 18, 2010
10 Min read time
How programs like Google Docs rob users of their freedom
Digital technology can give you freedom; it can also take your freedom away. The first threat to our control over our computing came from proprietary software: software that the users cannot control because the owner (a company such as Apple or Microsoft) controls it. The owners often take advantage of this unjust power by inserting malicious features such as spyware, back doors, and Digital Restrictions Management (DRM) (referred to as “Digital Rights Management” in their propaganda).
Our solution to this problem is developing free software 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.
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: Software as a Service. For our freedom’s sake, we have to reject that too.
How Software as a Service Takes Away Your Freedom
Software as a Service (SaaS) means that someone sets up a network server that does certain computing tasks—running spreadsheets, word processing, translating text into another language, etc.—and then invites users to do their computing on that server. Users must send their data to the server, which returns the results.
These servers wrest control from the users even more inexorably than does 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.
With SaaS, the users do not have even the executable file: it is on the 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.
Furthermore, SaaS automatically leads to harmful consequences equivalent to the malicious features of certain proprietary software. For instance, some proprietary programs are “spyware”: the program sends data about users’ computing activities to the program’s owner. Microsoft Windows sends information about users’ activities to Microsoft. Windows Media Player and RealPlayer report what users watch or listen to.
SaaS gives the same results as spyware because it requires users to send their data to the server. The server operator gets all the data with no special effort, by the nature of SaaS.
Some proprietary programs can mistreat users under remote command. For instance, Windows has a back door with which Microsoft can forcibly change any software on the machine. The Amazon Kindle e-book reader (whose name suggests it is intended to burn people’s books) has an Orwellian back door that Amazon used in 2009 to delete remotely many Kindle copies of Orwell’s 1984 and Animal Farm, which people had purchased from Amazon.
SaaS inherently gives the server operator the power to change the software in use, or the users’ data being operated on. Once again, no special code is needed to do this.
Thus, SaaS is equivalent to total spyware and a gaping wide back door, and it gives the server operator unjust power over the user. We can’t accept that.
Untangling the SaaS Issue from the Proprietary Software Issue
SaaS and proprietary software lead to similar harmful results, but the causal mechanisms are different. With proprietary software, the cause is that you have and use a copy which is difficult or illegal to change. With SaaS, the cause is that you use a copy you don’t have.
Many free-software supporters assume that the problem of SaaS 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 it doesn’t help you at all. But if the programs on the server are free, they still don’t protect you as the server’s user from the effects of SaaS. They give freedom to the operator, but not to you.
Releasing the server-software source code does benefit the community: suitably skilled users can set up similar servers, perhaps changing the software. But none of these servers would give you control over computing that you do on it, unless it’s your server. The rest would all be SaaS. SaaS always subjects you to the power of the server operator, and the only remedy is: don’t use SaaS! Don’t use someone else’s server to do your own computing on your data.
Distinguishing SaaS from Other Network Services
Does condemning SaaS mean rejecting all network servers? Not at all. Most servers do not raise this issue, because the job you do with them isn’t your own computing except in a trivial sense.
The original purpose 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 they don’t pose the SaaS problem, because accessing someone’s published information isn’t a matter of doing your own computing. Neither is publishing your own materials via a blog site or a micro-blogging service such as Twitter. The same goes for communication not meant to be private, such as chat groups. Social networking can extend into SaaS; however, at root it is just a method of communication and publication, not SaaS. If you use the service for minor editing of what you’re going to communicate, that is not a significant issue.
Software as a service always subjects you to the power of the server operator, and the only remedy is to avoid it.
Services such as search engines collect data and let you examine it. Looking through their data isn’t your own computing in the usual sense, so these services are not SaaS.
E-commerce is not SaaS, because the computing isn’t solely yours; rather, it is done jointly for you and another party. So there’s no particular reason why you alone should expect to control that computing. The real issue in E-commerce is whether you trust the other party with your money and personal information.
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 your own computing; rather, you are collaborating in Wikipedia’s computing.
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 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.
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.
Some sites offer multiple services, and if one is not SaaS, another may be. For instance, the main service of Facebook is social networking, and that is not SaaS; however, it supports third-party applications, some of which may be SaaS. Flickr’s main service is distributing photos, which is not SaaS, but it also has features for editing photos, which is SaaS.
Some sites whose main service is publication and communication extend it with “contact management”: keeping track of people you have relationships with. Sending mail to those people for you is not SaaS, but keeping track of your dealings with them, if substantial, is SaaS.
If a service is not SaaS, that does not mean it is ok. There are other bad things a service can do. For instance, Facebook distributes video in Flash, which pressures users to run non-free software, and it gives users a misleading impression of privacy. Those are important issues too, but this article’s concern is SaaS.
The information technology industry discourages users from considering 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. The term only lends itself to uselessly broad statements.
The real meaning of “cloud computing” is to suggest a devil-may-care approach towards your computing. It says, “Don’t ask questions, just trust every business without hesitation. 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.” In other words, “Think like a sucker.” I prefer to avoid the term.
Dealing with the SaaS Problem
Only a small fraction of all web sites do SaaS; most don’t raise the issue. But what should we do about the others?
For the simple case, where you are doing your own computing on your own data, 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.
But what about collaborating with other individuals? It may be hard to do this at present without using a server. If you use one, 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 can subpoena your data from the company with less basis than required to subpoena them from you, supposing the company doesn’t volunteer them à la the U.S. phone companies that illegally wiretapped their customers for President Bush. If you must use a server, use a server whose operators give you a basis for trust beyond a mere commercial relationship.
However, on a longer time scale, we can create alternatives to using servers. For instance, we can create a distributed program through which collaborators can share data encrypted. The free-software community should develop distributed peer-to-peer replacements for important “web applications.” The GNU project is looking for volunteers to work on such replacements. We also invite other free-software projects to consider this issue in their design.
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. Don’t buy or install “thin clients,” which are simply computers so weak they make you do the real work on someone else’s server. Use a real computer and keep your data there. Do your work with your own copy of a free program, for your freedom’s sake.
Copyright 2010 Richard M. Stallman. You can copy and redistribute this article under the Creative Commons Attribution Noderivs 3.0 license.
While we have you...
...we need your help. You might have noticed the absence of paywalls at Boston Review. We are committed to staying free for all our readers. Now we are going one step further to become completely ad-free. This means you will always be able to read us without roadblocks or barriers to entry. It also means that we count on you, our readers, for support. If you like what you read here, help us keep it free for everyone by making a donation. No amount is too small. You will be helping us cultivate a public sphere that honors pluralism of thought for a diverse and discerning public.
March 18, 2010
10 Min read time