>>24837998

How would you know if your paper ballot was ever counted, burned, or thrown in the garbage? You will never know. With this application, if you vote was ever changed by any nefarious means, it would generate a new encrypted hash and you would know that your vote changed by two ways. 1. You do not get back your ballot, obviously. 2. As part of the counting application, the app would show what number you were in the vote count, (ex vote 1001 out of 10 million) and the tail end of your encrypted hash, say 50 numbers out of 4096 characters, which is enough to show uniqueness. But there are other ways of doing this too, This is the concept of UUIDs, which are unique enough to not duplicate a serial number 1 in 47 billion.

>>24838040

>and the tail end of your encrypted hash

Understand that this is not a number of just digits alone, but a string of characters pulling from a pool of up to 64k characters, depending on implementation but even hexadecimal values are strong enough 1-9 and A-F for 10 to 16.

>>24837882

>>24837998

>>24838059

Remember, this ballot application was just a side affect to what the software can really do. It wasn't built specifically for ballots alone, but any type of dynamically created data driven apps. All this is is really that, an application that builds applications, but in this case, it calls a assigned function when a button is clicked that calls the security encrypting function. It could just as easily post to a backend database, send an email or SMTP call, or whatever I give or allow it.

But here is the big question, does anyone give a damn?