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
By date overload #601
Comments
Technically a website issue but I'll leave it open because it seems important. We have some warnings right now when this happens, but it still requires a moderator to manually do something about it. I don't see any warnings, or any users in particular that published a lot of saves. I see some bad junk saves, but that's normal. Which users were doing this? I disagree with the limits you're suggesting here, they are way too low. It shouldn't take into account number of views / votes when deciding whether to allow more, it should just be a plain limit on number of saves per time period. There could probably be separate limits like 1 new save per minute, and 10 new/reuploaded saves per 20 minutes. Would need to consider the exact numbers a bit more. |
I don't know how to deal with this other way. Maybe changing second page, to something like fp but faster changing, with saves staying max for~1-2days, but I'm not sure it can deal with this. And about user there are some who puts few saves per day, with under 50 views. Like today Jasper1010 or Osolar3. |
Closing because not a game issue, but a website issue. (Yeah I changed my mind about leaving this open lol). Also because I had more drive to fix this issue back then, but my priorities have changed since then and it's unlikely I'll be able to do anything soon. |
I've noticed there is a lot of spam saves in by date section, we got 5 pages in few hours. That fast make good saves hard to find, and some of them got only few views.
A lot of weak saves are created by 1-3 users. To prevent it can be added some daily limit of saves published(1-2?). Of course if user save gets lots of +1/views/fp he can post more.
The text was updated successfully, but these errors were encountered: