Knowledge talk:Semi-protection policy/Archive 2

3584:

can be unprotected. If it's unprotected or protected unwisely, the admin gets yelled at by many many others. Trust me. I know. I mean something else you aren't realizing is that if we implement semi-protection, it doesn't stop the new users or IPs from commenting on the semi-protecting admins page or on Requests for Protection (which has an unprotection request section) or anywhere else. So that's another check on protection creep. Objections by others could lead to the semi protection being lifted. It's not as if we are completely blocking them from Knowledge. Another point is that admins have alot of unwritten conventions, including IP blocks not going over 24 hours unless it's a repeat offender, pages not being protected if it's not a persistant edit war/vandalism case and many others. As I said, admins are good at self-policing. If things are getting out of hand, informal limits will be developed. They always are.

3574:

use the policy because they don't want to have to worry about time limits and # of admins to overturn and all of that. They will just avoid using the tool. And. As for protection creep, if...a month after the policy is initiated it looks as though the # of semi-protected pages is going way beyond what we expected, we can then add time limits. This is not set in stone. You've mentioned several times that "this isn't how you make policy". It is on Knowledge. We have to be very flexible. It's the nature of an ever changing site with different issues from day to day. We just can't start with the worst case scenario (i.e. that semi-protection is going to get out of hand). Like I said, if it does get out of hand, trust me, we'll figure it out. After all, that's essentially how we got to starting this discussion in the first place, i.e. GWB and others getting way out of hand.

2477:

anons can't do page moves in the GWB article, aside from that, how else do we prevent them from contributing? You're boilerplate appears to eliminate them from contributing in articles in which semiprotect is employed. Personally, I could care less if they can contribute and I think that almost all substantive edits come from registered users...that is my opinion and not based on anything other than that. Regardless, I was, once again, merely reminding all that if we are going to get this thing to pass, we will have to address the issue of why we think it is okay to dissallow edits from AOL and proxies, et al in articles in which semiprotect is utilized...so are we then actually stating that we essentially demand that only registered users have editiing rights under semiprotection? Because that is were we seem to be pretty close to being. Deeper thought for you.--

3475:. Thus, unlike protection, where there is stress put on the system to return the page to an editable state, semi-protected pages are more stable, receive less vandalism, and thus there exists a temptation to leave semi-protected pages longer than the initial flood of vandalism. Hell, I work on GWB and I can't wait for this to be implemented so that it can actually have a coherent edit history, and I guarantee it will be put on for a long time on that page. Thus, in sum, to answer your question, protection requires no measures to prevent the amount of protected pages increasing exponentially because there simply is no temptation to leave it protected; it's exactly the opposite, as most protected pages have editors waiting patiently for it to be un-protected. No editor will be waiting as such for semi-protection to be lifted, as they only see its benefits. -- 2021:, as I don't know what to do. This talk page takes too long to read, and the proposal page, while pretty good, is boring, imo (no offense to me or the others who created it). With a few minor exceptions, I wrote the majority; I'm pleased that people like my ideas, but it seems like nobody's really paying attention to it. Titoxd came up with the idea of a custom function, and posted a note on the talk page, but didn't realize I had said something to that effect the day before or so on the project page. Not to single Tito out, but people really do need to actually work on the proposal. The beauty of a wiki is that it's living. We shouldn't just talk about it, we should actually edit. If you edit something stupid into it, it can be reverted, so be bold! - 1512:. Sending them to a random article is not a good idea. Sending them to a page of stuff for them to do, look for other articles that interest them (breakdown hierarchy by categories/the way we do it on the main page) doesn't seem like a bad idea. Random articles will only provide to give them another place to vandalize. Further, if a new user sees "view source" instead of "edit" on the top, they will unlikely be deterred. Nobody tries to edit the main page when they first see it. Only if they are expecting to be able to edit will they get the message. I don't think this is the way to go about doing this, we should encourage expansion of our smaller/non-existant articles, or review of other other, watched, articles before continuing. 1020:

with unobservable consequences (restricting legitimate anon editors). Because of this tendency, we must be extra careful in what Splash calls "protection creep", or the tendency for this state of semi-protection to grow exponentially where it almost becomes standard practice. Accordingly, semi-protection should be affixed with a renewable time-limit, and the longer a page is semi-protected, the more admins required to validate such a request. If we make it so that leaving pages semi-protected requires an increasing amount of admin concensus along with forcing semi-protection to be renewed, it should help stem such "protection creep". As it stands, the following is what seems to work so far:

1367:

random article button or the community portal to-do list. After validating whether or not it is technically feasible from a software standpoint, it might be beneficial to still keep the "edit" button active rather than "view source" in order to provide a more detailed response if a new legitimate user clicks on "edit", in order to maximize the probability that the user will not be dismayed by the inability to edit the semi-protected page. This is the implementation that can allow for the previous suggestion of listing all the semi-protected pages so that one can see beforehand what pages are frequent targets so that they don't happen to choose yet another semi-protected page.

3514:

creep in the amount of semi-protected pages is insufficient. What if we have a good-intentioned admin who sees it different as you, and wants to semi-protect a moderately vandalized page for a long period of time? Do they deserve to get "roasted" if they simply disagree with your assesment? Remember, there is absolutely no physical evidence besides a lack of vandalism that warrants a page from becoming un-semi-protected, so it will be highly subjective as to when admins feel that a page should be un-semi-protected. If we use your lack of specificity in sp's application, than neither of you would be wrong. --

294:(for some variable setting of X). Most wikipedians seem to support allowing anons to edit, but I don't think the community would be too upset if they were prevented from editting a small number of pages that are heavily vandalized by anons. Similarly, we already have code that forces people to wait several days after registration before they "earn" the right to move pages. Also, even if we have a message explaining that one's account must be X days old before editting a given page, that doesn't really encourage a vandal to go attack something else (as the current proposal might). 2844:

with. I would be very surprised if there are not people whose job it is to alter pages to read their way, particularly pages like George Bush. Then, people who feel agrieved, who are simply determined to make a mark. The simplest way to remove something would just be to deface it, particular if they could not get consensus. These people are unlikely to be deterred by a simple scheme to discourage random visitors who fancy a laugh, but will jump whatever hurdle is put in their way. So the effectiveness of this scheme might depend on how many of these full time vandals there are.

2416:

the more radical bug that was discussed that would have prevented all unregistered editors from editing and naturally backed away from that as it was unwiki. I was merely voicing that if semiprotect is going to eliminate proxy or AOL users from editing without registering that we may have trouble getting this accomplished. It's not a matter of how many articles we utilize semiprotect on, it's the limitations it may impose on some editors by demanding they register. I am a

31: 1051:. POV disputes and edit wars should still be solved by protection until the talk page can restore some order. If we semi-protected in certain cases, it would allow certain users to edit while others couldn't simply due to their edit history, which given the lack of vandalism by these new users is fundamentally unfair to them. In these cases, POV disputes can last anywhere from a day to several weeks. In the case of vandalism, 1258:

something like (1hr, 1days) would be a more appropriate level. At most something like 3 days if there is really obvious sustained vandalism. AT the moment, vandal are annoyingly common because it is JUST SO EASY to mess up wikipedia. I think that with some apporpriate levels, vandals will find it isn't so easy to cause trouble and they will just go away - so i don't think that long term measures are needed.

1749:

process. But this thing with minimum admins and such just has so many holes. As I argued earlier, we'd need to literally set up a committee to do this if we were to have minimum #s of admins needed for each step. I love our admins, but they all do different things. There is just no way to guarantee participation. Hell, even the ArbCom typically has half of their membership inactive at any one time. --

154:Ævar, we are still in the middle of figuring out exactly how semi-protection should be implemented, but assuming we come up with a reasonable working proposal and get somewhere in the range of 100 signatures supporting it, what chance do you give this proposal getting through? Would the support of Mr. Wales in the matter make any headway towards getting this implemented by developers? -- 379:

so far and re-focus the debate. You can place a support vote if you agree with the way a certain passage is framed, or discuss why you believe it should be a different way. Also, don't be afraid to put your signature under the disagree part, even if its a little minor tweaking, as this isn't mean to be a vote whether the certain aspects "passes", but to polish the concepts down. --

3443:

creep i'm referring to is the amount of pages semi-protected exponentially increasing, not the intensity of the semi-protection applied on these levels. So far, we know that the temptation exists to use semi-protection in an indiscriminate manner, yet without time limits, you have not provided another solution that will help stem the increase in semi-protected pages over time. --

1133:. I do think it should have automatic expiry time limits. But further to comments earlier, i think it should be easier to remove than to impose. I think that any single admin should be able to remove it. Now arguably, any single admin should also be able to reinstate it within the original term for which it was imposed. This would allow people to test remove it. 2449:@MONGO: I can argue both sides of a debate! There seemed to be no-one here disagreeing with the proposal, and that's unhealthy. I will continue to be hard work where I think deeper thought is required. My grilling was laying out all the possible concerns with the proposal. I hope people have considered them. They seem to have. Protection of any kind 241:

edits, but if semi-protection amounts to "You can't vandalize here, go vandalize somewhere else", I'm not sure the encyclopedia is really any better for it. Of course, if one doesn't explain what is going on then you end up with a page that looks perpetually protected from the point of view of random visitor (or worse, random visiting journalist).

3653:

reason it is simple is not sufficient. The reason why we're in this mess now is because someone early on only conceived of a page being fully editable or not editable at all, without taking into consideration heavily visited pages that would be vandalized. Let's not make the same mistake and do something stupid purely in the name of simplicity. --

3497:) should be able to oversee the process ok. An admin who leaves a page SPd for longer than necessary will be fixed up by another one. Honestly, we admins are moderately capable folk. Those admins who see an opportunity to use this is a means to reduce anon editing should be taken out and shot. Which they will be, fairly publicly, on 3052: 3002: 2620: 2563: 1694: 3467:. When a page is protected, there are obvious visible consequences, in that no one can edit the page, and little benefit, in that it's a means to an end for the page to return to order. There is also a "ticking clock" initiated by the editors involved in the page, as they want to get back to making the article better. 3095:

approves all pending unproven edits, or rolls back to the last proven version respectively. I realise that doing all that would probably be even more work than the semi-protection proposal, but it might give the benefits of semi-protection to all pages without blocking anybody from making genuine contributions anywhere.

3180:, which uses a less sensical ordering of the same words. It doens't matter what it says, it's who it restricts that matters. Semi-protection will alwasy be indefinite. GWB won't be president forever, and the community is unlikely to support even semi-protection on an indefinite basis away from the Main Page. See 419:. Also, Levels 2 and 3 will require the person to be logged in, as both the minimum edit and account life thresholds become meaningless in the face of the mass of AOL IPs being used by various people. Alternatively, Level 1 can also require just simple registration as a first minor defense against vandalism. 4048:

will increase server load; no idea how much. A small difficulty would be getting the past edit counts at the point this is set up; it might slow the system down a lot when people first log in on the new system and the long-winded editcount query has to be run for each one; but it would be a one-time problem.

4047:

