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'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.

You never know when they will get killed. Same goes for Free Sharepoint, Free Office 365, Free One Drive etc. Get off them and breathe free.

and the manufacturer says "not our problem--it's old!" Then people might realize what a Pandora's Box this is...

This is exactly what Microsoft is saying about Windows XP. For IOT devices lasting dozens of years, it is better to stay as far away from Microsoft as possible.

My first and subsequent posts, and the article - are all about Microsoft's attempts to earn trust. Many millions of customers have already reposed trust and money with Microsoft for their software. Migrating to open source is not an easy option for most of them; and indeed that is not the point under debate.

If Microsoft wants their loyal trustworthy userbase to continue to trust them, they should adopt different measures than being pseudo-transparent with biggest customers such as the government. I have not written, nor intend to debate upon Microsoft's customers migrating to open source.

If you want to buy 20 machines today with a Windows OS, the only choice is Windows 8. Even though almost a billion PCs run XP, it is not possible to get a new machine with a legal licensed copy of XP without jumping through numerous hoops and shelling out loads of cash.

Microsoft wants us to trust their word that it is not feasible to offer or support XP on new machines. This is not believable. Opening up the source code is the only way to prove or disprove Microsoft's version of the facts.

Whether you agree or not is not important. Hundreds of legacy code developed for Windows platform using Windows development tools run only on XP and are not supported by 7 or 8. Customers are left with no choice but to rewrite code at great expense, often impossible since the vendors are no longer in business. In my view this represents a lock-in, whereby customers are forced to shell out large sums of money to obtain support for XP legally on new systems by investing in Enterprise Volume License Agreements and associated costs.

A pseudonym enables other posters to look at your posting history and judge for themselves based on what they see.

Be brave enough to post after logging in, or you will be thought of as a shill.

My post wasn't about the options for Microsoft's customers. It was about Microsoft's attempts at transparency to earn trust.

Don't force bloatware on hapless customers. XP was 1.2GB. XP with SP2 was about 2GB. XP with SP3 is about 7GB. And now Microsoft claims XP is so insecure it cannot be patched anymore, so customers have to buy a new OS which weighs in at 20GB.

Cut all the crap and come clean. Release the entire source code for XP if you are not going to patch it. Or keep quiet and prepare to be unbelieved even if you speak the truth.

Yeah! And you kids, get of my lawn!!

BTW, if you think that "real engineers" deliver on time with predictable results, you need to read more about real engineers.