Wisconsin Requires Open Source, Verifiable Voting
AdamBLang writes "Previously covered on Slashdot, Wisconsin Governor Jim Doyle today signed legislation that "will require the software of touch-screen voting machines used in elections to be open-source. Municipalities that use electronic voting machines are responsible for providing to the public, on request, the code used." Madison's Capital Times reports "the bill requires that if a municipality uses an electronic voting system that consists of a voting machine, the machine must generate a complete paper ballot showing all votes cast by each elector that is visually verifiable by the elector before he or she leaves the machine.""
[T]he machine must generate a complete paper ballot showing all votes cast by each elector that is visually verifiable by the elector before he or she leaves the machine.
And how do we know that the prinout matches whatever counter is incremented within the computer? Being open source makes it tamper-resistent, not tamper-proof. Would it not be easier to just use a paper ballot in the first place? Then any recount could be performed against the actual ballots cast, not as a spot check against computer (glitches|fraud).
Trolling is a art,
...but sadly, it is.
Common sense and open source prevailing? In America? Surely not!!
unfortunately you will still have to vote for either a republican, a democrat, or someone who will lose.
-Lod
Paper receipts should be a no brainer, as should be open source software for voting machines. Too bad this isn't occurring in every state, yet. Or is it? I am an ignorant person about this topic. Someone enlighten me.
... it does not matter what's used in the executable.
This is exactly what people have been saying all along. It is not a good idea to trust the numbers that the machine keeps track of electronically somewhere. Some sort of paper trail is definitely a good idea. Even a simple line printer that sits in the back of the room somewhere, printing a short summary of every cast ballot would work because it provides a paper trail that can be verified by a human.
Question is, why aren't other states doing this?
There's also a provision that the voting machines be made out of cheddar.
Try not. Do or do not, there is no try.
-- Dr. Spock, stardate 2822-3.
So instead of people who can't figure out how to punch the proper hole, now we'll have people pushing the wrong button, accidentely pushing the "Are you sure?" prompt's "OK" ....
Oh wait, whew, Wisconsin, not Florida...
MoM++ - A Classic Expanded - [Master of Magic 1.5]
http://mompp.sourceforge.net/
I can't wait to see what http://www.blackboxvoting.org/ has to say about this one.
It means they won't have to jump through fucking hoops just to test the machine (like in California)
[Fuck Beta]
o0t!
There seems to be (happily) no preclusion of printing bar codes indicating the choices underneath the names of the candidates. This should allow for rapid and accurate scanning and counting. Ballots can be verified by hand or other (possibly 3rd party) means to prove that the bar codes equal the name on the ballot.
This will speed up and make more accurate the counting vs. OCR of the candidates' names.
Unitarian Church: Freethinkers Congregate!
So the machine I/O will be avalible for examination ?
What about making the whole system from there through to the final count automated ?
Or is it still going to need a few recounts to be seen to be "fair"
making humans do the work of computers is silly!
This seems to be one step in the right direction hopefully they can avoid legal fiascos this way but does making it open source really help if the software is already reviewed? I suppose it cant hurt.
Diebold is getting right on this... : p
It hardly matters if it is open source. Who will compile it before it is uploaded to the machine ? Who will check that the correct software is loaded ? Who will check the guy doing the checking ?
Automated vote counting of any kind - electronic or mechanical - makes fraud considerably easier, puts a mystery shroud around the counting process and as such is incompatible with democracy. In the UK we count all the votes in our elections within 12 hours including the odd recount. Why are Americans obsessed with diluting their democracy by using machines to do it ?
the competing non-fraudulent technology will have to be electronic.
it's how the human brain works. electronic is seen as the next step.
so the good guys have to be electronic too.
if people try a completely different route, that entire class of technology is going to be ignored.
it's idiotic but true.
There are two meanings for "paper receipts":
1. paper ballot which is the actual ballot, kept by the county clerk / election officials;
2. paper receipt, kept by the voter, proving they've voted and indicating who they voted for.
The latter concept is VERY BAD. It would encourage the ability of someone to buy an election by paying money or favors to someone in exchange for their receipt proving they voted for someone in particular.
This is the reason we have secret ballots - to make vote-buying quite difficult if not impossible.
Unitarian Church: Freethinkers Congregate!
Isn't voting supposed to be anynomous for those who wish so?
:-)
non-american heratic
the bill requires that if a municipality uses an electronic voting system that consists of a voting machine, the machine must generate a complete paper ballot showing all votes cast by each elector that is visually verifiable by the elector before he or she leaves the machine.
Of course buried in the legalese was the rest of the bill:
The vote-tallying software shall be closed source and shall be owned in whole by Diebold. As such, the printed ballot shown to elector may have no bearing on actual vote recorded. Names may be substituted based on (1) party of candidate (2) intelligence of choice (3) corruption in district (4) time of day (5) OR if you live in Palm Beach or Broward County, pure whimsy. Additionally, elector may be fined or audited based on vote case, or in extreme cases, placed on the National Do-Not-Fly list and scheduled for investigation by the Department of Homeland Security.
Will the BIOS and firmware also have to be open source? Maybe this move will give some hardware manufacturers an incentive to start providing this.
Hallelujah!
(The above is not to be construed as an endorsement of any particular religion, or religion in general.)
"We reject as false the choice between our safety and our ideals." --The American President (20.1.2009)
Once we have a reliable computer voting system politicians will become redundant. Instead of voting for a president we can vote AS presidents (and senators, and representatives, and mayors, and so on). I have a friend who strongly believes the USA will become the first true democracy by voting itself as such in the 2012 elections....with all that has been happening, I think he might be right.
Sorry, "paper receipt" is just a bad idea, despite how popular it is among some. Here's the next step: the paper receipt goes to a party boss so you can collect the payment for your vote, or to your boss or union rep to prove you voted the "right" way so you can keep your job.
Flame me if you want, but I've been a candidate, so I have a vested interest in the issue. As long as the machine doesn't say "Diebold", I'd rather take a chance on some totally improbable conspiracy to rig electronic ballots. That's way less risky than a return to old party machine politics.
... provided we stop all the dead from voting Democratic as well.
Prof. Farnsworth - "Oh a lesson in not changing history from Mr I'm-My-Own-Grandpa!"
What would really be nice for secure voting would be a system of encrypted voting. Everyone writes their vote to a small disk or USB dongle twice: once cleartext, once encrypted with a public key. On Election Day the dongle is plugged into the open-source voting machine, which increments the vote-count of the appropriate candidate based on the cleartext version and associates the encrypted vote in a database with the voter's identity.
If at any point the vote needs to be verified or the voter contests the way their vote was registered said voter simply decrypts their encrypted vote with the necessary private key. Doing so violates the principle of the secret ballot, but unfortunately that's what must be done in order to verify that a vote was registered correctly, unless you simply run the election over again.
They're acting as if they want to avoid rampant abuse and fraud. While it sounds great, I don't think America is ready for such a radical notion.
-- scsg
Carma burning time ;)
I find it somewhat amusing that the country that brags to the world that they are such a great democracy, are having such a hard time to perform something as basic and simple as a vote without the citizens suspecting foul play and cheating all the time...
Isnt it some kind of generel error with a system when the major issue is not what to vote on, but if the voting process wasn't rigged?
Of course its good that the citicens can keep control on the elections, but why not just handle it like most of the rest of the "democratic" world, vote with paper notes, and have a public count for each election-locale where representatives from all parties who wants, can monitor the counting process.
That way there cant be any suspicions of rigged results - everything is public, and nobody can cheat.
Somehow I realy dont see the point in making elections electronic, since all machine-stored results is based on a chain of trust, since that trust doesnt exist, why not stick to paper?
The article states that "any device used". To me that implies that each county is responsible for deciding which machine they use. Is the state making sure that any system used also uses a standarized format for the results?
Also, just because you publish some source, that is no guarantee that that was the source that went into creating the binaries that are being executed. Are they going to use a mechanism to verify that a vendor publishes the exact source? Are they going to force vendors to react to bugs found within a specific timeframe. After all, someone examining the source could find a problem and potentially use it as an exploit, this usually isn't an issue because you're banking on someone else also finding the problem and being open/honest about it, but for something like voting, is that good enough? It seems like a lot of focus is being given to it being open source, but is ignoring other software deployment issues.
Can someone explain why we can standardize street signs and the amount of sugar allowed in school lunches but we cannot get a standardized election system?
After the 2000 election debacle, we had money thrown at the states to "fix the problem." So we ended up with 35 different solutions.
A simple federal mandate - the voter must be verifiable, their vote must be able to be able to be authenticated after they leave the booth, in the event of a recount and the system can be fully audited. Instead, we have systems with no paper trails, questionable vendor operations, and seemingly contradictory election results.
We can make millions of secure stock sales, bank transfers and on-line purchases daily, and we cannot get a vote counted and auditable? The people who produced these machines should be fired for stupidity and forced to return our money.
Wisconsin was also the state that delegated district boundary duties to a third party, to try and prevent Gerrymandering. I live in Minnesota, and I can say with some certainty that there must be somethhing up here that makes us slightly saner than the rest of the country. And I'm glad.
So when will we begin seeing extensions for our voting machines?
If this signature is witty enough, maybe somebody will like me.
Couldn't they do what many organizations do when implementing a new system and run them both in parallel until they're sure the new system is working as it's supposed to?
I mean since this thing generates a verifiable paper ballot... then have humans count the ballots for a few elections and see if it matches the computer generated total... if they do match (or come really close... like within 0.001% or something) then you have verified that the system is working and that you can trust it for further elections without requiring a human count.
I don't believe they should trust the system totally right out of the box... and with a human count for the first few elections it'll help transition in the technology and allow people to become comfortable with it. You may still want to do random human counts on various ridings to see if the computer is still producing accurate results after the full human count phase. But reducing the human portion of an election helps to produce more accurate and efficient results. (And ultimately the costs required to hold each election...)
From TFB:
5.91 (19) The coding for the software that is used to operate the system on election day and to tally the votes cast is publicly accessible and may be used to independently verify the accuracy and reliability of the operating and tallying procedures to be employed at any election.
This is somewhat less than what is usually meant by the term "Open Source". But it seems that at least voting machines running a completely closed operating systems are ruled out.
OS Reviews: Free and Open Source Software
"""How do you recount? Election results must be reproduceable by a human afterwards, especially if a virus or spyware got into the election results (either on purpose, or with malicious intent). Open Voting has this part figured out by producing a paper ballot that can be validated without the use of a computer, or you can use a computer to check it faster."""
v ote-hacking-2004.html
a me=FAQ&myfaq=yes&id_cat=11&categories=Security%2C+ Resiliency%2C+Integrity%2C+Reliability
...all in all it seems like a pretty good system and like I said they've done a lot of thinking about it.
http://www.robertames.com/blog.cgi/entries/links/
Links have broken with time, but here's an updated link to Open Voting...
http://www.openvotingconsortium.org/modules.php?n
Their systems are reallly neat and they've had a lot of smart people looking at the problem. I've not been involved in it, but have read some of their documentations, and promised myself that I'd speak up and give them google-juice anytime voting came up. Some highlights:
- Commodity hardware / software
- Open source code
- Paper "receipts" that can be verified by:
* Sight
* Barcode
* Audio / Visual
* Separate "reader / recounter"
- Accurate computer counts (ie: select count(*) from votes group by person)
- Paper trail for recounts (re-count manually or computer assisted the receipts), with useful information hidden in the water-marked receipts (kindof like scantron stuff, where both computers and humans can read it).
--Robert
SO . . . say I'm a sysadmin living in Florida and related to Dubya . . . d'ya suppose I could just noodle the count a teensy bit . . . no? How 'bout losing some of those packets, especially the ones with dangling or pregnant electrons? No? What are you, a damned democrat or something?
Sorry folks, you can't get rid of corruption that way; you can only make it pick up and move somewhere else (read: some other element of the electoral process). Build a better mousetrap and nature keeps answering with better mice.
George Bush did <blink>not</blink> steal the last election! As long as nobody looks, it's okay, right? After all, we had a "paper trail" from that election, but we still couldn't figure out what actually happened. The courts wisely held that collapsing the wave function was unconstitutional.
We're all adults here - I don't need <SARCASM> tags, right?
I thought they just gave the job to whoever the Democrat is.
Should be interesting to track the change, though. I have relatives in Wisconsin that are very set on voting, but are not computer friendly at all. Getting them to make the change should be entertaining. There comfort level is based on the old system, and any change about something they view as important as voting will make them very nervous. But, they are in small enough of an area to where they will probably be using paper for quite a while longer.
Although that would work on incredibly stupid voters, simple intimidation usually works on them anyway.
Voters with half a brain cell copy, forge or borrow a receipt to show to the boss.
There's no voter name on the receipt, thus no way for the boss to know how YOU voted.
(why is it that this stuff always seems easy to us slashdotians? Why do corporations always make it so complicated and broken??)
Cause if you make a product that works right, the first time (and every time) you get no new business.
To put in another way: job security.
-Valiss
> Wisconsin Governor Jim Doyle today signed legislation that "will
> require the software of touch-screen voting machines used in
> elections to be open-source."
The law does not require that the software be Open Source. It merely requires that voters be able to examine and test it.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
If you aren't from Wisconsin, write your state legislature and demand the same for you!
postmodernsideshow.com
Heheh, I just love slashdot... my little fortune cookie for the hour is:
:)
"Don't Vote -- it only encourages them!"
How fitting
so much of business, politics, heck even interpersonal relationships revolves aorund the issue of transparency
keeping secrets breeds mistrust, transparency breeds trust
and only after trust is established can prosperity grow- concrete prosperity as in $, or abstract prosperity as in political fidelity and integrity and legitimacy
transparency, transparency, transparency
much of the history of every single country's march towards progress can simply be summed up in the trend towards greater openness... or lack thereof, and the inevitable intellectual, capital, and political poverty from the resulting distrust
it really is a concept everyone should accept and extend
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
The problem here is that there are no open source voting machines on the market at this time. So what is going to happen?
In most cases they can't be since the OS is closed source. Moreover, federal certification is no longer just for stand alone voting machines but requires the whole "system" of vote counting and vote merging software to be certified. So even when the vote counters could be open source the vote databases may not be. Diebolds run on windows CE, ES&S ivotronics probably run on windows CE, ES&S opscans run on Qnix, sequoia touchscreen kiosks run on some undisclosed proprietary software and the ballot database software runs on windows. No word what Sequoia Optek/insights run on but again the ballot data bases run on windows.
thus these companies can't open their source since it's not theirs to open.
Accupol is built on linux and java so it could in principle be open source at their discretion. But because the accupols are cobbled together from mainly commodity components the company investors is averse to open sourcing their only real IP.
Not sure about avante and harte and unilect but it appears they contain windows software.
OVC is the only system truly designed with open source in mind. But it's not ready for sale yet.
Some drink at the fountain of knowledge. Others just gargle.
If you are keeping a copy of your ballot, you could be asked by your boss to show him that you voted the proper way.
Or you could get your bottle of booze from the precinct captain for voting the proper way.
You should only be able to look at the printout, before depositing it in a lockbox for later recount.
Uhm... usually, an individual vote is not contested-- it's the aggregate vote that is contested. So, this process would only work if you could get everyone who voted to release their vote.
The *only* way to do this is with a paper trail. Use electronic voting to generate the paper, and give instant results. If the vote is contested, count the paper ballots, just as we do now.
I see no other acceptable solution; anything beyond this is excessively complex, anything less is intrinisically untrustworthy.
Microsoft is to software what Budweiser is to beer.
I would expect this is only a ploy to make it seem like he cares about the voting irregularities which occurred in WI during the 2004 Presidental election, causing several leading Milwaukee Democrats to be investigated.
Reading the requirements, not only does no one currently offer such a machine, but most machines in the state wouldn't live up to it today.
That's great that their system will be open source, but that isn't quite enough. There are a few things that I think would make the systems more trustworthy in addition to the open source requirement:
new legislation requires that all electronic voting machines be outfitted with open-source artificial intelligence engines that will examine the positions of the various candidates and compare them to the fundamental ideals of the government. The machines will assign scores to each candidate/issue and select the highest in each choice, thereby eliminating any burden the voting process has on the voter.
In a pilot trial of this technology last November, however, it seems that all electronic voting machines segfaulted since no candidate received a positive score.
Why, why WHY? Why must the government/media always raise the specter of terrorism and "national security," even when it's clearly only peripherally related?
Come on, let's be honest. This legislation for a mandatory switch to digital has always been about money. The switch to digital allows the media companies to use all sorts of nifty DRM, like broadcast flags, to prevent unauthorized copying. A lot of people stand to make a whole hell of a lot of money from this, and the average consumer has a lot to lose (obsolete TVs, VCRs, DVRs, etc).
It's about MONEY, for chrissake. So let's NOT talk about terrorism here. Let's NOT invoke the name of September Eleventh when talking about digital TV.
Sure, ONE side effect of this legistlation is that we'll have more free radio spectrum, which emergency responders MAY eventually utilize, which MAY help in emergency situations. But the fact that this is a POSSIBILITY does NOT necessitate linking digital TV with "protection from terrorism!" Unfortunately, the ads being run and the articles being written are doing just that.
Writerati
> Commodity hardware
Bad idea. Closed-source firmware, excessive complexity, poor reliability. Voting machines need to be simple special-purpose machines with all design details (not just source code) public.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
See subject.
I am scientifically inaccurate.
Is there a non-profit out there that has produced an open-source voting machine? Either software that converts a regular PC into a voting machine, or maybe even take it a step further and is willing to build the hardware and sell it at cost to governments.
I don't see any sign that this bill requires the code to be open source. The bill requires it to be made public, but does it actually require the state to make it available under an open source licence?
The WIS quote only says that "the coding for the software that is used to operate the system on election day and to tally the votes cast is publicly accessible and may be used to independently verify the accuracy and reliability of the operating and tallying procedures to be employed at any election". For them to call this open source is bad enough, but for Slashdot to repeat this misunderstanding of the term is ridiculous.
The world has changed and we all have become metal men.
The most important feature to prevent tampering is for voters to be able to verify that their votes have not been modified AFTER all of the votes are pooled. There should be a final, public consolidated database that anyone should be able to tally to get the vote counts, and for which any indivual voter should be able to verify that their votes have not been modified.
Ideally, there would be multiple independent HTTP inquiry servers so regular voters could go home and enter their voting hash over and verify thet their actual vote is in the final pool.
The hard part is coming up with a way that the tallied vote database can be public and able to verify a voter's hash, but still prevent people from being able to determine which votes belong to which voter.
The voter visually verifies the printed ballot, then drops it in the box. The computer results can be used as early count results for the media, but the real vote is in the box. In the event of a recount, it's the box that gets counted. And there are random checks made between box counts and computer counts, regardless of calls for recounts.
This also addresses the vote coercion objections that people have voiced in this thread.
- First they ignore you, then they laugh at you, then ???, then profit.
Based on suggestions I've read in the comments, how about this:
Voter enters polling place, name scratched off list as usual. Voter enters booth. For each office up for election, voter types* a name or names+ into the voting machine. A blank vote or "Nobody" would indicate no vote for that office. Referendums etc. could be indicated with some predefined response (preferably more than a simple "yes" or "no" in order to avoid Windows-dialog-box-style confusion). When finished, the voting machine prints out the completed ballot. The format is importantly both human readable and machine readable via OCR. Surely if the machine knows the font beforehand, OCR can be fairly quick and highly accurate...? A ballot would essentialy be a list like:
A ballot may contain special marks to help a machine reader align the text, but the actual vote info must be human readable (i.e. not a barcode). The voter reviews the ballot and either destroys it and creates a new one, or submits it to the ballot box. Ballots are then machine tallied after all ballots are collected (it is important to not tally instaneously for the sake of voter anonymity). Hand recounts may be conducted as necesarry.
The good parts about this are 1) machine countable, 2) human countable, 3) transparent (voter puts physical paper ballot into box rather than bits into a database), 4) tamper resistant (difficult to invalidate votes by marking or tampering with the ballot after the fact) 5) anonymous.
One problem is: how to type a candidate's name. Keyboard? What about those with disabilities? I'm not really familiar with alternate text entry systems, but surely some exist.
* The biggest problem is, of course, determining who is meant by "John P. Doe", since there may be many John P. Does in America. I don't really like the idea of requiring people to "get on the ballot" because anyone who doesn't know who to vote for will almost certainly pick a candidate who is on the ballot. But I don't really have a solution for an all-write-in system. Please address this as a separate issue. In lieu of requiring a typed name, the system could easily offer a selection of candidates as is common now. (How do write-in votes work now? I assume they are silently ignored unless it's clear that a majority of votes are not for someone on the ballot which almost surely never happens).
+ Some offices may allow multiple candidates. Some voting systems may allow multiple votes, possibly ranked, for a single final winner. This voting method lends itself well to these alternative (surperior IMO) methods.
Discuss.
Counting ballots is exactly the kind of thing that scales nicely - just hire more counters. O(lg n) maybe, but then there's still no reason that in the US we couldn't simply wait 24 hours for nice handcounted results, except for our obsession with real time nownownow results.
Say this with me: Instant Runoff is flawed, use Condorcet instead; Instant Runoff is flawed, use Condorcet instead; Instant Runoff is flawed, use Condorcet instead. IRV has serious problems which are easily found with a simple Google search. Condorcet is no harder to use than IRV, doesn't yield bizarre unintuitive results like IRV, and removes incentives to vote dishonestly.
Constitutionally Correct
I ask this because its not like you could just look at the binary and tell that it was the same program as the source.
Are there going to be people who will read the entire source, then sit there and watch it compile, then installed, followed by watching the machines every moment from there until voting is completed?
DEAD DEAD DEAD DELETE ME
...whose senator actually voted against the Patriot Act.
North Carolina law states that the voting machine code must be available to (at least) the state. North Carolina certified 3 companies for e-voting in the state. None of the 3 provided any source code.
I'm sure this will be the same.
End of lesson. You may press the button.
Paper ballots.
Counted by hand, in public, in a goldfish bowl.
Representatives of both parties watching the counter.
After the tally is done, rotate the ballot stacks to different counting tables, and recount.
Check the tallies.
If they don't match, investigate the table counts. Redo.
If they match, all three, interested parties and counter, move to the head table. Enter tally, in plain view, on a master list.
After the tallies are totalled for the site, the totals are phoned in.
The paper ballots, labeled with approporate tags, are placed in containers with one-time-only interior latches. Close latch. To recount, you must cut the box apart with power tools. No PICKABLE LOCKS.
Ballot boxes are labeled and stored -- forever.
If these steps are followed, the vote count is impeccable, 100% accurate, and 100% verifiable (cut open the boxes, recount as necessary, reseal into new boxes).
And it would only take 3-6 hours. do the math.
Canada does something like this, and they have no problems. Using Occam's Razor, the only reason you'd want to use something as laughably alterable as a computer system is to alter the totals. Everything else is sophistry.
I think everyone's vote should be posted on a big website, using a special identification number. That way, anyone can check if their ballots were correct, anyone can access the raw data, and there's still anonymity.
"That which does not kill us makes us stranger." -Trevor Goodchild
Sorry folks. As someone who knows Wisconsin state IT (and posting anonymously). The voter registration server and apps (SVRS) are CITRIX based. And the papers are already publishing complaints about that application. It is failing to poor project management by state workers with a history of poor project management. The state CIO is a linux advocate (Matt M.), but even he had to bow to pressure for a high profile project and go with HP UX. And our efforts to get rid of MS Exchange had been fairly difficult, and may yet hit the papers. (Even the governor's office hasn't attempted the email conversion despite Larry Ellison's visit...Oracle is trying to help replace MS). The governor can sign anything he wants in to law, but how will it be implemented? And how will the municipalities feel about further requirements to get voters registered and voting, when SVRS works so poorly? It sounds like the average Wisconsin citizen is not going to be very happy with what the state government dictates. From my point of view, too many state IT management folk are jumping on the open source bandwagon because of the CIO, rather than practising good IT. Sounds like the governor signed into law a feel good law without thinking about the consequences. Do I have the answers? Nope, just know this will be a great idea, poorly implemented.
I agree. Please don't mod the GP as funny.
Anything but not funny.
There's a hidden treasure in Python 3.x: __prepare__()
They tried that with the holy ark of the covenant - and it still ended up in Cheney's hands.
... and then they built the supercollider.
Hmmm... am I the only one that thinks that with the prinitng requirement we are actually moving towards very expensive ballot printing? I mean, in the case of a recount they would count by hand anyway in most cases. Where exactly is the big improvement? This is becoming just as bogus as the 'paperless office' craze of the 90's.
Or am I just cynical?
Somebody, probably not me or you will compile the final code to be run on some computer that we don't know the details of anyway. That somebody may know how to alter the code, maybe not.
What's wrong with an interpreted language? PERL? Python? If the code can be edited, presumably a binary can be swapped just as easily. At least that way you know that the code on the machine is what the machine is running (unless someone is fooling with the compilers / interpreters themselves).
In Australia, we manage to get the results of most of our lower house seats counted on the evening of the election at least as quickly as the US did at the last presidential election.
Transparency is maintained through both neutral and partisan observers from all interested parties verifying the count as it happens. I participated (for a political party) at the last Australian federal election and I can tell you that if any votes were under or over counted in an electorate of maybe 30,000 it would have been in the order of 10 or fewer. Whenever a vote is in doubt it is put in a separate pile which is then debated by members of the interested parties and ultimately decided upon by a neutral scrutineer.
The only downside is that many votes are incorrectly cast on a paper ballot - as high as 1-3% - which is technically impossible on an electronic ballot. Unless you vote for Bush. *ducks*
Read Pynchon.
The existence of preference cycles in condorcet results is a pretty serious problem.
In theory, or in practice?
Can you imagine TV news explaining to the average American how the set theory behind the Schwartz set method determines the President?
Can you imagine TV news explaining the electoral kindergarten? But it manages to do so, and TV news is overrated anyway given that all major TV news networks are controlled by an MPAA member (ABC->Disney; NBC->Universal; CNN->Warner Bros.; Fox News-> 20th C Fox) except for CBS News which separated from Paramount Pictures less than a week ago.
That said, I highly recommend approval voting. The voter gives a thumbs-up or thumbs-down to each candidate, and the candidate that gets the most thumbs-up wins. Behind the scenes, it is a special case of Condorcet voting where the voter divides candidates into two groups: one tied for most preferred, and one tied for least preferred. Approval is much easier to count than IRV because unlike IRV, approval is summable. It's also trivial to implement on voting machines designed for plurality, as the operator needs only to remove the protection against an overvote.
The hard part is coming up with a way that the tallied vote database can be public and able to verify a voter's hash, but still prevent people from being able to determine which votes belong to which voter.
Actually, it's impossible. If there's a way for the voter to verify their vote once they leave the polling place, others can as well.
What we really want is the voter to finish voting confident that their vote has been counted, yet without any way to prove that to themselves or others once they leave the polling place.
"Those who cast the votes decide nothing; those who count the votes decide everything." - Joseph Stalin
map{$c{$_}++}and print'winner:'.(sort{$c{$a}<=>$c{$b}}keys %c)[-1];
:-)
Anyone for Perl golf?
Zen tips: Pay attention. Don't take it personally. Believe nothing.
As we've seen, it just takes one state to swing things. This is a good step but will not save anything unless it also takes place in GOP strongholds like Ohio and Florida (strongholds in terms of who is in charge of counting the votes, not by percentage of Republican voters).
verifiable as well.
It's great that Wisconsin has the love of liberty
and democracy so great that they make this change,
but what if they are the only one?
We need to have every, or as many as possible,
states state that they will not recognize the
results of any election that has non-open source
code, or whatever, otherwise to throw an election
only certain states need be targetted for attention.
Say Florida, Ohio for example.
Why do you need software?
The voting device: buttons for the candidates and a chip with lots of fuses (mechanicaly once-programmable registers). Doesn't matter how you count the votes upstream, they can allways be verified (recounted) from the voting-machine. It's so simple it could be done the good old hardware-way, without firmware, thus tamper-proof and with open-to-the-public schematics. Silicon is not so easy to check for malicious circuitry, but it's even harder to change it once it's approved.
The only connections to the outside (non-sealed enviroment) would be the read-only connection upstream and the buttons representing the candidates.
You could have enough fuses in the machine to last, say 100 elections (100 * voters passing through one voting-boot/election).
In Nevada, among other security measures, the state has a copies of the code used in all slot machines and audits machines to make sure they haven't been modified from the reference versions. Gamblers can request an immediate investigation of any machine they believe may have cheated them. After all, money is at stake. It would be nice to have at least the same level of security for our vote.
t /2004-06-13%20NYT%20Gambling%20on%20Voting.pdf (PDF)h tml (registration required)
Links to NY Times article "MAKING VOTES COUNT - Gambling on Voting",
contrasting slot machine and voting machine security
http://theory.lcs.mit.edu/~rivest/voting/press/ny
http://www.ejfi.org/Voting/Voting-31.htm (no registration required)
http://www.nytimes.com/2004/06/13/opinion/13SUN1.
Basicly, you go up to the computer and fill it all in.
The computer then prints out a ballot containing a human readable vote and a machine readable barcode.
Then, the ballot (assuming the voter aggrees with it) puts it into a sealed ballot box. To count the votes, the barcodes can be run through a barcode scanner. If necessary, a hand count could be performed. This could be done either with or without a direct count made by the poling station computer.
Another option would be to just do what we have in australia and use a paper ballot where you mark the boxes for the people you want (in our case, you indicate who you wnat to put as first preference, second preference etc etc)
Simple and no chance that the computer got it wrong.
SCALE 4x will be holding a workshop on open-source in government.
You give me paper, I'll give you your "Voting Brick(tm)". The point is that with paper (or caged gophers carving your votes into planks of wood), any recounts are very trustable and the security of physical items is a well-understood problem.
...somehow that doesn't give me the same warm-fuzzy. :^)
The point being that with any human-understandable, physical token serving as the official voting record, then the system(s) used to collect it are immaterial. Slap a hacked, virus-riddled, internet connected consumer PC into the voting booth and make me vote on it... if I get a paper receipt that I can read and understand and give that back to the election officials to serve as the vote of record, I'm OK with it. But give me a "Voting Brick(tm)" that says: "Your vote was cast. Click OK to continue."
--Robert
This is /. and most of the people here are technically competent and of at least average intelligence. Many of them cannot spell their way out of a paper bag. What makes you think the general populace can spell? How do you decide what a voter MEANT if they misspell a name? Further, what if they are physically incapable of typing?
Making every vote a write-in has serious issues, which is why it hasn't been done. I fully believe that write-ins should be allowed for every office, but it should not be mandatory to write in every name. If every office allowed write-ins, we wouldn't even need "none of the above" on ballots -- just encourage people to vote for THEMSELVES if they don't like any of the candidates on the ballot. Then you have millions of people getting one vote apiece, and the point has been made.
Mal-2
How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
The article -- and its bit about the bill requiring the source to be disclosed to citizens -- refers to the bill as introduced. On November 3rd, the committee gutted the disclosed source requirement. On November 10th, the new version of the bill was in place and THAT was what was passed.
p df
Legislative history of AB627: http://www.legis.state.wi.us/2005/data/AB-627hst.
^ New headline should read.
I don't think any of these "open-source" machines are going to solve anything. I'm just proud the machines won't be Diebold. After all, corruption comes from those manning the machines, not the machines themselves.
I have lived and voted in several districts in Wisconsin. The system that is in place now in most Municipalities is a scantron like form. You complete the arrow pointing toward the person, referendum, or party you're voting for.
When you complete the ballot you put it into a counter, that will reject the ballad if it is unreadable, over voted, or under voted. It prints out the record for a real time tally internally, and I'm certain it is able to run a report, and you have to go through the ballots anyway for write in candidates. Easy, Fast, tamper resistant, verifiable.
Why do we need to change the system in Wisconsin? Because we can and it is another great way to spend money on it now, rather than, uhm, making silly deals with Indian Gaming.