If you are wondering what the garbled text is below, it is the base64 encoding of a compressed election image from the Georgia Secretary of state website, concerning the early voters and absentee voters. So whatever live data is there will be stored on the chain every 15 minutes...well you'll see posts every 5 minutes, and that is an antispam feature of the hive chain-although I could have opted for comments.
This bot will not tell use who is voting for what, the GA data doesn't list that yet as far as I can tell. It just shows us the number of people who voted early, and various absentee data. I was unable to parse out the county records due to authorization errors, but a partial list of county early voters was found in the state records. Although the partial list omits DeKalb, Decatur and Fulton county, it did include Cobb.
We all know the 2020 election was stolen, but the exact mechanism of fraud isn't really understood. Those who express theories based upon solid evidence have been made example of through truly profound defamation suits or criminal sentences, where the first amendment didn't mean squat even where a speaker is otherwise entitled to litigators immunity or were otherwise seemingly performing magisterial duties mandated by federal statute that, contrary to the corrupt secretary of State, were not discretionary. The courts are corrupt, especially in Georgia... Layer upon Layer of corruption up the 11th circus.
Storing data to blockchains is one tiny step in permitting an accounting, because it offers some degree of immutability. One internet archive came under a server attack recently, but I don't know how extensive the damage was nor how decentralized they were. The records of ordinary databases can be modified or rolled back and recreated, meaning the custodian of the records can make up numbers as they go and delete the logs, as has been alleged. Hence why people demand paper hand counted ballots, not ballot images that became so corrupted no one could read nor QR codes that no [ordinary] human can read.
Although a formal tool of retrieval hasn't yet been developed, I have chosen a naming convention [not used at the time of this publication, hence testing is presently in the url] that a developer should be able to easily go through each link, given a starting date and ending date. A bot then just has to parse the data, decode the base64 format, uncompress, and then save to series of files of a developers naming convention.
