User:Dorsal Axe/Sandbox/Durian

Protection Policy

Interface protection
Administrators cannot change or remove the protection for some areas on Nookipedia which are permanently protected by the MediaWiki software:
 * Edits to the MediaWiki namespace, which defines parts of the site interface, are restricted to administrators.
 * Edits to system-wide CSS and JavaScript pages are further restricted to interface administrators.
 * Edits to personal CSS and JavaScript pages are restricted to the associated user and interface administrators. Interface administrators may edit these pages, for example, to remove a user script that has been used in an inappropriate way. Administrators may delete (but not edit or restore) these pages.
 * Edits to personal JSON pages are restricted to the associated user and administrators.

Permanent protection
In addition to hard-coded protection, the following are usually permanently fully protected:
 * Pages that are very visible, such as the Main Page and Contents Portal.
 * Templates that form part of the site interface, such as file licensing templates.
 * Policy pages. Changes can be implemented by administrators per consensus.
 * Pages that should not be modified for copyright or legal reasons, such as the general disclaimer, and about.

Full protection
A fully protected page cannot be edited or moved by anyone except administrators. The protection may be for a specified time or may be indefinite. Full protection should be applied to:
 * Pages and files subject to edit warring or vandalism by registered users.
 * Archived pages, these should be preserved in its state at the time of archival. They should no longer be edited other than to add the  template or to perform maintenance edits.
 * User pages per the user's request at the Staff noticeboard.

Full protection should only be used in the main or talk namespaces temporarily, as a means to end persistent vandalism or an edit war. Modifications to a fully protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus.

Semi-protection
Semi-protected pages cannot be edited by unregistered users, as well as accounts that are not autoconfirmed (accounts that are at least seven days old and have made at least ten edits to Nookipedia) or confirmed. Semi-protection is useful when there is a significant amount of disruption or vandalism from new or unregistered users, or to prevent sockpuppets of blocked or banned users from editing. Semi-protection may also be granted to user pages upon the user's request at the Staff noticeboard.

Modifications to a semi-protected page can be proposed on its talk page.

Guidance for administrators
Administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy. Semi-protection should not be used as a pre-emptive measure against vandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) content disputes.

In addition, administrators may apply temporary semi-protection on pages that are:


 * Subject to significant but temporary vandalism or disruption, if blocking individual users is not a feasible option.
 * Subject to edit warring if all parties involved are unregistered or new editors (i.e. in cases in which full protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
 * Subject to vandalism or edit warring where unregistered editors are engaging in IP hopping by using different computers, obtaining new addresses by using dynamic IP allocation, or other address-changing schemes.

Protection should be used sparingly on article discussion pages because it prevents unregistered and newly registered users from participating in discussions. A page and its talk page should not normally be protected at the same time. If a page and its talk page are both protected, the  template should be added to the talk page to direct affected editors to the Community Fountain to ensure that no editor is entirely prevented from contributing.

Template protection
A template-protected page can be edited only by administrators. This protection level should be used almost exclusively on high-risk templates and modules. In cases where pages in other namespaces become transcluded to a very high degree, this protection level is also valid.

This is a protection level that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should be used on templates whose risk factor would have otherwise warranted full protection. It should not be used on less risky templates on the grounds that the template editor user right exists—the existence of the right should not result in more templates becoming uneditable for the general editing community.

Modifications to a template-protected page can be proposed on its talk page.

Move protection
Move protected pages and files cannot be moved to a new title except by an administrator. Move protection is commonly applied to:


 * Pages and files subject to persistent page-move vandalism.
 * Pages and files subject to a page-name dispute.
 * Highly visible pages that have no reason to be moved, such as the Staff noticeboard or Community Fountain.
 * Files that should not be moved, such as images used in the interface or transcluded to the main page.
 * File redirects, these should typically be kept to preserve page history and avoid breaking external links (see Deletion policy for more information).

Fully edit-protected pages are also implicitly move-protected.

As with full edit protection, protection because of edit warring should not be considered an endorsement of the current name. When move protection is applied during a requested move discussion, the page should be protected at the location it was at when the move request was started.

Upload protection
Upload protected files cannot be replaced with new versions except by administrators. Upload protection does not protect file pages from editing. Upload protection may be applied to:


 * Files subject to persistent upload vandalism.
 * Files subject to a dispute between editors.
 * Files that should not be replaced, such as images used in the interface or transcluded to the Main Page.
 * Files with common or generic names.

As with full edit protection, administrators should avoid favoring one file version over another, and protection should not be considered an endorsement of the current file version. An exception to this rule is when files are protected due to upload vandalism.

Creation protection
Administrators can prevent the creation of pages. This level of protection is useful for bad pages that have been deleted but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that can be applied to pages, identical to the levels for edit protection. A list of protected titles may be found at Special:ProtectedTitles (se

Pre-emptive restrictions on new article titles are instituted through the title blacklist system, which allows for more flexible protection with support for substrings and regular expressions.

Pages that have been creation-protected are sometimes referred to as "salted". Contributors wishing to re-create a salted title with appropriate content should either contact an administrator (preferably the protecting administrator), file a request at Wikipedia:Requests for page protection#Current requests for reduction in protection level, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.

While creation-protection is usually permanent, temporary creation protection may be applied if a page is repeatedly recreated by a single user (or sockpuppets of that user, if applicable).