FORwiki:Protection policy

From FORwiki

Jump to: navigation, search

Fully protected
Protected by Office
Create protected
Indefinitely protected
Move protected

Administrators are able to protect a page to restrict editing or moving of that page, and remove such protection. Protection can be indefinite, or expire after a specified time.

  • Full protection prevents editing by everyone except administrators. Fully protected media files cannot be overwritten by new uploads.
  • Semi-protection prevents editing by unregistered contributions and contributors with accounts which are not autoconfirmed.
  • Creation protection prevents a page (normally a previously deleted one) from being recreated.
  • Move protection protects the page solely from moves.

Except in the case of office actions (see below), administrators may unprotect a page if the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary. Contacting the administrator who originally protected the page is advised in unclear circumstances. A log of protections and unprotections is available at Special:Log/protect.


<span id="full"/>

Full protection

A fully protected page can be edited only by administrators. The protection may be for a specified time, such as 7 or 14 days, or may be indefinite. The edit tab for a protected page is replaced by a "view source" tab, where users can view and copy, but not edit, the wikitext of that page.

Any modification to a fully protected page should be proposed on its talk page (or in another appropriate forum). After consensus has been established for the change, or if the change is uncontroversial, any administrator may make the necessary edits to the protected page.

<span id="full-dispute"/>

Content disputes

On pages that are experiencing edit warring, temporary full protection can force the parties to discuss their edits on the talk page, where they can reach consensus. Isolated incidents of edit warring, and persistent edit warring by particular users, may be better addressed by blocking, so as not to prevent normal editing of the page by others.

<span id="PREFER"/><span id="prefer"/>

When protecting a page because of a content dispute, administrators normally protect the current version, except where the current version contains content that clearly violates content policies, such as vandalism, copyright violations, or defamation of living persons. Since protecting the most current version sometimes rewards edit warring by establishing a contentious revision, administrators may also revert to an old version of the page predating the edit war if such a clear point exists. Pages that are protected because of content disputes should not be edited except to make changes which are uncontroversial or for which there is clear consensus (see above).

Administrators should not protect or unprotect a page to further their own position in a content dispute.


Pre-emptive full protection of articles is contrary to the open nature of Foresight Wiki. Brief periods of full protection are used in rare cases when a large number of autoconfirmed accounts are used to make a sustained vandalism attack on an article. Persistent vandalism, or the possibility of future vandalism for highly trafficked articles, rarely provides a basis for full-protection.

"History only" review

If a deleted page is undergoing deletion review, only administrators are normally capable of viewing the former content of the page. If they feel it would benefit the discussion to allow other users to view the page content, administrators may restore the page or blank it, and fully protect the page to prevent further editing.

<span id="full-talk"/>

Talk-page protection

Foresight Wiki now supports disabling users editing their own talk pages when blocking. This should be used instead wherever practical, as things like expiry are automatic (And it does not prevent other users from editing the page for typos etc). If the user is using sock puppet accounts, see the instructions below. Administrators may fully protect the user talk page of a blocked user if the page is being used for continued inappropriate editing by sock puppet accounts of the blocked user. If the user is not using sock puppet accounts, see the instructions above. This includes repeated abuse of the {{unblock}} template, or continued uncivil or offensive remarks. The protection should be timed so as not to exceed the length of the block. If the block is of indefinite duration, then the protection may be likewise.

<span id="office"/>

Office actions

<span id="semi"/>


Semi-protection prevents edits from anonymous users (IP addresses), as well as edits from accounts that are not autoconfirmed (have a four day old account and ten or more edits to Foresight wiki) or confirmed. Such users can request edits to a semi-protected page by proposing them on its talk page.

Administrators may apply indefinite semi-protection to pages which are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, neutral point of view). Semi-protection should not be used as a pre-emptive measure against vandalism that has not yet occurred, nor should it be used solely to prevent editing by anonymous and newly registered users.

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

  • Subject to significant but temporary vandalism or disruption (for example, due to media attention) when blocking individual users is not a feasible option.
  • Subject to edit-warring where all parties involved are anonymous or new editors (i.e., in cases in which full-protection would otherwise be applied). This does not apply when autoconfirmed users are involved.
  • Article discussion pages, when they have been subject to persistent disruption. Such protection should be used sparingly because it prevents anonymous and newly registered users from participating in discussions. A page and its talk page should not both be protected at the same time.
  • Talk pages of blocked IP addresses that are being used for continued inappropriate editing or continued uncivil or offensive remarks. The protection should be timed so as to not exceed the length of the block. Although administrators may also choose to change the block settings to block the user from editing their talk page instead, since there is no need to synchronize the block period with the page protection time period with this method.

<span id="indef"/>

Permanent protection

Some areas of Foresight Wiki are permanently protected by the MediaWiki software. The MediaWiki namespace, which defines parts of the site interface, is fully protected; administrators cannot remove this protection. In addition, user CSS and JavaScript pages are automatically fully protected. Only accounts that are associated with these pages or administrators are able to edit them. This protection applies to any user subpage with a ".css" or ".js" extension, whether an equivalent MediaWiki skin exists or not. Administrators may modify these pages, for example, to remove a user script that has been used in an inappropriate way.

In addition to the hard-coded protection, the following are usually permanently protected:

  • Pages that are very visible, such as the Main Page.
  • Pages that should not be modified for copyright or legal reasons, such as the general disclaimer or the local copy of the site copyright license.
  • Pages that are very frequently transcluded, such as {{tl}} or {{ambox}}, to prevent vandalism or denial of service attacks. This includes images or templates used in other highly visible or frequently transcluded pages.

<span id="create"/>

Creation protection

Administrators can prevent the creation of a page through the protection interface. This is useful for articles that have been deleted but repeatedly recreated by an editor. Such protection is case-sensitive.

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 more appropriate content should contact an administrator or use the deletion review process.

<span id="move"/>

Move protection

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

  • Pages subject to persistent page-move vandalism.
  • Pages subject to a page-name dispute.
  • Visible pages that have no reason to be moved, such as the Administrators' noticeboard.

Fully protected pages are also move-protected.

As with full protection, administrators should avoid favoring one name over another, and protection should not be considered an endorsement of the current name. An obvious exception to this rule is when pages are protected due to page-move vandalism.

<span id="semi-user"/>


Templates are like all pages in regard to protection, and are not protected unless there is a special reason to do so. Highly visible templates or templates in use on many pages are usually protected. Protection may be semi-protection or full protection, based on the degree of visibility, type of use, content, and other factors. In view of this, editors should not automatically add a protection template when working on templates.

It is preferable to place the protection template on a template's documentation page (if available), rather than on the template page itself.

User pages

User pages and subpages are protected at the user's request if there is evidence of vandalism or disruption. User talk pages are rarely protected, and are semi-protected for short durations only in the most severe cases of vandalism from IP users.

<span id="cascade"/>

Cascading protection

Cascading protection fully protects a page, and extends that full protection automatically to any page that is transcluded onto the protected page, whether directly or indirectly. This includes images and other media that are hosted on English Foresight Wiki. Files stored on Commons will not be protected by cascading protection, and need to be temporarily uploaded to English Foresight Wiki or protected at Commons.

Cascading protection should be used only to prevent vandalism to particularly visible pages such as the Main Page.

Available templates

The following templates may be added at the very top of a page to indicate that it is protected:

See also

Personal tools