IRC/ar

للتحدث مع مستخدمين آخرين في ميراهيز في الوقت الفعلي، يمكنك استخدام بروتوكول الدردشة عبر الإنترنت (IRC) عن طريق freenode. هذه هي القناة الأساسية حاليًّا:

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 sre@undefinedmiraheze.org.

If you are banned for any reason from our IRC channels, please contact an IRC operator or email sre@undefinedmiraheze.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/) 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.

Main

 * (logs) - general discussion related to Miraheze
 * (logs) - channel for contacting or for requesting assistance from Miraheze Site Reliability Engineers
 * (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.
 * (logs) - قناة عامة لإعلام أعضاء CVT عن أي تخريب أو إزعاج في ويكي.
 * - مناقشات خارج الموضوع

خارج الموضوع

 * - General chat channel for Miraheze Developers Wiki
 * - General chat channel for Public Test Wiki
 * (logs) - channel for contacting Miraheze channel operators

Feeds

 * - قناة التغذية الخاصة لبوتات المراقبة لـCVT
 * - تغذيات للتغييرات الأخيرة عن الـIRC في كل الويكيات العامة
 * - IRC Recent Changes Feed for commons.miraheze.org
 * - IRC Recent Changes Feed for dev.miraheze.org
 * - IRC Recent Changes Feed for login.miraheze.org
 * - تغذيات RC لـIRC لـmeta.miraheze.org.
 * - IRC Recent Changes Feed for publictestwiki.com

لمعرفة مشغِّلين IRC انظر IRC/Ops.

التسجيل
قناة #miraheze مسجلة حاليًّا هنا:
 * 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 to hide your IP address.

البوتات
نقوم باستخدام بعض البوتات (بعضها مملوكة لميراهيز، وبعضها لا). قبل إضافة بوت إلى قناة ما، الرجاء سؤال المشغّل أولاً.
 * $icinga - يرسل تقارير عن الأخطاء أو الاستعادات، وهو جزء من Icinga.
 * $mhz-logbot - يعرض عناصر السجلات على Server Admin Log.
 * $rc-bot - تغذيات بجميع التغييرات من جميع الويكيات العامة إلى IRC (#miraheze-feed).
 * $wm-bot - عرض الأوامر الشخصية (مثل "good night") وغيرها، بالإضافة إلى أنها توفر تسجيلات القناة. للتفاصيل انظر [$wmbotlink this].
 * $github(قد تختلف الأرقام) - عرض حركات موقع GitHub على [$githublink Miraheze Repos].
 * $sigyn - يقتل المزعجين من الشبكة المشغلة من قبل Freenode. إذا كان البوت غير موجود بسبب 'لا مزعجين مؤخرا' وعاد المزعجون، فعليك الدخول لوضع op لاستخدام الأمر $cmd واستدعاء البوت.
 * $eir - يقوم بإدارة الساكِتِين والمحظورين، ويسجل الأسباب وفك الحظر عند انتهاء فترة الحظر. انظر [$eirhelp هنا] لمعرفة استخدامها.
 * $Void-bot - يساعد في الحفاظ على القناة، انظر هنا لمعرفة المميزات.
 * $ZppixBot - بوت يتم تشغيله (على MirahezeBots) بواسطة ومطورة من قبل ، ، و الأوامر مذكورة في صفحة المساعدة.
 * $MH-Discord - بوت للمراسلة بين ديسكورد ميراهيز والـIRC مطورة بواسطة.
 * $SigmaBot - يساعد في محاربة التخريب والإزعاج.
 * $StreamBot - يرسل تقارير بالتغييرات الأخيرة من ويكيات/صفحاتسجلات معينة لقناة معينة.
 * 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  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.
 * CosmicAlphaCVT - A bot ran and maintained by Universal Omega to help monitor spam and vandalism and report to #miraheze-cvt-feed.

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)