Nice work @James...just some queries below:
1) How do you deal with double voting? As in I may have 2-3 simcards and I vote repeatedly for my guy using each?
2) How do you deal with impersonation aka Ghost voters? Or put differently, how can you tell that a certain vote from Mrs. Walu, indeed came from Mrs. Walu and not the 'abusive' and dictator husband 'Mr. Walu'? Furthermore, Mrs. Walu perhaps preferred NOT to vote but Mr. Walu voted for her anyway.
3) How do you deal with lost phones, so cant vote. Or folks with feature phones rather than smart phones, Or forgotten passwords?
4) How do you handle the concept of 'VERIFICATION'? which is a constitutional requirement that elections must be accurate, secure and verifiable? The verifiable concept is often done through comparing the electronic output (results transmission) with the manual tally. You system seems to lack the 'manual' aspects hence the question on how you would do verifications in the event of election petitions.
walu.
From: Jambo Creative via skunkworks <skunkworks@lists.my.co.ke>
To: Isaac Kiplagat <isaac.kiplagat@gmail.com>
Cc: Jambo Creative <jamesharuunmail@gmail.com>; Skunkworks Mailing List <skunkworks@lists.my.co.ke>
Sent: Tuesday, March 7, 2017 6:59 PM
Subject: Re: [Skunkworks] Real-time election transmission
Thank you Issac. The measures i have taken is that each vote is tied to the specific device matching the registered phone number, to ensure the user can only vote once, until the poll is re-opened.
When IEBC avails their API, i'll be able to add more stringent measures, and provide more awesome features i have on hold due to lack of validated data.
For the aspirants, they will be updated, when the various political parties provide their official lineup.
I can try look into the fingerprint module as an update. The limitation would be that, not many devices have a fingerprint reader but its a very good option none the less.
Regards,