TruthArchive.ai - Related Video Feed

I found Brian in the server logs, showing him the database. Christy Francois let him in, which could be a problem later on.

On February 11, 462 log entries were overwritten by a script, followed by 37,680 entries on March 3, and 330 entries on March 12, the day before the system was received. The EMS admin account was responsible for these actions. During an audit, having full context of the election is crucial, yet that was not the case here. Specifically, within the Dominion software used for results tallying and reporting, someone executed a command to purge all election results, successfully deleting all records and files from the NAS directory, which contained essential election data, just before the audit began.

On February 11th, a script overwrote 462 log entries. On March 3rd, the same script overwrote 37,686 log entries. On March 12th, the day before the system was received, 330 log entries were overwritten by the script. The EMS admin account performed these actions. A log file from the Dominion software for results tallying and reporting shows that someone purged all the results for the election. The action completed successfully, deleting all the files on the NAS directory, including results and images from the election. According to the transcript, an individual ran a program to clear all records in the system used to generate the official results the day before an audit started.

The speaker discusses the issue of Windows security logs being purged right before two audits were set to begin. They highlight the difficulty in determining who had access to the RTR admin account, which is shared among all accounts. The speaker questions why someone would delete all the results and records from the Dominion software, which is used for tallying and reporting election results, just before an audit. They mention that the deletion was successful and affected files on the NAS directory where election images and details were stored. Overall, the speaker emphasizes the lack of accountability and the need to understand the motives behind this action.

Clark County Technical employees independently found votes appearing and disappearing at night. They were only allowed a visual inspection of a USB drive, not a forensic examination.

On 2/11, 462 log entries were overwritten by a script. On 3rd March, 37,686 log entries were overwritten by the same script. The day before we received the system, 330 log entries were overwritten by that script. The EMS admin account was responsible for this. The challenge is that this occurred before an audit, and it deleted all the records and files related to the election. Someone deliberately ran a program to clear all the records in the system used for generating the official results.

On various dates, an individual ran a script to find blank passwords for the accounts on the system. The script was executed multiple times, overwriting a significant number of log entries. The EMS admin account was responsible for this, but due to the lack of accountability in assigning the username, it is difficult to prove who exactly did it. Fortunately, historical data from MTech video feeds helped identify the individuals at the keyboards during those times. However, their names will not be released to protect them from scrutiny and potential impacts.

On February 11, 462 log entries were overwritten by a script, and on March 3, 37,680 log entries were also overwritten. The day before we received the system, 330 log entries were overwritten. The EMS admin account was responsible for these actions. It raises concerns about the audit's integrity, as one would expect to have complete election context for auditing. The log file from the Dominion software indicates that someone executed a command to purge all election results, successfully deleting all records and images stored in the NAS directory. This action was taken just before the audit began, which is troubling.

The speaker reveals shocking information about the deletion of the entire database directory from the d drive of the machine called EMS primary. This deletion occurred approximately 10 days before the machines were handed over to the Senate. Deleting documents after being told to preserve them can have severe legal consequences. Additionally, the main database for the election management system software, which contains all election-related data from the November 2020 general election, is missing from the EMS primary machine. This suggests that it has been removed.

The speaker questions whether purging the 2020 election database in February is a standard practice for all elections. The response is uncertain, but they promise to provide an answer. The speaker further asks why data from previous elections was still present on the databases. Again, there is no clear answer, but they assure the congressman that they will find out. The chairman mentions limited server space as a reason for making room for new election data. The speaker raises concerns about the credibility of the recorder, who had criticized Adrian Fontes, the person in charge of the 2020 election. The speaker clarifies that they had a bipartisan board overseeing the election to ensure fairness.

Is it standard practice to delete files off a server after an election? I hope not. So, you admit Maricopa County deleted files after the election? Those files were archived. The auditors initially didn’t have access to those archived files, correct? They did not subpoena those, that's right. You didn’t feel obligated to turn them over? We responded to the subpoena. It’s laughable to suggest a county could delete files in response to a subpoena. Your Twitter mentions purging the 2020 election database in February as standard practice. Can you confirm that’s done for all elections? I cannot confirm that today, but we’ll get you an answer. Why was data from prior elections still present? I don’t have an answer now, but we will provide one. The recorder will answer questions in a timely fashion, but he previously criticized Adrian Fontes, who ran the 2020 election. Yes, we had oversight from both parties during the election.

The speaker reviewed server logs and identified "Brian." The speaker found a database in the next vendor and new forensics. Christy is mentioned in connection to a server. The speaker shows access and a deletion on the log from the database. A previous tweet shows Christy letting Brian into the server. The speaker repeats "Here he is" multiple times. The speaker mentions another law proposal and altering.

The speaker reviewed server logs and identified "Brian." The speaker found forensics in a database. The speaker shows access and a deletion on the log from the database. The speaker claims Christy previously tweeted about letting Brian into the server. The speaker repeats "Here he is" multiple times. The speaker mentions a law proposal.

