Nookipedia:Block policy


 * ''The following contains content adapted from the MarioWiki blocking policy and the Wikipedia blocking policy.

Blocking is the method by which administrators prevent users from editing Nookipedia. Blocks may be applied to user accounts, to IP addresses, and to ranges of IP addresses, and can be either temporary or indefinite. Blocked users can continue to read Nookipedia, but cannot edit, create or move pages. Blocks are used to prevent damage and disruption, and to enforce Nookipedia's policies.

Reasons for blocking
Blocks are most frequently used to deal with vandalism and spam, but may also be used in cases of persistent policy violation, inappropriate username creation, sockpuppetry, or unapproved or malfunctioning bots, as outlined below.

Vandalism and spam
Vandalism is the insertion of inappropriate, seemingly random, or deliberately incorrect information into pages, while spam involves the posting of promotional material encouraging users to visit another web address (often unrelated to Nookipedia).

Users or IPs who vandalize pages or insert promotional material should be blocked immediately on sight. For IPs, such blocks should initially last for around a week, but should be longer for repeat violations. However, they should never be indefinite, because IP addresses are often shared by several users. Blatant vandalism-only accounts, or accounts created for advertising purposes, should be blocked indefinitely. Warnings should not be given for these offenses.

Users or IPs who are blocked for vandalism or spam should also have the ability to edit their own talk page removed (see the 'How to block' section below). This will prevent the blocked user from being able to cause further disruption.

For lesser offenses, such as when the user's edits are merely unconstructive rather than blatant vandalism, warnings or temporary blocks should be used instead (see the 'disruption' section below).

Users or IPs whose attempts at vandalism are disallowed by the abuse filter may also be blocked at the individual sysop's disrection.

Disruption and policy violations
Blocks may also be used against any user that persistently disrupts the normal functioning of the wiki, or repeatedly breaks Nookipedia policy. Most violations of policy can be dealt with under this category, although some violations are more serious than others. Infractions that fall under this category include, but are not limited to:
 * Posting inappropriate or inflammatory comments towards other users
 * Participating in an edit war
 * Making unconstructive edits, or removing content without using the edit summary to explain why
 * Removing other users' talk page comments or warnings
 * Repeated violations of the upload policy
 * Creating extra accounts for malicious purposes
 * Revealing inappropriate personal information
 * Editing other users' pages or talk page archives without a good reason

In most cases, accounts who violate policy should be left a message on their talk page explaining what they are doing wrong. If the user continues to violate policy, an official warning should be issued to them by a staff member. Afterward, a temporary block can be issued if the users flouts the rules again. If a user has received multiple temporary blocks and is still continuing to be disruptive, an indefinite block should be considered.

In severe cases, users may be given an official warning or block straight away, especially if it has become clear that they are not here to contribute to Nookipedia.

Users who do not have an account and are editing via their IP address should not be given an official warning template, as they are often shared by several users. Instead, disruptive editing from them should be dealt with using informal warnings and/or temporary blocks at the individual sysop's discretion.

Usernames
Usernames that are inflammatory or deliberately confusing, as well as those that deliberately inpersonate another user on the wiki are not allowed. Accounts whose usernames are that of a famous person, company, or organization also fall into this category. Indefinite blocks should be applied to accounts with unacceptable usernames.

When blocking an account with an inappropriate username, template UsernameBlock should be left on the talk page to explain the reason for the block, and to allow the user to change their username. If the name is bad enough, however, they may simply be blocked as a troll/vandal, and not allowed a rename at all. Bureaucrats often rename accounts with inappropriate names to clear them from the recent changes and logs.

Sockpuppetry and multiple accounts
Users should, where possible, only edit using one account. If a user creates more than one account, the ones they are not using should be indefinitely blocked. Sysops should wait and see which account starts to edit and block the rest, although they should not go out of their way to issue blocks when it is unclear which account is the main one. Similarly, if a user forgets their password and creates a new account, their old account can be blocked, although the user should be encouraged to use the password reset function if possible.

If a user creates extra account(s) for a malicious purpose (such as voting multiple times in a discussion), this is considered sockpuppetry and therefore a warnable offense.

Users must also not attempt to circumvent blocks (by creating a new account or using a different IP, etc). If they do, their new account or IP is also eligible to be blocked, and an extension to the original block (especially if it is a temporary account block) should be considered.

Generally, blocks for sockpuppetry and misuse of multiple accounts should be dealt with by Bureaucrats and Directors, as they are the only ones who can check users' IP addresses. Non-bureaucrats should refer possible cases to a Bureaucrat or Director, but Administrators may still issue blocks if the extra account(s) obviously belong to the same person.

Bots
Bots must be approved by a Director and given a bot flag before they can make automated edits. Unapproved bots should be blocked indefinitely.

