SEO
Senior Member
- Jan 6, 2017
- 942
- 754
I will often open all of the spammy threads that I see in the recent threads list and begin reporting them. One of the problems I run into is the delay on actions.
It would be great if there were a way that the forum could decrease the amount of needed wait time based on something (number of posts, number of likes/post ratio, % of confirmed threads reported as spam, etc).
At the moment, I just wait for the time to expire, but if I have to report 5 threads, that can take a fair amount of wait time and if I move on to something else and I forget, then the thread might not be reported for a lot longer.
I know having this velocity increase mechanism in place could leave it open for someone to abuse it, but I think the amount of benefit you'd get from it overall would out-weigh the few times someone would abuse it each month/year. Just thought I'd make this suggestion as I would think you'd not want to deter people from reporting threads (for the most part).

I know the timer above is only on 2 seconds, but that's because I decided to take a screenshot a bit after I got the error, so I triggered it again.
It would be great if there were a way that the forum could decrease the amount of needed wait time based on something (number of posts, number of likes/post ratio, % of confirmed threads reported as spam, etc).
At the moment, I just wait for the time to expire, but if I have to report 5 threads, that can take a fair amount of wait time and if I move on to something else and I forget, then the thread might not be reported for a lot longer.
I know having this velocity increase mechanism in place could leave it open for someone to abuse it, but I think the amount of benefit you'd get from it overall would out-weigh the few times someone would abuse it each month/year. Just thought I'd make this suggestion as I would think you'd not want to deter people from reporting threads (for the most part).
I know the timer above is only on 2 seconds, but that's because I decided to take a screenshot a bit after I got the error, so I triggered it again.
Last edited: