사용자 계정 정책

From Miraheze Meta, Miraheze's central coordination wiki
This page is a translated version of the page User accounts policy and the translation is 7% complete.
Outdated translations are marked like this.


Shortcut:
UAP

이 요청의 의견으로부터의 여러 의견들을 조합하며, 이 정책은 계정에 사용에 관한 Miraheze의 입장을 나타냅니다.

Authorized account use

공유 계정

계정은 이 조건을 만족하는 경우에만 공유될 수 있습니다.

  • 공유 계정은 각각의 메타 사용자 문서에서 공유 계정임을 밝혀야 합니다. 이는 다음 조건을 강제하기 위함입니다.
  • 공유 계정은 어떤 전역 권한도 부여받을 수 없으며 공유 계정이 로컬 권한을 가져야하는 지는 로컬 위키 관리자가 판단합니다.
이유는 공유 계정의 기여를 확실히 추적할 수 없는 것처럼, 요청받은 실제 사람이 아닌 계정을 공유 받은 모든 사람이 권한을 악용할 수 있기 때문입니다.

다중 계정

사용자는 다중 계정을 가질 수 있습니다.

  • 동일한 사람에게 속한 다중 계정들은 악용의 심각성에 따라 집단적으로 혹은 개별적으로 차단될 수 있습니다, 판단은 잠금/차단하는 스태프 멤버가 합니다.
  • 다중 계정임을 밝힐 필요는 없으나, 밝히지 아니함은 특정 조건하에서 다중 계정의 악용으로 고려될 수 있습니다. 상식적으로 생각해주세요.
  • 계정 생성 또한 스팸의 한 종류라는 것을 명심해주세요. 사용할 계정만 생성해주세요.

Bots

Bots, or automated edit scripts, are often run from separate accounts from their human operators, in accordance with any locally established policies governing bot usage, where they exist. Where a wiki has no locally established policies governing bot usage, the bot operator should reach out to any bureaucrat on that wiki stating how they intend to operate their bot, the task(s) it aims to perform, how frequently it plans it to edit, etc., for assent to operate the bot. Bot accounts may be operated by more than one user if this is disclosed and the wiki where the bot operates permits it. Wikis may ban bots from operating in general.

Brand or role accounts

Accounts representing a specific organization or role, intended to be used by a rotating individual or multiple people, are permitted if the operators and scope of the account are disclosed. The account should always be able to verify its association with the entity it is named for. For example, accounts implying relationship with a wiki should be verifiably operated by the given wiki's administration and have a clear function.

Individual wikis can regulate the use of these accounts, including (but not limited to) forbidding their operation on that wiki, or only allowing them to post on talk pages.

Unauthorized uses

The inclusion of links to Wikipedia essays is for further reading. They are not incorporated into the policy.

  • Sockpuppetry (often abbreviated in discussion as "socking") is the use of multiple Miraheze user accounts for nefarious purposes. Attempts to deceive or mislead other editors, disrupt discussions, distort consensus, avoid sanctions, or otherwise violate community standards and policies are all examples of nefarious purposes.
  • Evasion of sanctions: Sanctions apply to individuals. Using another account to go around a sanction (such as an active block, ban or other restriction) is considered abuse. The offending account will likely be locked and further warning/notice will be issued to the main account.
  • If you want to contest a block or ban on a non-Meta Miraheze Wiki, you should follow these options in order: appeal by your local talk page/the locally designated appeal area, appeal to a local/active administrator by their talk page on Meta if this has not been allowed, appeal to Stewards via the Stewards' noticeboard by explaining the situation and getting them to look into it, and if you are unable to edit at all (for example, you've been locked), appeal by email to stewards@miraheze.org.
  • Spoofing: Creating multiple accounts to 'spoof' or disrupt community votes or discussions, and using alts to try and discredit the opposing argument with bad form (also called 'straw socking'). Votes and inputs from misused alternate accounts will be struck and implicated accounts will be investigated as necessary.
  • Good-hand/bad-hand accounts: Using one account constructively, but operating another (or multiple) for disruption, vandalism and so forth.
  • Editing while logged out to mislead: Treat your IP address as an account (a secret one where an actual account is always ideal); everyone is expected to conduct themselves properly even while logged out. Take care when editing with your IP to avoid 'Spoofing' or evading sanctions.
  • Misusing a clean start: Users who need a new beginning, wish to get away from their contentious history or wish to start up an account to pursue a different line of interests on Miraheze can attempt to do so. If global or local sanctions apply, they must be respected, and preferably a Steward is in contact, so they do not take the account for a sockpuppet of a repeat vandal or problem case. If not, especially if the problematic behavior resulting in the original sanctions or awful reputation is repeated, and no Steward has been contacted to reach terms, this attempted clean start will be seen as abuse.
  • Avoiding scrutiny: Accounts made to lure attention away from the activity or history of the primary account where that information is in the local community's interest. Especially relevant for, say, requesting adminship.
  • Long term abuse (LTA) is used to designate users whose main account has been locked for abusing multiple accounts and who continue to persistently create new sockpuppet accounts over a long period of time.

Addressing account abuse

Evidence of account abuse can be collected and presented to Stewards who can take further actions, ranging from formal warnings to account locks and other global or local measures. Evidence includes behavioral association, any technical evidence that may be visible, and anything else needed to corroborate the suspected abuse. The evidence and request for review can be offered on the Stewards' noticeboard, by Discord or IRC to a Steward or the official #cvt channel, or by email to [email protected].

Stewards will use their judgement to determine if global action is needed, including the use of CheckUser - a tool used on a short-term basis to gather technical details of users and connections they reasonably believe are/may be connected to the abuse. Where the link is obvious, i.e., a clear 'long-term abuse' pattern, local admins are encouraged to block outright and not engage at all. Global Sysops are empowered to deal with them, but are unable to use CheckUser and will defer to Steward investigation.

Revision history