You are viewing a single comment's thread from:

RE: The Downside of Downvotes

in #hive8 days ago

Currently there is no method of countering a down vote. When/if an account reaches a rep of 10 then that account should not be able to down vote. This solves the issue of petty "I['m going to piss people off" down vote accounts like sunsetjesus. We all saw over on steem how ignoring one tiny account ended up leading to lot and lots and lots of tiny accounts.

Down votes are needed, however there is no method to counter a down vote un-like the ability to counter an up vote. There is no need for a down voter to worry if they can not be down voted or effected by counter down votes.

If the rewards are removed then what reason for creating content? What makes Hive different than Twitter or Facebook, or youtube?

If/when a down vote is issued, and if people disagree with the down vote, then the down vote needs to be able to be down voted. As an example your post has a large down vote, some people disagree with said down vote. It is supposedly the people that decide what a post is valued at, yet we have only a one way voting system. If the down vote was able to be down voted, then the value portion of the anti-down vote would then be added back into the value previously voted for. 10 people down vote smooth's down vote for a total value of 8 dollars/hive, that amount on day 7 is added back to the post value. The people have spoken up and down and settled the value where it the community agrees.

Sort:  
 8 days ago 

Currently there is no method of countering a down vote.

Technically, an upvote can counter a downvote. Not sure if you mean something else though.

If the rewards are removed then what reason for creating content? What makes Hive different than Twitter or Facebook, or youtube?

I'm talking about HIVE rewards, and moving the rewards to the second layer. LEO is paving the way for this, and it can be focused much better for the community its rewarding.

If/when a down vote is issued, and if people disagree with the down vote, then the down vote needs to be able to be down voted.

You are describing the voting mechanism as it currently is. People can upvote to counter smooth's downvote, and have done so. I don't think this post is worth $80, and I'm not mad because I got downvoted, but if people find value in it, they can upvote to assign more rewards to counter the downvote.

I will try to make it simple. With the exception of disagreement on rewards all down votes apply to the author. They have full control over what they post. What they have no control over is the amount of rewards that are voted for on their post.

Simple Idea. A post on day 7 would have received 100 on rewards. 50% going to the author and 50% to the curators. Authors share would have been 50. The post get down voted for 30. In the system I propose the curators at the top would lose curation rewards. Lets pretend the top three curators all voted at 10. They would receive no rewards and be eligible for no rewards from that post. The remaining curators would still receive a curation reward based on 20 since that is what is left.

The Author then receives the 50 reward points that prior to down votes being calculated they would have received, the 30 points removed go to the null account.

The reason the people can up vote the post after a down vote does nothing to discourage I don't like it, you, or the concept behind the post, in other words people that use the down vote as a retaliatory tool. If an automatic comment is made under the down voters name then the people can decide if the down vote was really warranted. This would probably not be able to be coded, but the people that already voted or down voted on the post would not be able to down vote the down voter, the amount of down votes received would then be added back into the post allowing the curators to receive a little bit more of a reward. It would have no effect on the Authors share of the reward as it was untouched. The down votes in excess of the original down vote would go to the null account.