Voting Machine Data is Definitely NEVER Deleted...Without GOOD Reason
Special Conspiracy Theorist Edition
Let’s dispel a conspiracy theory….Election Machine admin user accounts (that use shared user names and shared passwords which is a best practice) will NEVER be used through INCOMPETENCE and/or IGNORANCE and/or MALEVOLENCE and/or CORRUPTION and/or “FUN” to DELETE Election Machine data.
Period Full Stop.
Even though the Delete functionality exists, CRITICAL data has NEVER been deleted. That is against the law, right? Questioning this statement immediately puts you into a category of “Extremely Illiterate Election Conspiracy Theorist MAGADonian Insurrectionist”.
Audit trails are typically used in IT systems to capture when data was DELETED. But not in our Certifiable Election Machines for the following reasons:
Our government officials are 100% trustworthy
The vendors who make the machines are even more trustworthy…150%
Having DELETE available makes supplying information for FOIA requests much easier for bureaucrats
Deleting for example, system logs, saves space on the hard drive
“Delete” in Serbian is spelled “избриши”. Look at the picture below. Completely different.
And so many more…..
As you will see in the examples below, while DELETE is available on these Election Machines, it actually INCREASES the integrity of the data and make it more reliable and easier to read, provided you even have a CLUE what you are reading.
Don’t take my word for it because you can find the context for these excerpts here.
If you navigate to the Sheriff Dar Leaf’s X account, you will find files which contain emails from DVS.
https://twitter.com/SheriffLeaf
https://x.com/SheriffLeaf/status/1769758994120274040
Further deprogramming on these topics can be found in Part1, Part2, Part3, Part4 and Part5 and many more posted on my substack.
__________
The following test should be added into the RTR Users Guide in section 7: "7.5 Deleting log files To delete the log files for the selected tabulators in the Tabulators screen use the 'Delete log' option. This option deletes the log file from the 'Device_Log' folder on the NAS. Additionally, it sets the 'isLogFileLoaded' field value (indicating whether the log file is loaded, for the selected tabulator(s)) to: false in the election project database. The value of that filed is displayed in column 'Log file' of the Tabulators grid. NOTE: Use this feature only if you are not sure that the values in 'Log file' column in the Tabulators screen reflect the log file loaded status of tabulators properly. For example, if the log files were manually deleted from the NAS folder."
__________
The audit trail folder was deleted from the USB. The USB had only the result file The result file and the ballot images were loaded in RTR via removable management media * Expected result*: Loading successful message should be displayed only for the result file loaded Since the USB did not have the audit trail folder, error message should be displayed saying that images not found Actual result: RTR displayed loading successful message for both result file and images. It created a Result folder without images in NAS
__________
In NAS it creates an images folder in the tabulator folder - but it's empty. We've deleted the results files and selected "Override images" - same failed to execute error every time they try to upload.
__________
We need to add a folder change notification to watch any folder change operation(add a new folder, delete the folder 2. check diagnostic test logic(verifydiagnostictest): This verification can only be applied in ICP2, the logic should be the same as the current implementation, and it should be run after new verifymachinestate
__________
Reject and Delete the result file. Note: this does not delete the results from the reporting model, until the reporting model is synchronized. - When you try to delete the qualified write-in in EED there is message: "Cannot delete qualified write-ins. Only qualified write-ins that do not have any results associated can be deleted." - That is CORRECT behavior. - After that synchronize reporting model and delete qualified write-in. - Create new qualified write-in and load results again in RTR, on the Result Files screen, on the Contest Results, there is OLD name for qualified write-in, the one that is deleted.
__________
Today while uploading results from ICE's for Pre-LAT we had an issue with two tabulators. During the upload process we were given the warning that "Images have already been loaded for this tabulator." Nothing for either tabulator had been previously uploaded. Going back to verify what had been uploaded for each of the two tabulators, we found that images and results were uploaded for both. We did, however, reject and delete both ICE Tabulator batches and re-upload them. There were no warnings this time and upload was successful. Is there something we may have done to cause this warning? Im nervous about this happening election night. And if it does happen Election Night, is rejecting, deleting and re-uploading the batch for the ICE tabulator the correct thing to do?
__________
In EED you can only delete a qualified write-in when there are no result files in RTR referring to this candidate. However EED does not check whether there are results for this candidate in the reporting model. If the user deletes a qualified write-in in this situation, the next time the RTR user runs a report or triggers synchronization of reporting model directly and exception will occur and the report model will not be synchronized with the latest changes. The only work around is to purge the results in RTR, afterwards purging will again function correctly. When deleting qualified write-ins in EED, the recommendation is to only do this after you have synchronized the reporting model (by running a report in RTR).
__________
……. also jumped in to help, she had the County Open Computer Management/Private queues/ballot preparation and we noticed 68 messages that we could not clear. Alyssa also tried to delete the data base in SQL and we are getting a dropped failed for database.
__________
El Dorado's voter information guide content is failing during import. During import the "successful" message prompts, but nothing updates. I tried to delete contest guide and re import Deleted election files and re import guide, but didn't work. Attached are screen shots and the voter guide file. Please advise as soon as possible. This is voter guide content needs to be implemented before the County can go live.
__________
From the Client Workstation: Click Delete Project The projects should populate in the window to the right. They are sporadically not appearing. ….Customer tried this from both the server and client workstation. They noticed that when one of the client's was logged off, leaving only one workstation, that it would sometimes work as expected. They are currently using the manual delete process by accessing NAS/SQL. I think that Louisiana may be the only one using this. Question: Does this module exist in 5.12B?
__________
The following methods are affected: SaveVoter DeleteVoter GetPin UpdateVoterStatus
__________
This error message is confusing and redundant for BMD mode since there are no result files and it sais:v"All the found result files are deleted from the existing result locations. The result file from the missing storage path is not deleted. Storage paths that do not exist: Path:... Export log to see detailed message. All election data files are deleted." This error is displayed when tabular is not selected, and therefore it is unknown whether BMD or DRE mode is active.
__________
*Steps to Reproduce:*
1. Load ICX results in RTR
2. Check Challenged Voter's Tab
3. Publish the batch
4. Export the Result files from RTR (Export Result)
5. Reject the result file and delete it from RTR and NAS
__________
In Colorado we use this when we need to delete ballot cards for consolidated elections for district-level ballots, when district-level reporting is not needed. In California, we need this when we have to delete non-applicable ballot cards. (Example being San Francisco's combination of bilingual + quadrilingual) ballot cards to create a single voter packet. Once a card is deleted, its activation code still exists, which can be problematic for users, as it may be incorrectly selected in ICVA. Thus, we need to consider how to handle this scenario long - term, and how to handle our short term needs. Shortterm: For the General Election, we need to know if there is any method to delete or remove activation codes for an entire set of ballots or a selection of identified ballots. Long term: We need to determine what the behavior should be (e.g. if i delete a ballot card, can the system automatically delete any associated activation codes? or can we prompt the user to see if they'd like to also delete the associated activation codes?
__________
ICR let us add multiple major categories and there is no character limit on default name which is shown on GUI on email administration. Email preview disappear which makes it non\0xAD functional and major category can not be deleted until the voting is open.
This is engineered word salad that comes across as coleslaw. Election software should never allow deleting of any files. Files should be renamed and have date and time in bedded in the file names for easy recognition. Deleting should be disabled AT THE HARDWARE LEVEL to prevent hacking attacks. Any attempt at deletion should result in a disabled system.