This is just a random idea that I wanted to get feedback on.
With Voat, one of the things we struggle with (on the backend) is the mutability of user votes (allowing a user to change previous votes on comments/submissions). When a user can change their vote (up to down or removing a previous vote) we can’t effectively deal with this data until it reaches the “archiving” phase, which is currently three months or 90 days.
If we can effectively “archive” user votes before this time we can do much more within the code base.
The idea is this:
User votes can not be changed after a 24-hour window (time period is variable, but shorter the better). This would mean that once a user has voted on a comment/submission, they are only free to change it within this window. After the 24 hours, it sticks and would be permanent.
What are the cons? How often would this be an issue? How often do you change a previous vote after 24 hours? Etc.
Let me know your thoughts on this.
This sticky will self-unsticky in a few hours.
view the rest of the comments →
MightoScrub ago
The question is how can this be exploited and to what gain? Which I have no idea about.
FullSemiAutomatic ago
As others have pointed out, a bad actor could attempt to build false consensus by editing a post/comment that had previously been received favorably to send a different message.
Itty-bitty_Tity-trap ago
How often do you check the posts you've upvoted after 24 hours?
That's why edits are timestamped
FullSemiAutomatic ago
Essentially never. I probably wouldn't be all that interested in being notified of edits either.
How about resetting up/downvoats upon edits?
PuttItOut ago
I don't see how it can be exploited but I've felt this way before... And was wrong.