>>11580383 pb
> Michigan
Joe Biden's fortunes in Pennsylvania looked bleak until an apparent computer system reboot.
Immediately afterward, his cumulative vote count curve bent upward at a rate that overtook Trump's just in time for the end of counting.
After the reboot, Trump's curve leveled off. With cumulative curves, this means there was a sudden and sustained shift in their splits of the votes heavily favoring Biden.
>>11580825 Pennsylvania
>>11580383 pb Michigan
Here's what we might expect from an election. This example is florida. When Biden kinks upward, so does Trump. Otherwise smooth.
Also, oddly, another midday computer glitch. In this case sending both candidates' totals to 20 million and then reversing at 10:30am on 11/4.
Compare how odd the PA and MI curves for Biden are relative to FL.
>>11580825 Pennsylvania
>>11580383 pb Michigan
>>11580944 Florida (sunny comparison)
Wisconsin appears to do a reboot suddenly AFTER a Biden spike in vote counts.
And then still needs another small spike to pull it all off before closing.
see this guy's work on the twitter, he worked harder and used numpy. results the same.
@APhilosophae
https://twitter.com/aphilosophae
http://s000.tinyupload.com/?file_id=14566999163598825215
>>11580825 Pennsylvania
>>11580383 pb Michigan
>>11580944 Florida (sunny comparison)
>>11581153 Wisconsin
Here's Georgia. Once again, vote spike for Biden with no corresponding movement for Trump, followed by what appears to be a computer reboot followed by an upward shift in Biden's cumulative vote curve as Trump's curve flattens. (Look for a hard-coded percentage vote flip product feature)
I've written code to hide what it's doing. Vendors do this a lot for Apple apps to hide that it's spyware and circumvent Apple's (weak) validation and security checks.
If they even hid it.
All you have to do is encrypt sections and nest them into incomprehensible series of recursive functions.
i think we can continue to be vigilant but I might anticipate that they've got it covered
Most computers can. It doesn't need to be a reboot but most people understand that so I used that language.
For some states these spikes go up to 20 million not down to zero.
A USB drive or some cool such thing like that, could prevent the computer/server from sending its update to the system - showing a zero total for one time stamp - while the code or tables are locked and in use by the USB update code.