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 →
ggolemg ago
24 hours from the initial per-user vote cast and not 24 hours since the post posted?
PuttItOut ago
Yes, time period would start from the point the vote was recorded on a user by user basis. Content would allow new votes up until the main archiving process kicks in.
Thisismyvoatusername ago
And just like that, my only question was asked and answered. As long as it doesn't affect how long people can vote on a post or comment (as opposed to changing a previous vote on that post or comment), this change sounds fine to me. The rare case where people really want to go back farther than that because of new information or something could be dealt with by them making a new post to get revised takes on it.