IRC/cs

This page is a translated version of the page IRC and the translation is 4% complete.

Other languages:

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.

Access

To access our IRC, you may click the little green "connect" button next to any channel below to open a web client or you can use any IRC client you wish. IRC users must remember to abide by the Miraheze Spaces Code of Conduct. Any violations to this conduct policy will result in sanctions.

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 sremiraheze.org.

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

Cloaks

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 the IRC Group Contact. To request one, please mention it in our main channel or send the Group Contact a private message.

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

Channels

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

Main

#miraheze ^connect (logs) - general discussion related to Miraheze
#miraheze-sre ^connect (logs) - channel for contacting or for requesting assistance from Miraheze Site Reliability Engineers
#miraheze-tech ^connect (logs) - channel for technical discussions relating to Miraheze, that is not requiring Site Reliability Engineers. This can be used for things such as requesting help for contributing to a Miraheze GitHub repository, talking about features or changes to an extension, or general discussion with the members of the channel, preferably technical in-nature.
#miraheze-cvt ^connect (logs) - a public channel to inform CVT members of any vandalism or spam on a wiki.
#miraheze-offtopic ^connect - off-topic discussion

Miscellaneous

#miraheze-dev ^connect - General chat channel for Miraheze Developers Wiki
#miraheze-testwiki ^connect - General chat channel for Public Test Wiki
#miraheze-ops ^connect (logs) - channel for contacting Miraheze channel operators

Feeds

#miraheze-cvt-feed ^connect - Feed channel for CVT monitoring bots
#miraheze-feed ^connect - an IRC Recent Changes feed of all public wikis
#miraheze-feed-commons ^connect - IRC Recent Changes Feed for commons.miraheze.org
#miraheze-feed-dev ^connect - IRC Recent Changes Feed for dev.miraheze.org
#miraheze-feed-login ^connect - IRC Recent Changes Feed for login.miraheze.org
#miraheze-feed-meta ^connect - IRC Recent Changes Feed for meta.miraheze.org
#miraheze-feed-test ^connect - IRC Recent Changes Feed for publictestwiki.com

For IRC Operators, please see IRC/Ops.

Logging

Some channels are logged on wm-bot.wmcloud.org. They are listed above with links to their logs.

Note: Using IRC without an IRC cloak will display your IP address to those currently in the channel at the time, so you are encouraged to request a libera.chat cloak and use SASL authentication to hide your IP address.

Poznámky

Pokud chcete napsat uživateli, který momentálně není online, můžete mu zanechat poznámku pomocí MemoServ. Až se uživatel opět přihlásí, obdrží od MemoServ soukromou zprávu s informací, že od Vás má poznámku, spolu s pokyny, jak si poznámku přečíst.

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 ChanServ pls gimme op on #libera.

Bots

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

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.
!sre - Used to get immediate attention of as much of SRE 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)