Domain: gnu.org
Stories and comments across the archive that link to gnu.org.
Stories · 596
-
Microsoft Open Technologies Is Closing: Good Or Bad News For Open Source?
BrianFagioli writes When Microsoft Open Technologies was founded as a subsidiary of Microsoft — under Steve Ballmer's reign — many in the open source community hailed it as a major win, and it was. Today, however, the subsidiary is shutting down and being folded into Microsoft. While some will view this as a loss for open source, I disagree; Microsoft has evolved so much under Satya Nadella, that a separate subsidiary is simply no longer needed. Microsoft could easily be the world's biggest vendor of open source software, which is probably one reason some people don't like the term. -
GCC 5.0 To Support OpenMP 4.0, Intel Cilk Plus, C++14
An anonymous reader writes: GCC 5 is coming up for release in the next few weeks and is presenting an extraordinary number of new features: C11 support by default, experimental C++14 support, full C++11 support in libstdc++, OpenMP 4.0 with Xeon Phi / GPU offloading, Intel Cilk Plus multi-threading, new ARM processor support, Intel AVX-512 handling, and much more. This is a big release, so those wishing to test it ahead of time can obtain the preliminary GCC 5 source code from GCC's snapshots mirror. -
GNU Nano Gets New Stable Release
jones_supa writes: GNU Nano 2.4.0 has been released as the first stable update to this UNIX command line text editor in a number of years. The release codenamed "Lizf" brings a wide variety of changes: full undo system, Vim-compatible file locking, linter support, formatter support, flexible syntax highlighting, and random bugfixes. -
The GNU Manifesto Turns Thirty
An anonymous reader writes: It was March, 1985 when Richard M. Stallman published the GNU Manifesto in Dr. Dobb's Journal of Software Tools. Thirty years on, The New Yorker has an article commemorating its creation and looking at how it has shaped software in the meantime. "Though proprietary and open-source software publishers might appear at the moment to have the upper hand, Stallman's influence with developers (among whom he is known simply by his initials, 'rms') remains immense. When I asked around about him, many people spoke of him as one might of a beloved but eccentric and prickly uncle. They would roll their eyes a bit, then hasten to add, as more than one did, 'But he's right about most things.' I told Stallman that I'd spoken with several developers who venerate his work, and who had even said that without it the course of their lives might have been altered. But they don't seem to do what you say, I observed; they all have iPhones. 'I don't understand that either,' he said. 'If they don't realize that they need to defend their freedom, soon they won't have any.'" -
RMS Objects To Support For LLVM's Debugger In GNU Emacs's Gud.el
An anonymous reader writes with the news that Richard Stallman is upset over the prospect of GNU Emacs's Grand Unified Debugger (Gud.el) supporting LLVM's LLDB debugger. Stallman says it looks like there is a systematic effort to attack GNU packages and calls for the GNU Project to respond strategically. He wrote his concerns to the mailing list after a patch emerged that would optionally support LLDB alongside GDB as an alternative debugger for Emacs. Other Emacs developers discounted RMS' claims by saying Emacs supports Windows and OS X, so why not support a BSD-licensed compiler/debugger? The Emacs maintainer has called the statements irrelevant and won't affect their decision to merge the LLDB support. -
RMS Objects To Support For LLVM's Debugger In GNU Emacs's Gud.el
An anonymous reader writes with the news that Richard Stallman is upset over the prospect of GNU Emacs's Grand Unified Debugger (Gud.el) supporting LLVM's LLDB debugger. Stallman says it looks like there is a systematic effort to attack GNU packages and calls for the GNU Project to respond strategically. He wrote his concerns to the mailing list after a patch emerged that would optionally support LLDB alongside GDB as an alternative debugger for Emacs. Other Emacs developers discounted RMS' claims by saying Emacs supports Windows and OS X, so why not support a BSD-licensed compiler/debugger? The Emacs maintainer has called the statements irrelevant and won't affect their decision to merge the LLDB support. -
Kawa 2.0 Supports Scheme R7RS
First time accepted submitter Per Bothner (19354) writes "Kawa is a general-purpose Scheme-based programming language that runs on the Java platform. It combines the strengths of dynamic scripting languages (less boiler-plate, fast and easy start-up, a REPL, no required compilation step) with the strengths of traditional compiled languages (fast execution, static error detection, modularity, zero-overhead Java platform integration).
Version 2.0 was just released with many new features. Most notably is (almost) complete support for the latest Scheme specification, R7RS, which was ratified in late 2013. This LWN article contains a brief introduction to Kawa and why it is worth a look." -
Kawa 2.0 Supports Scheme R7RS
First time accepted submitter Per Bothner (19354) writes "Kawa is a general-purpose Scheme-based programming language that runs on the Java platform. It combines the strengths of dynamic scripting languages (less boiler-plate, fast and easy start-up, a REPL, no required compilation step) with the strengths of traditional compiled languages (fast execution, static error detection, modularity, zero-overhead Java platform integration).
Version 2.0 was just released with many new features. Most notably is (almost) complete support for the latest Scheme specification, R7RS, which was ratified in late 2013. This LWN article contains a brief introduction to Kawa and why it is worth a look." -
Trisquel 7 Released
An anonymous reader writes: Trisquel 7.0 Belenos has been released. Trisquel is a "free as in freedom" GNU/Linux distribution endorsed by the FSF. This latest release includes Linux-libre 3.13, GNOME 3.12, Abrowser 33 (based on Firefox), the Electrum Bitcoin client and many more new features and upgrades. Trisquel 7.0 will be supported until 2019.
Interested users can check out the screenshots and download the latest release. The project also accepts donations. -
GNU Emacs 24.4 Released Today
New submitter Shade writes Well over one and a half years in the works, the latest and greatest release of GNU Emacs was made officially available today. Highlights of this release include a built-in web browser, improved multi-monitor and fullscreen support, "electric" indentation enabled by default, support for saving and restoring the state of frames and windows, pixel-based resizing for frames and windows, support for digitally signed ELisp packages, support for menus in text terminals, and much more. Read the official announcement and the full list of changes for more information. -
GNU Emacs 24.4 Released Today
New submitter Shade writes Well over one and a half years in the works, the latest and greatest release of GNU Emacs was made officially available today. Highlights of this release include a built-in web browser, improved multi-monitor and fullscreen support, "electric" indentation enabled by default, support for saving and restoring the state of frames and windows, pixel-based resizing for frames and windows, support for digitally signed ELisp packages, support for menus in text terminals, and much more. Read the official announcement and the full list of changes for more information. -
Stallman Does Slides -- and Brevity -- For TEDx
New submitter ciaran2014 writes Richard Stallman's long-format talks are well-known — there are videos going back to 2001 and transcripts dating back to 1986 — but he recently condensed his free software talk down to 14 minutes and set it to hand-drawn slides for TEDxGeneva (video link). He introduces with the four freedoms, as always, and then moves on to spyware, surveillance, non-free drivers, free software in schools, non-free javascript, Service as a Software Substitute and how free software is today necessary for a strong democracy. As usual, the talk is suitable for non-technical audiences. -
Stallman Does Slides -- and Brevity -- For TEDx
New submitter ciaran2014 writes Richard Stallman's long-format talks are well-known — there are videos going back to 2001 and transcripts dating back to 1986 — but he recently condensed his free software talk down to 14 minutes and set it to hand-drawn slides for TEDxGeneva (video link). He introduces with the four freedoms, as always, and then moves on to spyware, surveillance, non-free drivers, free software in schools, non-free javascript, Service as a Software Substitute and how free software is today necessary for a strong democracy. As usual, the talk is suitable for non-technical audiences. -
Stallman Does Slides -- and Brevity -- For TEDx
New submitter ciaran2014 writes Richard Stallman's long-format talks are well-known — there are videos going back to 2001 and transcripts dating back to 1986 — but he recently condensed his free software talk down to 14 minutes and set it to hand-drawn slides for TEDxGeneva (video link). He introduces with the four freedoms, as always, and then moves on to spyware, surveillance, non-free drivers, free software in schools, non-free javascript, Service as a Software Substitute and how free software is today necessary for a strong democracy. As usual, the talk is suitable for non-technical audiences. -
Stallman Does Slides -- and Brevity -- For TEDx
New submitter ciaran2014 writes Richard Stallman's long-format talks are well-known — there are videos going back to 2001 and transcripts dating back to 1986 — but he recently condensed his free software talk down to 14 minutes and set it to hand-drawn slides for TEDxGeneva (video link). He introduces with the four freedoms, as always, and then moves on to spyware, surveillance, non-free drivers, free software in schools, non-free javascript, Service as a Software Substitute and how free software is today necessary for a strong democracy. As usual, the talk is suitable for non-technical audiences. -
Stallman Does Slides -- and Brevity -- For TEDx
New submitter ciaran2014 writes Richard Stallman's long-format talks are well-known — there are videos going back to 2001 and transcripts dating back to 1986 — but he recently condensed his free software talk down to 14 minutes and set it to hand-drawn slides for TEDxGeneva (video link). He introduces with the four freedoms, as always, and then moves on to spyware, surveillance, non-free drivers, free software in schools, non-free javascript, Service as a Software Substitute and how free software is today necessary for a strong democracy. As usual, the talk is suitable for non-technical audiences. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
Richard Stallman Answers Your Questions
samzenpus (5) writes "A while ago you had the chance to ask GNU and Free Software Foundation founder Richard Stallman about GNU, copyright laws, digital restrictions management, and software patents. Below you'll find his answers to those questions." RMS: By way of explanation, I launched the free software movement; what I say about software issues is based on our values of freedom and community for the users of computers. We classify programs as either "free" or "nonfree".
A few of the questions asked about "open source software" in such a way that, responding to them directly, I'd be classifying programs as "open" or "closed". That I will not do, because those terms presuppose a different philosophy based on different values.
Rather than give no answer to those questions, I modified them to say "free software" instead, and answered them that way. (Square brackets show these changes.) I hope the answers to these modified questions are of interest to readers. They are rather different from what an open source supporter would say.
NSA/GCHQ
by click2005
What are your views on the recent NSA activities and how do you think it will change free software & the internet?
RMS: Nonfree software is likely to spy on its users, or mistreat them in other ways. It is software for suckers.
Awareness of this is spreading, which helps us make the case for free software to people who are not computing experts.
As for the internet, it has been turned into a spy network. A considerable fraction of the massive surveillance (but not all!) applies to the internet. Most use of the internet involves web sites that snoop on users, which is poisonous. That's in addition to the snooping by ISPs themselves.
Massive surveillance of people in general endangers human rights and democracy; but we should remember that US snooping agencies do this mostly by piggy-backing on businesses that massively collect data about people.
Therefore, it is not enough to legally limit the government's access to the digital dossiers about us. We must prevent those dossiers from being made, either by business or by government. We must legally require digital systems to be redesigned so that they do not accumulate data about people in general.
Here is my full position on massive general surveillance.
Opinion?
by Anonymous Coward
What is your opinion on cryptocurrencies?
RMS: In general, I am in favor of ways to pay each other cash on the Internet without going through a payment company that keeps track of all payments. I would like to be able to pay an on-line service with cash the way I pay cash for all the things I buy today.
However, Bitcoin payments are not anonymous. To serve this need requires anonymity at least for the payer. People are working on trying to improve Bitcoin in that way.
I am not an expert on encryption, and I can't judge the security of any particular cryptocurrency. What I do know, and what is illustrated by the recent collapse of several exchanges (banks, in effect) due to robbery, including MtGox, demonstrates that, here as in any field, the security of a practical activity that uses encryption is a very different question from the mathematical validity of the encryption system or the correctness of the software. It may take years to develop cryptomoney exchanges we can have confidence in.
These currencies raise economic issues, too; but not necessarily the way many people think. The number of bitcoins is capped, but new cryptocurrencies can always be created, so that the total number of Xcoins for all values of X has no particular limit. Does this mean that the value of all cryptocurrencies will inevitably tend towards zero? Not necessarily; that depends on how much people accept various other cryptocurrencies -- a sociological question, not an economic one.
I don't enjoy risk, so I will not do speculation in cryptocurrencies any more than I do in other commodities. I may use them for payment if and when it becomes possible to use them anonymously to buy something that I can't get with cash. To resist surveillance, I do buy goods with cash in a store, so that no data base knows what I bought -- therefore, I don't pay over the internet. But I would use an anonymous cryptocurrency to pay for services and downloads.
Cell phones
by Anonymous Coward
I read a little on your website about your take on technology that uses non-free software. Do you still not own a cell phone?
RMS: I certainly do not! A cell phone is Stalin's dream: its movements are tracked, and it can be converted (through the universal back door) into a listening device.
AC: If not, I'd love to hear your perspective on life without one these days, where its just assumed that people own one.
RMS: Please help teach everyone that this assumption is false!
There is a way to make a cell phone acceptable _for occasional communication only_: put a one-way pager in the phone, so people can page you if they are trying to reach you. That way, you can keep its radio connection off most of the time. When you get the page, you can decide when and where to reveal your location by connecting the phone to the network.
Of course, the software in the phone's main computer should also be free, but that is a separate issue. In other words, nonfree software in that computer is one assault on your freedom, and the phone system's location tracking is another.
The software in the baseband (phone radio modem) processor can't be free, at least not as things stand now. So the phone needs to be designed so the baseband processor can't talk to anything (peripherals, antenna, etc) unless the main processor permits it, and so that the baseband processor can't change the software in the main processor. Ideally the software in the baseband processor should be immutable, so we can treat it as a circuit.
AC: As a follow-up, where exactly do you draw the line concerning [freeness of software] and whether or not you use software. For example, do you toast bread in a toaster that runs proprietary code? Obviously we're talking about different things here, but I'm curious to know at what point you say "no thanks!" when it comes to locked down technology.
RMS: The case of the toaster is very clear: we can't tell, except by taking it apart, whether it has a processor and software or a special-purpose chip. Since that we can't tell the difference, it makes no difference: therefore, a program that will never be changed is equivalent to a circuit. I don't care whether a toaster or microwave oven contains software.
A very common design approach nowadays is an appliance or peripheral that contains software that could be changed, but normal use does not include changing it. I think we can still disregard that software, as regards the ethical issue of free vs nonfree software; it is just a short way into thr gray area. However, such devices can be a terrible security threat, because a corrupted computer can install malware in them that will propagate. Devices which have this problem include USB sticks, microSD cards, disk drives, and the cameras that go in computers.
Where is the other side of the line? If the device has an "update firmware" button, that firmware is software meant to be changed, so it is unacceptable.
GTK future?
by Anonymous Coward
Dear RMS, I for one am very interested in what your view is concerning the future of GNOME and specifically GTK. In the past there were concerns over licensing between GTK and Qt and there seems to be a rise in uptake of Qt. My question is whether you see there being a future in GTK and should developers consider moving their projects to Qt?
RMS: I can't see the future, because nobody can. I hope that GNOME and GTK will be very successful. Please help make it so.
GNU/Hurd
by mrflash818
Please share your vision for where you would like to see GNU/Hurd, and GNU software over the next 25 years, and what people would be doing with it.
RMS: I regret to say I have no response. I never try to think about what computing might be like 25 years from now; it would be a waste of time, since I know that I don't know.
I can tell you something about free software 5 years from now: most of it will be the same as today. Free software does not change rapidly. (I think that is a feature; our society teaches people to overvalue innovation so as to distract them from more important things such as freedom, democracy, and giving everyone a comfortable life). Most of the GNU/Linux system in 5 years will be the same as what we have now; some components will be new, but they will be a small change compared with the system as a whole.
The GNU Hurd kernel (and the GNU/Hurd system, which is GNU/Linux with the Hurd instead of Linux) is not a high priority for us any more, because it would be a replacement for the free parts of Linux, and we don't need to replace those. Volunteers continue to work on the Hurd, because it is an interesting technical project.
The parts of Linux we need to replace are the nonfree parts, the "binary blobs". But replacing those has nothing to do with the GNU Hurd. The main work necessary to replace the blobs is reverse engineering to determine the specs of the peripherals those blobs are used in.
That's a tremendously important job -- please join in if you can.
Free hardware? Why not?
by jkrise
In my experience; it is far easier to obtain; install and work with Free Software than with Free Hardware. I asked you about this in person 2 years back; but you brushed it aside saying hardware is not trivial to copy. Recent events have proved me right; I feel. We simply do not have access to Freedom Hardware at low cost - even the Raspberry Pi has proprietary components in its hardware.
RMS: When you say "free hardware" I think you mean hardware whose specs are known, so we can develop free software to run it. I call that "documented hardware". When I say "free hardware", it means to transpose the concept of free software to hardware. This means People are free to copy and change the hardware; if it is made from a design, that design must be free, with the same four freedoms that define free software. But that is mostly an issue for future technology. Documented hardware is what we need now.
The scarcity of documented hardware is indeed a tremendous problem. In general I don't see any way we can fix it except by reverse engineering to figure out the specs.
jkrise: Why can't the FSF pool resources; license technology from ARM Holdings; and build a truly Free Tablet, Free Cellphone and Free PC running Free GNU/Linux instead of the pseudo-free Android? I am sure the community will pay any money to buy truly free Hardware from the FHF.
RMS: This would cost millions of dollars, and we have no skills or experience in hardware manufacturing, so we couldn't do it.
We could try to raise funds to pay for reverse engineering of the VPU in the Novena laptop -- if we could find skilled reverse engineers ready to take the job. Can you introduce me to any?
Shorter copyright
by oneandoneis2
I believe you're in favor of much-reduced copyright terms - a few years rather than the endless decades of today. If copyright were reduced to, say, five years, then the vast majority of GNU code would become public-domain - copyleft depending on copyright as it does, this would mean anyone could create a [proprietary] fork of, say, emacs. How do you feel about that?
RMS: For this very reason, I oppose shortening copyright to 5 years without making some other change to prevent this harmful consequence. See http://www.gnu.org/philosophy/pirate-party.html.
With the 10-year copyright term I propose, this problem would not be significant.
People often identify proprietary software with copyright; there was a time when I did, too. However, that's a mistake. The two principal methods used to make programs proprietary are (1) EULAs (a legal method) and (2) keeping the source code secret (a technical method). Two secondary methods are (3) copyright (a legal method) and (4) putting the executable in a tyrant device (a technical method, see below). Patents are used too, but only to reinforce the others.
To defend our free software from being made nonfree, the only one of these four that we can use is copyright.
People like apps
by thetagger
There is an entire generation of people out there for whom mobile apps, mostly on iOS and Android, are the way in which they do their computing. The more successful apps are usually very well-designed with incredible user interfaces, an area where free software has not achieved much success, and sold at very low prices and,
RMS: These "advantages" can seem impressive to those who don't see what they cost in freedom. The most basic thing we must do is say, "I'd rather have nothing than have that," and then act accordingly.
thetagger: in many cases, also monetized through stolen personal data.
RMS: Please don't use "monetized" to mean "make money from". That word stinks of the attitude that "Profit justifies anything". See http://www.gnu.org/philosophy/words-to-avoid.html.
Besides which, the word's correct meaning is "to use something as a currency."
thetagger: It appears to me that the GNU project is mostly ignoring this important area - I am aware of Replicant and F-Droid but these are well behind their proprietary counterparts at the moment. What should we do? Ignore mobile and hope it goes away,
RMS: I personally will ignore it, because there is nothing about it that I want. Even if we assume it is has no phone radio connection, so it is not Stalin's dream, a computer with a small screen and no keyboard is so inconvenient as to be useless for me.
However, we need to try to bring freedom to mobile computer users. We must not ignore them.
thetagger: try to get onboard with Replicant and F-Droid,
RMS: If you want to use mobile computers, please contribute in this way.
But we will never have, in the free world, the sort of "social" snooping apps that so many internet users spend their time in. We can't compete in terms of the misguided values that our adversaries promote in order to ensnare people, and if we did, we would be doing wrong. We have to set an example of rejecting those values.
thetagger: try to bring in a new generation of free software developers that is native to the mobile environment,
RMS: If this is meant as an alternative to the previous two, I don't understand what it means. We welcome people of any and all generations in everything we do.
thetagger: or avoid the mobile "ecosystem" completely
RMS: In general, I avoid the word "ecosystem" in connection with computing because of its amoral premises.
In this case I'm at a loss for what it means. I don't understand how this option differs from the first option, "Ignore mobile and hope it goes away."
thetagger: and try to work on the hardware side and try to make free hardware that is not inherently trackable/centralized and then run free software on top of that instead?
RMS: When you say "free hardware", I think you mean documented hardware. (See above.)
We can in principle make our own documented hardware, but the only way that would directly help is by avoiding the need for reverse engineering to figure out how to run the peripherals. In practice, though, I think reverse engineering is probably easier.
However, preventing the tracking is another matter. The only way I can envision to prevent the tracking of geolocation of mobile phones is if you have them disconnected from the network nearly all the time. (Well, in theory it might work to carry a parabolic antenna so you can communicate with just one tower. Maybe that would prevent the use of triangulation to figure out where you are located. I don't know whether this could be made to really work. Does anyone want to try it?)
Fundamentally, privacy-preserving computing has to be done mainly in your own computer. We have to reject the dependence on servers that the proprietary world is pushing people into. Freedom requires local application programs, rather than "web apps" or server-backed "mobile apps".
Do you foresee a viable Free Car OS?
by Medievalist
Automobile user interfaces have become increasingly complex and de-standardized as computerization reaches into the driver's seat. The major vendors don't seem to care about possible legal liabilities of designing inherently dangerous UIs. Google has enticed Honda, GM and Audi to join the Open Automotive Alliance, but that project seems more oriented towards selling android and nVidia products than providing an objectively better car OS. Do you see a future where a real Free (or at least Open Source) car operating system is a reality, or do you think the car makers will just continue to create unsafe and unstandardized vehicle UIs indefinitely?
RMS: I don't see the future, so I can't tell you what will happen. I can comment on the problems I know about now in the automotive field, but I can't tell you whether we will win, because that depends on you.
It will be a hard fight to free the software in our cars, but it is essential for drivers -- and not just those that might wish to soup up or customize their cars. The issue affects everyone.
Proprietary software is an injustice in itself, but it also leads to further secondary injustices, such as malicious functionalities. In the case of cars, those can include surveillance and back doors, as well as DRM in the entertainment system.
To exclude those malicious functionalities, the users need to have control over the software. In other words, if you want to have even a chance to make sure that the only back door in your car is the one that lets you reach into the trunk, the software must be free/libre. Anything less is inadequate.
The question asks whether open source software might be almost as good as free software. The main difference between open source and free is in the values they are based on: free software raises the issue as a matter of right or wrong, while open source studiously avoids saying that. However, what's relevant to this question is the practical extensions of the two criteria. Those are _almost_ equivalent; nearly all programs that are open source are free software.
Source code that is open source but not free is rare. On GNU/Linux you will probably never encounter any. In a car, however, you really may find programs that are open source but not free. The main case of nonfree open source programs today is when you can change the source but you can't change the executable.
How is that possible? In such cases, the source is released under a free license; it is free software, and it is open source. You can change this source, but that doesn't do you much good, because you can't run your changed version. The executable comes signed by the manufacturer, and the processor it runs in is designed to reject any executable not signed. (We call such processors "tyrants".)
In the cases I know of, this program is a version of Linux, and the reason they can make its executable nonfree is that Linux is distributed under GNU GPL version 2. If it were under GPL version 3, the seller would be required to give you the signature key to sign executables for your car.
Android uses Linux (but not GNU; the only thing in common between the Android system and the GNU/Linux system is the kernel, Linux). If Android is used in a car, its executable is very likely to be made nonfree in this way.
Of course, tyrant processors can contain software whose source code is nonfree, even secret, and this too occurs in cars. However, those programs are not open source either, so they are not a difference between free software and open source.
What this shows is that we must insist that car software be free/libre; open source is not good enough. It is not enough to be allowed to play ineffectively with source code.
See here for more explanation of the difference between free software and open source. See Evgeny Morozov's article on the same point.
Projects not being done
by mwvdlee
Ignoring preference of [free software] license for a minute, the [free software] landscape has lots of software to satisfy a wide range of users. What piece of software is still sorely missing from the [free software] landscape that isn't yet being seriously attempted by any project? Short version; what [free software] projects still need to be started?
RMS: The most important missing programs are firmware for various peripheral devices, to replace the "binary blobs" found in the vanilla versions of Linux. Linux-libre deletes the blobs, and all the free GNU/Linux distros use deblobbed versions of Linux; that gets us a totally free system but it can't operate those peripherals.
It is also important to develop Gnash enough to handle the current version of Flash. People like to imagine that Flash is dead, but reports of its death are premature.
Look here for other things we would really like people to do.
free software into law?
by paulpach
You argue that it is unethical for someone to distribute software in a way that limits any one of the 4 freedoms to users. If you had the option, would you make it illegal to do so? In other words, if you had the option would you make it so that software developers were forced by law to use a free software license? or would you leave the option to the developers and try to convince them (without coercion) that it is the right thing to do?
RMS: In an ideal world, there would be no nonfree software. I think it is possible to get pretty close to that. But I don't propose to make nonfree software illegal under today's circumstances, because it is a leap too far; the public is not ready for it. Most users do not think that nonfree software is an injustice. A law that does not have public support is going to meet resistance.
What I advocate, for today, is to ban some egregious practices found in many proprietary programs, including digital restrictions management (see DefectiveByDesign.org), censorship of applications (jails) or works that can be viewed, or requiring code be signed with a key the user does not have (as in Restricted Boot; see fsf.org/campaigns).
Of course, there are other measures governments should adopt to recover computational sovereignty and lead society towards freedom.
We should also ban the practice of asking users of digital works to agree to contracts (EULAs) that give them less rights than copyright law allows to users. -
After a Long wait, GNU Screen Gets Refreshed
New submitter jostber (304257) writes "It's been a long wait, but now GNU Screen, the most useful CLI windows manager around, is available. Version 4.2.1 was released a couple of days ago and the maintainer's release news is here." There are fewer commits than you might expect for software that's had six years since its last major update, but that could be because the developers have had 23 years to knock out the major bugs. -
After a Long wait, GNU Screen Gets Refreshed
New submitter jostber (304257) writes "It's been a long wait, but now GNU Screen, the most useful CLI windows manager around, is available. Version 4.2.1 was released a couple of days ago and the maintainer's release news is here." There are fewer commits than you might expect for software that's had six years since its last major update, but that could be because the developers have had 23 years to knock out the major bugs. -
Interview: Ask Richard Stallman What You Will
Richard Stallman (RMS) founded the GNU Project in 1984, the Free Software Foundation in 1985, and remains one of the most important and outspoken advocates for software freedom. He now spends much of his time fighting excessive extension of copyright laws, digital restrictions management, and software patents. RMS has agreed to answer your questions about GNU/Linux, how GNU relates to Linux the kernel, free software, why he disagrees with the idea of open source, and other issues of public concern. As usual, ask as many as you'd like, but please, one question per post. -
Interview: Ask Richard Stallman What You Will
Richard Stallman (RMS) founded the GNU Project in 1984, the Free Software Foundation in 1985, and remains one of the most important and outspoken advocates for software freedom. He now spends much of his time fighting excessive extension of copyright laws, digital restrictions management, and software patents. RMS has agreed to answer your questions about GNU/Linux, how GNU relates to Linux the kernel, free software, why he disagrees with the idea of open source, and other issues of public concern. As usual, ask as many as you'd like, but please, one question per post. -
FSF's Richard Stallman Calls LLVM a 'Terrible Setback'
An anonymous reader writes "Richard Stallman has called LLVM a terrible setback in a new mailing list exchange over GCC vs. Clang. LLVM continues to be widely used and grow in popularity for different uses, but it's under a BSD-style license rather than the GPL. RMS wrote, 'For GCC to be replaced by another technically superior compiler that defended freedom equally well would cause me some personal regret, but I would rejoice for the community's advance. The existence of LLVM is a terrible setback for our community precisely because it is not copylefted and can be used as the basis for nonfree compilers — so that all contribution to LLVM directly helps proprietary software as much as it helps us.'" -
GNU Guile Scheme Gets a Register VM and CPS-Based IL
In late November, Andy Wingo pushed a new register VM to Guile's (the GNU implementation of the Scheme language) master branch. It brought a number of performance improvements, but led to a bit of a conceptual mismatch between the compiler's direct-style intermediate language and the virtual machine. Earlier this week Andy Wingo announced a new continuation-passing style intermediate language for Guile. From the article: "To recap, we switched from a stack machine to a register machine because, among other reasons, register machines can consume and produce named intermediate results in fewer instructions than stack machines, and that makes things faster. To take full advantage of this new capability, it is appropriate to switch at the same time from the direct-style intermediate language (IL) that we had to an IL that names all intermediate values. ... In Guile I chose a continuation-passing style language. ... Guile's CPS language is composed of terms, expressions, and continuations. It was heavily inspired by Andrew Kennedy's 'Compiling with Continuations, Continued' paper. ... The optimizations I have currently implemented for CPS are fairly basic. Contification was tricky. One thing I did recently was to make all non-tail $call nodes require $kreceive continuations; if, as in the common case, extra values were unused, that was reflected in an unused rest argument. This required a number of optimizations to clean up and remove the extra rest arguments for other kinds of source expressions: dead-code elimination, the typical beta/eta reduction, and some code generation changes." The article describes the CPS language provided by Guile and explains the reasons behind choosing CPS over SSA or A-Normal Form. The Guile manual contains draft documentation. The new VM and Intermediate Language will be released with Guile 2.2, which should be out later this year. -
GNU Guile Scheme Gets a Register VM and CPS-Based IL
In late November, Andy Wingo pushed a new register VM to Guile's (the GNU implementation of the Scheme language) master branch. It brought a number of performance improvements, but led to a bit of a conceptual mismatch between the compiler's direct-style intermediate language and the virtual machine. Earlier this week Andy Wingo announced a new continuation-passing style intermediate language for Guile. From the article: "To recap, we switched from a stack machine to a register machine because, among other reasons, register machines can consume and produce named intermediate results in fewer instructions than stack machines, and that makes things faster. To take full advantage of this new capability, it is appropriate to switch at the same time from the direct-style intermediate language (IL) that we had to an IL that names all intermediate values. ... In Guile I chose a continuation-passing style language. ... Guile's CPS language is composed of terms, expressions, and continuations. It was heavily inspired by Andrew Kennedy's 'Compiling with Continuations, Continued' paper. ... The optimizations I have currently implemented for CPS are fairly basic. Contification was tricky. One thing I did recently was to make all non-tail $call nodes require $kreceive continuations; if, as in the common case, extra values were unused, that was reflected in an unused rest argument. This required a number of optimizations to clean up and remove the extra rest arguments for other kinds of source expressions: dead-code elimination, the typical beta/eta reduction, and some code generation changes." The article describes the CPS language provided by Guile and explains the reasons behind choosing CPS over SSA or A-Normal Form. The Guile manual contains draft documentation. The new VM and Intermediate Language will be released with Guile 2.2, which should be out later this year. -
Emacs Needs To Move To GitHub, Says ESR
hypnosec writes "Eric S. Raymond, co-founder of the Open Source Initiative, has recommended that Emacs should move to another version control system like GitHub, as bzr is dying. In an email, Raymond highlighted the key reasons why he believes that Emacs should move. Raymond said that bzr is moribund; its dev list has flatlined; and most of Canonical's in-house projects have already abandoned bzr and moved to GitHub. ESR believes that bzr's codebase is sufficiently mature to be used as a production tool, but he does mention that continuing to use the revision control system will have 'social and signaling effects damaging to Emacs's prospects.'" Update: 01/06 20:50 GMT by U L : ESR did not suggest Github the proprietary hosting platform for git, but rather git the version control system. Which is actually already available on Savannah (the bazaar repository is automatically synced with the git repository). -
Emacs Needs To Move To GitHub, Says ESR
hypnosec writes "Eric S. Raymond, co-founder of the Open Source Initiative, has recommended that Emacs should move to another version control system like GitHub, as bzr is dying. In an email, Raymond highlighted the key reasons why he believes that Emacs should move. Raymond said that bzr is moribund; its dev list has flatlined; and most of Canonical's in-house projects have already abandoned bzr and moved to GitHub. ESR believes that bzr's codebase is sufficiently mature to be used as a production tool, but he does mention that continuing to use the revision control system will have 'social and signaling effects damaging to Emacs's prospects.'" Update: 01/06 20:50 GMT by U L : ESR did not suggest Github the proprietary hosting platform for git, but rather git the version control system. Which is actually already available on Savannah (the bazaar repository is automatically synced with the git repository). -
Open Source In the Datacenter: It Was Never About Innovation
An anonymous reader writes "The secret to open source innovation, and the reason for its triumphal success, has nothing to do with the desire to innovate. It's because of the four freedoms and the level playing field (and agility) that was the end result. It's like Douglas Adams' definition of flying: you don't try to fly, you throw yourself at the ground and miss. This article explains why it was never about innovation — it was always about freedom. Quoting: 'When the forces of economics put constant downward price pressure on software, developers look for other ways to derive income. Given the choice between simply submitting to economic forces and releasing no-cost software in proprietary form, developers found open source models to be a much better deal. Some of us didn't necessarily like the mechanics of those models, which included dual licensing and using copyleft as a means of collecting ransom, but it was a model in which developers could thrive.'" -
MELT, a GCC Compiler Plugin Framework, Reaches 1.0
karijes writes with news that the Middle End Lisp Translator extension for GCC has hit 1.0: "MELT is a high-level domain specific language for extending, customizing and exploring the GNU Compiler Collection. It targets advanced GCC users, giving them ability to hook on almost any GCC stage during compilation or interpretation phases. This release brings a lot of new things." New features include defmacro and changes to the antiquote operator. -
GCC 4.9 To See Significant Upgrades In 2014
noahfecks writes "It seems that the GCC developers are taking steps to roll out significant improvements after CLANG became more competitive. 'Among the highlights to look forward to right now with GCC 4.9 are: The Undefined Behavior Sanitizer has been ported to GCC; Ada and Fortran have seen upgrades; Improved C++14 support; RX100, RX200, and RX600 processor support; and Intel Silvermont hardware support.'" -
GCC 4.9 To See Significant Upgrades In 2014
noahfecks writes "It seems that the GCC developers are taking steps to roll out significant improvements after CLANG became more competitive. 'Among the highlights to look forward to right now with GCC 4.9 are: The Undefined Behavior Sanitizer has been ported to GCC; Ada and Fortran have seen upgrades; Improved C++14 support; RX100, RX200, and RX600 processor support; and Intel Silvermont hardware support.'" -
GNU Make 4.0 Released
jones_supa writes "A new major version of the classic GNU Make software has been released. First of all, Make 4.0 has integration support for GNU Guile Scheme. Guile is the extension system of the GNU project that is a Scheme programming language implementation and now in the Make world will be the embedded extension language. 4.0 also features a new 'output-sync' option, 'trace-enables' for tracing of targets, a 'none' flag for the 'debug' argument, and the 'job server' and .ONESHELL features are now supported under Windows. There are also new assignment operators, a new function for writing to files, and other enhancements. It's been reported that Make 4.0 also has more than 80 bug-fixes. More details can be found from their release announcement on the mailing list." -
GNU Make 4.0 Released
jones_supa writes "A new major version of the classic GNU Make software has been released. First of all, Make 4.0 has integration support for GNU Guile Scheme. Guile is the extension system of the GNU project that is a Scheme programming language implementation and now in the Make world will be the embedded extension language. 4.0 also features a new 'output-sync' option, 'trace-enables' for tracing of targets, a 'none' flag for the 'debug' argument, and the 'job server' and .ONESHELL features are now supported under Windows. There are also new assignment operators, a new function for writing to files, and other enhancements. It's been reported that Make 4.0 also has more than 80 bug-fixes. More details can be found from their release announcement on the mailing list." -
GNU Hurd 0.5, GNU Mach 1.4, GNU MIG 1.4 Released
jrepin writes "Which day could be better suited for publishing a set of Hurd package releases than the GNU project's 30th birthday? These new releases bundle bug fixes and enhancements done since the last releases more than a decade ago; really too many (both years and improvements) to list them individually, The GNU Hurd is the GNU project's replacement for the Unix kernel. It is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux)." -
New Unix Implementation Turns 30
Thirty years ago, rms wrote: "Free Unix! Starting this Thanksgiving I am going to write a complete Unix-compatible software system called GNU (for Gnu's Not Unix), and give it away free to everyone who can use it. Contributions of time, money, programs and equipment are greatly needed." And thus began the revolution. Thirty years after posting the initial announcement, it's hard to find someone who hasn't interacted with Free Software at some point, even if they didn't realize it. To celebrate, the FSF is holding an anniversary celebration and hackathon this weekend at MIT.To begin with, GNU will be a kernel plus all the utilities needed to write and run C programs: editor, shell, C compiler, linker, assembler, and a few other things. After this we will add a text formatter, a YACC, an Empire game, a spreadsheet, and hundreds of other things. We hope to supply, eventually, everything useful that normally comes with a Unix system, and anything else useful, including on-line and hardcopy documentation.
GNU will be able to run Unix programs, but will not be identical to Unix. We will make all improvements that are convenient, based on our experience with other operating systems. In particular, we plan to have longer filenames, file version numbers, a crashproof file system, filename completion perhaps, terminal-independent display support, and eventually a Lisp-based window system through which several Lisp programs and ordinary Unix programs can share a screen. Both C and Lisp will be available as system programming languages. We will have network software based on MIT's chaosnet protocol, far superior to UUCP. We may also have something compatible with UUCP.
Who Am I?
I am Richard Stallman, inventor of the original much-imitated EMACS editor, now at the Artificial Intelligence Lab at MIT. I have worked extensively on compilers, editors, debuggers, command interpreters, the Incompatible Timesharing System and the Lisp Machine operating system. I pioneered terminal-independent display support in ITS. In addition I have implemented one crashproof file system and two window systems for Lisp machines.
Why I Must Write GNU
I consider that the golden rule requires that if I like a program I must share it with other people who like it. I cannot in good conscience sign a nondisclosure agreement or a software license agreement.
So that I can continue to use computers without violating my principles, I have decided to put together a sufficient body of free software so that I will be able to get along without any software that is not free.
How You Can Contribute
I am asking computer manufacturers for donations of machines and money. I'm asking individuals for donations of programs and work.
One computer manufacturer has already offered to provide a machine. But we could use more. One consequence you can expect if you donate machines is that GNU will run on them at an early date. The machine had better be able to operate in a residential area, and not require sophisticated cooling or power.
Individual programmers can contribute by writing a compatible duplicate of some Unix utility and giving it to me. For most projects, such part-time distributed work would be very hard to coordinate; the independently-written parts would not work together. But for the particular task of replacing Unix, this problem is absent. Most interface specifications are fixed by Unix compatibility. If each contribution works with the rest of Unix, it will probably work with the rest of GNU.
If I get donations of money, I may be able to hire a few people full or part time. The salary won't be high, but I'm looking for people for whom knowing they are helping humanity is as important as money. I view this as a way of enabling dedicated people to devote their full energies to working on GNU by sparing them the need to make a living in another way.
For more information, contact me.
Arpanet mail:- RMS@MIT-MC.ARPA
Usenet:
- ...!mit-eddie!RMS@OZ
- ...!mit-vax!RMS@OZ
-
New Unix Implementation Turns 30
Thirty years ago, rms wrote: "Free Unix! Starting this Thanksgiving I am going to write a complete Unix-compatible software system called GNU (for Gnu's Not Unix), and give it away free to everyone who can use it. Contributions of time, money, programs and equipment are greatly needed." And thus began the revolution. Thirty years after posting the initial announcement, it's hard to find someone who hasn't interacted with Free Software at some point, even if they didn't realize it. To celebrate, the FSF is holding an anniversary celebration and hackathon this weekend at MIT.To begin with, GNU will be a kernel plus all the utilities needed to write and run C programs: editor, shell, C compiler, linker, assembler, and a few other things. After this we will add a text formatter, a YACC, an Empire game, a spreadsheet, and hundreds of other things. We hope to supply, eventually, everything useful that normally comes with a Unix system, and anything else useful, including on-line and hardcopy documentation.
GNU will be able to run Unix programs, but will not be identical to Unix. We will make all improvements that are convenient, based on our experience with other operating systems. In particular, we plan to have longer filenames, file version numbers, a crashproof file system, filename completion perhaps, terminal-independent display support, and eventually a Lisp-based window system through which several Lisp programs and ordinary Unix programs can share a screen. Both C and Lisp will be available as system programming languages. We will have network software based on MIT's chaosnet protocol, far superior to UUCP. We may also have something compatible with UUCP.
Who Am I?
I am Richard Stallman, inventor of the original much-imitated EMACS editor, now at the Artificial Intelligence Lab at MIT. I have worked extensively on compilers, editors, debuggers, command interpreters, the Incompatible Timesharing System and the Lisp Machine operating system. I pioneered terminal-independent display support in ITS. In addition I have implemented one crashproof file system and two window systems for Lisp machines.
Why I Must Write GNU
I consider that the golden rule requires that if I like a program I must share it with other people who like it. I cannot in good conscience sign a nondisclosure agreement or a software license agreement.
So that I can continue to use computers without violating my principles, I have decided to put together a sufficient body of free software so that I will be able to get along without any software that is not free.
How You Can Contribute
I am asking computer manufacturers for donations of machines and money. I'm asking individuals for donations of programs and work.
One computer manufacturer has already offered to provide a machine. But we could use more. One consequence you can expect if you donate machines is that GNU will run on them at an early date. The machine had better be able to operate in a residential area, and not require sophisticated cooling or power.
Individual programmers can contribute by writing a compatible duplicate of some Unix utility and giving it to me. For most projects, such part-time distributed work would be very hard to coordinate; the independently-written parts would not work together. But for the particular task of replacing Unix, this problem is absent. Most interface specifications are fixed by Unix compatibility. If each contribution works with the rest of Unix, it will probably work with the rest of GNU.
If I get donations of money, I may be able to hire a few people full or part time. The salary won't be high, but I'm looking for people for whom knowing they are helping humanity is as important as money. I view this as a way of enabling dedicated people to devote their full energies to working on GNU by sparing them the need to make a living in another way.
For more information, contact me.
Arpanet mail:- RMS@MIT-MC.ARPA
Usenet:
- ...!mit-eddie!RMS@OZ
- ...!mit-vax!RMS@OZ
-
New Unix Implementation Turns 30
Thirty years ago, rms wrote: "Free Unix! Starting this Thanksgiving I am going to write a complete Unix-compatible software system called GNU (for Gnu's Not Unix), and give it away free to everyone who can use it. Contributions of time, money, programs and equipment are greatly needed." And thus began the revolution. Thirty years after posting the initial announcement, it's hard to find someone who hasn't interacted with Free Software at some point, even if they didn't realize it. To celebrate, the FSF is holding an anniversary celebration and hackathon this weekend at MIT.To begin with, GNU will be a kernel plus all the utilities needed to write and run C programs: editor, shell, C compiler, linker, assembler, and a few other things. After this we will add a text formatter, a YACC, an Empire game, a spreadsheet, and hundreds of other things. We hope to supply, eventually, everything useful that normally comes with a Unix system, and anything else useful, including on-line and hardcopy documentation.
GNU will be able to run Unix programs, but will not be identical to Unix. We will make all improvements that are convenient, based on our experience with other operating systems. In particular, we plan to have longer filenames, file version numbers, a crashproof file system, filename completion perhaps, terminal-independent display support, and eventually a Lisp-based window system through which several Lisp programs and ordinary Unix programs can share a screen. Both C and Lisp will be available as system programming languages. We will have network software based on MIT's chaosnet protocol, far superior to UUCP. We may also have something compatible with UUCP.
Who Am I?
I am Richard Stallman, inventor of the original much-imitated EMACS editor, now at the Artificial Intelligence Lab at MIT. I have worked extensively on compilers, editors, debuggers, command interpreters, the Incompatible Timesharing System and the Lisp Machine operating system. I pioneered terminal-independent display support in ITS. In addition I have implemented one crashproof file system and two window systems for Lisp machines.
Why I Must Write GNU
I consider that the golden rule requires that if I like a program I must share it with other people who like it. I cannot in good conscience sign a nondisclosure agreement or a software license agreement.
So that I can continue to use computers without violating my principles, I have decided to put together a sufficient body of free software so that I will be able to get along without any software that is not free.
How You Can Contribute
I am asking computer manufacturers for donations of machines and money. I'm asking individuals for donations of programs and work.
One computer manufacturer has already offered to provide a machine. But we could use more. One consequence you can expect if you donate machines is that GNU will run on them at an early date. The machine had better be able to operate in a residential area, and not require sophisticated cooling or power.
Individual programmers can contribute by writing a compatible duplicate of some Unix utility and giving it to me. For most projects, such part-time distributed work would be very hard to coordinate; the independently-written parts would not work together. But for the particular task of replacing Unix, this problem is absent. Most interface specifications are fixed by Unix compatibility. If each contribution works with the rest of Unix, it will probably work with the rest of GNU.
If I get donations of money, I may be able to hire a few people full or part time. The salary won't be high, but I'm looking for people for whom knowing they are helping humanity is as important as money. I view this as a way of enabling dedicated people to devote their full energies to working on GNU by sparing them the need to make a living in another way.
For more information, contact me.
Arpanet mail:- RMS@MIT-MC.ARPA
Usenet:
- ...!mit-eddie!RMS@OZ
- ...!mit-vax!RMS@OZ
-
LLVM's Libc++ Now Has C++1Y Standard Library Support
An anonymous reader writes "LLVM's libc++ standard library (an alternative to GNU libstdc++) now has full support for C++1y, which is expected to become C++14 next year. Code merged this week implements the full C++1y standard library, with support for new language features in the Clang compiler frontend nearly complete." GCC has some support for the soon-to-be standard too. The C++ standards committee is expected to produce a more or less final draft in just a few weeks. The LLVM and GCC C++14 status pages both have links to the proposals for the new features.