Anyone who was seriously paying attention to the political climate in the United States heading into the 2022 midterm elections was well aware that the VAST majority of Americans had it up to HERE with the Democrat Party.
Nonetheless, for some inexplicable reason, as the results of the midterms slowly rolled in, what do you know, but the Democrats ended up retaining the Senate and barely losing the House of Representatives by the slimmest of margins.
There is only one way we could see this happening … CHEATING.
Well, there have been a lot of accusations to whether or not there were … ‘shenanigans’ involved in the 2020 elections but not too much hardcore proof .. UNTIL NOW …
The Gateway Pundit reported:
Guest post by Jay Valentine – reprinted with permission from American Thinker
Database latency – geeky term, but it’s how they DID It!
A policeman pulls over a speeder. The police computer, fortunately, picks up that 3 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 the database record lags behind current reality. We all experienced it in our electronic-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 batch, highly latent services as their baseline. If someone moved, it shows up in NCOA. Great. 2 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! One!
Our bad guys are happy to give up a few retail-level ballots to hide their 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 will. Win they do.
Ballot gatherers know Republicans use dumb technology – relational databases, SQL, NCOA, Melissa, all non-real-time, highly latent systems.
