Message from @Maw
Discord ID: 779734558182211586
But as you can see, in Dallas, there were more inconsistencies then San Antonio
It led them to believe that something suspicious was going on.
So this is what they did. They took the entire log, and they start tabulating the votes themselves based on that. They would flag any transaction that didn't make sense. The table above displays their results.
These machines' source code has been reviewed numerous times.
Notice that the "Votes exceed ballots" is flagged 1027 times.
@Maw It's more complicated than that. There are multiple companies, multiple patches that can be executed.
It's not just one simple image that's baked into the machine
I mean, saying it's insecure is a lot different to saying it's intentionally set up to swap votes.
This is just the beginning of the video, lol
This is what made them suspect of the software
Lots of these errors can also be caused by people improperly setting up machines.
And a number of other issues.
While running their software, 1027 TIMES, not votes, times, they flagged an error where the votes exceeded their running tally of ballots
no, it's the log
... yes, I am aware.
Once your iterator is out of balance, it repeats this same message.
Every time you feed a ballot.
it's not a single vote, they were taking data from precincts
Simply having it be unequal is enough to trigger this error.
They also found that 96 times, someone overwrote the data with USB sticks that didn't match the previous data
And it could easily be that any vote on this machine that was processed after the imbalance, was saying it's imbalanced still.
As that tends to be how iterations are set up.
Here is my beef with this. I can take Floyds autopsy report and in laymans language thoroughly explain why it was not murder. In a manner most people will clearly be able to understand, and how they could check to see if my claim was correct. I am waiting for this with the voter fraud, and all I am getting is massive amounts of smoke.
Texas is welcome to not like any mechanism they please for any reason. We can only hope that other states thought of vetting such things. Maybe they did and found it sufficient.
After their analysis, Russell's firm started to research. here are prior reports that also reported on voting machine vulnerabilities.
Everest Report - https://www.cise.ufl.edu/~butler/pubs/everest.pdf
C-Span Panel: ICIT - https://www.c-span.org/video/?417203-1/discussion-focuses-cybersecurity-us-voting-systems
Matt Blaze Testimony before US House Committee https://cs.georgetown.edu/news-story/matt-blaze-testifies-on-the-capitol-hill/
ES&S Security Test Report (2017) - https://votingsystems.cdn.sos.ca.gov/vendors/ess/evs5210/ess5210-sec.pdf
I just wish someone knew about this and made the argument *before* the election results made it convenient. We do have people for that; people in power with a stake in it who were either powerless or asleep at the wheel.
The Everest Report is dated 12/7/2007
Asleep at the wheel or powerless to do anything about it?
@NoobDad, you just advanced to level 6!
Kinda weird how 2016 went tho, no?
@Maw if you watch the video, they were counting batches of votes in the logs, it wasn't a single error from one ballot, the numbers submitted exceeded the number of ballots they recorded. So if I had 20 results for 20 ballots, then on next batch I would submit 50 results but only submitted 10 new ballots
President, House and Senate. Seems like the glitch dropped the ball.
But I'm assuming the ballots were calculated separately from the ballot results, regardless, I don't have the exact details on how they conducted the log analysis
@Zuluzeit But he didn't, he signed the executive order in preparation for this.
Hahahaha yeah we didn't see that coming. Seems like It would have been a better idea to expose and fix. I do understand he was busy. Priorities.
He sat on his hands for 4 years after the 4 years from when he initially knew. 3d chess.