From Miraheze Meta, Miraheze's central coordination wiki
Revision as of 18:07, 8 May 2024 by FuzzyBot (talk | contribs) (Updating to match new version of source page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

There are various ways to connect with other Miraheze users and volunteers in real-time. One of these ways is to connect with us via Internet Relay Chat (IRC). Miraheze has an ample presence on the Libera.Chat IRC network. There, you can talk with all our volunteers and solicit help or discuss particular topics.

Many IRC channels are also relayed to our Discord server so if you're on Discord, there is no need to connect to our IRC channels to receive assistance in certain channels and vice versa.

Please remember that the Miraheze Spaces Code of Conduct applies to all off-wiki spaces, including IRC.


Many of our IRC channels are moderated by designated IRC operators but some channels may have different operators depending on their purpose (for example, a feed channel for a wiki may have local wiki administrators as operators and not system administrators and so on). If you have any questions, please contact them.

Access with open proxies, web hosts, and/or VPNs may be banned from certain IRC channels. This is because of our open proxies policy. If you would like to request an exemption, please email

If you are banned for any reason from our IRC channels, please contact an IRC operator or email


If you are a Miraheze user in good standing with an on wiki account, you may request a Miraheze IRC cloak (in the form of @miraheze/<Username>) from one of the IRC Group Contacts. To request one, please mention it in our main channel or send a Group Contact a private message.

If a cloak holder engages in behavior which reflects negatively on the project and is unbecoming of a volunteer, they may have their cloak revoked without warning.


This is a general directory of IRC channels of importance. This doesn't reflect all IRC channels which exist in the #miraheze namespace.




For IRC Operators, please see IRC/Ops.


Some channels are logged on They are listed above with links to their logs.


If you want to talk with an user but they aren't currently online, you can leave them a memo using MemoServ. MemoServ will DM the user informing them that they have a memo from you when they log in, along with instructions on how to read the memo.

Send HELP to MemoServ through DM (for example /msg MemoServ HELP) for a list of commands. To send a memo, send SEND <IRC username> <content of the memo> to MemoServ via DM. For example: /msg MemoServ SEND IRCGroupContact hey, could I have one of those miraheze cloaks?.


There are some bots that we use (some are owned by Miraheze, some are not). Before adding a bot to a channel, please ask an operator first.

  • icinga-miraheze - Reports issues and recoveries. Part of Icinga
  • MirahezeLogBot - Logs items on Server Admin Log
  • MirahezeLSBot - Relays log items issued directly from the server by the system administrator to IRC from their issuing the logsalmsg command. MirahezeLogBot, in turn, logs the items to the Server Admin Log.
  • MirahezeRCBot - feeds recent changes from all public wikis to IRC (#miraheze-feed)
  • wm-bot - displays personalised commands (i.e. "good night") and others. Also provides channel logging. For details see this
  • botifico - displays GitHub actions on the Miraheze Repositories
  • Void-bot - Helps maintain channel, see here for features
  • MirahezeRelay - Relays messages between IRC and Miraheze's Discord.
  • StreamBotMH - Reports recent changes from specified wikis/pages/logs to specified channels.
  • litharge - Manages quiets and bans, logging reasons and un-bans when given date expires.


Stalkwords are words that can be used to get the attention of an entire group of people in an emergency.

  • !ops - Used to get immediate attention of channel operators in the event of an active situation requiring moderation powers on IRC.
  • !tech - Used to get immediate attention of as much of the Technology team as possible in an emergency. Please note that this is only to be used when an issue requires that as many people as possible get on an issue. This may at some point trigger SMS notifications and be used to wake up people / alert in a very spammy way. Incidents that require this ping should affect the entire farm and a significant proportion of users. (Cache proxy down, Database failures affecting a whole cluster, 502/3s lasting more than a few minutes etc., inability to edit despite logging in/out for all users)