THE CONE

THE CONE

- By H.G. Wells
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 WP:PP (disambiguation) and WP:PROTECT (disambiguation). 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 there is disruption that cannot be prevented through other means such as blocks. Wikipedia is built on the principle that anyone can edit and therefore aims to have as many 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 solely as a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed. Instead, protection is used when vandalism, disruption, or abuse by multiple users is occurring at a frequency that warrants protection. The duration of protection should be as short as possible and at the lowest protection level sufficient to stop the disruption, allowing edits from as many productive users as possible. Exceptions include the Main Page, along with its templates and images, which are indefinitely fully protected. Additionally, Today's Featured Article is typically semi-protected from the day before its scheduled appearance on the Main Page until the day after it leaves. 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 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 more than 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. ShortcutWP:UNPROTPOLExcept 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. Users can request unprotection or a reduction in protection level by asking the administrator who applied the protection on the administrator's user talk page. If the administrator is inactive, no longer an administrator, or does not respond, then a request 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 administrator. Logged-in editors will 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 Normal editing* 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 for a template editor to be able to edit extended confirmed protected pages, they 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. Semi-protection is generally a better option for articles with a high edit rate as well as articles affected by issues difficult for pending changes reviewers to detect, such as non-obvious vandalism, plausible-sounding misinformation, and hard-to-detect copyright violations. 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, administrators, and bots. Extended confirmed is automatically granted to users on the edit following the account meeting the criteria of being at least 30 days old and having 500 edits.[1] 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.[2] 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).[3] 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.[4] 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.[5] Extended confirmed protection can be applied at the discretion of an administrator when creation-protecting a page.[3] 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.[6] 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 8517 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[7] 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. Create protection of any duration may be applied to pages being repeatedly recreated in violation of policy using the lowest protection level sufficient to stop the disruption (autoconfirmed, extended-confirmed,[3] 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. Move protection of any duration may be applied to pages being repeatedly moved in violation of policy using the lowest protection level sufficient to stop the disruption (extended-confirmed or full). Due to the implementation of ACPERM, non-confirmed editors cannot move pages so semi-move protection has no effect. 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] Main page: 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.[8] Retired protections[edit] Superprotect[edit] ShortcutWP:SUPERPROTECT Superprotect was a level of protection,[9] 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".[10] 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.[11] 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.[12][13] 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}} – – – Indefinite {{pp-semi-indef}} {{pp-move-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] ^ For accounts meeting the 30-day requirement, the permission is added on the edit following the 500th (i.e., the 501st edit). For accounts meeting the edit count requirement before the 30-day requirement, the permission is granted on the edit following the account reaching 30 days in age. ^ 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
1 The night was hot and overcast, the sky red, rimmed with the lingering sunset of mid-summer. They sat at the open window, trying to fancy the air was fresher there. The trees and shrubs of the garden stood stiff and dark; beyond in the roadway a gas-lamp burnt, bright orange against the hazy blue of the evening. Farther were the three lights of the railway signal against the lowering sky. The man and woman spoke to one another in low tones.
2 "He does not suspect?" said the man, a little nervously.
3 "Not he," she said peevishly, as though that too irritated her. "He thinks of nothing but the works and the prices of fuel. He has no imagination, no poetry."
4 "None of these men of iron have," he said sententiously. "They have no hearts."
5 "He has not," she said. She turned her discontented face towards the window. The distant sound of a roaring and rushing drew nearer and grew in volume; the house quivered; one heard the metallic rattle of the tender. As the train passed, there was a glare of light above the cutting and a driving tumult of smoke; one, two, three, four, five, six, seven, eight black oblongs - eight trucks - passed across the dim grey of the embankment, and were suddenly extinguished one by one in the throat of the tunnel, which, with the last, seemed to swallow down train, smoke, and sound in one abrupt gulp.
6 "This country was all fresh and beautiful once," he said; "and now - it is Gehenna. Down that way - nothing but pot-banks and chimneys belching fire and dust into the face of heaven... But what does it matter? An end comes, an end to all this cruelty... To-morrow." He spoke the last word in a whisper.
7 "To-morrow," she said, speaking in a whisper too, and still staring out of the window.
8 "Dear!" he said, putting his hand on hers.
9 She turned with a start, and their eyes searched one another's. Hers softened to his gaze. "My dear one!" she said, and then: "It seems so strange - that you should have come into my life like this - to open - " She paused.
10 "To open?" he said.
11 "All this wonderful world - " she hesitated, and spoke still more softly - "this world of love to me."
12 Then suddenly the door clicked and closed. They turned their heads, and he started violently back. In the shadow of the room stood a great shadowy figure - silent. They saw the face dimly in the half-light, with unexpressive dark patches under the penthouse brows. Every muscle in Raut's body suddenly became tense. When could the door have opened? What had he heard? Had he heard all? What had he seen? A tumult of questions.
13 The new-comer's voice came at last, after a pause that seemed interminable. "Well?" he said.
14 "I was afraid I had missed you, Horrocks," said the man at the window, gripping the window-ledge with his hand. His voice was unsteady.
15 The clumsy figure of Horrocks came forward out of the shadow. He made no answer to Raut's remark. For a moment he stood above them.
16 The woman's heart was cold within her. "I told Mr. Raut it was just possible you might come back," she said, in a voice that never quivered.
17 Horrocks, still silent, sat down abruptly in the chair by her little work-table. His big hands were clenched; one saw now the fire of his eyes under the shadow of his brows. He was trying to get his breath. His eyes went from the woman he had trusted to the friend he had trusted, and then back to the woman.
18 By this time and for the moment all three half understood one another. Yet none dared say a word to ease the pent-up things that choked them.
19 It was the husband's voice that broke the silence at last.
20 "You wanted to see me?" he said to Raut.
21 Raut started as he spoke. "I came to see you," he said, resolved to lie to the last.
22 "Yes," said Horrocks.
23 "You promised," said Raut, "to show me some fine effects of moonlight and smoke."
24 "I promised to show you some fine effects of moonlight and smoke," repeated Horrocks in a colourless voice.
25 "And I thought I might catch you to-night before you went down to the works," proceeded Raut, "and come with you."
26 There was another pause. Did the man mean to take the thing coolly? Did he after all know? How long had he been in the room? Yet even at the moment when they heard the door, their attitudes... Horrocks glanced at the profile of the woman, shadowy pallid in the half-light. Then he glanced at Raut, and seemed to recover himself suddenly. "Of course," he said, "I promised to show you the works under their proper dramatic conditions. It's odd how I could have forgotten."
27 "If I am troubling you - " began Raut.
28 Horrocks started again. A new light had suddenly come into the sultry gloom of his eyes. "Not in the least," he said.
29 "Have you been telling Mr. Raut of all these contrasts of flame and shadow you think so splendid?" said the woman, turning now to her husband for the first time, her confidence creeping back again, her voice just one half-note too high. "That dreadful theory of yours that machinery is beautiful, and everything else in the world ugly. I thought he would not spare you, Mr. Raut. It's his great theory, his one discovery in art."
30 "I am slow to make discoveries," said Horrocks grimly, damping her suddenly.
"But what I discover..." He stopped.
31 "Well?" she said.
32 "Nothing;" and suddenly he rose to his feet.
33 "I promised to show you the works," he said to Raut, and put his big, clumsy hand on his friend's shoulder. "And you are ready to go?"
34 "Quite," said Raut, and stood up also.
35 There was another pause. Each of them peered through the indistinctness of the dusk at the other two. Horrocks' hand still rested on Raut's shoulder. Raut half fancied still that the incident was trivial after all. But Mrs. Horrocks knew her husband better, knew that grim quiet in his voice, and the confusion in her mind took a vague shape of physical evil. "Very well," said Horrocks, and, dropping his hand, turned towards the door.
36 "My hat?" Raut looked round in the half-light.
37 "That's my work-basket," said Mrs. Horrocks, with a gust of hysterical laughter. Their hands came together on the back of the chair. "Here it is!" he said. She had an impulse to warn him in an undertone, but she could not frame a word. "Don't go!" and "Beware of him!" struggled in her mind, and the swift moment passed. 38 "Got it?" said Horrocks, standing with the door half open.
39 Raut stepped towards him. "Better say good-bye to Mrs. Horrocks," said the ironmaster, even more grimly quiet in his tone than before.
40 Raut started and turned. "Good-evening, Mrs. Horrocks," he said, and their hands touched.
41 Horrocks held the door open with a ceremonial politeness unusual in him towards men. Raut went out, and then, after a wordless look at her, her husband followed. She stood motionless while Raut's light footfall and her husband's heavy tread, like bass and treble, passed down the passage together. The front door slammed heavily. She went to the window, moving slowly, and stood watching - leaning forward. The two men appeared for a moment at the gateway in the road, passed under the street lamp, and were hidden by the black masses of the shrubbery. The lamp-light fell for a moment on their faces, showing only unmeaning pale patches, telling nothing of what she still feared, and doubted, and craved vainly to know. Then she sank down into a crouching attitude in the big arm-chair, her eyes wide open and staring out at the red lights from the furnaces that flickered in the sky. An hour after she was still there, her attitude scarcely changed.
42 The oppressive stillness of the evening weighed heavily upon Raut. They went side by side down the road in silence, and in silence turned into the cinder-made by-way that presently opened out the prospect of the valley.
43 A blue haze, half dust, half mist, touched the long valley with mystery. Beyond were Hanley and Etruria, grey and dark masses, outlined thinly by the rare golden dots of the street lamps, and here and there a gaslit window, or the yellow glare of some late-working factory or crowded public-house. Out of the masses, clear and slender against the evening sky, rose a multitude of tall chimneys, many of them reeking, a few smokeless during a season of "play." Here and there a pallid patch and ghostly stunted beehive shapes showed the position of a pot-bank, or a wheel, black and sharp against the hot lower sky, marked some colliery where they raise the iridescent coal of the place. Nearer at hand was the broad stretch of railway, and half invisible trains shunted - a steady puffing and rumbling, with every run a ringing concussion and a rhythmic series of impacts, and a passage of intermittent puffs of white steam across the further view. And to the left, between the railway and the dark mass of the low hill beyond, dominating the whole view, colossal, inky-black, and crowned with smoke and fitful flames, stood the great cylinders of the Jeddah Company Blast Furnaces, the central edifices of the big ironworks of which Horrocks was the manager. They stood heavy and threatening, full of an incessant turmoil of flames and seething molten iron, and about the feet of them rattled the rolling-mills, and the steam hammer beat heavily and splashed the white iron sparks hither and thither. Even as they looked, a truckful of fuel was shot into one of the giants, and the red flames gleamed out, and a confusion of smoke and black dust came boiling upwards towards the sky.
44 "Certainly you get some fine effects of colour with your furnaces," said Raut, breaking a silence that had become apprehensive.
45 Horrocks grunted. He stood with his hands in his pockets, frowning down at the dim steaming railway and the busy ironworks beyond, frowning as if he were thinking out some knotty problem.
46 Raut glanced at him and away again. "At present your moonlight effect is hardly ripe," he continued, looking upward. "The moon is still smothered by the vestiges of daylight."
47 Horrocks stared at him with the expression of a man who has suddenly awakened. "Vestiges of daylight?... Of course, of course." He too looked up at the moon, pale still in the midsummer sky. "Come along," he said suddenly, and, gripping Raut's arm in his hand, made a move towards the path that dropped from them to the railway.
48 Raut hung back. Their eyes met and saw a thousand things in a moment that their eyes came near to say. Horrocks' hand tightened and then relaxed. He let go, and before Raut was aware of it, they were arm in arm, and walking, one unwillingly enough, down the path.
49 "You see the fine effect of the railway signals towards Burslem," said Horrocks, suddenly breaking into loquacity, striding fast, and tightening the grip of his elbow the while. "Little green lights and red and white lights, all against the haze. You have an eye for effect, Raut. It's a fine effect. And look at those furnaces of mine, how they rise upon us as we come down the hill. That to the right is my pet - seventy feet of him. I packed him myself, and he's boiled away cheerfully with iron in his guts for five long years. I've a particular fancy for him. That line of red there - a lovely bit of warm orange you'd call it, Raut - that's the puddlers' furnaces, and there, in the hot light, three black figures - did you see the white splash of the steam-hammer then? - that's the rolling mills. Come along! Clang, clatter, how it goes rattling across the floor! Sheet tin, Raut - amazing stuff. Glass mirrors are not in it when that stuff comes from the mill. And, squelch! - there goes the hammer again. Come along!"
50 He had to stop talking to catch at his breath. His arm twisted into Raut's with benumbing tightness. He had come striding down the black path towards the railway as though he was possessed. Raut had not spoken a word, had simply hung back against Horrocks' pull with all his strength.
51 "I say," he said now, laughing nervously, but with an undernote of snarl in his voice, "why on earth are you nipping my arm off, Horrocks, and dragging me along like this?"
52 At length Horrocks released him. His manner changed again. "Nipping your arm off?" he said. "Sorry. But it's you taught me the trick of walking in that friendly way."
53 "You haven't learnt the refinements of it yet then," said Raut, laughing artificially again. "By Jove! I'm black and blue." Horrocks offered no apology. They stood now near the bottom of the hill, close to the fence that bordered the railway. The ironworks had grown larger and spread out with their approach. They looked up to the blast furnaces now instead of down; the further view of Etruria and Hanley had dropped out of sight with their descent. Before them, by the stile rose a notice-board, bearing still dimly visible, the words "BEWARE OF THE TRAINS" half hidden by splashes of coaly mud.
54 "Fine effects," said Horrocks, waving his arm. "Here comes a train. The puffs of smoke, the orange glare, the round eye of light in front of it, the melodious rattle. Fine effects! But these furnaces of mine used to be finer, before we shoved cones in their throats, and saved the gas."
55 "How?" said Raut. "Cones?"
56 "Cones, my man, cones. I'll show you one nearer. The flames used to flare out of the open throats, great - what is it? - pillars of cloud by day, red and black smoke, and pillars of fire by night. Now we run it off in pipes, and burn it to heat the blast, and the top is shut by a cone. You'll be interested in that cone." 57 "But every now and then," said Raut, "you get a burst of fire and smoke up there." 58 "The cone's not fixed, it's hung by a chain from a lever, and balanced by an equipoise. You shall see it nearer. Else, of course, there'd be no way of getting fuel into the thing. Every now and then the cone dips, and out comes the flare." 59 "I see," said Raut. He looked over his shoulder. "The moon gets brighter," he said.
60 "Come along," said Horrocks abruptly, gripping his shoulder again, and moving him suddenly towards the railway crossing. And then came one of those swift incidents, vivid, but so rapid that they leave one doubtful and reeling. Halfway across, Horrocks' hand suddenly clenched upon him like a vice, and swung him backward and through a half-turn, so that he looked up the line. And there a chain of lamp-lit carriage-windows telescoped swiftly as it came towards them, and the red and yellow lights of an engine grew larger and larger, rushing down upon them. As he grasped what this meant, he turned his face to Horrocks, and pushed with all his strength against the arm that held him back between the rails. The struggle did not last a moment. Just as certain as it was that Horrocks held him there, so certain was it that he had been violently lugged out of danger.
61 "Out of the way," said Horrocks, with a gasp, as the train came rattling by, and they stood panting by the gate into the ironworks.
62 "I did not see it coming," said Raut, still, even in spite of his own apprehensions, trying to keep up an appearance of ordinary intercourse.
63 Horrocks answered with a grunt. "The cone," he said, and then, as one who recovers himself, "I thought you did not hear."
64 "I didn't," said Raut.
65 "I wouldn't have had you run over then for the world," said Horrocks.
66 "For a moment I lost my nerve," said Raut.
67 Horrocks stood for half a minute, then turned abruptly towards the ironworks again. "See how fine these great mounds of mine, these clinker-heaps, look in the night! That truck yonder, up above there! Up it goes, and out-tilts the slag. See the palpitating red stuff go sliding down the slope. As we get nearer, the heap rises up and cuts the blast furnaces. See the quiver up above the big one. Not that way! This way, between the heaps. That goes to the puddling furnaces, but I want to show you the canal first." He came and took Raut by the elbow, and so they went along side by side. Raut answered Horrocks vaguely. What, he asked himself, had really happened on the line? Was he deluding himself with his own fancies, or had Horrocks actually held him back in the way of the train? Had he just been within an ace of being murdered?
68 Suppose this slouching, scowling monster did know anything? For a minute or two then Raut was really afraid for his life, but the mood passed as he reasoned with himself. After all, Horrocks might have heard nothing. At any rate, he had pulled him out of the way in time. His odd manner might be due to the mere vague jealousy he had shown once before. He was talking now of the ash-heaps and the canal.
69 "Eigh?" said Horrocks.
70 "What?" said Raut. "Rather! The haze in the moonlight. Fine!"
71 "Our canal," said Horrocks, stopping suddenly. "Our canal by moonlight and firelight is an immense effect. You've never seen it? Fancy that! You've spent too many of your evenings philandering up in Newcastle there. I tell you, for real florid effects - But you shall see. Boiling water..."
72 As they came out of the labyrinth of clinker-heaps and mounds of coal and ore, the noises of the rolling-mill sprang upon them suddenly, loud, near, and distinct. Three shadowy workmen went by and touched their caps to Horrocks. Their faces were vague in the darkness. Raut felt a futile impulse to address them, and before he could frame his words, they passed into the shadows. Horrocks pointed to the canal close before them now: a weird-looking place it seemed, in the blood-red reflections of the furnaces. The hot water that cooled the tuyeres came into it, some fifty yards up - a tumultuous, almost boiling affluent, and the steam rose up from the water in silent white wisps and streaks, wrapping damply about them, an incessant succession of ghosts coming up from the black and red eddies, a white uprising that made the head swim. The shining black tower of the larger blast-furnace rose overhead out of the mist, and its tumultuous riot filled their ears. Raut kept away from the edge of the water, and watched Horrocks.
73 "Here it is red," said Horrocks, "blood-red vapour as red and hot as sin; but yonder there, where the moonlight falls on it, and it drives across the clinker-heaps, it is as white as death."
74 Raut turned his head for a moment, and then came back hastily to his watch on Horrocks. "Come along to the rolling-mills," said Horrocks. The threatening hold was not so evident that time, and Raut felt a little reassured. But all the same, what on earth did Horrocks mean about "white as death" and "red as sin?" Coincidence, perhaps?
75 They went and stood behind the puddlers for a little while, and then through the rolling-mills, where amidst an incessant din the deliberate steam-hammer beat the juice out of the succulent iron, and black, half-naked Titans rushed the plastic bars, like hot sealing-wax, between the wheels. "Come on," said Horrocks in Raut's ear, and they went and peeped through the little glass hole behind the tuyeres, and saw the tumbled fire writhing in the pit of the blast-furnace. It left one eye blinded for a while. Then, with green and blue patches dancing across the dark, they went to the lift by which the trucks of ore and fuel and lime were raised to the top of the big cylinder.
76 And out upon the narrow rail that overhung the furnace, Raut's doubts came upon him again. Was it wise to be here? If Horrocks did know - everything! Do what he would, he could not resist a violent trembling. Right under foot was a sheer depth of seventy feet. It was a dangerous place. They pushed by a truck of fuel to get to the railing that crowned the place. The reek of the furnace, a sulphurous vapor streaked with pungent bitterness, seemed to make the distant hillside of Hanley quiver. The moon was riding out now from among a drift of clouds, halfway up the sky above the undulating wooded outlines of Newcastle. The steaming canal ran away from below them under an indistinct bridge, and vanished into the dim haze of the flat fields towards Burslem.
77 "That's the cone I've been telling you of," shouted Horrocks; "and, below that, sixty feet of fire and molten metal, with the air of the blast frothing through it like gas in soda-water."
78 Raut gripped the hand-rail tightly, and stared down at the cone. The heat was intense. The boiling of the iron and the tumult of the blast made a thunderous accompaniment to Horrocks' voice. But the thing had to be gone through now. Perhaps, after all...
79 "In the middle," bawled Horrocks, "temperature near a thousand degrees. If you were dropped into it... flash into flame like a pinch of gunpowder in a candle. Put your hand out and feel the heat of his breath. Why, even up here I've seen the rain-water boiling off the trucks. And that cone there. It's a damned sight too hot for roasting cakes. The top side of it's three hundred degrees."
80 "Three hundred degrees!" said Raut.
81 "Three hundred centigrade, mind!" said Horrocks. "It will boil the blood out of you in no time."
82 "Eigh?" said Raut, and turned.
83 "Boil the blood out of you in... No, you don't!"
84 "Let me go!" screamed Raut. "Let go my arm!"
85 With one hand he clutched at the hand-rail, then with both. For a moment the two men stood swaying. Then suddenly, with a violent jerk, Horrocks had twisted him from his hold. He clutched at Horrocks and missed, his foot went back into empty air; in mid-air he twisted himself, and then cheek and shoulder and knee struck the hot cone together.
86 He clutched the chain by which the cone hung, and the thing sank an infinitesimal amount as he struck it. A circle of glowing red appeared about him, and a tongue of flame, released from the chaos within, flickered up towards him. An intense pain assailed him at the knees, and he could smell the singeing of his hands. He raised himself to his feet, and tried to climb up the chain, and then something struck his head. Black and shining with the moonlight, the throat of the furnace rose about him.
87 Horrocks, he saw, stood above him by one of the trucks of fuel on the rail. The gesticulating figure was bright and white in the moonlight, and shouting, "Fizzle, you fool! Fizzle, you hunter of women! You hot-blooded hound! Boil! boil! boil!" 88 Suddenly he caught up a handful of coal out of the truck, and flung it deliberately, lump after lump, at Raut.
89 "Horrocks!" cried Raut. "Horrocks!"
90 He clung crying to the chain, pulling himself up from the burning of the cone. Each missile Horrocks flung hit him. His clothes charred and glowed, and as he struggled the cone dropped, and a rush of hot suffocating gas whooped out and burned round him in a swift breath of flame.
91 His human likeness departed from him. When the momentary red had passed, Horrocks saw a charred, blackened figure, its head streaked with blood, still clutching and fumbling with the chain, and writhing in agony - a cindery animal, an inhuman, monstrous creature that began a sobbing intermittent shriek.
92 Abruptly, at the sight, the ironmaster's anger passed. A deadly sickness came upon him. The heavy odour of burning flesh came drifting up to his nostrils. His sanity returned to him.
93 "God have mercy upon me!" he cried. "O God! what have I done?"
94 He knew the thing below him, save that it still moved and felt, was already a dead man - that the blood of the poor wretch must be boiling in his veins. An intense realisation of that agony came to his mind, and overcame every other feeling. For a moment he stood irresolute, and then, turning to the truck, he hastily tilted its contents upon the struggling thing that had once been a man. The mass fell with a thud, and went radiating over the cone. With the thud the shriek ended, and a boiling confusion of smoke, dust, and flame came rushing up towards him. As it passed, he saw the cone clear again.
95 Then he staggered back, and stood trembling, clinging to the rail with both hands. His lips moved, but no words came to them.
96 Down below was the sound of voices and running steps. The clangour of rolling in the shed ceased abruptly.

Current Page: 1

GRADE:6

Additional Information:

Rating: A Words in the Passage: 900 Unique Words: 1,134 Sentences: 359
Noun: 1356 Conjunction: 366 Adverb: 274 Interjection: 11
Adjective: 373 Pronoun: 411 Verb: 683 Preposition: 559
Letter Count: 18,409 Sentiment: Positive / Positive / Positive Tone: Neutral Difficult Words: 676
EdSearch WebSearch

Report an Error