That Moment In Michigan, While You Slept, When Trump's 50+% Lead Was Stolen
(media.patriots.win)
🛑 STOP THE STEAL 🛑
Comments (13)
sorted by:
DEFAULT COMMUNITIES
•
All
General
AskWin
Funny
Technology
Animals
Sports
Gaming
DIY
Health
Positive
Privacy
Who can forget that dramatic moment, while you were sleeping, that Trump lost his 50% plurality in Michigan? The trick they used was to wait until the numbers got big enough so that a seemingly insignificant "blip" in the overall percentages would scroll on past you in hopes you wouldn't notice that there was a huge number of votes making that happen. Why did they "present" the votes to the TV audience in terms of percentages? Was it to hide this exact technique? And you can see how their software vote flipping, which was designed to stay under the radar, was insufficient to produce a Biden victory, so obviously they had to produce a massive quantity of "mail-in" ballots to spike the count in a very significant way. Which was why so many states all stopped counting simultaneously--to give them time to mark all those fake ballots after kicking out the election monitors.
All the states are online:
https://static01.nyt.com/elections-assets/2020/data/api/2020-11-03/race-page/michigan/president.json
Right. Where I got the data. Been looking in my spare time, but this is the first big obvious smoking gun I've found thus far. There are a lot of anomalies, but this was the white whale.
Nice! I’m gonna suck this into excel. Thanks.
Virgina buggery starts at 11/04 04:14:40 GMT
Note the source “Edison” - fuckery runs deep
Let me know how you convert these timestamps e.g.; 2020-11-04T04:42:34Z into Excel time/date data, and do you know what time zone they are coded as? Hmm... Dominion servers in Frankfurt, Germany, eh? So that explains why they're all the 4th instead of the 3rd. I don't know of any Americans who timestamp their stuff as GMT data...
GMT = UTC (Universal time) You need to know the UTC to local offset for the area you are looking at on Nov. 3. The election happened before we set clocks back for the current daylight savings time. Virginia time was UTC - 4 hours when the election happened. So the timestamp 04:14:40 should align with 12:15:40 am local time Nov 4. It can be tricky - some states like Michigan have a time zone boundary running through the state.
Ah, thank you! So, for Eastern Daylight Time, I'll use the formula
=DATEVALUE(LEFT(G2,10)) + TIMEVALUE(MID(G2,12,8)) - TIME(4,0,0)
and format it with
[$-en-US]ddd, mmm dd, yyyy h:mm:ss AM/PM
to convert
2020-11-04T02:39:32Z
into
Tue, Nov 03, 2020 10:39:32 PM
This NY times JSON?
That column takes into account both 3rd party votes and rounding errors (it is the percent of running-total votes that were counted as either dem or rep). Because they were using floating point numbers for votes instead of whole numbers, which was part of the software vote-ratio/flipping scheme. The gradual overtake over time by Biden was the software doing its thing. But they needed those 135,290 fake mail-in ballots to make it work with the hard-coded percentages they had calculated into the software. Certainly as some point they may have started stealing 3rd party votes for Biden too, which is why you might see the total percentage (for either dem or rep) go up, meaning 3rd party went down.
Edit: the data actually has a 3rd party column, which I didn't show, as it seems to be populated with nothing but zeroes. The whole thing is really sloppy. Because you get the number of votes (running total, not broken down into new votes or into Trump votes or Biden votes) and then a dem-percentage and a rep-percentage figure, and then you have to reverse-engineer to figure out what actually happened, which there's no telling at this point what actually happened unless the Kraken releases the Dominion server data.