FAQ/zh-cn

欢迎来到 Miraheze ，我们很高兴您来到这里！本页回答了用户可能遇到的一些常见问题. 如果你有任何进一步的问题，请在社区论坛提问.

此页面不是方针文档而是介绍性的指导文档. 但该参考引用了一些方针文档，例如休眠方针. 若要更加了解实际方针，请阅读这些文档.

常规


这里是什么地方？
这里是一大批的维基的集合（“农场”）. “维基”是面向可协作编辑的网站，可供以全世界即时使用. 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维基技术上的操作运行以确保一切都不出差错.


 * 董事会 - 这是 Miraheze Limited 的行政部门. 目前，它维持着公司的全部财务、决策和目标制定权限. 目前有 2 位董事.


 * 元维基管理员 - 他们的义务来负责管理本维基——“元维基”的事务. 元维基管理员只负责管理元维基本地上的维基事务.



这些维基是什么
Miraheze维基目前一共有个不同的维基. 您可以在维基名录查看本网站上的一些维基以及由其使用其作者撰写的简短描述. 这些维基上很多都是可供您阅读甚至是也可让您作出编辑的贡献. 至于有关所有维基上的目录您可参阅Special:WikiDiscover所举出的列表.

There are currently 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.



为什么叫做Miraheze？
如果有兴趣了解的话，Miraheze这个名词是由刍藁增二（Mira）以及角宿二（Heze）拼接而成，两者都是恒星的名称.

为什么不这样叫呢？顺便一提，很多人对 Miraheze 的发音 亦不相同.



业务模式


你们如何为自己的维基托管项目提供资金？
Miraheze维基是一个非盈利的组织并完全依靠于其他人的捐赠. 我们没有广告，也没有公司或政府的资助，因此我们依靠的是捐赠者. 更多详情请参阅捐赠以及财务的信息.



为什么无广告？
人们不喜欢广告，而且广告不会比捐赠带给我们更多资金（广告可会促使多数人停止对我们的捐款），广告可会泄露我们的隐私，而且广告也会增加我们迫于广告商压力而调整维基上的内容的风险. 因此我们捍卫我们编辑以及各个维基上编者们的独立性.



我该如何向Miraheze捐款？
Miraheze目前支持所有PayPal所支持的付款方式. 你可以点击这里或直接将捐款发送至. 要了解更多信息，请参阅捐款页面或联系Owen.



我可以用其他方式支持你们吗？
我们非常愿意！请参阅支持以获取更多信息.



你们有多少个服务器，而且你们的服务器位于哪里？
自2022年1月起，我们拥有了自己的物理硬件，可用于托管大多数服务器. 我们的数据中心（被称为SCSVG）位于英国的斯蒂文尼奇（Stevenage）. 除了物理硬件，我们还使用缓存代理服务器，托管于OVH和通过RamNode托管的ns1（nameservers）.

You can see more information and documentation about each of them on our list of servers and on their specific pages



属于你自己的维基


我该如何申请维基？
首先要创建一个账户并登录，然后前往Special:RequestWiki并填写表单.



如何确认是否已经创建我的维基？
你的申请应该已经出现在农场日志和Wiki申请队列上了. 当有人接受你的请求并创建你的维基后，也应该会在农场日志上显示. 此外，你会在请求被接受或拒绝后收到通知.

You can also track your request via the request wiki queue. The Farmer log also displays a log of all wiki approvals and rejections.

在某些情况下维基无法被创建，例如已存在同名维基、没有在请求中提供足够的信息或创建的维基违反了内容方针或其他Miraheze方针政策. 在这种情况下，你会在你的用户讨论页上收到建议和提醒.



我的新维基的初始状态是怎样的？
鉴于没有维基用户写下一些内容，我们会使用您选择的语言创建一个首页，并尽可能留下吸引人的话. 我们鼓励您在这里写下任何您希望被访问者首先看到的文字.



