Awesome! A long time needed Feature on the Hive Blockchain and i like the Solution to bring it to the Protocol so other Dapps/Frontends can easily integrate it in to their application.
Some ideas i directly i have in mind for the filters to widen up the range of usecases:
- filter up by reputation i.e: only accounts with reputation over 30 can vote
- filter up by dapps: i.e: Splinterlands Polls - people can only vote if they are currently in the Champions League in Modern - or Accounts can vote if they have a bought Spellbook - or participating in Brawls, Land, Conflicts...
- filter up by Post-Vote i.e: Count a Vote if a Vote on a Post was already made
- filter up by HE-Pools i.e: if you are a liquidity provider in a given pool.
cant wait to play with it / try to break things. hit me up for testing guys!
Awesome!!!!
Edit: Maybe add up a Pre-Check if the User met all the Requirements before posting the json to chain.
Edit 2: Filter Up by Follower. People can only Vote if they follow you.
Edit 3: People can only vote if they were active in the last 30 days in a specific community.
I agree that it sounds very interesting, but in my eyes HIVE reputation hasn't any meaning at all.
Or also (and maybe most of the time more reasonable) if YOU follow THEM ... (otherwise everybody could just decide to follow you for a minute, vote, and then unfollow you again - of course you could set a criteria of a min duration of following you).
Most important, however, is that there will be poll options in which not only money matters - so I fully agree with you that it could become a very nice tool.
Indeed. One possibility will be that anyone can create a token and distribute it according to whatever algorithm or system they desire to use or to experiment with. This will then become the voting power or decision-making influence that people have. This can perhaps help us find other paradigms beyond proof-of-work and proof-of-stake (even if technically you have staked a token, you may have received it not because you locked in money but because you e.g. made a certain kind of contribution that was recognized by the community).
Great suggestions, thank you. Some will be more difficult to do than others.
Do you mean that if someone upvotes the post, then the upvote would count as a vote on the poll?
Yes, it would be good for better user experience if the frontend can let the user know if all filter requirements are met, or if not, which ones aren't. But, of course, we cannot prevent users from posting a custom_json if they want to do it manually. If it doesn't meet the filters, we will just ignore the custom_json.
All of these filters would have to be done at a level outside the blockchain: The application backend or the application front-end.