JFK'S 'RACE TO SPACE' SPEECH

- By President John F. Kennedy
Font Size
Policy on page protection See also: Wikipedia:Requests for page protection and Wikipedia:Lists of protected pages "WP:PP" and "WP:PROTECT" redirect here. For other uses, see Wikipedia:Perennial proposals, Wikipedia:WikiProject Parliamentary Procedure, Wikipedia:Party and person, Wikipedia:Child protection, and Wikipedia:WikiProject Protected areas. This page documents an English Wikipedia policy.It describes a widely accepted standard that all editors should normally follow. Changes made to it should reflect consensus.ShortcutsWP:PPWP:PROTECT This page in a nutshell: While Wikipedia strives to be as open as possible, sometimes it is necessary to limit editing of certain pages in order to prevent vandalism, edit warring, or other disruptive edits. Are you in the right place?This page documents the protection policy on Wikipedia. If you are trying to... Then... make a request to protect or unprotect a page see Wikipedia:Requests for page protection make a request to edit a page see Wikipedia:Edit requests obtain user rights to edit protected pages request user rights report a user for persistent vandalism or spam file a vandalism report report a user for edit warring or violating revert restrictions open an edit warring report Enforcement policies Administrators Banning policy Blocking policy Protection policy vte Protection icons Icon Mode White Pending changes protected Silver Semi-protected Blue Extended confirmed protected Pink Template-protected Gold Fully protected Red Interface protected Green Move protected Skyblue Create protected Purple Upload protected Turquoise Cascade protected Black Protected by Office In some circumstances, pages may need to be protected from modification by certain groups of editors. Pages are protected when a specific damaging event has been identified that cannot be prevented through other means such as a block. Otherwise, Wikipedia is built on the principle that anyone can edit it, and it therefore aims to have as many of its pages as possible open for public editing so that anyone can add material and correct errors. This policy states in detail the protection types and procedures for page protection and unprotection and when each protection should and should not be applied. Protection is a technical restriction applied only by administrators, although any user may request protection. Protection can be indefinite or expire after a specified time. The various levels of protection are detailed below, and they can be applied to the page edit, page move, page create, and file upload actions. Even when a page is protected from editing, the source code (wikitext) of the page can still be viewed and copied by anyone. A protected page is marked at its top right by a padlock icon, usually added by the {{pp-protected}} template. Preemptive protection[edit] ShortcutsWP:NO-PREEMPTWP:PREEMPTIVE Applying page protection as a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed if applied solely for these reasons. However, brief periods of an appropriate and reasonable protection level are allowed in situations where blatant vandalism, disruption, or abuse is occurring by multiple users and at a level of frequency that requires its use in order to stop it. The duration of the protection should be set as short as possible, and the protection level should be set to the lowest restriction needed in order to stop the disruption while still allowing productive editors to make changes. Exceptions are largely confined to the Main Page, which is fully protected (along with its templates and images), and Today's Featured Article, which is semi-protected from the day before being featured until the day after it leaves the Main Page. Requesting protection[edit] Protection types[edit] ShortcutWP:PPLIST The following protection types are available to administrators for protecting different actions to pages: Edit protection protects the page from being edited. Move protection protects the page from being moved or renamed. Creation protection prevents a page (normally a previously deleted one) from being created (also known as "salting"). Upload protection prevents new versions of a file from being uploaded, but it does not prevent editing of the file's description page (unless edit protection is applied). Protection levels[edit] The following protection levels are available to administrators for adding protection to the different actions to pages: Pending changes protection (only available for edit protection) requires any edits made to the page by unregistered users and accounts that are not confirmed to be approved by a pending changes reviewer or an administrator before the changes become visible to readers who are not logged in. Semi-protection prevents the action by unregistered users and users with accounts that are not confirmed. Extended confirmed protection, previously known as 30/500 protection, prevents the action if the user's account is not extended confirmed (at least 30 days old with at least 500 edits). In most cases, it should not be a protection level of first resort, and should be used where semi-protection has proven to be ineffective. Activation or application of this protection level is logged at the Administrators' noticeboard. Template protection prevents the action by everyone except template editors and administrators (who have this right as part of their toolset). Full protection prevents the action by everyone except administrators. Submitting requests[edit] Any of the above protections can be requested at Wikipedia:Requests for page protection. Changes to a protected page should be proposed on the corresponding talk page, and then (if necessary) requested by adding an edit request. From there, if the requested changes are uncontroversial or if there is consensus for them, the changes can be carried out by a user who can edit the page. Except in the case of office actions (see below), Arbitration Committee remedies, or pages in the MediaWiki namespace (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. Editors desiring the unprotection of a page should, in the first instance, ask the administrator who applied the protection unless the administrator is inactive or no longer an administrator; thereafter, requests can be made at Requests for unprotection. Note that such requests will normally be declined if the protecting administrator is active and was not consulted first. A log of protections and unprotections is available at Special:Log/protect. Comparison table[edit] Interaction of Wikipedia user groups and page protection levels   Unregistered or newly registered Confirmed or autoconfirmed Extended confirmed Template editor Admin Interface admin Appropriate for No protection Normal editing The vast majority of pages. This is the default protection level. Pending changes All users can editEdits by unregistered or new editors (and any subsequent edits by anyone) are hidden from readers who are not logged in, until reviewed by a pending changes reviewer or admin. Logged-in editors see all edits, whether accepted or not. Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users. Semi Cannot edit Normal editing Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules. Extended confirmed Cannot edit Normal editing* Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive. Template Cannot edit Normal editing High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space. Full Cannot edit Normal editing Pages with persistent disruption from extended confirmed accounts. Critical templates and modules. Interface Cannot edit Normal editing Scripts, stylesheets, and similar objects central to operation of the site or that are in other editors' user spaces. * In order to edit through extended confirmed protection, a template editor must also be extended confirmed, but in practice this is almost always the case.Other modes of protection: Create protectionMove protectionUpload protectionOffice protectionCascade protection viewtalkedit Protection levels[edit] Each of these levels is explained in the context of edit protection, but each can be applied to other types of protection except for pending changes. Pending changes protection[edit] Further information: Wikipedia:Pending changes ShortcutsWP:PCPPWP:WHITELOCK Pending changes protection allows unregistered and new users to edit pages, while keeping their edits hidden from most readers (specifically, unregistered editors – the vast majority of visitors to Wikipedia articles) until those changes are accepted by a pending changes reviewer or administrator. An alternative to semi-protection, it is used to suppress vandalism and certain other persistent problems while allowing all users to continue to submit edits. Pending changes is technically implemented as a separate option, with its own duration, and it yields to other edit protection levels in cases of overlap. When a page under pending changes protection is edited by an unregistered (IP addresses) editor or a new user, the edit is not directly visible to the majority of Wikipedia readers, until it is reviewed and accepted by an editor with the pending changes reviewer right. When a page under pending changes protection is edited by an autoconfirmed user, the edit will be immediately visible to Wikipedia readers, unless there are pending edits waiting to be reviewed. Pending changes are visible in the page history, where they are marked as pending review. Readers who are not logged in (the vast majority of readers) are shown the latest accepted version of the page; logged-in users see the latest version of the page, with all changes (reviewed or not) applied. When editors who are not reviewers make changes to an article with unreviewed pending changes, their edits are also marked as pending and are not visible to most readers. A user who clicks "edit this page" is always, at that point, shown the latest version of the page for editing regardless of whether the user is logged in or not. If the editor is not logged in, their changes join any other changes to the article awaiting review – for the present they remain hidden from not-logged-in users. (This means that when the editor looks at the article after saving, the editor won't see the change made.) If the editor is logged in and a pending changes reviewer, and there are pending changes, the editor will be prompted to review the pending changes before editing – see Wikipedia:Pending changes. If the editor is logged in and not a pending changes reviewer: If there are no unreviewed pending edits waiting, this editor's edits will be visible to everyone immediately; but If there are unreviewed pending edits waiting, then this editor's edits will be visible only to other logged-in users (including themself) immediately, but not to readers not logged in. Reviewing of pending changes should be resolved within reasonable time limits. When to apply pending changes protection[edit] Pending changes can be used to protect articles against: Persistent vandalism Violations of the biographies of living persons policy Copyright violations Pending changes protection should not be used as a preemptive measure against violations that have not yet occurred. Like semi-protection, PC protection should never be used in genuine content disputes, where there is a risk of placing a particular group of editors (unregistered users) at a disadvantage. Pending changes protection should not be used on articles with a very high edit rate, even if they meet the aforementioned criteria. Instead, semi-protection should be considered. In addition, administrators may apply temporary pending changes 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. As with other forms of protection, the time frame of the protection should be proportional to the problem. Indefinite PC protection should be used only in cases of severe long-term disruption. Removal of pending changes protection can be requested of any administrator, or at requests for unprotection. The reviewing process is described in detail at Wikipedia:Reviewing pending changes. Semi-protection[edit] See also: Wikipedia:Rough guide to semi-protection ShortcutsWP:SEMIWP:SILVERLOCK Semi-protected pages like this page cannot be edited by unregistered users (IP addresses), as well as accounts that are not confirmed or autoconfirmed (accounts that are at least 4 days old with at least 10 edits on English Wikipedia). 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, especially when it occurs on biographies of living persons who have had a recent high level of media interest. An alternative to semi-protection is pending changes, which is sometimes favored when an article is being vandalized regularly, but otherwise receives a low amount of editing. Such users can request edits to a semi-protected page by proposing them on its talk page, using the {{Edit semi-protected}} template if necessary to gain attention. If the page in question and its talk page are both protected, the edit request should be made at Wikipedia:Requests for page protection instead. New users may also request the confirmed user right at Wikipedia:Requests for permissions/Confirmed. Guidance for administrators[edit] Semi-protection should not be used as a preemptive measure against vandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) content disputes. Administrators may apply temporary semi-protection on pages that are: Subject to significant but temporary vandalism or disruption (for example, due to media attention) if blocking individual users is not a feasible option. Subject to edit warring if all parties involved are unregistered or new editors. 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. Article discussion pages, if they have been subject to persistent disruption. Such protection should be used sparingly because it prevents unregistered and newly registered users from participating in discussions. Protection should be used sparingly on the talk pages of blocked users, including IP addresses. Instead the user should be re-blocked with talk page editing disallowed. When required, or when re-blocking without talk page editing allowed is unsuccessful, protection should be implemented for only a brief period not exceeding the duration of the block. In addition, administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, neutral point of view). A page and its talk page should not normally be protected at the same time. In exceptional cases, if a page and its talk page are both protected, the talk page should direct affected editors to Wikipedia:Request for edit through the use of a non-iconified page protection template, to ensure that no editor is entirely prevented from contributing. Today's featured article is, since 2023, always semi-protected. This was historically not the case, however. Extended confirmed protection[edit] See also: Wikipedia:Rough guide to extended confirmed protection ShortcutsWP:ECPWP:30/500WP:BLUELOCK Extended confirmed protection, previously known as 30/500 protection, allows edits only by editors with the extended confirmed user access level, granted automatically to registered users at least 30 days old with at least 500 edits on English Wikipedia. As escalation from semi-protection[edit] Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as vandalism, abusive sockpuppetry, edit wars, etc.) on any topic.[1] Extended confirmed protection should not be used as a preemptive measure against disruption that has not yet occurred, nor should it be used to privilege extended confirmed users over unregistered/new users in valid content disputes (except as general sanction enforcement; see below).[2] Contentious topics[edit] When necessary to prevent disruption in designated contentious topic areas, administrators are authorized to make protections at any level. (This is distinct from the extended confirmed restriction below.) Some community-authorized discretionary sanctions grant similar authorizations. Extended confirmed restriction[edit] Some topic areas are under Arbitration Committee extended confirmed restriction as a general sanction.[3] When such a restriction is in effect in a topic area, only extended-confirmed users may make edits related to the topic area. Enforcement of the restriction on articles primarily in the topic area is preferably done with extended confirmed protection, but it's not required (other enforcement methods are outlined in the policy). As always, review the policy before enforcing it. Community general sanctions, applying a similar extended confirmed restriction, have also been authorized by the community. General sanctions has a list of the active general sanctions that incorporate the extended confirmed restriction. Other cases[edit] High-risk templates can be extended-confirmed protected at administrator discretion when template protection would be too restrictive and semi-protection would be ineffective to stop widespread disruption.[4] Extended confirmed protection can be applied at the discretion of an administrator when creation-protecting a page.[2] Logging and edit requests[edit] As of September 23, 2016, a bot posts a notification in a subsection of AN when this protection level is used.[5] Any protection made as arbitration enforcement must be logged at Wikipedia:Arbitration enforcement log. Community-authorized discretionary sanctions must be logged on a page specific to the topic area. A full list of the 7469 pages under extended confirmed protection can be found here. Users can request edits to an extended confirmed-protected page by proposing them on its talk page, using the {{Edit extended-protected}} template if necessary to gain attention. Full protection[edit] ShortcutsWP:FULLWP:GOLDLOCK A fully protected page cannot be edited or moved by anyone except administrators. 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. Placing the {{Edit fully-protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes. Content disputes[edit] See also: Wikipedia:Stable version "WP:PREFER" redirects here. For what title name should be preferred, see Wikipedia:Disambiguation § Primary topic. While content disputes and edit warring can be addressed with user blocks issued by uninvolved administrators, allowing normal page editing by other editors at the same time, the protection policy provides an alternative approach as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page consensus a requirement for implementation of requested edits. ShortcutWP:PREFER When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as vandalism, copyright violations, defamation, or poor-quality coverage of living people. Administrators are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older, stable, or pre-edit-war version. Fully protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains policy-violating content, or that protection has rewarded edit warring or disruption by establishing a contentious revision, may identify a stable version prior to the edit war and request reversion to that version. Before making such a request, editors should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked. Administrators who have made substantive content changes to an article are considered involved and must not use their advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policies that bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally. "History only" review[edit] ShortcutWP:PPDRV If a deleted page is going through 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, blank it or replace the contents with {{Temporarily undeleted}} template or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to everyone via the page history. Protected generic file names[edit] Generic file names such as File:Photo.jpg, File:Example.jpg, File:Map.jpg, and File:Sound.wav are fully protected to prevent new versions from being uploaded. Furthermore, File:Map.jpg and File:Sound.wav are salted. Template protection[edit] Main page: Wikipedia:Template editor ShortcutsWP:TPROTWP:PINKLOCK A template-protected page can be edited only by administrators or users in the Template editors group. 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[6] 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. In borderline cases, extended confirmed protection or lower can be applied to high risk templates that the general editing community still needs to edit regularly. A full list of the pages under template protection can be found here. Editors may request edits to a template-protected page by proposing them on its talk page, using the {{Edit template-protected}} template if necessary to gain attention. Protection types[edit] Edit protection[edit] Edit protection restricts editing of a page, often due to vandalism or disputes, ensuring only experienced users can make changes (see above for more information). Creation protection (salting)[edit] ShortcutsWP:SALTWP:SKYBLUELOCK Administrators can prevent the creation of pages. This type of protection is useful for 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 can be found at Special:ProtectedTitles (see also historical lists). Preemptive 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". Editors 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. Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed,[2] or full. Due to the implementation of ACPERM, non-confirmed editors cannot create pages in mainspace; thus, semi-creation protection should be used only for protection of pages outside of mainspace. While creation-protection is usually permanent, temporary creation protection can be applied if a page is repeatedly recreated by a single user (or sockpuppets of that user, if applicable). Move protection[edit] ShortcutsWP:MOVPWP:GREENLOCK Move-protected pages, or more technically, fully 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. Highly visible pages that have no reason to be moved, such as the administrators' noticeboard and articles selected as "Today's featured article" on the main page. 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. All files and categories are implicitly move-protected, requiring file movers or administrators to rename files, and page movers or administrators to rename categories. Upload protection[edit] ShortcutsWP:UPLOAD-PWP:PURPLELOCK Upload-protected files, or more technically, fully upload-protected files, cannot be replaced with new versions except by an administrator. Upload protection does not protect file pages from editing. It can be applied by an administrator 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. (e.g., File:Map.png) As with full edit protection, administrators should avoid favoring one version over another, and protection should not be considered an endorsement of the current version. An exception to this rule is when they are protected due to upload vandalism. Uncommon protections[edit] Cascading protection[edit] "WP:CASCADE" redirects here. You may also be looking for Help:Cascading Style Sheets or Wikipedia:Cascade-protected items. ShortcutsWP:CASCADEWP:TURQUOISELOCK 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 templates, images and other media that are hosted on the English Wikipedia. Files stored on Commons are not protected by any other wiki's cascading protection and, if they are to be protected, must be either temporarily uploaded to the English Wikipedia or explicitly protected at Commons (whether manually or through cascading protection there). When operational, KrinkleBot cascade-protects Commons files transcluded at Wikipedia:Main Page/Tomorrow, Wikipedia:Main Page/Commons media protection and Main Page. As the bot's response time varies, media should not be transcluded on the main page (or its constituent templates) until after it has been protected. (This is particularly relevant to Template:In the news, for which upcoming images are not queued at Wikipedia:Main Page/Tomorrow.) Cascading protection: Should be used only to prevent vandalism when placed on particularly visible pages, such as the main page. Is available only for fully protected pages; it is disabled for lower levels of protection as it represents a workflow flaw. See below as well as this bug ticket for more information. Is not instantaneous; it can be several hours before it takes effect. See Phabricator:T20483 for more information. Should generally not be applied directly to templates or modules, as it will not protect transclusions inside <includeonly> tags or transclusions that depend on template parameters, but will protect the documentation subpage. See § Protection of templates below, for alternatives. The list of cascading-protected pages can be found at Wikipedia:Cascade-protected items. Requests to add or remove cascading protection on a page should be made at Wikipedia talk:Cascade-protected items as an edit request. Permanent protection[edit] Icon for pages that can be edited only by interface administrators ShortcutsWP:PPINDEFWP:INTPROTWP:REDLOCK Administrators cannot change or remove the protection for some areas on Wikipedia, which are permanently protected by the MediaWiki software: Edits to the MediaWiki namespace, which defines parts of the site interface, are restricted to administrators and interface administrators. Edits to system-wide CSS and JavaScript pages such as MediaWiki:common.js are further restricted to interface administrators. Edits to personal CSS and JavaScript pages such as User:Example/monobook.css and User:Example/vector-2022.js 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 inappropriately. Administrators may delete (but not edit or restore) these pages. Edits to personal JSON pages such as User:Example/data.json are restricted to the associated user and administrators. Such protection is called permanent or indefinite protection, and interface protection in the case of CSS and JavaScript pages. In addition to hard-coded protection, the following are usually fully protected for an indefinite period of time (though not necessarily with interface protection): Very visible pages, such as the Main Page. Pages that should not be modified for 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 {{citation needed}}, to prevent vandalism or denial of service attacks. This includes images or templates used in other highly visible or frequently transcluded pages. See Wikipedia:High-risk templates for more information. Office actions[edit] See also: Wikipedia:Office actions ShortcutsWP:WMF-PROWP:BLACKLOCK As outlined in Foundation:Policy:Office actions § Use of advanced rights by Foundation staff, pages can be protected by Wikimedia Foundation staff in response to issues such as copyright infringement or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff.[7] Deleted protections[edit] Superprotect[edit] ShortcutWP:SUPERPROTECT Superprotect was a level of protection[8], allowing editing only by Wikimedia Foundation employees who were in the Staff global group. It was implemented on August 10, 2014 and removed on November 5, 2015. It was never used on the English Wikipedia. For several years, the gadget namespace (which no longer exists) could only be edited by WMF staff, which has sometimes been referred to as superprotection even though it is unrelated to the above use. Cascading semi-protection[edit] Cascading semi-protection was formerly possible, but it was disabled in 2007 after users noticed that non-administrators could fully protect any page by transcluding it onto the page to which cascading semi-protection had been applied by an administrator. Pending changes protection level 2[edit] ShortcutWP:ORANGELOCK Originally, two levels of pending changes protection existed, where level 2 required edits by all users who are not pending changes reviewers to be reviewed. Following a community discussion, level 2 was retired from the English Wikipedia in January 2017. It was suggested then that "Pending changes level 1" be referred to in the future as simply "Pending changes".[9] Protection by namespace[edit] ShortcutWP:PROTNS Article talk pages[edit] ShortcutWP:ATPROT Modifications to a 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. Placing the {{Edit protected}} template on the talk page will draw the attention of administrators for implementing uncontroversial changes. Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of disruption. User talk pages[edit] ShortcutWP:UTPROT User talk pages are rarely protected. However, protection can be applied if there is severe vandalism or abuse. Users whose talk pages are protected may wish to have an unprotected user talk subpage linked conspicuously from their main talk page to allow good-faith comments from users that the protection restricts editing from. A user's request to have their own talk page protected is not a sufficient rationale by itself to protect the page, although requests can be considered if a reason is provided. Blocked users[edit] Blocked users' user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. It also prevents others from being able to use the talk page to communicate with the blocked editor. In extreme cases of abuse by the blocked user, such as abuse of the {{unblock}} template, re-blocking the user with talk page access removed should be preferred over applying protection to the page. If the user has been blocked and with the ability to edit their user talk page disabled, they should be informed of this in a block notice, subsequent notice, or message, and it should include information and instructions for appealing their block off-wiki, such as through the UTRS tool interface or, as a last recourse, the Arbitration Committee. When required, protection should be implemented for only a brief period, not exceeding the duration of the block. Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected. User pages[edit] ShortcutsWP:UPROTWP:UPPROT Base user pages (for example, the page User:Example, and not User:Example/subpage or User talk:Example) are automatically protected from creation or editing by unconfirmed accounts and anonymous IP users. An exception to this includes an unconfirmed registered account attempting to create or edit their own user page. IP editors and unconfirmed accounts are also unable to create or edit user pages that do not belong to a currently registered account. This protection is enforced by an edit filter.[10] Users may opt-out of this protection by placing {{unlocked userpage}} anywhere on their own user page. User pages and subpages within their own user space can be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or preemptively protected without good reason or cause.[11][12] Requests for protection specifically at uncommon levels (such as template protection) can be granted if the user has expressed a genuine and realistic need. When a filter is insufficient to stop user page vandalism, a user may choose to create a ".css" subpage (ex. User:Example/Userpage.css), copy all the contents of their user page onto the subpage, transclude the subpage by putting {{User:Example/Userpage.css}} on their user page, and then ask an administrator to fully protect their user page. Because user space pages that end in ".css" and ".js" are editable only by the user to which that user space belongs (and interface administrators), this will protect one's user page from further vandalism. Deceased users[edit] See also: Wikipedia:Deceased Wikipedians/Guidelines In the event of the confirmed death of a user, the user's user page (but not the user talk page) should be fully protected. Protection of templates[edit] ShortcutWP:PTPROT See also: Wikipedia:High-risk templates and Wikipedia:Template documentation Highly visible templates – those used on a large number of pages or frequently substituted – are often edit protected based on the degree of visibility, type of use, content, and other considerations. Protected templates should normally have the {{documentation}} template. It loads the unprotected /doc page, so that non-admins and IP-users can edit the documentation, categories and interwiki links. It also automatically adds {{pp-template}} to protected templates, which displays a small padlock in the top right corner and categorizes the template as protected. Only manually add {{pp-template}} to protected templates that don't use {{documentation}} (mostly the flag templates). Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside <includeonly> tags or transclusions that depend on template parameters, but will protect the template's documentation subpage. Instead, consider any of the following: If the set of subtemplates is static (even if large), protect them using normal protection mechanisms. If the set of subtemplates is unbounded, use MediaWiki:Titleblacklist to protect all subtemplates using a particular naming format (as is done for editnotice templates and subtemplates of Template:TFA title). Note: All editnotice templates (except those in userspace) are already protected via MediaWiki:Titleblacklist. They can be edited by admins, template editors and page movers only. Sandboxes[edit] See also: Wikipedia:About the sandbox Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The Wikipedia:Sandbox is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, or copyrights, should instead be warned and/or blocked. Available templates[edit] The following templates can be added at the very top of a page to indicate that it is protected: Protection templates Edit Move Pending changes Upload Generic {{pp}} {{pp-move}} {{pp-pc}} {{pp-upload}} BLP {{pp-blp}} – – – Blocked user's talk page {{pp-usertalk}} – – – Dispute {{pp-dispute}} {{pp-move-dispute}} – – Extended confirmed protection {{pp-extended}} – – – Long-term {{pp-semi-indef}} – – – Main Page image {{pp-main-page}} – – – Office {{pp-office}} – – – Sockpuppetry {{pp-sock}} – – – Templates and images {{pp-template}} – – {{pp-upload}} Vandalism {{pp-vandalism}} {{pp-move-vandalism}} – – Talk page {{Permanently protected}} {{Temporarily protected}} – – –Module:Protection banner On redirect pages, use the {{Redirect category shell}} template, which automatically categorizes by protection level, below the redirect line. A protection template may also be added below the redirect line, but it will serve only to categorize the page, as it will not be visible on the page, and it will have to be manually removed when protection is removed. See also[edit] MediaWiki:Protectedpagetext Special:ProtectedPages Special:ProtectedTitles Wikipedia:Edit lock Wikipedia:List of indefinitely protected pages Wikipedia:Requests for page protection Wikipedia:Rough guide to semi-protection Wikipedia:Make protection requests sparingly, an essay Wikipedia:Salting is usually a bad idea, an essay metawiki:Protected pages considered harmful metawiki:The Wrong Version Wikipedia:Protection policy/Padlocks Notes[edit] ^ Wikipedia:Requests for comment/Extended confirmed protection policy. ^ a b c Wikipedia:Requests for comment/Extended confirmed protection policy 2. ^ The extended confirmed restriction was previously known as the "500/30 rule" which differed slightly. ^ Should we use ECP on templates? discussion at the village pump. ^ Wikipedia talk:Protection Policy discussion to remove manual posting requirement ^ Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎ ^ Unlike with WP:SUPERPROTECT, admins technically can still edit or unprotect these pages, however, they should not do so without permission. ^ "Superprotect". Wikimedia Meta-Wiki. 2014-09-08. Retrieved 2024-03-20. ^ VPR RfC to remove PC2 ^ Please refer to Wikipedia:Requests for comment/Protect user pages by default and its talk page for community discussion related to a preventative measure for user pages. ^ Per discussion at Wikipedia talk:Protection policy/Archive 15 § Own userspace pages protection policy, June 2013 ^ Per discussion at Wikipedia:Administrators' noticeboard/Archive314 § Protecting an editor's user page or user space per their request, September 2019 vteAdministrators' guideArticles Advice for new administrators Blocking Cleaning backlogs Dealing with disputes Dealing with spam Deleting Edit filters Granting and revoking user rights History merging Protecting Reading list Rollback Tools, scripts and gadgets Viewing deleted pages and contributions Policies Administrator policy (WP:ADMIN) Banning policy (WP:BAN) Blocking policy (WP:BLOCK) Deletion policy (WP:DEL) Protection policy (WP:PROTECT) Revision deletion policy (WP:REVDEL) vteWikipedia key policies and guidelines (?) Five pillars Ignore all rules Content (?)P Verifiability No original research Neutral point of view What Wikipedia is not Biographies of living persons Copyright (Copyright violations) Image use Article titles G Notability Autobiography Citing sources Reliable sources Medicine Do not include copies of lengthy primary sources Plagiarism Don't create hoaxes Fringe theories Patent nonsense External links Conduct (?)P Civility Consensus Harassment Vandalism Ignore all rules No personal attacks Ownership of content Edit warring Dispute resolution Sockpuppetry No legal threats Child protection Paid-contribution disclosure G Assume good faith Conflict of interest Disruptive editing Do not disrupt Wikipedia to illustrate a point Etiquette Gaming the system Please do not bite the newcomers Courtesy vanishing Responding to threats of harm Talk page guidelines Signatures Deletion (?)P Deletion policy Proposed deletion Biographies Criteria for speedy deletion Attack page Oversight Revision deletion Enforcement (?)P Administrators Banning Blocking Page protection Editing (?)P Editing policy G Article size Summary style Be bold Disambiguation Hatnotes Broad-concept article Understandability Style Manual of Style Contents Accessibility Dates and numbers Images Layout Lead section Linking Lists Classification Categories, lists, and navigation templates Categorization Template namespace Project content (?)G Project namespace WikiProjects User pages User boxes Shortcuts Subpages WMF (?)P Terms of Use List of policies Friendly space policy Licensing and copyright Privacy policy List of all policies and guidelines P: List of policies G: List of guidelines Summaries of values and principles

JFK'S 'RACE TO SPACE' SPEECH

"John F. Kennedy speaks at Rice University" by NASA is in the public domain.

President Pitzer, Mr. Vice President, Governor, Congressman Thomas, Senator Wiley, and Congressman Miller, Mr. Webb, Mr. Bell, scientists, distinguished guests, and ladies and gentlemen:

I appreciate your president having made me an honorary visiting professor, and I will assure you that my first lecture will be very brief.

I am delighted to be here and I'm particularly delighted to be here on this occasion.

We meet at a college noted for knowledge, in a city noted for progress, in a State noted for strength, and we stand in need of all three, for we meet in an hour of change and challenge, in a decade of hope and fear, in an age of both knowledge and ignorance. The greater our knowledge increases, the greater our ignorance unfolds.

Despite the striking fact that most of the scientists that the world has ever known are alive and working today, despite the fact that this Nation's own scientific manpower is doubling every 12 years in a rate of growth more than three times that of our population as a whole, despite that, the vast stretches of the unknown and the unanswered and the unfinished still far outstrip our collective comprehension.

No man can fully grasp how far and how fast we have come, but condense, if you will, the 50,000 years of man's recorded history in a time span of but a half a century. Stated in these terms, we know very little about the first 40 years, except at the end of them advanced man had learned to use the skins of animals to cover them. Then about 10 years ago, under this standard, man emerged from his caves to construct other kinds of shelter. Only five years ago man learned to write and use a cart with wheels. Christianity began less than two years ago. The printing press came this year, and then less than two months ago, during this whole 50-year span of human history, the steam engine provided a new source of power.

Newton explored the meaning of gravity. Last month electric lights and telephones and automobiles and airplanes became available. Only last week did we develop penicillin and television and nuclear power, and now if America's new spacecraft succeeds in reaching Venus, we will have literally reached the stars before midnight tonight.

This is a breathtaking pace, and such a pace cannot help but create new ills as it dispels old, new ignorance, new problems, new dangers. Surely the opening vistas of space promise high costs and hardships, as well as high reward.

So it is not surprising that some would have us stay where we are a little longer to rest, to wait. But this city of Houston, this State of Texas, this country of the United States was not built by those who waited and rested and wished to look behind them. This country was conquered by those who moved forward - and so will space.

William Bradford, speaking in 1630 of the founding of the Plymouth Bay Colony, said that all great and honorable actions are accompanied with great difficulties, and both must be enterprised and overcome with answerable courage.

If this capsule history of our progress teaches us anything, it is that man, in his quest for knowledge and progress, is determined and cannot be deterred. The exploration of space will go ahead, whether we join in it or not, and it is one of the great adventures of all time, and no nation which expects to be the leader of other nations can expect to stay behind in the race for space.

Those who came before us made certain that this country rode the first waves of the industrial revolutions, the first waves of modern invention, and the first wave of nuclear power, and this generation does not intend to founder in the backwash of the coming age of space. We mean to be a part of it - we mean to lead it. For the eyes of the world now look into space, to the moon and to the planets beyond, and we have vowed that we shall not see it governed by a hostile flag of conquest, but by a banner of freedom and peace. We have vowed that we shall not see space filled with weapons of mass destruction, but with instruments of knowledge and understanding.

Yet the vows of this Nation can only be fulfilled if we in this Nation are first, and, therefore, we intend to be first. In short, our leadership in science and in industry, our hopes for peace and security, our obligations to ourselves as well as others, all require us to make this effort, to solve these mysteries, to solve them for the good of all men, and to become the world's leading space-faring nation.

We set sail on this new sea because there is new knowledge to be gained, and new rights to be won, and they must be won and used for the progress of all people. For space science, like nuclear science and all technology, has no conscience of its own. Whether it will become a force for good or ill depends on man, and only if the United States occupies a position of pre-eminence can we help decide whether this new ocean will be a sea of peace or a new terrifying theater of war. I do not say that we should or will go unprotected against the hostile misuse of space any more than we go unprotected against the hostile use of land or sea, but I do say that space can be explored and mastered without feeding the fires of war, without repeating the mistakes that man has made in extending his writ around this globe of ours

There is no strife, no prejudice, no national conflict in outer space as yet. Its hazards are hostile to us all. Its conquest deserves the best of all mankind, and its opportunity for peaceful cooperation may never come again. But why, some say, the moon? Why choose this as our goal? And they may well ask why climb the highest mountain? Why, 35 years ago, fly the Atlantic? Why does Rice play Texas?

We choose to go to the moon. We choose to go to the moon in this decade and do the other things, not because they are easy, but because they are hard, because that goal will serve to organize and measure the best of our energies and skills, because that challenge is one that we are willing to accept, one we are unwilling to postpone, and one which we intend to win, and the others, too.

It is for these reasons that I regard the decision last year to shift our efforts in space from low to high gear as among the most important decisions that will be made during my incumbency in the office of the Presidency.

In the last 24 hours we have seen facilities now being created for the greatest and most complex exploration in man's history. We have felt the ground shake and the air shattered by the testing of a Saturn C-1 booster rocket, many times as powerful as the Atlas which launched John Glenn, generating power equivalent to 10,000 automobiles with their accelerators on the floor. We have seen the site where five F-1 rocket engines, each one as powerful as all eight engines of the Saturn combined, will be clustered together to make the advanced Saturn missile, assembled in a new building to be built at Cape Canaveral as tall as a 48-story structure, as wide as a city block, and as long as two lengths of this field.

Within these last 19 months at least 45 satellites have circled the earth. Some 40 of them were "made in the United States of America" and they were far more sophisticated and supplied far more knowledge to the people of the world than those of the Soviet Union

The Mariner spacecraft now on its way to Venus is the most intricate instrument in the history of space science. The accuracy of that shot is comparable to firing a missile from Cape Canaveral and dropping it in this stadium between the 40-yard lines.

Transit satellites are helping our ships at sea to steer a safer course. Tiros satellites have given us unprecedented warnings of hurricanes and storms, and will do the same for forest fires and icebergs.

We have had our failures, but so have others, even if they do not admit them. And they may be less public.

To be sure, we are behind, and will be behind for some time in manned flight. But we do not intend to stay behind, and in this decade, we shall make up and move ahead.

The growth of our science and education will be enriched by new knowledge of our universe and environment, by new techniques of learning and mapping and observation, by new tools and computers for industry, medicine, the home as well as the school. Technical institutions, such as Rice, will reap the harvest of these gains

And finally, the space effort itself, while still in its infancy, has already created a great number of new companies, and tens of thousands of new jobs. Space and related industries are generating new demands in investment and skilled personnel, and this city and this State, and this region, will share greatly in this growth. What was once the furthest outpost on the old frontier of the West will be the furthest outpost on the new frontier of science and space. Houston, your City of Houston, with its Manned Spacecraft Center, will become the heart of a large scientific and engineering community. During the next 5 years the National Aeronautics and Space Administration expects to double the number of scientists and engineers in this area, to increase its outlays for salaries and expenses to $60 million a year; to invest some $200 million in plant and laboratory facilities; and to direct or contract for new space efforts over $1 billion from this Center in this City.

To be sure, all this costs us all a good deal of money. This year's space budget is three times what it was in January 1961, and it is greater than the space budget of the previous eight years combined. That budget now stands at $5,400 million a year - a staggering sum, though somewhat less than we pay for cigarettes and cigars every year. Space expenditures will soon rise some more, from 40 cents per person per week to more than 50 cents a week for every man, woman and child in the United States, for we have given this program a high national priority - even though I realize that this is in some measure an act of faith and vision, for we do not now know what benefits await us. But if I were to say, my fellow citizens, that we shall send to the moon, 240,000 miles away from the control station in Houston, a giant rocket more than 300 feet tall, the length of this football field, made of new metal alloys, some of which have not yet been invented, capable of standing heat and stresses several times more than have ever been experienced, fitted together with a precision better than the finest watch, carrying all the equipment needed for propulsion, guidance, control, communications, food and survival, on an untried mission, to an unknown celestial body, and then return it safely to earth, re-entering the atmosphere at speeds of over 25,000 miles per hour, causing heat about half that of the temperature of the sun - almost as hot as it is here today - and do all this, and do it right, and do it first before this decade is out - then we must be bold.

I'm the one who is doing all the work, so we just want you to stay cool for a minute. [laughter]

However, I think we're going to do it, and I think that we must pay what needs to be paid. I don't think we ought to waste any money, but I think we ought to do the job. And this will be done in the decade of the sixties. It may be done while some of you are still here at school at this college and university. It will be done during the term of office of some of the people who sit here on this platform. But it will be done. And it will be done before the end of this decade.

I am delighted that this university is playing a part in putting a man on the moon as part of a great national effort of the United States of America.

Many years ago the great British explorer George Mallory, who was to die on Mount Everest, was asked why did he want to climb it. He said, "Because it is there."

Well, space is there, and we're going to climb it, and the moon and the planets are there, and new hopes for knowledge and peace are there. And, therefore, as we set sail we ask God's blessing on the most hazardous and dangerous and greatest adventure on which man has ever embarked.

Thank you.

Current Page: 1

GRADE:9

Additional Information:

Rating: Words in the Passage: 1520 Unique Words: 750 Sentences: 81
Noun: 647 Conjunction: 266 Adverb: 120 Interjection: 2
Adjective: 147 Pronoun: 150 Verb: 346 Preposition: 273
Letter Count: 9,499 Sentiment: Positive Tone: Neutral (Slightly Formal) Difficult Words: 436
EdSearch WebSearch
Questions and Answers

Please wait while we generate questions and answers...

Ratings & Comments

Write a Review
5 Star
0
0
4 Star
0
0
3 Star
0
0
2 Star
0
0
1 Star
0
0
0

0 Ratings & 0 Reviews

Report an Error