Don't worry, he won't. And this story (like so much of
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Don't worry, he won't. And this story (like so much of
I'm uninterested in DRM'd e-readers or any e-reader that reveals my location, refuses to let me copy, quote, print, and do other things I do with books. I'm unwilling to sacrifice my rights because some publisher wants a rent scheme on books or wants me to constantly feed them information on my whereabouts, what I'm reading, logging my name with what I read (which even my local library only does as long as the loan), and other privacy violations that simply aren't possible with books. Calling DRM "digital restrictions management" is right and proper because that frames the debate where it belongs—around user's rights.
I'm not so sure that's true because the relevant laws are set such that the penalties are so light for the wealthy violators and virtually non-existant for the most powerful participants in the system. First, the organization with the most patents is not in a position to "feel pain" as you say; IBM's power is (as they've said long ago) in cross-licensing. They said they get an order of magnitude more benefit by leveraging the power the patent scheme was built to exert (which is also part of the problem of calling organizations "patent trolls" as if leveraging that power is somehow not to be expected, or an abuse of an otherwise upright system, when in fact that power is just part of the system operating as designed). As a result, losing patent infringement lawsuits is not common for IBM. Richard Stallman laid out how this works in his patent talks many years ago:
IBM got two kinds of benefit from its 9000 US patents. I believe the number is larger today. These were first, collecting royalties and second, getting access to the patents of others. They said that the latter benefit is an order of magnitude greater. So the benefit that IBM got from being allowed to use the ideas that were patented by others was 10 times the direct benefit IBM could get from licensing patents. What does this really mean?
What is the benefit that IBM gets from this access to the patents of others? It is basically the benefit of being excused from the trouble that the patent system can cause you. The patent system is like a lottery. What happens with any given patent could be nothing, could be a windfall for some patent holder or a disaster for everyone else. But IBM being so big, for them, it averages out. They get to measure the average harm and good of the patent system. For them, the trouble of the patent system would have been 10 times the good. I say would have been because IBM through cross-licensing avoids experiencing that trouble. That trouble is only potential. It doesn't really happen to them. But when they measure the benefits of avoiding that trouble, they estimate it as 10 times the value of the money they collect from their patents.
With regard to Apple specifically, it's not that difficult to see that they get by in part by violating government-granted monopoly and they're wealthy enough to be able to afford to do it repeatedly. The people who run Apple now ran NeXT years ago. NeXT infringed the FSF's license (GPLv2) in NeXT's initially unauthorized GCC derivative in which NeXT added Objective-C support. NeXT and the FSF settled out of court when the FSF got them to comply with the terms of the GPL (lesson learned here: stand up for your strong copylefted free software licenses and the bullies will meet your terms). Apple would again violate the GPLv2 later by distributing an infringing copy of VideoLAN Client. VLC co-author Rémi Denis-Courmont wrote critically of Apple's choice to let the program through it's app store saying "Those terms are contradicted by the products usage rules of the AppStore through which Apple delivers applications to users of its mobile devices." Apple infringed upon 3 Chinese writer's copyrights and were ordered to pay 730,000 yuan ($118,000), hardly a sum that would stop Apple from doing this again. But the pattern seems clear: Apple violates laws it doesn't like and never really meets a punishment that will make the leaders of the organization question whether to do it again. Apple isn't unique in this but that is a detail; we need punishments for the wealthy and powerful that make them take the law more seriously. But most importantly for endeavors practiced by the general public, such as computer programming, we need to fight in an organized and political way to end software idea patents. Mere patent reform is a delaying tactic that benefits the powerful.
What stands out to me about your post and the grandparent post is how both of you malign someone with no evidence. I'm certainly not taking you seriously about speaking for "many people [in Seattle]" either.
Ah, the flames from someone without much finesse: Premature declaration of failure to discourage further examination ("The masses have spoken..."), misidentification of fault ("If Apple could have continued using gcc...", "[The FSF] should have gone into the hardware business..."), citing trends with no backing and overvaluing business interests ("...then corporations wouldn't have run away from any GPLv3 software..."), and outright lying about intention and execution ("...weighing the costs of the walled garden (censorship etc) vs the benefits (no viruses)...", "...the attempt to take over the Linux kernel by renaming GNU/Linux..."), your post has so much flamebait to choose from it's almost as if you were taking instruction from an open source proponent who is eager to convince licensors to pick non-copylefted software licenses so they see their work become charitable contributions to software proprietors.
If there's so little interest in protecting oneself from international spying, malware, and other forms of user abuse Glenn Greenwald and other journalists would find it hard to get articles on the Snowden revelations published anywhere, world leaders wouldn't be holding meetings about the Snowden revelations, and people/organizations around the world wouldn't care about encryption. Don't confuse a non-technical user's inability to do better than running proprietary apps from a walled garden with not caring about these issues. They get both no software freedom and plenty of malware in their choice. Most computer users are weighing options where freedom is not available; they're suffering from the myth of choice where all of the readily-available options they know about deny them loyal computers.
Speaking of proprietors, Apple is no victim here. Apple wasn't forced to switch to LLVM and Clang, they chose to because they're proprietors eager to rob users of their software freedom in derivative works. If any organization with the means can be accurately accused of not writing their own stuff, it's Apple not writing their own compilers but instead relying on other compilers. This goes back to NeXT which was the first big GPL copyright infringement case (according to Brad Kuhn, former Executive Director of the FSF which holds the copyright on GCC in his discussion on his OggCast "Free as in Freedom"). NeXT got caught distributing a proprietary derivative of GCC which contained code to compile Objective-C. When Jobs spoke with the FSF about the matter, the FSF informed him that they would enforce their license (GPLv2). Jobs never liked that and never forgot. Apple doesn't mind the GPL they just don't like to be in a position of equality with their users unless they can pull out of that relationship when it suits them (see Apple's purchase of Easy SW which originally developed CUPS).
The FSF never tried to "take over the Linux kernel" and isn't doing so now by properly identifying Linux as a part of an operating system. They have said for years and continue to say they would like the GNU Project to get a share of the credit (1, 2). They also acknowledge that there are systems that don't include GNU and therefore should not be called "GNU slash" anything. No doubt, it would be equally unfair and erroneous to call GNU/kFreeBSD or GNU/HURD a "Linux" system when Linux isn't a part of that. This has nothing to do with capability of writing a kernel; a Linux kernel without the blobs is available so there's no pressing need for a fully-free system to have its own original kernel written by the FSF or the GNU Project. The core of the issue was and is a "greenwashing" (as Brad Kuhn aptly put it) open source movement not bringing to mind a user's software freedom (mirror) and the intended effect (older essay, newer essay) that has on people not understanding what software freedom is for its own sake.
You should explain what you mean lest people read something into your hit-and-run argument that you don't mean. As it is, yours is an inarticulately defended counterargument which suggests you're not aware of the problems of arguing against software freedom by claiming that if one is free to become a slave, one isn't really free. That merely tries to turn freedom into paradox wherein proprietary software (the software that restricts your freedoms) are equivalent to respecting a user's software freedom. It's not a good argument.
In fact, nobody is restricting you from choosing non-free software or non-copylefted Free Software. The point remains with what you choose—what freedoms are you getting from your choices? With Free Software, particularly strongly-copylefted Free Software, the choices you are free to partake of are a lot more clear and beneficial to you, even if the strongly-copylefted Free Software program doesn't currently implement what you want. Because adding the missing functionality is an option and you don't have to fear that you trade away valuable freedoms in return. Convenience is simply overvalued to the point of giving up on liberties and that's a major problem.
I believe you're making a gross assumption by picking apart a minor error in my post. Most people use IP as shorthand.
No, I am responding to what you actually said. I do recommend avoiding the term "IP" no matter how popular it is precisely for the reasons I linked to if you wish to avoid the confusions that term raises.
I'm sure we're all grateful for your past and ongoing contributions to our software freedom (I certainly am) but nobody should get a pass for evidenceless assertions such as:
- "The issue with the FSF is that it is a political organization and doesn't give a crap about the quality of the software they release."
- "What RMS doesn't want is a threat to what he sees as his privileged place in the community."
When I hear an RMS talk I hear him give examples of real-world instances to back up his points. He writes with links to news stories to back up his claims. I don't see any pointers to that kind of information in what you write, just your opinion on matters that really need some backing up.
Consider your point about RMS's alleged egotistical involvement in this LLVM issue:
I can't help but hear a note of jealousy in RMS' tone when he fights against tools which are already free for the sake of preserving the FSF's position. The FSF has, quite frankly, sewn the seeds of this for many years by taking the policy that it did with GCC and other projects and making them inferior in order to keep them free. This position BEGS another group to come in and do it right. Some people may argue that he has a problem with the license.... I suspect that even if it were LGPLv3+ or GPLv3+ he would still have an issue since it is NOT gcc. If you make a more useful tool... people will flock to it. This is a lesson that I hope the FSF learns well and takes away from this experience.
I recall RMS saying something to this point:
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.
In fact much of that post to the firstname.lastname@example.org mailing list would be relevant to reply to this story today. And RMS published that post about a year ago.
Quite right, in fact most of what gets posted to
The Affero GPL version 3 or later will keep software Free as in freedom and meet the needs of the future. Users will undoubtedly want to know how things work and benefit from software written by programmers allowed to understand how things work. This will help us avoid the very trap the grandparent post referred to (and you wisely advised against).
RMS is not alone in his views on working to marginalize GCC in favor of something that can be made into proprietary software, Brad Kuhn talks about copyleft licensing and around 21m44s in the linked linux.conf.au talk he points out that proprietors (he notes Apple by name) contribute enough upstream to non-copyleft Free Software projects to keep those projects useful to the proprietor. It's hardly a stretch to see Apple doing the same for LLVM "because [Apple and Qualcomm] want GCC to die" as Kuhn points out in his talk. Steve Jobs and NeXT's history of copyright infringement with GCC is very much a part of this story. Being caught infringing the GPL on GCC is something I doubt Jobs or Apple ever forgot and is a big part of the reason why he, like so many open source enthusiasts, think non-copylefted licenses such as the MIT X11 and new BSD license are better than than an enforced GNU GPL.
Eben Moglen is quick to point out in his consistently wise speeches that "RMS was right" (as he did in his linux.conf.au 2015 keynote speech).
I am so disappointed in the open source community. It's like they don't care about the very foundation this community was built on.
The open source movement was started to never raise a user's software freedom as an issue. Read the FSF's essays (older essay, newer essay) on how open source differs from free software and you'll get a very clear explanation of how open source's goal to speak to business means accepting proprietary software and whatever other anti-user stuff businesses want to implement with proprietary software (DRM, spyware, back doors, patent traps, etc.). Mozilla's partnering with Adobe, the Linux kernel accepting and distributing proprietary software as part of the project (code which GNU Linux-libre removes), and Mono developers celebrating Microsoft's releasing
I concur. A development methodology ("open source") will not address any of the deficiencies (when viewed from the voter's perspective, the perspective that should matter most) of voting. No matter how much one trusts a voting program, there's no way to be sure that the computer used for voting is running only software one trusts. No electronic system can compete with the simplicity and recount-friendly approach of what is called for here: voter-verified paper ballots.
So address to the question in the
There are computers one can purchase that do as the parent post specified—the voter feeds in a blank ballot (one which they could have filled out manually if desired) and the computer (which has a scanner and printer attached) will scan the ballot, help the voter by showing the choices on a screen, reading the ballot aloud, or reading the ballot text to headphones, and then collect votes from the voter. Then the computer's printer will print the voter's votes on the paper ballot, and eject the printed paper ballot to let the user inspect that printed ballot. At this point the voter can choose to carry the voter-verified paper ballot to be counted or spoil that ballot and start again. The voter can also feed in a marked up ballot (marked by hand or by computer) and let the computer summarize the votes which that ballot specifies. These features let the blind and/or illiterate vote without losing their privacy by forcing them to find & bring in someone else to mark up their ballot for them. This is as close to computers used in voting as one should want to get.