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!
R&I – FS