Knowledge talk:Semi-protection policy/Archive 1

3365:

a permanent fixture of the page, remaining semi-protected for several months, possibly even until 2009. Such permanence requires a hell of a lot more discretion and caution on our parts. Imagine other pages which aren't quite vandalized a lot, and lets say one get a flurry of vandalism. An admin could rightfully up the level to 100+ edits, and then justify keeping it there for a lot longer than the vandalism flurry. It will become highly easy to justify leaving a page with a requirement of 100+ edits, as it would stop vandalism and no obvious signs that any editors had been turned away could be discerned. Thus, without such discretion, semi-protection would be endangered of the very thing Splash keeps talking about: protection creep. A time limit would generally solve this problem, but on some pages like GWB, permanent semi-protection is definetely warranted. Thus, either semi-protection should come in the temporary form up to a maximum of a week, which can be initiated by any admin, or a more permanent form, which should come from a concensus of at least several admins to respect the wiki way. --

3655:

from drive-by vandals. If a page has vandals dedicated enough to wait the week, then we can just up it to 3 months with the 5 admin concensus. I'm telling you this right now, and I will bet a large amount of money on it, if we don't set time-limits, you're going to see the amount of pages semi-protected jump a considerable amount and stay that way. The funny thing is, I really am more on your side about semi-protection, I'd rather it be applied very liberally to a lot of pages without restricting the time limit, but I do agree that Splash has a valid point (which I wish he would chime in with) that unlike normal protection, semi-protection has a definite potential to expand quite beyond its original use. By the way, when you get a chance, if you could answer my previous question, how will a time limit or lack thereof affect the potential for protection creep? --

3492:

off as a "test" and then possibly put back on. I'm not being critical, but I'd suggest looking at the pages we protect now. Admins are always double checking them to make sure that they should be protected. I think semi-protection will be similar. Every day, we will have admins (probably me, dmcdevit, katefan0 and others) looking at the semi-protected articles to make sure that they should be kept semi protected. I think you are making a faulty assumption. I think we need to start slow with it...if it looks like you are right and it'll be mostly permanent, THEN we can do time limits. I just really don't like putting shackles on this on the get go. I think it's counter productive. And how do you know tht it'll just be used for vandalism? I could see it used to stop edit wars in extreme cases, since there are times that anon IPs and new users (look at

3723:

help with the matter should be made. I personally don't think un-semi-protecting a page should require 5 or any amount of votes, it is the process of semi-protecting that should require these votes. That's like passing another test only if you don't want to renew your driver's license. If this were so, not many people would want to make the effort to get 5 votes just to unprotect a page. The duress of concensus should be placed upon keeping the page semi-protected in order to address concerns of protection creep. Just to clarify, my proposal is that any admin can semi-protect a page up to one week, an admin seconded by another can semiprotect up to a month, and 5 admins semiprotect up to 3 months, where any more than 2 consecutive semiprotections require the consent of 5 admins as well. --

3089:), I propose that there be some sort of threshold for the percentage of edits that are vandalism-related before a page may be considered for semi-protection. For example, if the threshold for semiprotection were set at 80% in the last 50 edits, then over 80% of the last 50 edits to an article would have to be vandalism-related before an admin could arbitrarily protect it. Pages would be eligible for un-semi-protection after a predetermined interval of time (unless, of course, the vandalism rate were to still exceed the threshold). Even if my proposal is rejected, I still support the introduction of semi-protection. It might help significantly in reducing the wiki-stress that leads to premature 3539:

having people cry "See, it didn't work, that's what happens when you mess with the wiki way!" Let me ask you this, Woohoo. Seeing as if semi-protection is doing its job and a previously vandalized page is no longer vandalized, what specific criteria would you use to determine when "making sure that they should be kept semi protected"? If there is no vandalism, how long do you wait before un-semiprotecting the page? Is this amount of time arbitrarily picked out of the blue, or will you wait the same amount of time, keeping in mind the only evidence you have is the lack of vandalism? Do you think other admins will be as conservative as you are in leaving semi-protection on certain pages? --

3482:, the reasons for semi-protection are different. We only semi-protect a page when there is vandalism occuring, at the unobservable consequence of restricting valid anonymous contributions. There needs to be a time limit set for each semi-protection, otherwise the reality will be that many pages will simply remain endlessly in their state of semi-protection, as it has observable benefits (no vandalism) and unobservable consequences (no valid drive-by users). Forcing time limits along with requiring escalating thresholds of admin concensus strikes a balance between those who wish to combat vandalism and those who wish to cater to the benevolent anonymous drive-by contributor. -- 3563:

dilligent and the most incompetent admins will be using this policy. Though you might be conservative in leaving pages semi-protected, other admins could see it vastly different and keep pages semi-protected for a long long time. If you came along the page and told him that the page should be un-protected and he disagreed, who would be right? How would it be decided? By making this policy as explicit as possible, we reduce the chance of ambiguity in its application. This does not require testing on our part, as it is either going to reduce vandalism or not. Lets say it does. How will the lack of a time limit affect the potential for protection creep? --

1184:

level, there is a hierarchy here in any case; people who reach a certain number of edits can gain the respect of the community and can become admins and have a greater impact on the day-to-day look of any given page, among other things, which is as it should be, I think. Requiring people to make real edits before they edit sensitive pages is not an undue burden on them. I also think that pages should not be protected because of their "importance," but protected when they are under constant attack by multiple IPs, for whatever reason. I'd be in favor of Level 4 protection for a fair number of pages.

1550:

quick to revert the vandalism, this makes not stopping the vandalism acceptable? That's more fundamentally wrong to me than to protect high profile pages. Anyway Hall Monitor, I think the only reason why we can't really use protection against the Bush page is because in order to stop vandalism using the current process, we'd have to have it protected 24/7 and that's not acceptable to Splash or me or anyone else I've run into. I mean it literally gets hit multiple times an hour. It makes it kind of pointless to permanently protect it, which is why I think semi-protection is a good idea. --

3687:

where we won't even have 5 admins working on semi-protection. It's just a fact of Knowledge. Alot of the admins just do not like doing this sort of work. So I understand the concerns of Splash about creep, but in terms of admins to start semi-protection and extend it, we need to look at stuff like quorum and committees. In other words, that's part of stopping creep as well. I mean if we never have 5 admins working on the s-p page and we have this 5 vote rule, then yes, pages will be semi-protected forever. That's why we need to be careful on time limits and minimum votes and such. --

2286:-- building an encyclopedia. Without the encyclopedia mandate, what's the point of the wiki? High-falutin' ideals are great, and I value the idea of open-source et al, it's clearly important to Knowledge's success, but it also does no good if Knowledge drowns in a cesspool of (valid) criticism. I can't imagine any newspaper writing an article criticizing Knowledge for its articles being protected too much (people outside Knowledge, frankly, don't realize or care); on the other hand, the USA Today editorial is a perfect example of the kind of things that WILL get noticed. · 2260:

legitimate edits are performed on that article, it's not like there's a flood of them. They can be handled on an individual basis. We have a large enough corps of administrators. Do I suggest protecting it forever? No. Do I suggest protecting it until the devs give us a better option? Absolutely. I don't speak for every admin but I may just remove it from my watch list, not wanting to clean up after the mess of others, especially when my fellow admins encourage the mess. I would not be surprised if other admins are similarly annoyed with always being on vandal watch. --

3251:

that's a fact of life that comes with a wiki. However, the question should be whether the benefits of this proposal outweight the downsides and risks; I believe that there are too many risks, uncertainties and unknowns to overcome the (in my opinion) limited benefits that we can get. Vandals, in my opinion, seem to be more determined than potential users stumbling upon Knowledge for the first time; vandals won't let account age or editcountitis stop them. We shouldn't risk losing many potential valuable contributors in the hopes of stopping a few vandals. Thanks!

3527:

controversial because some thing they made the stuff up. To make a long story short, we ended up with countless sockpuppets and new users constantly edit warring on the page. Eventually the arbcom ruled that they can be banned on sight if there only edits have been to the Bogdanov Affair article. Now see on that one, we could've just put it in semi-protection for awhile and that might've let us avoid the arbcom case. That's the kind of case I mean. And as Knowledge gets bigger and more prominent, cases like that might happen more often. It was just a thought. --

2299:'the wiki format is a means to an end'? So once an article is complete it should be locked, and one day hardly any articles will be left to do and it will be finished? No, that is the encyclopedia on my bookcase. Locked the day it was published, outdated the day after. I think, if wiki is to work in the long term it can not go the route of locking things down. Otherwise it is exactly the same as any other encyclopedia. It will be necessary to educate readers as to the limitations of an encyclopedia of this nature. Oh, and a decent page rating system would help. 3573:

us doing something like that. There's also the idea of maybe electing a committee of admins to do this. That way we'd always have x number of admins voting. Because like I said, for the protection page, it's voluntary. Right now there is 3 of us on it full time but there has been 5...for awhile they had one guy doing it and that was it. It'd be hard to require a vote of 2 for something if suddenly we only had one admin doing the entire page, which is a possibility. We have 700 admins but many of them do not do "dirty work" like this. --

4350:

discrimination against possible legitimate editors? Whether its Spanish or English, I don't think it really matters, 25 edits along with a 5 day minimum account life (to counter vandalbots) for level 1 and 100 edits with a 1 month edit time for level 2 (for pages like GWB) will suit all intents and purposes, even as Knowledge grows in scale. As for simpler to code, I don't see logically how that is simpler than just running a simple check against the user whether their account has existed for X amount of time and they have X edits. --

3317:

something like this be decided automatically or on a case-by-case method? How will your said proposal address protection creep, or the tendency for exponential increases in the amount of semi-protected pages? How should pages become candidates for semi-protection, through the community like request for protection exists today, or through admin discussion? Should semi-protection self-expire after a predetermined time, or should it change status according to a vote? If it self-expires, what about continually vandalized pages such as

2195:) To me, the real question is a philosophical one. And that is -- which is worse: Someone coming to a vandalized article that says "George W. Bush, president of the United States, is a GIANT PENISHEAD!" and thinking "Man, this Knowledge sucks, I'll never use it again" -- or someone coming to the article, not being able to edit, and therefore not getting addicted to Knowledge enough to become a regular contributor? Which is worse? Damage to Knowledge's reputation as a reference work, or damage to Knowledge's pool of new users? · 4125:. We have 100 pages protected. And 1/3rd of those are temporary. With semi-protection, we'd be looking at another 50 or so probably? So 150 articles out of 800,000. I think it's a small price to pay to make the encyclopedia more readable and to ease the burden on admins. Bush is literally vandalized every 5-10 minutes. I just don't see where it's a big deal here. We're not talking thousands of articles. We're talking less than 100. I don't see jumping from this to "we're stopping the wiki element of the site". it's alarmist. -- 3549:

but some allow more than others. So it's really hard to answer that. And again, it's going to depend on the case. And if we keep the talk pages completely unprotected, we might be able to see from there whether the vandalism has gone away. So I can't really say, kizzle. I wish I could. It's just going to vary. On the protection page, we often give pages a "try out" for a few days just to see if the vandalism subsides. We might end up with something similar for semi-protection. There really is no other way to test it. --

3585:

instead. We might be able to judge vandalism by that. Vandalism on talk pages isn't quite as big of a deal simply because it's not as visible to the average reader of the site. I mean it's not good :) But for our purposes, it's not as bad. We can also look at what kinds of editors are editing the article page. Is it people just over the threshold? If it is, then maybe unprotection isn't the best thing to do. Other than that, time would be an issue. If it's been 2 weeks, then maybe unprotection could be tried.

1463:) Hi there. You've recently begun something of a determined course of action to have this article protected. Admins have repeatedly unprotected it quite quickly; I was wondering if you were aware of this. It's fundamentally wrong to have our highest profile articles protected, in the same way we never protect the main page article. Most vandalism on GWB is removed in well under a minute, and those in #wikipedia-en-vandalism practically scramble to be the first to revert. Perhaps you should take a look at 3523:

has literally never been tried and we really have no idea how anyone will react. The other idea would be to do a trial for like...a month...analyze the results and then make a permanent policy, which could include time limits. I can see us having time limits. I just don't want to start with them. I want this to be open for awhile just to see how it pans out because we can sit here and argue theoretical and what we think will happen, but we won't really know until we start doing this.

957:

small amount of pages. We're not talking 100s here. It would probably be the same amount of pages that are permanently protected...20-30 at most. It wouldn't stop discussion on talk pages. It would just give a threshold for editing certain pages. And btw, I work on the Protection request page every day. I'm very careful about protection. Like I said, I'm not talking every article we have or even .1%. It'd be the more visible ones that get vandalized alot. --

644:: 23 were vandalism. 18 were reversions. The difference is because of vandals in a row. That's, together, 41 edit out of 50. The reverts have been very quick, but it's a problem regardless. The article gets vandalized several times per hour. I took a random hour of today and counted 5 vandalisms in it. Given 1 minute to revert each, that would still be 5 minutes in an hour that the article is vandalized, which amounts, by the way, to 8% of total time. 31: 3508:

is missing the point: in the case of an edit war or POV dispute, we would protect the entire page, even in extreme cases. If we only semi-protected in such disputes, it would allow certain editors in the discussion to edit the page while others couldn't simply because they hadn't been on as long, which would be fundamentally unfair. Just because an edit war involves new or anon users, doesn't mean they are in the wrong. The

