Page MenuHomePhabricator

Special:MultiLock to implement flood setting at meta
Closed, ResolvedPublic


When stewards using the lovely new tool [[m:Special:MultiLock]] we can be blocking a large number of spambot accounts. This has an impact on [[m:Special:RecentChanges]] in that a large number of accounts.

It would be useful to either automagically implement the existing flood flag when using this tool, or look to have the ability to toggle on flood flag for the time of the multiple lock.

Version: unspecified
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:25 AM
bzimport set Reference to bz47491.

Related URL: (Gerrit Change I225308fd939e1383c1e774ee806d159d7ca701cb)

Change 60282 merged by jenkins-bot:
Allow MultiLock users to use a temporary bot right for RecentChange entries