Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

United.vote features #349

Open
dhyan40 opened this issue Jun 7, 2018 · 0 comments
Open

United.vote features #349

dhyan40 opened this issue Jun 7, 2018 · 0 comments

Comments

@dhyan40
Copy link

dhyan40 commented Jun 7, 2018

This is a (Feature Proposal)

馃帺 Description

I dont know how many of you are aware of https://united.vote/

I think sovereign should incorporate some of their features. It is a working model, albeit in the pilot stage.

Some good features:

  • Only one vote per issue.

Again please consider this as a serious issue -- One person, One issue, One vote. That is the basis of democracy. Of course due to computer based voting, you should be given the chance to alter or change your vote until the results are closed, counted and declared.

I still dont understand the concept of one person casting or delegating multiple votes.

Can you write a separate small section in your whitepaper why this was chosen ?

It is going to be extremely difficult to convince any authority to allow multiple votes per person for an issue if we cannot provide a sound and logical reason.

  • Very easy to add multiple proxies, You can add multiple proxies in order of rank. This is a very interesting feature.

So if your first ranked proxy does not vote on the issue, but the second ranked proxy did vote on an issue, then your vote is given to the second ranked proxy. That way you always have a guranteed vote on any issue if you chose multiple proxies.

  • Already in use in USA albeit on a pilot basis -- so it already lists the Congress candidates, shows how they voted along with their voters or against them, and even ranks them according to how they voted along with their voters or against.

For bug reports:

  • What went wrong?
  • What did you expect should have happened?
  • What was the config you used?
  • What stacktrace or error message from your provider did you see?

For feature proposals:

  • What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
  • If there is additional config how would it look

馃搶 Related issues

  • #010101

馃搵 Additional Data

  • Sovereign deployment where you found the issue:
  • Browser & version:
  • Screenshot:
  • Error messages:
  • URL to reproduce the error:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant