Imported from https://github.com/wikimedia/countervandalism-CVNBot/issues/8.

@Krinkle@github.com wrote on 23 Nov 2012:

Imported from https://jira.toolserver.org/browse/SWMTBOT-25.

Krinkle wrote on 12 September 2010:

Currently a bot can't be admin and an admin can't be bot. Currently when a botadmin does, for example, mass-blocking of open proxies (like WindAdminBot on ru.wikipedia and RonaldB on nl.wikipedia), there are a few options:

Botadmin = admin (default). Actions are parsed (Autoblacklist occurs and both the action and the list-addition are reported in the channel). The reporting in the channel causes flooding + most likely a delay in the feed (huge message stack up) and will take long for the bot to catch up afterwards (if at all).

Botadmin = bot (possible right now). Actions are not parsed because in the bot the first check in Program.ReactToRCEvent() is the is_bot-check, which, if true, returns directly. No Autoblacklist, no reporting in the channel of anything.

Botadmin = bot & admin (requested feature). Action are parsed, and a new check is added to Program.ReactToRCEvent() that will cause botadmins to be acted upon in the backend (Autoblacklist) but no reporting back to the channel (ideally of both the action and of the list-addition, but just the action will already make a significant different). Hiding the list-addition success-message aswell may require a change in the AddToXX functions and/or the listman.addUserToList() aswell.