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 →
SandHog ago
One downside is that someone could go back and edit their comment so that the voats would reflect the opposite of what the people voating on the comment intended. I would probably make it longer than a day. I'd suggest three days or something along those lines since the conversation will likely have moved on by that point.
pepe16 ago
This has little to do with vote mutability. Say someone changed a post after 10 days. It's long gone from the new queue, maybe it's in the top queue. Even if someone changes their comment, it's not like many people will notice this, go back, and change their vote. So, the issue has little to do with vote mutability.
DeliciousOnions ago
They're not the same issue but they're directly related, one causes the other to be worse.