如果出错了该怎么办？
很不幸，这种情况时不时会发生. 保持冷静！请在农场日志确认你的请求在记录中并经过了处理. 最迅速（也是推荐的）报告问题的方法是Phabricator或IRC、Discord. 但你也可以在Community noticeboard上留言或是联系某位系统管理员. 如果你在尝试查看你的维基或尝试进行某项本应可行的操作时见到了出错信息，请将对应的信息复制下来并附到你的报告中.

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 analyse the wiki, it's approved scope and policies and will decide from there whether intervention is needed or not.

What is consensus?
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 favor 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 more 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.

监管员是由全域社区选出的用户（而不是Miraheze公司的全职员工），负责协助维基站点解决它们所面临的任何问题，同时执行高级任务（如删除大量页面、访问用户查核、监督、在没有行政员的维基站点上分配权限等），并在没有活跃的管理员/行政员的维基站点上充当管理员/行政员. 监管员在可能的情况下尽量不在本地进行干预. 如果一个问题可以在本地解决，监管员尽量不采取任何行动，并将其留给本地管理员. 监管员很少（如果有的话）参与调解编辑冲突，除非问题已经升级到违反行为准则等全域方针的程度，或者问题已经升级到威胁.

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 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 amount 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' noticeboard. 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 have the ability to 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, again, unless there is a violation of global policies.

Do note though that while communities are autonomous, they are not independent. All wikis are subject to our global policies and are subject to British law. Some wikis erroneously get the idea that they are not subject to our Privacy Policy, Terms of Use or anything else. That is not the case. Miraheze has policies that were elected by users and legal obligations so while wikis are free to do as they wish for the most part, they must follow our global policies.



私密维基
<span id="How_private_is_a_private_wiki?">

一个私密维基有多私密？
私有wiki只能被其成员（members）访问和编辑（Miraheze监管员、系统管理员和信任与安全也可以，但只有在必要时才会这样做）. 你可以访问您的wiki的Special:UserRights，输入任何一个Miraheze 注册用户的用户名，将其加入您wiki的 的用户组

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 tell 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.

<span id="Why_can_everyone_see_the_Main_Page_on_my_private_wiki?">

为什么所有人都可以看到我的秘密维基的首页？
根据规定，首页一直都是公开的. 你可以通过将首页内容放到其它地方来绕过此规定（比如命名为“真正首页”，然后将你的首页重定向至此：
 * 1) 重定向 真正首页

<span id="Wiki_management_requests">

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 who you grant the right. For more information, please check the ManageWiki page.

<span id="What_is_Phabricator?">

“Phabricator”是什么？是个人吗？
Phabricator是一个系统，维基的拥有者可以通过这个系统向系统管理员寻求技术帮助. Phabricator意味着您不再需要将请求单独提交给某个系统管理员，也不必再担心这个人在休假或已经辞职的可能性. Phabricator会记录请求并且让任何一个志愿者都能去满足这个申请. 它让请求丢失或被忽略的可能性降低.

Phabricator是独立于Mediawiki软件之外的独立程序，提供了您维基的网页，但仍然受Miraheze控制.

Please check out the Phabricator page for a guide on how to sign in to Phabricator. Generally, it's pretty straightforward. In the sign in page, click the MediaWiki logo to be signed in to Miraheze.

<span id="Why_does_my_wiki_not_have_the_same_features_as_other_wikis?">

我还可以使用哪些技巧？
All new wikis feature an ordinary vanilla MediaWiki installation which may lack the feature you're looking for. Many people have written extensions for MediaWiki which extends MediaWiki and adds new features but most of these, by default, are not enabled on new Miraheze wikis. Some popular extensions enable:
 * Additional functions in the MediaWiki meta-language
 * Assembling lists of pages on your wiki, which can be inserted into a page
 * Helpful ways of linking to additional media from other websites, such as Google Maps
 * Translation of pages
 * Usage of a social profile system