This may be how it is at present (I'm not quite sure), but it surely doesn't have to be that way. For instance, give each user an editcount field in the relevant database table, and update present count+1 every time the user does an edit. It's one extra read call, one extra write call per edit, which

4032:

Actually, calculating if someone is in the latest 1% of users is as simple as performing a single database query (getting the date of account creation from the users db). Calculating the total amount of edits from a user could potentially take hundreds of database queries. The new guideline is much

3991:

it happen, rather than put forth shoddy policy. Concerns over realistic constraints such as execution time are valid, but if that is purely because the current way just needs to be re-done, then that's not a excuse not to do it. If we get this policy hashed out and get around 100 support signatures

3754:

Right, but asking for a user-supplied edit count / account life threshold is virtually no more work (and no more execution time) than if we supply standard hard-coded entries. Did you see the previous proposal that different wiki implementations might want different thresholds of vandalism? We need

3690:

Splash is right, she and I both know this due to our involvement with Knowledge and the amount of time we spend reverting vandalism day in and day out. Whenever I review a vandal's contribution history, they generally hit 5 or 6 pages before they are finally blocked. You would be surprised to learn

3382:

indefinetely? We have no policy that would state otherwise, and he'd be as right as you are. This is highly ironic coming from the person who highlighted the importance of addressing "protection creep", now you are completely ignoring any attempts to account for such a possibility within policy and

3201:

Semantics matter. Full protection is always temporary and does deal with vandalism, at a cost. What doesn't matter is the fact that most of the community often won't support semi-protection, because they won't oppose it strongly. Whereas the minority who do want a page semi-protected will feel very

2843:

I thought I posted this last night, but maybe i forgot to save it. Has anyone considered the issue of people whose business is to make bad alterations to wiki? The higher profile wiki becomes, the more people are going to be paid to sit around all day altering articles which their bosses do not agree

2177:

How did we get to "all unregistered users from editing that page"? I thought that we were only trying to ensure that there was a minimum number of edits before the editor could then begin his/her contributions to tagged articles. Unless there is a software or development reason why IP's must register

2000:

I was just editing the page, but stopped, because I was worried about different levels. Should we have only time be a factor? And if so, should level 2 be the newest .5 or 1% of users, and level 2 be the newest 1 or 2% of users? And just ignore edits in total, not even 10 or so? I dunno, and it seems

1551:

with something added that says something like "If you are new to Knowledge, click here to see how to edit pages" or something like that. I also wouldn't mind a reason in there as to why the page is semi-protected or a link to a reason. Something informative, but that doesn't sound like we're stopping

908:

I agree with Splash (wow. again). I think one level would help put the kabosh on protection creep, which I know Splash fears. Like I said, this isn't in stone. We can always alter it later if it is not working out. I say...20 edits would work. I just don't see the strong argument for multiple levels.

325:

I like this proposal, but it occurs to me to wonder if anyone has tried to determine what the necessary threshold for semi-protection should be. i.e. of vandalism done to the GWB page, how many of those vandals had already performed edits on other pages? How many had 10 edits under their belt? How

127:

Oh, I wasn't mocking you, just figured that something involving money would impede the progress of this. I for one, am much appreciative that you've chimed in here...thanks! In the event that this is "deemed important enough", how complex a matter does this become and what kind of potential timeframe

3704:

But why limit yourself to one level? Just like the proposal to make the tool variable itself because of different wiki implementations, we should think about scalability and the future. One level simply doesn't make sense as there will be different situations with a different amount of vandalism.

3513:

But those aren't observable consequences, they are only inferred. I just think that the lack of specificity you are proposing to wrap around this powerful tool is going to bite us in the ass. I think simply relying on the threat of an admin getting "roasted" at the noticeboard to combat protection

3329:

Any good admin shouldn't be thinking like that. They should be trying to have as many people edit a page as possible. It has a directly detrimental effect to the way the wiki works. There is nothing to stop Admin B from unprotecting Admin A's protection at any moment they think fit. The system works

2415:

On the one hand you seemed opposed to the implementation of this semiprotect with your grilling and seeming indication that it is unwiki while now you seem to support it. That doesn't make sense. I am well aware of the protection guidelines. I was merely stating that I actually at one time supported

2402:

Also, full protection already prevents anons editing, so this is no different. And, of course, this is only for short term protection against vandalism, so they'll be able to edit the article again soon. Noone is suggesting, or I hope no-one is suggesting, permanent protection of any article by this

1748:

I wholeheartedly endorse this. I can see kizzle's ideas working too but I feel like this idea of Splash's is the most feasible to start with. If it feels like we need more rules and such, we can add them later. Start simple, not complex. I mean if we get overloaded on the RfP page, we can change the

1019:

It has been asked why semi-protection, a less restrictive practice than normal protection, requires more scrutiny than protection itself, which can be executed by any admin. It should be fairly obvious that leaving pages in a semi-protected state has clear observable benefits (no vandalism) coupled

986:

The only part that strikes me as excessively creep-ish is the definition of multiple levels. I'd say just strike out "Level 3". I suspect (or at least hope!) that Level 2 would dramatically reduce the amount of drive-by vandalism. If it proves to not be as effective as we'd hoped, then we can either

942:

That's actually something I hadn't thought of either. Could people be blocked indefinitely for doing something like this, i.e. try to get around the threshold rule by making minor or bad faith edits in as many places as possible or do one edit on the first day and then wait a few days until they are

920:

I think that having lower account life numbers would achieve the aims. Even something like 1-2 days account life would be a pretty big bar against vandals (usually won't have the commitment to create an account, wait a couple of days before vandalising -- esp. if the account gets killed by an admin

293:

Might I suggest that if one is going to be asking for software changes, it might be easier to create a semi-protection policy based on account age. In other words have some semi-protected pages that can only be edited by registered accounts, or accounts that have been registered for at least X days

267:

Also, it is unclear to me whether you want this to apply to anons and registered users alike. If it applies to all, then the AOL superproxy system would make it often ineffective against this large class of (often irritating) anons who share IPs and hence would often already have a significant edit

3986:

I have absolutely no idea why Jimbo isn't participating in this discussion. It's not like this is a fringe debate over a technicality in Knowledge, this should have been considered from the very beginning given Knowledge's increasing amount of visibility within the public. I think we should do it

3880:

Regardless, we probably should have both an edit count check along with a time limit, so whether that time limit is a certain number or simply the amount of time that equals the newest 1% of articles, that is debatable, but we do need both checks to be in effect to effectively combat vandalbots and

3718:

is an absolutely, sure-fire guaranteed way of having a proposal fail. A proposal that achieves as much as it can with as little effort as possible has the highest chance of success. Note that the vast bulk of vandalism is from anons. That's all we really need to stop, along with the clever ones who

3573:

Kizzle, you are missing a major point here. We can change this. You have to start simple and then go more complex. You have to start general before you go to the specific. Otherwise, you are handcuffing the admins. What's going to happen if we put time limits in right away is that admins just won't

3129:

The first is just a statement of fact. The second is sort of a promise. Given that semi-protection can be gotten around by any patient vandal (Create an account, let it age for a week, make 50 random edits somewhere), claiming that this "deals with" vandalism is too strong. It probably helps but

2476:

Splash, I don't argue that preventing anons from editing is a non-starter. But the wording in the boilerplate you proposed does indeed do just that. There is nothing unhealthy about no one disagreeing with this proposal...in fact, that is a good sign as far as I am concerned. While recognizing that

1366:

The page will simply have a notice at the top that says this page is a frequent target for vandalism, along with a internal link to the semi-protection policy page. It should also contain one line that directs new users somewhere else where they can help make Knowledge a better place, possibly the

1233:

Hard time limits don't allow for fuzziness where it may be needed. The hard time limits offered here don't cover anything like the fine-ness we would need. They offer no means of reversing a semi-protection early. Admins don't work in committees because that would be the formulation of a cabal that

788:

must be registered that will deter some of them. Besides, are you really arguing that more options are bad? I'd prefer the least level of protection that addresses the issue going towards none most of the time. Ideally it would be like the block function with some default options and the ability

378:

discussion on Knowledge. I am going to summarize what seems to have been concluded so far as to what semi-protection should resemble, keep in mind I might include certain ideas that you still disagree with, by all means share your thoughts. I just want to summarize the progress that has been made

3652:

I highly disagree with the proposal to have only one level of semi-protection. There are some cases where we want to stem off a tide of casual vandals without going too far, and sometimes we want to stem off dedicated vandals, like at GWB. Why should we limit ourselves to one level, and the mere

3593:

So the thing is that there are alot of checks to this system. Another admin could easily overturn another admin and if there's a dispute, it'll go to the administrator's noticeboard. Users stopped from editing an article due to semi-protection are not stopped from commenting on the RfPP page or on

3583:

I think what Splash is trying to explain is that admins are very good at self-policing. If one of us makes an odd block (like blocking an IP for a month), there is usually another admin there to jump in. If someone makes any odd moves, someone is there. If a page is protected that shouldn't be, it

3430:

additional level only and is only to be applied in cases of serious vandalism: these articles are routinely protected now, and there's no reason to suppose it would be applied significantly more widely. Indeed, the wording is intended to prevent that. The presence of hard time limits significantly

3408:

Read my text on the above proposal about why protection is different from semi-protection in the amount of caution we ascribe to it. Like I said, I was just catering to your good point about the possibility for protection creep. You are completely disregarding such a possibility now, and I still

94:

I was asked to comment on this subject on my talk page regarding the feasibility of a technical implemtation of it. First of all, the expensiveness of figuring out the edit count of a user is currently too large to be able to make that check on every edit (and it won't be any less expensive if the

3782:

I was away while we decided on using the newest 1% of all users. First of all, in my mind, this calculation seems much more complicated than a simple edit count and account life check, maybe a developer would like to chime in on the feasability of either. Second, how is this in any way shape or

3732:

Keep in mind the software aspect of the proposal given to developers is for a completely variable tool. The levels are set within policy of each Wiki implementation. The difference between 25 edits / 5 days is waaaaay different from 100 edits / 30 days, so you are incorrect in saying one can be

3543:

If two admins disagree they either a)Work it out or b)Take the matter to a community forum and try to establish a consensus. If there is no consensus for an article to be protected, clearly it is unprotected (or not protected). Wrapping ourselves in vagueness works excellently because it provides

3094:

But to be honest, I'd prefer to see a system where unproven accounts can edit anything, but their edits have to be accepted/reverted by a proven account before being displayed publically, or at least, before any other edits are made to that page. Accept/revert could be a single click that either

2453:

unwiki, and I would not want to see this proposal used widely or have too many different restrictions that can be placed on editors. To that end, my boxed idea above reduces the usage to handling simple vandalism, which is from where it originated, and increases the restrictions only so far as is

2250:

Oh, don't misunderstand me as I am in support of this proposal and even the more radical bug in which Kizzle and I fought to try and see if we could demand that only registered editors be allowed to edit pages. I have since altered my viewpoint on the latter, but am concerned about the wording of

1257:

In my view, Semi-protection should be used as something as a brake against specific 'runs' of vandalism (e.g. GW Bush says something controversial and then every vandal and their dog appears to vandalise wiki). As such, I think that SemiP should have flexible (non-fixed) durations. I think that

357:

Frequent vandals who have racked up an edit count with a registered account are easily traceable and blockable. If an account has 100 edits and all of them are vandalism, it should be a no-brainer to an admin to indefinetely block, thus we shouldn't see too much of a problem with this concerning

251:

If a user is blocked from editing something a clearly defined reason must be given. Personally I think partially protected pages should scale on account creation date as well as number of edits, so if you have some newly-created vandal they'd have to wait a month and survive through 50 vandalism

3442:

If a semi-protection is terminated early, I have absolutely no problem with that. My problem is semi-protection becoming standard practice and thus becoming a permanent fixture on articles that really don't need it. The amount of levels is irrelevant to the possibility of protection creep, the

2429:

Yes, they MUST be logged in, otherwise many people can edit a semiprotected article no matter what. IPs tend to accumalate randmom edits, by many different people. Not sure what I think about the "newest percent" plan, definetely worth a try if it is easier on the servers. Remeber it should only

770:

The question is: would it be temorary? Let me guess; the first thing you did here was register? No. We all were annonymous at some point (with the exception of maybe Jimbo and the founders), and there's no reason to exclude anons from editing, while allowing new registered users to edit. It just

304:

This also sounds good to me. I think is a lot more doable (in terms of coding) than keeping track of number of edits. Frankly, I'd just be happy if there was a "Protection against Anonymous peoples" that we could place on a page, as that would solve the vast majority of vandalism. --Cyde Weys

240:

seem to favor offering a clear explanation of the situation, but doesn't that just tell the vandal that he has to go attack 10, 20, 50 other pages first and then he will get rewarded by being able to attack GWB? Okay, so maybe we would catch and block most such vandals before he got to 20 or 50

3613:

The benefits of semi-protection are local. The costs are thinly spread. That's a recipe for creep because it means that, for any specific page, the people who want it are much more motivated than those who don't want it. I really don't see how time limits could be enforced? So I don't think

3108:

No. There is no content review process on Knowledge other than open editing. Instituting content review is a complete departure from how we edit. There will be an article validation feature switched on in January, and that's as far as we're likely to go. I don't see the point of the alternative

1622:

Semi-protection will only be applied if the page in question is facing a serious vandalism problem. It is not an appropriate solution to editorial disputes of any kind since it may restrict some editors and not others. Administrators will thus apply semiprotection in the same manner as current

2680:

In my opinion: absoultely not. Keep it simple, for goodness sake! We're not trying to hamstring new editors. We're just trying to reduce vandalism a bit. And what you are asking for would require significant changes to the MediaWIki engine which does not, at presesnt to my knowledge, have any

2390:

MONGO, most AOL IPs have hundreds of edits. Why would that mean anything in terms of them being an established user? IPs are shared, and widely in some cases. A vandal who has never edited before could come along and edit on the back of other people's work, and probably on the back of other's

2238:

They would not be allowed to edit semi-protected articles, yes. I myself think the anons should be allowed to still edit it if they've performed a certain # of edits. Again Mongo, we'd be talking 20-30 articles, if that. And as has been said, you already have to be outside of the newest 1% of

1836:

On second thought, limiting access from the newest 1% would probably work better than N number of edits for the majority of vandals. If someone is willing and dedicated enough to wait it out for ~4 days to create a malintended sleeper account, then they will probably find a way to get around

976:

I support the idea but I think the restrictions should be minimal and the process should be as simple as possible: start with exactly one level of semi-protection. I would prefer to see it start with even a 1-day account history, assuming that most vandalism happens spur-of-the-moment and on

414:

The minimum account life is meant to address the possibility for vandalbots to rack up edits in an incredibly short time, while the minimum edit count allows us to view the history of a user and see if they have made any significant contributions rather than exclusively committing vandalism.

393:

From a software standpoint, semi-protection will have built in variability to address different wiki implementations. It has been brought up before that different wiki implementations may want different thresholds to combat vandalism. However, policy will dictate its usage by admins in the

2228:

At some point, to get this through it is going to take massive support and my bet is that Jimbo will oppose it, although I may be completely wrong, but if does not support it, it probably won't happen. I may be confused but the proxies and AOL won't be immune but will probably be completely

329:

It also doesn't seem to take into account the fact that frequent vandals will have lots of edits to their name anyway; they will just have been reverted by other users. I don't know if there's a good way to take that into account when totting up someone's edit history, and distinguishing a

1481:. If I had turned up and wanted to add something to george Bush, I doubt I would be impressed by being offered a random article to look at. Better take people to something telling them about wiki and what they can do. Yes, certainly it must explain that the page has been protected and why. 1801:

Even in a KISS world, and I do see some virtue in that, I'd like to restate my preference for account age rather than edits as the deciding factor. If a vandal comes along and gets told all he has to do is go vandalize N times somewhere else... well it only encourages other stupidity.

3680:

how do you know that? I find it extremely surprising, and someone else above posted they knew a case. But even if there aren't, there will be as wiki becomes higher profile. But I would be absolutely amazed if there were not. It is an obvious thing for politicians to do to articles.

1535:

We shouldn't be trying to obscure out editing practises by operating with smoke and mirrors. This is not our wiki. Don't slap messages on articles that amount to saying "this article is usually rubbish — oh, and we don't think that you can improve it for us, we have better people".

3130:

that's all. As noted above, it may make things worse because it might just move vandalism to pages that aren't watched as closely, especially if the reward for vandalising 50 unprotected pages in subtle ways or at high speed is that you then get to vandalise semi-protected pages.

3742:

Well, in my mind, all we ask the devs to do is provide a single level of SP. The less we ask for, the exponentially higher our chances of having the wish granted. I don't see any need for multiple levels, and protection creep up-the-scale actively disuades me from supporting it.

2976:

We're not putting hard numbers on it, but I think that it would more or less replace the need for full protection in the case of vandalism, since most such attacks are anonymous or from very new accounts. So about as often as we currently vprotect things and for about as long.

943:

cleared? It's important since you know at least one person will try it. I don't think it'll happen alot since I agree...most vandals are fly by night...they come...vandalize...and leave. But we'll have a few who will try to get around the semi-protection one way or another. --

4072:{starting over} Agreed. If Jimbo wants to come, he'll come. Otherwise, someone might want to e-mail him, or IRC him with some general info, and see if he wants to get involved. Otherwise, I've been spamming people who've reverted vandalism on GWB with my own template, 1567:

linking to the "Request for…" page from the main WP:Semi-protection page. At the point where you have to click on the Semi-prot link and read it far enough to understand that the time limit is on the Requests page, you've surely defeated most of the drive-by vandals.

1333:

Generally acceptable in spirit, in that I think any time a page is semi-protected, an end date should be indicated (though not necessarily on the page itself); however, the comments here have convinced me that the suggested duration categories are not a good thing.

167:

and AFAIK not a single line of code has been written to implement that. Talking from experiance, if you want something done with MediaWiki (or any other voulenteer project for that matter, including Knowledge) you basically have to do it yourself or pay someone to.

3333:

Simply by limiting it to dealing with bouts of vandalism, the same way we do at present. That usually only lasts for a few hours. In the case of George W. Bush, well, you're all just overreacting a bit...at the moment, the vandal rate is way down owing to other

855:. Don't I just love to sit on the fence? I support it strongly as an alternative to full protection. Less strongly if it, say, doubles the number of protected pages. not at all if it results in many more pages having more then the 25 edit level of protection. 2886:

I like this new N%(1-3 or so) idea. Why? Because both version stop vandalism to the protected article, BUT this version will not encourage vandals to rage through other article's first. Less vandalism=better. Can we get a developer now...lets try this

1634:

Requests to lift semi-protection should generally be unnecessary in the same way that unprotection against simple vandalism at present is generally swiftly seen to by either the protecting admin or another. Generally, a simple note to the talk page or

2073:

Agreed. Sorry I'm a little cranky, it's past my bedtime (it's 2:19 here). Should I edit the proposal with the changes in mind, or do you want to? And yes, Woohookitty, you did. Thank you ;). I really need to get to sleep soon, big day to me tomorrow.

3368:

You're putting way too much faith in the admin's role. This isn't crafting policy, this is a recipe for ambiguity in sp's application. "Any good admin" is not how one creates policy, nor how WP:NPOV or any other policy was created. The temptation

3219:

There are some major problems with content review. For example, what if an anon proposes a change, and someone else actually changes the page before the proposed change gets reviewed, in a way that would require the anon's proposal to be refigured?

2936:

I'm just reading this talk page right now, and I haven't gone through everything yet. But just how often do we plan on using this feature, if it is enabled? If it is only for a handful of articles, it does not seem to be worthwhile to implement...

3246:

I imagine that in order for someone else to start editing they have to either accept or reject the change. Unless they themselves are unproven, in which case their changes would 'chain' and the next reviewer will have to accept/reject the lot.

1043:

Note: Semi-protection can be applied consecutively, such as an admin extending an initial week-long semi-protection for another week. However, after 2 consecutive semi-protections, the third attempt must gain a concensus from 5 admins as well.

3383:

just "trusting" that admins will use it properly. We are not here to craft a simple proposal purely for simplicity's sake and put it through a test run if we can conceive of highly possible scenarios where its implementation would run afoul. --

1826:

It's the newest 1% of accounts and on en.wikipedia that amounts to ~4 days. Assumming this is only going to be used for short durations, there won't be much advantage to sleepers since the protection would be over after a few days anyway.

896:

We should have only one level of intermediate protection, to avoid unnecessary stratification of editors and articles. Either we trust people to edit, or we do not. And we do, until Jimbo or the Board of the Foundation indicates otherwise.

3501:

and the like. A public roasting can achieve quite a lot. GWB may be long term semi-protected, but that can be effected by a discussion on AN/I like we had the other day, that doesn't come out resolutely against the idea (as that one did).

1846:

Honestly, it doesn't matter to me either way. I think either way is workable. Only problem I have with doing it by how old an account is is that would mean anons could not edit the semi protected pages, correct? Or am I missing something?

1245:

For once I agree with Splash. :) As someone who works on RfP regularly, I am really iffy on time limits. We just need as much wiggle room as possible. I still say that we try this out for a month or so first before we try ANY time limits.

340:

The main problems are from anonymous users, which would be blocked totally under this proposed system since their edits can't be tracked. If vandals are actually registered users then they become a lot easier to deal with. --Cyde Weys

3337:

We don't do specific criteria. We trust to the goodness of human judgement on what is a very simple question: "has the vandal gone?" If so, unprotect. In a conflict, we decide on AN or AN/I or talk page as at present. No need to change

3431:

reduces the usefulness of the system, as I described in the section much further up: rarely will one of the options be what I want. Also, any admin can reverse me at any time as with all admin actions, so the limits won't hold up. -

3484:

The observable consequences are that some good new editors and all anons will be unable to edit the page. Both things are bad, as a matter of Wikimedia Foundation doctrine. Once admins get used to SP, which will be quite quickly,

3283:

I was thinking of that. I think the 'best' metric might be something like one day after the 50th edit. That give time for the edits to be evaluated by other people plus it potentially reduces the load on the servers. Regards,

1140:

Auto-removal will not work, simply because it's better to have a human make judgement calls. I was thinking the same thing you were, but there's a reason we don't have regular protected pages automatically unlocked like this.

932:

Thats an interesting point: is it intended as a means of seek and destroy of people only making bad-faith edits before they get to/as soon as they get to the magic threshold? And how would someone decide how to nuke a new ID?

4057:

The number could be cached and recalculated at regular intervals. It's probably a good thing if there is a delay between the 50 edit and granting of trusted status. Which raises the question, how do we 'untrust' a user?

373:

I have been immensely impressed by the discussion above; I'd just like to take a second and thank everyone for their wonderful ideas in fleshing out this sorely-needed concept. I don't think I've ever been part of a more

1370:

In addition, it is important we do not mention how long the page is semi-protected for on the notice, as it will encourage vandals to wait until the semi-protection is over. It will still be determinable by going to the

1915:. I think that it is a very valid proposal, in particular as I have deal with this kind of vandalism on a daily basis in RC patrol. I would side with the distinction of newest account rather than on number of edits. 3594:

admin's user pages. As long as we specify that this is to be used only for severe vandalism, I don't see it getting out of hand. And again, if it does, we can address it later. Start simple and go from there. --

3373:

exist, and you can't possibly say that most admins are "good" so we just shouldn't worry about it. Protection is incredibly clear cut, as one can see evidence for its removal in the talk page. Semi-protection

3392:

How is this different from the current full protection? One admin applies, another removes it. Job done. If an admin wants to permanently semi-protect an article, they're going to have to defend that desire on

2762:

Splash, you are an admin. No one can tell you what to do! lol Yeah. lol I'm glad we're making progress on this. It won't cover alot of pages, but I think it's a very important proposal for us vandal fighters.

2486:

No, that's not what I said. When a page is protected at the moment, anons can't edit it. The same would be true of semi-protected pages. It doesn't change the status of anons with regard to protected pages.

2724:

So that everyone knows up front what the status of the article is. We edit and operate openly here, not secretively. At present the protection notoice is shown to absolutely everyone. That should continue.

2858:

article. The level of POV being pushed there was well beyond that of a strong minded person, and a number of us there commented that it definitely appeared to be the work of a paid blogger or the like.--

2744:

an article should be distracted by the mechanics of how the article is being edited. By all means, make the info easily available; but separate. An obvious way is to only show it after Edit is clicked.

2714:

I don't see why that message should be displayed to everyone reading the article. Why not display it only after "edit" has been clicked, if the user attempting to edit is affected by the restriction?

2351:

MONGO: As Woohookitty has already said, only registered users who are among the oldest 99% of accounts can move pages. This is exactly the same restriction, just on a different but similar prospect. -

1841: 3719:

work out that they need an account for a few minutes to have fun. There's no difference between 25 edits and 100 — I can game one just as easily as the other. Just as easily as I can game 1%, too. -

1563:

Generally the right idea, but I agree with others here that the "go help somewhere else" link is not constructive. I'm also not sure I see much value in the extra level of obfuscation afforded by

3353:

I think we would have protection creep (in terms of number of protected pages) whether we have infinite expiry or not. At least, unless we have some limit on rolling semi-protection. Regards,

2420:

of this proposal and am not trying to be obstructionist, just bringing the issue to the forefront having previously dealt with the issue of registration as a requirement of editing priviledge.--

1402: 973:'s idea, I also think that there should be a "no blanking" and a "no linkspam" category to specifically prevent blanking or linkspamming. Those are two of the most common forms of Wikivandalism. 3881:

for other people who simply register an account, wait a few days, then start vandalizing. We want them to both wait and have to make valuable contributions before they can edit these pages. --

2187:

Wasn't that the point of all this? If not, AOL users and children behind school proxies will be completely immune to semi-protection, which would defeat the entire purpose of account aging.

1794: 1078: 442: 2299: 2209: 2191: 1815:

was/is unavailable to the newest 2% of accounts. At one time, this resulted in Willy on Wheels setting up sleeper accounts, but any numeric threshold is gamable one way or the other. -

3556:

I am still unconvinced. Your proposal simply does not in any way attempt to address protection creep in the amount of pages protected. Without any limitation to semi-protection, it

4001:

Because Jimbo is a very busy man. I'm not sure that innundating his page will do anything but keep him away from this. If he's interested, he'll come. Otherwise, this is up to us. --

3817:

to see yours), and then, that number is compared with the number of accounts created (there is a MediaWiki variable to find that, but I don't remember which one... it is visible on

3755:

to try and address scalability so that we don't make the same mistake as the first person did in assuming we only need an editable/non-editable dichotomy for article pages. --

2205:

Correct me if I am wrong, but isn't this something the entire community should decide upon, and not just Jimbo? It seems like there is plenty of support behind this to me.

491:

This isn't a vote. He can choose to sit on the fence if he likes. The weakness of voting is that it confines one to the options and prevents one thinking in shades of grey. -

3138:

Addresses the question of 'why this page and not that page'. Says that semi-protection isn't for just any page that cops vandalism, but only for those that really need it.

2161:

I would make one general comment about account age: 1% or ~4 days will often be a much higher bar than, say, 20 edits would be. It would be nice if I could edit everything

1971:

Care to change the text on the proposed policy from editcountits to the new proposal? It wil remove many of the objections stated and will go long ways to gain acceptance.

1760:

Hopefully, no more requests for SP will go through RFPP than do requests for urgent protection against vandalism at present. I presume most such protections originate from

3951:

Titoxd beat me to it. The devs aren't going to implement this anyway; they don't respond to requests, but we might at least persuade some newbie-dev-to-be to take it on. -

728: 3853:

4 days has been indicated above, so you're in the same ballpark. It will decrease over time, of course, so we might need to fix the number of days rather than the %age.-

3633:

clearly I have a different interpretation of what semi-protection should be, so i'm going to stay out of this. you guys hash it out, I'm going to take a step back. --

3937:

We want to do it the way it gets done. If we require a change in the MediaWiki implementation, that is a sure way of getting our request way on the back burner... :)

4082:(always subst'd), if you want, go ahead and use and even modify the text, I don't mind. As long as we can get as many people here as possible to chip in. Thoughts? - 1295:. I'm in agreement with Splash that hard time limits are bad, but should this be a general guideline? Sounds like we should have something along these lines in place 81: 76: 71: 59: 2740:. This is one of my more fundamental gripes about Knowledge - it too often assumes everyone wants to be an editor. I see no reason why someone who merely wants to 2454:

absolutely necessary. Nothing fancy, nothing that filters users against one another more than we have to, and nothing that will be left in place for very long. -

2200: 2001:

like the entirety of the editing his happening here. Like good Knowledge users, everyone's using the talk page, but unlike good wikipedia users, nobody's being

1853: 808:. Should we semi- all pages linked from high traffic sites? No. We should watchlist them, at least temporarily, as a way of encouraging new users to our site. - 3663:

There are no dedicated vandals at GWB. They all just drive by and carry on elsewhere. Temporarily protecting against brand new accounts and anons (rather than

236:

I am wondering what the people hear want the user experience to be like when visiting such a page. Either we explain that it is semi-protected or we don't.

177:

True, but we could recycle a lot of code from the page move function and using it in the semi-protection functions, so it isn't that radical of a change...

2854:

That is where we would be forced to implement full protection. It is already going on and I helped fight what definitely looked like paid spammers in the

118:

Note that the comment only applies to the current code and DB schema, if this was deemed important enough both could be changed to accommodate for it. —

3378:, thus there will be no standard of when it gets lifted, and some admins will want to keep it for a long time. What if an admin wants to semi-protect 1379:

page, but if the page isn't directly linked, the vandal must already be pretty familliar with Knowledge to figure out when the time limit will expire.

909:

I mean. If this is going to be limited (30-40 articles at most), why divide it in 2? I mean, I think it's only going to be used for severe cases. --

3303:

I see that some people are opposed to having limits set on the amount of time a page is semi-protected. For those people, I have a few questions.

3313:

What specific criteria warrants a page to be un-semi-protected? Will this criteria be variable between admins? How will we decide in a conflict?

2295:

It's a much better solution than preventing everyone from editing an article during a vandalism attack, which is what we're faced with right now.

3082: 3032: 2654: 2600: 1724: 697:

been used and only 40,000 have made more than 10 edits. In other words, we already have vast numbers of one time (and no time) use accounts.

3804:

By the way, in a test case scenario, can someone tell me what threshold is the newest 1% of all accounts? How many days is that currently? --

761:

How is having the option to temporarily exclude anons anti-wiki? It would still be weaker than any of the other proposals being made here.

237: 47: 17: 3307:

Do you recognize the temptation for many admins to leave a page semi-protected, as it has observable benefits and unobservable consequences?

2251:

registered accounts, and I have doubt that this will happen...they'll be crying that it is unwiki and have a valid point in that argument.--

169: 146: 119: 100: 2465:

Protection against anons is a non-issue. We do it already. Preventing anons from editing completely, on the other hand, is a non-starter. -

2296: 2206: 2188: 1838: 1791: 1399: 1075: 439: 3078: 3028: 2650: 2596: 1720: 278:

Anons shouldn't be allowed to edit partially protected pages since there is no way to keep track of their number of edits. --Cyde Weys

1682:, but this is clearly the simplest way to have semiprotection operate. The v.01 proposal fails owing to being laden down with too many 1047:

It has also been asked why semi-protection has a proposed time-limit as well when normal protection has no such limit. Keep in mind,

95:

user has fewer edits). Secondly, although our current page restriction scheme could be hacked to support it we'd really need a proper

3146:

I doubt that semi-protection will always be temporary. The word "currently" allows for it to be temporary or permanant, as desired.

780:

Actually yes, I did register before I editted anything, but that's just me. Imagine someone posts: "Go kill Knowledge's entry about

1775:

Hard to tell. We get 1-2 protection against vandalism requests daily. So yeah...probably RC Patrol starts the most protections. --

977:

impulse. The numbers can always be adjusted upwards, or new levels of protection added, if it does not put a brake on vandalism.

3060: 3010: 2628: 2571: 1702: 649:(I think the numbers could be played with, but frankly I think it would need to be road-tested to determine the best thresholds). 1532:. Perhaps a link to community portal-open tasks would be nice :-). Moved vote here since I absolutely DO NOT want "random page". 3783:

