Dominion and the Voting Machines

Self | 12 Novembr 2020 | elf

[ShadowAce]

I've been on FR for 20 years now (as of 11/29/2020), and many of you know me through my Tech Pings.

While I am not in any way a politician, I have been in charge of computers systems in both the financial and medical sector, and I have some questions about Dominion that some of you may be able to answer.

I have been in charge of systems (with companies you would all know, and some you would not know at all) that process 160 million financial accounts in a single night--every night of the week, every week of the year. This would include all the activities you would expect in a financial transaction--approval, withdrawals, deposits, contacting various *other* financial institutions to be sure both sides of the transaction were properly accounted for. It's how our economy works. This was back in the 90's, so I know that the ability to do so now has only been enhanced. This kind of load would not make any modern system even breathe hard. No state that I am aware of has that large of a population, so the processing would be quite a bit faster.

My experience in the medical IT field has also be extensive. This includes transactions that contain information that is highly confidential--more so that the financial ones--due to HIPAA. Both experiences include heavy experience with databases and other forms of data retention.

Here's my question.

We have all heard of a "glitch" in Dominion systems that flipped votes from GOP to Dem (never the reverse), yet media (even those on "our" side (Newsmax, OAN, etc)) never bring up this point--WHAT IN THE HECK IS DOMINION DOING?

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!

So tell me again--what possible "glitch" could have caused this, and WHY did the software allow any data manipulation at all?

Secondarily, why do machine vote counts take so long?

[SKI NOW]

So tell me again--what possible "glitch" could have caused this

That's a feature.

TotalBidenvotes = ActualBidenvotes + 130,000

Sure they used more cryptic variable names.

[LowNslow]

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

[C210N]

Interesting. Cert denied for SO MANY reasons.

I can only wonder what’s changed from Suite 5.5-A.

Based on Nov 3, I’d surmise if its any different, it is worse from the perspective of election integrity.

[Bama_84_928]

there is a feature, "Weighted voting" - supposedly used to give more "weight" to officials in a company (decision makers).

Dr. Shiva seemed to show weighting in Republican counties - more votes added to dems based on the precinct. pretty shocking "beautiful line" as he put it.

Dr.SHIVA: MIT PhD Analysis of Michigan Votes Reveals Unfortunate Truth of U.S. Voting Systems

[UnbelievingScumOnTheOtherSide]

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.

[Al B.]

And it was denied 3 separate times.

I've seen reports that in Wayne County, MI, the USB reports were wide open. That was a particular point of concern in this report.

[Al B.]

reports = ports. Oops.

[Macoozie]

“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.

[copaliscrossing]

The worst designers and programmers in the entire world would have made a more secure system.

The simplest approach would be to have verified code as reviewed by software people from both parties then generate a checksum of the code and have that checksum verified multiple times by both parties during the counting to ensure something has been hacked or changed on the fly.

With that said, this wouldn't even account for hackable databases after the votes are "tabulated" by the machines.

My wife succinctly put it this way. "There is no impetus to disallow cheating or make the system secure because it serves those in power". I would extend that to both parties by the way.

[copaliscrossing]

sorry... meant “hasn’t been hacked”...lol

[Golden Eagle]

From your article:

Dominion voting machines tallied the Antrim County votes correctly, but ElectionSource software used to combine the results from individual voting machines was not properly configured, according to Benson’s office.

That is clearly still a computer miscalculation, or glitch, no matter how they want to spin it.

[dila813]

I can only imagine processing if they were serialized to eliminate duplicates

[Pollard]

This is what TX sos machine examiners think of dominion. 3-6 each minutes to speed read. One is just a single page statement that basically says hell no. Dominion employees and machines are basically a mess. I don’t know why any State would use them.

https://www.sos.texas.gov/elections/forms/sysexam/oct2019-hurley.pdf
https://www.sos.texas.gov/elections/forms/sysexam/oct2019-mechler.pdf
https://www.sos.texas.gov/elections/forms/sysexam/oct2019-pinney.pdf
https://www.sos.texas.gov/elections/forms/sysexam/oct2019-sneeringer.pdf
https://www.sos.texas.gov/elections/forms/sysexam/oct2019-watson.pdf
https://www.sos.texas.gov/elections/forms/sysexam/oct2019-vassar.pdf

[ParityErr]

I've been in the corporate IT world for over 25 years and have done enough backend db programming to know these so called glitches is a bunch of BS.

Allan Graham just posted on Parler and hour ago:

BREAKING from President Trump!!

“REPORT: DOMINION DELETED 2.7 MILLION TRUMP VOTES NATIONWIDE. DATA ANALYSIS FINDS 221,000 PENNSYLVANIA VOTES SWITCHED FROM PRESIDENT TRUMP TO BIDEN. 941,000 TRUMP VOTES DELETED. STATES USING DOMINION VOTING SYSTEMS SWITCHED 435,000 VOTES FROM TRUMP TO BIDEN.”

[CedarDave]

To avoid the YouTube so-called “age” restriction, the video has been re-posted at this alternate link:

https://www.bitchute.com/video/scUpSRkNoJ9g/

[CedarDave]

Ping to my #35

[semimojo]

That is clearly still a computer miscalculation, or glitch, no matter how they want to spin it

It's an error in how someone used the tool. It's a human glitch, not a software one.

[Golden Eagle]

It was a computer calculation, not a human input. “Human error” makes it sound as if data was entered incorrectly, which is not what happened. If what you are saying was the case, ALL computer errors could be defined as human errors, since humans ultimately build and configure all computers.

[American in Israel]

I have come to realize community standards is a polite way to say the party line.

[Chgogal]

Bookmark