More from Law
This issue was repeatedly highlighted bu Judge Totenberg:
Dominion’s system “does not produce a voter-verifiable paper ballot or a paper ballot marked with the voter’s choices in a format readable by the voter because the votes are tabulated solely from the unreadable QR code.”
Judge also found that Dominion's QR codes are NOT encrypted:
“Evidence plainly contradicts any contention that the QR codes or digital signatures are encrypted,”
This was “ultimately conceded by Mr. Cobb and expressly acknowledged later by Dr. Coomer during his testimony.”
Judge Totenberg said there was “demonstrable evidence” that the implementation of Dominion’s systems by Georgia placed voters at an “imminent risk of deprivation of their fundamental right to cast an effective vote,” which she defined as a “vote that is accurately counted.”
Judge Totenberg found that Dominion Systems inherently could not be audited.
She noted that auditors are severely limited and “can only determine whether the BMD printout was tabulated accurately, not whether the election outcome is correct.“
Totenberg stated in her ruling that a BMD printout “is not trustworthy” and the application of an Risk-Limiting audit (RLA) to an election that used BMD printouts “does not yield a true risk-limiting audit.”
Georgia used RLAs to claim no fraud...
Dominion’s system “does not produce a voter-verifiable paper ballot or a paper ballot marked with the voter’s choices in a format readable by the voter because the votes are tabulated solely from the unreadable QR code.”
Witness explaining that on electronic ballots (QR code ballots), it's impossible to determine voter intent. The machine decides the intent, whereas, with paper ballots, a human can double-check the ballot. https://t.co/kkhamio2Je
— The Election Wizard (@Wizard_Predicts) December 30, 2020
Judge also found that Dominion's QR codes are NOT encrypted:
“Evidence plainly contradicts any contention that the QR codes or digital signatures are encrypted,”
This was “ultimately conceded by Mr. Cobb and expressly acknowledged later by Dr. Coomer during his testimony.”
Judge Totenberg said there was “demonstrable evidence” that the implementation of Dominion’s systems by Georgia placed voters at an “imminent risk of deprivation of their fundamental right to cast an effective vote,” which she defined as a “vote that is accurately counted.”
Judge Totenberg found that Dominion Systems inherently could not be audited.
She noted that auditors are severely limited and “can only determine whether the BMD printout was tabulated accurately, not whether the election outcome is correct.“
Totenberg stated in her ruling that a BMD printout “is not trustworthy” and the application of an Risk-Limiting audit (RLA) to an election that used BMD printouts “does not yield a true risk-limiting audit.”
Georgia used RLAs to claim no fraud...
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.