FAQ/ko

Miraheze에 오신 것을 환영합니다. 우리는 여러분이 여기로 찾아온 것이 기쁩니다! 이 문서는 사용자들이 궁금해할 법한 자주 묻는 질문 몇개를 답해드립니다. 만약 더 묻고 싶은 점이 있다면, Community noticeboard에서 물어보세요.

이 곳의 내용은 정책에 관한 것이 아니라, 소개하기 위한 안내서 입니다. 일부는 비활동 정책처럼 실제 정책에 대한 내용도 참조하고 있습니다. 자세한 내용은 해당 문서를 확인해 주세요.

기본적인 질문들


무엇을 하는 곳인가요?
Miraheze에 오신 것을 환영합니다! Miraheze는 모든 주제의 다양한 위키를 호스팅하는 위키 팜입니다. 우리는 많은 위키를 호스팅하지만, 공식적으로 운영하지는 않는다는 점을 명심하세요. 만약 특정 위키의 지역 정책에 관해 궁금한 점이 있다면, 지역 위키 관리자에게 연락해 주세요.

Miraheze는 수많은 사람들이 같은 문서를 편집하고, 강조표시와 삽화, 특수 효과, 그리고 현재의 판으로부터 복사하거나 현재의 판을 교체할 수 있는 과거의 모든 시점의 모든 문서의 판을 간직할 수 있는 위키백과를 구동하는 소프트웨어와 동일한 미디어위키를 사용합니다.

저희는 변함없이 우리 사용자에 대한 약속을 7년 넘게 지켜오고 있습니다. 자세한 정보는 대문을 확인해 주세요.



Miraheze는 누가 운영하나요?
많은 회사나 프로젝트와는 달리, Miraheze는 공식적으로는 서비스를 운영하는 "직원"이 없습니다. 그 대신에, Miraheze는 자원봉사자들이 위키 팜의 일상적인 운영을 관리하고 있습니다. 아래에 중요한 점 몇가지가 있습니다:


 * 사무장 - 사무장들은 공동체 역할의 최상위 계층에 있는 사용자입니다. 이들은 전역 공동체와 모든 전역 위키 동작의 문제에 대한 책임이 있습니다. 예를 들어, 지역 관리단의 조치로 해결하기 어려운 파괴적인 행위는 사무장에게 맡길 수 있습니다. 당신은 Stewards' noticeboard에서 이들에게 연락할 수 있습니다.


 * 시스템 관리자 - 시스템 관리자들은 Miraheze의 기술적인 부분을 담당하고 모든 것이 정상적으로 작동하는 것을 보증하는 사람들입니다.


 * 이사회 - 이사회는 Miraheze 유한회사의 관리 기관입니다. 현재는 법인의 모든 재정, 의사 결정, 목표 설정 권한을 갖고 있습니다. 현재 3명의 이사가 있습니다.


 * 메타 관리자 - 메타 관리자들은 이 위키, Miraheze 메타에 대한 일을 담당하고 있습니다. 메타 관리자는 오직 이 위키만을 담당합니다.



어떤 위키를 호스팅하나요?
Miraheze는 끈끈한 소규모 공동체부터 거대한 팬층과 협업 프로젝트까지, 콘텐츠 정책을 준수하는 모든 종류의 위키를 호스팅합니다.

현재 개의 위키가 Miraheze에서 호스팅되고 있습니다. 여러분은 Gazetteer of wikis에서 몇몇 위키의 목록을 사용자가 작성한 짧은 설명과 함께 보실 수 있습니다. 이러한 위키 대부분은 여러분이 읽고 기여까지 하는 것을 환영합니다. Miraheze에서 호스팅하는 모든 위키의 목록은 Special:WikiDiscover에서 확인하세요.



왜 Miraheze라고 불리나요?
Miraheze의 공동창립자 중 한명이 위키미디어 재단에서 근무했을 때, 이들의 서버 중 일부는 별의 이름으로 지어졌습니다. 특히 두 개의 서버는 와  로 지어져서 이 둘을 합치면 우리의 이름, Miraheze가 됩니다! Mira와 Heze는 둘 다 별입니다.

공식 발음에 대해서는, 정말 하나도 없습니다. 다양한 사람들이 Miraheze를 다르게 부르지만, 2022년 현재의 일반적인 합의로는 "meer-ah-heez"라고 부르는 것 같습니다.



비즈니스 모델


호스팅 서비스를 하는데 비용은 어떻게 조달하나요?
Miraheze는 비영리적이고 완전히 기부에 의존하고 있습니다. 우리는 광고를 하지 않고 정부나 회사의 재정에 의존하지 않습니다. 그러므로 기여자들에게 의존합니다. 더 많은 정보는 기부와 재정을 봐주세요.



왜 광고를 하지 않나요?
몇몇 사람들은 광고를 싫어하고, 광고는 후원보다 더 많은 돈을 얻도록 하지 않기 때문입니다(그리고 광고는 사람들이 우리에게 후원하는 것을 멈추도록 합니다). 광고가 사생활 침해를 할 수 있고, Miraheze가 광고 회사의 압박으로 위키의 글들에 개입할 우려가 있습니다. 우리는 우리의 편집 독립성을 지킬것이고, 개인 위키에서 작업하는 저자들의 편집 독립성도 지킬것입니다.



어떻게 Miraheze에 후원할 수 있나요?
Miraheze는 현재 PayPal에서 지원하는 모든 결제 방법을 지원합니다. 당신은 링크를 [$pp 클릭]하거나  에 직접 기부를 할 수 있습니다. 더 많은 정보는 기부를 보거나 와 Owen에게 문의하세요



다른 방법으로도 기여할 수 있나요?
기여를 참고하세요



얼마나 많은 서버가 있고, 그 서버들은 어디에 위치하여 있나요?
Since January 2022, we have our own physical hardware where we host most of our servers. Our datacentre 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.

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



나만의 위키 만들기


어떻게 위키를 만들 수 있나요?
첫번째로 계정을 만들고, 위키 요청 하기로 가서 양식을 채우세요.



어떻게 내 위키가 만들어졌는지 확인하나요
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.

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

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.



무언가 잘못되면 어떡하죠?
This unfortunately can happen from time to time. 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 noticeboard, 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 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 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' 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 entirely independent and free from regulations related to safety, security, civility, and legality. 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.



How private is a private wiki?
A private wiki can only be viewed and edited by its members. To allow someone to view and edit your wiki, please go to Special:UserRights on your wiki (not this wiki, Miraheze Meta, whose rights are only editable by local administration) and enter the name of any registered Miraheze user to put that user in the  group on your 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 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.

Why can everyone see the Main Page on my private wiki?
The main page is always public, by rule. You can get around this rule by putting your main content on some other page (say, "Home"), then edit your main page to redirect it there:
 * 1) REDIRECT Home

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.

What is Phabricator?
Phabricator is a system by which wiki bureaucrats can report technical issues to system administrators or request configuration changes for configuration variables that are not in ManageWiki. Phabricator is not meant for general support requests like help with CSS, only for technical issues. For general support, check out the Help center

Phabricator is separate from MediaWiki, which is the software powering your wiki, but it is still under the control of Miraheze.

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

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 features 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 include:
 * 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, security, and other reasons. Check that page out to see how to request extensions not in ManageWiki.

How do I change my logo or favicon?
Please check out the ManageWiki help page for details on how to make the change.

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.

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.

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.

 폐쇄된 위키

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.

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,  list 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.

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.

I've got an issue with a user or wiki
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

 * 1) Talk to them
 * 2) Raise the issue to a local wiki administrator. On this wiki (Miraheze Meta) only, you can use Administrators' noticeboard.
 * 3) If there is no resolution and the problem you're facing involves violations of the Code of Conduct, please email stewards@undefinedmiraheze.org. Stewards' will investigate the matter and bring a satisfactory resolution.

If it'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.

<span id="Still_have_questions?"> 아직 질문있나요?

If you have any questions that this FAQ does not answer, feel free to ask at Community noticeboard or contact us.