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.
What are you going to do about it? Reverse the election?
The new, and current “ballot gathering strategy” mandated by the almost universal mail-in ballots adds pretty cool database games — exploiting database latency.
Database latency, as you likely gathered, is when current reality lags the underlying record. We all experience it in our electronics-driven society.
The ballot gathering scammers know about latency — it’s their ground game!
To Republicans, election engineering is civics. To Democrats, it’s business — and they are great at it!
They know the Republicans have hundreds of diligent election sleuths working in basements and dining room tables checking voter rolls for the dead and the fakes.
They know those people rely on NCOA and Melissa and other highly latent services as their baseline. If someone moved, it shows up in NCOA — two months later.
A real voter moved. They want to keep getting their St. Jude’s donation cards. They fill in their NCOA form to get mail forwarded to their new address. Our fraud detectives find this person — and maybe someone voted for them. Cross out one phantom!
Our bad guys are happy to give up a few retail-level ballots to hide the wholesale-level ballot-gathering apparatus. They count on it.
Here’s the fraud equation taking place across the country:
Count the in-person votes on election day.
Count the early, in-person votes.
Shut down the system (Atlanta water leak, Maricopa County everything).
Bring in undeliverable ballots gathered when you changed voters’ names, addresses, or zip codes, then changed them back.
Determine the votes you need to win. Press the “WIN” button.
Wait for the Republicans to file a lawsuit months later.
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.
The RNC helps with its antiquated “big data” system equally oblivious to anything that happens within a month.
Want to run for office? It’s uglier.
A latency-prone database, like the RNC’s, to pick one, tells you how your voter was prone to vote over the last 10 election cycles. She “leans” Republican.
Unfortunately, it does not tell you that while she leaned Republican for years, she donated, this week, to Greenpeace, enraged at the Dollar Store being built across her street. Real time means something: what is going on here, now, today.
Your Democrat opponent knows that — she is real time, you aren’t, you are RNC.
You, dear candidate, are using the RNC latency database to get out the vote for your opponent — because you are “latent.”
Story cited here.
