Im willing to bet the real reason there is inconsistencies is that the app used an home-brewed noSQL back end with week to no protections against duplicate entries and no real data validation despite the use of smartphones, which tend to increase data entry errors over full keyboard devices.
It's likely that you have the same precient reporting in using both the app and the phone system and entries where someone is missing an zero or mistypes a 9 instead of an 8 somewhere, causing the votes cast to differ from voters present in some precients.
Now with an well designed sql schema detecting and eventually correcting this kind of data quality issues are straightforward but as this is the work of an small relatively new digital marketing agency with almost no record outside of working for the party machinery so whats the odds that this app is backed by an well designed transactional database framework rather then a quickly cobbled together nosql schema.
To make it worse this is an case where the democratic party could have demonstrated an commitment to more transparency and less centralization as there is no secrets that needs protecting and yet the Iowa democrats went down the opposite road of more centralization and less transparency in an move that's just showcasing everything that is wrong with america's political establishment.
The open democratic way to run an election like this would be for the individual districts to publish their results for 3rd party validation directly to the public when they are done caucusing instead of placing them in escrow until the incompetents at the party HQ is done calculating the way it seems to happen now.
As of now the app is likely destined for a complete rewrite with the actual tally being done the old fashioned way using calculators and spreadsheets so an DHS code-audit would just make the issue resurface at an inconvenient time when this is no longer news, as im pretty sure anyone with a clue about IT inside of the party machine knows exactly how they screwed up and prefers strange conspiracy theories to being exposed as mundane fools.
It's likely that you have the same precient reporting in using both the app and the phone system and entries where someone is missing an zero or mistypes a 9 instead of an 8 somewhere, causing the votes cast to differ from voters present in some precients.
Now with an well designed sql schema detecting and eventually correcting this kind of data quality issues are straightforward but as this is the work of an small relatively new digital marketing agency with almost no record outside of working for the party machinery so whats the odds that this app is backed by an well designed transactional database framework rather then a quickly cobbled together nosql schema.
To make it worse this is an case where the democratic party could have demonstrated an commitment to more transparency and less centralization as there is no secrets that needs protecting and yet the Iowa democrats went down the opposite road of more centralization and less transparency in an move that's just showcasing everything that is wrong with america's political establishment.
The open democratic way to run an election like this would be for the individual districts to publish their results for 3rd party validation directly to the public when they are done caucusing instead of placing them in escrow until the incompetents at the party HQ is done calculating the way it seems to happen now.
As of now the app is likely destined for a complete rewrite with the actual tally being done the old fashioned way using calculators and spreadsheets so an DHS code-audit would just make the issue resurface at an inconvenient time when this is no longer news, as im pretty sure anyone with a clue about IT inside of the party machine knows exactly how they screwed up and prefers strange conspiracy theories to being exposed as mundane fools.