Open records requests reveal 64 of 66 Georgia counties have the same unsolved 'Tennessee Error' that caused seven scanners to miscount hundreds of ballots.
As a software developer, I can actually confirm that there is such a thing as "we don't know what caused this, but it's fixed".
When we ("we" here being my employer, not Dominion -- but I doubt any other software company is different in this regard) get a bug report about an old version of our software, the first thing we do is try doing what is described as triggering the bug on the current version. If we can reproduce the bug, we go on to check what's causing it. If we can't, it gets closed as "fixed in the current version" without further investigation.
Now given that this bug possibly changed the outcome of an election and there's no "This is fixed in the current version, so we'll recount the election with the current version" mitigation, this is not acceptable at all - but the fact that they're saying "we don't know what caused it, but it's fixed" by itself is not necessarily evidence of foul play. It IS evidence of sloppy work that should not be permitted under those circumstances. Unlike ours, their product is NOT something where "fixed in the next version" is sufficient.
Thanks for your input. As a Luddite, I have always been wary of anything electronic or mechanical that requires 3rd party "input" for interpreting or documenting. My immediate reaction is, if a company says it doesn't know what caused a problem with an allegedly certified product, why would anyone use the product, and how lax was the certification?
As a non-Luddite, I have to agree that voting machines and vote counting machines are a bad idea. I wouldn't even trust a voting machine I built myself (and I am perfectly capable of building one).
The people doing the certification might even have done a half-decent job without catching this. If the makers of voting machines hide behind copyright law to not reveal the inner workings of the machine, what can you do if you're asked to certify it? You run a stack of ballots through it and you verify that the count matches what you put in. You make sure the ballots include some invalid ones like marking multiple candidates, some write-in candidates, some corner cases (one candidate marked lightly and the other one marked heavily), and you throw in some things that aren't ballots to make sure they get tossed. And you do it in multiple scenarios, one featuring a Republican win, one featuring a Democrat win, one featuring a Third Party candidate winning. If you want to be thorough, you pull the plug while the machine is doing its work and then put it back in to make sure the count will still be valid if there's a power outage in the middle of counting. You've just confirmed that the machine CAN do what it claims it does.
But what if there's a backdoor programmed into it that you won't trigger with those tests? Maybe "Count a vote for write-in candidate Abcdef Ghijklm as 10000 votes for Biden"? Unless you happened to predict the exact name of the fake write-in candidate triggering those 10000 votes, you won't catch it. (And of course someone hiding malicious code could make it even more unlikely to uncover it by not relying on a single write-in candidate triggering bad behavior - it could also be a case of "If invalid write-in candidates Abcdef Ghijklm, Adolph Hitler, Joseph Stalin, God and Satan each get one write-in vote, add a million votes for Biden." All you'd have to do to rig the election is get 5 people to vote the "correct" way.)
Or maybe "If someone puts a sticker with a certain QR code on the ballot, ignore the next 10000 votes for Trump"? No way to catch that if you don't have access to the machine's source code for copyright reasons, and the chances of catching that in any test are infinitely small (just like with write-in candidate Abcdef Ghijklm having a special meaning, you'd have to guess the exact QR code triggering it and on top of that put it in the exact right place on the ballot).
Outside of the fact that they should have refused to certify any machine without having full access to every bit of source code running in there, the people who certified it may actually have done their job if we're dealing with an "intentional malfunction".
Now, if I were to build a voting machine, I'd make sure it uses only open source components so anyone trying to verify it for certification could make sure there's no such malicious constructs in it, and assuming I didn't make any mistakes that would allow someone else to break into the machine, that machine would give the correct results... Or wouldn't it? How could I verify on election day that the machine is actually still running the exact code I put on it?
Sure, an election official put a seal on it. But do I know that election official isn't corrupted? Maybe he took off the original seal, "extended" my software with some of the "special cases" I listed before, and then re-sealed it?
That's why I would never certify any voting machine or vote counting machine, not even my own.
I could certify that mine (or one of the existing open voting machine projects) is better than Dominion's or Diebold's, but I would never certify that it's totally safe.
You want honest elections? Vote on paper and count manually and in public, with representatives of each party watching the count.
They would never admit anything because they have been under scrutiny from the end of the rigged 2020 election. If the majority of counties in GA had the same error, how many votes were never counted? We saw nearly every vote switch go down for Trump and up for Biden. That is not an anomaly. That’s a PATTERN.
It is time to go back to paper ballots. Hire enough people to count the votes in each polling station. That can be easily verified unlike this software voting system.
Agreed, and if you want to have a kick in your blood pressure today, try registering & watching this little meeting, using a non-trackable email address, just in case, and see how our gov't is basically told by big tech how to run everything, including security, which is really a farse, given the solarwinds breach has never really been repaired, just band-aided...
Without meaning to defend them, this COULD have a benign explanation. Of course fractional voting is entirely useless in a national or state election, but if they want to make the same product usable for other use cases - such as voting by shareholders of a company, where the vote of someone holding multiple shares counts more than the vote of someone holding just one share, or voting in a home owner association where someone with a bigger/more expensive condo has more votes than someone with a smaller/cheaper condo in the same complex - that functionality has a purpose (and maintaining one product with this functionality that can be turned off is less work than maintaining 2 versions, one with and one without the function).
I agree that it was likely used to cheat - but the fact that the machine supports it alone is not proof.
As a fellow software dev, though, there is also the 'fixed by inspection' cure. There is a pretty good error message there that should lead back to one or two pieces of code; I could see them fixing the error handling to not invalidate future ballots by inspecrion, but not knowing why the underlying issue happened. (SD card corruption?)
For volunteers going to Logic and Accuracy Testing at ROV's all over the country in the coming weeks, what do we look for? What information do we request? What documents should we file to preserve our rights to appeal or protest should some anomaly be suspected?
Definitely do NOT sign off on the testing if you have any doubts. Ideally write something to that effect on the document itself, with your signature. I think these tests are just staged, feel-good tours anyway.
Each State has Election Laws & Rules or Election Management Guidelines, even if they don't follow them, so you have to use a search engine other than googoo-el, and find those, for starters! Then, I would also follow the forensic guidelines to preserve the data & anomalies, taking pictures or screenshots with the date and timestamps visible/able to zoom in on, and proof of the machine's serial numbers, etc...I would get a CPA who also knows forensic accounting to team up with an IT expert who knows CISA, or is certified in it, and then someone who studied the State's Election laws to create a good team in each county! Great question!
I am wondering if there's any lawyers who would pick up on this, or if you have shared this info with Mike Lindell's legal team, to see if they can prosecute, or add it to current legal proceedings, yet?
Great job on getting the details all sorted out! We are grateful for your diligence!!
A lawsuit is planned. That is what the GiveSendGo is for. Please donate. This needs to fixed. It's not just GA, where I am, but across the country wherever these machines were/are used. Dominoes must fall!
This is just incredible and generates more questions certainly than it answers with stunning inconsistencies, puzzling and questionable statements that make absolutely no sense. So much so that it approaches nonsense and pure bull shit.
I have read this account carefully and something smells very, very real and fishy.
While I am not a programmer or even a computer scientist, I do know enough that these ‘codes’ do not ‘mysteriously appear’ and in most cases do not self-generate. This ‘inconclusive root cause assessment’ from Dominion is laughable and almost sounds like they are already hiding behind the 5th amendment. The fact the ‘government experts’ couldn’t figure it out is a sad testament to the abilities and capabilities of incumbent ‘government experts.’ What are they being paid to do then?
Here’s some self-proclaimed gourmet food for thought.
Why are federal agencies not eagerly investigating and ALL OVER this? Investigating such claims and wrong doings in a federal election tells this ignorant citizen something is broken.
DHS could be accountable, certainly DOJ and fbi but they are too busy and ‘spread thin’ harassing private citizens, political enemies and opponents to do their REAL JOBS according to their 1) charters and ‘mission statements’ and 2) job descriptions.
I find it disgusting, reprehensible and so broken as to be close to beyond repair.
But wait. We the People CAN fix it. We MUST VOTE. Those votes MUST BE COUNTED with honesty and integrity which is apparently as you point out a HUGE problem.
We MUST clean house this coming election AND CLEAN the senate as well and then the Shady Rest Hotel formerly known as the White House.
So, there is no telling how many votes for Kemp’s opponent were not counted, as well as the 2020 election. But we are supposed to be quiet about the election because it was perfect. For Democrats yeah. They accomplished their MISSION. Anyone thinking the software didn’t do EXACTLY what it was DESIGNED to do is in denial that elections would be rigged through software. The software owners were not shy about their hatred of certain candidates.
These errors cause Adjudication. Which 93% were adjudicated ballots in Georgia in 2020, causing the election to get stolen from Trump. Seems they are at it again , because they got away with it the first time and nothing is stopping them now.
Incredibly, 64 of 66 or 97% of Georgia’s counties have the same “Tennessee Error” that Dominion Voting Systems and the U.S. government already investigated and admitted they do not know the cause.
GA has 159 counties. I’m not saying Dominion isn’t crooked as hell. A weird section of the GA constitution says the voter had to be able to walk to and from the polling station in the same day, so we have an inordinate number of counties
I read your logfiles that appear to have this error. As the EDC says, this log message preceded each anomaly, but not all instances of this log message indicate an anomaly. In fact, I would suggest that the scan failing in your logs is more concerning. However, I would propose that the evidence, that the counter kept on going up after this log message, is good evidence that the machine was still counting ballots correctly. Without seeing the source I can't say, but to me it looks like the machine detects a wrong-way ballot by looking for a relevant QR code, and logs when it doesnt find one (and presumably spits the ballot out to be reversed). I don't think this particular log message is worrisome.
If you published all the slogs somewhere, it would be interesting to see if the ballot counts recorded counted in the log match up with the expected counts, to check whether the anomaly was seen. I would most like to see the TN slogs with the anomaly, though; I would hope there are more clues in those logs.
While we may often comment about the machines, we really ought to understand why "blocked and significantly delayed” by Ryan Germany from the Secretary of State’s office" is not the real issue. It almost seems like the officials MUST defend their wise purchase of the particular machine. Thus they would rather not have mere citizens poking around causing trouble.
The TN case is more than troubling in that the root cause was not found. So they had the certification people who do have third party access to the source code, the vendor who created the source code telling the buyer that something went wrong and we don't know why. That can't possibly be true. It can't be that complicated unless the original software creators are long gone and those creators wrote non-maintainable software. That situation stinks and if true ought to decertify the software until the bug can be fully defined.
This continues to call for fully open source non-proprietary software freely available to any who wish to use it employing industry standard scanners and ballot printers. The paper should continue to be specification based printing with suitable tracking one-time codes. And in conjuration with blockchain technology, voters could be assured their vote was counted and not modified - any voter using their private key could verify their vote. The graft involved with the various purchase agreements would end and election officials would not need to defend their procurement choices. Removing the graft alone is reason enough to mandate such systems. Of course, such development has been going on for some 20 years and will go on developing forever if the vendors have their way.
As a software developer, I can actually confirm that there is such a thing as "we don't know what caused this, but it's fixed".
When we ("we" here being my employer, not Dominion -- but I doubt any other software company is different in this regard) get a bug report about an old version of our software, the first thing we do is try doing what is described as triggering the bug on the current version. If we can reproduce the bug, we go on to check what's causing it. If we can't, it gets closed as "fixed in the current version" without further investigation.
Now given that this bug possibly changed the outcome of an election and there's no "This is fixed in the current version, so we'll recount the election with the current version" mitigation, this is not acceptable at all - but the fact that they're saying "we don't know what caused it, but it's fixed" by itself is not necessarily evidence of foul play. It IS evidence of sloppy work that should not be permitted under those circumstances. Unlike ours, their product is NOT something where "fixed in the next version" is sufficient.
Thanks for your input. As a Luddite, I have always been wary of anything electronic or mechanical that requires 3rd party "input" for interpreting or documenting. My immediate reaction is, if a company says it doesn't know what caused a problem with an allegedly certified product, why would anyone use the product, and how lax was the certification?
As a non-Luddite, I have to agree that voting machines and vote counting machines are a bad idea. I wouldn't even trust a voting machine I built myself (and I am perfectly capable of building one).
The people doing the certification might even have done a half-decent job without catching this. If the makers of voting machines hide behind copyright law to not reveal the inner workings of the machine, what can you do if you're asked to certify it? You run a stack of ballots through it and you verify that the count matches what you put in. You make sure the ballots include some invalid ones like marking multiple candidates, some write-in candidates, some corner cases (one candidate marked lightly and the other one marked heavily), and you throw in some things that aren't ballots to make sure they get tossed. And you do it in multiple scenarios, one featuring a Republican win, one featuring a Democrat win, one featuring a Third Party candidate winning. If you want to be thorough, you pull the plug while the machine is doing its work and then put it back in to make sure the count will still be valid if there's a power outage in the middle of counting. You've just confirmed that the machine CAN do what it claims it does.
But what if there's a backdoor programmed into it that you won't trigger with those tests? Maybe "Count a vote for write-in candidate Abcdef Ghijklm as 10000 votes for Biden"? Unless you happened to predict the exact name of the fake write-in candidate triggering those 10000 votes, you won't catch it. (And of course someone hiding malicious code could make it even more unlikely to uncover it by not relying on a single write-in candidate triggering bad behavior - it could also be a case of "If invalid write-in candidates Abcdef Ghijklm, Adolph Hitler, Joseph Stalin, God and Satan each get one write-in vote, add a million votes for Biden." All you'd have to do to rig the election is get 5 people to vote the "correct" way.)
Or maybe "If someone puts a sticker with a certain QR code on the ballot, ignore the next 10000 votes for Trump"? No way to catch that if you don't have access to the machine's source code for copyright reasons, and the chances of catching that in any test are infinitely small (just like with write-in candidate Abcdef Ghijklm having a special meaning, you'd have to guess the exact QR code triggering it and on top of that put it in the exact right place on the ballot).
Outside of the fact that they should have refused to certify any machine without having full access to every bit of source code running in there, the people who certified it may actually have done their job if we're dealing with an "intentional malfunction".
Now, if I were to build a voting machine, I'd make sure it uses only open source components so anyone trying to verify it for certification could make sure there's no such malicious constructs in it, and assuming I didn't make any mistakes that would allow someone else to break into the machine, that machine would give the correct results... Or wouldn't it? How could I verify on election day that the machine is actually still running the exact code I put on it?
Sure, an election official put a seal on it. But do I know that election official isn't corrupted? Maybe he took off the original seal, "extended" my software with some of the "special cases" I listed before, and then re-sealed it?
That's why I would never certify any voting machine or vote counting machine, not even my own.
I could certify that mine (or one of the existing open voting machine projects) is better than Dominion's or Diebold's, but I would never certify that it's totally safe.
You want honest elections? Vote on paper and count manually and in public, with representatives of each party watching the count.
Principal Agent Problem.
They would never admit anything because they have been under scrutiny from the end of the rigged 2020 election. If the majority of counties in GA had the same error, how many votes were never counted? We saw nearly every vote switch go down for Trump and up for Biden. That is not an anomaly. That’s a PATTERN.
It is time to go back to paper ballots. Hire enough people to count the votes in each polling station. That can be easily verified unlike this software voting system.
Agreed, and if you want to have a kick in your blood pressure today, try registering & watching this little meeting, using a non-trackable email address, just in case, and see how our gov't is basically told by big tech how to run everything, including security, which is really a farse, given the solarwinds breach has never really been repaired, just band-aided...
https://federalnewsnetwork.com/cme-event/federal-insights/maximizing-security-and-flexibility-in-the-orbit-of-a-cloud-migration/
There is also WAD, Working As Designed.
Dominion has the ability for the user to program fractional voting and that was done for one reason only....to cheat.
Without meaning to defend them, this COULD have a benign explanation. Of course fractional voting is entirely useless in a national or state election, but if they want to make the same product usable for other use cases - such as voting by shareholders of a company, where the vote of someone holding multiple shares counts more than the vote of someone holding just one share, or voting in a home owner association where someone with a bigger/more expensive condo has more votes than someone with a smaller/cheaper condo in the same complex - that functionality has a purpose (and maintaining one product with this functionality that can be turned off is less work than maintaining 2 versions, one with and one without the function).
I agree that it was likely used to cheat - but the fact that the machine supports it alone is not proof.
Lol.
Dominion is a garbage and criminal company which is doing fine with all the criminals in the US political and judiciary branches.
As a fellow software dev, though, there is also the 'fixed by inspection' cure. There is a pretty good error message there that should lead back to one or two pieces of code; I could see them fixing the error handling to not invalidate future ballots by inspecrion, but not knowing why the underlying issue happened. (SD card corruption?)
For volunteers going to Logic and Accuracy Testing at ROV's all over the country in the coming weeks, what do we look for? What information do we request? What documents should we file to preserve our rights to appeal or protest should some anomaly be suspected?
Definitely do NOT sign off on the testing if you have any doubts. Ideally write something to that effect on the document itself, with your signature. I think these tests are just staged, feel-good tours anyway.
Each State has Election Laws & Rules or Election Management Guidelines, even if they don't follow them, so you have to use a search engine other than googoo-el, and find those, for starters! Then, I would also follow the forensic guidelines to preserve the data & anomalies, taking pictures or screenshots with the date and timestamps visible/able to zoom in on, and proof of the machine's serial numbers, etc...I would get a CPA who also knows forensic accounting to team up with an IT expert who knows CISA, or is certified in it, and then someone who studied the State's Election laws to create a good team in each county! Great question!
I found another way to get help to uncover any fraud you may see: Catherine at True the Vote has created a fraud hotline: https://truethevote.locals.com/upost/2829894/truth-is-like-the-sun
Great article brother. Your getting better by the day. So much dirty information coming out daily about Government involvement.
Worse part, cant label anything ‘conspiracy theory anymore. Its all true!!
I am wondering if there's any lawyers who would pick up on this, or if you have shared this info with Mike Lindell's legal team, to see if they can prosecute, or add it to current legal proceedings, yet?
Great job on getting the details all sorted out! We are grateful for your diligence!!
A lawsuit is planned. That is what the GiveSendGo is for. Please donate. This needs to fixed. It's not just GA, where I am, but across the country wherever these machines were/are used. Dominoes must fall!
Dominion just seems an appropriate name Dominion over us!
I'm sure a recount would show that the "error" undoubtedly resulted in Dem wins. As usual.
This is just incredible and generates more questions certainly than it answers with stunning inconsistencies, puzzling and questionable statements that make absolutely no sense. So much so that it approaches nonsense and pure bull shit.
I have read this account carefully and something smells very, very real and fishy.
While I am not a programmer or even a computer scientist, I do know enough that these ‘codes’ do not ‘mysteriously appear’ and in most cases do not self-generate. This ‘inconclusive root cause assessment’ from Dominion is laughable and almost sounds like they are already hiding behind the 5th amendment. The fact the ‘government experts’ couldn’t figure it out is a sad testament to the abilities and capabilities of incumbent ‘government experts.’ What are they being paid to do then?
Here’s some self-proclaimed gourmet food for thought.
Why are federal agencies not eagerly investigating and ALL OVER this? Investigating such claims and wrong doings in a federal election tells this ignorant citizen something is broken.
DHS could be accountable, certainly DOJ and fbi but they are too busy and ‘spread thin’ harassing private citizens, political enemies and opponents to do their REAL JOBS according to their 1) charters and ‘mission statements’ and 2) job descriptions.
I find it disgusting, reprehensible and so broken as to be close to beyond repair.
But wait. We the People CAN fix it. We MUST VOTE. Those votes MUST BE COUNTED with honesty and integrity which is apparently as you point out a HUGE problem.
We MUST clean house this coming election AND CLEAN the senate as well and then the Shady Rest Hotel formerly known as the White House.
So, there is no telling how many votes for Kemp’s opponent were not counted, as well as the 2020 election. But we are supposed to be quiet about the election because it was perfect. For Democrats yeah. They accomplished their MISSION. Anyone thinking the software didn’t do EXACTLY what it was DESIGNED to do is in denial that elections would be rigged through software. The software owners were not shy about their hatred of certain candidates.
Fraud is Fraud - FIX 2020 - How can we go further without this? Reading Stop BUSH 7 CLINTON below says it all.
Rigged.
These errors cause Adjudication. Which 93% were adjudicated ballots in Georgia in 2020, causing the election to get stolen from Trump. Seems they are at it again , because they got away with it the first time and nothing is stopping them now.
Incredibly, 64 of 66 or 97% of Georgia’s counties have the same “Tennessee Error” that Dominion Voting Systems and the U.S. government already investigated and admitted they do not know the cause.
GA has 159 counties. I’m not saying Dominion isn’t crooked as hell. A weird section of the GA constitution says the voter had to be able to walk to and from the polling station in the same day, so we have an inordinate number of counties
A friend of mine messaged me the link to this article and I posted it on Facebook on my timeline and in 2 private groups. Facebook immediately labeled it as False Information and removed it from my timeline. Then they sent a link to the admins in the private groups asking them to remove it "To make Facebook a nicer place" and sent the admins this link: https://leadstories.com/hoax-alert/2022/10/fact-check-election-results-not-invalidated-by-dominion-voting-machines-qr-code-signature-mismatch.html?fbclid=IwAR31uIf9K7HR2PJ6Vovmi1Gn3nw5WgQ4D5SVq24K60_IMX3ddOb3hLXZF_4
They are in denial and shilling for the Democrats.
latest maga news http://magaera.createbank.app
I read your logfiles that appear to have this error. As the EDC says, this log message preceded each anomaly, but not all instances of this log message indicate an anomaly. In fact, I would suggest that the scan failing in your logs is more concerning. However, I would propose that the evidence, that the counter kept on going up after this log message, is good evidence that the machine was still counting ballots correctly. Without seeing the source I can't say, but to me it looks like the machine detects a wrong-way ballot by looking for a relevant QR code, and logs when it doesnt find one (and presumably spits the ballot out to be reversed). I don't think this particular log message is worrisome.
If you published all the slogs somewhere, it would be interesting to see if the ballot counts recorded counted in the log match up with the expected counts, to check whether the anomaly was seen. I would most like to see the TN slogs with the anomaly, though; I would hope there are more clues in those logs.
While we may often comment about the machines, we really ought to understand why "blocked and significantly delayed” by Ryan Germany from the Secretary of State’s office" is not the real issue. It almost seems like the officials MUST defend their wise purchase of the particular machine. Thus they would rather not have mere citizens poking around causing trouble.
The TN case is more than troubling in that the root cause was not found. So they had the certification people who do have third party access to the source code, the vendor who created the source code telling the buyer that something went wrong and we don't know why. That can't possibly be true. It can't be that complicated unless the original software creators are long gone and those creators wrote non-maintainable software. That situation stinks and if true ought to decertify the software until the bug can be fully defined.
This continues to call for fully open source non-proprietary software freely available to any who wish to use it employing industry standard scanners and ballot printers. The paper should continue to be specification based printing with suitable tracking one-time codes. And in conjuration with blockchain technology, voters could be assured their vote was counted and not modified - any voter using their private key could verify their vote. The graft involved with the various purchase agreements would end and election officials would not need to defend their procurement choices. Removing the graft alone is reason enough to mandate such systems. Of course, such development has been going on for some 20 years and will go on developing forever if the vendors have their way.