What does /g/ make of this?
https://youtu.be/Fob-AGgZn44
From what I can tell, it seems they're claiming that the software is built in such a way that you can, using fractions (because they're not simple Int even though there's no reason why they shouldn't be), change the weights of individual votes. So for example those who voted for Sanders only count 0.5 or something while those who voted for Clinton count 0.9 (which rounded off are both 1). The decimals which result in the report and such can be optionally hidden, thus obscuring the fraud. Supposedly all of this is built into the voting software and has been exposed in this video.
Something tells me none of this would be possible if the voting software was Open Source.
The entire "weighted race" option was introduced into GEMS because of a special race in Sacramento, not for election fraud. Read the email between the software developers below:
>Sacramento is holding a mail-in election with some referendum questions. The hitch is that not all voters are counted equally. Each voter is apportioned a value, or weight, for their vote. To make things even more interesting, the rules for assigning weights vary by race. So voter X might be give weight 5 for race A and weight 12 for race B. Too fun. In Sacramento's case, the rules are as follows:
>FOR ALL VOTERS Safety Light votes are accorded a fixed weight of 3.35 per parcel.
>FOR RESIDENTIAL VOTERS weights are fixed at 16.32 per parcel for street lights and 26.98 per parcel for decorative lights.
>FOR COMMERCIAL VOTERS weights are varying and based on a figure of .2702 per front foot for street lights and .4467 per front foot for decorative lights.
>The figures are monetary.
>The solution is to print a barcode on each ballot to identify each voter. The high-speed central count client then scans the barcode and looks up the weight for the voter for each race on the ballot, and passes them on to GEMS. GEMS then adds the weight to the counter table. Weighted races are identified in GEMS with a new race type "Weighted".
>The weights add up pretty quick, and have a lot of significant digits: potentially millions of dollars stored to the penny. GEMS counters, central count server, poster, reporting, manual entry, etc all need modifications to handle large numbers and fractions.
>This is all in the works, and will be part of GEMS 1.18.
>Ken
Source: http://tenaya.physics.lsa.umich.edu/~dwchin/Diebold/diebold/lists/rcr.w3archive/200106/msg00017.html (The same source that Bev pulled the "damning" emails between programmers from)
>>57380258
>special case scenario
>better implement it to the entire system
Seems legit
>>57380258
DRUMPFTARDS BTFO!!!
>>57381197
If you need to implement special cases for specific customers, you usually want to implement them so that they can be applied to the system in general. This makes it significantly easier to maintain the software: instead of maintaining separate branches for each customer, you only need to maintain one.
>>57382107
It also makes it susceptible for abuse, especially when implemented like here as demonstrated.
Why not make a simple module?