Wikipedia talk:Protection policy

"Protection is not an endorsement of the current version"

>Protection is not an endorsement of the current version I have to say that this policy offends me. I get in an edit war with some one-minded user, I goto the trouble of explaining every edit I make on the talk page, and they simply revert my edits repeatedly without so much as a reply. So what happens? the page gets protected under THEIR version. If one user goes through the trouble of explaining their edits, and another is reverting without discussing using offensive edit notes, why should their version be graced with the benefit of sitting around as the protected version for god knows how long until I am allowed to request unprotection? And what good will that do? So long as their version is protected, they are not going to discuss the changes. So as soon as it's unprotected, it's just going to continue warring. TheHYPO 18:09, 24 February 2007 (UTC)

The glib answer is to refer you to meta:The Wrong Version.

The longer, more serious answer, is to say that it is in no way whatsoever the responsibility of an intervening administrator who chooses to protect a page to prevent edit warring or other disruptive action to decide which version of a page ought to be the one that is preserved. The only exception is content which is immediately harmful, such as potentially libellous content. This goes to the heart of the reasons that protection is used. Protection is essentially used to stop edit wars and force people to engage in discussion on the talk page. If someone is clearly not explaining their edits, then it should be easy to build a consensus for the version that is well explained, which can be applied once the article is unprotected. Disruptive users who refuse to cooperate in discussion, or refuse to participate in consensus building, can be dealt with through other means. --bainer (talk) 06:38, 28 February 2007 (UTC)

But you've made my point for me. "Protection is essentially used to stop edit wars and force people to engage in discussion". The page in this was protected WHILE one party had explained all their edits on the talk page and the other party was blindly reverting anyway. And the blind reverter ended up having their version protected. There is no way this situation would cause them to engage in discussion and at worst, may validate their feeling that they are right to just revert without discussion. It's one thing if, say, it were an article like The Simpsons where there are a dozen editors who watch the page and read the 'talk' daily, and there will be lots of outside input towards consensus, but when it's a small page with little watch-ship, noone's going to discuss the issues while the page is protected, and there won't be any consensus beyond the one party who has explained themself. People who are disruptive and refuse to participate in consensus building can be dealt with through other means, I don't see why protection was warrented in this case, where one party had already explained themself, and the other was blindly reverting. This should have been dealt with via the 'other means' you refer to. TheHYPO 08:28, 9 March 2007 (UTC)

I've felt vaguely similar concerns, but not over general quality so much as a very specific issue: references. In principle, everything on WIkipedia is supposed to be verifiable; surely protection therefore is at least a tiny "endorsement" to the extent that it means the page consists of factual (if possibly irrelevant/badly written/NPOV) content? If not, then… well… perhaps a qualification for protection should be citing sources, or at least having the "no cited sources" warning. Right up until I encountered the phrase "not an endorsement of the current version", I was feeling very good about the fact that at least some pages are "guarenteed" trustworthy through protection. To put this another way, I'm wondering if a page has ever been locked, or ever would be, while carrying an "unreferenced" tag (which in my opinion would actually be a good thing, so that articles wouldn't just dwell in limbo but immediately stick to that warning until the information is verified by someone). How, if at all, has this been discussed? $\sim$ Lenoxus " * " 16:38, 27 March 2007 (UTC)

Protection of archives

I just got an idea for an addition to the protection policy. I think that any archives of talk pages that haven't been edited for a week (to ensure the archive is complete) should be protected. This would prevent the vast majority of vandalism or accidental responses to cut-and-paste or move archive pages.

Also, it wouldn't be too hard to write a bot that would do this automatically. It would have sysop status so it could protect pages, and it would simply protect any page in the talk or user talk namespaces that has the {{talkarchive}} tag, has had no edits for a week, has the word archive in its name, and is a subpage of a page that links to them.

I see no downside to this addition to policy, and it would certainly be very useful, so I'd like to establish some consensus here before adding it to the policy. Pyrospirit ^{Flames Fire} 02:13, 28 February 2007 (UTC)

You are both proposing the creation of an admin bot and a change in policy to make archives uneditable? That's quite silly. There is nothing special about archived talk pages. There are various reasons to edit them (bypass redirects when certain redirects are deleted, fix transclusions of certain templates, rm categories, etc). The goal should be to ensure that archives are useful for future readers, not making sure that their state is completely unedited from the moment they have been archived.

And of course, we don't protect pages to prevent against vandalism that hasn't already happened — there is wide consensus on this matter. And it is doubtful that consensus regarding the creation of admin bots is going to change, especially for this issue — if protecting the main page isn't enough to change consensus, the protection of talk archives is not going to. --- RockMFR 00:15, 12 March 2007 (UTC)

Agreed. Protection is very un-wikiwiki like and using it any more then unnecessary is a Bad Thing♣. ---J.S (T/C/WRE) 06:21, 12 March 2007 (UTC)

Indefinite Sprotection on Userpages

The line User pages (but not user talk pages), when requested by the user is kind of odd. I've seen a couple requests at RPP quoting this. The question is do we really need this? According to WP:USERPAGE, while the userpages are in your userspace, you don't own them. Others can/do make changes (especially in cases of WP:UBM). Should we continue to allow users to just arbitrarily ask for indefinite sprotection of anything they want in their userspace? -Royalguard11(Talk·Review Me!) 02:39, 8 March 2007 (UTC)

My understanding is that it's not really supposed to happen. The current policy states, "Semi-protection should not be used: As a preemptive measure against vandalism before any vandalism has occurred." -- zzuuzz^(talk) 02:53, 8 March 2007 (UTC)

Seems only slightly contradictory. I mean, if one of your pages in userspace is getting hit, then that's a reason to protect. Just because "it says I can" doesn't seem like a good enough reason. -Royalguard11(Talk·Review Me!) 03:39, 8 March 2007 (UTC)

User pages can be sprotected when required by any user when the page is being defaced. Permanent semiprotection goes against our wiki spirit. Even George W. Bush is unprotected from time to time. -- ReyBrujo 04:05, 8 March 2007 (UTC)

Though this may be true, this is not what the current or the past[1] semi-protection policies say. Should this policy line be changed to reflect, like the other two lines describing indefinite protection, that this only applies to userpages which are "subject to vandalism"? -- zzuuzz^(talk) 10:56, 8 March 2007 (UTC)

Disregarding the "it's the wiki way" non-argument, can anyone show how prohibiting semi-protection of userpages indefinitely/when it's not the target of vandalism actually improves the encyclopedia? Even better, does anyone have evidence to say that leaving userpages open to anons and new users generally leads to improvements in those pages? – Steel 11:38, 8 March 2007 (UTC)

I don't think that's really the point. WP:SEMI also says about sprotection that it's not to prohibit anonymous editing in general. That's all this seems to be. WP:USERPAGE says (about protection) that protected pages in user space should be unprotected as soon as practical. We've got contradictory things all around. And it just goes against the spirit of Wikipedia, the anyone can edit part. Now, I wouldn't be against move protection of userpages (I move protect mine and talk) because they might not ever be a reason to move it. It's just the editing part. -Royalguard11(Talk·Review Me!) 02:09, 9 March 2007 (UTC)

This "it's the wiki way" argument is highly unconvincing. We block/protect hundreds of users/pages every day, which clearly prevents people editing and is "against the wiki way". If we've got contradicting policies, then that's something that obviously needs sorting out. So, I reiterate my questions: Does having indefinitely protected userpages harm the encyclopedia in some way? Does anyone have evidence to refute the claim that 99% of anon edits to userpages are vandalism? – Steel 02:26, 9 March 2007 (UTC)

Again, your ignoring everything else and just casting all annons as vandals. Do you have anything that says we should disallow it besides "annons are vandals"? That "wiki way" is the way it has been and probably how it always will be. Why should we preemptively protect random userpages? -Royalguard11(Talk·Review Me!) 02:42, 9 March 2007 (UTC)

I've just said, we go against the "wiki way" all the time, and a few extra protected userpages isn't going to make this place significantly less a wiki. Also, I have not once said we should pre-emptively protect 'random' userpages, nor have I said that all anons are vandals. Either you're misunderstanding me, in which case you should re-read my previous comments, or you attempting to construct a strawman, in which case you should stop. Please answer my questions, the main one being how does having indefinitely protected userpages harm the encyclopedia? – Steel 02:49, 9 March 2007 (UTC)

It does not hurt the encyclopedia. -Royalguard11(Talk·Review Me!) 23:14, 9 March 2007 (UTC)

So there's no real problem then is there? Glad we've settled that. – Steel 23:24, 9 March 2007 (UTC)

I think in this case there needs to be a "why" reason rather than a "why not". -Royalguard11(Talk·Review Me!) 00:02, 10 March 2007 (UTC)

This wiki has no firm rules. As such, users can do as they see fit unless it's explicitely forbidden by policy, not the other way round (i.e. users can't do anything unless explicitely allowed by policy). So, in actual fact, this is a question of "why should we forbid it?" (the question I'm proposing to you), not "why should we allow it?" (the question you're proposing to me). – Steel 00:09, 10 March 2007 (UTC)

(deindenting) I've already given reasons above as to why I don't think indefinate semiprotection of userpages on demand is a good idea (my first and third responces). Among others, it contidicts other policies and guidelines. -Royalguard11(Talk·Review Me!) 00:20, 10 March 2007 (UTC)

That argument doesn't work. You're saying, essentially, "this policy must change because it contradicts the userpage policy". I could go over to WP:USER right now and say "this policy needs to change because it contradicts the protection policy". – Steel 00:27, 10 March 2007 (UTC)

Right now, we need to change one of them. I would prefer changing this one (especially since the "not to prohibit anonymous editing in general" will never get changed on this one). There is no justification to indefinitely protect userpages other than to prohibit annon editing in general. -Royalguard11(Talk·Review Me!) 00:48, 10 March 2007 (UTC)

Firstly, what is your definition of "prohibiting anon editing in general"? Secondly, while users don't 'own' their userpages, we let them do what they like with them unless they start adding offensive content or fair use images or whatever. WP:OWN is much, much more relaxed on userpages, the WP:3RR doesn't even apply. None of the points you've made hold any water. – Steel 00:56, 10 March 2007 (UTC)

