I am a software guy; it's what I do for a living. I don't work with election systems, though. What Silicon Greybeard is describing here is... mostly correct, but doesn't quite tell the whole story. I'm going to try to fill in the gaps.
What he's describing is the most basic level of "glitch", something that happens in a hardware failure or a very basic programming failure. Maybe memory is corrupted, network packets get lost, an electrical surge. Those issues can happen, but they are relatively rare in modern computer systems and applications.
We agree that that's almost certainly not what we are seeing in this case. The computer itself almost certainly did not screw this up.
That leaves us with two possibilities: malfeasance or innocent human error.
I believe malfeasance is a serious possibility, but we don't YET have enough detail to eliminate innocent human error. Suppose for example that the voting software in question has human input in how ballots are generated. (It HAS to have some degree of human input, of course, but how much and how exactly it works is unknown). Could a human accidentally transpose identifiers for Biden or Trump so ballots cast for one go to the other? Yes, it could be done, and depending on how the software works, it might not be obvious. Database software often uses random identifiers for cases like this, eg:
45989832458: Biden 32498398983: Trump
That prevents issues that could arise from two people named Biden or two people named Trump, but does make it hard to spot if they get transposed. The transposition could be deliberate and it could also be accidental.
If it only shows up in one precinct, gets corrected, and never shows up again... fine.
If it shows up twice or more... that's malfeasance.
This entry was published Fri Nov 13 14:14:48 CST 2020 by TriggerFinger
and last updated 2020-11-13 14:14:48.0.