This page is not a policy document but an introductory guide. It refers to some actual policy documents, such as the Dormancy Policy. Please read those documents for more specifics.
這裡是存放所有維基（稱為「維基農場」）的地方。維基是一種面向協作編輯的網站，具有即時性和全球性的出版物。Miraheze 使用 MediaWiki 軟體，可讓人們編輯同一個頁面、且支持高亮、插圖、及其它特殊功能等，且能保留過去所有頁面編輯紀錄的副本，供用戶複製或取代為現有的副本。維基百科即是最具知名度的維基。
Miraheze uses MediaWiki, the same software that powers Wikipedia, which lets several people edit the same page, supports highlighting, illustrations, and special effects, and retains a copy of every page at every point in the past, which can be copied from or can replace the current copy.
Miraheze 的用戶僅能透過其用戶名作為識別。人們使用的用戶名在所有 Miraheze 維基是一致的。在註冊時，您可以建立屬於自己的用戶名。Miraheze 的用戶可以選擇透露自己的身分，但若未經他人許可就透露他人身分，則會造成嚴重的違規行為。 以下為 Miraheze 中出現的角色：
- System administrators - System administrators are responsible for the technical functioning of Miraheze and making sure everything is working as intended.
- Board of Directors - The Board of Directors is the governing body of WikiTide Foundation, a U.S. 501(c)(3) educational nonprofit who oversees the Miraheze project and has full financial, decision, and goal-making authority for the company.
- Meta Administrators - Meta Administrators are responsible for matters involving this wiki, Miraheze Meta. Meta administrators are only in charge of this wiki.
What types of wikis do you host?
There are currently 8864 hosted on Miraheze. You can see a list of some wikis at Gazetteer of wikis with an author-created thumbnail description of the wikis. Many of these wikis welcome you to read them or even make contributions. For a list of all wikis hosted on Miraheze, see Special:WikiDiscover.
Where does your logo come from?
Our logo is inspired by the old design of the MediaWiki logo and the identical nature of each honeycomb cell, symbolizing the ideal of being able to "clone" independent wikis while sharing a beneficial common infrastructure.
How do you finance your hosting?
Since January 2022, we have our own physical hardware where we host most of our servers. Our data centre which we call SCSVG is located in Stevenage, United Kingdom. Other than our own hardware, we also host cache proxy servers with OVH and ns1 (nameservers) with RamNode.
We are in the process of moving to dedicated servers located in the United States, and expect to be done by March 2024.
How do I confirm that my wiki has been created?
If you have an email attached to your account, you should get an email telling you your wiki has been created. If you don't, you should add an email to your account because if you lose your password, you'll be permanently locked out of your account. You'll also get an on-wiki notification when your wiki is created.
There are some cases where a wiki can't be created, such as when a wiki with the same name already exists, when you didn't provide enough information in your request, or when creating it is against either the Content Policy or any other Miraheze policies. In those cases, a wiki creator will inform you of that via the wiki request.
What is the initial state of my new wiki?
We will put a Main Page on your wiki, with wording (in your chosen language) that is as inviting as possible, given that no wiki member has written anything real yet. We encourage you to edit this with whatever material you want a visitor to see first.
Special:ManageWikion your newly created wiki.
What if something goes wrong when creating or visiting the wiki?
Although very rare, this can sometimes happen. Stay calm! Check your request in the Farmer log to be sure the request got into the log and was serviced. The quickest (and recommended) ways to report an issue are Phabricator, IRC, Discord, but you can also leave a message on the Community portal, or contact a system administrator. If you were shown an error message when you tried to view your wiki, or tried to take an action that should have been allowed, copy this information and include it in your report.
How do I transfer my wiki to Miraheze?
We have an entire page which explains how to transfer your wiki to Miraheze. Generally, you will need to send an XML dump to us, and an image dump if you also want to import images. Please check the page for more information.
Who owns a wiki?
Since the early beginnings of wiki communities, wikis have generally operated on community consensus. This was the case with WikiWikiWeb, the very first wiki and is also the case with all Wikimedia projects, including Wikipedia. As such, Miraheze takes the stance that wikis are owned by their community and operate based on community consensus. No single person owns a wiki and can act as an autocratic dictator.
Wikis should generally try to strive to take local users into consideration where possible. Where possible too, administrators and bureaucrats should be elected by the local community and local communities should pass policies based on a community vote and community consensus. Local administrators are sometimes afforded extra leverage when it comes to wiki governance. Some wikis sometimes pass policies and rules without consulting the community. While not the best, as long as the policy is not seriously challenged, it may stand. If the policy is challenged though, bureaucrats should not try to suppress the users in question but instead, the policy in question should go before a community vote for endorsement. Bureaucrats do have discretion though to ignore the challenge if they feel that the contesting was done in bad-faith or by a user trying to circumvent a long-standing rule for their benefit. If a matter is not resolved adequately, Stewards may intervene if requested by local users or administrators. Stewards will first analyze the wiki, it's approved scope and policies and will decide from there whether intervention is needed or not.
What is consensus?
Error: no text specified (help).
Consensus is defined by Wiktionary as "General agreement among the members of a given group or community, each of which exercises some discretion in decision-making and follow-up action."
Consensus is just that. When users come to an agreement on how a community should be run. Consensus isn't just counting votes though, it's about seeing who makes the best, most thoughtful argument. For example, imagine User A is nominated for adminiship. User B, C, and D vote in favour but give no reason why or just say "I like them". User E votes against and cites proof that User A has been rude in the past to other users, that they have very little experience, and that they are not very active. In weighing votes, User E's vote weighs much heavier than User B, C, and D's because they gave solid reason to back their opinion while User B, C, and D did not.
Bureaucrats are generally in charge of determining local consensus unless they are inactive, in which case a Steward may do that in their stead if requested. Bureaucrats should never try to override community consensus or suppress the will of the community because of personal opinions. There are only very limited sets of times when community consensus can be ignored, such as in extreme cases where the consensus would lead to a danger or instability in the community or where there are concerns with the voting process such as concerns of sockpuppetry, etc. In those cases, a Steward should be contacted to help. If the community is dissatisfied with the outcome of a decision, they may challenge it. If the community feels that consensus on any challenge was still interpreted wrong, they may contact Stewards who will attempt to mediate the issue.
What is Stewards' role within wikis?
Stewards are users elected by the global community at large to assist wikis with any issues that face them along with doing advanced tasks (such as deleting big pages, CheckUser, Oversight, assigning rights on wikis without bureaucrats, etc.) and acting as administrators/bureaucrats on wikis without active administrators/bureaucrats. Stewards try not to intervene locally where possible. If an issue can be resolved locally, Stewards try not to take any action and will try to leave it to local administrators. Very rarely (if ever) do Stewards get involved in mediating editorial conflicts unless the issue has escalated to a point where global policies like the Code of Conduct are being broken or where the issue has escalated to threats.
Stewards should not be the first people contacted when you have an issue on a wiki unless the issue is severe, and it breaks our global policies or where you feel you are uncomfortable raising an issue with local administrators because of fear of reprisal. If local administrators do not resolve an issue such as a conduct issue within a reasonable number of times, Stewards may be called in at the request of users.
Stewards are always expected to act in the community's best interests, after researching what the community is and how it works. They are not sole arbiters or dictators either. If there is an issue with how a Steward has assessed or interpreted an issue, please bring it to public attention on the Stewards requests page. Individual Steward actions are superseded by a consensus of Stewards, and even the consensus of Stewards must be informed by the will of the global Miraheze community and the policies that users have elected.
As mentioned above, Stewards act as bureaucrats on wikis without local bureaucrats. This means that they can promote or demote administrators and bureaucrats on wikis without local bureaucrats and can do other administrative tasks. Global Sysops help Stewards do some administrative tasks related to countervandalism on all wikis.
To what degree are wikis autonomous?
Much like Wikimedia, Miraheze allows for local self-rule and autonomy. All wikis are granted autonomy to act as their local community wishes, so long as they obey all global policies. Wikis are free to elect their own leaders, establish their own policies, and more. Stewards and other global officials very rarely meddle with local affairs unless requested to or a violation of our global policies occurs. Unlike other wiki farms which may forcefully take actions that go against the will of the local community, Stewards will not do that unless there is a violation of global policies.
只有該私人維基的成員、Miraheze的工作人員才能閱讀及編輯私人維基。你可以到維基的 用戶權限，輸入 Miraheze用戶的用戶名，讓用戶成為你維基團體的
If you don't see the username of the person who you want to add to your wiki, that means their account doesn't exist locally. Please ask them to visit the wiki so that our login system can create a local account for them.
Under very rare circumstances, Stewards, System administrators and Trust and Safety can check private wikis. This is almost always to ensure compliance with all global policies, legal requirements, or to troubleshoot a problem on a wiki.
主頁因為規定必須公開。但你可以藉著把主頁內容放在其他頁面（做一個「Real Main Page（真正的主頁）」），然後把主頁重定向至首頁（如下），這樣就能隱藏主頁。
#REDIRECT [[Real Main Page]]
What is ManageWiki?
ManageWiki is a special tool that lets wiki bureaucrats edit their wiki's local configuration without needing a system administrator to do it for them. It is divided into 5 sections: Core settings, additional settings, extensions and skins, permissions and namespaces. ManageWiki is a very powerful tool, so please be careful to whom you grant the right. For more information, please check the ManageWiki page.
Phabricator 為維基擁有者能向 Miraheze 系統管理員申請技術協助的系統。使用 Phabricator 的話，你就不用特地向特定某位系統管理員尋求協助（有些人很可能在度假或離開了）。Phabricator 會記得所有請求，所有貢獻者都會想辦法滿足申請者的請求。這樣可以減少你的請求被弄不見或忽視的機率。
Phabricator 為 MediaWiki（能改變你的維基頁面呈現的方式）的獨立程式，但是是由 Miraheze 管理。
你必須先登錄 Phabricator 才能使用，但如果你已經登入 Mirahezed 的話，按下有 MediaWiki logo 的按鈕就會自動登錄。
你的新維基一樣也有安裝 MediaWiki。有很多人在 MediaWiki寫了「擴充功能」，但大部份的功能在維基的預設狀態都沒有啟用。某些能啟用擴充功能很受歡迎：
- Writing alternative renderings, to be chosen at random
- 對 MediaWiki 的後設語言增加額外功能
- 幫助連結其他網站的媒體，像 Google 地圖
我要怎麼換 logo 跟圖標？
如果你不喜歡黃色和黃褐色的 Miraheze logo，且有自製作品的話，你可以把它安裝作為自己維基的 logo 或是圖示（favicon）。更多資訊請參閱ManageWiki的幫助頁面。
所有 Miraheze 的維基皆使用 Tech:Bacula來備份，但如果你是管理員，你可以在維基使用Special:DataDump 來立即取得 XML檔。圖片檔備份請聯絡系統管理員。
要讓維基在一段特定的時間內對所有人顯示唯讀（包含你自己）的話，你可以在 ManageWiki 啟用「ProtectSite（保護網站）」的擴充功能。
要讓網站對特定用戶/用戶組唯讀的話，你可以利用 ManageWiki 的用戶權限功能。
行政員為維基中擁有最高權限的人。通常需要向 Miraheze 服務人員 提出移除行政員的申請。你必須有讓人信服的理由（像行政員濫用權利，或維基對這個處理需要有共識），而不是叫服務人員在兩方的衝突中選一邊站。
我可以擁有 $oversight 或 $checkuser 權限嗎？
Stewards have the sole authority to delegate these rights to other users but generally speaking, the Steward body feels that it can handle all of these requests in a timely manner. CheckUser and Oversight may be locally granted following a local election that meets the requirements for Stewardship. Please see their respective pages for more information.
- If you require Oversight of an edit, please privately contact a Steward via email to stewardsmiraheze.org, Discord or IRC. DO NOT REQUEST THIS IN PUBLIC!
- Where CheckUser assistance is needed, you may request help on the Steward requests board in most cases. If you are not comfortable requesting help publicly, or you believe private information is involved which you should reveal, please contact the Stewards via the above methods.
I just enabled an extension or changed a setting but I don't think it is working, what should I do?
Please try turning the extension off and on again or re-saving the configuration change and then wait a few minutes. If you are still having an issue, please ask for help on Phabricator and we will try to get it working as soon as possible.
How do I change my wikis license?
To change your wikis license, you must go to Special:ManageWiki/settings and switch to the editing section. There, look for Content Licensing, click the dropdown menu below it, and select the license you want.
If you do not see your desired license, please request it to be set on Phabricator.
How do I add infoboxes?
Your new wiki starts blank, without any templates — and infoboxes are, usually, the most important ones. See this in-depth guide about infoboxes and how to create and use them.
How do I make my wiki appear in search engines?
To make your wiki indexed by search engines, like Google, Bing, etc, you'll need to register a search console on such engine, then set up a meta tag on your wiki. For more information see this guide.
A wiki is also automatically after a period of inactivity, as specified by the Dormancy Policy. Read the actual policy document rather than relying on this summary. The Dormancy Policy went into effect on 5 January 2016 and applies to all wikis.
If you have perused a closed wiki and believe you could take it further, please go to Requests for reopening wikis.
Exporting pages from a wiki, such as to a mirror site or to a host other than Miraheze, is the reverse of importing pages from another wiki onto your Miraheze wiki.
If your wiki consists of a small number of pages,
Special:AllPages list them. You can copy this list and paste it into the
Special:Export page to produce a content dump in XML format.
If your wiki is larger, Miraheze can provide assistance. You should request this assistance by opening a ticket on Phabricator.
If the target host does not use the MediaWiki software, the pages may require conversion into the format that the target host uses. Miraheze cannot help you with that.
Where can I find your configuration?
We have a GitHub organisation where we store our Puppet configuration, extensions, MediaWiki install and other code.
維基的 Config 可以在mw-config repository找到。
Why can't I access the site using HTTP?
HTTP is prone to attacks and your connection can be eavesdropped by anyone who knows how to. For your safety, we use HTTPS to secure your connection between your browser and our servers.
If you've had issues with users or wikis, there are steps you can take to settle the dispute. Please try to remain civil and calm at all times. All users are bound to the Code of Conduct. No one is above it, including wiki administrators and Miraheze's own volunteers. Incivility will not be tolerated at all.
If it's a user
If it's a wiki
- Please raise all local issues with local wiki administrators first.
- If there are still issues or if the issue involves a severe violation of our global policies, and you do not feel comfortable contacting the wiki's administrators, you may contact a Steward for help either on the Steward requests board or via email to stewardsmiraheze.org. If you are reporting violations of the Content Policy or other global policies, please make sure to include plenty of evidence.
Editorial disputes usually are not resolved by Stewards. Stewards will always defer editorial disputes to local administrators. Coming to Stewards attempting to get them to overturn a local decision will not work.