Steve Bennett wrote:
On 7/2/06, William Allen Simpson william.allen.simpson@gmail.com wrote:
No bot or editor or administrator should be able to do more than 1 move per minute. Just reject them. That should be easy to do in software. And maybe enforcement of clearing double redirects.
Queueing moves? Eep. Why not just reject page move requests that take place within 60 seconds of the last, with no restrictions for admins?
Sorry, but that's not what I wrote in the paragraph above, "Just reject them." I'd include the same restrictions for administrators.
There are too many administrators that may be well-meaning, but skim without understanding instructions, or don't bother to fix double redirects, or are quite simply technically incompetent.
No bot or editor should be able to do more than 1 edit per 20 seconds. Just queue the edit until the time has elapsed. Of course, administrators should be able to go faster, as they may be hurrying to fix a problem.
I'd thought queuing edits would be OK, with no restrictions for administrators. Don't have any idea how hard to implement here. In my long ago database days, it was a feature that was implementable in foxbase, so I'm sure that the fancier tools of today would be easy.
Heck, these days I often have to wait half a minute to see the response anyway. But I've noticed "edits" at a rate of 2-3 per second from "normal" editors at times, and when confronted they've claimed they aren't using a bot. Maybe not, but slow them down enough that others can notice the changes and react in human time frames.
It's possible to edit at 2-3 per second without using a bot, if you open multiple tabs in your browser, and press "save" almost simultaneously in them all. I've done that on a number of occasions. Also, AWB isn't a bot, but can exhibit behaviour like that.
It might be possible, but it's not desirable in a shared environment.
And AWB is capable of running without user interaction, so it's a bot.