Bots that are malfunctioning may also be blocked temporarily until their issues are resolved by the owner.

Partial blocks
In addition to sitewide blocks (which prevent blocked users from editing all pages on Nookipedia), sysops also have the option of blocking users or IP addresses from editing specific page(s) and/or namespace(s). Generally, partial blocks should be avoided and sitewide blocks issued instead, especially when dealing with vandalism. However, if an editor's disruption is clearly limited to only a small number of specific pages (for example in an edit war), a partial block can be considered.

When blocking may not be used
The list above is widely considered to be an exhaustive list of the situations that warrant blocking. Blocking should not be used in any other circumstances, unless there is exceptional widespread community support.

Use of blocks to gain advantage in a content dispute, and self-blocking in an effort to enforce a "Wikiholiday" or departure are specifically prohibited. Likewise, users should not block those with whom they are currently engaged in conflict.

How to block
Administrators may go to the list of special pages and select the "Block user" link. This takes them to Special:Block, which has further instructions. Special:Block is also quickly accessible via the [block] link that appears next to each user on the recent changes page, and at the top of a user's contributions page.

Expiry times are set by selecting a block length from a drop down menu that is provided. Unique expiry times can also be entered, using the GNU standard format. The option for an "infinite" block can also be found in the drop-down menu, in which case, there is no expiry date, and an administrator must remove the block if the user is to be allowed back onto the wiki. If an administrator does not enter an expiry time when blocking, an error message will be displayed.

The "reason" that the administrator fills in will be displayed to the blocked user when they attempt to edit, and will also appear in the block log and the list of blocked accounts and IP addresses. A selection of the more common reasons are provided in a drop-down menu.

There are also number of checkboxes present on the blocking page, which will determine whether the blocked user is also blocked from making new accounts, or if they will be able to edit their own talk page or send e-mail using Special:EmailUser during the block. As mentioned above, if the block is for vandalism or spam, the block should be set to not allow talk page editing. Otherwise, talk page editing should be enabled, but if a user abuses this privilege, it can be revoked. The 'autoblock' feature may sometimes need to be disabled when blocking duplicate accounts belonging to the same user, as otherwise the main account could also find itself wrongly blocked.

Effects of being blocked
Blocked users can still see all Wiki pages, but the "edit" link brings up a "User is blocked" page which explains the reason behind the block and gives information on how to request unblocking. This page includes the "reason" message supplied by the administrator who placed the block. Links and template includes all work as normal in the "reason" section.

The duration of the block depends on the expiry time that was entered at the time of the block, which may be "indefinite" or "infinite" (ie, until explicitly unblocked).

When a blocked user attempts to edit, the IP from which they are editing is "autoblocked," so that they may not make the same edit anonymously or under a different user name. Occasionally however, the blocking administrator may choose to disable autoblock (see the 'How to block' section above). There is an internal autoblock expiry time variable, which is set to one week, meaning that when a username is blocked, their IP will be automatically unblocked one week after they last accessed a page.

In addition, when an IP block is placed, or an autoblock is set by an account block, a cookie will be set in the blocked users' browser. This means that the user will still be blocked even if their IP address changes. However, the cookie will expire after 24 hours, and is only meant to provide a small extra level of protection.

Note that blocking does not in any way restrict any feature other than normal article editing: blocked users can still read articles, as well as adjust their watchlists and user preferences.

Range blocks
Range blocks are sometimes used when a vandal or disruptive user has been IP blocked on several occasions but responds by using a different IP address. In most cases, range blocks will affect at least some legitimate users. IPv4 and large IPv6 range blocks should only be used when the disruptive behavior is frequent and severe enough to make other methods ineffective. This is a matter of judgement, and the likely number of legitimate users that might be affected should be considered. However, /64 ranges of IPv6 addresses are usually only accessible to one user/connection/physical location, and can therefore be blocked even if disruption has only occurred from a single IP address.

Range blocks can be placed by the server administrator, and prevent all access to the wiki. The blocked IP(s) will be unable to edit, view, or even load images from Nookipedia servers. This is used only in extremely severe cases. Accounts can also be blocked in this way by the directors, these should have template BlockDirector placed on their talk page.

Unblocking and appeals
If you feel that there are good reasons that you should be unblocked, or if you were blocked in error, please e-mail support@nookipedia.com. The staff team will then discuss the situation. However, this does not guarantee that you will be unblocked. You should try to address what you were blocked for, and make it clear that you will not engage in further disruptive behavior.

Administrators may also remove blocks they feel were made in error or are no longer necessary, but it is preferred if they discuss the issue with other staff on Discord.

Special:BlockList contains a list of all currently blocked users and IPs. Sysops will see a link to [unblock] next to each user. After clicking this, they should type in the reason that they are unblocking the user and then click the Unblock this address button.