form superior to a edit count/account life combo? What are the proposed advantages and disadvantages over such a system? --

1372: 2906:

Agreed. Let's go for it! We can even use recycled code from pagemoves, which I love. Anyone feel like contacting someone? -

3793:

The ability to move is usually not available to the newest 1% of accounts, so that particular test is already available. -

1980: 1924: 1623:

protection against vandalism is applied — either on their own initiative or following an alert on an article's talk page,

3272:

and certainly not a specific # (if you state the number to vandals, they may vandalize just to get to the specific number

145:

in this context but rather refers to the execution time of the code required to implement the proposed functionality. —

1933:

Agreed. Down with editcountits. The nice thing is, it can already be implimented; we do this for pagemoves already. -

2196:

That was already shot down, numerous times...forcing people to register accounts to edit will never get past Jimbo--

4076: 4039: 347: 311: 284: 258: 38: 3544:

maximum flexiblity in application and determination. Having a situation where noone is wrong sounds good to me. -

3064: 3014: 2632: 2575: 1706: 1376: 2947:

We're thinking 30 at most, but it will be extremely helpful in combatting constantly vandalized pages (have you

1211:

I don't see why the process should be any different than the current criteria for protecting/unprotecting pages.

3181: 2391:

vandalism. That doens't make sense. This doesn't prevent them editing completely, just on the SP'd articles. -

2062:

See the section title? :) Simple is sweet, and one single extra level will give you everything you're after. -

3839:

If my estimates don't fail me, that is about two days. A user can make 100 edits in the same period of time.

4112: 4102: 4062: 4052: 4042: 4007: 3996: 3979: 3957: 3946: 3932: 3899: 3885: 3859: 3848: 3834: 3808: 3799: 3787: 3759: 3749: 3737: 3725: 3709: 3695: 3685: 3673: 3657: 3637: 3618: 3600: 3564: 3550: 3518: 3508: 3479: 3458: 3447: 3437: 3417: 3403: 3387: 3357: 3348: 3321: 3288: 3251: 3233: 3206: 3190: 3164: 3115: 3102: 2983: 2971: 2941: 2926: 2901: 2873: 2862: 2848: 2833: 2803: 2769: 2749: 2731: 2718: 2706: 2687: 2674: 2544: 2529: 2493: 2481: 2471: 2460: 2444: 2424: 2409: 2397: 2376: 2328: 2268: 2255: 2245: 2233: 2182: 2171: 2146: 2125: 2110: 2099: 2068: 2057: 2046: 1995: 1984: 1958: 1928: 1905: 1864: 1831: 1821: 1806: 1781: 1770: 1755: 1742: 1577: 1558: 1542: 1529: 1509: 1478: 1452: 1433: 1415: 1393: 1343: 1328: 1319: 1292: 1262: 1252: 1240: 1227: 1208: 1183: 1166: 1130: 1109: 1069: 996: 981: 966: 949: 937: 925: 915: 903: 887: 852: 833: 793: 775: 765: 756: 710: 701: 682: 660: 646: 627: 598: 568: 540: 531: 497: 486: 451: 433: 383: 362: 350: 334: 314: 298: 287: 272: 261: 245: 225: 205: 186: 172: 158: 149: 132: 122: 113: 103: 3928:

Only in the current implementation. Do we want to do this right, or do we want to do this the easy way? --

1976: 1920: 2889: 2694: 2519: 2432: 2260:

I agree with Jimbo anyway. Let the hoi polloi edit Knowledge without having to register? Fine with me —

1686:, each of which is something to go wrong and something to object to. Suggested template (note the links): 1645:

This is just for clarification in the discussion here; we do not presently have hard-and-fast rules about

1517: 1456: 1215: 784:

on a message board." Then a bunch of anons surf over. If we can put up a barrier saying that editors of

556: 3890:

That is too taxing on the MediaWiki software. The first section on this page was written by a developer.

3714:

It's a question of what the community will accept and what the devs will implement this decade. Too much

3174: 3085: 3035: 2657: 2603: 1727: 706:

That doesn't make it right... we need to kill a lot of those accounts, but we shouldn't encourage more. -

3379: 1761: 802: 3072: 1972: 1916: 3963: 2828: 2798: 2371: 2094: 2041: 2008: 1953: 1900: 1504: 1287: 1161: 1104: 882: 828: 751: 593: 526: 481: 109:

Hah, I knew it...then we're back to the demanding only registered editors edit and that didn't fly.--

2867:

Yep. Full protection to guard against vandalism would definitely not go away under this proposal. --

1324:

Guidelines in this field are good, but these limitations need to be flexible and not set in stone.

4088: 3974: 3941: 3894: 3843: 3829: 3814: 3667:

accounts and anons) will knock out ~90% of the vandalism since that's where 90% of it comes from. -

2957: 2912: 2539: 2509: 2141: 1989:

I changed the text in the yellow box (in line, so we can still see what else is being discussed). -

1828: 1803: 1657: 1447: 1314: 1301: 970: 790: 762: 698: 679: 655: 614: 295: 269: 242: 222: 181: 96: 3705:

If we stick with 25 edits, that's easily surmountable. 100 edits is too much on certain pages. --

3818: 2671: 2265: 1571: 1548: 1412: 1337: 1180: 990: 963: 624: 610: 1583: 1349: 1002: 506:"; so fence sitting is allowed, but discouraged. Sorry if I didn't make my reasons more clear. - 3813:(edit conflict) It's actually quite simple. Every user has an ID number registered (go to your 1049:

the only reason why a page needs to be semi-protected is in cases of extreme or heavy vandalism

214:

Don’t we already do something like this for page moves? Would it be possible to make the check

3692: 3452:

What is there at present to stop the number of protected pages increasing at any given rate? -

