Tech Ping
“It’s not a bug , it’s a feature!”
To ask the question is to answer it.
Their SW is malicious. It’s not that it makes mistakes, it’s that it does things that it shouldn’t do at all.
You can program computers to do anything, even unethical things.
Hopefully you won’t eventually try to turn this thread into some sort of Linux religion sermon.
If not, here’s a tweet you might be Interested in.
https://twitter.com/AOECOIN/status/1326396193631559685
#Dominion Instruction Manual shows how to:
-Hack it’s software
-Feed it “test stacks” with only Biden marked
-Can those be counted as legitimate results? YES.
-Were they? YES.
-Can Purge ENTIRE BATCHES of #Trump votes.
AND THEY DID ALL OF IT
Check this out ....
Hammer and Scorecard - From the Censored YouTube WarRoom Episode 470
https://rumble.com/vaz2ih-hammer-and-scorecard-from-the-censored-youtube-warroom-episode-470.html
Dominion software / hardware was designed to be a platform wide open for tampering. Tampering is built in. How to tamper on a small scale is even explained in the user manual as a feature. Overseas servers - just wow. Editable audit files just make me speechless. Hackable in under 2 minutes with a cell phone from outside the building.
The only way Dominion could be so simple to attack in so many ways (actually every conceivable way) is for it to have been created to be so. The worst designers and programmers in the entire world would have made a more secure system.
Loosy Goosy, Eazy Peazy
I’ve worked in what is now called “big data” for over 20 years. Glitches like that don’t occur. What does happen is someone may manually do something incorrectly and then it be called a glitch to make it sound nicer. If they have voting machines that can glitch and flip thousands of votes then those that purchased these machines are either fools or willing idiots desiring that outcome. A secure vote scanning machine should never be able to glitch in such a fashion.
Glitch usually refers to hardware.
The Dominion problem is in the software - (computer program).
Example of good code:
If candidate name = Biden then add 1 to Biden counter.
If candidate name - Trump then add 1 to Trump counter.
Bad Code:
If candidate name = Biden then add 1 to Biden counter.
If candidate name - Trump then add 1 to Biden counter.
There is nothing wrong with either of the examples, they both will work fine.
The good code will provide a count for the different candidates.
The bad code will count Biden for Biden and Trump for Biden.
Voting System Examination Dominion Voting Systems Democracy Suite 5.5-A
You bring up a great point.
Banks and merchant services handle billions of transactions per day nationwide, and 99.99% of them are secure. The only time there is fraud is when there is human error or malice, usually at the data entry level, not within the data transmission/encryption/storage systems.
The big exception is when merchants themselves do not secure customer purchase data, such as Target/Home Depot several years back, but the fault was on the retailer systems, not the transaction systems themselves.
The only reason our voting system is fallible and and exploitable is because it was designed to be that way. There are examples of systems that are rarely exploited all around us. Airline passenger check-ins would be another example.
If the machine reads a paper ballot, the excess recount time is to feed ballots into the machine.
What we are learning is that the electronic voting era has been designed to cheat.
Vote with paper ballots. Ballots can be electronically scanned or manually counted. Ballots should be serialized. Absentee ballots are marked as absentee and are different than in person with serial numbers. Provisional ballots should be clearly marked and serialized.
That's a feature.
TotalBidenvotes = ActualBidenvotes + 130,000
Sure they used more cryptic variable names.
Follow tech link will answer questions. Google and FB making it difficult to link by imposing age limit of 18 to see people talk about election computers due to “community standards”.
https://www.youtube.com/watch?v=ficae6x1Q5A&feature=youtu.be
I was in IT as well as an application programmer in an F500 co.
But I could also program occasionally at the system and machine level and did, same place.
Some manipulation of the voting data is necessary for testing and resetting for live voting.
Here is where the system level programming comes in.
Any decent and secure database system is going to employ what is called file journaling. You don’t have to program it. Journaling, when it is set, operates behind the scenes at the system level to create a database listing every change made to the data in a file, when and by which program and user the changes were made. The purpose of journaling, in addition to keeping a log of changes that can be consulted, is to be able to easily back out corruption and bad data. It also automatically records malicious changes by unauthorized viruses, programs and users, invisible to all but the most sophisticated attacks that attempt to cover tracks by altering or destroying system journals, which may require other system authorities. Journals provide prime evidence for all kinds of investigations from debugging to criminal.
If Dominion files are journaled, and anything funny went on in the database, people are dead in short order.
“Votes are supposed to be static pieces of information. NEVER should be “processed” AT ALL!
Votes, once cast, should be read-only database records, UNABLE TO BE CHANGED BY ANY MEANS!”
Agreed.
“Processing”? To do what? It’s a COUNT.
We wrote BASIC code to count back in elementary school computer class.
The scam reveals itself.
I can only imagine processing if they were serialized to eliminate duplicates