4363:, which would be set in every individual Wiki (we don't know how much vandalism is considered "acceptable" at other Wikipedias, and some of them have a minimum one-month block guideline for vandalism, so there will be other interpretations besides ours) The problem with coding a number in MediaWiki is that it is first, bad programming practice, and second, prevents other Wikipedias from setting their own policies. 2272:

of the trash and AfD the rest. I think more damaging than journalists ranting are stories in whichever paper it was about Wales having to protect the GWB article for the whole of 2004 (when it was only during the campaign) to which there is no "yeah, but" defence, apart from the fact that it wasn't Wales who protected it. Having an article protected from now until 2009 doesn't seem at all right to me. -

1385:

unwiki, especially given the article is completely uneditable, highly vandalized, and a pain to deal with. We should be hashing out what process should justify semi-protection, currently, I think an admin vote of at least 15 people with a 70% pass rate should set semi-protection, in addition to only allowing semi-protection to go up one level at a time, in other words a separate vote for each level. --

3151:

high-traffic pages is a bad idea. While the principle - attempting to strike a balance between editing and stopping vandalism - is good, I don't like the implementation. What is 25, 50, or 100 edits to a vandal? Vandals, including those who are determined enough to write a 'bot to vandalise, won't let an arbitrary number of edits stop them, especially after they start vandalising other pages first and

2573:. But most experienced users who leave, including Essjay and Kate, are motivated not by single incidents but by an overall feeling of wiki-stress and desperation. (I know this sounds dramatic, but it takes a serious problem for such dedicated contributors as Essjay and Kate to abandon Knowledge.) Undoubtedly the vandalism situation is an important factor. No one can say it better than 1399:

administrators, except in special circumstances (I've seen one edited by an admin all of once). Semi-protection would allow edits by everyone over a certain threshold, which means that basically 90% of the registered users (if not more) would be able to edit the page. So shouldn't it be less restrictive or be the same level (one admin) as protection? I don't quite understand that. --

2668:

in the resiliency of the wiki, but only so much. You cannot honestly tell me that a new user will leave in disgust if they can't edit a page, so please do not even compare it to images of penises, feces, Hitler, or other juvinile vandalism. There is no way anyone can make an argument that these two are even remotely comparable. The issue at stake here is not Knowledge's

484:

this is to stop the vandalism, which has consumed our editing resources and, in effect, help editing. Just like the main page, this is a high profile page, and we want to keep it as clean as possible. I don't know about disallowing anons to edit, but I do think if we left the threshold at 25, vandalism would be greatly decreased. Thanks for your questions. -

4422: 1202:

more power than other users. We'd be creating one, possibly 2 more levels of users and it would be for just semi-protection and nothing else. And we're not talking 1,000 edits or 100 or even 50. It would just be a way from stopping anons and brand new users from vandalizing some of these pages. IronDuke, the thing with importance is that we already

828:— Related to the above, we will, with absolute certainty, end up with more articles in a state of protection. Knowledge is nowhere near finished, despite the endless push to WP1.0, and low-level protection of more articles will inhibit the process. Articles contributing to this point will also be subject to protection creep of the first kind. 2152:.) It doesn't matter how wrong the journalists are with their accusations of completely vandalized pages, the fact remains that it hurts our image. We need to make ourselves look respectible before we can look credible. The warnings would be very useful, and even if this fails, I think they should go into effect currently. - 519:

users). i.e. After an account reaches a certain age, then it can edit a semi-protected page. This would drastically cut down on vandalism, allow non-administrators to freely edit high traffic pages after minimal experience with Knowledge, and free up administrators time to accomplish other tasks: a win-win-win situation.

3456:

comment, if we apply a time limit to semi-protection along with increasing amounts of admin concensus for consecutive applications of such protection, it will get progressively harder for semi-protection to expand beyond its essential uses, thus I'm not too worried about protection creep in this implementation. --

3246:

spend time counting the exact edits? What distinguishes an article that has 79.9% vandalism and one that has 80.1% vandalism? Who likes rhetorical questions? :-) No, seriously though, my point is that I don't think setting an arbitrary percent that can be calculated at any random time would be too effective.

3860:

Anonymous users shouldn't be allowed to edit SP'ed pages. If they want to edit a page, they should create an account, just as AOL users must create an account if they want to recieve their messages. It's not like it's a big deal to register. All you have to do is choose a name and password. If you're

3722:

I realize that admins won't like doing this stuff, but you didn't go through a popularity contest just to get a rollback button and block people who disagree with you ;). A protection/semi-protection informal committee should be formed, and a push to recruit at least a dozen out of the 700 admins to

3654:

We don't have to and probably shouldn't advertise when the page will be un-semiprotected, the only way they could tell is if they went to the semi-protection page, looked up when it was initiated and for how long, and then waited that long. Keep in mind that a significant majority of vandalism stems

3618:

want a fixed time limit on when to try to unprotect the article, because that would just be too much of a signal to vandals. It's why we don't do it for protection now. I mean if you say, ok...in 2 weeks, we have to try unprotection, well then the vandals will wait until it's unprotected and then hit

3465:

I would prefer that we not do time limits. If you look at the protection cases we have now, there are no rules per se. Time limits are just not practical. In some cases, a day will be enough. In some, 2 weeks will be enough. In some cases, it might be longer. It all depends on the situation. I really

3406:

Actually I can accept that. I'd go for maybe extending it to 2 weeks for a single admin, but you are right. We probably should add more admins to make it permanent. If anything else, it'd gain consensus, which is one of our mantras. More powerful in numbers. Does anyone know how these pages that were

3396:

An addendum to my previous post, it would seem that enabling a permanent semi-protection would be hard to justify undoing later. Semi-protection should come in the form of a week (initiated by any admin), a month (initiated and seconded by another admin), or a 3 month period (initiated by at least 5

3364:

Because semi-protection could end up being a lot more permanent on some pages than mere protection. When a page is protected, there is a clock ticking where either a POV dispute or edit war is resolved, or a flood of vandalism is stopped. Semi-protection, especially on such pages as GWB, may become

3316:

How will semi-protection be applied to a page? Should it go through arbcom? A majority vote of at least X amount of admins (10-25)? Should there be a physical limit to the amount of semi-protected pages on Knowledge, such as 10-15? Should it simply be decided by the vandalism percentage rate? Can

3245:

Age of account certainly is an interesting proposal; however, I would still be concerned about the hindrance of progress in an effort to stop vandalism. Regarding the minimum threshold of vandalism — isn't the line between vandalism and non-vandalism be extremely ambigious with some edits? Who would

3209:

I think my suggestion above can prevent too many articles from being semi-protected. It would allow only extremely vandalized pages to be semi-protected, and it would set a time-table for un-semi-protection. The number of admins and highly experienced users leaving recently has convcinced me that the

2447:

I agree with Katefan0, that it hurts our image, but I also agre with Splash that we should keep this as wiki-like as possible. The problem is, however, I've seen many good websites bust because of issues within, and I think we should, first and foremost, not make us look like jackasses with images of

2359:

Get more good editors, and give them a rollback button. Outweigh the vandals by demonstrating that anyone can fix the problem in a matter of seconds. Setting up admins as ad-hoc committees for editorial approval leaves us wide open to charges of censorship that would be hard to defend against, apart

2271:

We shouldn't worry too much about journalists ranting; it's what they're paid for and, as Dbachmann says, they haven't really 'got' Knowledge. To Katefan0's specific point, no, I don't think we should give people a "Wiki sucks" first impression and to that extent we should be sure to speedy the worst

1881:

Semi-protection could be temporary right? It doesn't say on the project page, but I would think that it would be an ideal tool against vandalism. Instead of doing vprotect, we could put semi protection on for a day or so until the threat ceases. That way, constructive edits could be done. I don't see

1708:

Should be done without a vote. Votes are evil. Semi-protects should be determined by admins just like regular protected pages. Different levels should exist (as proposed), instead of the un-wiki idea of complete protection, a limit on how much newbies can edit will increase stability on pages such as

1353:

I would urge caution and light-footedness over this. Protection == unwiki == bad. Protection with new algorithms controlling it...I see what BD2412 is driving at, but we do want to retain the element of admin discretion. The admins are a fairly dim bunch at times, but collectively they manage more or

978:

Agreed with Kizzle, but I also understand Splash's concern, and I'm glad this was brought up at some point by a friendly editor, rather than a hostile one. Not all articles would be protected (I think I like the idea of only having a few pages protected, and have to pass a vote first), and this would

858:

and the POV status of many articles renders the Project basically unciteable. If those problems were hypothetically remedied, then the vandalism would be a scratch rather than a scar since people could still cite the article nearly all of the time. Increasing the protection level decreases the number

347:

should be subject to this sort of thing too, possibly with a very high edit count needed. It will stop 90% of vandalism to this page, and coming to Knowledge and seeing the first words on the page as an insult is not a good idea. However, there is a way for dedicated vandals to get round this problem

3572:

Well I would rather do it like we do the protection page. But...if you are looking for other ideas...Maybe require that 2 admins vote to un-semi-protect. The arbcom uses a voting system I like where they have a requirement of say...4 support votes...but every no vote takes away a yes vote. I can see

3562:

That's ok :) but keep in mind, we're developing policy here. Not everyone is going to treat it as you do, and allowing such variability when it is not needed (unlike protection) is detrimental and increases if not guarantees the possibility of protection creep. We need to assume that both the most

3548:

That's hard to answer. And no that's not a cop out. :) I say it because the admins have their own standards. Think of it as umpires in a baseball game. For some umps, a pitch can be called a strike by one umpire, but a ball on the same pitch by a different umpire. We have the same general standards,

3522:

You make some good points, but. :) I still say...let's start it with no time limits just to see how this works out. If articles are being routinely semi-protected beyond say...4 weeks...then we can change the policy and add time limits. I just don't think we can assume anything with a new policy. It

3507:

Seeing as semi-protection has observable benefits (no vandalism) and unobservable consequences (no valid anonymous driveby edits), you really can't see a temptation to leave certain pages semi-protected for a long period of time? Setting semi-protection for pages that engage in endless edit warring

3491:

I just don't see it that way. I don't see why semi-protection would need time limits. I don't think we can assume anything. I don't think we can assume that it will be permanent. Like with the Bush article. I think it's more likely that the page will be semi-protected for a few days...it'll be taken

3477:

Keep in mind the reasons for protecting and semi-protecting a page when you talk about time limits. Protection generally occurs when there is a POV dispute or an edit war, of which both are observable within the talk page. Some POV disputes may last weeks (as in our good friend Rex at John Kerry),

3443:

Here's something that confuses me. We have...no protection, semi-protection level 1, level 2 and then protection. Why can't we just have 1 semi-protection level? It would decrease the possibility of creep. I don't see why we'd have to split semi-protection into 2 when really, full protection is just

3386:

Lets be honest: vandals are not going to give up soon. So much of vandalism comes from drive-by vandals that they will never be discouraged by a previous semi-protection notice they never saw. I'll wager you a beer that if semi-protection gets enabled, that after a month of semi-protection, within

3159:

I know several users that I have talked to would probably not have joined if the first article they tried to edit was restricted. I'm also worried that the increasing proposals to restrict editing will slowly but surely chip away at the spirit and freedom of the Wiki. What's to stop all the articles

2133:

If semi-protection is implemented, we definitely need to provide some sort of communication to our editors what the terms of the semi-protection are. I wish that we communicated something more definitive to newly registered users who wish to move pages as well, but we do not. As to which is worse,

1609:

I know this has been attempted before (I'm guessing a number of times), and has failed every time, but I'm hoping this could be pushed to the front well enough that it will finally become policy. We could have dealt with this back in july, but we didn't; if we had, maybe we wouldn't have had to have

1549:

This is partially in response to Splash's post. You know what? I'd much rather have a high profile page protected than to make people look at multiple pictures of penises, which is something we got hit with last night. And I don't get this attitude about the vandalism room in IRC. Because people are

483:

Again, you ask a good question. I do not believe this is the case, as the only threshold is edit count, an arbitrary number. There will be no requests for permission. We do not have (m)any problems with admins fighting over protected page content, and I doubt this will be much diferent. The point of

471:

has proposed we limit the editing of these pages to registered users (see the GWB talk page). I, for one, am having mixed feelings over this; I think it might solve your issue, but is it truly what we're aiming for here? Again, the purpose of this policy is not to eliminate vandalism completely (and

3879:

If you are a good anon, 25 edits is not hard to get, and it is only on a few of 800,000+ articles until you build up the edits on your new account. Also, IP edit histories naturally build up from random users over time, so we should not try to include IPs here, this on top of all of the AOL issues,

3430:

This being protection creep (of the first kind: only ever upwards), there should be a means of de-creeping, too. I have no particular suggestion that doesn't result in the creation of protectionism, unprotectionism and nonprotectionism, but I'm just pointing out that we need a way down as well as a

3278:

I'm for this proposal in that its spirit is to block blantant vandalism only...Having certain articles editable only by aged accounts would curb a LOT of the major acts of vandalism taking place everyday. Even if the age was low, say 3 days, that would still help. Heck, even if it is nothing more

2921:

BD2412, could you please tell me what defines a latest wave? There are waves of vandalism on GWB, there is also the thick background noise of vandalism, and the two have little to differentiate them except volume. I think it's a constant issue, and will not let up, so why pander to them? Why coddle

2667:

I think Katefan hit the nail right on the head by saying "is Knowledge's ultimate purpose to be a wiki, or an encyclopedia?" Which are we more aiming for? The wiki idea is great, but it is not infalliable. We must be more of an encyclopedia than simply a wiki, as that is our purpose here. I believe

2407:

Sorry, Splash, we agree on lots of things, but this one isn't one of them. Last time I checked, throwing admins at the problem didn't solve the issue at hand: that we're wasting valuable time in reverting vandalism that we could be using improving the encyclopedia itself. While I sometimes do spend

2285:

Don't you think this is slightly missing the point? Splash and DBachmann suggest we should ignore media criticism "because they don't get the point" of the wiki-way -- but is Knowledge's ultimate purpose to be a wiki, or an encyclopedia? Which mandate reigns? The wiki format is a means to an end

2207:

Knowledge's reputation as a reference is very low anyway. Few articles cite their sources properly, and any high-profile article usually has serious issues of POV. Then, of course, the editors here are, for the most part, non-experts. Vandalism doesn't reduce the reference value of the work because

1418:

Short-term protection would not be so complex. Long-term would require a discussion and admin/experienced user vote. Short-term would work like regular protection, and be undone in about a week, while long term would stay until a big event, or high visibility passes. This is the major difference, I

1229:

Agreed. Protection creep doesn't have to happen, but it might happen. I personally would hate to see Knowledge become unwiki, but, like others have said, "Which is worse?" I don't think a new user will care or notice that they can't edit the one page. (Somebody) makes a good point in discussing the

1201:

I'd agree with IronDuke. I mean the thing is, this would be limited. We're not talking about having 10-15 levels of editors. I don't personally want that. I don't think anyone does. But IronDuke makes a good point. We already have admins, bereaucrats...you could argue that people on the arbcom have

956:

I wasn't being whimsical. The problem if we don't have some level of protection, then we'll burn out more people. The Bush page literally gets 30+ vandal hits a day. Talk:Main page is up to 10+ a day. I don't think you quite understood what I was saying. I don't see the harm in limiting access to a

562:

Yes, this would apply only to those with newly registered accounts. I propose using the same time limit or aging formula that we use for allowing page moves, which I believe amounts to a few days. Does anyone know the exact formula used for allowing new users to move pages? I have been unable to

3780:

Anonymous contributors probably shouldn't be allowed to edit semi-protected pages anyway. Requiring them to register before editing semi-protected pages does not significantly reduce their freedom because registering actually makes them more anonymous if they choose not to reveal their real names.

3686:

I understand. But. One thing to consider is something I mentioned up above. We literally only have 3 admins doing the protection page right now. We're going to have to set up a committee or require a "quorum" of admins present to perform functions or something because otherwise there will be times

3455:

I think there should be two, because in some cases, a 10 edit requirement is enough to combat vandalism and help new and anon users as well, whereas in some cases, like GWB, 100 should be used. We can even require that 10 be tried first, and if vandalism continues, upgrade to 100. As for Splash's

2219:

Splash, I agree with you philosophically on many things here, but on this we part ways. I can't believe that the answer to point one is "lots of people already think we suck, so we might as well just continue to let them think we suck." ESPECIALLY when Knowledge starts to get media coverage like

1959:

It is very possible to do this; many wikis using MediaWiki software indeed do make registration a requirement for editing. However, one of the main points of Knowledge is that all people can edit it, without having to register. There are many anosn who are good editors, perhaps just coming here to

1017:

I think changing semi-protection should even be harder than page protections, it should be decided by a certain amount of people, arbcom would be ideal, a certain majority of admins if not arbcom. As long as we stick to only enabling semi-protection changes through a lengthy due process, we avoid

3994:

One suggestion, maybe if instead of just showing view source on the top like normal protection, it still says edit page for those who have an edit count under the threshold. Then, if this person clicks on edit this page, it will give them some kind of friendly error message saying this page is a

3512:

POV disputes and edit wars should still warrant page protection until the dispute is over, which could last anywhere from a day to several weeks. However, since semi-protection deals with vandalism, there is no visible evidence to warrant un-semi-protecting a page. This will simply be the case,

2371:

I agree with Splash's concerns. I am not a big fan of locking pages and consider it unwiki...but, the page has been locked in accordance with procedure so there is no violation in that respect either. I also agree that if we do develop this semiprotection feature, it must only be used in the most

1183:

I'm going to go out on a limb here and say I actually favor protection-creep. I have been watching the Napoleon page and, because of his rather high historical visibility, there are many defacements of the page every day. Despite people's misgivings about keeping wikipedia editors all on the same

1035:

I have major objections to this. The arbcom is already bogged down in alot of difficult cases. I don't see where it helps to give them even more to do. I'm not sure why semi-protection couldn't use the same page that protection does. We are very careful with what we give protection to and what we

649:

I appreciate the semi-protection solution if only because of this. Most vandalism is easily dealt with, but Knowledge is one of the world's most visited sites, and George Bush must be one of the most read articles. Just imagine a first-time visitor whose first impression of Knowledge is seeing an

629:

I consider the 28th to be a typical day in the life of this article. In fact, there have been much worse as I recollect numerous IP's blocked during a true attack day. I will be willing to concede that much of the reversions are quick, in far less than a minute, but in one case, the page was in a

518:

If an edit threshold were to be imposed to registered users of a proposed "semi-protected" page, it should be a relateively low number, 100 or below. Personally though, I would prefer we stay in line with how we limit page moves to newly registered users (and prevent page moves from unregistered

330:

After reading most of the discussion on this page, and myself reverting GWB more times in the last several months than I care to count, I support this policy. Personally I prefer about 50 edits for edit capability, but 25 will do. Implementing this will make the GWB article usable again; right

4349:

I think leaving the threshold up to the individual admins is a very bad idea, we could get anywhere from 5 to 500 edits minimum. What guidelines or policies would we provide admins as to how many edits they should require, keeping in mind that setting the bar too high will result in unnecessary

3584:

I just realized I didn't answer some of your questions. :) As for criteria, there are a few we can use. First of all, we can look at the talk page. What's happened with Talk:Main Page is that because the main page is protected but it's talk page has not, the vandals have vandalized the talk page

3250:

the semi-protection worked out, I would support just a general guideline advocating when to semi-protect, similar to the guidelines we have for protection now. However, I still am concerned about the blocking of progress in an attempt to stem vandalism. Of course all vandalism won't be stopped —

3150:

included) do get a large amount of vandalism, that shouldn't be a reason to hinder progress. Progress on making an article better shouldn't be sacrificed or hindered just for the sake of attempting to prevent vandalism. In my opinion, setting arbitrary edit thresholds for editing very public and

1384:

we need to urge caution over this. That's why we will have a lengthy process to change semi-protection status that requires multiple admins, if not arbcom. The goal is only to semi-protect about 5-10 pages on all of Knowledge, if even that. But I'm sorry, protection does not necessarily equal

1115:

The difference, I see is that with full protection, we have almost no articles or pages that have been protected for a long period. I think that the advantage of semi-protection is it makes longer term (semi-)protection possible, but not neccissary. Short protection can be decided on by a single

875:

If we only allow changes of a page's semi-protection status to run through either arbcom or an admin-only vote, then we don't have to worry too much about every page getting protected left and right. Semi-protecting a page should become a huge deal with only the top 5-10 pages out of the entire

3538:

For the example you give, it is the sockpuppetry which warrants semi-protection, as I consider sockpuppetry a form of vandalism. We can test it out for a month and see what happens, but I'd like to hash out as much as possible to get it right now, so that it has less of a chance of failing and

2672:

credibility (or lack thereof) or its ability to revert vandalism quickly. No; to an outside user/journalist, vandalism is vandalism, no matter how quickly it can be reverted. I am saddened to see the spirit of the wiki die, but we must prevent vandalism from even showing up, and thereby keep or

2323:

One other point to DBachmann -- you suggest that "GIANT PENISHEAD" isn't as serious a vandalism as some other things a vandal could do, like introducing erroneous facts. I agree with that. But I think both are equally damaging -- if I saw something juvenile in an article I was looking at, the

2259:

You misunderstand something. There are often 50, 100 edits a day on that article - and often, 90-100% of them are vandalisms or reversions. My point? If there were unreviewed, unreferenced, false, or inaccurate statements, they'd be fixed in those 50-100 edits. They haven't been. Very, very few

3732:

OK. Well you and I seem to be making progress. Hopefully others will chime in now. :) Yeah an informal committee would be fine. We'd need something. I mentioned all of this because it hadn't been mentioned before. I'd love to say...hey...we're going to have 20 admins working on this around the

2481:

Three hours of vandalism per day on high-profile pages is a much more potent threat to Knowledge's "pool of new users" than semi-protection would be. After all, new readers would be likely never return to Knowledge if they were to find ridiculous statements such as those from GWB quoted above.

2053:

To me, the real question is a philosophical one. And that is -- which is worse: Someone coming to a vandalized article that says "George W. Bush, president of the United States, is a GIANT PENISHEAD!" and thinking "Man, this Knowledge sucks, I'll never use it again" -- or someone coming to the

4257:

Yep. And we can build it into the policy...something along the lines of...anyone who is doing that (creating a user account, getting their edit count #s up and then vandalizing the article) can be reverted (and eventually blocked) for doing so. It's not that hard to figure out...we do it when

4108:

I read the discussion up above (good discusion) and I just have some points. First of all, again, remember that semi-protection would NOT have to be permanent. It could be used on an ad hoc basis when its needed to stop vandalism. It could be on the articles for less than a day in some cases.

2240:

of people have GWB on their watchlist, so it is extremely unlikely that vandalism goes unnoticed. Hopefully the problem will go away by itself in another three years :) journalists who rant about vandalized article versions simply have not got what we are about here, so never mind. No serious

3115:

I'm not sure something like semi-protection should be decided on an automatic level. Caution should be exercised, possibly through multiple admins or arbcom, but setting some arbitrary limit doesn't seem to be the answer, as cases may come up that hit right below the mark that still warrant

1366:

Yes, but we need more weapons against vandalism and this would be another weapon. And as I said, take a look at the RfP page. We don't give protection liberally. We reject as many (if not more) requests than we accept. And this would be similar. The purpose of semi-protection is to help stop

4137:

Agreed with every point except for the conjecture that one day vandals will get tired of vandalizing GWB. After 5 years of being president, vandals have only gotten more determined than before, I highly doubt they will ever give up until he's out of office and a new douchebag is president.

2796:

When we have a system in place that can prevent the random vandalism from overwhelming the article - like the semi-protection under discussion, or perhaps bots that are smart enough to automatically revert the obvious things (deletion of large chunks of text, insertion of dirty words, etc.)

2119:

Considering that I'm reasonably sure more people view Knowledge pages than actually attempt to edit them, I'm personally more concerned with the former. I'm uncomfortable with the proposals about only letting registered users edit, but this sort of semi-protection policy seems like a pretty

743:

Yes, I've seen it done a number of times, and I love the idea of opening the main page to those other than admins. The great thing is that this isn't as harsh as full protection, which is unwiki, but isn't as bad as making us look like fools with these vandalism edits, and can be temporary.

299:

I support semi protection for certai articles like George W Bush to keep vandalism to a minimum. Another option, though I don't think it can be done, would be to have some sort of time delay as in have a administrator check (anonymous) edits before they become visible. Is that possible with

1589:

except to revert vandalism that occured just before protection and also some other very limited circumstances. And if we agreed to a semi-protection policy, we can pretty easily forbid admins and others from adding content that's proposed by people with less than whatever the threshold is.

3526:

And btw kizzle, I wasn't saying that just new users and anons can get into edit wars. I don't know if you know the Bogdanov Affair case, but essentially, it's an outside controversy...something outside of Knowledge. It's about 2 men who came out with some new physics theories. It's become

1398:

Question for you kizzle. Why would the semi-protection process have to be so much more difficult than protection? I ask this because protection only takes one admin. Semi-protection would actually be much less restrictive than protection. Protection now allows absolutely 0 edits...even by

3789:! Unfortunately, the MediaWiki software has no means of identifying anonymous users except by their IP addresses. People with dynamic IP's will just have to register if they want to accumulate edits or account age or even if they want to receive the correct messages on their talk pages. 797:

the scale. If it's only to be used when the vandalism has become a serious problem, there is unlikely to be a de-escalation short of e.g. a president leaving office. If the vandalism were serious but brief, then full protection for a few hours, as already available, would still be fine.

1276:

I'm kind of having difficulty deciding what the purpose of this is. I think this should start small and stay small, but it has some potential for as the wiki grows in scalability. For now, I think we should maybe leave it to high profile pages like GWB and others (only a few), and then

389:

feature which is quite similar to this. By freezing content in a special section of the site, they are planning on producing a stable version that can be cited and quoted. While the goals of the two proposals are different, perhaps cross-posting there would benefit this discussion?

3513:

that many pages become semi-protected long after an initial flood of vandalism. This doesn't mean it can't be semi-protected for longer, it just requires more of an admin concensus than a single person. If we don't set time-limits, then Splash's concerns will become a reality. --

268:

Agreed. We protect the front page, but under this, a user with a minimum of ___ edits can edit the templates, or change the front page, virtually eliminating the vandalism. Enough people have the front page on their watchlists (or see it enough) that reverting it would be easy.

129:- Knowledge slowly evolves to the next stage, with a core of "done" articles and lots of work on the fringes. It is a good idea to have a means of protecting that core. I trust that we Wikipedians will find a way to handle semi-protection in a responsible and working manner. -- 4385:

I guess the edit threshold and time limit could be built in as variable within the tool, and let policy (preferably as explicit as possible) be referenced by admins using semi-protection. That way, the time limit and threshold can be decided upon by a concensus from each wiki

3923:. Perhaps a template could be placed at the top of a semi-protected page's talk page with a link to a project page describing the possible reasons behind the protection, a sort of semi-protection policy. Alternatively, if we decide that a high vandalism rate is absolutely the 928:

also suffers a similar fate. What would be nice with semi-protection is that we could slap it on Community Portal too...and other visible pages that people should be allowed to edit but on the other hand, often fall victim to vandals. I like it...let's give it a whirl, I say.

3223:

will still be a problem, but many of the thousands of minor vandals that add stupid comments to high-profile articles might be deterred. Vandalism will still occur on "normal" non-protected pages, but semi-protection can help reduce vandalism considerably on such articles as

940:

There: protection creep of the second kind, before we even the ability. You must be ultr-careful about applying any level of protection to articles. It is not something that the community at large will support if it is applied in the rather whimsical fashion above. We do not

1610:

this discussion now. All we can do to prevent this discussion from happening again and again is get it passed now. Looking at the past pages, it doesn't seem like there was a real reason it wasn't implimented; only that there wasn't enough attention brought to the issue.

4112:

Secondly, to splash, just because people might enjoy RC patrol doesn't mean that it's a good thing. I mean if vandalism ceased tomorrow, I highly doubt that people would be too sad. I'm not sure how much RC patrol you've done, but it's very draining. We essentially lost

2503:, what more is going to take? I love this project, but not enough to put countless hours into fighting needless vandalism, and dealing with stuff I really shouldn't be dealing with. There is absolutely no good reason to allow this to happen: we must find a better way. - 472:

keep this as non-anti-wiki-like as possible), merely cut it down greatly. I don't mind reverting the page every once in a while, just not when it happens so often. We could always experiment with different types of protection, which is what semi-protection is all about.

4417:

Tito, before you claim an idea as your own, how 'bout taking a look at the main page ;). We've been doing so much talk about this on the discussion page (and frankly, it's huge), that we havn't really done anything to the proposal page. I guess great minds think alike

4184:

Yep. I totally agree. That's why I'm really going to bat for semi-protection. You're talking to someone who does RC patrol AND the RfP page. :) We really really need an intermediate step. Otherwise, protection is too harsh and having it completely open is too lenient.

3762:

Should the levels of semi-protection address edit count, or the length of time an account has been used? How do IP addresses factor in the previous question? How will AOL and other proxy accounts be addressed? Should there be more levels than simply 25/100, such as

2533:

Well, I agree with that point as well. Vandalism patrol can often mean lots of wasted wikitime. Some would argue that folks enjoy it and that makes the situation less desperate than it seems. Maybe that's true. Personally, I do vandalism fighting-related activities

1206:. We'd be talking about similar pages for semi-protection. We'd be talking Community Portal, maybe some of the higher profile templates...basically stuff that usually isn't changed without a major consensus anyway, so there isn't much harm in semi-protecting them. -- 3821:

I didn't realize that, I just thought it was minimum amount of edits. I didn't think we decided that already, you're saying if we have a legitimate anon editor with a static IP and over 500 edits, that person would be banned from editing any semi-protected pages?

2448:

penises and feces on our pages. We want to encourage new users, but a few pages that are high-profile that can't be edited immediately should not be a concern, they'll simply move on to another page, or maybe come back later to a different page and edit that. -

1948:

can contribute edits? I'm sure it's obvious to anyone that's ever had to revert an article, that the vandalism almost always comes from unregistered users. Just the usual thought that my penny can buy, odds are good I'll be getting change back from it. --

2134:

the first scenario obviously takes the cake. I am not convinced at all that we would damage our pool of users by protecting an otherwise highly trafficked and highly vandalised page such as this one. Were any users lost after the Main Page was protected

1518:

after reluctantly placing this under {{vprotect}}. I believe we both agree that this article needs to be open to well-intentioned editors, but on that same token we are equally beholden to our readers to present them with something more professional than

4117:

over it and we'll lose others, I guarentee you. I just don't like this idea of "well it sucks, it's always going to suck, so let's not change it". Just because it sucks now doesn't mean that it's right or that it's something that we can't ever change.

1997: 844:). Clearly, there will be a tendency to seek increased protection for better articles. This may not be a bad thing, and I am merely mentioning the point. Asymptotically, however, as Knowledge approaches completion, everything will be fully protected. 1573:

where he basically says that if somone wants a change, they can and I quote, "submit" it on the talk page. The idea that admins should have a content approval role is extremely distasteful and gives them a role they were never considered for in RfA.

3374:

I don't think that Bush would need it permanently. I still think that the vandals would be discouraged by semi-protection so that maybe it would be lowered to the point where it would not be needed. I'm not sure it'll *ever* be needed permanently.

2644:

When it comes to "being a wiki" vs. "credability", obviously, I will go with the later. Also, we will loss many possible users if they say penises all over the article they first come up upon. ALso, this issue is causing the loss of current users

1534:

I've crossposted this here because it raises valid concerns on what to do in the interim while a semi-protection policy is being hashed out and discussed. When is it appropriate to use the current vandalism protection feature with regards to the

1960:

look up a topic, but seeing a typo and wanting to correct it without having to go through a registration process. I am positive that making registration mandatory will never happen as long as Jimbo is still an active personality in Knowledge. -

2627:

Fundamentally, wiikipedia needs to decide if it wants to be a useful and relatively reliable encyclopaedia using a wiki format, or a wiki posing as an encyclopaedia – but actually being a graffiti wall and a dump for all the world’s unverified

475:

Anon IPs are where you, me, and nearly everyone else got their start, I believe. While it is more desireable to have registered users, sometimes usernames can be mass-created, making it very difficult to stem their vandalism. For more, see

3849:

One thing to consider, how will AOL proxies factor in the edit count? Since AOL IP addresses are used by multiple people, won't some AOL vandals be able to get over this requirement if many people have edited before on their ip address?

2616:

In short, it's not the end of the world when people leave Knowledge, provided they are replaced with "fresh blood." On the other hand, where there are systematic problems causing many people to leave, that's something we have to address.

2054:

article, not being able to edit, and therefore not getting addicted to Knowledge enough to become a regular contributor? Which is worse? Damage to Knowledge's reputation as a reference work, or damage to Knowledge's pool of new users? ·

2420:

the credibility-as-an-encyclopedia problem, we need to take a first step. Perhaps fixing the POV and citation problems of other articles is more needed, but that does not mean that those needs and this proposal are mutually exclusive.

2066:

It seems obvious that the first situation would be worse. If the person would really "never use it again," then he would not be editing anyway. At least not being able to edit one article would not ruin the credibility of Knowledge. -

455:-Will availability of different levels of protection start off wars within editors of each high-profile page, each editor asking for a higher or lower level of protection, thus diverting our efforts from editing, our primary task?? -- 2673:

restore our credibility. The wiki format is not yet mature enough to defend its practices. What is the disadvantage between semi-protecting an article for a short period of time v.s. full protecting? Keep in mind this is not for for

3733:

clock...but we won't. Alot of it isn't just that admins don't like doing it. Alot of it is numbers. Yes we have 700 admins but we have lots and lots of projects for them to work on. RC Patrol, ArbCom, mediation, etc, etc, etc. --

3397:

admins). Thus, if it truly needs semi-protection for longer, it simply can be "renewed" every 3 months. In addition, semi-protecting a page for a week more than two consecutive times requires the consent of 5 admins as well. --

3279:

then Requiring any account to edit would help. While of coure any current vandalism IS removable by anyone, it takes diligent editors to remove it as soon as possible, thus keeping the encyclopedia as accurate as possible,

2624:

has left now, and part of his departure message is very clear: there is a systematic problem with Knowledge that is driving off way too many editors (especially points 2 and 6), and I couldn't have said it beeter than him:

2570: 2241:

criticism of Knowledge would even mention vandalism as obvious as "GIANT PENISHEAD" as an issue. Knowledge's value is degraded much, much more by unreviewed, unreferenced false or inaccurate statements on obscure articles.

1340:

One problem we're going to run into is that even the protection page doesn't have hardened "rules" like that. Not sure how well that's going to sit with some. Everything we do on WP:RfP is through very informal guidelines.

1486:

There have been several recent cases where this page, the most highly vandalised and watched page on Knowledge, remained vandalised for over one hour and fourty minutes, as originally pointed out by Rhobite in October.

449:-Anon IP edits - some of the anon IPs are dynamic, some are shared by many users. e.g. AOL, University IPs. On a given day, some of the more high-profile IPs would contribute 25 edits in a day. How would we deal with it? 2708:

You see the spirit of the Wiki die. I will oppose permanently any policy or technical change that causes that to happen. Knowledge's purpose is to build an encyclopedia using the Wiki method. The two are non-separable.

719:

THis solves a lot of problem, IF and only if we as users can easily getadmins to mark pages as semiprotected. Many times vandalism comes in the form of people shipped from other forums to edit wikipedia to push a PoV.

979:

aid us in our push to 1.0, by freeing up resources that used to be used on vandal fighting (admittedly very tiring), to be used to edit articles and such. Long-term semi-protection would be decided on at a page like

1894:

Yes, I like that idea a lot. This way, the vandalism will subdue, while still allowing good edits. The semi-pro can be removed as is done with regular full protection. I think this would probably be the best idea.

3232:. Legitimate users with the tenure required to edit semi-protected articles will be much more productive with the resulting coherent history pages for the articles, most of which are critical to Knowledge 1.0. -- 4281:. Instead of having two or three protection levels set at a fixed ratio, how about there is just one level (semi-protected), which then can be set individually? It would be similar to the "Other" selection in 840:— Articles are not equal, and they are not created equal. See the various stubs compared to the Featured Articles. At present we have these 3 levels of articles: stubs, normal and featured (and putatively, 1716:

This should not be seen as promoting some sort of elitism, in fact its the opposite. Pages that otherwise would be protected (admin only edits), would with this stay editable even though with limitations.

2310:

Ah, now that's a more persuasive argument. However, it is our only means to the end. We don't have another one available without becoming Britannica. Closing it off should be done only in emergency. -

3909:

Should there be a notice of some sort notifying people that the page is semi-protected? If so, how should the message be crafted without inferring illegitimacy within the text, such as NPOV tags? --

1059:

It doesn't have to be arbcom, maybe just a certain minimum amount of admins voting on it, as semi-protecting a page is too powerful in my mind to be left up to the discretion of a single admin. --

893:

I agree with Kizzle. As one of the people who has had to keep reverting on the GWB article lately, it does get annoying. It would be silly to not do something about this when we have the chance.--

1845:

I asked a little while ago about Bugzilla, and was told to wait. I'm not sure if this is the right time, but if someone (possibly me) could ask the devs in the IRC channel, it would be awesome. -

1613:

I'm not feeling well, and I thank those of you who have been editing the proposal for my grammatical and spelling errors (they're showing in my off-wiki work too...). Thanks, and happy editing.

902:

Agree with the above - vandalism fighting takes time away from other improvements. Let's at least experiment and see if this proposal makes the positive difference that many of us anticipate.

1735:

of full protection? You may have a point...Full could be replaced with 500 or 1000, which is basically admin-level. It would have a tag like full protection, but not just admins could edit. -

3353:

As I asked you above kizzle, why would the semi-protection process, which is far less restrictive than protection, have to go through a much more restrictive process than protection does? --

3176:

expect articles, especially high-profile ones, to be protected, even if it's semi-protection. Thus, in my opinion, we shouldn't sacrifice progress in an attempt to hinder vandalism. Thanks!

1230:

Main Page. We will not drive off a new user perminately because they can't edit a few pages (again, we're talking about a small amount here), but we might, and probably will, if they see

3116:

semi-protection. In addition, what you'll get on moderately vandalized pages is legitimate users vandalizing the page in order to get to the semi-protection threshold, I guarantee it. --

1503:

So, while vandalism may be reverted within 1–2 minutes, it is rather moot when the article is being attacked every other minute. The decision to temporarily protect this page was made

452:-Would the above give a new user an incentive to be an anon IP user rather than a registered user? imo, registeed users are more desirable to the project, so this needs some addressing. 4065:

Good idea. Also, new users would realize that only a few pages are on the list, and that they can edit the other (6,889,528 minus the number of protected pages) pages on Knowledge. --

622:

The subject of the article is called a "Bastard", "co%ksucker", "Dumbass" and "Hitler", to name a few, all within the article text. We also have this fine edit summary by an anon IP:

3129:

Never mind my idea. I think admins can be trusted to use good judgement when semi-protecting pages. They won't protect too many, and they'll unprotect them when it is appropriate. --

1149:

I'm no developer, but I think it is. I agree that we should be trying to unify editors as much as possible, but some content should at least be given this (maybe 10 pages at most). -

1523:, or much, much worse. If you have any suggestions on how to better deal with distributed vandalism attacks such as the one made earlier today, please let me know. Best regards, 4147:

We won't know until we try, now will we? :) I dunno. I understand your concerns that we need to have a consensus for long term s-p. I just want this to pass. It's my main goal. --

2013:

wrote a great essay on the subject, that, at some point, we were all newbie anons. Knowledge is a great way to launch into wikis, so we have to be the best one out there. -

1234:

on pages. Even the "____on wheels!" stuff would probably not bother a new user too much, even though it bothers us. We simply must have a better way of dealing with this. -

3995:

frequent target for vandalism, but that many other pages are available to edit, so that it still encourages those newcomers to remain and simply edit a different page. --

3793:

I don't think there should be more than one level, at least until the system is tested. We're not planning on using semi-protection on a lot of articles, only a few. --

582:

The proposal notes that GWB is vandalised for "hours a day". This probably is a bit of exaggeration, although my data suggests that at worst it could be an hour a day.

4047:

of the semi-protected pages (of which there should only be a handful) so our prospective editor does not jump right to another one closed to his or her contributions.

2964:

