Bang goes the gavel at SCOTUS! Edit: all numbers were from PA SOS webpage. They pulled down the 2.5 million count last night, but the 1.8 was confirmed in the hearing as not changing.
Comments (553)
sorted by:
Bang goes the gavel at SCOTUS! Edit: all numbers were from PA SOS webpage. They pulled down the 2.5 million count last night, but the 1.8 was confirmed in the hearing as not changing.
700,000 extra illegal last minute ballots for one candidate that were never mailed out in the first place are neither glitch nor mistake.
They are high treason.
We don’t us the term glitch at the company I work at.
There is no glitch - fuckery is by design. Plus, something this important would have multiple sprints dedicated specifically to bug hunting and scrubbing.
Treason. That’s what it is.
That’s one huge detail here that even I didn’t have at the front of my mind at first until sometime else said it.
If your program can’t count numbers properly:
You were drunk while working
You maliciously modified the program
You’re so incompetent that you shouldn’t work in the industry
Computers ( to my knowledge ) cannot unintentionally mimic human error in the results that they output. A program error would likely look like not being able to show results for 50+ separate write-in candidates because they didn’t leave room in the storage variable or variables for more than say 30 different candidates. With my very limited experience and learning on coding I can hardly conceive how you might fuck up a tabulation program in a way that gets by bug testing. Especially for a program being used for voting purposes!
If any programmers would like to correct me, please do.
As a programmer, the optical reader can cause issues if the signal is noisy, and if they mix signed and unsigned numbers, or add floats of low precision, but if that is the case you're back to option 3.