Open pajlada opened 9 years ago
:crying_cat_face:
The thought behind requiring you to fill in the information to downvote, was to prevent people from just arbitrarily downvoting legitimate tempests. Truly you can't be sure the report is wrong unless you know what it actually is.
It's a tricky situation. If you can just downvote freely, then malicious users can get together and downvote legitimate reports. With the way things currently work, they would at least have to coordinate with what they want to pretend is active.
Thoughts?
I'm going to add more logging to help track these silly votes & block them.
How about implementing downvote only but with reduced "strength"? So to fully "remove" a wrongful tempest that has 2 votes would require, say, 8 downvotes so each downvote carries 0.25 strength whereas each upvote carries 1 strength.
The easier fix would simply to find a method of blacklisting people who input too many tempests in x amount of time, or who improperly input a tempest y amount of times in a certain time frame.
Edit: There also seems to be no shortage of upvotes for the wrong tempests either, as a whole page of "Abyssal Tempest of Aberrance" has 5-20 upvotes on each one.
For now I've put in something along the lines of @ChandlerFerry's idea. We'll see how it goes.
Right now the only way to downvote tempests is by also specifying the correct tempest. In a situation like this: it's quite annoying. I'd like to generate a discussion about having a pure downvote functionality, instead of the current downvote and correct functionality.
Thoughts? Any big negatives to having that functionality?