Template:Sockpuppet
An editor has expressed a concern that this account may be a sock puppet of [[User:{{{1}}}|{{{1}}}]] ([[User talk:{{{1}}}|talk]]·[[Special:Contribs/{{{1}}}|contribs]]·[[Special:Log/{{{1}}}|logs]]). Please refer to editing habits or contributions of the sock puppet for evidence. This policy subsection may also be helpful. Account information: block log · current autoblocks · contribs · logs · abuse log · CentralAuth |
Usage
editCode | Use | Displays | |||
---|---|---|---|---|---|
{{sockpuppet|Example}}
|
Account is not yet blocked but is under investigation. |
| |||
{{sockpuppet|Example|blocked}}
|
The account has been blocked based on en:WP:DUCK or behavioural evidence combined a with a possible or likely CU result (but it isn't certain). |
| |||
{{sockpuppet|Example|proven}}
|
Behaviour is beyond a reasonable doubt (e.g., an admission) but there is no CU Confirmed result (CU may have given another result). |
| |||
{{sockpuppet|Example|confirmed}}
|
A CU has Confirmed that the accounts are related. |
| |||
{{sockpuppet|Example|confirmed|locked=yes}}
|
Account has been confirmed by a CU, locally blocked indef and globally locked. |
| |||
{{sockpuppet|Example|cuconfirmed|notblocked=yes}}
|
A CheckUser has confirmed that the account is a sock (as above) but has not been blocked. This works with all parameters. |
|
For use when there is a master which is not confirmed (can be used in addition to the parameters below)
Code | Use | Displays | |||
---|---|---|---|---|---|
{{Sockpuppet|Example|confirmed |altmaster=Example2|altmaster-status=proven}} | User:Example has been confirmed to another sock account but there is a very strong connection to another master (Example2) which is not CU confirmed. |
| |||
{{Sockpuppet|Example|confirmed |altmaster=Example2|altmaster-status=suspected}} | User:Example has been confirmed to another sock account but User:Example2 is the suspected master. |
| |||
{{Sockpuppet|Example|proven |altmaster=Example2|altmaster-status=suspected}} | User:Example is proven to be a sock of another account but both are suspected to be a sock of User:Example2. |
|
The template adds the __NOINDEX__
magic word.
Parameters
editThe first parameter in this table is required and the template will fail without it. All the other parameters are optional.
Parameter(s) | Values | Notes |
---|---|---|
|
Username of the sockmaster or suspected sockmaster | Just include the name, no "User:" or square brackets. |
|
|
|
|
Evidence of sockpuppetry | This field can be used to link to the evidence of sockpuppetry, or to give a very brief summary (a couple of words). If this parameter is left blank and the sockpuppet investigation case page is a blue link, then a link to the case page is provided automatically. |
|
Subpage name (just the master) of the SPI if not the same as the master | This field can be used to specify a different SPI page if the page is not named for the master in parameter 2. |
|
|
Use |locked=yes if the account is globally locked.
|
|
|
This parameter can be used to remove the note about the account being blocked, such as when a version other than the default applies. Such as if an account is confirmed by a CheckUser but is left unblocked. This parameter works with all parameters. |
|
Length of time the sockpuppet or suspected sockpuppet was blocked | Use this field if the sockpuppet or suspected sockpuppet was blocked for a specific length of time. This parameter defaults to "indefinitely". This parameter is ignored, and does not default to indefinitely, if nbconfirmed is used.
|
|
Custom category name for the sockpuppet or suspected sockpuppet | This parameter defaults to the category "Sockpuppets of X" if the second positional parameter is set to "confirmed", and "Suspected sockpuppets of X" if the second positional parameter is set to anything else. Here, "X" is the username specified in the first positional parameter. |
Categories
editThis template adds pages to one of (as appropriate):
- Category:Suspected sockpuppets and Category:Suspected sockpuppets of {{{1}}};
- Category:Sockpuppets of {{{1}}}.
TemplateData
editTemplateData for Sockpuppet
This template is placed on the user pages of accounts which are sockpuppets, usually by patrolling administrators at SPI.
Parameter | Description | Type | Status | |
---|---|---|---|---|
Master's username | 1 | Username of the sockpuppeteer | User | required |
Status | 2 | The status of the account. Set to "spi" or "suspected" if the user is not yet blocked or confirmed by a checkuser but is under investigation. Set to "blocked" if the user has been blocked on behavioral evidence (checkuser not used). Set to "proven" if the user is a sock beyond reasonable doubt. Set to "confirmed" "cuconfirmed" or "nbconfirmed" if the account has been confirmed by a checkuser. If defined, defaults to the 'not yet blocked or confirmed by a checkuser but is under investigation'. | String | suggested |
Evidence | 3 evidence | Use this parameter to specify evidence different from the normal link to the case page | Content | optional |
Block length (if not indefinite) | length | The length of time the user has been blocked for. Defaults to indefinite. | String | optional |
Block override | notblocked | Set to no if the account has not been blocked and the status template is not the default | Line | optional |
Globally locked? | locked | Set to "yes" if the account has been globally locked | Line | optional |
Subpage name of SPI | spipage | Define if the SPI has a different name to the master | String | optional |
Custom category | category cat | Adds the user to a custom category. Defaults to "Suspected sockpuppets of [sockmaster]" or "Sockpuppets of [sockmaster]" based on the "Status" parameter. | Unknown | optional |
Remove categories | nocat | Defining this parameter will remove the categories | Line | optional |
See also
edit{{Sockpuppeteer}}