wm-bot

wm-bot is an IRC bot that is being used in several Wikimedia IRC channels, particularly developer channels. This page documents the bot. Right now the bot is running on Libera.

The bot is designed to have separate configuration for each channel, so that anyone can get it on their channel and have their own database. The bot is maintained by the user who brought it to the channel, so anyone can configure it as they want.

In case you need any help with this bot, please contact one of its operators:

• Petrb (preferred) as petan on Libera
• Billinghurst as sDrewth... on Libera
• Matthewrb as Matthew_ on Libera
• MacFan4000 as MacFan4000 on Libera
• Legoktm as legoktm on Libera

Or—fill in a ticket: [1]

In case you are a Wikimedia or Miraheze user with a Wikimedia or Miraheze cloak and you want to use this bot in a Wikimedia or Miraheze related channel, you can just join #wm-bot ^connect , where you can type:

@add #nameofchannelyouwant

This make the bot join your channel and give you admin permissions for that channel.

However, there may be some exceptional situations:

Bot is probably banned or stuck in some way. For example if you invite a bot and then use freenode's /remove command (which isn't compliant with IRC standards anyway so it makes sense the bot doesn't know it) the bot will still think it's in the channel. You can try to make it part the channel from #wm-bot by calling @part #channel. You will require to be identified with either a Wikimedia or Miraheze IRC cloak, otherwise the bot will ignore your request.

If the bot was in the channel previously and removed using @part command, it will still have the same ACL so that you won't get admin rights. Instead, the same people as before will have it. You can always contact some of the bot operators to help you in this situation.

Admin has access to all commands, the user who bring the bot to channel is always made admin unless the bot was previously parted (in that case the previous access list is preserved). This user level can be granted to anyone else using the @trustadd command (see below).

Trusted users have access to most of the commands

If you are a trusted or admin you can use command @trustadd to insert more people to access list

User list can be controlled using following commands

Display list of users for current channel

@trusted (channel) displays the trust list for (channel)

Add regex to defined level, level being one of admin, trusted. Example:

@trustadd .*@wikipedia/John trusted

Optionally, you can add a channel name to the end of the command. This will add the regex to the trust list in the specified channel. This can only be done by users with root permissions.

Delete regex, you can only delete users from same or lower access level

Optionally, you can add a channel name to the end of the command. This will delete the regex from the trust list in the specified channel. This can only be done by users with root permissions.

wm-bot supports a relay of recent changes feed directly to any channel, below is a list of commands which you can use in order to set up the bot

Requires admin rights, this command has no parameters

Disables a feed of recent changes of Wikimedia wikis in current channel. The database of pages you configured will be preserved.

Requires admin rights, this command has no parameters

Enables a feed of recent changes in current channel, you can select certain pages on selected wikis to be watched.

Requires trusted rights, this command has 2 parameters

Removes a page from list of recent changes, affects only current channel.

Example: @RC- en.wikipedia.org User:Test_page

Requires trusted rights, this command has 2 parameters

Insert a page to a feed, example @RC+ de.wikipedia.org User:Test_page would make it report changes to de.wikipedia.org/wiki/User:Test_page directly to channel.

