IRC

From Meta
Jump to navigation Jump to search
This page is a translated version of the page IRC and the translation is 7% complete.
Outdated translations are marked like this.
Other languages:
English • ‎català • ‎español • ‎français • ‎italiano • ‎magyar • ‎português do Brasil • ‎sicilianu • ‎svenska • ‎اردو • ‎العربية • ‎हिन्दी • ‎বাংলা • ‎中文(中国大陆)‎ • ‎中文(台灣)‎ • ‎日本語

Per parlat amb altres usuaris de Miraheze a temps real pots connectar-te a través de Internet Relay Chat (IRC) a la xarxa IRC freenode. Actualment aquest és el canal principal:

Canals

Equip contra el vandalisme (CVT)

Offtopic

Miscellaneous

MirahezeBots project channel

For IRC Operators please see IRC/Ops.

Access

Access with open proxies, web hosts, and/or VPNs are automatically banned, by MirahezeBot, from certain IRC channels. This is because of our open proxies policy. If you would like to request an exemption, please email tech(at)miraheze.org.

Logging

Some channels are logged on wm-bot.wmflabs.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 use an IRC client like IRCCloud, which provides you a complimentary cloak upon creating an account

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 effect 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)

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. New in #T5397
  • MirahezeRCBot - feeds recent changes from all public wikis to IRC (#miraheze-feed)
  • wm-bot - displays personalized commands (i.e. "good night") and others. Also provides channel logging. For details see this
  • not-* (numbers can be different) - displays GitHub actions on the Miraheze Repositories
  • Void-bot - Helps maintain channel, see here for features
  • MirahezeBot - A bot ran and maintained (on MirahezeBots) by Void, RhinosF1, and Reception123, command listing is found by .help
  • MH-Discord - Relays messages between IRC and Miraheze's Discord.
  • SigmaBotMH - Helps combat spam and vandalism. Deprecated; superceded by the CVTfeed plugin included as part of MirahezeBot
  • 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.