We could revoke permission to edit protected pages (this gets a little complicated) but would prevent people from abusing the semi-pro part (e.g. a vandal warned with

2191: 1799:

s with proposed changes at the bottom, which can be rejected or accepted, (far off in the future, that is, when we're much more complete, but may be useful for GWB). -

880:

on pages like GWB, it has crippled the page so that it makes it incredibly hard to view the progress of the page when the history consists of 90% vandalism/reverts. --

3831:

Yeah I have that same question. I don't like that if that's the case. I mean some of our anons are good users. They are far outnumbered by the vandals, but still. --

79: 71: 66: 4109:

Honestly, I'm not sure it'd have to be permanent for Bush. I mean, I can see a day where vandals get tired of not being able to edit the page, so they give up.

223:

I strongly recomment a minimum of 25. I have watched vandals and they can easily rack up the ten needed to hit a major page and damage more user's view of Wiki.

3861:

not willing to do that, then you shouldn't need to edit an SP'ed page. (Anons will still be able to edit most pages because only a few pages will be SP'ed.) --

1982: 410:

Which is the best level? 10 or 25? 50 or 100? More? Should there be more levels, more incriments of protection? Is it good the way it is? Is this feasable? -

4206:

I added the alert at the top because I'm not sure everyone here (especially the non admins) know the existing policy and tags. I thought it'd be helpful. --

1674: 3308:

Lets focus for a second on three things which really haven't been resolved yet that are irrespective of whether one believes in semi-protection or not...

2767:

Until 2009? No. Full protection is evil. But we can try to find something to cut down on the vandalism already occuring, and this proposal fits the bill.

1312:

Don't know if there's a way to work scalability into the system, but I'm thinking that we can limit protection to pages that are vandalized an average of

361:

Just to let you know, if we enforce a minimum amount of days the account has existed, as in 5 days or a month, it should warrant off most vandalbots. --

4161:

I just range-blocked an entire University for GWB vandalism. The attacks were coming way too fast over several proxy servers, so I had no choice. Now,

813:— Wiki is not prophylactic, it does not usually defend itself against imagined threats. This is to keep things as nearly free-as-in-speech as we can. 348:- vandalbots that can clock up a lot of edits, and then quickly go on to vandalise this page. It's not that hard to create a vandalbot. Nevertheless, 4359:

It would not be leaving it to admins' individual discretions, there would be limits set in the Semi-protection policy, similar to the ones at the

2606: 786:

Let me give this a grilling, in the traditions of...well...grillings. It's important to beat new concepts up a bit to be sure they are robust:

3870:

If it will be a problem to semi-protect through an edit count against anon AOL ips, then I agree we should enforce only logged-in accounts. --

2088:

Could semi-protected pages come with some kind of disclaimer explaining why the person wishing to edit can not work on that particular page?

1498:

article is now being vandalised to such an extreme that, on average, the article is effectively in a vandalised state 8% of any given time.

1491: 331:

now, because of the extraordinary number of vandalisms and reverts, it is impossible to follow the evolution of the article in the history.

47: 17: 3321:? How will the enabling of semi-protection as said affect the request protection page? As Coffee talk lady says, Tawk amongst yourselves. -- 3196:

What do you think about the proposal to, instead of going by edit count, by age of the account? Similar to what's done with page moves. ·

2360:

from simple protestation. Possibly, and only possibly, semi-protection is a solution to that. Full blown protection for 4 years isn't. -

2408:

time reverting vandalism "just for the heck of it", I do not think it is the most efficient way to address the problem. I know that if

1772: 386: 2677:

article, and will be tightly controlled. I just cannot sit back and watch GWB become vandalized 80 times a day. There is no excuse. -

4223:

Since this policy is simple to get around (have fun elsewhere to whatever level required, then you can vandalize whatever you want)

4326:; having a customizable level allows the different Wikis to adopt a semi-protection policy more suited to their individual needs. 4165:

is something that will irritate potential editors—being blocked—and I wouldn't have had to do it if the page were semi-protected.

1835:

if anyone knows how to do it, can they post the link to this page on the wikipedia mailing lists, along with bugzilla? Thanks. --

3098: 1506:

while the article was in the process of being simultaneously attacked from multiple IP addresses, meeting my interpretation of

4121:

Thirdly, this isn't as severe as I think people are thinking it is. #1 we would not be talking lots of articles here. Look at

3289: 2208:

it is so low anyway. Thus, the risk in protection is people not being able to edit the encyclopedia...that anyone can edit. -

650:

article on George Bush calling him a "cocksucking bastard" - which wouldn't even be among the worst the article has endured.

816:

An article is greenlighted on Slashdot. At present, we'd just revert the trolls. But why not use, say, level 3 protection,

2745:

As our popularity grows, so will vandalism - I fear that the time is not far off when this article (unless protected to

2000:. Knowledge is experiencing exponential growth; I wonder what the outcome of that poll would be two years from today. 3919:

Good idea.... Well, when a page is nominated for deletion, the template placed on its talk page contains a link to the

1663: 1514:

is open for debate after a review of the protection log, but please do note that I specifically requested that someone

2148:

I agree with Kate, and with BD (I've been invisining some idea along those lines, or maybe just like we have now with

1586: 1507: 3478:

and some may last a day. This variability requires the length of protection to be fluid to adapt to the situation.

2479:"Which is worse? Damage to Knowledge's reputation as a reference work, or damage to Knowledge's pool of new users?" 624:

GEORGE BUSH LOVES TO ASSFUCK PORN DEALER WALES AT *(deleted Jimbo Wales address)* CALL HIM AT (delete#) FOR A RIMJOB

3160:

from being semi-protected like this in one month, two months, or three months? Anyone - regardless of edit counts,

1985:. It is a Foundation issue that will probably never receive support from either the Board, the community or Jimbo.- 1135:

Is this even technically feasible? And if so, shouldn't we not be trying to create a bunch of levels of editors? --

876:

article space being protected, and would have gotten there through some kind of due process. Regardless, Vandalism

189: 160: 38: 2585:

reason for continuing here, and I support semi-protection because it might play a part in correcting that flaw. --

2221: 1650: 169: 4360: 4232:

since moving draft edits to the published page will be less work for admins than the reverting of vandalism today

4122: 3945: 3930: 3920: 3161: 1480: 1464: 242:

I believe that we have to assure users that this is just supposed to be used in our most-vandalized pages, like

3164:, country, or IP address should be able to edit Knowledge. Finally, I've seen some analogies above to when the 1141: 382: 2335:

We're not as far apart as you think. That's more a less the statement I wrote some time ago on my user page. -

4451: 4404: 4395:

Yes, the policy should be implemented in each Wiki as clearly and explicitly possible, on that we do agree.

4390: 4372: 4354: 4343: 4264: 4252: 4240: 4212: 4191: 4174: 4153: 4142: 4131: 4087: 4069: 4060: 4038: 4029: 4011: 3999: 3984: 3962: 3939: 3913: 3894: 3874: 3865: 3854: 3837: 3826: 3816: 3797: 3767: 3739: 3727: 3693: 3659: 3625: 3579: 3567: 3555: 3543: 3533: 3517: 3502: 3486: 3472: 3460: 3450: 3437: 3413: 3401: 3391: 3381: 3369: 3359: 3348: 3325: 3293: 3265: 3236: 3214: 3202: 3190: 3133: 3120: 3109: 3068: 3054: 3039: 2999: 2935: 2926: 2882: 2839: 2821: 2810: 2791: 2776: 2762: 2740: 2729: 2715: 2702: 2659: 2639: 2589: 2544: 2528: 2494: 2473: 2430: 2376: 2366: 2354: 2341: 2330: 2316: 2303: 2292: 2278: 2264: 2254: 2229: 2214: 2201: 2177: 2141: 2126: 2114: 2110:

Kate, how many times do you think the former will happen as compared to the latter? BD, I like your idea. --

2101: 2083: 2060: 2038: 2004: 1991: 1976: 1953: 1931: 1920: 1888: 1870: 1839: 1824: 1783: 1760: 1725: 1702: 1638: 1596: 1580: 1556: 1543: 1527: 1473: 1444: 1405: 1389: 1373: 1360: 1347: 1333: 1306: 1259: 1212: 1188: 1174: 1143: 1090: 1063: 1042: 1022: 1008: 963: 951: 935: 915: 897: 884: 869: 769: 726: 706: 669: 654: 634: 601: 589: 567: 557: 523: 509: 459: 435: 399: 365: 356: 338: 325: 322:

25-50 edits before editing a semi-protected page would be a good idea. I support the semi-protection policy!

317: 304: 294: 263: 237: 203: 192: 178: 163: 148: 133: 121: 4292:, since you would be passing down a variable into the MediaWiki software, which would then be processed as 2720:

Right now, the only alternative we have is to completely protect an article, which is even more anti-Wiki.

4066: 4035: 3936: 3882: 3862: 3804: 3794: 3774:"Should the levels of semi-protection address edit count, or the length of time an account has been used?" 3233: 3211: 3130: 3106: 2647: 2586: 2491: 468: 225: 3968: 3949: 820:

things get serious? At present, we'd maintain the Wiki-way and let people edit it, and slap the vandals.

3971:

is a good model (as the page would only ever be semi-protected, or perhaps Sprotected, for vandalism).

3339:

or some other place that is visited often, but ArbCom is too busy to deal with these sorts of things.

983:. Short-term semi-protection can be used at an admin's descresion, much like full protection is now. - 4446: 3257: 3182: 3034: 2994: 2697: 2523: 2468: 2172: 2033: 1915: 1865: 1819: 1755: 1697: 1633: 1439: 1301: 1254: 1231: 1169: 1003: 764: 701: 678: 552: 504: 430: 289: 2412:

had seen "GEORGE W BUSH IS A FUCKHEAD" or something like that the first time I visited Knowledge, I

532:

What do you propose the time limit be? Is this only for registered accounts (I agree, by the way). -

4399: 4367: 4338: 4169: 4024: 3343: 3063: 2771: 2734:

We've lost the point of this thread. It was: should GWB be protected from now until 2009. Yes/no. -

2724: 2634: 2425: 2246: 2081: 1974: 1721: 1570: 1136: 666: 394: 335: 258: 3935:

It's short and to the point, but readers could find out more information by following the link. --

4226:

since having a protected "published" page visible will never be vandalized (unless admins go bad)

3953: 724: 3510:

only reason for semi-protection to be applied to a page is to combat cases of extreme vandalism.

924:

will also appreciate it because we're kind of tired of rejecting requests for the Bush article.

3155:

turn to the high-profile pages. Potential users, on the other hand, will be deterred by this -

4315: 3802:

You have to be logged in for any kind of semi-protect anyway. So this is not much of an issue.

3220: 2138: 2001: 1540: 1524: 564: 520: 4259: 4207: 4186: 4148: 4126: 4114: 4082: 4055: 4006: 3979: 3957: 3832: 3734: 3688: 3620: 3574: 3550: 3528: 3497: 3467: 3445: 3408: 3376: 3354: 2877: 2834: 2805: 2757: 2621: 2096: 1950: 1926: 1883: 1780: 1591: 1551: 1419:

see. The point of this is to be more wiki-like with protected pages than we are currently. -

1400: 1368: 1342: 1328: 1207: 1085: 1037: 958: 945:

on anything. Why? Because of protection creep of the first kind, and the permanence of it. -

930: 910: 323: 859:

of people who can work on making the article so good it rises above the level of vandalism.

4441: 3493: 3252: 3177: 3029: 2989: 2692: 2518: 2463: 2167: 2028: 1925:

OK. I'll alter the proposal a tad since right now, it doesn't mention this possibility. --

1910: 1860: 1814: 1750: 1692: 1628: 1434: 1296: 1249: 1164: 998: 759: 696: 665:

I think it is unfair that only admins can edit the Main Page, this is a good alternative.

598: 586: 547: 499: 456: 425: 284: 2826:

Well, try it now. Maybe the latest wave has been capped by the protection to this point.

3172:

a high-profile website's front page to be locked — besides, it's not an article. People

3318: 3229: 3225: 3147: 2782: 2300: 2242: 2074: 2069: 2010: 1967: 1962: 1710: 1670: 1536: 1495: 980: 802: 641: 477: 332: 301: 243: 187: 158: 4427: 3015: 2975: 2678: 2504: 2449: 2153: 2014: 1896: 1846: 1800: 1736: 1678: 1614: 1420: 1282: 1235: 1150: 1084:

So I assume you feel that way about protection too? That also just takes one admin. --

984: 745: 682: 681:, would take the time to garner 500 or 1000 edits simply to vandalize the main page. - 619:

a total time of almost exactly 3 hours in which the article was in a vandalized state.

533: 485: 411: 270: 4432: 4282: 4278: 3284: 3210:

current attitude towards vandalism is not beneficial to Knowledge in the long run. --

3197: 3146:

I'm kind of concerned about this proposal, to be frank. While admittedly some pages (

3020: 2980: 2683: 2562: 2539: 2509: 2454: 2325: 2287: 2224: 2196: 2158: 2121: 2055: 2019: 1998:

Knowledge:Disabling edits by unregistered users and stricter registration requirement

1901: 1851: 1805: 1741: 1683: 1619: 1425: 1287: 1240: 1185: 1155: 989: 921: 750: 721: 687: 608: 538: 490: 416: 375: 275: 1367:

vandalism. It wouldn't be used for edit wars as far as I can see. Just vandalism. --

3619:

it harder than before. We've had it happen on the protection page several times. --

3336: 3090: 2485: 1203: 894: 851: 841: 314: 2974:/multiple-blocked vandal/editor who edits a (temporarily) semi'd page. Thoughts? - 3387:

a week of removing it, vandalism will be at least up to 75% of what it is now. --

563:

locate a precise answer on this, but it seems to be approximately 5 days or so.

4396: 4387: 4364: 4351: 4335: 4247: 4237: 4166: 4139: 4075: 4048: 4021: 4005:

Sounds good to me. Whether the wiki software can do that is another question. --

3996: 3972: 3910: 3871: 3851: 3823: 3764: 3724: 3656: 3564: 3540: 3514: 3483: 3457: 3432: 3398: 3388: 3366: 3340: 3322: 3117: 3086: 3060: 2968: 2923: 2827: 2816: 2798: 2786: 2768: 2750: 2735: 2721: 2710: 2631: 2566: 2557:? There's still a glimmer of hope in that word. Hopefully her break will not be 2500: 2422: 2361: 2351: 2336: 2324:

entire rest of the article, to me, would immediately be suspect. Same effect. ·

2311: 2273: 2261: 2209: 2111: 2089: 1986: 1836: 1793: 1776: 1575: 1468: 1386: 1355: 1321: 1060: 1019: 946: 903: 881: 864: 855: 651: 391: 362: 353: 255: 198: 173: 143: 46:

If you wish to start a new discussion or revive an old one, please do so on the

2561:

She has apparently left becuase of the editcountitis epidemic that is sweeping

4017: 3051: 2932: 2574: 2373: 925: 631: 595: 583: 247: 130: 4074:

We could say that too - maybe even point 'em to projects needing assistance.

2236:

we can keep protecting in case of waves of vandalism and unprotecting later,

154:

There you go, much better. Doesn't Democracy feel nice? :-P --Cyde Weys

3165: 3094: 2550: 344: 251: 185: 156: 118: 110: 3407:

permanently protected (like Main Page) got that way? Was it via a vote?? --

677:

YES! This is where a higher threshold would come in. NO vandal, except for

3059:

No, hold on. There's no need to archive yet, 32 KB is a subjective limit.

1789:

Yeah, it would definately help to push this along. I'm invisioning FAs or

444:

The following may be viewed more as concerns rather than questions per se.

2350:

Then offer a better solution than simply letting the vandals run wild. --

2009:

This has been discussed ad nauseaum, and most people decided against it.

114: 2749:

degree) will be vandalised three or four or five hundred times per day.

1673:, I encourage you to make changes, have discussions, start fights, and 3791:"Should there be more levels than simply 25/100, such as 25/100/500?" 3927:

legitimate reason to semi-protect a page, then the template can say

2416:. So, the sword goes both ways. Also, if we ever intend on actually 1983:

Knowledge:Village pump (perennial proposals)#Abolish anonymous users

594:

I hope to come back with some wider comments on the proposal later.

1479:

Thank you for contacting me. Yes, I am aware of the discussion at

4323: 4301: 1771:

I'm wondering if there is any possible synthesis between this and

142:. You tried to vote on a proposal that is still being worked on. - 3093:. And, for the record, I think that the privilege of editing the 3050:

Lets not break the thread just yet...give it another day or so.--

630:

vandalized state for 23 minutes, and in another for 15 minutes.--

313:

Minimum of 25 sounds appropriate to me and I agree with Titoxd.--

920:

I think it's a terrific idea myself. Those of us who patrol the

3948:

to see what the protection tag looks like. The 2 main ones are

4305: 4294:

IF $ User.editcount < $ Protect.threshold THEN rejectEdit()

2538:

but it's not really the way I prefer to spend my time here. ·

25: 3012:

P.S. Are we ready to archive yet? We're at 41 kb or something

2484:"Which is worse? Damage to Knowledge's pool of new users, or 1516:"please remove and protect from moves only when appropriate" 4327: 1882:

that mentioned, but I assume it could be used for that. --

4319: 3444:

one level. Let's not over complicate things, I'd say. --

3168:

was protected. You can't really compare the two; people

2931:

This entire thread is proof that we NEED semi-protect.--

1281:

we'll increase the number in the future. Any thoughts? -

109:- we need some minimum level of protection on our pages 3101:

who have been determined trustworthy by the community.

2781:

So, keeping this thread on-topic, when can I unprotect

2135: 1658: 1504: 1501: 1499: 1488: 1484: 4246:

Because it doesn't involve locked forks of articles. -

3785:

In my opinion, AOL users should stop whining and just

3778:"How do IP addresses factor in the previous question?" 3783:"How will AOL and other proxy accounts be addressed?" 2569:

left primarily because of the bitterness surrounding

1512:"Admins have repeatedly unprotected it quite quickly" 2922:

them with the resignation of "It's the wiki way?" --

4314:. The levels of semi-protection needed here at the 3103:

Now, please reveal the fundamental flaw in my plan.

2372:

egregious of circumstances...ie the Bush article.--

1483:, and have commented there earlier this morning. 4043:I'd add that said error message page should list 2488:to Knowledge's pool of highly experienced users?" 1944:Is there any way Knowledge can be set up so that 3956:. I'm sure we could just modify one of those. -- 3776:Either one will probably have the same results. 611:archives of 11/28/2005 and here is what I found: 3219:Of course, all vandalism won't be stopped. The 3157:Hey, isn't this supposed to be edit-able by me? 3077:Percent-vandalism threshold for semi-protection 343:I think this is a very good idea, and that the 4229:since *anyone* can wiki edit the "draft" page 183:You're right, it's a mobocracy. --Cyde Weys 8: 4218:why not use the publish methodology instead? 3933:because it is a common target of vandalism." 3905:Effect of semi-protection on visible content 3758:Criteria to consider within Semi-protection 805:has long been protected against moves only. 4258:figuring out afd votes all of the time. -- 4318:might not be the same as those needed on 2581:a fatal flaw in the system, that flaw is 1569:pages is embodied in Golbez's comment on 1320:days (say, 10 times per day for a week). 1204:pages protected due to visibility reasons 1116:admin, long-term has to have a consensus. 679:someone who really didn't want to be here 93:Putting this up for a vote. Vote either 1677:in order to get this proposal to pass! - 1018:Splash's concern of protection creep. -- 801:Observe this already in practise, where 1940:Suggestion in the form of a question... 4296:or something similar (that line would 3466:dislike having lack of wiggle room. -- 3335:go to ArbCom. Perhaps it should go to 640:Similarly, among the last 50 edits to 44:Do not edit the contents of this page. 2630:Isn't it time to address this issue? 1510:first line item. The statement that 18:Knowledge talk:Semi-protection policy 7: 4419: 4277:I just had an idea after looking at 3496:) engage in endless edit warring. -- 2536:because they're desperately needed, 3085:(The second kind, as suggested by 1773:Knowledge:Requests for publication 848:Vandals aren't the biggest problem 793:— Articles will usually only move 387:Knowledge:Requests for publication 24: 2815:I meant seriously. One day, two?- 1664:Knowledge:WikiProject Semiprotect 1521:"George Bush is a son of a bitch" 1455:Crosspost regarding GWB vandalism 4420: 3944:Look at any of the pages on the 3886: 3880:lets keep it to logged in users. 3808: 2651: 1508:Knowledge:Protection_policy#Uses 1492:Semi-protection policy talk page 229: 29: 2482:Perhaps the question should be 4202:I added the note at the top... 2553:is on "indefinite wikibreak." 2549:I just noticed that the other 2137:or we restricted page moves? 607:Okay, I just went through the 1: 3889: 3811: 3331:Right off the bat, it should 3215:23:37, 30 November 2005 (UTC) 3203:23:33, 30 November 2005 (UTC) 3191:23:29, 30 November 2005 (UTC) 3110:22:27, 30 November 2005 (UTC) 3069:23:57, 30 November 2005 (UTC) 3055:21:36, 30 November 2005 (UTC) 3040:21:00, 30 November 2005 (UTC) 3000:21:00, 30 November 2005 (UTC) 2654: 2590:23:29, 30 November 2005 (UTC) 2545:21:46, 30 November 2005 (UTC) 2529:21:44, 30 November 2005 (UTC) 2495:21:39, 30 November 2005 (UTC) 2474:21:00, 30 November 2005 (UTC) 2431:23:55, 30 November 2005 (UTC) 2377:20:08, 30 November 2005 (UTC) 2367:19:43, 30 November 2005 (UTC) 2355:19:03, 30 November 2005 (UTC) 2342:19:43, 30 November 2005 (UTC) 2331:19:39, 30 November 2005 (UTC) 2317:19:43, 30 November 2005 (UTC) 2293:19:08, 30 November 2005 (UTC) 2279:18:56, 30 November 2005 (UTC) 2265:19:03, 30 November 2005 (UTC) 2255:18:46, 30 November 2005 (UTC) 2230:18:37, 30 November 2005 (UTC) 2215:18:31, 30 November 2005 (UTC) 2202:18:18, 30 November 2005 (UTC) 2178:21:00, 30 November 2005 (UTC) 2142:18:55, 30 November 2005 (UTC) 2127:18:57, 30 November 2005 (UTC) 2120:reasonable middle ground. · 2115:18:53, 30 November 2005 (UTC) 2102:18:31, 30 November 2005 (UTC) 2084:18:28, 30 November 2005 (UTC) 2061:18:22, 30 November 2005 (UTC) 2039:21:00, 30 November 2005 (UTC) 2005:19:19, 30 November 2005 (UTC) 1992:18:21, 30 November 2005 (UTC) 1977:18:19, 30 November 2005 (UTC) 1954:17:30, 30 November 2005 (UTC) 1921:21:00, 30 November 2005 (UTC) 1889:16:49, 30 November 2005 (UTC) 1871:21:00, 30 November 2005 (UTC) 1840:06:59, 30 November 2005 (UTC) 1825:21:00, 30 November 2005 (UTC) 1784:06:32, 30 November 2005 (UTC) 1761:21:00, 30 November 2005 (UTC) 1726:09:41, 30 November 2005 (UTC) 1703:05:31, 30 November 2005 (UTC) 1639:05:31, 30 November 2005 (UTC) 1597:00:47, 30 November 2005 (UTC) 1581:00:38, 30 November 2005 (UTC) 1557:00:43, 30 November 2005 (UTC) 1544:00:02, 30 November 2005 (UTC) 1528:22:08, 29 November 2005 (UTC) 1474:19:47, 29 November 2005 (UTC) 1445:21:00, 30 November 2005 (UTC) 1406:16:24, 30 November 2005 (UTC) 1390:04:13, 30 November 2005 (UTC) 1374:00:34, 30 November 2005 (UTC) 1361:23:53, 29 November 2005 (UTC) 1348:23:01, 29 November 2005 (UTC) 1334:22:54, 29 November 2005 (UTC) 1307:22:39, 29 November 2005 (UTC) 1260:21:00, 30 November 2005 (UTC) 1213:01:25, 30 November 2005 (UTC) 1189:22:49, 29 November 2005 (UTC) 1175:22:39, 29 November 2005 (UTC) 1144:22:28, 29 November 2005 (UTC) 1091:11:17, 30 November 2005 (UTC) 1064:08:24, 30 November 2005 (UTC) 1043:22:54, 29 November 2005 (UTC) 1023:22:40, 29 November 2005 (UTC) 1009:22:07, 29 November 2005 (UTC) 964:22:43, 29 November 2005 (UTC) 952:22:17, 29 November 2005 (UTC) 936:21:42, 29 November 2005 (UTC) 916:20:27, 29 November 2005 (UTC) 898:20:16, 29 November 2005 (UTC) 885:19:45, 29 November 2005 (UTC) 870:15:13, 29 November 2005 (UTC) 770:21:00, 30 November 2005 (UTC) 727:20:07, 30 November 2005 (UTC) 707:22:07, 29 November 2005 (UTC) 670:14:57, 29 November 2005 (UTC) 655:13:51, 29 November 2005 (UTC) 635:09:31, 29 November 2005 (UTC) 602:08:46, 29 November 2005 (UTC) 590:08:46, 29 November 2005 (UTC) 568:23:54, 29 November 2005 (UTC) 558:22:07, 29 November 2005 (UTC) 524:18:27, 29 November 2005 (UTC) 510:12:20, 29 November 2005 (UTC) 460:07:33, 29 November 2005 (UTC) 436:06:14, 29 November 2005 (UTC) 400:05:58, 29 November 2005 (UTC) 326:21:26, 30 November 2005 (UTC) 318:19:27, 29 November 2005 (UTC) 305:16:59, 29 November 2005 (UTC) 295:05:57, 29 November 2005 (UTC) 264:05:56, 29 November 2005 (UTC) 238:05:42, 29 November 2005 (UTC) 232: 101:, and state your reasons why. 4452:06:23, 3 December 2005 (UTC) 4405:01:27, 3 December 2005 (UTC) 4391:01:25, 3 December 2005 (UTC) 4373:21:27, 2 December 2005 (UTC) 4355:21:19, 2 December 2005 (UTC) 4344:21:08, 2 December 2005 (UTC) 4265:13:44, 1 December 2005 (UTC) 4253:13:23, 1 December 2005 (UTC) 4241:13:19, 1 December 2005 (UTC) 4236:Why this proposal instead? - 4213:09:16, 1 December 2005 (UTC) 4192:20:14, 1 December 2005 (UTC) 4175:20:08, 1 December 2005 (UTC) 4154:07:06, 1 December 2005 (UTC) 4143:06:46, 1 December 2005 (UTC) 4132:06:40, 1 December 2005 (UTC) 4088:23:13, 1 December 2005 (UTC) 4070:22:57, 1 December 2005 (UTC) 4061:21:29, 1 December 2005 (UTC) 4039:21:27, 1 December 2005 (UTC) 4030:20:51, 1 December 2005 (UTC) 4012:20:43, 1 December 2005 (UTC) 4000:20:31, 1 December 2005 (UTC) 3985:19:48, 1 December 2005 (UTC) 3963:09:05, 1 December 2005 (UTC) 3940:05:26, 1 December 2005 (UTC) 3914:01:48, 1 December 2005 (UTC) 3895:05:52, 2 December 2005 (UTC) 3883: 3875:21:57, 1 December 2005 (UTC) 3866:21:21, 1 December 2005 (UTC) 3855:19:28, 1 December 2005 (UTC) 3838:19:03, 1 December 2005 (UTC) 3827:18:58, 1 December 2005 (UTC) 3817:18:51, 1 December 2005 (UTC) 3805: 3798:05:06, 1 December 2005 (UTC) 3768:01:40, 1 December 2005 (UTC) 3740:19:52, 1 December 2005 (UTC) 3728:19:43, 1 December 2005 (UTC) 3694:19:36, 1 December 2005 (UTC) 3660:19:25, 1 December 2005 (UTC) 3626:19:15, 1 December 2005 (UTC) 3580:19:28, 1 December 2005 (UTC) 3568:19:12, 1 December 2005 (UTC) 3556:19:00, 1 December 2005 (UTC) 3544:18:52, 1 December 2005 (UTC) 3534:18:43, 1 December 2005 (UTC) 3518:18:31, 1 December 2005 (UTC) 3503:10:01, 1 December 2005 (UTC) 3487:09:23, 1 December 2005 (UTC) 3473:09:01, 1 December 2005 (UTC) 3461:08:34, 1 December 2005 (UTC) 3451:07:17, 1 December 2005 (UTC) 3438:07:08, 1 December 2005 (UTC) 3414:07:03, 1 December 2005 (UTC) 3402:06:54, 1 December 2005 (UTC) 3392:06:53, 1 December 2005 (UTC) 3382:06:48, 1 December 2005 (UTC) 3370:06:40, 1 December 2005 (UTC) 3360:06:27, 1 December 2005 (UTC) 3349:03:31, 1 December 2005 (UTC) 3326:01:40, 1 December 2005 (UTC) 3294:04:50, 3 December 2005 (UTC) 3266:00:35, 1 December 2005 (UTC) 3237:00:05, 1 December 2005 (UTC) 3134:21:33, 1 December 2005 (UTC) 3121:01:43, 1 December 2005 (UTC) 2936:20:59, 1 December 2005 (UTC) 2927:15:31, 1 December 2005 (UTC) 2883:07:08, 1 December 2005 (UTC) 2840:03:37, 1 December 2005 (UTC) 2822:03:26, 1 December 2005 (UTC) 2811:03:22, 1 December 2005 (UTC) 2792:03:20, 1 December 2005 (UTC) 2777:02:53, 1 December 2005 (UTC) 2763:02:52, 1 December 2005 (UTC) 2741:02:50, 1 December 2005 (UTC) 2730:02:48, 1 December 2005 (UTC) 2716:02:42, 1 December 2005 (UTC) 2703:02:37, 1 December 2005 (UTC) 2660:00:58, 1 December 2005 (UTC) 2648: 2640:00:54, 1 December 2005 (UTC) 2607:Replies to common objections 2304:22:42, 3 December 2005 (UTC) 1932:06:20, 1 December 2005 (UTC) 1877:Am I missing something or... 1587:cannot touch protected pages 1036:don't give protection to. -- 366:20:22, 2 December 2005 (UTC) 357:19:40, 2 December 2005 (UTC) 339:02:35, 2 December 2005 (UTC) 226: 204:18:34, 3 December 2005 (UTC) 193:18:31, 3 December 2005 (UTC) 179:18:29, 3 December 2005 (UTC) 170:Knowledge is not a democracy 164:18:29, 3 December 2005 (UTC) 149:18:25, 3 December 2005 (UTC) 134:18:06, 3 December 2005 (UTC) 122:09:30, 3 December 2005 (UTC) 4285:. This has two advantages: 1561:My particular concern with 826:Protection creep (2nd kind) 791:Protection creep (1st kind) 172:. Voting here is rubbish. - 4468: 1996:Thank you for the link to 1461:Crossposted from talk page 838:Stratification of articles 4330:would like this idea too. 4312:Inter-wiki simplification 2184:George W. Bush protection 1585:Yes but admins generally 1481:Knowledge:Semi protection 1465:Knowledge:Semi protection 832:Stratification of editors 616:66 instances of vandalism 4300:work in MediaWiki, it's 4123:the protected pages list 4020:can work something out. 3429:<carriage return: --> 3304:Three things to consider 3081:To address the issue of 1831:requests for advertising 1767:Requests for publication 383:Knowledge:Pushing to 1.0 3312:Semi-protection Process 3097:should be reserved for 1354:less to get it right. - 300:Knowledge's software?-- 4273:Semi-protection levels 1675:dress like a superhero 1131:Is this even possible? 2499:Agreed. We just lost 2414:would not have joined 1946:only registered users 1659:Village Pump proposal 1232:Image:Human Feces.jpg 878:is not just a scratch 42:of past discussions. 4016:I'm pretty sure the 3946:protected pages page 3929:"This page has been 3281:as often as possible 2876:I unprotected it. -- 922:Page protection page 3787:register an account 2960:Revoking permission 1651:VotesforSemiprotect 1571:Talk:George W. Bush 1490:As is noted on the 1316:times per day over 4324:English Wiktionary 3221:determined vandals 856:verifiable sources 811:Easing prophylaxis 4386:implementation.-- 4320:Spanish Knowledge 4316:English Knowledge 4251: 4067:TantalumTelluride 4036:TantalumTelluride 3937:TantalumTelluride 3863:TantalumTelluride 3795:TantalumTelluride 3436: 3264: 3234:TantalumTelluride 3212:TantalumTelluride 3189: 3131:TantalumTelluride 3107:TantalumTelluride 3013: 2820: 2790: 2739: 2714: 2587:TantalumTelluride 2492:TantalumTelluride 2365: 2340: 2315: 2277: 2253: 2213: 2190:Crossposted from 1990: 1724: 1579: 1472: 1359: 950: 868: 469:Voice of All(MTG) 202: 191: 177: 162: 147: 85: 84: 54: 53: 48:current talk page 4459: 4449: 4444: 4437: 4430: 4425: 4424: 4423: 4402: 4370: 4341: 4250: 4172: 4104:Just some points 4080: 4053: 4034:I agree also. -- 4027: 3977: 3891: 3888: 3885: 3813: 3810: 3807: 3435: 3346: 3261: 3255: 3186: 3180: 3083:protection creep 3066: 3037: 3032: 3025: 3018: 3011: 2997: 2992: 2985: 2978: 2973: 2967: 2832: 2819: 2803: 2789: 2774: 2755: 2738: 2727: 2713: 2700: 2695: 2688: 2681: 2656: 2653: 2650: 2637: 2526: 2521: 2514: 2507: 2471: 2466: 2459: 2452: 2428: 2364: 2339: 2314: 2276: 2245: 2212: 2175: 2170: 2163: 2156: 2094: 2079: 2077: 2072: 2036: 2031: 2024: 2017: 1989: 1972: 1970: 1965: 1918: 1913: 1906: 1899: 1868: 1863: 1856: 1849: 1822: 1817: 1810: 1803: 1798: 1792: 1758: 1753: 1746: 1739: 1720: 1700: 1695: 1688: 1681: 1655: 1649: 1636: 1631: 1624: 1617: 1578: 1471: 1442: 1437: 1430: 1423: 1358: 1326: 1304: 1299: 1292: 1285: 1257: 1252: 1245: 1238: 1172: 1167: 1160: 1153: 1139: 1006: 1001: 994: 987: 949: 908: 867: 767: 762: 755: 748: 704: 699: 692: 685: 555: 550: 543: 536: 507: 502: 495: 488: 433: 428: 421: 414: 397: 385:came out with a 292: 287: 280: 273: 261: 234: 231: 228: 201: 184: 176: 155: 146: 63: 56: 55: 33: 32: 26: 4467: 4466: 4462: 4461: 4460: 4458: 4457: 4456: 4447: 4442: 4435: 4428: 4421: 4400: 4368: 4361:Blocking policy 4339: 4295: 4290:Simpler to code 4283:Special:Blockip 4279:Special:Blockip 4275: 4220: 4204: 4170: 4106: 4076: 4049: 4025: 3973: 3921:deletion policy 3907: 3760: 3494:Bogdanov Affair 3344: 3314: 3306: 3292: 3259: 3184: 3144: 3079: 3064: 3035: 3030: 3023: 3016: 2995: 2990: 2983: 2976: 2971: 2965: 2962: 2828: 2799: 2772: 2751: 2725: 2698: 2693: 2686: 2679: 2635: 2524: 2519: 2512: 2505: 2469: 2464: 2457: 2450: 2426: 2186: 2173: 2168: 2161: 2154: 2090: 2075: 2070: 2068: 2051: 2034: 2029: 2022: 2015: 1968: 1963: 1961: 1942: 1916: 1911: 1904: 1897: 1879: 1866: 1861: 1854: 1847: 1833: 1820: 1815: 1808: 1801: 1796: 1790: 1769: 1756: 1751: 1744: 1737: 1698: 1693: 1686: 1679: 1653: 1647: 1634: 1629: 1622: 1615: 1607: 1457: 1440: 1435: 1428: 1421: 1322: 1302: 1297: 1290: 1283: 1274: 1255: 1250: 1243: 1236: 1170: 1165: 1158: 1151: 1137: 1133: 1004: 999: 992: 985: 904: 784: 765: 760: 753: 746: 702: 697: 690: 683: 663: 580: 553: 548: 541: 534: 505: 500: 493: 486: 431: 426: 419: 412: 407: 395: 380: 374:Does this help 290: 285: 278: 271: 259: 220: 90: 59: 30: 22: 21: 20: 12: 11: 5: 4465: 4463: 4455: 4454: 4414: 4413: 4412: 4411: 4410: 4409: 4408: 4407: 4378: 4377: 4376: 4375: 4332: 4331: 4309: 4293: 4274: 4271: 4270: 4269: 4268: 4267: 4234: 4233: 4230: 4227: 4224: 4219: 4216: 4203: 4200: 4199: 4198: 4197: 4196: 4195: 4194: 4159: 4158: 4157: 4156: 4105: 4102: 4101: 4100: 4099: 4098: 4097: 4096: 4095: 4094: 4093: 4092: 4091: 4090: 3992: 3991: 3990: 3989: 3988: 3987: 3931:semi-protected 3906: 3903: 3902: 3901: 3900: 3899: 3898: 3897: 3847: 3846: 3845: 3844: 3843: 3842: 3841: 3840: 3759: 3756: 3755: 3754: 3753: 3752: 3751: 3750: 3749: 3748: 3747: 3746: 3745: 3744: 3743: 3742: 3730: 3707: 3706: 3705: 3704: 3703: 3702: 3701: 3700: 3699: 3698: 3697: 3696: 3673: 3672: 3671: 3670: 3669: 3668: 3667: 3666: 3665: 3664: 3663: 3662: 3641: 3640: 3639: 3638: 3637: 3636: 3635: 3634: 3633: 3632: 3631: 3630: 3629: 3628: 3599: 3598: 3597: 3596: 3595: 3594: 3593: 3592: 3591: 3590: 3589: 3588: 3587: 3586: 3570: 3560: 3559: 3558: 3524: 3505: 3489: 3427: 3426: 3425: 3424: 3423: 3422: 3421: 3420: 3419: 3418: 3417: 3416: 3394: 3319:George W. Bush 3313: 3310: 3305: 3302: 3301: 3300: 3299: 3298: 3297: 3296: 3288: 3271: 3270: 3269: 3268: 3240: 3239: 3230:Saddam Hussein 3226:George W. Bush 3217: 3206: 3205: 3148:George W. Bush 3143: 3140: 3139: 3138: 3137: 3136: 3124: 3123: 3078: 3075: 3074: 3073: 3072: 3071: 3048: 3047: 3046: 3045: 3044: 3043: 3042: 2961: 2958: 2957: 2956: 2955: 2954: 2953: 2952: 2951: 2950: 2949: 2948: 2947: 2946: 2945: 2944: 2943: 2942: 2941: 2940: 2939: 2938: 2902: 2901: 2900: 2899: 2898: 2897: 2896: 2895: 2894: 2893: 2892: 2891: 2890: 2889: 2888: 2887: 2886: 2885: 2857: 2856: 2855: 2854: 2853: 2852: 2851: 2850: 2849: 2848: 2847: 2846: 2845: 2844: 2843: 2842: 2783:George W. Bush 2765: 2665: 2664: 2663: 2662: 2619: 2613: 2612: 2611: 2599: 2598: 2597: 2596: 2595: 2594: 2593: 2592: 2476: 2445: 2444: 2443: 2442: 2441: 2440: 2439: 2438: 2437: 2436: 2435: 2434: 2433: 2392: 2391: 2390: 2389: 2388: 2387: 2386: 2385: 2384: 2383: 2382: 2381: 2380: 2379: 2348: 2347: 2346: 2345: 2344: 2321: 2320: 2319: 2308: 2307: 2306: 2269: 2268: 2267: 2185: 2182: 2181: 2180: 2145: 2144: 2131: 2130: 2129: 2107: 2106: 2105: 2104: 2050: 2047: 2046: 2045: 2044: 2043: 2042: 2041: 1979: 1941: 1938: 1937: 1936: 1935: 1934: 1878: 1875: 1874: 1873: 1832: 1829: 1828: 1827: 1768: 1765: 1764: 1763: 1729: 1728: 1717: 1714: 1711:George W. Bush 1667: 1666: 1661: 1656: 1606: 1603: 1602: 1601: 1600: 1599: 1565:protection of 1559: 1537:George W. Bush 1532: 1531: 1530: 1496:George W. Bush 1456: 1453: 1452: 1451: 1450: 1449: 1448: 1447: 1411: 1410: 1409: 1408: 1393: 1392: 1377: 1376: 1351: 1350: 1337: 1336: 1273: 1270: 1269: 1268: 1267: 1266: 1265: 1264: 1263: 1262: 1220: 1219: 1218: 1217: 1216: 1215: 1194: 1193: 1192: 1191: 1178: 1177: 1132: 1129: 1128: 1127: 1126: 1125: 1124: 1123: 1122: 1121: 1120: 1119: 1118: 1117: 1102: 1101: 1100: 1099: 1098: 1097: 1096: 1095: 1094: 1093: 1073: 1072: 1071: 1070: 1069: 1068: 1067: 1066: 1050: 1049: 1048: 1047: 1046: 1045: 1028: 1027: 1026: 1025: 1012: 1011: 976: 975: 974: 973: 972: 971: 970: 969: 968: 967: 966: 888: 887: 861: 860: 850:— the lack of 845: 835: 829: 823: 822: 821: 808: 807: 806: 803:George W. Bush 783: 780: 779: 778: 777: 776: 775: 774: 773: 772: 734: 733: 732: 731: 730: 729: 712: 711: 710: 709: 662: 659: 658: 657: 646: 645: 642:George W. Bush 627: 626: 620: 617: 613: 612: 579: 578:Data accurate? 576: 575: 574: 573: 572: 571: 570: 527: 526: 515: 514: 513: 512: 481: 473: 463: 462: 453: 450: 447: 446: 445: 439: 438: 406: 403: 379: 372: 371: 370: 369: 368: 341: 328: 320: 311: 310: 309: 308: 307: 244:George W. Bush 240: 219: 216: 215: 214: 213: 212: 211: 210: 209: 208: 207: 206: 136: 124: 89: 86: 83: 82: 77: 74: 69: 64: 52: 51: 34: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 4464: 4453: 4450: 4445: 4440: 4439: 4438: 4431: 4416: 4415: 4406: 4403: 4398: 4394: 4393: 4392: 4389: 4384: 4383: 4382: 4381: 4380: 4379: 4374: 4371: 4366: 4362: 4358: 4357: 4356: 4353: 4348: 4347: 4346: 4345: 4342: 4337: 4329: 4325: 4321: 4317: 4313: 4310: 4307: 4303: 4299: 4291: 4288: 4287: 4286: 4284: 4280: 4272: 4266: 4263: 4262: 4256: 4255: 4254: 4249: 4245: 4244: 4243: 4242: 4239: 4231: 4228: 4225: 4222: 4221: 4217: 4215: 4214: 4211: 4210: 4201: 4193: 4190: 4189: 4183: 4182: 4181: 4180: 4179: 4178: 4177: 4176: 4173: 4168: 4164: 4155: 4152: 4151: 4146: 4145: 4144: 4141: 4136: 4135: 4134: 4133: 4130: 4129: 4124: 4119: 4116: 4110: 4103: 4089: 4086: 4085: 4081: 4079: 4073: 4072: 4071: 4068: 4064: 4063: 4062: 4059: 4058: 4054: 4052: 4046: 4042: 4041: 4040: 4037: 4033: 4032: 4031: 4028: 4023: 4019: 4015: 4014: 4013: 4010: 4009: 4004: 4003: 4002: 4001: 3998: 3986: 3983: 3982: 3978: 3976: 3970: 3966: 3965: 3964: 3961: 3960: 3955: 3951: 3947: 3943: 3942: 3941: 3938: 3934: 3932: 3926: 3922: 3918: 3917: 3916: 3915: 3912: 3904: 3896: 3893: 3892: 3878: 3877: 3876: 3873: 3869: 3868: 3867: 3864: 3859: 3858: 3857: 3856: 3853: 3839: 3836: 3835: 3830: 3829: 3828: 3825: 3820: 3819: 3818: 3815: 3814: 3801: 3800: 3799: 3796: 3792: 3788: 3784: 3779: 3775: 3772: 3771: 3770: 3769: 3766: 3763:25/100/500?-- 3757: 3741: 3738: 3737: 3731: 3729: 3726: 3721: 3720: 3719: 3718: 3717: 3716: 3715: 3714: 3713: 3712: 3711: 3710: 3709: 3708: 3695: 3692: 3691: 3685: 3684: 3683: 3682: 3681: 3680: 3679: 3678: 3677: 3676: 3675: 3674: 3661: 3658: 3653: 3652: 3651: 3650: 3649: 3648: 3647: 3646: 3645: 3644: 3643: 3642: 3627: 3624: 3623: 3617: 3613: 3612: 3611: 3610: 3609: 3608: 3607: 3606: 3605: 3604: 3603: 3602: 3601: 3600: 3583: 3582: 3581: 3578: 3577: 3571: 3569: 3566: 3561: 3557: 3554: 3553: 3547: 3546: 3545: 3542: 3537: 3536: 3535: 3532: 3531: 3525: 3521: 3520: 3519: 3516: 3511: 3506: 3504: 3501: 3500: 3495: 3490: 3488: 3485: 3481: 3476: 3475: 3474: 3471: 3470: 3464: 3463: 3462: 3459: 3454: 3453: 3452: 3449: 3448: 3442: 3441: 3440: 3439: 3434: 3415: 3412: 3411: 3405: 3404: 3403: 3400: 3395: 3393: 3390: 3385: 3384: 3383: 3380: 3379: 3373: 3372: 3371: 3368: 3363: 3362: 3361: 3358: 3357: 3352: 3351: 3350: 3347: 3342: 3338: 3334: 3330: 3329: 3328: 3327: 3324: 3320: 3311: 3309: 3303: 3295: 3291: 3286: 3282: 3277: 3276: 3275: 3274: 3273: 3272: 3267: 3262: 3254: 3249: 3244: 3243: 3242: 3241: 3238: 3235: 3231: 3227: 3222: 3218: 3216: 3213: 3208: 3207: 3204: 3201: 3200: 3195: 3194: 3193: 3192: 3187: 3179: 3175: 3171: 3167: 3163: 3158: 3154: 3149: 3141: 3135: 3132: 3128: 3127: 3126: 3125: 3122: 3119: 3114: 3113: 3112: 3111: 3108: 3104: 3100: 3099:those editors 3096: 3092: 3088: 3084: 3076: 3070: 3067: 3062: 3058: 3057: 3056: 3053: 3049: 3041: 3038: 3033: 3028: 3027: 3026: 3019: 3010: 3009: 3008: 3007: 3006: 3005: 3004: 3003: 3002: 3001: 2998: 2993: 2988: 2987: 2986: 2979: 2970: 2959: 2937: 2934: 2930: 2929: 2928: 2925: 2920: 2919: 2918: 2917: 2916: 2915: 2914: 2913: 2912: 2911: 2910: 2909: 2908: 2907: 2906: 2905: 2904: 2903: 2884: 2881: 2880: 2875: 2874: 2873: 2872: 2871: 2870: 2869: 2868: 2867: 2866: 2865: 2864: 2863: 2862: 2861: 2860: 2859: 2858: 2841: 2838: 2837: 2833: 2831: 2825: 2824: 2823: 2818: 2814: 2813: 2812: 2809: 2808: 2804: 2802: 2795: 2794: 2793: 2788: 2784: 2780: 2779: 2778: 2775: 2770: 2766: 2764: 2761: 2760: 2756: 2754: 2748: 2744: 2743: 2742: 2737: 2733: 2732: 2731: 2728: 2723: 2719: 2718: 2717: 2712: 2707: 2706: 2705: 2704: 2701: 2696: 2691: 2690: 2689: 2682: 2676: 2671: 2661: 2658: 2657: 2643: 2642: 2641: 2638: 2633: 2629: 2623: 2620: 2618: 2614: 2610: 2608: 2603: 2602: 2601: 2600: 2591: 2588: 2584: 2580: 2576: 2572: 2571:the CCW's MfD 2568: 2564: 2560: 2556: 2552: 2548: 2547: 2546: 2543: 2542: 2537: 2532: 2531: 2530: 2527: 2522: 2517: 2516: 2515: 2508: 2502: 2498: 2497: 2496: 2493: 2489: 2487: 2480: 2477: 2475: 2472: 2467: 2462: 2461: 2460: 2453: 2446: 2432: 2429: 2424: 2419: 2415: 2411: 2406: 2405: 2404: 2403: 2402: 2401: 2400: 2399: 2398: 2397: 2396: 2395: 2394: 2393: 2378: 2375: 2370: 2369: 2368: 2363: 2358: 2357: 2356: 2353: 2349: 2343: 2338: 2334: 2333: 2332: 2329: 2328: 2322: 2318: 2313: 2309: 2305: 2302: 2298: 2297: 2296: 2295: 2294: 2291: 2290: 2284: 2283: 2282: 2281: 2280: 2275: 2270: 2266: 2263: 2258: 2257: 2256: 2252: 2250: 2244: 2239: 2235: 2234: 2233: 2232: 2231: 2228: 2227: 2222: 2218: 2217: 2216: 2211: 2206: 2205: 2204: 2203: 2200: 2199: 2194: 2193: 2183: 2179: 2176: 2171: 2166: 2165: 2164: 2157: 2151: 2147: 2146: 2143: 2140: 2136: 2132: 2128: 2125: 2124: 2118: 2117: 2116: 2113: 2109: 2108: 2103: 2100: 2099: 2095: 2093: 2087: 2086: 2085: 2082: 2078: 2073: 2065: 2064: 2063: 2062: 2059: 2058: 2048: 2040: 2037: 2032: 2027: 2026: 2025: 2018: 2012: 2008: 2007: 2006: 2003: 1999: 1995: 1994: 1993: 1988: 1984: 1980: 1978: 1975: 1971: 1966: 1958: 1957: 1956: 1955: 1952: 1947: 1939: 1933: 1930: 1929: 1924: 1923: 1922: 1919: 1914: 1909: 1908: 1907: 1900: 1893: 1892: 1891: 1890: 1887: 1886: 1876: 1872: 1869: 1864: 1859: 1858: 1857: 1850: 1844: 1843: 1842: 1841: 1838: 1830: 1826: 1823: 1818: 1813: 1812: 1811: 1804: 1795: 1788: 1787: 1786: 1785: 1782: 1778: 1774: 1766: 1762: 1759: 1754: 1749: 1748: 1747: 1740: 1734: 1731: 1730: 1727: 1723: 1718: 1715: 1712: 1707: 1706: 1705: 1704: 1701: 1696: 1691: 1690: 1689: 1682: 1676: 1672: 1665: 1662: 1660: 1657: 1652: 1646: 1645: 1644: 1641: 1640: 1637: 1632: 1627: 1626: 1625: 1618: 1611: 1604: 1598: 1595: 1594: 1588: 1584: 1583: 1582: 1577: 1572: 1568: 1564: 1560: 1558: 1555: 1554: 1548: 1547: 1546: 1545: 1542: 1538: 1529: 1526: 1522: 1517: 1513: 1509: 1505: 1502: 1500: 1497: 1493: 1489: 1485: 1482: 1478: 1477: 1476: 1475: 1470: 1466: 1462: 1454: 1446: 1443: 1438: 1433: 1432: 1431: 1424: 1417: 1416: 1415: 1414: 1413: 1412: 1407: 1404: 1403: 1397: 1396: 1395: 1394: 1391: 1388: 1383: 1379: 1378: 1375: 1372: 1371: 1365: 1364: 1363: 1362: 1357: 1349: 1346: 1345: 1339: 1338: 1335: 1332: 1331: 1327: 1325: 1319: 1315: 1311: 1310: 1309: 1308: 1305: 1300: 1295: 1294: 1293: 1286: 1280: 1271: 1261: 1258: 1253: 1248: 1247: 1246: 1239: 1233: 1228: 1227: 1226: 1225: 1224: 1223: 1222: 1221: 1214: 1211: 1210: 1205: 1200: 1199: 1198: 1197: 1196: 1195: 1190: 1187: 1182: 1181: 1180: 1179: 1176: 1173: 1168: 1163: 1162: 1161: 1154: 1148: 1147: 1146: 1145: 1142: 1140: 1130: 1114: 1113: 1112: 1111: 1110: 1109: 1108: 1107: 1106: 1105: 1104: 1103: 1092: 1089: 1088: 1083: 1082: 1081: 1080: 1079: 1078: 1077: 1076: 1075: 1074: 1065: 1062: 1058: 1057: 1056: 1055: 1054: 1053: 1052: 1051: 1044: 1041: 1040: 1034: 1033: 1032: 1031: 1030: 1029: 1024: 1021: 1016: 1015: 1014: 1013: 1010: 1007: 1002: 997: 996: 995: 988: 982: 977: 965: 962: 961: 955: 954: 953: 948: 944: 939: 938: 937: 934: 933: 927: 923: 919: 918: 917: 914: 913: 909: 907: 901: 900: 899: 896: 892: 891: 890: 889: 886: 883: 879: 874: 873: 872: 871: 866: 857: 853: 849: 846: 843: 839: 836: 833: 830: 827: 824: 819: 815: 814: 812: 809: 804: 800: 799: 796: 792: 789: 788: 787: 781: 771: 768: 763: 758: 757: 756: 749: 742: 741: 740: 739: 738: 737: 736: 735: 728: 725: 723: 718: 717: 716: 715: 714: 713: 708: 705: 700: 695: 694: 693: 686: 680: 676: 675: 674: 673: 672: 671: 668: 660: 656: 653: 648: 647: 643: 639: 638: 637: 636: 633: 625: 621: 618: 615: 614: 610: 609:George W Bush 606: 605: 604: 603: 600: 597: 592: 591: 588: 585: 577: 569: 566: 561: 560: 559: 556: 551: 546: 545: 544: 537: 531: 530: 529: 528: 525: 522: 517: 516: 511: 508: 503: 498: 497: 496: 489: 482: 479: 474: 470: 467: 466: 465: 464: 461: 458: 454: 451: 448: 443: 442: 441: 440: 437: 434: 429: 424: 423: 422: 415: 409: 408: 404: 402: 401: 398: 393: 388: 384: 377: 373: 367: 364: 360: 359: 358: 355: 351: 346: 342: 340: 337: 334: 329: 327: 321: 319: 316: 312: 306: 303: 298: 297: 296: 293: 288: 283: 282: 281: 274: 267: 266: 265: 262: 257: 253: 249: 245: 241: 239: 236: 235: 222: 221: 217: 205: 200: 196: 195: 194: 190: 188: 186: 182: 181: 180: 175: 171: 167: 166: 165: 161: 159: 157: 153: 152: 151: 150: 145: 141: 137: 135: 132: 128: 125: 123: 120: 116: 112: 108: 105: 104: 103: 102: 100: 96: 87: 81: 78: 75: 73: 70: 68: 65: 62: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 4434: 4433: 4333: 4311: 4297: 4289: 4276: 4260: 4235: 4208: 4205: 4187: 4162: 4160: 4149: 4127: 4120: 4111: 4107: 4083: 4077: 4056: 4050: 4044: 4007: 3993: 3980: 3974: 3958: 3928: 3924: 3908: 3881: 3848: 3833: 3803: 3790: 3786: 3782: 3777: 3773: 3761: 3735: 3689: 3621: 3615: 3575: 3551: 3529: 3509: 3498: 3479: 3468: 3446: 3428: 3409: 3377: 3355: 3332: 3315: 3307: 3280: 3247: 3198: 3173: 3169: 3156: 3152: 3145: 3102: 3082: 3080: 3022: 3021: 2982: 2981: 2963: 2878: 2835: 2829: 2806: 2800: 2758: 2752: 2746: 2685: 2684: 2674: 2669: 2666: 2646: 2626: 2615: 2604: 2582: 2578: 2558: 2554: 2540: 2535: 2511: 2510: 2483: 2478: 2456: 2455: 2417: 2413: 2409: 2326: 2288: 2248: 2237: 2225: 2197: 2189: 2187: 2160: 2159: 2149: 2139:Hall Monitor 2122: 2097: 2091: 2056: 2052: 2021: 2020: 2002:Hall Monitor 1945: 1943: 1927: 1903: 1902: 1884: 1880: 1853: 1852: 1834: 1807: 1806: 1770: 1743: 1742: 1732: 1685: 1684: 1668: 1642: 1621: 1620: 1612: 1608: 1592: 1567:high-profile 1566: 1562: 1552: 1541:Hall Monitor 1533: 1525:Hall Monitor 1520: 1515: 1511: 1460: 1458: 1427: 1426: 1401: 1381: 1369: 1352: 1343: 1329: 1323: 1317: 1313: 1289: 1288: 1278: 1275: 1242: 1241: 1208: 1157: 1156: 1134: 1086: 1038: 991: 990: 959: 942: 931: 911: 905: 877: 862: 847: 837: 831: 825: 818:just in case 817: 810: 794: 790: 785: 752: 751: 689: 688: 667:Gerard Foley 664: 628: 623: 593: 581: 565:Hall Monitor 540: 539: 521:Hall Monitor 492: 491: 418: 417: 381: 349: 277: 276: 224: 139: 138: 126: 106: 98: 94: 92: 91: 60: 43: 37: 4261:Woohookitty 4209:Woohookitty 4188:Woohookitty 4150:Woohookitty 4128:Woohookitty 4115:Doc glasgow 4008:Woohookitty 3959:Woohookitty 3834:Woohookitty 3736:Woohookitty 3690:Woohookitty 3622:Woohookitty 3576:Woohookitty 3552:Woohookitty 3530:Woohookitty 3499:Woohookitty 3469:Woohookitty 3447:Woohookitty 3410:Woohookitty 3378:Woohookitty 3356:Woohookitty 2879:Woohookitty 2622:Doc glasgow 2150:view source 1951:Cjmarsicano 1928:Woohookitty 1885:Woohookitty 1593:Woohookitty 1553:Woohookitty 1402:Woohookitty 1370:Woohookitty 1344:Woohookitty 1209:Woohookitty 1087:Woohookitty 1039:Woohookitty 960:Woohookitty 932:Woohookitty 197:Whatever. - 36:This is an 4334:Thoughts? 3969:Vprotected 3950:Vprotected 3253:Flcelloguy 3178:Flcelloguy 3091:wiki-death 2555:Indefinite 1671:WP:JEFTA!! 1643:See also: 1539:article? 1467:instead? - 926:John Kerry 457:Gurubrahma 333:Antandrus 248:John Kerry 3967:Agreed - 3954:protected 3431:way up. - 3166:Main page 3142:Concerned 3095:Main page 2559:infinite. 2301:Sandpiper 2011:Redwolf24 1563:permanent 943:"slap it" 834:— is bad. 478:Redwolf24 405:Questions 345:Main page 302:Kalsermar 252:Knowledge 111:evolution 80:Archive 5 72:Archive 3 67:Archive 2 61:Archive 1 3285:xaosflux 3199:Katefan0 2577:. There 2541:Katefan0 2327:Katefan0 2289:Katefan0 2226:Katefan0 2198:Katefan0 2123:Katefan0 2057:Katefan0 1722:Cool Cat 1605:Previous 1186:IronDuke 852:reliable 782:Grilling 722:Dominick 218:Comments 115:abortion 4322:or the 3480:However 2192:WP:AN/I 2049:The nut 1733:Instead 1272:Purpose 895:Alhutch 350:Support 315:Alhutch 127:Support 107:Support 95:Support 39:archive 4388:kizzle 4352:kizzle 4308:); and 4304:, not 4248:Splash 4238:Jcbarr 4140:kizzle 4078:BD2412 4051:BD2412 3997:kizzle 3975:BD2412 3911:kizzle 3872:kizzle 3852:kizzle 3824:kizzle 3765:kizzle 3725:kizzle 3657:kizzle 3565:kizzle 3541:kizzle 3515:kizzle 3484:kizzle 3458:kizzle 3433:Splash 3399:kizzle 3389:kizzle 3367:kizzle 3323:kizzle 3170:expect 3118:kizzle 3087:Splash 2924:Golbez 2830:BD2412 2817:Splash 2801:BD2412 2787:Splash 2753:BD2412 2736:Splash 2711:Splash 2670:actual 2628:cruft. 2567:Essjay 2501:Essjay 2486:damage 2418:fixing 2362:Splash 2352:Golbez 2337:Splash 2312:Splash 2274:Splash 2262:Golbez 2210:Splash 2112:kizzle 2092:BD2412 1987:Splash 1837:kizzle 1777:Jmabel 1576:Splash 1494:, the 1469:Splash 1387:kizzle 1382:course 1356:Splash 1324:BD2412 1061:kizzle 1020:kizzle 947:Splash 906:BD2412 882:kizzle 865:Splash 661:I LIKE 652:Solver 376:WP:1.0 363:kizzle 354:Mark J 336:(talk) 250:, and 199:Splash 174:Splash 144:Splash 140:Reject 99:Reject 88:Voting 4302:BASIC 4163:there 3884:Voice 3806:Voice 3614:I do 3337:WP:AN 3260:note? 3185:note? 3174:don't 3052:MONGO 2933:MONGO 2675:every 2649:Voice 2605:From 2575:RickK 2374:MONGO 2220:this 2076:blade 1969:blade 1775:? -- 1669:P.S. 1279:maybe 632:MONGO 596:Pcb21 584:Pcb21 324:])]] 227:Voice 131:Mkill 117:. -- 16:< 4448:rity 4397:Tito 4365:Tito 4336:Tito 4328:Meta 4167:Tito 4022:Tito 4018:devs 3952:and 3925:only 3341:Tito 3228:and 3153:then 3061:Tito 3036:rity 2996:rity 2769:Tito 2747:some 2722:Tito 2699:rity 2645:too. 2632:Tito 2551:Kate 2525:rity 2470:rity 2423:Tito 2238:lots 2174:rity 2071:Pure 2035:rity 1981:See 1964:Pure 1917:rity 1867:rity 1821:rity 1781:Talk 1757:rity 1699:rity 1635:rity 1441:rity 1303:rity 1256:rity 1171:rity 1005:rity 981:RFPP 842:good 766:rity 703:rity 599:Pete 587:Pete 554:rity 506:rity 480:'s . 432:rity 392:Tito 378:too? 352:. -- 291:rity 256:Tito 168:No. 119:Cyde 113:and 4429:Mys 4306:PHP 4298:not 4045:all 3890:All 3887:of 3812:All 3809:of 3616:not 3333:not 3162:ISP 3017:Mys 2977:Mys 2785:? - 2680:Mys 2655:All 2652:of 2563:RfA 2506:Mys 2451:Mys 2243:dab 2155:Mys 2016:Mys 1898:Mys 1848:Mys 1802:Mys 1738:Mys 1680:Mys 1616:Mys 1422:Mys 1380:Of 1284:Mys 1237:Mys 1152:Mys 986:Mys 747:Mys 684:Mys 535:Mys 487:Mys 413:Mys 272:Mys 233:All 230:of 97:or 4443:ku 4401:xd 4369:xd 4340:xd 4185:-- 4171:xd 4138:-- 4026:xd 3850:-- 3822:-- 3375:-- 3345:xd 3283:. 3258:A 3248:If 3183:A 3105:-- 3065:xd 3031:ku 2991:ku 2972:}} 2969:bv 2966:{{ 2773:xd 2726:xd 2694:ku 2636:xd 2583:my 2579:is 2565:. 2520:ku 2490:-- 2465:ku 2427:xd 2223:· 2169:ku 2080:| 2030:ku 1973:| 1912:ku 1862:ku 1816:ku 1797:}} 1794:GA 1791:{{ 1779:| 1752:ku 1719:-- 1694:ku 1654:}} 1648:{{ 1630:ku 1590:-- 1436:ku 1341:-- 1298:ku 1251:ku 1166:ku 1138:LV 1000:ku 929:-- 854:, 795:up 761:ku 698:ku 549:ku 501:ku 427:ku 396:xd 286:ku 260:xd 254:. 246:, 76:→ 4436:e 4426:- 4084:T 4057:T 3981:T 3290:C 3287:/ 3263:) 3256:( 3188:) 3181:( 3024:e 3014:- 2984:e 2836:T 2807:T 2759:T 2709:- 2687:e 2609:: 2513:e 2458:e 2410:I 2251:) 2249:ᛏ 2247:( 2188:( 2162:e 2098:T 2023:e 1905:e 1895:- 1855:e 1809:e 1745:e 1713:. 1687:e 1623:e 1574:- 1459:( 1429:e 1330:T 1318:y 1314:x 1291:e 1244:e 1159:e 993:e 912:T 863:- 754:e 744:- 691:e 542:e 494:e 420:e 279:e 269:- 50:.

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge

talk:Semi-protection policy/Archive 1 - Knowledge

Index