We had (I think) our first "wild admin" incident today: Robdurbar suddently went beserk.
http://en.wikipedia.org/w/index.php?title=Special:Log&limit=25&offse... http://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Inciden...
13 minutes later it was all over, and would have been even quicker if anyone on IRC at the time had happened to remember the name of the channel where the stewards hang out.
On 4/19/07, Earle Martin wikipedia@downlode.org wrote:
We had (I think) our first "wild admin" incident today:
Not true. Although things are more clear cut this time
Robdurbar suddently went beserk.
http://en.wikipedia.org/w/index.php?title=Special:Log&limit=25&offse... http://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Inciden...
13 minutes later it was all over, and would have been even quicker if anyone on IRC at the time had happened to remember the name of the channel where the stewards hang out.
In future you might want to consider that repeated blocks every few seconds will in effect make an admin account inactive as far as deletion is concerned.
Huh. Sorry I wasn't there to help out. =\
If you're quick, I think you only really need two or three local people to deal with it. One admin keeps the interloper blocked, a second admin undoes any blocks by the interloper, and a third user goes running to the stewards ASAP. Depending how many people are available, more can watch the interloper's deletion and protection logs, reverting as needed -- one quick person per log seems the way to go, avoids confusion and keeps them outnumbered.
That at least seems like it might work? The problem would be getting those people together and organized on very short notice.
But then, I've never dealt with this sort of thing on that sort of scale, so... -Luna