A scanner can only scan one dollar per second, but there are 4,000 ballots with the exact same time stamp of November 5th at 11:19:40. This suggests that these ballots may have been inserted and cannot be authenticated. The main question is whether this time stamp, which shows an unbelievable speed of scanning, is from the EMS system and not something we created.

Is it standard practice to delete files off a server after an election? I hope not. So, you admit Maricopa County deleted files after the election? Those files were archived. Initially, auditors didn’t have access to those archived files, correct? They did not subpoena those, that’s correct. It’s laughable to suggest that a county can delete files in response to a subpoena while claiming they are archived. Your Twitter mentions purging the 2020 election database in February; is that standard for all elections? I can’t confirm that today, but we’ll get you an answer. Why was data from prior elections still present? I don’t have an answer now, but we’ll provide one. The recorder will answer questions timely. You hired someone to oversee the 2020 election due to concerns about Adrian Fontes, correct? We took back responsibility for election operations to ensure oversight.

Forensic copy bit for bit of everything that was on the Mesa County computer. Just to clarify, there were two forensic images taken of the Mesa County Election server. One, before the software update. Another image taken after. Everything that had been on that drive before this update was gone. Looks like a cover up. Low risk of being caught. Low consequence if they are caught. The reason we know it was deliberate is because of Tina Peters. Are those files important to elections? Critical. The federal voting system standards are very clear that the election records that are required to audit a voting system include the digital records that are all the log files generated by that voting system, especially when it's a complex computer system.

The Windows security logs were purged right before two audits were scheduled to begin. This makes it difficult to determine who had access to the RTR admin account, which is shared among all accounts. It is unclear why someone would delete all the records and files from the Dominion software, which is used for tallying and reporting election results, the day before an audit started.

Is it standard practice to delete files off a server after an election? I hope not. It’s appropriate to maintain files, and while we deleted some files, they were archived. The auditors initially did not have access to those archived files because they were not subpoenaed. It’s laughable to suggest that deleting files in response to a subpoena is acceptable. The subpoena should have covered all election-related records. I cannot confirm if purging the database after elections is standard practice, but limited server space may require it. If that is the case, why was data from prior elections still present? We will provide answers to these questions. It's important to note that we had oversight during the 2020 election due to concerns about the previous administration's competence.

On 2/11, 462 log entries were overwritten by a script. On 3rd March, 37,686 log entries were overwritten by the same script. On 12th, 330 log entries were overwritten. The EMS admin account is responsible for this. The challenge is that this occurred before an audit, which means the full context of the election is not available. The log file shows that someone purged all the results for the election, deleting all records and files. This happened right before the audit started.

Mr. Bennett questions if it's standard practice to delete files off a server after an election. Mr. Gates says they maintained files but deleted the ones that were archived. It is revealed that Maricopa County deleted files off the server after the election, which the auditors didn't have access to initially. The auditors didn't subpoena those files, and Maricopa County claims they responded to the subpoena. Mr. Bennett finds it laughable that the county would delete files in response to a subpoena, as the subpoena requested all records related to the election. The county interpreted the subpoena differently.

On various dates, an individual ran a script to search for blank passwords on the system. This script overwrote a significant number of log entries. The EMS admin account was responsible, but it's difficult to prove who specifically executed the script due to the lack of accountability in assigning usernames. Fortunately, historical data from MTech video feeds allowed us to identify individuals at the keyboards during those times. However, we won't disclose their names due to the potential scrutiny and impact on them.

Social Security needs a closer look. We're finding people listed as recipients who are 50 years old, but I don't know anyone that age receiving benefits. They'd be incredibly old, practically setting a world record. It seems likely many of these individuals have passed away, or they would be very well known. There's a clear problem with the accuracy of the records.

There is a discussion about log files on two screens. One screen shows hundreds of log files from 2019 until May 22, 2021. The other screen only has three years of log files, which have mysteriously disappeared. It is mentioned that when a Dominion employee came in, the log files vanished. These files record all access to a specific machine. It is also mentioned that Dominion sent people around the country for software updates during that time. Some participants confirm this information.

There is a pentagon that hides a billion dollars without any accountability, and it has never passed an audit. To uncover the truth, it seems that someone may need to leak information from these labs online, potentially facing dire consequences afterward.

On February 11th, a script overwrote 462 log entries. On March 3rd, the same script overwrote 37,686 log entries. On March 12th, the day before the system was received, 330 log entries were overwritten by the script. The EMS admin account performed these actions. A log file from the Dominion software for results tallying and reporting shows that someone purged all the results for the election. The action was completed successfully, deleting all the files on the NAS directory, which contained all the results and images from the election. An individual ran a program to clear all records in the system used to generate the official results the day before an audit started.