Edited by ZenBalancer at 4-25-2017 19:59 |
You misread. Or misunderstood. The timeout is forum wide. The forum user can't post in any other thread within 2 minutes. If you dismiss someone's experience as incidental, because no one finds it important, then maybe you will miss the point, that could matter to users that don't tend to report things as actively.
There is no good reason to prevent posting in different threads beyond waiting 25 seconds instead of the current 120 seconds. Is there any history of bot attacks needing the 120 second time out to prevent?
I even think it's not too risky to use a different method to prevent bot attacks, to even go as far as only putting a 25 seconds timeout on posting consecutively in the same thread, not forum wide timeout. The situation with bots abusing that, can be (sufficiently) prevented by forum user group limitations.
Depending on the forum user group, recently registered and no experience with the user, such 120 seconds.timeout can be imposed for that security reason. But can be reduced depending on user group. The more the forum allowed, be more often it can be used, the more responsive users can become. As long as the servers can handle the load, and not because of usability hampering security measure to all forum users.
Edit2: and in case a less limited user group account gets abused purposefully or because of a password leak, then a second measurement can be put in its place, to prevent consecutive posts beyond 10 in a row, with a 2 minutes timeout.
There is no other forum system thus far that limited me in this way
Because.the most limiting factor was my own time, and capacity to process posts and formulate responses. We're as humans limited enough. We really don't need more limitations.
Edits: clarity + addition.