[copaliscrossing]

I not only vote in person, I drop it into the paper scanner and see the number of scanned ballots tick up by 1.

Now whether or not the vote count software after that does some fuzzy math, I dunno.

The "fuzzy math" is my real problem. As a software developer, I know how easy it is to time/date trigger software to behave differently depending on the time and date. I could write software in my sleep that would kick out or mis-count a (R) vote ONLY on election day or a subset of hours during election day BUT behave correctly during controlled audit runs before the election or after the election. Easy to do and untraceable with access to the source code OR a hand recount of the actual ballots (not the totals from the machines). Of course, the manufacturers of the machines won't let any look at the source code...Proprietary. You could also time/date trigger the vote weighting (1.3 for them, .7 for the other guy). So many nefarious things can go on inside the coding.

That's why I won't trust another election until the source code is verified by both parties and independent software analysts and the verified object code is checksummed with the ability for independent voting machine watchers to verify the checksum ANY time during the vote tabulations to ensure the object code checksum has not changed (think remote access). Hard core. Yes. Necessary. Also Yes.

[copaliscrossing]

Should have said “without access to the source code”...oops!

[Tell It Right]

I’m a programmer too (software engineer by title, but that honestly means I’ve got tons of age and experience really). My #1 concern with the Dominion software is the FRS some of the states signed specifically saying things like the software allows the administrators to salt the counts (i.e. multiply Trump’s votes by 0.7 and Biden’s votes by 1.2 if they wanted to).