When you write code, you have to compile it. Here is an easily readable if statement in C:
If ( trump_count > biden_count)
{
trump_count --;
biden_count++;
}
That says if trump has more than biden, then subtract 1 from Trump and add 1 to Biden.
That is an oversimplified example but there would have to be something along those lines in the Smartmatic/Dominion code. So we should be able to get that off of the machines right? Wrong. Machines don't read code like that. That kind of code is compiled so that when it gets on the machine it is all just 1's and 0's and the program called the compiler creates that code and it is generally unreadable.
https://files.catbox.moe/ahpcx1.png
If we knew what the compiler they used was then we could decompile the code and have our smoking gun right there in the code. However, I think they thought that through and created their own compiler so that if the code and compiler are subpoenad, they can hand over a compiler that was designed in a way to obfuscate the offending code.
If you think writing your own compiler is hard, guess again. You just need to know how the CPU works and how storage and memory are addressed. Even that crazy bastard that wrote TempleOS wrote his own compiler.
I cannot believe we aren't dissecting the code forensically, and if someone is, that would be the absolute best way to prove this, beyond statistical analysis, eyewitness testimony, etc.
Happy Thanksgiving.
view the rest of the comments →
[–] 26555357? 0 points 2 points 2 points (+2|-0) ago (edited ago)
Would you be able to have code that does the fraud and then deletes the offensive bits?
There are so many points of failure - the whole system stinks from top to bottom. Just tabulating in foreign nations presents a thousand holes to exploit.
In a well designed system there should be a FULL audit trail from the ballot to the final count, that anyone can go back and verify each step.
Why do banks never get their numbers wrong?
[–] 26558399? ago
Banks do get their numbers wrong. But they keep their mouths shut and eat the errors if necessary. Database recovery program developers know this is true.
[–] 26555427? [S] 1 point -1 points 0 points (+0|-1) ago (edited ago)
To do that, you would have to have a CPU that could overwrite it's own code and I don't think that is possible. You could do that with a coprocessor and if the exact location of the code on the CPU was known, which would be easy, then you could have it so that at a certain time, that code was overwritten with a harmless and unsuspecting comment, but, then the code on the coprocessor would be there, showing what storage loations were overwritten, or it could delete its own firmware but then you'd have this blank coprocessor sitting there connected to the main CPU like "what's this for?". We would have to forensically analyze the hardware and the software, which is possible.
[–] 26555491? 0 points 1 point 1 point (+1|-0) ago
Don't worry the nations most trusted organization is on it, the FBI.
[–] 26556930? ago
What the fuck are you jabbering about? Of course code can delete itself.
[–] 26555620? ago
You underestimate the unlimited skills of the Venezuelan and Serbian programmers LOL
[–] 26555544? ago
It wouldn’t take that. Just some code to clean up after itself... I’ve written a few exploits in my day