This story from the American Thinker offers in interesting supposition on how bad actors have corrupted our elections in some jurisdictions… It’s well worth the read.
It explains how you get ballot counting numbers that look like this graphed out.
Here’s a teaser… From the American Thinker.
By Jay Valentine
Database latency — a geeky term, but that’s how they did it!
A policeman pulls over a speeder. The police computer reports that three hours ago a similar vehicle and person held up a liquor store — so the police are on alert.
No database latency.
County election managers change the zip code of 31,000 voters on September 3. Ballots go out that week. Those 31,000 are undeliverable. Someone collects those valid ballots. On September 15th, those addresses are quietly changed back.
National Change of Address Database (NCOA) will not pick up those address changes. They didn’t happen because there is no history.
The 31,000 citizens were getting their mail just fine — except for ballots. Ballot addresses were driven by the county mail-in ballot database — the one that was changed, then changed back.
Many states send ballots to everyone; the recipient is none the wiser that they never received a mail-in ballot. They may vote in person. Oops! “You already voted!” Ever heard that?
Welcome to database latency.
Our bad guy pals know they can change voter rolls, take an action, then change them back. Who would know?
A thousand voters are changed from inactive, voted, then changed back, and how would you ever know? With lots of complex footwork, you could eventually tell from their voter history file — months after the election.
And while the Dems are ballot “harvesting,” Republicans are busy playing “pick up sticks.”
Watch the George Senate run-off race.
Floating ballots are the lifeblood Democrats need to win — and win they do.
Ballot gatherers know Republicans use dumb technology — relational databases, SQL, NCOA, Melissa, all non-real time, highly latent systems.
Bad guys are happy to watch Republicans waste time finding ones and twos, while the real action takes place by the thousands — invisible to these batch, latency-prone systems.