For crying out loud, this is a solved problem! Banks deal with online funds all the time. When was the last time any e-banking solution from a major bank was hacked?

That isn't true. The banks have been "eating losses" caused by electronic theft, and keeping it unpublicized, in order to "maintain the faith of their clients". There have been quite a few stories written on this, typically someone (inside) electronically rips off an account, the victim starts to scream, and the bank just returns the money out of it's profits, and it's written up as a loss of some kind. When the security people finally track down the culprit, they are typically let off, if they promise to keep their mouth's shut.

So the banking system, only appears secure (albeit it is beyond me to hack it), but insiders can have a field day ripping them off. So think what insiders could do to rig elections? Even if they are traced down a year later, it is too late.

The only way is to have an open system, is where there is a paper trail, an audit number for each vote cast, redundant hard drives to store the data,( with them stored and transported separately), and freely inspected source code.

Perl would be perfect for this, because it is alot more understandable than C.

You have to face up to the fact that the people in power "want the ability to fix elections", it's the only way they will be able to control elections as the population of poor and underprivileged grows, to where the fat-cats would be voted down in fair elections. All the BS they put out, on the need for secret source code, is just pulling the wool over the eyes of the sheep.


I'm not really a human, but I play one on earth. flash japh

In reply to Re^2: Larry Wall for President! (or at least voting systems in Perl...) by zentara
in thread Larry Wall for President! (or at least voting systems in Perl...) by radiantmatrix

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.