opticod-007 on master
Update CNAME (compare)
opticod-007 on master
Update CNAME (compare)
opticod-007 on master
Create CNAME (compare)
opticod-007 on master
Set theme jekyll-theme-cayman (compare)
opticod-007 on master
Set theme jekyll-theme-slate (compare)
opticod-007 on master
Delete CNAME (compare)
opticod-007 on master
Update CNAME (compare)
opticod-007 on master
Update CNAME (compare)
opticod-007 on master
Update CNAME (compare)
opticod-007 on master
Update CNAME (compare)
arnabdasbwn on master
Updated README.md (compare)
opticod on master
Initial commit Merge pull request #1 from IamR… (compare)
Here comes an opportunity for you to work on open-source and open-hardware projects extending from Embedded Systems to Android. Participate in Google Summer of Code 2018 with our organisation and make the world a better place. We have applied to GSOC 2018 as a mentoring organisation.
Here are the Ideas Posted >>
We are also open to new breakthrough ideas and potential mentors.
For More Info on Ideas Please Visit http://brofoss.org/
GitHub: https://github.com/BroFOSS
Hello there @opticod. I was thinking of creating API endpoints. This way, a central server for handling the voting data can be established, reducing the effort of building a server twice, once for web app and once for mobile app.
And regarding cryptography, I was thinking of using GPG encryption.
And regarding cryptography, I was thinking of using GPG encryption.
@opticod It can be generated on client side on creation of new account and the user data and the public key associated will be stored on the server. And since the key creation is on client side, the user will have to store the private key. And when the user is voting, he'll have to enter his private key which will be used to sign the message containing the voting information to be sent to the server.
May be you can suggest a better way out?