The page Extensions describes extensions that are pre-enabled on your wiki, extensions you can enable yourself via ManageWiki, and extensions we won't add for privacy and other reasons. Check that page out to see how to request extensions not in ManageWiki.

<span id="How_do_I_change_my_logo_or_favicon?">

怎样更改维基的图标？
Please check out the ManageWiki help page for details on how to make the change.

<span id="How_can_I_get_a_custom_domain_for_my_wiki?">

怎样得到我的维基的自定义域名？
If you don't want your wiki to use a  subdomain, you can request we change the domain name to any domain you own and point to us. Please see Custom domains for more information.

<span id="How_do_I_get_a_backup_of_my_wiki?">

怎样获得我的维基的备份？
If you are a local administrator, you can go to Special:DataDump on your wiki and request a backup.

For more details, please see Backups.

<span id="How_do_I_make_my_wiki_read-only?">

怎样使得我的维基只读？
For making your wiki read only from everyone (including yourself) for specific periods of time you can enable the "ProtectSite" extension in ManageWiki.

For making it read-only to specific users/groups only you can utilise the ManageWiki/permissions feature.

How can I remove a bureaucrat from my wiki?
Bureaucrats are the highest-ranking officials of a wiki. If you wish to remove a bureaucrat, please request that on the Stewards' noticeboard. You must have a valid reason, such as abuse, resignation, or there must be consensus in the wiki to do so. The Steward will want evidence (such as specific edits) that shows you are not just asking them to take one side in a clash of personalities.

Bureaucrats can also change ManageWiki permissions to empower them to remove other bureaucrats, including you. Note that this change should not be done without community consensus. If Stewards feel a bureaucrat demotion was unjustified, they reserve the right to revert the demotion and may take local action to resolve any issues.

Can I use CheckUser and Oversight?
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 stewards@undefinedmiraheze.org, Discord or IRC. DO NOT REQUEST THIS IN PUBLIC!
 * Where CheckUser assistance is needed, you may request help on the Stewards' noticeboard 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.

<span id="Closed_wikis">

关闭的维基
<span id="How_does_a_wiki_close?">

维基是如何关闭的？
A wiki closes (becomes inactive) when you go to  and tick the Closed button. It is reopened when you return to  and uncheck this button.

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.

<span id="How_do_I_move_my_wiki?">

怎样移动我的维基？
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,  lists them. You can copy this list and paste it into the  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.

杂项
<span id="Where_can_I_find_your_configuration?">

我可以在哪里找到配置？
We have a GitHub organisation where we store our Puppet configuration, extensions, MediaWiki install and other code.

The config for wikis can be found in the mw-config repository.

<span id="Why_can&#039;t_I_access_the_site_using_HTTP?">

为什么我不能够使用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.

<span id="I&#039;ve_got_an_issue_with_a_user_or_wiki">

我遇到了关于用户或维基的问题
如何你不幸遇到关于用户或者维基的问题，按照以下步骤来解决. 请始终确保保持文明和冷静.

<span id="If_it&#039;s_a_user">

如果是用户

 * 1) 讨论.
 * 2) 提起给管理员. 如果仅在本维基（meta.miraheze.org），可以使用Administrators' noticeboard.
 * 3) 如果没有解决，可以阅读Code of Conduct. 如果是个CoC问题，可以发邮件给conduct[at]Miraheze[dot]org.

<span id="If_it&#039;s_a_wiki">

如果是维基

 * 1) Please raise all local issues with local wiki administrators first.
 * 2) 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 Stewards' noticeboard or via email to stewards@undefinedmiraheze.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.

Is Miraheze toxic?
No, Miraheze is not toxic. Toxic communities are not allowed according to our Content Policy and previous wikis which became toxic have been closed and subsequently deleted.

If you believe a wiki has developed in such a way as to be characterised as toxic please report it to us.

<span id="Still_have_questions?">

仍有问题？
如果你仍有一些FAQ没有回答的问题，请随时去社区公告栏提问或联系我们.