-
Notifications
You must be signed in to change notification settings - Fork 430
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instead of flag add negative scale to upvote slider #938
Comments
How will the slider behave after a previous vote? If a previous vote was negative, defaulting to the same negative value the next time the vote button is pressed could result in accidental downvotes. At the same time, having the slider at the same value for previous upvotes is convenient most of the time, as click-click to vote is a simpler and quicker process than click-slide-click. |
@pfunks yes, I think it just shouldn't remember negative vote values. |
Currently the slider is not shown to users with less than 1 MVESTS in SP. Are there any ideas how to tackle this case? |
Not sure if we want to handle it this way, but one idea is to not allow a downvote through the UI until they reach 1 MV. Another possibility - two buttons (upvote/downvote). [Edit] If you disable downvoting for users under 1 MV, you could still give them the option to enable the slider (with upvotes and downvotes) via their settings, but just give them a boolean -100% and +100% option slider. |
What problem is this trying to solve? At first glance I really don't think we should be doing this. |
Invoking Dan's name doesn't mean we short-circuit our process and plan. That's not on our roadmap and it's not on the critical path to user growth. It's a non-problem right now. Maybe it becomes a problem in the future when we see more shitposting or trolling, but until that happens, we should be putting 100% of our effort into our growth initiatives. There will be plenty of time to tune the reputation and downvoting system later - but only if we ship the things in the roadmap first. |
I think down voting/ flagging is ridiculous. If you don't like what someone is posting, don't upvote it. That is the response to not liking something. Don't throw bricks through the window of the store you disagree with what they are selling just don't purchase anything from them. If the majority of people agree with you then the store goes out of business. Elicit content is market as such and all other content is opinion which should not be hindered upon. Honestly, people are too biased to objectively mark content as inappropriate. By which standard are we judging? Is this not similar to book burning? Down vote a persons content enough and they are not seen. And, limiting the down vote option to people with a certain vest is irrelevant. Just because someone has money does not make them objective and should certainly not give them the power to squash another persons ability to post content. Can someone please tell me why there is an option to limit another persons ability to express themselves? Why is this even a subject on this forum? |
The ability to downvote posts is built into the blockchain, and the whitepaper lists 'payout too high' (which is subjective) as a valid reason to downvote. From a UI perspective, switching the 'flag' to a downvote slider would be more in line with the way the functionality is designed and implemented at the blockchain level. There is a valid discussion to be had about the appropriateness and etiquette of flagging, but it is probably best had outside of GitHub. |
Agree with @sneak, so I'm closing this issue.. |
FWIW, there isn't. The blockchain is append-only. Even flagging is just additional speech. Flag away on whatever subjective grounds you like - but everyone reaps what they sow. This community has a memory. :) |
No description provided.
The text was updated successfully, but these errors were encountered: