https://bugzilla.wikimedia.org/show_bug.cgi?id=17929
--- Comment #12 from Quentinv57 <[email protected]> 2012-03-03 13:17:14 UTC --- I've put the priority to normal, as suggested above. We're now waiting for three years. It would be very nice if this could be processed, even if I agree that it would be time-consuming for developers. But the time you will spend doing this is insignificant regarding the time stewards have lost due to this for now. As Marco Aurelio said above, this will be an amazing gain of time. Now, when stewards want to globally block a crosswiki vandal, they have to perform the following operations : 1- lock the account 2- give themselves the CheckUser status locally 3- check the user IP 4- block the IP globally 5- remove themselves the CheckUser status 6- lock and delete the stuff the vandal has spread between the time the account has been locked and the IP globally blocked If we had an auto-block that works, we would no more have to perform the last five points. The gain of time is at least 80%. Moreover, some vandals know we can't perform checks on projets with local CheckUsers. Indeed, the steward policy forbids us to do this. So sometimes they play with us creating multiple accounts to vandalize, and move from a wiki with local CUs to an other. And we have to wait sometimes for dozens of minutes that a local CheckUser is available to perform the check and to globally block the IP. I hope I was convincing enough. Thanks for your understanding. Quentinv57 -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