• SPP for Userspace should be used to stop vandalism, but should not be indefinite, I've come across several of these pages lately (which were also NOT in the protected pages category for review) and set expirys on them (usually 2 fortnights). — xaosflux ^Talk 16:16, 10 March 2007 (UTC)

  To that end I'd support moving "User pages when requested" form the indefinite section to the temporary section (I must have missed the discussion where they got to be indefinite in the first place and don't have the gumtion to go researching policy difs right now). — xaosflux ^Talk 16:19, 10 March 2007 (UTC)

  (I recall adding wording to that effect in December. Diff: [2])
  The question of why they should only be temporary remains unanswered. – Steel 16:39, 10 March 2007 (UTC)

  I'd say the reverse should be looked at, why must they be indef protected? Why should policy exist to just arbitraily protect anything? — xaosflux ^Talk 16:47, 10 March 2007 (UTC)

  I direct you to this post above to avoid repeating myself. Perhaps this is a wiki-philosophical difference between us. – Steel 17:02, 10 March 2007 (UTC)

On a side note, a short while ago a nameless admin went through WP:PP/U and unprotected a number of userpages. For several days afterwards his talk page was flooded with complaints from users. I think we need to pay attention to the practicalities of this, in that allowing indef-protected userpages will cause less frustration and disruption (for want of better words). – Steel 17:08, 10 March 2007 (UTC)

I'm with Xaosflux on this one. Why do we have to fight here? What we've asking is for you to justify the indefinate protection of userpages. We've told you why not and you've dismissed us every time. Your turn. Tell us a why reason now. Defend the current policy without bringing up wiki-philosophy. Ball's in your court. -Royalguard11(Talk·Review Me!) 18:16, 10 March 2007 (UTC)

Because it doesn't hurt anything and there's no compelling reason not to if the user wishes it. That is the justification. Users can revert as many times as they like on their userpages, if they want to fill it full of crappy userboxes they can fill it full of crappy userboxes, if they want to post their life story they can post their life story, if they want it deleted they can have it deleted. Allowing them to have it protected if they want it protected isn't that outrageous a suggestion. – Steel 13:53, 11 March 2007 (UTC)

Well, it's still within my rights to refuse to do them then. -Royalguard11(Talk·Review Me!) 18:37, 11 March 2007 (UTC)

Of course. – Steel 01:22, 12 March 2007 (UTC)

• I agree with Steel. Oh, and of course Royalguard is correct that admins aren't obliged to, well, oblige. >Radiant< 12:10, 13 March 2007 (UTC)

• Now that Special:Protectedpages is working having >4200 pages is making it's usefulnes well, less useful. I've filed a bug report to add a namespace selector, but it still shows that we have thousands of uneditable pages without expirations, and filling this with userpages just because isn't helping matters. While of course no admin is obliged to protect one of these pages, having it in the policy prevents any other admin from removing it without wheeling. — xaosflux ^Talk 02:19, 22 March 2007 (UTC)

• This brings us right back to the previously discussed point of why anyone would need to remove these protections. Once the per namespace search is implimented this will become a non-issue. – Steel 13:48, 22 March 2007 (UTC)

• That said, and while IPs can easily contribute to main-article space I can't see many reason why IPs would need to edit userpages (apart from vandalism). If they want to be part of the community register. Agathoclea 10:11, 26 March 2007 (UTC)

If that is the goal, it could be achieved without the need for coutless page protections, we just update it site-wide... — xaosflux ^Talk 11:51, 26 March 2007 (UTC)

I agree, but then there is the thin edge of the wedge argument. Anyway I found this very enlighening. Agathoclea 18:42, 26 March 2007 (UTC)

I see good edits and bad edits, even anons reverting vandalism in there. We've seen that any determined vandal will have no problem registering an account by now. — xaosflux ^Talk 01:01, 27 March 2007 (UTC)

I removed the clause from the page. Hopefully we'll get some constructive feedback if anyone objects to me removing it. --Deskana (ya rly) 00:19, 31 March 2007 (UTC)

24 hours and no contest? --Deskana (ya rly) 23:27, 31 March 2007 (UTC)

Alright, 23. I'm at BST which is obviously UTC + 1. Duhh. --Deskana (ya rly) 23:28, 31 March 2007 (UTC)

I will when I'm back off wikibreak and have the time and motivation to discuss further. Be patient :) – Steel 15:50, 1 April 2007 (UTC)

• I do object to the removal. It really is no big deal if users want their userpage (not their talk page) semi'ed. The protected page list shows a bunch of examples. >Radiant< 10:59, 2 April 2007 (UTC)

My main concern is that this contradicts the clause underneath it that states that sprotection shouldn't be used to prohibit anonymous editing in general, which I really do feel this does. --Deskana (ya rly) 15:24, 2 April 2007 (UTC)

• Yes. It is an exception in a specific case to a rule not to protect in general. >Radiant< 08:52, 3 April 2007 (UTC)

Just like userpages are the exception to lots of other rules: WP:ATT, WP:OWN/WP:3RR, WP:NPOV, etc. – Steel 13:00, 4 April 2007 (UTC)

Exceptions are always available, but why not make them on a case-by-case basis, rather than namespace: basis? — xaosflux ^Talk 12:11, 5 April 2007 (UTC)

Because it's the nature of the namespace (i.e. being people's personal pages) that allows for the exception. Again, WP:OWN, etc. – Steel 12:19, 6 April 2007 (UTC)

WP:USER trumps WP:OWN in userspace: As a tradition, Wikipedia offers wide latitude to users to manage their user space as they see fit. However, pages in user space still do belong to the community (emphases my own). So, they do not own their userpages, they just have more freedom with them. -Royalguard11(Talk·Review Me!) 20:18, 6 April 2007 (UTC)

Precisely. – Steel 22:55, 6 April 2007 (UTC)

More freedom doesn't mean "whatever" though. -Royalguard11(Talk·Review Me!) 00:45, 7 April 2007 (UTC)

Right. And we don't allow copyright violations, grossly offensive content and the like on userpages. I personally wouldn't put page protection on the same level as advocating paedophilia or breaking the law or whatever. – Steel 00:59, 7 April 2007 (UTC)

Indefinite Sprotection on Userpages (section break)

I still quite strongly feel that unconditional protection of userpages is contrary to the beliefs of the wiki way. Of course they should be protected in instances of extreme vandalism, but I feel that users are saying "I own this, hands off to new users since I don't trust you". That is contrary to the wiki way of letting anyone edit. --Deskana (ya rly) 00:50, 7 April 2007 (UTC)

Userpages are except from the 3RR; users are allowed to say "I own this, hands off to new users since I don't trust you". Also, as I mentioned above, given the number of pages we protect and users we block daily, having a few userpages protected here and there won't make this any less a wiki. Incidentally, Wikisource, a wiki, fully protects its featured texts. There is nothing in the concept of the wiki which says that all pages must be kept open unless the sky is threatening to fall. – Steel 00:59, 7 April 2007 (UTC)

Wikibooks also protects finished modules if I remember right, but someone who's a sysop there failed to get past RFA here for even suggesting that we semiprotect "finished" articles. Not even same language wiki's are the same in terms of policies and how the community works. -Royalguard11(Talk·Review Me!) 01:02, 7 April 2007 (UTC)

Right. So userpage protection doesn't go against any "wiki way". – Steel 01:05, 7 April 2007 (UTC)

It all depends on which wiki you're talking about. Here we don't lock "finished articles". So speaking from the POV of Wikipedia, the free encyclopedia it does go against the wiki way. If this were Wiki-books/source/news then it wouldn't. But it isn't. This is a different community. -Royalguard11(Talk·Review Me!) 01:21, 7 April 2007 (UTC)

What we're actually discussing is whether en.wikipedia.org's policy should allow userpage protection on request or not. An argument that appeals to some "wiki way" is a poor one. – Steel 01:28, 7 April 2007 (UTC)

Semi-protection to allow for vandalism recovery

Is it a good idea to semi-protect a heavily vandalized page — in this case LSD — for one day to give users the chance to recover the article from vandalism. The problem with that page is that it has received vandalism at a high pace during the last weeks interspersed by legit edits and partial reverts and there seem not be enough adept watchers to keep pace. Cacycle 13:24, 9 March 2007 (UTC)

If someone asked me to protect a page for that reason, I'd probably grant it, since I would argue that it clearly helps the encyclopedia. Whether it needs to be codified in policy is another question, however. – Steel 23:48, 9 March 2007 (UTC)

I'd protect for this reason, but the reason is simply vandalism, and if it was high-paced it may warrant longer then a day even. The vandalism reason in the current policy should suffice though. — xaosflux ^Talk 16:09, 1 April 2007 (UTC)

Semi-protection against heavy anonymous vandalism

Related to the previous question: Could longer semi-protection be a legit method to protect a page from heavy and continous vandalism that comes from anonymous users with changing IP addresses if there are not enough enough adept watchers who are able to properly restore the page. Cacycle 23:44, 9 March 2007 (UTC)

Um, yeah. Of course. – Steel 23:50, 9 March 2007 (UTC)

I'm not sure if it's enshrined in policy, but it's been de facto for a while now. -Royalguard11(Talk·Review Me!) 00:03, 10 March 2007 (UTC)

Oops, sorry, this case is already mentioned in the policy. Cacycle 02:29, 10 March 2007 (UTC)

Wikipedia:Semi-protection policy redirects

I'm about to fix all the double redirects to Wikipedia:Semi-protection policy. If, for some reason, these pages were to be split again, anyone can check my contrib history for the redirects that were changed. --- RockMFR 00:19, 12 March 2007 (UTC)

• Good work on the merge! >Radiant< 14:12, 12 March 2007 (UTC)

Using the less prominent protection template

I started a discussion at Template_talk:Protected2 about when to use that template. It puts a small padlock at the upper right corner, without explaining why the page is protected. I'm concerned about the lack ofprominence and explanation. (I understand that we use Template:Sprotect2 for long-term semiprotection of biographies of living persons, and there are good reasons for that, but I feel full protection should generally be explained.) If you have an opinion about guidelines for using the template, please express it at Template_talk:Protected2. Kla'quot 16:37, 14 March 2007 (UTC)

theres this article that i know is wrong but im a noob and its semi-protected so i cant do anything. should i request unprotection or wait till im more than four days old?

Advice

List of homeopaths is a salvaging of an old, VERY bad list which had been invaded by advertising. It's not well-monitored, but the semi-protection guidelines only suggest indefinate semi-protection for not well-monitored biographies. Would it be appropriate to semi-protect it, to keep off the vultures? Adam Cuerden ^talk 19:35, 14 March 2007 (UTC)

• Please make such requests on WP:RFPP. The short answer is "probably". >Radiant< 09:19, 15 March 2007 (UTC)

Template protection

Hello all. When a high-risk template is protected, should we be putting {{protected template}} at the top of the template's page, or is {{permprot}} on the talk page sufficient? I always thought it was, but I've just come across a spate of requests to add {{protected template}} to a bunch of templates while going through WP:EPP, and am discussing the best thing to do with the user who made the requests, User:Qxz. I can't find a guideline or even a rule of thumb about which is best ... personally, I think {{permprot}} on the talk page is fine, but then why would we have an {{protected template}} template? Neil (not Proto ►) 22:41, 15 March 2007 (UTC)

{{Protected template}} adds the template into a category or two, whereas {{Permprot}} doesn't. Other than that there isn't much difference. I don't really consider this a big deal; If someone makes an edit protected request, I'll grant it (as I did earlier with one from Qxz), but if I happen upon an untagged protected template I'd probably just leave it. I suppose {{Protected template}} would be preferable if you're a categorisation nut. – Steel 22:51, 15 March 2007 (UTC)

Just to clarify something that Steel359 may not be aware of, or may have overlooked: {{permprot}} goes on the talk page, whereas {{protected template}} goes on the template page. So it's not a case of choosing one or the other. I was under the impression that both were needed; up until today many protected templates had neither; since the talk pages can be edited I've gone round and added {{permprot}} to them all but I can't add {{protected template}} to the templates because they're protected – Qxz 23:53, 15 March 2007 (UTC)

Another thing, too – {{permprot}} is used on non-template pages, whereas {{protected template}} is template-specific – Qxz 00:06, 16 March 2007 (UTC)

I was aware permprot went on the talk and protected template went on the template itself, but didn't notice that permprot was used on non-template pages. – Steel 00:14, 16 March 2007 (UTC)

sprotect tagging but not protecting

I've noticed a few articles lately being tagged but not actually protected. Doing this is undoubtedly a disincentive to some ip vandals. But is it appropriate? Views? —Moondyne 00:03, 19 March 2007 (UTC)

Tagging pages as protected when they're not should be avoided, since it's misleading to everybody. I'm unconvinced it actually deters vandals, since the "edit this page" link still glares at them (as opposed to "view source" when the page is actually protected). – Steel 00:08, 19 March 2007 (UTC)

It only deters the legitimate editors for the reasons stated above. 95% of the time it is new editors who think they are actually applying protection in good faith. They should be pointed to WP:PPOL and WP:RFPP. There is even a user talk page template: {{noprotection}}. The remainder of the time there are ownership issues. In most cases the editors welcome a pointer towards policy or process. There is simply never any good reason to keep a protected tag on an unprotected page. There is even a bot which removes them now. -- zzuuzz^(talk) 00:39, 19 March 2007 (UTC)

Misinformation?!

What if you protect a page that has vandalism? And where do you go to report such behaviour?--Migospia 23:41, 24 March 2007 (UTC)

You can report vandalism in protected pages at Wikipedia:Administrator intervention against vandalism. --bainer (talk) 03:55, 25 March 2007 (UTC)

put {{editprotected}} on it's talk page. — xaosflux ^Talk 03:57, 25 March 2007 (UTC)

That's also a good option, although AIV is often faster, which is useful in some cases. --bainer (talk) 04:30, 25 March 2007 (UTC)

Color-code locks

Why not try color-coding locks?

semi-protection
full protection
move protection
cascade protection
— zero » 03:39, 25 March 2007 (UTC)

Those images look a bit childish, sort of like Comic Sans. However, you'll probably be interested in this VPR discussion (permanent link). Gracenotes^T § 01:58, 26 March 2007 (UTC)

Templates on semi-protected pages

Until recently the protection-confirmation page said that pages semi-protected for a finite period shouldn't be tageed with the {{sprotected}} template; that's now disappeared. What happened? I've seen a number of cases recently where a page has been sprotected, another editor has added the template, and no-one has bothered to remove it after the protection has expired. --Mel Etitis (Talk) 12:11, 25 March 2007 (UTC)

Centrx (talk · contribs) would be the person to speak to about this [3]. – Steel 21:33, 25 March 2007 (UTC)

Thanks. --Mel Etitis (Talk) 09:42, 26 March 2007 (UTC)

Semi-protection of userpages

Why can people get their userpages sprotected when there is minimal/no vandalism to them? It seems to be in contradiction to the bit that says sprotection shouldn't be used "to prohibit anonymous editing in general". If lots of vandalism is present on a userpage then I see no reason why it can't be sprotected, but we seem to be endorsing pre-emptive sprotection here. I'd strongly support the removal of that clause from the policy. --Deskana (talk) 17:25, 25 March 2007 (UTC)

Well the users have always been able to mostly freely edit their userspace, and even get it deleted, so I don't see any reason what we should discourage them from protecting it as well. Besides, each user may have his own reasons for the protection; perhaps one user would like to leave Wikipedia and doesn't want anyone screwing with his userspace while he's gone?, or maybe he simply wants to have his userpage deleted permanently? We should think a bit differently here. Michaelas10^{Respect my authoritah} 18:44, 25 March 2007 (UTC)

I think you're missing the point of what I was saying, a bit. The reasons you gave are probably good reasons to protect the pages. I just don't think pages should be protected "just because". If they want to leave and don't want it modified, that's a reason. "Because it's my userpage" seems to be a bit protective, like "I don't want anonymous users editing it, but other users can". Seems a bit exclusive, and the wiki is supposed to be about everyone being equal, including anons. Of course, sometimes we need to take certain measures to prevent anons editing, but saying "I don't trust anons to do it" seems unfair. --Deskana (talk) 19:30, 25 March 2007 (UTC)

This has been discussed at (reasonable) length above. See Wikipedia talk:Protection policy#Indefinate Sprotection on Userpages. – Steel 21:30, 25 March 2007 (UTC)

I just want to respond to Michaelas10 here. Yes we delete userpages on demand. But if someone wants to leave wikipedia and wants their userpage protected for a while then that is totally different than Joe Editor going "hey, don't let people touch my page". Same thing with permanent deletion. -Royalguard11(Talk·Review Me!) 22:15, 2 April 2007 (UTC)

What does "endorsement" mean?

"Protection is not an endorsement of the current version." Everything I've read and heard defending this claim seems to make the assumption that those who disagree with it are engaged in a petty edit war over a potentially protected page. Well, I wouldn't say I necessarily disagree with the idea of the phrase, but I find it rather vague on one particualr count: Does the concept of "endorsement" include "believed to be factual based on cited sources?" To repeat something I asked earlier on this page, would a protected page ever have an {{unreferenced}} tag, as a temporary measure when no sources would be easily found, and the admins are too busy to look into the question? $\sim$ Lenoxus " * " 16:56, 27 March 2007 (UTC)

It basically is a protection for ourselves (ie, admins). It means that if we have to lock a page with full protection, especially because of an edit war, then we want to make sure that people know that we as admins, and possibly the community, may not endorse the current version. It probably will not contain vandalism or blatantly wrong facts, but may (or probably will in an edit war) contain disputed material. It's a warning that could be taken as "this article is in dispute right now, and this particular version might not be our best work. Check back later for better edited work". -Royalguard11(Talk·Review Me!) 02:35, 28 March 2007 (UTC)

• Indeed. Additionally, if user:A and user:B are in dispute and edit warring over an article, and user:Admin steps in and protects the page, he protects the page in whatever version he happens to find it in. If this is user:A's version, that does not mean that user:A is in the right with respect to the dispute. That also means that user:B does not get to ask to please have the page protected in the other version. Oh and yes, protected pages can have any kind of tags on them. >Radiant< 08:05, 28 March 2007 (UTC)

Thanks for clearing things up a bit there. So now I'm wondering something slightly different -- has anyone ever floated the idea of having this be made clear on the template itself, given that many templates go into extra detail to explain equivalent things? $\sim$ Lenoxus " * " 10:08, 28 March 2007 (UTC)

• {{protected}} says so. Do you think that is clear enuogh? >Radiant< 10:33, 28 March 2007 (UTC)

Well, specicifically, I mean some phrase equivalent to "this is not an endorsement of the page's current version, nor a guarantee of neutrality, validity, or excellence." Even after seeing the template I used to naturally assume so, until I had read what I've since read (which makes sense now.) $\sim$ Lenoxus " * " 10:42, 28 March 2007 (UTC)

• Yes,b ut unprotected pages aren't guaranteed to be neutral/valid/excellent either. >Radiant< 11:07, 28 March 2007 (UTC)

Many people view them with additional suspicion, though, knowing that they are user-editable. The standard argument that might go in many people's heads without their fully realizing it is something like this:

1. Page A is untrustworthy because it can be edited by anyone.

#Page B cannot, in its current form, be edited by anyone; therefore, it is trustworthy.

Without some explanation along the lines I put, a lot of people are going to scratch their heads and say, "You mean, you protected it and it wasn't even 100% satisfactory?" -- especially those newbies and outsiders who, thanks to their conventional understanding of "encyclopedia," are Immediatists without knowing it. Is there a way I could make this clearer? $\sim$ Lenoxus " * " 17:49, 28 March 2007 (UTC)

WHOA HOLD UP PLEASE DON'T RESPOND UNTIL I SORT THINGS OUT $\sim$ Lenoxus " * " 17:53, 28 March 2007 (UTC)

Uhhh... what? That's confusing. --Deskana (talk) 17:59, 28 March 2007 (UTC)

OK, cooling down. Wow. I honestly just noticed that Yes, Lenoxus, the text "protection is not an endorsement of the current version" is on the template. Like you told me. And I just thought you didn't understand what I was talking about, or something... So... stupid... so I change my mind a bit, and now feel simply that the link should maybe be bolded to make it more apparent to idiots like me. But I don't feel too strongly about it. (My guess is that I was thinking all along of Template:Vprotect, which currently doesn't mention the endorsement thing. That's something I might eventually bring up, but I'm about to go on a moderate WikiBreak first.) Anyway, thanks for your responses and patience, Radiant. $\sim$ Lenoxus " * " 18:12, 28 March 2007 (UTC)

Protection templates?

Are we using the {{pp-semi-vandalism}} templates now? Because the {{sprotect}} templates are still up with no message. -- _Hdt83 ^Chat 01:30, 29 March 2007 (UTC)

{{sprotected}} displays a message. --Deskana (talk) 01:31, 29 March 2007 (UTC)

I was asking if we are now adopting {{pp-semi-vandalism}} to replace the older {{sprotect}} templates? -- _Hdt83 ^Chat 01:33, 29 March 2007 (UTC)

Whoops, sorry, I misunderstood you. I have no idea :-p --Deskana (talk) 01:40, 29 March 2007 (UTC)

Anybody else have any idea? -- _Hdt83 ^Chat 02:35, 29 March 2007 (UTC)

• If so I'm sure we'll redirect the old name there as well. >Radiant< 10:44, 29 March 2007 (UTC)

• Per WP:KISS I oppose the new templates as being too estoteric. With that being said if the old template will still work, with the same results then redirects are fine with me. — xaosflux ^Talk 16:10, 1 April 2007 (UTC)

How Long?

On pages that are semi-protected, how long must a user have been registered for before they can edit such pages? — Preceding unsigned comment added by [[User:{{{1}}}|{{{1}}}]] ([[User talk:{{{1}}}#top|talk]] • [[Special:Contributions/{{{1}}}|contribs]])

• Four days. Says so at the top of the policy. >Radiant< 12:27, 5 April 2007 (UTC)

Preemptive Semi-Protection

I am suggesting that the disuse of preemptive semi-protection, as it is mandated in §2, to be removed from the policy. I believe that some articles(i.e.Recently Deceased Persons, Controversial events) or articles with topics that would be recently brought to sudden public interest, could benefit from use of preemptive semi-protection. Articles such as these, as any Wikipædian knows, are prone to vandalism, and at the same time, are bound to be suddenly viewed by large volumes of people. Of course, due to their nature, these articles will need to be edited, but the editing can be done by legitimate users. Obviously other policies and guidelines will have to govern this, but those are to be made.--Whytecypress 21:57, 7 April 2007 (UTC)

Many editors would disagree with being called illegitimate, especially when they add much of the content. There is no reason to exclude unregistered editors if there has been no vandalism. If they are excluded you will never know what improvements might have been made. It's only when the trade-off between vandalism and good edits becomes not worth it that protection should be used. This is rarely known in advance. -- zzuuzz^(talk) 22:10, 7 April 2007 (UTC)

Semi-protection is not used to prohibit annon editing (and we've all agreed on that in terms of the mainspace). Period. That is one of the foundation issues: The Wikimedia projects as a community have certain foundation issues that are essentially beyond debate...Ability of anyone to edit articles without registering. As it says, it's not debatable. Of course protection policy allows us to temporarily protect pages that are receiving heavy vandalism, but we can't just do it to exclude annons in general. -Royalguard11(Talk·Review Me!) 17:55, 8 April 2007 (UTC)

I think the issue is easily resolved by not doing it preemptively but reactively. If such articles are indeed prone to vandalism, we don't have to wait for several days, we can just drop the issue on WP:RFPP. >Radiant< 09:21, 10 April 2007 (UTC)

"Protection is not an endorsement of the current version"—a delusion? a lie? or both?

Are the people who make the claim that "protection is not an endorsement of the current version" just totally oblivious to the world around them? Or are they deliberately trying to deceive us?

This will, of course, be something invoked in the case of content disputes. It will be invoked on the basis of someone's claim that "edit-warring" exists (usually without even any verification of that being the case by the protecting administrator).

As the project page says:

"Instead, editors should attempt to resolve the dispute on the related talk page."

Another rule provides:

"However, unless consensus has been reached, pages should not be unprotected soon after protection without prior consultation with the admin who first protected the page."

In other words, failure to gain consensus means that the protected page cannot be changed. The protected version is in fact "endorsed" as the official version.

But according to another rule stated in the policy here, even consensus itself, as that term is used in Wikipedia jargon, is not sufficient:

"Admins should not edit pages that are protected due to a content dispute, unless all parties agree to the change, or the change is unrelated to the dispute."

This, by its own terms, requires something much stronger than consensus. It in fact requires unanimous consent to make changes once the page is protected. Nobody who is not an admin can make any changes; an admin can only do so with unanimous consent. Not an endorsement? Don't try to pull my leg.

However, the version which is protected has a significant effect on the ensuing discussion. Not an endorsement? What difference does that make, if it in fact shifts the burden of proof in the ensuing discussions. If consensus at the very least, or something much stronger than consensus (unanimous consent) as stated in the rules here, is needed to make a change once the pages is protected, then the choice of the version to be protected quite clearly and obviously has the same effect as an endorsement of that version, whether it is described as being an endorsement or not. Is everyone involved in making this choice just deluded? Or is someone deliberately trying to pull the wool over our eyes?

There will always, of course, be unscrupulous editors like Husond, a sysop well aware of this fictious rule, who will take advantage of it to game the system. To make an edit while at the very same time request its protection as part and parcel of his gaming of the system to shift the burden of proof in any subsequent discussions.

As a first remedy, the rule quoted above should be changed to specify that consensus as defined in our rules ("Consensus does not mean that everyone agrees with the outcome...") is the requirement for administrators to make a change in protected pages, not unanimous consent. It should also be specified that changes in accordance with various procedures such as Wikipedia:Requested moves will still be implemented as usual on protected pages (perhaps by specifying that such results are grounds for removing the protection).

Second, when a clear start of an edit-war can easily be determined, without any significant subsequent editing related to the edit warring, then the pre-edit war version should be the protected version.

I'd suggest one further simple change to help alleviate the problem of gaming the system:

• The page shall be protected in the last version (excluding pure vandalism) by an editor other than the editor requesting page protection, and the page shall not be protected under a name which results from the last move being made by the person requesting page protection.

If the claim that "protection is not an endorsement of the current version" were true and believable, then this might not be necessary. Editors such as Husond would see no advantage in trying to game the system. But he knows better—knows that he can gain an advantage from getting his version protected—and now the only real question is whether or not the rest of us are gullible enough to continue to believe that he does not. Gene Nygaard 19:42, 11 April 2007 (UTC)

I'm going to assume that this isn't just trolling and try and make a civilised comment.

• In most cases (note "most", not "all") page protection isn't an endorsement of the current version, and this is true with Josef Vašíček. Alison protected the version which was 'live' when she came across it while reviewing WP:RFPP requests. There is no evidence I can see that she protected that version because she approved of it in some way. So no, this wasn't an endorsement of the current version.
• I would agree that "unless all parties agree to the change" ought to be changed to something along the lines of "unless there's consensus for the change".
• The version protected does, of course, influence the resulting talk page discussion. This seems trivially true (people who support the current version have less an incentive to discuss than those who oppose it). It doesn't, however, influence discussion to the extent where trying to argue against the current version is futile, which is what you make it out to be. The page has to be protected on some version, sometimes it works in your favour, other times it doesn't.
• There is a potential problem with people reverting an article and then immediately requesting protection; it is, in effect, gaming the system. I have yet to hear a good solution to this. Your suggestion that we protect the other version to the version supported by the editor requesting protection is terrible. It will lead to no protection requests, and subsequently no admin intervention against edit wars. That is not productive. In practice, protection requests take time to be reviewed, so this isn't a too much of a problem.
• I'm not convinced by the "protect the version prior to the edit war" suggestion. This will encourage people to whinge and wikilawyer over which version is the 'before the edit war' version. A much better use of time and energy would be to discuss the relative merits of the versions and resolve the dispute.
• "I don't like Husond" and "The Wrong Version of Josef Vašíček was protected" are not a compelling arguments.

– Steel 22:01, 11 April 2007 (UTC)

I'm going to largely end up repeating what Steel said above. I am the admin who protected the disputed page, as it happens and as with all RFPP enttries, I just review each request on its apparent merit. In this case, there is a very obvious revert-war going on and the correct response in this case was full protection with move protection. Needless to say I was not endorsing Husond's edit. I agree somewhat, that there's scope here for "gaming the system", as you put it, but note that 45 minutes had elapsed since Husond's revert and my protection of the page. The purpose behind protection is not endorsement of any particular version, as you know, but to stop the pointless waste of time and energy that is a revert war, rationale being that the warring editors focus on the talk page and resolve their differences. Nice in theory.

But yes. There is no "right version" to protect, and I see no way forward on that one. Best answer is compromise and dialog, and as quickly as possible. - Alison^☺ 22:38, 11 April 2007 (UTC)

"but note that 45 minutes had elapsed since Husond's revert and my protection of the page." What's your point? That I should have been putting that time to use to gamble on timing another revert, trying to guess whether you would protect the page in 23 minutes or 47 minutes or 72 minutes and trying to get my version in there just before that happened? That I should have been trying to push Husond to violate the three-revert rule? Given the stance you have taken in this discussion, there is one thing I know for certain: I damn sure better not hear any complaints about "violating the spirit" of the three-revert rule or anything along those lines in the future. You have just told me that this is the only option available when a request for page protection is pending. Gene Nygaard 01:36, 12 April 2007 (UTC)

Gene, if you'll stop for a minute and assume a little good faith on my part, please? My point is neither of the two suggestions you made. Rather, it is this; 45 minutes had elapsed between Husond reverting and applying for prot, and my applying protection. I don't believe it was a ploy on his part to expedite both of these as, quite simple, anything could have happened in the interim. Furthermore, I really like you to clarify exactly what "stance [I] have taken in this discussion". Please be careful about putting words into my mouth when you suggest I "have just told you". Try to remain civil, please. I more than aware about some of the discussions going on elsewhere right now regarding your behaviour and, as this is our first encounter, it's a pity it had to be so antagonistic. - Alison^☺ 06:15, 12 April 2007 (UTC)

Once again, no manners. I've reported your constant incivility to WP:ANI (here).--Húsönd 01:57, 12 April 2007 (UTC)

So what exactly are you complaining about here? Gene Nygaard 02:36, 12 April 2007 (UTC)

Sounds like someone's holding a grudge. Page protection is not an endorsement of the current version, you're welcome to think otherwise but you're essentially saying that a tree isn't a tree, but is instead the Bolivian navy on maneuvers in the South Pacific. Call it what you want, it doesn't change the fact that its true. --Deskana (fry that thing!) 03:28, 12 April 2007 (UTC)

Sure, in some sense it probably is true. But it is only trivially true as a nonsense blandishment, something really irrelevant to the issue at hand. Its truth depends on the meaning assigned to the word "endorsement".

But endorsements or not have little meaning, when what the "protected version" is such an overwhelming advantage that even if it were an endorsement, it would have no effect on the outcome. What the "protected version" gives you is the default version; the one that cannot be changed except by unanimous consent. It doesn't matter one whit whether or not the protecting sysop is endorsing it, given that state of affairs. That statement is a trivial observation offered as pabulum to placate the masses, to pull the wool over our eyes by bringing up something that really doesn't have any effect whatsoever.

If it really were relevant and effective, in a broader meaningful sense, then nobody would would be out there trying to game the system, because no advantage would be gained by trying to do so. But that quite obviously is not true, and people are gaming the system to gain the totally non-random advantage of the protected versions, by getting sympathetic sysops, or just unwitting ones, to act at the times most to their advantage to gain a leg up on the dispute. Gene Nygaard 05:55, 12 April 2007 (UTC)

So which am I then, Gene; sympathetic or unwitting? I'm not impressed with either of those appellations - Alison^☺ 07:48, 12 April 2007 (UTC)

• If we state that protection is not an endorsement, that gives both sides the incentive to discuss on the talk page knowing that a compromise has to be reached, and knowing that the page is not protected forever. The "protection" template tells people that there's a problem with the page. If we were to change this and say that protection is an endorsement, that would give one group the incentive to not do anything since they've already won, and it would encourage admins to take sides and pick the version they like best to protect in. That is undesirable, and that is why even though protection means a de facto top version, it is not de iure considered better. At any rate these are short-term concerns only, and we're not working on a deadline here. >Radiant< 08:31, 12 April 2007 (UTC)

Gene, on the face of it the concern you raise does seem to be valid, but it seems to me to be based on a misunderstanding (which may well be caused by deficiencies in the wording). The purpose of protection in the case of edit warring is to compel the parties in a content dispute to engage in discussion, and, importantly, to seek the views of other users. The objective is to achieve a consensus (not unanimity) as to which of the competing versions is preferable, at which point protection may be removed.

The particular sentence you have identified is specifically addressed to admins, who of course have the technical ability to edit protected articles. It cautions them not to edit the article while it is protected unless there is complete agreement among the parties (who at that time should be busy discussing on the talk page) or unless the content is not related to the dispute. It has nothing to do with the objective of the people discussing the content dispute, which is to achieve a regular, garden variety consensus as to which version should be put in place once the article is unprotected.

Of course, this is the approach for protection in response to edit warring. If the revision in place at the time of protection contains, for example, copyvio content, then naturally that can be removed.

Does this explanation make sense? If need be, then we can discuss changes to the wording which may be necessary to make it clear that the sentence you identify is a cautionary note addressed at admins, and is irrelevant for the purposes of the editors discussing the content issue. --bainer (talk) 09:40, 12 April 2007 (UTC)

Indefinite semi-protection?

Since when has indefinite semi-protection been allowed? I thought semi-protection was supposed to be temporary. --ALL IN 02:49, 13 April 2007 (UTC)

Maybe, but unprotected George W. Bush is nothing short of foolish. And Jimbo himself said that indefinite semi-protection could be used on biographies subject to drive-by nonsense, and he's a big promoter of the "anyone can edit" philosophy. You're right about the userpages though, they shouldn't be indefintely protected, but very few people seem to agree. --Deskana (fry that thing!) 03:20, 13 April 2007 (UTC)

I just had added Penis as another example of an indef semi-protected article, but rememberd that it has been briefly unprotected a few times. It seems that articles like that that are blatant vandal targets should be. Why don't we have a list of permanently protected pages, so this can be debated? The way, the truth, and the light 11:52, 26 April 2007 (UTC)

'Indefinitely protected' isn't a formal classification for an article (like say, featured is). If a page's protection log is a mile long - full of protections, unprotections and reprotections - people just don't bother unprotecting it and it becomes a de facto 'indefinitely protected article'. To be honest I think we can do away with that term entirely. – Steel 17:14, 26 April 2007 (UTC)

Yes, I was suggesting that maybe it should be. It certainly wouldn't hurt to avoid the disruption cause by unprotecting problem articles, while articles that usually aren't would not have to be protected any longer than they need to be. I'm confused why you would 'do away with' the term, indefinitely protected pages exist whether that's formal policy or not. The way, the truth, and the light 18:26, 26 April 2007 (UTC)

See above. The term implies that 'indefinitely protected' is a class of articles like featured articles or good articles or whatever, when in reality it's simply a protection that no-one feels the need to lift. And this system works well, I don't really see the need for a bureaucratic approvals process to designate articles 'indefinitely protected class'; indeed, this is a textbook example of instruction creep. – Steel 19:16, 26 April 2007 (UTC)

Talk page protection

Currently Talk:Virginia Tech shootings is sprotected. I find that that would exclude anyone coming to Wikipedia because of the current news event from participating and providing information. If the talk page is sprotected, then shouldn't another page, a Talk talk or something be provided for new editors? They might provided worthwhile information, and it will make sure that Wikipedia is a place where anyone can contribute. Zyxwvutsrqp 23:14, 16 April 2007 (UTC)

The talk page was protected because people were posting libel on it. I don't think there is an easy solution to this, if a different page is provided for new editors people would just post libel there instead. – Steel 23:21, 16 April 2007 (UTC)

A solution would be useful, since as it stands now, it appears as though we are actively discouraging participation from people drawn by current events. Zyxwvutsrqp 23:34, 16 April 2007 (UTC)

I'm all ears if you have a solution. – Steel 23:35, 16 April 2007 (UTC)

How about a policy where the talk page cannot be protected? People come to Wikipedia to view the article, as the article is where the actual information is. Eliminating the possiblity of discourse on the topic by protecting the talk page could have such a chilling effect that the credibility of Wikipedia could be at stake. The talk page is *by definition* not an assertion of truth. Libel, BY DEFINITION, requires that the matter be asserted as truth. No reasonable person would believe that things being discussed in a talk page are assertions of truth. I don't necessarily disagree with protecting the article itself, but the talk page should never be protected. Rooot 20:18, 17 April 2007 (UTC)

This is moot. It's unprotected now anyway. – Steel 20:21, 17 April 2007 (UTC)

This is not moot because the possibility of this happening again still exists. The issue is greater than one specific incident. Rooot 20:25, 17 April 2007 (UTC)

Talk pages will generally be protected or sprotected in serious situations (like the talk page "rumours" issues). We can't outlaw it because we might need it just in case. -Royalguard11(Talk·Review Me!) 21:53, 18 April 2007 (UTC)

so called armenian genocide

it is not our duty to make history, but to write history. to write to history and to decide what happened really, historian make researchs and the result must be depended on the real documents not the fake ones secondly citations and documents must not be distorted. as an alternative source of knowledge, wikipedia can share any knowledge that is a fact. however, so called armenian genocide claim has many contradictions. and it has not been proven yet. moreover, the fakeness of the documents that were seen as the proofs of the genocide and the distortion of the documents and the knowledge has been shown on this page. ( http://www.ttk.org.tr/index.php?Page=Sayfa&No=90 ) if you have any difficulties understanding the content of the page, i will be pleased to help. to be fair and to help justice to be served wikipedia must share this information on the web. otherwise, it would be shameful for you. with my best regards

umut azak umutazak@gmail.com —The preceding unsigned comment was added by 139.179.219.3 (talk) 17:16, 17 April 2007 (UTC).

Lock color

I know this is strange but why did they change the lock color from gold to silver? Personally, I think gold is more appealing and easier to see. —The preceding unsigned comment was added by 68.81.252.24 (talk) 21:48, 17 April 2007 (UTC).

New Protected pages tool

Special:Protectedpages has been updated, and now include many options for sorting and filtering the list, admins may be able to use this to help resolved improper or forgotten protections now. — xaosflux ^Talk 02:20, 20 April 2007 (UTC)

Finally! A real replacement for WP:PP. Now we can get somewhere with old articles (since it goes by oldest too it looks like). -Royalguard11(Talk·Review Me!) 02:23, 20 April 2007 (UTC)

I just got 30-40 really old pages unlocked. Also helpful to go and set expirys on pages that are currently set for indef. — xaosflux ^Talk 02:55, 20 April 2007 (UTC)

I have some protection script[4] to help as well.Voice-of-All 19:18, 21 April 2007 (UTC)

Romeo and Juliet

Famous play subject to disfiguring vandalism daily by middle school kids. Please semi-protect.

Sprotect 2 icon too subtle

The little icon on the right corner is too subtle and it is confusing new users or anons. Many anons who don't know why it is protected may ask "Where did that edit button go" since the "edit button" will be replaced by "view source". I think that there needs to be at least some text that at least tells the user that this page is protected and to link to a page that shows the reason why. Maybe a small note beside the icon saying "Page protected see (link to reason) for details" or something. -- _Hdt83 ^Chat 22:56, 20 April 2007 (UTC)

If I recall correctly, the view source page has wording to that effect. – Steel 17:08, 26 April 2007 (UTC)

Of course, many people won't know what the "view source" button means... Perhaps the words should be changed to "edit this page" but still link to the same page? -- _Hdt83 ^Chat 05:03, 4 May 2007 (UTC)

Protection of a policy page in the "wrong version" is an endorsement

As I write, Wikipedia:No personal attacks is locked in a version which includes a contested change. Therefore, the contested version is now policy, in spite of the fact that the change in question has been disputed for over two weeks with no resolution in sight. The disclaimer simply doesn't work in this case.

Policy pages which are locked for edit warring need to be locked as they were before the edit war began. Mangoe 14:50, 27 April 2007 (UTC)

Agreed; unless protected policy pages lose their status while locked, including something disputed in a policy makes little sense. -Amarkov moo! 14:53, 27 April 2007 (UTC)

This may be a bit too idealistic to implement properly. I can see someone reverting then protecting, then another admin reverting the reversion because they see that as indicating a preference. --Deskana (fry that thing!) 15:42, 27 April 2007 (UTC)

No comment on the first half, but the 'locked on the before the edit war' version is suggested here periodically and would be a nightmare to impliment properly, not least because it's not always clear which version is the 'before the edit war' version. A comment I made a few sections up seems relevant here as well: I'm not convinced by the "protect the version prior to the edit war" suggestion. This will encourage people to whinge and wikilawyer over which version is the 'before the edit war' version. A much better use of time and energy would be to discuss the relative merits of the versions and resolve the dispute. (Just quoting myself, not accusing anyone in the WP:NPA war of anything)
Perhaps part of the protection policy should be changed with regards to protected policies, it's not the worst suggestion anyone has ever made, but it'll need to be thought through. – Steel 15:52, 27 April 2007 (UTC)

That is a new dilemma. I agree with what Steel said though. It's best to discuss the changes on that talk page and get the dispute resolved than try to wikilawyer the right version. Maybe there needs to be a specific protection tag for policies indicating that a certain part of the policy is under dispute (see talk) or something like that. Comments? -Royalguard11(Talk·Review Me!) 02:50, 30 April 2007 (UTC)

I would support that. Actually, I expect it's possible to have the {{pp-dispute}} template say something different if it's placed on a WP page, so it's probably not even necessary to create a separate template. – Steel 02:54, 30 April 2007 (UTC)

I assume there's a way, but I have no idea (I'm not the best person when it comes to way complicated template syntax). -Royalguard11(Talk·Review Me!) 03:26, 30 April 2007 (UTC)

I'll see if I can get it working, otherwise we can wheel in a template whiz. The wording still needs to be decided upon, at any rate. – Steel 15:53, 30 April 2007 (UTC) OK, after about 30 seconds of testing on the testwiki it was working. Easy, really. – Steel 15:57, 30 April 2007 (UTC)

• If it turns out that a policy page is protected in a version that obviously misrepresents policy, you should ask a neutral admin to fix that, using {{editprotected}}. In the cases where it's not obvious, it's probably not that big a deal to leave it in the "wrong" version for a few days. >Radiant< 09:49, 1 May 2007 (UTC)

Semiprotection in response to continual low-level vandalism?

When there's an article which has high visibility to people unfamiliar with Wikipedia - like an article on a cartoon fandom, for example - and lots of people are amazed by the ability to edit the article and it ends up with amateurish edits or vandalisms a few times a day, is this a suitable case for indefinite semiprotection? I wouldn't think so, because the policy specifically points out heavy vandalism, and a few vandalisms a day are easy enough to keep up with, though it really is a pain to keep having to edit them out. I'd like to see this situation mentioned in the policy, and for it to clearly state whether or not indefinite semiprotection is an acceptable solution. Right now I'm seeing a large number of articles with indefinite semiprotection in response to really light vandalism. - Brian Kendig 03:13, 4 May 2007 (UTC)

Yes, the concept of indefinite semi-protection is not really defined, and therefore there are no standards for it, other than 'consensus' of admins. I guess you would support my idea that there be an organized list of indefinite-protected articles. The way, the truth, and the light 04:13, 4 May 2007 (UTC)

In cases of light vandalism, just reverting and warning the vandals (read: warning is a very important step) is good enough. If it's the same people then they'll get tired of getting blocked (if they're normal). -Royalguard11(Talk·Review Me!) 04:06, 4 May 2007 (UTC)

That's how you deal with individual vandals. However, many articles are continually vandalized by different people, and that's when the question of semi-protection arises. The way, the truth, and the light 04:13, 4 May 2007 (UTC)

Gasp! Our pages are editable by every random joe that walks by! Every page receives vandalism. Random drive by has no solution, except revert, warn, block. Read m:Foundation Issues. -Royalguard11(Talk·Review Me!) 04:16, 4 May 2007 (UTC)

I know that. But clearly there's some point at which semi-protection is appropriate; that's already been decided. And a few articles are permanently protected, or nearly so. My suggestion, which the original poster seems to agree with, is that this be formalized. The way, the truth, and the light 04:21, 4 May 2007 (UTC)

• I think the page already says that. "Indefinite semi-protection may be used for ... articles subject to heavy and continued vandalism". >Radiant< 09:08, 4 May 2007 (UTC)

I'm talking about articles that are targets of moderate and continued vandalism, by a wide range of anonymous newbies. The article I'm particularly thinking of as an example is Virtual Magic Kingdom, where different kids keep wandering in and editing it to say "come find me in the game!" or "here's a list of all the events this week!" or deleting sections or slipping in four-letter words or doing any of the numerous things that newbies do that aren't appropriate for Wikipedia articles. If you'll look at the article's history, you'll see that the vast majority of edits are of this type or reverts of them; and since there are many, many more newbies than experienced editors looking at this article, there have been some obscene edits left up there for days, and some vandalism has gone unnoticed for weeks. I would really like to put this under indefinite semiprotection, but the vandalism can't be called "heavy". And if semiprotection isn't appropriate for this article, then it definitely isn't appropriate for articles I see under semiprotection because they've gotten a couple of vandalisms over a couple of days. I just want the policy to be more clear in this area. - Brian Kendig 11:27, 4 May 2007 (UTC)

I'd like to see the group come up with a bit clearer definition - and include it in the policy - of just what "persistent" vandalism consists of. What is persistent and moderate to one person may not be so to another. For instance, 1986 averages 3 to 6 anon IP vandalism acts a day, almost every day. I, personally, would consider this persistent vandalism, and since most of the vandalism is by IPs, sprotection would certainly help in this case. I've gone over the archived discussions here, and cannot find anywhere where we've tried to actually quantify the rather vague standard we have now. I may be all wet, but I think it's time to reduce this policy's vagueness. Therefore, as an attempt to generate discussion on actual thresholds, what would the community think about defining "persistent" vandalism as "an average of three vandalism edits by anon users per day for a period of two weeks or more"? Akradecki 04:20, 5 May 2007 (UTC)

I think that such a low number would result in semiprotection becoming commonplace here on Wikipedia, and I don't think that would be a good thing. I'd suggest a higher bar, something like "ten vandalism edits on most days over a month-long period." - Brian Kendig 16:53, 5 May 2007 (UTC)

It's lucky for everyone then that we have admins who have gone through RFA and are allowed to use their own good judgement to decide a)to protect or not and b)for how long. The fact that it isn't so set in stone is a good thing, because then we can be flexible. As for 1986, I have sprotected it for 2 weeks (the proper page to make request is WP:RFPP, admins don't just patrol around looking for pages to protect). Brian, your an admin, and I'm sure you can use some judgement in protecting pages and which ones need it (in my opinion, VMK does need a couple weeks of sprotection). I think that the policy is better when loosely defined rather than rules and tests (just like RFA is very loosely defined and crats must use their own judgement when determining consensus). -Royalguard11(Talk·Review Me!) 18:41, 5 May 2007 (UTC)

The problem with giving that article "a couple weeks of sprotection" is that this doesn't address the underlying problem - random newbies vandalizing the article for the fun of it - and that's going to pick right up again when the sprotection goes away. You're correct that the policy is good to be loosely defined, but I believe it's too loosely defined when there are no guidelines for how much vandalism deserves permanent sprotection. - Brian Kendig 20:07, 5 May 2007 (UTC)

What we clearly need here is some kind of Wikipedia:Protections for discussion where we discuss the relative merits of various protection durations for nominated articles. After seven days someone closes the discussion and impliments the community's decision. Obviously we'd need Wikipedia:Protection review if someone thinks an article should have been protected indefinitely and only got six weeks. Before all this we'd need to hold a long discussion here about what the various threshold levels are for vandalism, and how long each page gets protected. I suggest that an article about a famous painter from Italy should need 67.93% of it's recent history to be vandalism to be protected for a month. This threshold rises to 73.4% if the painter died between February 1901 and October 1967, but falls to 37.7% if it's a Tuesday. Sound good?
What's funny is that this probably isn't all that different to what would actually happen. – Steel 19:24, 5 May 2007 (UTC)

That's a really good idea, actually - having a procedure in place for deciding what articles deserve more-or-less permanent semiprotction. It would make the decision depend less on the opinion of a single editor. - Brian Kendig 20:07, 5 May 2007 (UTC)

You get a troutslap for taking that seriously. The current system is not based on the opinion of a single editor, and we don't need a special procedure. See my comments above in #Indefinite semi-protection?. – Steel 23:40, 5 May 2007 (UTC)

I like that that comparison there. But I disagree that sometimes it is based on the opinion of 1 editor (for example, if I come across an article that has massive recent vandalism, I might protect it). But everything is over-turnable too. For example, if someone declines to protect on RPP, then another admin might come along and protect if they think it needs to, and I don't really care if someone overrules me on something like that. -Royalguard11(Talk·Review Me!) 00:32, 6 May 2007 (UTC)

When I said "that's a really good idea," I wasn't referring to that silly bit with all the percentages - I only meant your idea about setting up Wikipedia:Protections for discussion and Wikipedia:Protection review. Right now, if I un-semiprotect a page because I don't believe that the vandalism on it qualifies as "heavy", and somebody else re-semiprotects it because he does feel that the vandalism on it qualifies as 'heavy', it would be nice to have a forum to use to come to a consistent decision, and to see other similar cases all in one place. - Brian Kendig 15:21, 7 May 2007 (UTC)

Each others' talk pages, or if you really can't resolve it, ANI. Really, does this occur so often that we need yet another process for it? – Steel 15:23, 7 May 2007 (UTC)

I suppose not. All I'm really looking for are some better guidelines for what constitutes the sort of "heavy vandalism" which merits semiprotection. It seems that a lot of articles are semiprotected after a short period of light vandalism, and I'd like to see the guideline be clearer about this. - Brian Kendig 18:02, 7 May 2007 (UTC)

Case in point: Geometry

This conversation is relevant to a discussion at the Math WikiProject right now. User:Arcfrk made a strong argument for protecting Geometry. Of course there are also the foundation principes to consider. I would appreciate hearing others' thoughts on the matter. CMummert · talk 13:30, 11 May 2007 (UTC)

Given that history, I would semiprotect it for a couple weeks. I don't see where it contradicts "current admin practices", because there are no unified admin practices regarding protection (I mean, there's no formula, no requirements than need to be met for each and every case. Each admin may evaluate in a totally different way). The protection log is also clean, so it didn't just come off protection or anything. So I would say s-p is a good band-aid for a little while at least. -Royalguard11(Talk·Review Me!) 20:57, 11 May 2007 (UTC)

There are two ways of approaching vandalism protections. Either we look at the rate of vandalism and ask ourselves whether it's too high to expect volunteer RC patrol and watchlisters to revert it (Eg, George W. Bush), or we look at the article itself and ask whether an anon activity in general is likely to improve it or not (Eg, Geometry). For new, high profile articles (Eg, Virginia Tech massacre, back when it was in the news) the first approach is definitely the way to go. For mature articles on non-trivial subjects (trivial subjects being List of .hack//Sign episodes and the like, non-trivial being Physics and such), we need to consider shifting the mentality from the first approach (which is current practice, policy, and ingrained in many people's wikiphilosophies) to the second. – Steel 21:10, 11 May 2007 (UTC)

Thanks for the comments. The only reason I hesitate to protect the article is that the reason to protect it (its high profile name) will never go away, and so the protection would be justified indefinitely. And I'm sure there are a lot of other articles in the same situation; it's hard to protect one and then refuse to protect the others. CMummert · talk 22:56, 11 May 2007 (UTC)

You've got to at least try unprotection for some articles (heck, even Bush gets unprotected a couple times a year). -Royalguard11(Talk·Review Me!) 04:13, 12 May 2007 (UTC)

... or we look at the article itself and ask whether an anon activity in general is likely to improve it or not. However, that's not a criteria for semiprotection - as the guideline says, "Semi-protection should not be used to prohibit anonymous editing in general." - Brian Kendig 04:36, 12 May 2007 (UTC)

I know that; perhaps I wasn't clear. The first approach is current practice and policy, the second isn't, but en.wikipedia needs to at least consider shifting in that direction. – Steel 16:03, 12 May 2007 (UTC)

Or we should shift in the direction that we use semiprotection to dissuade some people from making repeated vandal edits (the same reason for blocking really). It's kind of like a "smarten up". -Royalguard11(Talk·Review Me!) 19:59, 12 May 2007 (UTC)

That sentence in the policy page ought to be reworded - the entire point of semiprotecting a page is to prevent anonymous editing in general. The alternative is to block IPs one at a time. C Mummert · talk 20:45, 12 May 2007 (UTC)

To temporarily prevent anonymous (and non-autoconfirmed) editing. -Royalguard11(Talk·Review Me!) 21:08, 12 May 2007 (UTC)

The distinction is that you don't want to say, "I don't think anons should be allowed to edit this article." That goes against the spirit of Wikipedia. - Brian Kendig 21:30, 12 May 2007 (UTC)

Although the change to policy because of this talk looks good, I fear that it may lead to more wikilawyering about it (who else but the protecting admin can say what the "sole purpose" was). -Royalguard11(Talk·Review Me!) 02:28, 13 May 2007 (UTC)

I found it very difficult to find a good phrasing for that bullet. If anyone else can think of a better way to express it, please get rid of my phrasing. Anyway, I think admins are less prone to wikilawyering than is generally feared, especially about admin actions.C Mummert · talk 03:18, 13 May 2007 (UTC)

I meant some users may wikilawyer about an admin decision to protect saying that they're intent was to prohibit anon editing or something. -Royalguard11(Talk·Review Me!) 05:30, 13 May 2007 (UTC)

One of the main problems with the protection policy is that some admins focus on the number of vandalism events per unit day. But this is not the critical measure. It should be the fraction of vandalism edits per total number of recent edits. This is because it does not matter how fast the vandalism arrises on a page when you are trying to undo the edits. It just matters how many of them there are mixed in with the productive edits. So I think we could gain a lot of ground by explicitly mentioning in the policy that the rate of vandalism shall be measured per unit edits when we are determining if a page has high low or medium vandalism.

Ttguy 10:25, 16 May 2007 (UTC)

A more explicit semi-protection policy for articles subject to vandalism

Our current policy says:

Articles subject to heavy and continued vandalism, such as George W. Bush.

I hope we can work out some guidelines for this. I recently indefinitely protected Superman, Batman and Spider-man. The elated response I got from the regular Batman editors makes me think that I was doing the right thing. I've gone over this page looking for some guidelines for making decisions about when to add semi-protection and for how long and found none. I have noticed the following about the three pages I semi-protected, and perhaps this can be the start of some criteria for adding semi-protection:

• The vandalism is often of an offensive nature on high profile pages. This has a detrimental effect on how Wikipedia looks to the public.
• Almost all, if not all of the vandalism is coming from anons. Semi-protecting would effectively solve the vandalism problem.
• Anons are making very few contributions to the article compared to the amount of vandalism coming from anons. Blocking anons would not have a large effect on discouraging their positive contributions.
• There are regularly many new vandals, therefore it would be a huge task to notify and warn all the vandals. This seems to be too large and too dreary a task to expect anyone to undertake.
• The proportion of constructive edits to nonconstructive edits (vandalism and the reverts) by all editors is very low. This means that the regular editors are devoting most of their effort to reverting vandalism.

These seems like a good set of criteria for semi-protection. In addition, I've noticed the following:

• All of the pages have been semi-protected previously. This shows that the problem is on-going, and that temporary semi-protection did not help.
• Vandalism continues very shortly after semi-protection is removed. This shows that the page is a popular target for random vandalism.
• The vandalism is not related to a current event (I'd have to check this for Spider-man). If it were related to a current event the semi-protection could be lifted once the event was out of the public eye, and perhaps it would no longer be needed.

These seem like some good criteria for making the semi-protection indefinite.

What do people think about this? Should these criteria be quantified? I'm new to the semi-protection policy discussion. I'd like to hear from others who have indefinitely added semi-protection, and what criteria they have used to decide. -- Samuel Wantman 01:22, 14 May 2007 (UTC)

I feel that this part of the policy should be as loose as possible to allow for the greatest amount of flexibility by admins. Although several of those criteria that you listed are already de facto when it comes to indefinitely semiprotecting pages. Although I'd like to respond to a couple of them.

The vandalism is often of an offensive nature on high profile pages Not something new or alarming. This happens on all pages really

Almost all, if not all of the vandalism is coming from anons and Anons are making very few contributions to the article compared to the amount of vandalism coming from anons This has already been studied (not vandalism studies, but other ones), and it's already widely known. But it's a Foundation issues (#2)

There are regularly many new vandals, therefore it would be a huge task to notify and warn all the vandals There are many JS's to quickly warn vandals, and there will always be new vandals here. And sometimes I think that people need to be less lazy about it. Sprotection isn't the end all-be all of answers. -Royalguard11(Talk·Review Me!) 01:40, 14 May 2007 (UTC)

Perhaps, some day, after too many pages are semi-protected there will come a cry from the vandal patrollers, "Please unprotect some more pages so we can track down more vandals!" I don't see this as being very likely. The reality is that we have the ability to semi-protect, and admins are using that ability to semi-protect articles. The point of having guidelines is to describe what the current practice is as it evolves. By making it explicit we can discuss the pros and cons of the practice. Are you advocating not having guidelines? If you think there should be guidelines, what do you think they should be? -- Samuel Wantman 01:52, 14 May 2007 (UTC)

Are you advocating not having guidelines? Am I an anarchist now? But really, there's no point in trying to create guidelines for when to permanently protect pages. You'd have to throw in over a hundred "if" situations. Usually permeant sprotection comes about after discussion by admins/editors, or sometimes an admin will just declare when semiprotecting a page "don't unprotect it, it doesn't work", and other admins come around, see the history, and agree. I think we need to trust our admins a little more. We're not perfect, but that's what talk pages are for. -Royalguard11(Talk·Review Me!) 22:28, 14 May 2007 (UTC)

I'm an admin, and I've spelled out the criteria I am using. I want to hear from others about the criteria they use. If there is a consensus about the criteria, we can write a guideline. This doesn't mean that it is rigid, inflexible and incapable of changing. What it would mean is that each admin would not have to reinvent the wheel from scratch. I want to hear from the collective wisdom of the community about this subject. I also don't think it is a good idea for each admin to have radically different criteria for protecting pages. If that were the case, people would shop for a hard-ass protector when they want a page protected and a lenient one when they want it unprotected. A scenario like this sounds like a recipe for frustration. -- Samuel Wantman 23:53, 14 May 2007 (UTC)

Nice to see some discussion of this. Not having guidelines is very frustrating, not only for unsure or inexperienced admins, but especially for editors who want to request protection. They come here, but they get no indication of whether their article is appropriate for protection or not. Additionally, there is inconsistency among administrators - I've had some admins protect some pages with continued but low levels of vandalism, while others have stated they would expect at least 15-20 vandal edits a day before they would consider protection. Besides the number of vandal edits, two other important factors could be considered if proposing guidelines (even just very rough ones) - the percentage of time the article remains vandalized (this is important for reader perception - it isn't quite so bad if the vandalism is cleaned up quickly), and the percentage of vandalism vs. contributive edits (an article that has had little addition for a month is a better candidate than one that is vandalized, but also improved regularly).

I think it would be a good compromise to provide some rough guidelines, pointing out that it isn't simply one factor that is taken into consideration, and making it clear that there is no concrete rule and that administrators will use their own personal judgment as well. Richard001 09:21, 14 May 2007 (UTC)

See related discussion at Wikipedia talk:Protection policy#Indefinite semi-protection? and Wikipedia talk:Protection policy#Semiprotection in response to continual low-level vandalism?. – Steel 14:02, 14 May 2007 (UTC)

I, for one, like Sam's first attempt at some guidelines. As I've said before, I believe we should have them. Maybe one other thing to consider, at least loosely, is a ratio of constructive vs. vandalism edits from IPs on the subject article. If there's evidence that it's the type of article that IPs regularly edit constructively, then there's a good case for keeping the protections as temporary as possible. On the other hand, if a look back over the previous month or two shows that there's a lot of vandal IP edits and almost no constructive ones, that's a good argument in the other direction. Akradecki 00:10, 15 May 2007 (UTC)

Well then, I must admit that I don't really have a list of criteria that I follow. Every page is pretty unique in the vandalism it receives and the amount. That's why I never evaluate based on the article's topic. I don't know what half the pages I've protected are about. That's because we should be treating every single page the same in terms of vandalism. If it's getting hit just a ton, then it's semi'd. I also don't look at each individual edit to check it for vandalism or good faith. When I look through history, I specifically look for reverts (admin, TW, VOA script, VP, VS, popups, undoes, others). A revert tells me the edit was judged to be bad. If the page has just a ton of edit-revert combinations in the first 50, then it's a excellent candidate for semiprotection (esp if it's over the past couple days). A good candidate for indefinite would have a lot of prior semiprotections in the log, which might have been on and off for a good while (not just a couple months). Other unforeseeable circumstances would have to be taken into effect also. -Royalguard11(Talk·Review Me!) 03:39, 15 May 2007 (UTC)

The process you describe sounds very much like the process I've used. It sounds like you have criteria, you just haven't made them explicit. You are going through a process to convince yourself that semi-protection is needed, and there are no other practical options. Like you, I look at the history and the protection log. I look at the history based on the when the previous protections started and stopped. Comparing the vandalism level before and after gives me a good idea as to whether the protection should be temporary or indefinite. I also check some diffs if it is unclear whether an anon was reverted or not, such as when there are several anon edits followed by a revert. I'm not hearing anyone saying that there should be criteria based on quantities or ratios. I'm fine with leaving that as a judgement call. -- Samuel Wantman 05:07, 15 May 2007 (UTC)

As a non-admin person trying to understand the semi-protection policy I want to say - yes we need a more explicit policy on this. Because it has been my experience that several admins measure the degree of vandalism on a per unit time basis. They will look at the history of a page and say "there is only one vandalism event per day - this is not enough for semi-protection". However this ignores the fact that it does not matter if 10 vandalism edits arrive on a page in one day or over 10 days, if, in both cases, they are mixed in with 2 (say) productive edits. It is just as much work to find the vandalism and undo the edits. So I think the policy should explicity state that the vandalism rate is to be measured as non-productive edits per total number of edits rather than non-productive edits per day.

I have had an admin say that they will not protect a page because the level of vandalism on the page is just the "usual level of vandalism". The problem with this is that the poor admin guy is allways looking at pages that have come up for request for protection and thus she thinks that the degree of vandalism on these nominated for protection pages is the norm. I did a quick little analysis by using the Random page link to see what the rate of vandalism is on a few random pages. You can see the details of the analysis here. But in summary on two random pages we have 100% and 47% of the IP address edits being productive whereas on pages nominated for semi-protection we have

Genetically_modified_food the fraction of productive IP edits is 6%

Geneticaly Modified Organism the fraction of productive IP edits is 16%

1992 the fraction of producive IP edits is 15%

I think it would be a good idea to codify what constitutes "significant" levels of vandalism from IP addresses. And I would suggest that it should be a figure calculated by counting the number of IP edits done in the last 50 edits and calculating a fraction of productive IP edits from this. Then applying an arbitrary number - say 30% - If the % of productive IP edits is 30% or greater then you do not semi-protect the page. If the % of productive IP edits is under 30% you do semi-protect it. We don't need this arbitary % figure. But what we do need is to get away from the vandalism counts PER DAY method. Looking at the ratio of productive to non-productive edits is the way to go and this should be codified into a policy. IMNSHO

Ttguy 14:56, 15 May 2007 (UTC)

Yes, I'm very glad someone brought the subject up. Looking at the RFPP's, I can definitely see fluctuations in the criteria for semi-protection. I, for one, enforce this rule with less leniency than the average admin. Other than looking at recent vandalism, I also look at the long term vandalism and take that into account. Since there are no apparent guidelines on the protection policy at this time, there may be conflicts over whether to protect a page or not (i.e. history of vandalism vs. recent vandalism). For example, just recently, an admin closed an RFPP as a decline. Then, the user who applied for the RFPP (the user who commented above) re-submitted and I ended up semi-protecting the article for 1 week. There definitely should be reform on this. Sr13 01:52, 16 May 2007 (UTC)

Please avoid instruction creep. Need for protection, regardless of the vandalism amount, varies significantly from a page to page, and so is the sensitivity of vandalism and/or disruption. The best thing to do is just trust the judgment of administrators in accepting/declining a nomination. Michaelas¹⁰ 14:08, 16 May 2007 (UTC)

As another non-administrator, I also think some more guidelines should be in place. I had become very frustrated over a period a weeks at the vandalism in an article I was watching. I finally looked up the protection policy and submitted it for semi-protection. I was shocked when protection was declined. What I thought was clear case of heavy vandalism (41 of the last 50 edits being either vandalism or reverts) was viewed differently by someone else. Frankly, I'm still not sure why it was declined. Following this, another editor and administrator got the article protected.

Wikipedia allows articles to be protected. It may as well be used in a consistent way. This would help regular editors as well as administrators avoid frustration and better use their time. TK421 20:09, 16 May 2007 (UTC)

If you can find a diff, that would help us out more. We can't comment on why it was denied or even by who, as there's no log of RFPP, as it would be very, very long. And the best way to understand the policy is to see it in action, not read it. Admins kind of have a de facto standard for protection for the most part (and it's definitely not all about x amount of edits over y time period, but that is a part of it). -Royalguard11(Talk·Review Me!) 22:07, 16 May 2007 (UTC)

"Temporary protection" not so temporary

increasingly i find pages that are allegedly "temporarily protected" are simply protected in such a manor to prevent anonymous editing. this is a clear contravention of the use of semi protection policy. this is done to avoid the proper discussion that would be involved in permanently protecting a page.

if an article is indeed going to be temporarily protected. attention must be more prominently brought to this fact. the template should show when the article was protected and should emphasize that it should be unprotected as soon as possible... —The preceding unsigned comment was added by 58.106.71.227 (talk) 13:44, 14 May 2007 (UTC).

You first paragraph indicates that you don't understand the policy; your second indicates you don't understand how protections and unprotections actually work. At any rate, I encourage you to create an account and protected pages will no longer be a problem for you. – Steel 14:02, 14 May 2007 (UTC)

first of all i don't see how your arrogant and dismissive response is likely to help anyone...

please correct me if i am wrong but my understanding of the policy is that it is quite clear that semi protection should not be used "With the sole purpose of prohibiting editing by anonymous users. Protection should be used only to prevent continuing disruption." it is also clear that permanent protection is ONLY to be used for "heavy and continued vandalism." it is clear to me that light or sporadic vandalism is not grounds for permanent protection. the problem i am highlighting however, is that" temporary" protection in far to many cases has become defacto permanent protection.

i think you would do wise to consider foundation issues. —The preceding unsigned comment was added by 58.106.71.227 (talk) 14:19, 14 May 2007 (UTC).

Perhaps you could provide examples. – Steel 14:22, 14 May 2007 (UTC)

even for an example such as John Howard where the protection log shows it has been protected and unprotected frequently. it has now been protected for over 3 months. this is not TEMPORARY. now I'm not saying a case might not be made for permanent protection. but call a spade as spade. don't use this defacto permanent protection to avoid the discussion. —The preceding unsigned comment was added by 58.106.71.227 (talk) 14:40, 14 May 2007 (UTC).

If an article is protected frequently and generally gets reprotected shortly after an unprotection due to vandalism, people begin to see little value in trying another unprotection and it becomes a permanent protection by de facto. That's the way we do it; we don't have discussions on what articles to designate 'permanently protected'. – Steel 14:48, 14 May 2007 (UTC)

Ditto to what Steel said. Eventually it becomes pointless to unprotect. If you want to take it up with the foundation, I'm sure they'll side with us on this one (sometimes practicality overrides principle). -Royalguard11(Talk·Review Me!) 22:23, 14 May 2007 (UTC)

I concur as well. Though it may seem pointless, I'd unprotect any page if requested to test whether the vandalism level is low. Better to call it indefinite protection, rather than permanent. You never know, miracles sometimes happen. -- Samuel Wantman 05:13, 15 May 2007 (UTC)

• If you see articles that have been "temporarily protected" for, say, a month or other excessively long time, please visit this forum to request unprotection. >Radiant< 12:10, 15 May 2007 (UTC)

Propose move protect lock and info change

See Template_talk:Pp-move for more details. -- _Hdt83 ^Chat 14:59, 15 May 2007 (UTC)

Lock colors and what they mean

Could a table explaining the various colors of locks be added to the policy page? Silver, gold, and the greenish gold that is on WP:HD don't really emote the particular protection that is in force on a particular page. I'm just thinking something simple like:

Examples

	Gold	Protected from editing until disputes have been resolved Protected from editing to deal with vandalism Protected from editing to prevent [Page name] from using it to make disruptive edits or continuing to abuse the {{unblock}} template Protected from editing It is a high-risk template that has been protected from editing to prevent vandalism.
	Silver	Editing of this page by unregistered or newly registered users is currently disabled to deal with vandalism, It is a high-risk template that has been protected from editing by new or unregistered users to prevent vandalism, A user talk page that has been protected from editing by new or unregistered users to prevent [User name] and other new users from making disruptive edits, Editing of this page by unregistered or newly registered users is currently disabled to deal with vandalism by a spambot, Editing of this page by unregistered or newly registered users is currently disabled.
	Olive	Protected from moves until disputes have been resolved on the discussion page.

Dismas|^(talk) 22:24, 16 May 2007 (UTC)