Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement support for adminbots #8

Closed
Krinkle opened this issue Nov 23, 2012 · 1 comment
Closed

Implement support for adminbots #8

Krinkle opened this issue Nov 23, 2012 · 1 comment

Comments

@Krinkle
Copy link
Member

Krinkle commented Nov 23, 2012

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.


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

  • Reporter: Krinkle
  • Created: 12 September 2010 21:48:49
@Krinkle
Copy link
Member Author

Krinkle commented Jan 16, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant