Wikipedia talk:Protection policy

This page is not for proposing or discussing edits to protected pages.

To request or propose a change to a page that you are not able to edit, place a message on its talk page. If the page is fully protected, you may attract the attention of an admin to make the change by placing the {{edit fully-protected}} template above your request. Requests placed here will probably be removed or ignored.

If the page in question and its talk page are both protected please make your edit request at Wikipedia:Request for edit.
To request that a page be protected or unprotected, see Wikipedia:Requests for page protection.
To suggest that a move-protected page be renamed, see Wikipedia:Requested moves.
To request that a deleted page protected against re-creation be re-created or restored, see Wikipedia:Deletion review.
For information about protecting the main page featured article or other featured content, see Wikipedia:Main Page featured article protection.

This is the talk page for discussing improvements to the Protection policy page.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Shortcuts

Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18: 60 days

The project page associated with this talk page is an official policy on Wikipedia. Policies have wide acceptance among editors and are considered a standard for all users to follow. Please review policy editing recommendations before making any substantive change to this page. Always remember to keep cool when editing, and don't panic.

This page is written in American English, which has its own spelling conventions (color, defense, traveled) and some terms that are used in it may be different or absent from other varieties of English. According to the relevant style guide, this should not be changed without broad consensus.

Counter-Vandalism Unit

This page is within the scope of the Counter-Vandalism Unit, a WikiProject dedicated to combating vandalism on Wikipedia. You can help the CVU by watching the recent changes and undoing unconstructive edits. For more information go to the CVU's home page or see cleaning up vandalism.Counter-Vandalism UnitWikipedia:Counter-Vandalism UnitTemplate:Counter-Vandalism UnitCounter-Vandalism Unit articles

Superprotect

I'd like to talk about the story we're telling in WP:SUPERPROTECT. Compare these two versions:

"where the MediaViewer had been deactivated in a wheel war involving two administrators...the community was discussing what to do"
"used the same day to override community consensus"

One of these is from our policy. One of these is from Meta-Wiki.

Here are the diffs that seem relevant to me, at 21:58, 22:13, 22:15 on 9 August. I believe that the technical change made it impossible to use Media Viewer, even if you wanted to use it yourself and enabled it in your own preferences. The admin who made the first and third edits was de-sysopped as soon as their policy allowed them to do so.

Additionally, this tool was used several times at other wikis, at the request of communities, to solve problems they were having.

I think that the story we're telling is ultimately misleading. Perhaps we should change it, or maybe just remove it? WhatamIdoing (talk) 01:12, 19 March 2024 (UTC)[reply]

Would this be acceptable as a replacement for that paragraph?

Superprotect was a level of protection, 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 only used on two occasions on other Wikipedia editions.

I think that's sufficient for something that something that happened almost ten years ago. The current version of the paragraph is a little too editorial and the linked MediaWiki page and its talk page are the appropriate locations for a historical summary and any discussion on it. Daniel Quinlan (talk) 00:55, 20 March 2024 (UTC)[reply]

Yes, I think that would be much better.

About the last sentence, I know it was used on Wikidata, and I'm not certain that it was only twice. (I heard once five total uses, but I don't know whether that's true.) Perhaps the more relevant point would be "never used at the English Wikipedia". WhatamIdoing (talk) 01:23, 20 March 2024 (UTC)[reply]

That works for me. Daniel Quinlan (talk) 03:43, 20 March 2024 (UTC)[reply]

Would you like to make the change? WhatamIdoing (talk) 03:47, 20 March 2024 (UTC)[reply]

Done. Daniel Quinlan (talk) 03:54, 20 March 2024 (UTC)[reply]

WP:ECR and WP:PREEMPTIVE

I've had some thoughts regarding the application of WP:PREEMPTIVE to articles covered by an extended-confirmed restriction that I'd like to hear other editors' opinions on. At the moment, my experience of WP:RFPP is that pages within the scope of an ECR are declined if there haven't been any edits to the page by non-XC editors. However, waiting until a non-extended-confirmed editor makes an edit to such a page (presumably innocently), just for that edit to be reverted and the page then protected, seems unnecessarily WP:BITEy to me.

The language in WP:PREEMPTIVE (that pre-emptive protection is contrary to the open nature of Wikipedia) suggests that the reason for it not being permitted is because we shouldn't be disallowing edits to an article from non-confirmed/XC editors when there hasn't been any disruption to said article from those editors. However, to me, the ECR falls in a different situation to this -- edits by non-XC editors to ECR-covered articles are already disallowed; therefore, applying protection in these cases is only enforcing a restriction that already exists, rather than creating a new one (as page protection would otherwise generally be doing).

I'd therefore suggest that it might be worth excluding pages covered by the extended-confirmed restriction from the policy against pre-emptive protection. To be clear, this wouldn't place any obligation on administrators to actively seek out and protect articles that are covered by an ECR; but rather, would mean that there isn't any policy forbidding them from being protected once an admin becomes aware of them (e.g. at RFPP).

I welcome others' thoughts on this, and let me know if there are any queries about anything I've said. All the best, ‍—‍a smart kitten_[meow] 11:54, 7 May 2024 (UTC)[reply]

There's no requirement spelled out in WP:ECR to always revert edits made by non-EC users if the topic area is covered by ECR. It says may be enforced and not "must be enforced", after all. Community-authorized extended confirmed restrictions such as the one in WP:GS/RUSUKR are similarly phrased.

Bearing that in mind, if a non-EC user's edit is good faith and improves the article, reverting the edit does indeed seem bitey and I personally wouldn't automatically revert such an edit even if I was protecting the article. And with that approach, if it's necessary to revert an edit then there should always be a good revert reason that can be put into an edit summary and a user talk page explanation such as NPOV, sourcing requirements, or some other good reason that explains the reversion rather than a bitey "you're not extended confirmed" reason.

Anyhow, I'm strongly opposed to the idea of adding this exception to WP:PREEMPTIVE. It's a core principle and there are a high number of articles falling under ECR right now that have zero disruption which also occasionally receive good faith and beneficial edits by non-EC editors. Making ECP a virtual requirement for those articles would open up the floodgates to create a deluge of article requests on WP:RFPP and I think increasing the number of articles under ECP by such a huge number would be much more bitey than the situation we have today. Daniel Quinlan (talk) 22:31, 7 May 2024 (UTC)[reply]