2/ This Appeal includes the basis for the Maricopa Malfeasance video that has been viewed over 25M times. The same one @maricopacounty has said were "lies" and would debunk. There's been ZERO debunking:
https://t.co/cbfb2r8tfn
3/ The "Print to Fit" issue- produced over 8,000 unreadable ballots. Scott Jarret knowingly lied and said only three vote centers that produced less than 1,300 unreadable ballots. The P2F ballots required duplication to be read/counted. What happened to the rest?
4/ There's more. The tabulator system logs showed that the database was not of the same domain as the election program and warned of this condition. All 446 tabulators issued the same warnings:
5/ One of the most grave and critical issues found was that the tabulator also warned that the Machine Behavioral Settings (MBS) file was not correct. The MBS file contains the counting rules for the tabulator and can be used to control the outcome of an election:
6. What's even more concerning is that the system was expecting a file from the 5.10 platform, and not the 5.5B platform certified for use in AZ. The only place 5.10 is used is in California- and it isn't certified by the EAC.
7/ There is ONLY ONE MBS version certified by the EAC and the SOS for use in Arizona- and it is listed here in the EAC's 5.5B Scope of Conformance (available on the EAC website):
8/ To note: There are no Engineering Change Orders (ECO) approved by Maricopa County, the State of Arizona, or the EAC to permit such a change. The use of versions other than those tested and certified by the EAC voids the certification:
@BrianTerry180 2/
Right before...
@BrianTerry180 3/
And during:
@TimC_266 @PootDibou @AngryFleas @KariLake 2/
In response to Lake's Rule 60 motion (appealed today) @maricopacounty lied (LIED) and said there was no testing (they didn't know we had video) and county attorney @Rachel1Mitchell didn't knowthat M.C. had provided L&A TESTING records for the dates/tabulators in question.
@TimC_266 @PootDibou @AngryFleas @KariLake @maricopacounty @Rachel1Mitchell 2/
testing was performed was on October 11th. The logs must include the test as the law requires that the test be performed using the same election program as is used for the election- and specifically states "Not a Copy". Second, we have the Logic & Accuracy test
@TimC_266 @PootDibou @AngryFleas @KariLake @maricopacounty @Rachel1Mitchell 3/
checklists for all tabulators and the only ones dated for the 11th are for the 5 tabulators @maricopacounty identified as "Spare". Third, we have the L&A test results which are attached to the fraudulent certification which shows that only scribd.com/document/65243…
@TimC_266 @PootDibou @AngryFleas @KariLake @maricopacounty @Rachel1Mitchell 4/
45 Election Day ballots were counted in the test. M.C. has 4,312 Election Day ballot styles- and therefore did not test the ballot styles or the equipment they were required by law to test.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
@jhalderm@GabrielSterling@MITREcorp@realMikeLindell@MarilynRMarks1 1/
The election software was not "stolen" as it was imaged with the express authorization of those responsible for operating the Coffee EMS server after Gabe and the SoS ignored repeated requests for help. Your characterization is disingenuous, libelous, politically
@jhalderm@GabrielSterling@MITREcorp@realMikeLindell@MarilynRMarks1 2/
motivated and not appropriate from a scientist and election systems expert. Are you claiming that @dominionvoting failed to address the alleged breach that Marilyn Marks knew about for a year before raising it in the Curling v. Raffensperger case? That would mean she
@jhalderm@GabrielSterling@MITREcorp@realMikeLindell@MarilynRMarks1@dominionvoting 3/
would be liable and complicit for concealing such a threat and would mean Dominion is negligent.
Lastly I find it stunning that you have the audacity to lay blame at the feet of those who were only trying to resolve a very real and documented problem and allege
@stephen_richer 1/
Bottom of the barrel? Let's talk about @Rachel1Mitchell's false statements of fact that she filed in the Lake case. Mitchell asserted that the undisclosed testing of October 14-18 (260 tabulators failed) was not a test. Maricopa's records (446 L&A checklists) say otherwise:
@stephen_richer@Rachel1Mitchell 2/ @Rachel1Mitchell also falsely claims that Scott Jarrett's sworn testimony is that L&A testing occurred on October 11th and "...included tabulators use in vote centers"; however, Jarett states that the "Tabulation Programs" were tested- NOT the 446 tabulators the EPM requires:
@stephen_richer@Rachel1Mitchell 3/
The reason that @Rachel1Mitchell falsely claimed the test was not a test is because AZ statute requires an "errorless test" of every tabulator before it is used in an election. The tabulator system logs show that 260 of the 446 tabulators tested on October 14-18th failed
1/ @stephen_richer, I know you've had a long day abusing your power, belittling the common-folk, and overall just putting the ass in class, but I told you that I would be posting this today- so let's get into this. @MaricopaVote has been spreading dis- and misinformation
2/ on their website (fact-check page 🙄). This time they're claiming that the election equipment is tested prior to each election to ensure that the systems are running the correct versions of software/hardware approved by the EAC, and haven't been changed:
Here is the approved version of the Machine Behavioral Settings (MBS) which were approved by the EAC for Dominion Democracy Suite 5.5B, along with the warning /error present on every vote center tabulator system log for the 2022 General Election: