At 10/29/16 01:23 PM, aviewaskewed wrote:
That actually sounds to me like it's more of a precaution AGAINST hacking or rigging. Because if one machine or program by one company is penetrated, you'd still have to get through another 4 machines and programs to get to the golden ticket of rigging the vote in the whole state.
Nah it just means some machines might be rigged for one candidate while other machines are rigged for another and still others aren't rigged at all.
As for the rigged machines, doesn't matter so much if it's intentional or not (simply a glitch) because the effect is the same. There's really zero excuse for not thoroughly debugging these things before putting them into use so even if it's a bug, at this level I'd hold them fully accountable.
There's a very good reason most software says *not* to be used for -- and then goes on to state pretty much anything besides on a standard computer. The software that runs in things other than standard computers is supposed to be held to a much higher caliber than the rest. That means the software running in medical equipment, vehicles, and yes voting machines, etc...
Honestly if any of those machines are using any version of Windows at all (and it wouldn't surprise me if they are) then IMO that should be cause for throwing them out. They should be entirely custom-built, not relying on consumer-grade OSes, etc...
Because there's no way you can fully account for the stricter accuracy of the software (to the extent required in the stricter testing required of medical equipment, vehicles, specialized machines, etc...) if you're not using a completely custom setup, including a custom OS, if it even has an OS at all.
If any machines are found to be rigged, hold the makers criminally liable, even if they hold it's just a glitch. They're held to a higher standard than most software folks. It's time they face the consequences if they don't uphold their end of the bargain.