Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.

 



Forgot your password?
typodupeerror

Comment: Voter-verified paper ballots trump "open source" (Score 3, Insightful) 127

by jbn-o (#48471393) Attached to: Voting Machines Malfunction: 5,000 Votes Not Counted In Kansas County

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 /. summary: You never should have stopped using voter-verified paper ballots.

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.

Comment: A sort-of correction conducing to the same (Score 1) 525

by jbn-o (#48375801) Attached to: Microsoft To Open Source<nobr> <wbr></nobr>.NET and Take It Cross-Platform

A sort-of correction that reaches the same conclusion: End Software Patents (ESP) speculates that "the 2012 'in re Spansion' case in the USA and the judge ruled that a promise is the same as a licence". And since ESP mentions that Microsoft's Patent Promise has serious problems restricting its promise to those who don't add covered code to another project or those who produce something other than a "compliant implementation" of .NET, it seems that Microsoft patent promise has enough problems that it's still wise to not build dependencies on .NET (as the FSF warned).

Comment: Beware: MS no-sue promise can turn on you (Score 1) 525

by jbn-o (#48374411) Attached to: Microsoft To Open Source<nobr> <wbr></nobr>.NET and Take It Cross-Platform

Mono developer Miguel de Icaza has pledged to continue to add Microsoft's code to Mono saying "Like we did in the past with .NET code that Microsoft open sourced, and like we did with Roslyn, we are going to be integrating this code into Mono and Xamarin's products".

But is that wise? To your point, the Free Software Foundation's reaction to Microsoft's similar 2009 action point to exactly how changing ownership of patents render Microsoft's Patent Promise not to sue useless. This very promise could become the basis for a patent trap. In 2009 Microsoft's promise not to sue was called a "Community Promise" but today's .NET promise not to sue is risky in the same way—it's not (as the FSF rightly puts it) "an irrevocable patent license for all of its patents that Mono actually exercises" and neither is the MIT license Microsoft chose to release their code under.

Looking back at that essay from 2009, we see the FSF warn us (emphasis mine):

The Community Promise does not give you any rights to exercise the patented claims. It only says that Microsoft will not sue you over claims in patents that it owns or controls. If Microsoft sells one of those patents, there's nothing stopping the buyer from suing everyone who uses the software.

Falling into this trap will directly adversely affect your ability to run, share, and modify covered software. The FSF points to a practical way out as well:

The Solution: A Comprehensive Patent License

If Microsoft genuinely wants to reassure free software users that it does not intend to sue them for using Mono, it should grant the public an irrevocable patent license for all of its patents that Mono actually exercises. That would neatly avoid all of the existing problems with the Community Promise: it's broad enough in scope that we don't have to figure out what's covered by the specification or strictly necessary to implement it. And it would still be in force even if Microsoft sold the patents.

This isn't an unreasonable request, either. GPLv3 requires distributors to provide a similar license when they convey modified versions of covered software, and plenty of companies large and small have had no problem doing that. Certainly one with Microsoft's resources should be able to manage this, too. If they're unsure how to go about it, they should get in touch with us; we'd be happy to work with them to make sure it's satisfactory.

Until that happens, free software developers still should not write software that depends on Mono. C# implementations can still be attacked by Microsoft's patents: the Community Promise is designed to give the company several outs if it wants them. We don't want to see developers' hard work lost to the community if we lose the ability to use Mono, and until we eliminate software patents altogether, using another language is the best way to prevent that from happening.

I find it no accident that the built-to-be-business-friendly "open source" language is all over this announcement including the aforementioned blog post from a prominent endorser, while the wise warnings of falling into a patent trap come from the FSF who consistently looks out for all computer user's software freedoms—software freedom being the very thing that "open source" was designed never to bring to mind (see source 1, source 2 for the history and rationale on this point).

Comment: Never ethical, never private, never secure (Score 1) 164

by jbn-o (#47642071) Attached to: F-Secure: Xiaomi Smartphones Do Secretly Steal Your Data

Location data and contact/address data are sensitive yet inextricably linked to how people use trackers (also known as cell phones and other portable electronic devices). Whether the device conveys GPS coordinates, can be tracked to a remarkably small area via cell tower triangulation, or unknown (to the user) parties get the information from a proprietor (such as Apple), the privacy loss inherent in ordinary tracker operation makes it impossible to "avoid storing sensitive data on the phone".

This is no accident. When societies face the combination of nonfree software (both in OS and programs people are encouraged to install later), devices that are as close to always-on as is possible for mobile computing, and a userbase as persistently distracted away from focusing on their civil liberties as most tracker users are (no thanks to sites like /. which carry stories like these without any ethical critique to go alongside the corporate-written stockprice-sensitive spin) results like these are the outcome. Add to that the unethical ways in which trackers are made (such as Apple turning a blind eye to the environment in China or expoiting workers at Pegatron even worse than at Foxconn but Apple is certainly not alone in any of this) and you have an ugly recipe for abuse from end-to-end. Many thanks to people including Richard Stallman for compiling useful information about all of this and for his many years of warning people against nonfree software.

Comment: Proprietary power is always anti-user. (Score 0) 267

by jbn-o (#47619659) Attached to: Skype Blocks Customers Using OS-X 10.5.x and Earlier

It's news because so many people are never taught to think of software freedom. Instead sites like this one shill for Microsoft, Apple, and a weaker "open source" message that was designed to draw attention away from ethical examination of the issue. Cutting off service and not providing programs for various systems are just two of the things proprietors with the power they wield over users. Software freedom would mean letting users maintain older OSes as much as they want to, backport programs they found valuable, and run builds of modern programs as much as desired.

You're quite right to point out that Apple is no friend on these grounds. But this shouldn't be looked at in terms of business; the effect on the user is far more important. Proprietors are the same in how they treat people because the heart of any nonfree software is unethical power over someone else's use of a computer. Richard Stallman reminds us that Apple uses this same leverage to pressure users into malicious "upgrades":

Using the lever of "You have a choice, but unless you say yes, your old activities will stop working" is something that Apple has done before, with malicious "upgrades". Apple ostensibly doesn't force people to accept the new nasty thing; it just punishes them if they don't.

Nobody should be obliged to work on developing programs and nobody should have the power to prevent users from developing the software.

Comment: Yes, voters need voter-verified paper ballots (Score 1) 190

by jbn-o (#47586497) Attached to: Ask Slashdot: Should I Fight Against Online Voting In Our Municipality?

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.

Comment: Please explain your terms (Score 1) 189

by jbn-o (#47571131) Attached to: An Accidental Wikipedia Hoax

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.

Comment: Reject all proprietary software and "choice" too (Score 1, Insightful) 436

by jbn-o (#47561643) Attached to: Which Is Better, Adblock Or Adblock Plus?
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.

Comment: Software freedom is worth caring about (Score 2) 234

by jbn-o (#47558991) Attached to: Free Copy of the Sims 2 Contains SecuROM

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").

Comment: Can it be updated and run Free Software? (Score 1) 91

by jbn-o (#47520383) Attached to: Intel Launches Self-Encrypting SSD
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.

Comment: Yet another reason to insist on software freedom (Score 2) 277

by jbn-o (#47472047) Attached to: Sony Forgets To Pay For Domain, Hilarity Ensues

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?

Comment: Stallman's "blessings" are for software freedom (Score 1) 101

by jbn-o (#47436411) Attached to: First Release of LibreSSL Portable Is Available

[...] 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.

Comment: Everyone needs software freedom. (Score 1) 307

by jbn-o (#47184551) Attached to: GM Names and Fires Engineers Involved In Faulty Ignition Switch

And why all computer users need free software in all of their computers. I don't want someone I don't trust vetting the software that has the ability to ruin my project or kill me. Those who get to audit code may be expert in someone else's opinion, but I would rather have software freedom.

Comment: Re:Fixing a social problem with technical means? (Score 1) 108

It's not enough, true, but we need to get Americans trained in the practice of being more politically active and to seriously consider the consequences of their consumerism. Today, encouraging people to think of encryption as required for increased secure communications is good. We can't fix anything "once and for all" because any change to anything can be reverted (hence Andrew Jackson's warning "...eternal vigilance by the people is the price of liberty, and that you must pay the price if you wish to secure the blessing" applies here too). Software proprietors and others who want to rob computer users of their freedom spend billions training people to think ephemerally (in fact, /.'s chosen "firehose" structure of fast and frequent updates usually from corporate repeaters exists to further that end). We need ordinary people to become more aware of the consequences of ignorance, make better choices, and train future generations that the acceptable social norm is lifelong political involvement. I think failing to meet this need is one of Snowden's fears ("The greatest fear that I have regarding the outcome for America of these disclosures is that nothing will change..."), and why Stallman says things like "I don't want any fans I want Freedom Fighters, who could actually help in his revolution". I have no doubt that whomever follows that murderous war criminal Obama in the US White House will follow the same behavior he both chose to follow from George W. Bush and ramp up. I'm not certain what will stop the horrors of "Terror Tuesday" killings, indiscriminate NSA spying, and more, but I won't object when groups want to raise awareness and help normalize objecting to the loss of our civil liberties.

Comment: More of Eben Moglen's ramifications on Snowden (Score 1) 348

by jbn-o (#47102299) Attached to: Why Snowden Did Right

In case you didn't get to the bottom of the Guardian essay, that essay comes from "Snowden and the Future", a 4-part talk series Eben Moglen gave on October 9, October 30, November 13 and December 4 2013. It is highly recommended reading, watching, and/or listening. Audio, video, and transcripts are available at his website.

Is your job running? You'd better go catch it!

Working...