Additionally, @RC+ de.wikipedia.org User:Test_page/* would make it report changes to any subpages (but not the primary page) of de.wikipedia.org/wiki/User:Test_page directly to channel. Note that the * wildcard can only be used on the end of the string.

See a list of existing commands for each channel, in https://wm-bot.wmcloud.org/dump/systemdata.htm (Libera) or https://wm-bot.wmflabs.org/dump/systemdata.htm (freenode (historical))

Infobot can be controlled by trusted users using following commands:

<@petan> !key is some data
<wm-bot> Key was added!
<@petan> !key
<wm-bot> some data
<@petan> !key del
<wm-bot> Deleted key
<@petan> !key is this is 1ドル
<wm-bot> Key was added!
<@petan> !key 1
<wm-bot> this is 1
<@petan> !google is https://www.google.com/search?q=$url_encoded_*
<wm-bot> Key was added
<@petan> !google some special symbols % 6 7#%#$%@
<wm-bot> https://www.google.com/search?q=some+special+symbols+%#25+6+7%#23%#25%#23%#24%#25%#40
<@petan> !google some special symbols % 6 7#%#$%@ | addshore
<wm-bot> addshore: https://www.google.com/search?q=some+special+symbols+%#25+6+7%#23%#25%#23%#24%#25%#40
<petan> !highfive act highfives $infobot_nick!
<wm-bot> Key was added
<petan> !highfive
* wm-bot highfives petan!

You can create an alias by typing !key alias key2 so that !key would display value of key2.

The aliases have lower priority than keys so you can overwrite an alias with key (it's possible to create both)

Command !key unalias removes it

Search regular expression in all values

Search key names and values for given word

You can send a private command to wm-bot like this:

/msg wm-bot @command parameter

This command let you know when specified user becomes active or online. You can use this even on users who aren't registered on the server or even on users who are online, but not active currently.

Example: @notify hashar

@seen user

Tell you when user was last seen

See help for @labs-*

Require admin rights

Insert a bot to another channel (@add #example)

Doesn't require any permission

Link to HTML dump of database and channel info (no parameters)

Create a table of channel use statistics to be included in the HTML dump accessible with @info

Stop measuring channel use statistics to be included in the HTML dump accessible with @info

(off by default)

For example if I was waiting for hashar, I could just send a private message

@notify hashar

to wm-bot and he would send me a private message whenever hashar appeared or spoke somewhere. It works even on users who are already online but idle – he then pings you when the user stops being idle.

You can also use this command to send a message to target user when they appear online (as well as notifying you)

@notify petan Hello, cool bot!

Requires admin rights

Turn on infobot for current channel

Requires admin rights

Disable infobot on current channel

Requires admin rights

Create a link to infobot db of different channel, this allows you to share infobot with other channels. If you link channel A to channel B's db, the local db of channel A will be no longer accessible, but will not be deleted. If you unlink the channel db, local db will be accessible again.

Example: @infobot-link #mediawiki will make a bot use db of #mediawiki, instead of local db.

Syntax: @infobot-link #channel

Requires admin rights

Enable shared infobot, this is necessary to execute on the channel you want to share the db of with other channels.

Requires admin rights

Remove a channel from trusted relation. This channel will no longer have access to shared db.

Requires admin rights

Insert a channel to db, that means this channel will be allowed to access the shared db for reading and writing.

example: @infobot-share-trust+ #test

this allows #test to link to infobot db of the channel where you triggered this command and to read and write into it, based on own access list.

Requires admin rights

Disable shared infobot

Requires trusted right

Insert a new string to ignore list of infobot, for example

@infobot-ignore+ seen

makes the bot ignore any commands !seen in a channel

Requires trusted right

This command remove an ignored key from list, syntax: @infobot-ignore- <item>

Doesn't require any rights

Syntax: @infobot-detail <key>

Display information about key

Requires trusted right

Make the key "raw" that means, all special words, 1,ドル 2ドル... will be displayed as they are, instead of converting to specific values, the | symbol is ignored in such a key. Only special word that is respected is $url_encoded_* and $*

Require trusted right

Syntax: @infobot-unset-raw <key>

This command undo the @infobot-set-raw

Requires admin right

example: @infobot-recovery previousdb

Recovers a snapshot—be careful as this operation removes the current database without asking, it's useful to create a snapshot before recovering some other so that you can restore the current db in case something go wrong.

Requires admin right

example: @infobot-snapshot previousdb

Creates a snapshot of current db, it is a bit clone of a database that can be restored anytime to its current status.

Requires admin right

example: @infobot-snapshot-rm previousdb

Removes a snapshot

List all snapshots for current channel

Requires trusted right

Tell you when user matching regex was last seen

Example: @seenrx ^[Pp]etan$

Tell you when the specified user was last seen, case-insensitive and doesn't support wild cards.

Example: @seen petan

Requires admin right

Turn on the seen for the current channel

Requires admin right

Turn off the seen for the current channel

Requires trusted right

Insert a new item, syntax: @rss+ <name> <url>

example: @rss+ bbc https://bbc.co.uk/rss.xml

Requires trusted right

Remove an item

syntax: @rss- <name>

Requires admin right

Enable RSS feed

Requires admin right

Disable RSS feed, doesn't remove the DB

Requires admin right

Direct method of configuring RSS feeds also obtainable by using @configure style-rss

Please note, there must be no spaces (wrong: key = value bla bla correct: key=value bla bla)

List of variables for style-rss:

• $bugzilla_assignee
• $bugzilla_component
• $bugzilla_creation
• $bugzilla_priority
• $bugzilla_product
• $bugzilla_reporter
• $bugzilla_resolution
• $bugzilla_severity

Examples:

@rss-setstyle Bugzilla [bugzilla] $bugzilla_resolution $title ($bugzilla_severity $bugzilla_priority assignee: $bugzilla_assignee created by: $author) - $link
@rss-setstyle gerrit [gerrit $name] $title - Diff: $link

Requires admin right

Start to generate public logs for current channel

By default, this feature is disabled, no channels the bot is invited to are logged, unless you enable it

Channels with logging and their logs can be found on https://wm-bot.wmcloud.org/logs/ (Libera) or https://wm-bot.wmflabs.org/logs/ (freenode)

Requires admin rights

Disable logs

Display help

You can also type @help <command> to display 1 line help for the command

Requires admin rights

Change the language for the channel—this will change the language bot will speak for all users in the channel

Example: @language en

Languages:

• cs
• de
• en
• es
• zh
• ko
• pt

Requires admin rights

Change various keys

The current value of the content of a key can be retrieved like:

@configure recent-changes-template

Note: Returns Value of recent-changes-template is: <default value> if not set.

Examples:

@configure ignore-unknown=true

Please note, there must be no spaces (wrong: key = value bla bla correct: key=value bla bla)

List of variables for style-rss:

• $bugzilla_assignee
• $bugzilla_component
• $bugzilla_creation
• $bugzilla_priority
• $bugzilla_product
• $bugzilla_reporter
• $bugzilla_resolution
• $bugzilla_severity

Examples:

@rss-setstyle Bugzilla [bugzilla] $bugzilla_resolution $title ($bugzilla_severity $bugzilla_priority assignee: $bugzilla_assignee created by: $author) - $link
@rss-setstyle gerrit [gerrit $name] $title - Diff: $link

Requires admin rights

Part current channel preserving the configuration and database

Display your user level

Requires admin rights

Disable output to a channel

Requires admin rights

Enable output to a channel

Requires admin rights

Leave channel and remove the configuration, logs and db. The data can't be recovered once removed, so please don't use this command in case you want to keep logs.

Display time of last recent change logged

Turns the last line of wikilinks in the channel to actual links using the default wiki specified in the default-link-wiki parameter of @configure.

Requires admin rights

Turns on the automatic linker in the channel using the default wiki specified in the default-link-wiki parameter of @configure.

When linker is on, every wiki link similar to [[page]] will be translated to url

Requires admin rights

Turns off the automatic linker in the channel.

Resolve instance ID / name / FQDN

Provide info for instance

List users in a project

List instances in project

Display info about user

Useful if you need to send a message to any IRC channel from Wikimedia labs

Requires admin rights

This command is useful if you need to send a message to any IRC channel from Wikimedia Cloud Services/Toolforge, but you don't want to create a bot for that. If you enable relay, anyone on Cloud Services/Toolforge will be able to send a TCP message to wm-bot.wm-bot.wmcloud.org:64835 in format of:

#channel message is here

And a bot will relay it to your channel

Simple shell script to relay "hello world" to channel #wm-bot

#!/bin/sh
echo "#wm-bot hello world" | nc wm-bot.wm-bot.wmcloud.org 64835 64835 -w0

Requires admin rights

Turn off a relay

Requires admin rights

Generate a token for your channel which needs to be provided in a message in order to relay it, example:

#channel TOKEN message is here

Requires admin rights

Disable token

It's possible to bridge messages between freenode and libera for channels with same name, there are 2 conditions:

• You need to be admin in both channels on both sides
• Network relay must be enabled (token-less) on both sides

Requires admin rights

Will relay all messages that don't start with ! or @ to other side, you can also create one-way bridge if you don't run this command on second network

Requires admin rights

Stop sending messages to other side

Requires admin

Enable optools - that let you execute @kb @jb and @kick in a channel, these commands require channel to be registered and bot needs to have +o in chanserv

Requires admin

Disable optools

Requires admin

Bot will not deop itself after op action

Requires admin

Bot will deop itself after op action

Requires admin

@kb user <reason>

Kickban a user from the channel

Requires admin

@jb user

Set a redirect ban. This is supposed to be used for people who join flood channel because of temporary connection issues

Requires admin

@q user

Quiet a user

Requires admin

@unkb user

Removes a ban of user -- bugzilla:53600 "@unkb can't unban user kicked from channel"

Requires admin

@unq user

Removes a quiet from user

Requires admin

@kick user <reason>

Kick user from a channel

Bot can echo push and commit messages for GitHub repositories to any channel. The detailed setup is below:

IMPORTANT: Channel must have relay on, so if you didn't do that yet, run @relay-on

1. Enable relay – by running @relay-on
2. Insert a repository by running @github+ <full name of repo>
3. Install a webhook (see screenshot below)

For every repository for which you wish to receive messages to your IRC channel, install a webhook to https://wm-bot.wmcloud.org/github/index.php (Libera) or https://wm-bot.wmflabs.org/github/index.php (freenode) in the settings of your repository. Make sure you set the content type to JSON, or it won't work.

Known issues: If you set up a token for channel relay, you will need to remove the repository and re-add it because tokens get added to the database only when a repository is inserted.

Requires trusted

Insert a repository full name into a database of your channel. If your repository is https://github.com/benapetr/test-100, then the full name is benapetr/test-100.

For this to work you also need to install webhook into GitHub, see above for how to do that.

Requires trusted

Removes a repository full name from the database, hooks for this repository will be silently ignored.

These commands are not useful for regular users

Require root rights

Restart the process of bot

Require admin rights

Reload configuration of the channel

Requires root

This is a low-level system command that tell a bot to unload a specific module from system

Requires root

Load a module to system

Requires root

@system-rejoin-all <instance>

Rejoins all channels on instance

Requires root

@reauth <instance>

Re-authenticates instance in IRC, including giving voice to the bots.

Requires root

@instance <instance> #<channel>

Changes default instance for a channel

• freenode
  • Data: https://wm-bot.wmflabs.org/dump/ - database of infobot
  • Channel logs (raw): https://wm-bot.wmflabs.org/logs/
  • Channel logs (sql): https://wm-bot.wmflabs.org/browser/
• libera
  • Data: https://wm-bot.wmcloud.org/dump/ - database of infobot
  • Channel logs (raw): https://wm-bot.wmcloud.org/logs/
  • Channel logs (sql): https://wm-bot.wmcloud.org/browser/

The bot will talk any language you want in a specific channel. All you need to do, is ask admin of bot to say @language <code>

You can translate the bot to your language by creating a subpage, example Wm-bot/ru for Russian. Then just translate the default English file.

Supported languages are:

• Czech cs
• Danish da
• German de
• English en
• Spanish es
• Chinese zh
• Korean ko
• Portuguese pt

Source code is in git type

gitclonehttps://github.com/benapetr/wikimedia-bot.git

to download it

In order to compile the bot, you need a C# compiler like GCS or Microsoft's CSC. Visual Studio or MonoDevelop are the recommended IDE's: they allow you to just open the project file and hit make.

This is a most simple way to build stuff on Debian:

# after you checkout the bot
cdwikimedia-bot
make

• When you build the bot for the first time, there should be a binary either in bin/debug or bin/Release (depends on if you directly invoke xbuild or use the make script). Pick one of these binaries.
• Create a folder and optionally a Unix user which you will use to run the wm-bot under as a service
• Copy the binary into root of that path, let's call it $wmibhome
• Create folder $wmibhome/configuration
• Create file $wmibhome/configuration/wmib.conf and put there following text

// This is a username for a bot
username=wm-bot;
// This password is optional and bot will use it to auth with nickserv in case you provide it
password=blabla;
// This is a root url that will be used in queries like @info
web=https://bots.wmflabs.org/~wm-bot/;
// Whether bot uses a bouncer or not
serverIO=false;
// Debug channel
debug=#wm-bot;
// Irc server bot will connect to
network=holmes.freenode.net;
// This is css style that will be used for dynamically created html pages
style_html_file=https://bots.wmflabs.org/~wm-bot/wmib/style.css;
// This is interval that bot will send messages to network server to in milliseconds, lower the interval is
// faster the bot will send messages to server. Low interval may result in k-line on some networks.
interval=800;
// Nickname for primary instance
nick=wm-bot;
// Optional mysql username
mysql_user=jimmy_wales;
// Optional mysql host
mysql_host=bots-labs;
// Optional password
mysql_pw=I_own_wikipedia;
// Name of database to store items to (by default bot doesn't use mysql, but some extensions might want to)
mysql_db=wmib;
mysql_port=3306;

• chown this file to wm-bot user and change chmod to 600, this file is dynamically updated by a bot, never write to it when bot is running
• create database of bot administrators in $wmibhome/configuration/admins example below

.*@wikimedia/Petrb|root|this is a secret password|root

These users will be globally recognized in any channel, first column is regular expression to match IRC hostname, second is user level, third is password for system console, fourth is username for system console

• now you can launch the bot (mono wmib.exe)

See admin guide at wikitech:wm-bot

• db of wm-bot in #mediawiki

• IRC bots
• Wm-bot