Yes, you should object.

Voters can't be sure that there's any evidence of their vote entering the system accurately reflecting their vote without a voter-verified paper ballot. Electronic ballots are easily lost, misrepresented, and useless in a recount. Electronic voting doesn't improve on the problems with voter-verified paper ballots and electronic ballots introduce problems all their own. So this is an area where traditional voter-verified paper ballots are better for the voter and well worth fighting for.

Braille printed ballots are extra nice to have (the braille can co-exist with the ink print on the same voter-verified paper ballot). But voters who can't read ink printed text without braille (illiterate and blind voters, to name a couple of examples) can get help from a computer to help them prepare a voter-verified paper ballot. These voters can feed in a voter-verified paper ballot into a machine that is essentially a scanner/printer combo that prints marks on a traditional voter-verified paper ballot filling in the blanks in accordance with user input to the computer. The user can get the voter-verified paper ballot out of the machine and check out its accuracy, either submit it to be counted or spoil it to get a new voter-verified paper ballot and mark it themselves, Such voters can also bring someone they trust to help them vote but this is obviously less preferred as this means divulging one's vote to someone else.

I occassionally use ed even on normal machines while I'm running X... it does a fine job on simple little edits, and just feels so nice and lightweight, it doesn't even clear the terminal.... (which can be handy, e.g. when you want to preserve your terminal context)

It's not installed by default on Debian.

You can easily install it, of course, but you can easily install a bazillion text editors....

I'm not convinced Wikipedia is somehow profoundly not an encylopedia. Part of the reason your post doesn't convince me is because you criticize Wikipedia for not being "on par with the Brittanica" without specifying what you think exactly that par is, or what exactly you think "the concept of an encyclopedia is". It's difficult to have a conversation about these things without understanding what you view those things to be.

I know that I don't get the same freedoms with Brittanica I get with Wikipedia: I'm not allowed to distribute verbatim or edited copies of Brittanica entries. These freedoms translate into practical outcomes for most people, most notably the main means of keeping Wikipedia viable and an (apparently) mainstream source of information. By contrast, if someone wants to build on what they view as Brittanica's articles they have to negotiate with Brittanica to do that (and I've never seen anyone do this) but I know of projects that build on Wikipedia. Many articles I find interesting and worth listing in an encyclopedia are simply missing from Brittanica but are present in Wikipedia, such as why Brittanica thinks "GNU/Linux" and "Linux" are the same (which is both inaccurate and unfair) while maintaining that the former is an operating system and the latter a kernel (which is accurate and fair).

I have no changelog for Brittanica, so I have nothing to point to there that compares with what I can get in Wikipedia's changelog. TFA implicitly shows the value of changelogs for identifying how long edits have remained and who edited what when.

As for editing by non-experts: I don't know who edits Brittanica's many editions (including the paper editions) nor do I know what their qualifications are. I find this to be roughly equivalent to Wikipedia because I don't know who edits Wikipedia either, nor do I know their qualifications.

I remember some years ago reading an article by a Brittanica affiliate who essentially proposed to weigh Brittanica and Wikipedia on an evaluation of one obscure point he knew something about. Not only is that bad surveying, but it invites critique that can be used against Brittanica just as easily. I recall being struck by how behind the times Brittanica was the last time I saw it, particularly on the free software movement, a topic I know something about. I found the lack of coverage in Brittanica telling. Where Brittanica had something to say on the matter, I found Brittanica made the usual errors and confusions people make when they've only been exposed to "open source" (such as attributing what Richard Stallman's actions with "open source" despite historical contradiction and Stallman's own words and deeds); open source movement's philosophy, practical outcomes, or history isn't the same as free software and it's a shame history and contemporary evidence weighs so lightly for Brittanica.

You'd not only rightly reject Google Chrome you'd also reject choice as a reason to favor nonfree software. Chrome is a nonfree browser so that is right out. A choice of nonfree programs doesn't satisfy what computer users need—software freedom. Choice is easily satisfied in that there's more than one alternative but choice of software says nothing about how well the alternatives address important needs to control one's computer (rather than letting the software control the users). So choice of software is a weak substitute for the freedoms to run, inspect, share, and modify software.

People who care about controlling their computers care, as should all computer users care. This is another instance in a long line of great learning opportunities to distinguish between 'free as in price' and 'free as in freedom'—software proprietors get away with malware because how the software works is kept secret from its users. TFA tells us that Electronic Arts didn't tell prospective users SecuROM was a part of the gratis Sims 2 install, probably because EA knew users wouldn't install Sims 2 if they knew it came with SecuROM. Proprietors abuse the trust users have placed in them and it's time to teach users how things actually work, not encourage dismissal that hands users over to the abusers ("who cares").

If the drive's software were flashable (the device could be updated with different software) and the software were Free Software, there would be no reason to fear Intel's connection to the NSA. Users would have the freedoms they need to make sure the software does what they want it to do. Proprietary encryption, no matter who writes it or distributes it, is always untrustworthy for the same reason proprietary software is untrustworthy—you don't really know what it's doing and neither does anyone you can trust to help you understand what it's doing. Furthermore you can't make it do what you want and you can't help others by distributing improved versions that respect other user's freedoms.

Early Tuesday, gamers woke up to find out that they couldn't log in to any Sony Online Entertainment games--no Everquest, no Planetside 2, none of them.

Could the users have used another server to connect with each other? Or is this a case of DRM ("Digital Restrictions Management", when properly viewed from the perspective of its effect on the users) and, more generally, nonfree software restricting users from running the games with other people?

[...] not everything has to be blessed by Stallmann to be acceptable

Regarding this point, Stallman certainly does endorse Free Software. And so much of what is in OpenBSD is Free Software—software that respects a user's software freedom—and the same goes for OpenSSL. Stallman (and his organization, the Free Software Foundation(FSF)) are known for standing up for a user's software freedom. Non-copylefted Free Software is Free Software. Furthermore, in 2004 the FSF gave Theo de Raadt an award for the Advancement of Free Software, "[f]or recognition as founder and project leader of the OpenBSD and OpenSSH projects, Theo de Raadt's work has also led to significant contributions to other BSD distributions and GNU/Linux. Of particular note is Theo's work on OpenSSH". A free system need not include GNU software or be licensed under a GNU license (such as the GPL) to respect a user's software freedom.

The FSF is quite clear why it doesn't list OpenBSD (or the other BSD distributions) in their list of Free system distributions:

FreeBSD, NetBSD, and OpenBSD all include instructions for obtaining nonfree programs in their ports system. In addition, their kernels include nonfree firmware blobs.

Nonfree firmware programs used with Linux, the kernel, are called "blobs", and that's how we use the term. In BSD parlance, the term "blob" means something else: a nonfree driver. OpenBSD and perhaps other BSD distributions (called "projects" by BSD developers) have the policy of not including those. That is the right policy, as regards drivers; but when the developers say these distributions âoecontain no blobsâ, it causes a misunderstanding. They are not talking about firmware blobs.

No BSD distribution has policies against proprietary binary-only firmware that might be loaded even by free drivers.

Including nonfree software and pointing users to nonfree software is quite common among those who endorse the open source philosophy, as the FSF has long pointed out (older essay, newer essay). The open source movement's philosophy is a development methodology built to toss aside software freedom for practical convenience in an attempt to be "more acceptable to business". So this philosophical difference sets up a radically different reaction in the face of reliable, powerful proprietary software. Quoting the newer essay:

A pure open source enthusiast, one that is not at all influenced by the ideals of free software, will say, "I am surprised you were able to make the program work so well without using our development model, but you did. How can I get a copy?" This attitude will reward schemes that take away our freedom, leading to its loss.

The free software activist will say, "Your program is very attractive, but I value my freedom more. So I reject your program. Instead I will support a project to develop a free replacement." If we value our freedom, we can act to maintain and defend it.

The other problem is that all this development seems like an insane urban-planning clusterf*ck... the rulers who are bankrolling it all want a glitzy showpiece to puff up their egos, and basically spend their lives traveling between high-end luxury malls, 60th floor corporate boardrooms, and enormous homes, in fleets of air-conditioned Mercedes SUVs. So they're designing a city optimized for those things. The result seems to be someplace that looks impressive in very long shots of the night-time skyline featured in inflight magazines, but which doesn't really work very well as an actual city (with, you know, people, not all of whom are necessarily ultra-wealthy)...

FWIW, I'm also learning German. It's the fifth language I'm learning as an adult and it's definitely the toughest. I've never found any good software or edu-websites, I just use the old methods. I watch a lot of German telly:

* http://mediathek.daserste.de/s...
* http://www.zdf.de/Sendungen-vo...

Series are the easiest because you can get to know the characters and then they're kinda predictable so you can't get completely lost. The News is easy enough because there's lots of pictures and you'll know the context of most stories, but it doesn't teach you conversational German. Comedy can be the toughest. On Das Erste, there's a crime drama most Friday and Sunday nights called Tatort which is good because there's also a version for blind people ("hÃrfassung" - o-umlaut between h and r, if that doesn't display right), which has everything of the normal version plus one extra voice describing the visuals, so you hear a lot more words.

I also read German translations of books I've already read. And when I'm cooking I leave on WDR5 talk radio in the background, all to help develop a feel for how the language sounds when used correctly:

* http://www.listenlive.eu/germa...

And I do tandems with a native German:

* http://conversationexchange.co...

Oh, and of course I'm working my way through a book with grammar and exercises.

Yeh, German's a tough nut to crack alright. Unlike Spanish, you have to do a lot of grammar before you can really start building sentences (the declensions are what frustrate me most) but I think it's a language where your effort won't show at first, but then there's the breakthrough later.

With regard to this, one helpful thing in the ruling is that the Court says that old and ubiquitous technologies don't count when judging if an abstract concept has been transformed into a patentable application of said abstract concept.

(Patent lawyers are up in arms about this, complaining that the Court has "mixed up article 101 (subject matter) with articles 102 (prior art) and 103 (obviousness)". To get more patents, they want to reduce the "abstract ideas" exception to a theoretical concept that only happens inside people's brains any patent application can pass.)

So Timothy's right (as usual), but still, at least we have the Justices acknowledging that algorithms shouldn't be patentable, and that "on a computer" doesn't make a non-patentable concept patentable. All we have to do is bridge that last gap and show them that all software is math:

http://en.swpat.org/wiki/Softw...

For Alice v. CLS, more analyses listed at the end of this page:

http://en.swpat.org/wiki/Alice...

I know the headline is correct because Gene Quinn is hopping mad. Quinn makes a living by obtaining software patents and always says he can draft around any limits imposed by the courts, but here's what he's saying today:

"an intellectually bankrupt opinion ... will render many hundreds of thousands of software patents completely useless ... On first read I donâ(TM)t see how any software patent claims written as method or systems claims can survive challenge."

http://www.ipwatchdog.com/2014...

I didn't want to trust my own reading, but I knew it was a big victory when I read Quinn's reaction.

Sorry, all you've got is me.

If anyone can help, I've been building this wiki for five years now without a break:

http://en.swpat.org/

(And I'm working on campaigns against software patents since 2003.)