3068: 3018: 2640: 2586: 1710: 1325: 663:(but I now think the account-age/account-percentage method is much, much easier to implement) 4002: 3715: 3595: 3228: 2938: 2868: 2775: 2764: 2323: 2240: 2105: 2052: 2015: 1848: 1776: 1750: 1683: 1553: 1436:(although not with the "random" idea, but since that's just a possibility, I'll consider it 1428: 1247: 1203: 944: 910: 641: 200: 164: 4109: 4097: 4083: 4059: 3615: 3354: 3285: 3248: 3203: 3161: 3099: 2966: 2952: 2921: 2907: 2823: 2793: 2366: 2089: 2036: 1948: 1912: 1895: 1499: 1282: 1156: 1099: 877: 823: 772: 746: 707: 588: 521: 476: 1649:

to seek ordinary unprotection once vandalism has passed in the case of a forgetful admin.

1911:

I read these discussions with interest, after being informed of this proposed policy by

687:

logical, but would inevitably lead to creation of vast numbers of one time only acounts

4037: 3682: 3498: 3494: 3486: 2845: 2003: 1640: 1636: 1628: 1624: 1475: 1460: 1189: 1127: 934: 849: 724: 688: 537: 448: 417:

Both of these restrictions are in effect, thus each person must satisfy both conditions

345: 309: 282: 256: 219: 3409:

haven't heard from you how whether or not time limits or lack thereof will affect the

2809: 2779: 2352: 2075: 2022: 1934: 1881: 1485: 1268: 1142: 1085: 863: 809: 732: 574: 507: 462: 2814: 2784: 2667: 2357: 2261: 2080: 2027: 1939: 1886: 1490: 1408: 1273: 1259: 1176: 1147: 1090: 959: 922: 868: 814: 737: 620: 606: 579: 512: 467: 3490: 3394: 1664: 1437: 1307: 3691:

how many times at least one of those 5 or 6 pages is the George W. Bush article.

4108:

Let's wait till we get a bit more agreement before bothering the man, I think.

3993: 3992:

and innundate Jimbo's page with this, I think its priority will get upgraded. --

3971: 3952: 3938: 3929: 3891: 3882: 3854: 3840: 3826: 3805: 3794: 3784: 3756: 3744: 3734: 3720: 3706: 3668: 3654: 3634: 3561: 3545: 3515: 3503: 3476: 3453: 3444: 3432: 3414: 3398: 3384: 3343: 3318: 3221: 3185: 3110: 2978: 2726: 2682: 2536: 2488: 2466: 2455: 2404: 2392: 2166: 2138: 2120: 2063: 1990: 1859: 1816: 1765: 1737: 1547:

The random page idea is a really bad idea. I would rather see a notice like the

1537: 1444: 1421: 1390: 1311: 1298: 1235: 1196: 1066: 898: 652: 634: 492: 430: 380: 359: 178: 155: 46:

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

1552:

these people because we think that they are bad or detrimental to Knowledge. --

4049: 2859: 2746: 2715: 2478: 2421: 2252: 2230: 2197: 2179: 1053:

we will have no specific evidence that will warrant un-semi-protecting a page.

129: 110: 2681:

scrutiny of edits except for forbidden external links. Just make life easy! -

1811:

Yes, that's something that might be interesting. From memory, I believe that

1230:. Lets just cut through the new red tape and keep it like regular protection. 407:

Level 3 (extreme vandalism) - 100 minimum edits / 30 day minimum account life

4035: 3465:

because there is no temptation for protection to stay indefinetely on a page

3310:

If there are no time limits, how do you propose we limit "protection creep"?

2855: 720: 343: 307: 280: 254: 2692:

I actually AGREE with Splash here, that tag would scare me off i I was new.

771:

doesn't make sense. The vandalism from both types of accounts is similar. -

3330:

fine at present, and there's no reason to suppose it will suddenly break.

2526: 1619:% of registered users and all unregistered users from editing that page. 1587: 1353: 1006: 978: 785: 781: 693:

We already have 600,000+ registered accounts, of which only 140,000 have

404:

Level 2 (minor vandalism) - 25 minimum edits / 5 day minimum account life

331: 1055:

This is the central reason for affixing time limits to semi-protection.

536:

if I have to pick one, then I support, but with the reservations below.

252:

edits before they could edit a frequently-vandalized page. --Cyde Weys

163:

Might have some effect but probably not a lot, Jimbo announced in june

3157:

Article validation sounds interesting. What will the new feature do?

1790:

This may be a better first step, keeping it simple is usually best.

678:

How about a 1.5 that requires a logged in user but no other limits?

3202:

strongly about it, so the result will usually be semi-protection.

3051: 3001: 2619: 2562: 2535:

One could redirect to the other, so that isn't really a problem...

1693: 2581: 2011:. I honestly don't know where to go from here, but I can only say 2178:

to be able to edit these tagged pages, then I won't support it.--

2403:

means. Because if they are, the proposal is dead in the water. -

2555:

Why not put into policy something like the following, as well?

3560:

become more commonplace than its original utility warrants. --

2808:

Ooh, Splash, I'm loving the change "many" to "some." Thanks! -

1858:

Anons are excluded from editing SP'd pages in both versions. -

25: 2778:

might be listening!). Thanks for adding it, sans grudge ;). -

1880:

I like it, it's pretty :). Oh, and I like the wording too. -

1459:, but I'll put it on this column instead. I just don't like 3471:, semi-protection has observable benefits (no vandalism) 2239:

accounts to perform moves, so this isn't entirely new. --

2051:

Hey, don't look at me. I edited the main proposal. :) --

1653:

Articles that are semi-protected will be indicated with

3967: 2229:

eliminated from editing without registering to do so.--

394:

following levels for the English version of Knowledge:

2104:

Be bold! :-D I added the proposed template to use. --

