Hacker News new | ask | show | jobs
by nobodyorother 3233 days ago
pvote.org seems like a decent solution, it's <500 lines of code that needs to be audited.

That doesn't handle auditing the machines themselves, but as the 2016 US presidential election recount found in Wisconsin, the tamper-evident machines showed evidence of tampering, so maybe we're closer to knowing whether the trusted systems we use to count votes are trustworthy.

Of course, the current machines are still Diebold ("Premier Election Solutions"), so who knows. Ken Blackwell will make sure only the right folks vote, anyway, just like he did in 2008.

1 comments

> pvote.org seems like a decent solution, it's <500 lines of code that needs to be audited.

Quoting from the website:

"Pvote is small. The current version is 460 lines of Python. It uses Pygame for graphics and audio."

So, add to that 130000 lines of pygame, 1.5 million lines of cpython, 14 million lines for gcc, 20 million for the linux kernel, ... and you haven't even begun to list all the stuff you would need to audit?