1613:edits, and all those without a registered username 1578: 1344: 997: 731:on the topic, which I agre whole-heartedly with. 1375:page, which shouldn't directly be linked to the 1113:(changed to oppose 06:07, 4 December 2005 (UTC)) 3426:no protection creep beyond the minimum. It has 1667:in the same way as protections are at present. 619:I have additional reservations, see below — 8: 4033:more technologically feasible. --Cyde Weys 862:Please pick only one (most likely oppose.) - 613:01:28, 4 December 2005 (UTC). But I DO like 461:Please pick only one (most likely oppose.) - 3170:Meh, it's just semantics and grammar. See 3046: 2996: 2614: 2557: 1688: 218:when trying to edit semi-protected pages? 1033:: Initiated and seconded by another admin 165:that we'd make an API for the KDE project 3987:right, and then gather enough people to 987:bump up the numbers or add a new level. 330:responsible user from an active vandal. 3121:Nearly the same thing, but not quite. 1373:Knowledge;Requests_for_semi-protection 1015:Process for Initiating Semi-Protection 44:Do not edit the contents of this page. 3134:"persistent vandalism" vs "vandalism" 789:to customize it to any other state. 232:On appearances and aging vs. editting 18:Knowledge talk:Semi-protection policy 7: 3823:$ numberOfUsers * 0.99 < $ userID 3109:template, it says the same thing. - 2525:for a teeny bit more clarity? :-) 1039:: Supported by at least (5) admins 24: 2951:the history for George W. Bush? - 1549:protection notice we already have 3733:gamed as easily as the other. -- 3050: 3000: 2774:Psh, you better take that back ( 2618: 2561: 1837:anything else we come up with. 1692: 29: 3825:, then the edit is disallowed. 1674:We can talk about the value of 1599: 1027:: Can be initiated by any admin 3473:but no observable consequences 3125:"Because of" vs "To deal with" 3077:Please discuss changes on the 3027:Please discuss changes on the 2649:Please discuss changes on the 2595:Please discuss changes on the 2297:Can't sleep, clown will eat me 2207:Can't sleep, clown will eat me 2189:Can't sleep, clown will eat me 1839:Can't sleep, clown will eat me 1792:Can't sleep, clown will eat me 1719:Please discuss changes on the 1400:Can't sleep, clown will eat me 1306:03:20, 5 December 2005 (UTC). 1076:Can't sleep, clown will eat me 440:Can't sleep, clown will eat me 1: 3049: 2999: 2617: 2560: 1691: 1631:or some other relevant page. 921:after one/two vandal edits). 369:Semi-protection proposal v.01 4113:10:46, 5 December 2005 (UTC) 4103:06:26, 5 December 2005 (UTC) 4063:10:46, 5 December 2005 (UTC) 4053:09:10, 5 December 2005 (UTC) 4043:07:03, 5 December 2005 (UTC) 4008:06:20, 5 December 2005 (UTC) 3997:04:52, 5 December 2005 (UTC) 3980:04:52, 5 December 2005 (UTC) 3958:04:48, 5 December 2005 (UTC) 3947:04:47, 5 December 2005 (UTC) 3933:04:35, 5 December 2005 (UTC) 3900:04:22, 5 December 2005 (UTC) 3886:04:11, 5 December 2005 (UTC) 3860:04:08, 5 December 2005 (UTC) 3849:04:07, 5 December 2005 (UTC) 3835:04:05, 5 December 2005 (UTC) 3809:04:01, 5 December 2005 (UTC) 3800:03:40, 5 December 2005 (UTC) 3788:03:36, 5 December 2005 (UTC) 3760:04:00, 5 December 2005 (UTC) 3750:03:55, 5 December 2005 (UTC) 3738:03:53, 5 December 2005 (UTC) 3726:03:49, 5 December 2005 (UTC) 3710:03:45, 5 December 2005 (UTC) 3696:18:50, 6 December 2005 (UTC) 3686:18:41, 6 December 2005 (UTC) 3674:03:35, 5 December 2005 (UTC) 3658:03:32, 5 December 2005 (UTC) 3638:06:49, 5 December 2005 (UTC) 3619:06:33, 5 December 2005 (UTC) 3614:they'd help much. Regards, 3601:06:14, 5 December 2005 (UTC) 3565:05:45, 5 December 2005 (UTC) 3551:04:47, 5 December 2005 (UTC) 3519:04:42, 5 December 2005 (UTC) 3509:04:16, 5 December 2005 (UTC) 3480:04:08, 5 December 2005 (UTC) 3459:03:58, 5 December 2005 (UTC) 3448:03:57, 5 December 2005 (UTC) 3438:03:54, 5 December 2005 (UTC) 3418:03:49, 5 December 2005 (UTC) 3404:03:45, 5 December 2005 (UTC) 3388:03:43, 5 December 2005 (UTC) 3358:03:38, 5 December 2005 (UTC) 3349:03:34, 5 December 2005 (UTC) 3322:03:28, 5 December 2005 (UTC) 3289:20:46, 5 December 2005 (UTC) 3252:03:35, 5 December 2005 (UTC) 3234:03:11, 5 December 2005 (UTC) 3207:20:46, 5 December 2005 (UTC) 3191:03:43, 5 December 2005 (UTC) 3182:m:Article validation feature 3165:03:35, 5 December 2005 (UTC) 3154:Speaks for itself, I think. 3142:"currently" vs "temporarily" 3116:02:45, 5 December 2005 (UTC) 3103:02:31, 5 December 2005 (UTC) 2984:01:51, 5 December 2005 (UTC) 2972:01:50, 5 December 2005 (UTC) 2942:01:47, 5 December 2005 (UTC) 2927:01:51, 5 December 2005 (UTC) 2902:20:47, 4 December 2005 (UTC) 2874:10:15, 4 December 2005 (UTC) 2863:10:12, 4 December 2005 (UTC) 2849:09:52, 4 December 2005 (UTC) 2834:07:56, 4 December 2005 (UTC) 2804:07:52, 4 December 2005 (UTC) 2770:07:32, 4 December 2005 (UTC) 2750:10:23, 6 December 2005 (UTC) 2732:21:31, 4 December 2005 (UTC) 2719:21:28, 4 December 2005 (UTC) 2707:20:43, 4 December 2005 (UTC) 2688:17:54, 4 December 2005 (UTC) 2675:17:06, 4 December 2005 (UTC) 2545:20:29, 7 December 2005 (UTC) 2530:13:41, 7 December 2005 (UTC) 2494:02:50, 5 December 2005 (UTC) 2482:21:26, 4 December 2005 (UTC) 2472:20:58, 4 December 2005 (UTC) 2461:20:58, 4 December 2005 (UTC) 2445:20:41, 4 December 2005 (UTC) 2430:query when you click "edit". 2425:20:39, 4 December 2005 (UTC) 2410:17:59, 4 December 2005 (UTC) 2398:17:54, 4 December 2005 (UTC) 2377:15:38, 4 December 2005 (UTC) 2329:10:08, 4 December 2005 (UTC) 2300:10:05, 4 December 2005 (UTC) 2269:17:10, 4 December 2005 (UTC) 2256:10:07, 4 December 2005 (UTC) 2246:10:02, 4 December 2005 (UTC) 2234:09:55, 4 December 2005 (UTC) 2210:09:47, 4 December 2005 (UTC) 2201:09:46, 4 December 2005 (UTC) 2192:09:43, 4 December 2005 (UTC) 2183:09:41, 4 December 2005 (UTC) 2172:07:20, 4 December 2005 (UTC) 2147:03:26, 5 December 2005 (UTC) 2126:07:32, 4 December 2005 (UTC) 2111:07:25, 4 December 2005 (UTC) 2100:07:22, 4 December 2005 (UTC) 2069:07:10, 4 December 2005 (UTC) 2058:07:08, 4 December 2005 (UTC) 2047:07:06, 4 December 2005 (UTC) 1996:07:15, 4 December 2005 (UTC) 1985:06:55, 4 December 2005 (UTC) 1959:06:51, 4 December 2005 (UTC) 1929:06:49, 4 December 2005 (UTC) 1906:06:10, 4 December 2005 (UTC) 1865:07:15, 4 December 2005 (UTC) 1854:07:00, 4 December 2005 (UTC) 1842:06:23, 4 December 2005 (UTC) 1832:06:18, 4 December 2005 (UTC) 1822:05:52, 4 December 2005 (UTC) 1807:05:45, 4 December 2005 (UTC) 1795:05:40, 4 December 2005 (UTC) 1782:06:25, 4 December 2005 (UTC) 1771:05:52, 4 December 2005 (UTC) 1756:05:35, 4 December 2005 (UTC) 1743:05:25, 4 December 2005 (UTC) 1559:03:58, 4 December 2005 (UTC) 1543:03:10, 4 December 2005 (UTC) 1530:01:21, 4 December 2005 (UTC) 1510:01:27, 4 December 2005 (UTC) 1479:00:47, 4 December 2005 (UTC) 1453:03:22, 5 December 2005 (UTC) 1434:02:38, 4 December 2005 (UTC) 1416:01:28, 4 December 2005 (UTC) 1403:23:26, 3 December 2005 (UTC) 1394:23:16, 3 December 2005 (UTC) 1329:19:42, 5 December 2005 (UTC) 1320:03:20, 5 December 2005 (UTC) 1293:06:07, 4 December 2005 (UTC) 1263:04:46, 4 December 2005 (UTC) 1253:03:55, 4 December 2005 (UTC) 1241:03:10, 4 December 2005 (UTC) 1228:02:33, 4 December 2005 (UTC) 1209:02:31, 4 December 2005 (UTC) 1184:01:28, 4 December 2005 (UTC) 1167:01:23, 4 December 2005 (UTC) 1131:00:42, 4 December 2005 (UTC) 1110:01:23, 4 December 2005 (UTC) 1079:23:26, 3 December 2005 (UTC) 1070:23:16, 3 December 2005 (UTC) 1037:Semi-protection for 3 months 982:02:45, 5 December 2005 (UTC) 967:17:01, 4 December 2005 (UTC) 950:09:25, 4 December 2005 (UTC) 938:09:16, 4 December 2005 (UTC) 926:06:16, 4 December 2005 (UTC) 916:04:03, 4 December 2005 (UTC) 904:03:10, 4 December 2005 (UTC) 888:01:21, 4 December 2005 (UTC) 853:01:12, 4 December 2005 (UTC) 834:02:25, 4 December 2005 (UTC) 794:01:46, 4 December 2005 (UTC) 776:01:35, 4 December 2005 (UTC) 766:01:23, 4 December 2005 (UTC) 757:01:21, 4 December 2005 (UTC) 711:01:35, 4 December 2005 (UTC) 702:01:23, 4 December 2005 (UTC) 683:00:58, 4 December 2005 (UTC) 661:03:18, 5 December 2005 (UTC) 647:02:27, 4 December 2005 (UTC) 628:17:01, 4 December 2005 (UTC) 599:01:21, 4 December 2005 (UTC) 569:01:17, 4 December 2005 (UTC) 541:09:05, 4 December 2005 (UTC) 532:06:05, 4 December 2005 (UTC) 498:03:10, 4 December 2005 (UTC) 487:01:21, 4 December 2005 (UTC) 452:00:31, 4 December 2005 (UTC) 443:23:25, 3 December 2005 (UTC) 434:23:16, 3 December 2005 (UTC) 384:23:16, 3 December 2005 (UTC) 363:22:25, 3 December 2005 (UTC) 351:18:47, 3 December 2005 (UTC) 335:18:42, 3 December 2005 (UTC) 315:18:28, 3 December 2005 (UTC) 299:18:10, 3 December 2005 (UTC) 288:18:28, 3 December 2005 (UTC) 273:18:10, 3 December 2005 (UTC) 262:18:28, 3 December 2005 (UTC) 246:18:10, 3 December 2005 (UTC) 226:12:00, 3 December 2005 (UTC) 206:08:51, 3 December 2005 (UTC) 187:02:18, 6 December 2005 (UTC) 173:02:06, 6 December 2005 (UTC) 159:22:36, 3 December 2005 (UTC) 150:12:13, 3 December 2005 (UTC) 133:09:41, 3 December 2005 (UTC) 123:08:34, 3 December 2005 (UTC) 114:08:21, 3 December 2005 (UTC) 104:08:16, 3 December 2005 (UTC) 3013:, this page is temporarily 2839:calculated bad faith edits. 2631:, this page is temporarily 2574:, this page is temporarily 2137:But I gave sample code! :P 1705:, this page is temporarily 1310:works well in that aspect. 1031:Semi-protection for 1 month 4129: 1643:can be used if necessary. 1639:should be sufficient, but 1468:Disagree even a little bit 1234:only admins can work in. - 1120:Disagree even a little bit 1025:Semi-protection for 1 week 672:Disagree even a little bit 401:Level 1 - No moves allowed 3063:, this page is currently 2119:much bolder than you. :P 1377:Knowledge:Semi-protection 1362:Effect on Visible Content 3966:(a feature request) and 2505:Does the tag have to be 1609:editors with fewer than 969:- Not only do I support 2637:having sections removed 170:Ævar Arnfjörð Bjarmason 147:Ævar Arnfjörð Bjarmason 120:Ævar Arnfjörð Bjarmason 101:Ævar Arnfjörð Bjarmason 3413:of protection creep.-- 2776:Supreme Lord Chancelor 502:FYI, it says "isagree 3542:<reset indent: --> 3422:The simpler proposal 3380:South Park Republican 3299:Regarding Time limits 3071:users and users with 3067:from being edited by 3021:users and users with 3017:from being edited by 2643:users and users with 2589:users and users with 1713:users and users with 1709:from being edited by 42:of past discussions. 4077:User:Mysekurity/Semi 3962:Oh, Splash, look at 3648:Only one level of SP 3463:Absolutely nothing, 3376:has no such evidence 3083:request unprotection 3061:persistent vandalism 3033:request unprotection 2990:Yet more suggestions 2655:request unprotection 2601:request unprotection 2515:? Could we make it 1764:. (Is that right?) - 1725:request unprotection 1470:(PLEASE state why): 1122:(PLEASE state why): 674:(PLEASE state why): 321:Vandalism Statistics 143:costs a lot of money 128:are we looking at?-- 3716:m:instruction creep 3266:with newer accounts 3011:deal with vandalism 2882:Where are the devs? 2629:deal with vandalism 2572:deal with vandalism 2009:editing the article 1703:deal with vandalism 1607:of a page prevents 615:User:Dragons flight 410:Level 4 - Protected 358:semi-protection. -- 3819:Special:Statistics 3025:very new accounts. 3023:fewer than N edits 2647:very new accounts. 2645:fewer than N edits 2593:very new accounts. 2591:fewer than N edits 1717:very new accounts. 1715:fewer than N edits 326:many had 20? etc. 99:system for this. — 4041: 3970:, they do reply. 3956: 3858: 3798: 3748: 3724: 3672: 3549: 3507: 3457: 3436: 3402: 3397:pretty quickly. - 3347: 3189: 3114: 3092: 3091: 3073:very new accounts 3042: 3041: 2982: 2932:Just wondering... 2730: 2686: 2664: 2663: 2610: 2609: 2492: 2470: 2459: 2408: 2396: 2170: 2149: 2124: 2067: 1994: 1983: 1927: 1863: 1820: 1769: 1741: 1734: 1733: 1672: 1671: 1650: 1541: 1457:Voice of All(MTG) 1239: 902: 504:even a little bit 496: 349: 313: 286: 260: 238:Previous comments 90:Technical comment 87: 86: 54: 53: 48:current talk page 4120: 4100: 4093: 4086: 4081: 4075: 4034: 3977: 3955: 3944: 3897: 3857: 3846: 3832: 3797: 3747: 3723: 3671: 3548: 3506: 3456: 3435: 3401: 3346: 3264:I'd be more for 3226: 3188: 3179: 3173: 3113: 3054: 3047: 3004: 2997: 2981: 2969: 2962: 2955: 2924: 2917: 2910: 2898: 2895: 2892: 2831: 2826: 2819: 2812: 2801: 2796: 2789: 2782: 2729: 2703: 2700: 2697: 2685: 2622: 2615: 2565: 2558: 2542: 2524: 2518: 2514: 2508: 2491: 2469: 2458: 2441: 2438: 2435: 2418:strong supportor 2407: 2395: 2374: 2369: 2362: 2355: 2169: 2144: 2136: 2123: 2097: 2092: 2085: 2078: 2066: 2044: 2039: 2032: 2025: 2020: 2014: 1993: 1975: 1973:≈ jossi fresco ≈ 1956: 1951: 1944: 1937: 1919: 1917:≈ jossi fresco ≈ 1903: 1898: 1891: 1884: 1862: 1819: 1768: 1740: 1696: 1689: 1662: 1656: 1644: 1600: 1591: 1590: 1580: 1574: 1540: 1526: 1523: 1520: 1507: 1502: 1495: 1488: 1450: 1426: 1357: 1356: 1346: 1340: 1317: 1304: 1290: 1285: 1278: 1271: 1238: 1224: 1221: 1218: 1201: 1164: 1159: 1152: 1145: 1107: 1102: 1095: 1088: 1010: 1009: 999: 993: 901: 885: 880: 873: 866: 831: 826: 819: 812: 807: 801: 754: 749: 742: 735: 658: 639: 596: 591: 584: 577: 565: 562: 559: 529: 524: 517: 510: 495: 484: 479: 472: 465: 342: 306: 279: 253: 184: 68: 56: 55: 33: 32: 26: 4128: 4127: 4123: 4122: 4121: 4119: 4118: 4117: 4098: 4091: 4084: 4079: 4073: 3975: 3942: 3895: 3844: 3830: 3824: 3780: 3778:1% of new users 3650: 3301: 3222: 3177: 3171: 2992: 2967: 2960: 2953: 2934: 2922: 2915: 2908: 2896: 2893: 2890: 2884: 2841: 2829: 2824: 2817: 2810: 2799: 2794: 2787: 2780: 2760: 2701: 2698: 2695: 2553: 2540: 2522: 2516: 2512: 2506: 2439: 2436: 2433: 2372: 2367: 2360: 2353: 2142: 2095: 2090: 2083: 2076: 2042: 2037: 2030: 2023: 2018: 2012: 1954: 1949: 1942: 1935: 1913:User:Mysekurity 1901: 1896: 1889: 1882: 1660: 1654: 1605:Semi-protection 1598: 1582: 1572: 1569: 1524: 1521: 1518: 1505: 1500: 1493: 1486: 1448: 1422: 1364: 1348: 1338: 1335: 1315: 1302: 1288: 1283: 1276: 1269: 1222: 1219: 1216: 1197: 1162: 1157: 1150: 1143: 1105: 1100: 1093: 1086: 1017: 1001: 991: 988: 883: 878: 871: 864: 829: 824: 817: 810: 805: 799: 752: 747: 740: 733: 656: 635: 594: 589: 582: 575: 563: 560: 557: 527: 522: 515: 508: 482: 477: 470: 463: 391: 371: 323: 234: 182: 92: 64: 30: 22: 21: 20: 12: 11: 5: 4126: 4124: 4116: 4115: 4070: 4069: 4068: 4067: 4066: 4065: 4029: 4028: 4027: 4026: 4025: 4024: 4023: 4022: 4021: 4020: 4019: 4018: 4017: 4016: 4015: 4014: 4013: 4012: 4011: 4010: 3984: 3983: 3982: 3913: 3912: 3911: 3910: 3909: 3908: 3907: 3906: 3905: 3904: 3903: 3902: 3869: 3868: 3867: 3866: 3865: 3864: 3863: 3862: 3822: 3811: 3779: 3776: 3775: 3774: 3773: 3772: 3771: 3770: 3769: 3768: 3767: 3766: 3765: 3764: 3763: 3762: 3702: 3701: 3700: 3699: 3698: 3649: 3646: 3645: 3644: 3643: 3642: 3641: 3640: 3626: 3625: 3624: 3623: 3622: 3621: 3606: 3605: 3604: 3603: 3588: 3587: 3586: 3585: 3578: 3577: 3576: 3575: 3568: 3567: 3540: 3539: 3538: 3537: 3536: 3535: 3534: 3533: 3532: 3531: 3530: 3529: 3528: 3527: 3526: 3525: 3524: 3523: 3522: 3521: 3363: 3362: 3361: 3360: 3341: 3340: 3339: 3335: 3331: 3315: 3314: 3311: 3308: 3300: 3297: 3296: 3295: 3294: 3293: 3292: 3291: 3276: 3275: 3274: 3273: 3259: 3258: 3257: 3256: 3255: 3254: 3239: 3238: 3237: 3236: 3214: 3213: 3212: 3211: 3210: 3209: 3194: 3193: 3152: 3151: 3150:the extra link 3144: 3143: 3136: 3135: 3127: 3126: 3119: 3118: 3090: 3089: 3055: 3040: 3039: 3005: 2991: 2988: 2987: 2986: 2974: 2933: 2930: 2883: 2880: 2879: 2878: 2877: 2876: 2840: 2837: 2759: 2758:Doing as told? 2756: 2755: 2754: 2753: 2752: 2712: 2711: 2710: 2709: 2662: 2661: 2623: 2608: 2607: 2566: 2552: 2549: 2548: 2547: 2503: 2502: 2501: 2500: 2499: 2498: 2497: 2496: 2463: 2427: 2388: 2387: 2386: 2385: 2384: 2383: 2382: 2381: 2380: 2379: 2340: 2339: 2338: 2337: 2336: 2335: 2334: 2333: 2332: 2331: 2311: 2310: 2309: 2308: 2307: 2306: 2305: 2304: 2303: 2302: 2284: 2283: 2282: 2281: 2280: 2279: 2278: 2277: 2276: 2275: 2274: 2273: 2272: 2271: 2219: 2218: 2217: 2216: 2215: 2214: 2213: 2212: 2159: 2158: 2157: 2156: 2155: 2154: 2153: 2152: 2151: 2150: 2134: 2133: 2132: 2131: 2130: 2129: 2128: 2060: 1998: 1964: 1963: 1962: 1961: 1878: 1877: 1876: 1875: 1874: 1873: 1872: 1871: 1870: 1869: 1868: 1867: 1829:Dragons flight 1804:Dragons flight 1798: 1797: 1788: 1787: 1786: 1785: 1784: 1732: 1731: 1697: 1670: 1669: 1663:and listed at 1597: 1594: 1593: 1592: 1561: 1545: 1533: 1513: 1482: 1465: 1464: 1461:Special:Random 1441: 1418: 1405: 1396: 1363: 1360: 1359: 1358: 1331: 1322: 1296: 1265: 1255: 1243: 1231: 1212: 1193: 1172: 1171: 1170: 1169: 1135: 1134: 1117: 1116: 1114: 1081: 1072: 1041: 1040: 1034: 1028: 1016: 1013: 1012: 1011: 984: 974: 955: 954: 953: 952: 929: 928: 918: 906: 893: 892: 891: 890: 857: 856: 846: 845: 844: 843: 842: 841: 840: 839: 838: 837: 836: 791:Dragons flight 763:Dragons flight 717: 716: 715: 714: 713: 699:Dragons flight 680:Dragons flight 669: 668: 665: 664: 650: 617:'s idea below. 602: 601: 571: 552: 551: 550: 549: 548: 547: 546: 545: 544: 543: 456: 455: 445: 436: 412: 411: 408: 405: 402: 399: 398:Level 0 - Open 390: 387: 370: 367: 366: 365: 354: 353: 322: 319: 318: 317: 296:Dragons flight 291: 290: 270:Dragons flight 265: 264: 243:Dragons flight 233: 230: 229: 228: 212: 211: 210: 209: 208: 197: 196: 195: 194: 193: 192: 191: 190: 189: 91: 88: 85: 84: 79: 74: 69: 62: 52: 51: 34: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 4125: 4114: 4111: 4107: 4106: 4105: 4104: 4101: 4096: 4095: 4094: 4087: 4078: 4064: 4061: 4056: 4055: 4054: 4051: 4046: 4045: 4044: 4040: 4038: 4036: 4031: 4030: 4009: 4006: 4005: 4000: 3999: 3998: 3995: 3990: 3985: 3981: 3978: 3973: 3969: 3965: 3961: 3960: 3959: 3954: 3950: 3949: 3948: 3945: 3940: 3936: 3935: 3934: 3931: 3927: 3926: 3925: 3924: 3923: 3922: 3921: 3920: 3919: 3918: 3917: 3916: 3915: 3914: 3901: 3898: 3893: 3889: 3888: 3887: 3884: 3879: 3878: 3877: 3876: 3875: 3874: 3873: 3872: 3871: 3870: 3861: 3856: 3852: 3851: 3850: 3847: 3842: 3838: 3837: 3836: 3833: 3828: 3820: 3816: 3812: 3810: 3807: 3803: 3802: 3801: 3796: 3792: 3791: 3790: 3789: 3786: 3777: 3761: 3758: 3753: 3752: 3751: 3746: 3741: 3740: 3739: 3736: 3731: 3730: 3729: 3728: 3727: 3722: 3717: 3713: 3712: 3711: 3708: 3703: 3697: 3694: 3689: 3688: 3687: 3684: 3679: 3678: 3677: 3676: 3675: 3670: 3666: 3662: 3661: 3660: 3659: 3656: 3647: 3639: 3636: 3632: 3631: 3630: 3629: 3628: 3627: 3620: 3617: 3612: 3611: 3610: 3609: 3608: 3607: 3602: 3599: 3598: 3592: 3591: 3590: 3589: 3582: 3581: 3580: 3579: 3572: 3571: 3570: 3569: 3566: 3563: 3559: 3555: 3554: 3553: 3552: 3547: 3520: 3517: 3512: 3511: 3510: 3505: 3500: 3496: 3492: 3488: 3483: 3482: 3481: 3478: 3474: 3470: 3466: 3462: 3461: 3460: 3455: 3451: 3450: 3449: 3446: 3441: 3440: 3439: 3434: 3429: 3425: 3421: 3420: 3419: 3416: 3412: 3407: 3406: 3405: 3400: 3396: 3391: 3390: 3389: 3386: 3381: 3377: 3372: 3367: 3366: 3365: 3364: 3359: 3356: 3352: 3351: 3350: 3345: 3342: 3336: 3332: 3328: 3327: 3326: 3325: 3324: 3323: 3320: 3312: 3309: 3306: 3305: 3304: 3298: 3290: 3287: 3282: 3281: 3280: 3279: 3278: 3277: 3271: 3267: 3263: 3262: 3261: 3260: 3253: 3250: 3245: 3244: 3243: 3242: 3241: 3240: 3235: 3232: 3231: 3227: 3225: 3218: 3217: 3216: 3215: 3208: 3205: 3200: 3199: 3198: 3197: 3196: 3195: 3192: 3187: 3183: 3176: 3169: 3168: 3167: 3166: 3163: 3158: 3155: 3149: 3148: 3147: 3141: 3140: 3139: 3133: 3132: 3131: 3124: 3123: 3122: 3117: 3112: 3107: 3106: 3105: 3104: 3101: 3096: 3088: 3087: 3084: 3080: 3076: 3074: 3070: 3066: 3062: 3056: 3053: 3048: 3045: 3038: 3037: 3034: 3030: 3026: 3024: 3020: 3016: 3012: 3006: 3003: 2998: 2995: 2989: 2985: 2980: 2975: 2973: 2970: 2965: 2964: 2963: 2956: 2950: 2946: 2945: 2944: 2943: 2940: 2931: 2929: 2928: 2925: 2920: 2919: 2918: 2911: 2904: 2903: 2900: 2899: 2881: 2875: 2872: 2871: 2866: 2865: 2864: 2861: 2857: 2853: 2852: 2851: 2850: 2847: 2838: 2836: 2835: 2832: 2827: 2822: 2821: 2820: 2813: 2806: 2805: 2802: 2797: 2792: 2791: 2790: 2783: 2777: 2772: 2771: 2768: 2767: 2757: 2751: 2748: 2743: 2739: 2735: 2734: 2733: 2728: 2723: 2722: 2721: 2720: 2717: 2708: 2705: 2704: 2691: 2690: 2689: 2684: 2679: 2678: 2677: 2676: 2673: 2669: 2660: 2659: 2656: 2652: 2648: 2646: 2642: 2636: 2634: 2630: 2624: 2621: 2616: 2613: 2606: 2605: 2602: 2598: 2594: 2592: 2588: 2583: 2579: 2577: 2573: 2567: 2564: 2559: 2556: 2551:More features 2550: 2546: 2543: 2538: 2534: 2533: 2532: 2531: 2528: 2521: 2520:semiprotected 2511: 2495: 2490: 2485: 2484: 2483: 2480: 2475: 2474: 2473: 2468: 2464: 2462: 2457: 2452: 2448: 2447: 2446: 2443: 2442: 2428: 2426: 2423: 2419: 2414: 2413: 2412: 2411: 2406: 2400: 2399: 2394: 2378: 2375: 2370: 2365: 2364: 2363: 2356: 2350: 2349: 2348: 2347: 2346: 2345: 2344: 2343: 2342: 2341: 2330: 2327: 2326: 2321: 2320: 2319: 2318: 2317: 2316: 2315: 2314: 2313: 2312: 2301: 2298: 2294: 2293: 2292: 2291: 2290: 2289: 2288: 2287: 2286: 2285: 2270: 2267: 2263: 2259: 2258: 2257: 2254: 2249: 2248: 2247: 2244: 2243: 2237: 2236: 2235: 2232: 2227: 2226: 2225: 2224: 2223: 2222: 2221: 2220: 2211: 2208: 2204: 2203: 2202: 2199: 2195: 2194: 2193: 2190: 2186: 2185: 2184: 2181: 2176: 2175: 2174: 2173: 2168: 2164: 2148: 2145: 2140: 2135: 2127: 2122: 2118: 2114: 2113: 2112: 2109: 2108: 2103: 2102: 2101: 2098: 2093: 2088: 2087: 2086: 2079: 2072: 2071: 2070: 2065: 2061: 2059: 2056: 2055: 2050: 2049: 2048: 2045: 2040: 2035: 2034: 2033: 2026: 2017: 2010: 2006: 2005: 1999: 1997: 1992: 1988: 1987: 1986: 1982: 1978: 1974: 1970: 1969: 1968: 1967: 1966: 1965: 1960: 1957: 1952: 1947: 1946: 1945: 1938: 1932: 1931: 1930: 1926: 1922: 1918: 1914: 1910: 1909: 1908: 1907: 1904: 1899: 1894: 1893: 1892: 1885: 1866: 1861: 1857: 1856: 1855: 1852: 1851: 1845: 1844: 1843: 1840: 1835: 1834: 1833: 1830: 1825: 1824: 1823: 1818: 1814: 1810: 1809: 1808: 1805: 1800: 1799: 1796: 1793: 1789: 1783: 1780: 1779: 1774: 1773: 1772: 1767: 1763: 1759: 1758: 1757: 1754: 1753: 1747: 1746: 1745: 1744: 1739: 1730: 1729: 1726: 1722: 1718: 1716: 1712: 1708: 1704: 1698: 1695: 1690: 1687: 1685: 1681: 1677: 1668: 1666: 1659: 1651: 1648: 1642: 1638: 1632: 1630: 1626: 1620: 1618: 1614: 1612: 1606: 1602: 1601: 1595: 1589: 1585: 1581: 1575: 1573:HorsePunchKid 1566: 1562: 1560: 1557: 1556: 1550: 1546: 1544: 1539: 1534: 1531: 1528: 1527: 1514: 1511: 1508: 1503: 1498: 1497: 1496: 1489: 1483: 1480: 1477: 1473: 1472: 1471: 1469: 1462: 1458: 1454: 1451: 1446: 1442: 1439: 1435: 1432: 1431: 1427: 1425: 1419: 1417: 1414: 1410: 1406: 1404: 1401: 1397: 1395: 1392: 1388: 1387: 1386: 1384: 1380: 1378: 1374: 1368: 1361: 1355: 1351: 1347: 1341: 1339:HorsePunchKid 1332: 1330: 1327: 1323: 1321: 1318: 1313: 1309: 1305: 1300: 1297: 1294: 1291: 1286: 1281: 1280: 1279: 1272: 1266: 1264: 1261: 1256: 1254: 1251: 1250: 1244: 1242: 1237: 1232: 1229: 1226: 1225: 1213: 1210: 1207: 1206: 1202: 1200: 1194: 1192: 1191: 1185: 1182: 1178: 1174: 1173: 1168: 1165: 1160: 1155: 1154: 1153: 1146: 1139: 1138: 1137: 1136: 1132: 1129: 1125: 1124: 1123: 1121: 1115: 1112: 1111: 1108: 1103: 1098: 1097: 1096: 1089: 1082: 1080: 1077: 1073: 1071: 1068: 1064: 1063: 1062: 1060: 1056: 1054: 1050: 1045: 1038: 1035: 1032: 1029: 1026: 1023: 1022: 1021: 1014: 1008: 1004: 1000: 994: 992:HorsePunchKid 985: 983: 980: 975: 972: 971:Dragonsflight 968: 965: 961: 957: 956: 951: 948: 947: 941: 940: 939: 936: 931: 930: 927: 924: 919: 917: 914: 913: 907: 905: 900: 895: 894: 889: 886: 881: 876: 875: 874: 867: 861: 860: 859: 858: 854: 851: 847: 835: 832: 827: 822: 821: 820: 813: 804: 797: 796: 795: 792: 787: 783: 779: 778: 777: 774: 769: 768: 767: 764: 760: 759: 758: 755: 750: 745: 744: 743: 736: 730: 726: 722: 718: 712: 709: 705: 704: 703: 700: 696: 692: 691: 690: 686: 685: 684: 681: 677: 676: 675: 673: 667: 666: 662: 659: 654: 651: 648: 645: 644: 640: 638: 632: 631: 630: 629: 626: 622: 618: 616: 612: 608: 600: 597: 592: 587: 586: 585: 578: 572: 570: 567: 566: 554: 553: 542: 539: 535: 534: 533: 530: 525: 520: 519: 518: 511: 505: 501: 500: 499: 494: 490: 489: 488: 485: 480: 475: 474: 473: 466: 460: 459: 458: 457: 453: 450: 446: 444: 441: 437: 435: 432: 428: 427: 426: 424: 420: 418: 409: 406: 403: 400: 397: 396: 395: 388: 386: 385: 382: 377: 368: 364: 361: 356: 355: 352: 348: 346: 344: 339: 338: 337: 336: 333: 327: 320: 316: 312: 310: 308: 303: 302: 301: 300: 297: 289: 285: 283: 281: 277: 276: 275: 274: 271: 263: 259: 257: 255: 250: 249: 248: 247: 244: 239: 231: 227: 224: 221: 217: 213: 207: 204: 203: 198: 188: 185: 180: 176: 175: 174: 171: 166: 162: 161: 160: 157: 153: 152: 151: 148: 144: 141:doesn't mean 140: 136: 135: 134: 131: 126: 125: 124: 121: 117: 116: 115: 112: 108: 107: 106: 105: 102: 98: 89: 83: 80: 78: 75: 73: 70: 67: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 4090: 4089: 4071: 4003: 3988: 3964:Special:Cite 3781: 3693:Hall Monitor 3664: 3651: 3596: 3557: 3541: 3472: 3468: 3464: 3427: 3423: 3410: 3375: 3370: 3316: 3302: 3269: 3265: 3229: 3223: 3159: 3156: 3153: 3145: 3137: 3128: 3120: 3097: 3093: 3069:unregistered 3058: 3057: 3043: 3022: 3019:unregistered 3008: 3007: 2994:Instead of: 2993: 2959: 2958: 2948: 2935: 2914: 2913: 2905: 2888: 2885: 2869: 2842: 2816: 2815: 2807: 2786: 2785: 2773: 2765: 2761: 2741: 2737: 2713: 2693: 2665: 2644: 2641:unregistered 2638: 2626: 2625: 2611: 2590: 2587:unregistered 2584: 2580:edited with 2569: 2568: 2554: 2504: 2450: 2431: 2417: 2401: 2389: 2359: 2358: 2324: 2241: 2162: 2160: 2116: 2106: 2082: 2081: 2053: 2029: 2028: 2002: 1941: 1940: 1888: 1887: 1879: 1849: 1812: 1777: 1751: 1735: 1714: 1711:unregistered 1700: 1699: 1684:instructions 1679: 1675: 1673: 1652: 1646: 1633: 1621: 1616: 1610: 1608: 1604: 1603: 1564: 1554: 1516: 1492: 1491: 1467: 1466: 1438:obiter dicta 1429: 1423: 1382: 1381: 1369: 1365: 1326:Hall Monitor 1275: 1274: 1248: 1214: 1204: 1198: 1188:agrees with 1187: 1149: 1148: 1119: 1118: 1092: 1091: 1083: 1058: 1057: 1052: 1048: 1046: 1042: 1036: 1030: 1024: 1018: 945: 911: 870: 869: 816: 815: 803:high-traffic 739: 738: 694: 671: 670: 642: 636: 604: 603: 581: 580: 555: 514: 513: 503: 469: 468: 422: 421: 416: 413: 392: 375: 372: 328: 324: 292: 266: 235: 215: 201: 142: 138: 93: 65: 43: 37: 4110:Ben Aveling 4060:Ben Aveling 4004:Woohookitty 3815:Preferences 3616:Ben Aveling 3597:Woohookitty 3411:probability 3355:Ben Aveling 3286:Ben Aveling 3249:Ben Aveling 3204:Ben Aveling 3162:Ben Aveling 3100:Ben Aveling 3059:Because of 3044:What about 2939:HappyCamper 2870:Woohookitty 2766:Woohookitty 2578:from being 2325:Woohookitty 2322:Exactly. -- 2242:Woohookitty 2107:Woohookitty 2054:Woohookitty 1850:Woohookitty 1778:Woohookitty 1752:Woohookitty 1615:the newest 1555:Woohookitty 1463:to be used. 1249:Woohookitty 946:Woohookitty 912:Woohookitty 719:Plus, it's 202:Woohookitty 36:This is an 3175:vprotected 2527:Tim Pierce 2510:sprotected 1658:sprotected 1584:2005-12-06 1455:. Same as 1350:2005-12-06 1003:2005-12-06 979:Tim Pierce 798:See also: 773:Mysekurity 708:Mysekurity 376:productive 332:Tim Pierce 268:history. 137:Note that 3968:this diff 3683:Sandpiper 3338:anytning. 3334:measures. 3268:then the 3160:Regards, 3098:Regards, 3079:talk page 3065:protected 3029:talk page 3015:protected 2856:Ray Nagin 2846:Sandpiper 2651:talk page 2633:protected 2597:talk page 2576:protected 2115:Oh, I am 1762:RC patrol 1721:talk page 1707:protected 1476:Sandpiper 1190:Sandpiper 1128:Sandpiper 935:Sandpiper 850:Sandpiper 782:lollipops 725:Redwolf24 721:anti-wiki 689:Sandpiper 538:Sandpiper 449:Sandpiper 220:Susvolans 139:expensive 82:Archive 5 77:Archive 4 72:Archive 3 66:Archive 2 60:Archive 1 3270:very new 2668:Rickyrab 2262:Rickyrab 1586:04:19:51 1409:Rickyrab 1352:04:25:25 1260:novacatz 1177:Rickyrab 1005:04:28:32 960:Rickyrab 923:novacatz 786:lollipop 621:Rickyrab 607:Rickyrab 199:Sigh. -- 3499:WP:AN/I 3495:WP:AN/I 3487:WP:RFPP 3469:However 2165:, no? - 2016:sofixit 1678:and/or 1641:WP:RFPP 1637:WP:AN/I 1629:WP:AN/I 1625:WP:RFPP 1383:Support 1059:Support 605:*-- — 423:Support 39:archive 4099:kurity 3994:kizzle 3953:Splash 3930:kizzle 3883:kizzle 3855:Splash 3821:). If 3806:kizzle 3795:Splash 3785:kizzle 3757:kizzle 3745:Splash 3735:kizzle 3721:Splash 3707:kizzle 3669:Splash 3655:kizzle 3635:kizzle 3562:kizzle 3546:Splash 3516:kizzle 3504:Splash 3477:kizzle 3454:Splash 3445:kizzle 3433:Splash 3415:kizzle 3399:Splash 3385:kizzle 3344:Splash 3319:kizzle 3224:BD2412 3186:Splash 3111:Splash 2979:Splash 2968:kurity 2923:kurity 2727:Splash 2683:Splash 2489:Splash 2467:Splash 2456:Splash 2405:Splash 2393:Splash 2167:Splash 2121:Splash 2064:Splash 2007:, and 1991:Splash 1860:Splash 1817:Splash 1766:Splash 1738:Splash 1596:KIS(S) 1538:Splash 1424:BD2412 1407:-- — 1391:kizzle 1236:Splash 1199:BD2412 1175:-- — 1067:kizzle 899:Splash 723:. See 637:BD2412 493:Splash 431:kizzle 389:Levels 381:kizzle 360:kizzle 156:kizzle 4050:Rd232 3493:(and 3491:WP:PP 3395:WP:AN 2891:Voice 2860:MONGO 2747:Rd232 2716:Rd232 2696:Voice 2635:from 2582:links 2479:MONGO 2434:Voice 2422:MONGO 2253:MONGO 2231:MONGO 2198:MONGO 2180:MONGO 2163:today 1665:WP:PP 1519:Voice 1308:WP:PP 1217:Voice 729:essay 558:Voice 130:MONGO 111:MONGO 16:< 3989:make 3972:Tito 3939:Tito 3892:Tito 3841:Tito 3827:Tito 3558:will 3489:and 3371:does 2949:seen 2887:out! 2830:rity 2800:rity 2742:read 2736:Yes 2672:Talk 2612:or 2537:Tito 2373:rity 2266:Talk 2139:Tito 2096:rity 2043:rity 2004:bold 1955:rity 1902:rity 1813:move 1506:rity 1445:Tito 1413:Talk 1312:Tito 1299:Tito 1289:rity 1181:Talk 1163:rity 1106:rity 964:Talk 884:rity 830:rity 753:rity 695:ever 653:Tito 625:Talk 611:Talk 595:rity 528:rity 483:rity 216:only 179:Tito 4085:Mys 3665:all 3428:one 3424:has 3184:. - 3081:or 3031:or 3009:To 2954:Mys 2909:Mys 2897:All 2894:of 2811:Mys 2781:Mys 2738:but 2702:All 2699:of 2666:— 2653:or 2639:by 2627:To 2599:or 2585:by 2570:To 2440:All 2437:of 2354:Mys 2077:Mys 2024:Mys 1936:Mys 1883:Mys 1723:or 1701:To 1647:how 1565:not 1525:All 1522:of 1487:Mys 1270:Mys 1223:All 1220:of 1144:Mys 1087:Mys 958:— 865:Mys 811:Mys 734:Mys 727:'s 576:Mys 564:All 561:of 509:Mys 464:Mys 97:ACL 4080:}} 4074:{{ 3976:xd 3943:xd 3896:xd 3845:xd 3831:xd 3317:-- 3178:}} 3172:{{ 2937:-- 2825:ku 2795:ku 2763:-- 2670:| 2541:xd 2523:}} 2517:{{ 2513:}} 2507:{{ 2451:is 2368:ku 2264:| 2143:xd 2117:so 2091:ku 2038:ku 2019:}} 2013:{{ 1979:• 1950:ku 1923:• 1897:ku 1847:-- 1661:}} 1655:{{ 1627:, 1515:-- 1501:ku 1484:-- 1474:-- 1449:xd 1443:-- 1420:-- 1411:| 1398:-- 1389:-- 1385:: 1316:xd 1303:xd 1284:ku 1267:-- 1246:-- 1195:-- 1186:- 1179:| 1158:ku 1126:-- 1101:ku 1084:-- 1074:-- 1065:-- 1061:: 962:| 879:ku 848:-- 825:ku 806:}} 800:{{ 748:ku 657:xd 633:-- 623:| 609:| 590:ku 573:-- 523:ku 478:ku 447:-- 438:-- 429:-- 425:: 183:xd 4092:e 3743:- 3502:- 3230:T 3086:. 3075:. 3036:. 2977:- 2961:e 2916:e 2818:e 2788:e 2725:- 2658:. 2604:. 2487:- 2361:e 2084:e 2074:- 2031:e 1981:@ 1977:t 1943:e 1925:@ 1921:t 1890:e 1736:- 1728:. 1680:X 1676:N 1617:X 1611:N 1588:Z 1579:龜 1576:→ 1570:— 1536:- 1494:e 1440:) 1430:T 1354:Z 1345:龜 1342:→ 1336:— 1277:e 1205:T 1151:e 1141:- 1094:e 1007:Z 998:龜 995:→ 989:— 897:- 872:e 818:e 741:e 643:T 583:e 516:e 471:e 454:. 223:⇔ 168:— 50:.

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

Knowledge

talk:Semi-protection policy/Archive 2 - Knowledge

Index