Knowledge:Requests for comment/Extended confirmed protection policy

1423:

tools and powers to? Admins can edit full protected articles because they passed community scrutiny, and are expected to be able to read consensus out of discussion, ensure policy is followed in said consensus, and implement. If we pass ECP, 30/500 editors will be allowed to edit ECP protected articles because they made a bunch of edits, whether they spent 2 years significantly improving/creating 500 articles, or 30 days archiving dead reference links on 500 pages from the backlog. Many people here have already mentioned that many very trustworthy editors and/or topic experts will be falsely assumed untrustworthy and discouraged under 30/500; it's also important to consider that many editors, good faith and trustworthy or not, who are regardless not necessarily equipped and community-vetted to read consensus, will be automatically trusted as extended confirmed, and given an inappropriate amount of automatic power. With the semi/full dichotomy, we avoid stratification, because either almost all editors can, or almost all editors can't, edit. It's much less discouraging for an active editor with, say, 150 edits, to encounter a full protected page than a 30/500 page, because they know that power-editors are just as restricted as they are, and everyone is subject to the same edit request system. The same goes for a completely new editor, who sees even the experienced power-editors discussing and arguing for their proposed edits on the talk page, and thus sees a path to their participating on the exact same level as those power-editors, but in talkspace. PC2 would also be a good solution, but in the absence of PC2, full protection serves this purpose a lot better than ECP. As for sockpuppetry, yes, ECP would be a monumental tool for combating it. But I think that the stratification it causes, further discouraging our dwindling supply of new editors, is a far greater concern, especially when there's already systems in place for identifying and quickly limiting the impact of socks. A tool to pre-empt socks, when we already have good tools to limit their impact within minutes, is not important enough to overlook the stratification of the entire encyclopedia it will cause. Additionally, even with option B, we'd essentially be allowing socks and what they want to do, to determine the scope ECP takes on the encylopedia. No matter how much we want to keep it small, the socks will determine how many pages it's used on.

7815:

the same reasons we would in the mainspace. My userpage is actually fully protected. There was some disruption from way back when, but either way it's my userspace; it is not meant for collaboration. The exceptions are of course user talk pages (or any talk page for that matter) – rarely protected in any form. I don't know why admins would add ECP to their userspace but I see no harm in doing so if there's good reason. There is also no maximum duration for protection levels, including full protection, ECP will be no different. It's about good judgement and mostly common sense, and the same judgement will be applied with ECP, with added caution in situations where it is used over the less restrictive semi. If semi doesn't work and I protect under ECP for 2 days, 1 week, 1 month, 3 months, 6 months, 1 year, perhaps 2 years, and disruption still is out of hand, it's time for indefinite. It would have to be really bad for that to actually happen; like I said I think such scenarios will be few and far between. Most of the time it's just juvenile vandalism or BLP violations that require page protection, and semi takes care of that quite well. Anyway you are correct that this is an admin resource, precisely, just like any other tool in the toolbox. The only protection that really could be perceived as reflecting the trust of the user is template protection, since such pages are highly visible and changes will be widespread, e.g. we don't want a bunch of trial/error edits that break the template on 20,000 pages. If we're only looking at maybe 100 or so transclusions, the template might be a good candidate for ECP given we're only suffering from vandalism or edit warring from confirmed users. ECP allows extended confirmed users to still contribute to this otherwise not-so-high-risk template, which is a win-win, right? In a nutshell, semi/PC/ECP/full are just as you say admin resources to combat disruption, plain and simple, but revolve around our policy which purposefully reflects the spirit that a wiki is supposed to be open, and it's this mentality that admins are expected to have

76:

some cases—among most participants that there are certain situations in which semi-protection is simply inadequate to protect the encyclopaedia from harm from anybody sufficiently determined, and that full protection is too blunt an instrument, and therefore we (the community, through our elected administrators) need to be able to use the new "extended confirmed protection" in at least some circumstances. I acknowledge that there is a principled minority who would rather this new level of protection did not exist or was not used at all; they have conducted themselves honourably, but as I understand it such discussion is outwith the scope of this RfC: the deed is done and we are here to decide under what circumstances admins should be using the new protection level. Despite the overwhelming support for option C, many editors expressed reservations about it being used flippantly and tempered their comments with caveats like "extremely rare", "sparingly", "truly necessary", "clear-cut criteria", and "only when all lesser options have been exhausted" (to pick out a few); clearly many feel that the mandatory notification to the administrators' noticeboard (for protections not related to arbitration enforcement) will serve an important purpose in allowing the community to monitor and review its use, and expect that these protections will be rare (possibly excepting an initial wave as admins make use of an option that was not available before). Therefore I believe it is reasonable to say that

379:: I would have been much more hesitant to support ECP earlier this year if I had known it would lead down this slippery slope. Content disputes should not be solved by applying ECP instead of full protection—even if the original war was between two (or more) non-500/30 users, a 500/30 account could come along and (either maliciously or making an honest mistake) carrying on the reverting. We have enough protection levels for combating vandalism: pending changes is something I am a big supporter of and while few people !voting here might agree with me because they can't remember ever being at that point, I think even semi-protection will stop quite a few people from editing (lots of people create an account specifically because they want to edit one page, and if they find out that page is semi-protected, they might just give up and we have lost a potential new editor; the 30/500 criteria will seem ridiculously unattainable to a newbie). Since option A seems like it will fail (although anything is possible), I should note that I would strongly prefer option B to option C—I don't like the idea of more esoteric protection rules for rare cases (persistent autoconfirmed socks); although I can see its benefits, I think the disadvantage of 969:. The principle of the least required power should be always applied. There are many compelling comments in the discussion section below explaining how widely applying 30/500 would discourage newcomers and IP editors (who are responsible for a huge bulk of the edits) from contributing just because they don't have the numbers. Not to be anecdotal, but I wanted to contribute to another language's wiki (that's poor in quantity and quality), but couldn't and kept hitting walls with every edit or request, because I was considered by the software to be a "newcomer", even though I had much higher edits here on enwiki (not even allowing me to post a request to lift the restriction). Needless to say I'm not gonna be contributing to it anymore. And I don't want newcomers here to have a similar experience. I feel like this goes against the spirit of Knowledge's openness. Initially I was in favor of Option B, but then what quantifies "persistent"? And if it's persistent, then other measures should be followed, up to ArbCom (which is the current procedure for the few problematic topics that emerge). This type of high-level protection should be always decided per case. — 3855:, as a step short of full protection, though the limitations on its use should be stringently adhered to, since it will affect legit editors. At some point, an exemption mechanism for individuals should be devised (i.e., grant the userright before it auto-applies). Would also support a 15/250, if needed, but no more restrictive than 30/500. Despite the beliefs and behavior of far too many GA/FA-focused editors and certain wikiprojects, WP is not a good ol' boys' club of vested editors who have increased content control per their tenure. A terrible result would be something like a 1yr/6000 level. The 3:50 ratio seems okay; very active editors, not using automation, but participating in frequent discussion and making lots of minor cleanup edits, seem to average in the ballpark of 1,000 per month, so half that seems reasonable. If you can't make 50 edits in 3 days you are not trying very hard ( 8031:

is going to jump to ECP knowing semi will work just fine. There may however be a scenario where semi was deemed appropriate at first, and then the numerous socks or what have you waited till they became confirmed to continue disrupting. In that case the protection might be elevated to ECP. The decision to use ECP over semi of course also involves other considerations: Will blocking the users be effective? Is there an edit filter that could be tweaked? This is the normal process and having ECP does not change that. It's about judgement and carrying out the most effective preventive measure that has the least amount of collateral damage. I'm sorry this unclear to users who are less familiar with the administrative process, but I don't think we need to spell it out because frankly that's the philosophy ingrained in a wiki and a new level of protection is not going to change our core values

8278:

giving the reviewers much more control over content, and to some that sets up an additional hierarchy of users to which Biblioworm referred. An edit by an established user without the reviewer user right, even one with 100K edits, would have to be approved by another established user on an edit-by-edit basis. It sets the reviewers apart from other users, and that rankles some people that might not be so rankled about ECP. We're also not currently granting the reviewer user right based on PC2 criteria – we're doing it based on countervandalism history and experience, and that would need to change if PC2 were implemented. This isn't the place to rehash the PC2 discussion, though. It's been two years since the last well-publicized RFC on the subject, so when this is over, if someone wants to propose it again, maybe it's time. (Not going to be me, though. I'm RFC'd out for a while.)

7842:

treated exactly as the full protection, and given the cautious tone of most people who voted the option C, I think that it could be the consensus. I should also like the wording to be clearly state when it's appropriate and when is not. For example, if there is a conflict with two sides, one EC the other not, ECP should not be used as a means to silence the non-EC editors. Because that will in effect topic ban the one side of the discussion regardless of the behaviors of the individuals. Currently admins have to assess the situation to see exactly which editors are being disruptive, they don't ban all inexperienced editors indiscriminately. Using this protection, in effect bans every good faith non-EC editor working on that area even if they are not disruptive, while allowing any EC editor who is disruptive but not enough to warrant a ban yet.

6726:

As I said above in the vote section, it was actually the biting from an experienced editor, who was shortly after topic banned, that led to 500/30 protection. Knowledge was against creationists with all the resources to build an Ark, Scientologists with the power of Xenu, climate change deniers who are friends with creationists, all of which were much more powerful and well funded, those topics did not require this kind of protection but a hashtag with a lame internet drama was too much, we need new tools for admins, man the harpoons, it's Gamergate!!! I don't buy it. This protection might make the subject much more quiet, it does not make it better. Gamergate article didn't improve as far as I can see, It still reads like autism incarnate. And now people suggest using this protection as commonly as semi protection.

7519:. You are absolutely right that non-extended confirmed users are less likely to speak up about their inability to edit, but they are certainly more likely than unconfirmed users. My point here is that no admin in their right mind is going to add indefinite extended confirmed protection without trying shorter durations first. If they do that is abuse or severe negligence, plain and simple. Outside ArbCom-authorized topics or long-term issues of sockpuppetry, you probably won't see a need for an indefinite duration since semi usually does the trick. Even for semi, I can't tell you how many times I see "indefinite semi-protection" being requested at RFPP and the response is "semi-protected for a period of 1 week". As much as we care about protecting the wiki we care about keeping it open 7650:

contributions from new editors who might be rightfully bothered. I am not persuaded by comments above that are worried about new topic-experts unable to participate, because they can always post their draft or suggestions on the article's talk page. For contentious topics, that is usually the best first step anyway. An article that is subject to persistent vandalism, edit warring and disruptive WP:TE will exhaust any topic-expert (anyone for that matter). Semi-protecting and ECP for 1 to 6 months can actually help new knowledgeable editors or topic-experts to help improve the quality of difficult or contentious topics, in a more stable format through the article's talk page. We must assume good faith not only for new users, but also for not-new users and for admins.

2067:

advice rather than automated means. I am very uncomfortable about EP being used in edit warring situations because it effectively gives older accounts a great upper hand over newer users. I am not as concerned about full protection since admins go through a vetting process and risk desysop if they abuse their power over protected article. I would be open to creating a user right that would be granted upon request to edit through an intermediate protection level, but since extended confirm is about account age and not trust, it doesn't satisfy me in that regard. The only use of ECP I feel confortable with is to prevent socks, and even then I worry about overuse leading to a sort of arms race with sockmasters.

5477:—are deliberately modified to conflict with one of those "procedures through which policy and guidelines may be enforced" that the ArbCom creates. A reading of CONEXCEPT would find that the ArbCom procedure overrides the policy-mandated procedure, but an initial reading of the arbitration policy would find that policy overrides ArbCom cases. My personal intuition here is that the ArbCom procedure would indeed override the policy procedure. It is not the role of the community to hear appeals of ArbCom decisions—the ArbCom was created because we accept that there are issues the community cannot resolve by itself. The policy conflict would have to be resolved by the Committee, not the community. 7715:, I do agree with some of his points. I'm also a fairly casual Wikipedian. I've been here a bit more than one and a half years now and I've made about 60 edits per year, give or take a few. Therefore, it would take me about six to seven more years to achieve EC status, which could be a big problem if ECP was used on many articles. I've never tried to edit an article on a very contentious topic, so this wouldn't really affect me yet. However, it feels like content creators or casual Wikipedians could take a long time to achieve 500, even if they are good-faith members of the community and good at what they do. I would be much more comfortable with a 30/200 restriction or something similar. 7497:

and if they do apply full protection haphazardly, the multitude of experienced editors who are not admins will surely raise complaints. On the other hand, experienced non-admins won't be affected by the haphazard application of EC protection, so they have no incentive to complain unless they dislike EC on principle. Meanwhile, the new users (those with less than 500 edits) are unlikely to request unprotection due to their unfamiliarity with Knowledge, or unwillingness to jump through so many hoops. Proportional duration is still up to each admin's interpretation. If an admin does decide to EC protect a page indefinitely, it could easily languish that way forever. Just looking through

9441:, it seems that the important distinction is that the talk page is not under 30/500, only the article. That allows people to request changes even if they haven't met the restriction. In that sense it is working. However, I also note that semi was only applied in June, and there were three minor vandalism attacks since then. Although there have been no edits to the article since 30/500 was applied, we've got four edit requests that needed to be turned down. In terms of stopping disruption, 30/500 seems only mildly more effective than semi was. The long term effect may be better, though, so I guess we'll see what happens over time, as 10 days is a bit short to evaluate the result. - 712:: It is a bad idea to give more importance to edit count. An user who has 500 edits of wiki-gnoming is no more deserving of editing some pages that an editor who has extensively contributed to a few articles doing a few edits of 1,000+ bytes each plus a few minor edits, who may easily not have totaled 500 edits yet could have done a much more valious contribution than a wiki-gnome. Also, we already have a lot of people reverting vandalism. This kind of restriction (“protection”) can't be justified on the basis of vandalism when most of it gets reverted in minutes. Knowledge doesn't have a problem with vandalism. It ha a problem with excessive restrictions and revert-happy editors. 2320:

they're not at all clear on what hoops they are and are not willing to jump through, what sacrifices they are and are not willing to make, to achieve it. Thus, we are in a situation where we agree that we need a tool capable of making things harder for vandals, but have consensus to implement the tool with no policy other than "semi protection must have been tried and failed". 500 edits is a lot of effort for a vandal to go to, but it's also quite a hurdle for a good faith new user. In short of a workable policy to protect such users, option B is the appropriate step - signal that this should go further than Arbcom, but that we are not willing to use this as a free-for-all.

4626:. The use of ECP will help greatly when it comes to POV warriors, prolific sockmasters, and LTA vandals. It seems both bureaucratic and counterproductive to limit ourselves in when we can make use of this tool. If it will stop the disruption while still allowing through at least some constructive edits, that's a win for the encyclopedia. It is tedious beyond belief to deal with some LTA vandals. The ones who add sneaky vandalism, such as plausible-sounding hoaxes, consume massive amounts of volunteer time. If ECP turns out to be problematic in itself, we can review its use. We can also add restrictions if the community finds it's being used indiscriminately. 8232:) made a good point: Why is it that editors are overwhelmingly approving unrestricted use for this "intermediate" protection level, but yet rejected the also intermediate PC2 for reasons of "bureaucracy and hierarchy"? Even more remarkably, PC2 was weaker, to a certain extent. With PC, changes are simply reviewed and not blocked outright. But ECP is hard protection—editing is completely disallowed for those who have less than 500/30. What is the reason for this conflict? Could it be that people voting here are not concerned because they know that ECP will not affect them due to their long tenures and high edit counts? 7416:. I'm sorry this was not clear, perhaps we should amend the wording for clarity. Semi on the other hand may be handed out more liberally since it involves less collateral damage, but semi itself is not given a longer duration because it is still "technically open to edits", and this would be much less the case for the more restrictive 30/500 protection. This should go without saying, but we can amend the policy language to clarify that 30/500 is no different than the other protection levels when it comes to deciding on a duration (with exception of highly visible templates which are given an indefinite duration) 5357:— it should never be widespread, but should be applied to problematic topics/article sets where disruption exists despite semi-protection. Semi-protection should always be the first step, only when that doesn't cut it should this be implemented. Controversial topics can otherwise be overrun by SPAs, at detriment to seasoned editors — eating up their time, especially so when policies need to be reiterated over and over again. I've never seen a new editor who started editing with an agenda on something controversial, who later went on to do constructive edits elsewhere. It just doesn't happen. 9420:

depending on the vexatiousness of the topic. The problem with the edit-count based privileges is that the edit count has no bearing on the editor quality. The auto-confirmed protection works well, because it is not too much of a burden for good faith editors while it is an inconvenience for disruptive editors.(especially effective against vandals since vandalism is quite a blockable offense) But this one asks too much of a casual contributor in good faith. I don't deny that it can, in some instances, prevent persistent disruption. but in my opinion, the cost far outweighs the benefits.

7791:

the article or topic (those are ArbCom decisions or community decisions). Say a 3-month maximum. It should probably be treated as full-protection in terms of time in order to be egalitarian and avoid the problem of registered user castes. Also clarify that it is never appropriate in user or WP spaces (i.e. admins who semi-protect their userspace should never escalate to EC protection, they should warn/block the registered account). EC is solving an admin resource issue rather than an article content quality issue and shouldn't reflect "not trusted enough yet" back on the editor. --

1081:

disenfranchise new editors and encourage ownership of articles by entrenched, adroit factions. Edit counts should not be used as a license to edit or to lock down articles. It took me 10 years to get 500 edits, yet, even were I now to start editing an extended restricted page, I would likely be dismissed as simply a sleeper account that grinded just enough edits to game the system. If it must exist, then I adamantly oppose its use except in the most drastic or extraordinary cases and adamantly oppose its unchecked use by administrators. Appreciate the watchlist notification.

2101:- without prejudice to migrating to C down the road after this is tried out. Recent use of 30/500 has been, in all cases so far, a "we're at the end of our wits trying to solve this, so its either this or full-protection". So Option B would maintain that Last-Resort mentality without having to tie up ArbCom. I think we give this a try and see how it works first. Using this for "regular disruption" treads the line on infringing on "anyone can edit" due to a few bad apples. It may be that it is inevitable, but I'd rather go incrementally down that road. 2902:

semi-protection. As an example, which I offer cautiously as I have not been involved in Gamergate issues, I see that it has proved useful in that brouhaha. I can envision that a new article about a player in that controversy might be created and then might erupt into problems. I can imagine that this level of protection might be warranted rather than insisting that semi be added and failed before jumping to this level, but I am totally on board with the concept that jumping immediately to this level of protection would be extremely rare.--

7886:

then it's just a replacement for full protection in cases of heavy vandalism or where all editors involved are not extended confirmed, and like full protection would always be temporary. The problematic examples you've listed elsewhere (e.g. applying ECP in a content dispute when one party is extended confirmed and the other isn't) would be obvious misuse of admin tools (like semi protecting an article when one party is autoconfirmed and the other isn't). That situation isn't an argument for getting rid of semi protection, is it?

6927:

was a solid enough fan base who ensured they were autoconfirmed to keep pushing the disruption. ECP would have been an excellent choice to deploy at that point. Articles relating to politicians that are not covered by WP:ARBAP2, particularly around election time in any given country especially those given to extreme partisan politics, would be another example. Like I said in an another post, a discussion about specific aspects, such as duration, should wait until consensus has been reached as to actually permit admins to deploy ECP.

8921:

have an administrative power to choose who is productive and who is not. There is a reason for the distinction of involved admins. (This is unique to ARBPIA3 where the arbcom unwisely created a broad sanction which made it impossible to ECP every article this sanction applies, another of the many flaws of this new protection.) Secondly, as you just said, the puppetmasters are willing to create and game this new system too, which supports what I said that the only people who are being disallowed are the dispassionate new editors.

7341:, EC is permanent, or usually is, yet socking or edit warring is a fleeting thing. Why would we want to protect an article so that someone can't contribute positively? Perhaps Option C should have a time limit, temp-EC. As for my Option A, I could see a fast-track system of ARBCOM approvals so that we don't have to wait for a full case to get ARBCOM approval for EC. The one thing we SHOULD NOT have is EC available to every admin. It will do terrible things to Knowledge. Everyone can edit is turning into only the elite can edit. 6481:

application is established. Moreover, if the only attention it receives is in the form of complaints (assuming there will be at least a few) there will be a sort of selection bias in people’s perception of the policy‘s success, while mandatory reporting will create an easily visible ‘track record’. (For that matter, it may be worthwhile to survey the reversions and edit-requests on ECP pages, to evaluate the balance of disruption-reduction against inconvenience to good-faith newbies and the editors who process their requests.)—

6820:

broadly it is used for I/P), but realistically, if semi is not working, there is something else going on that needs a better evaluation of the situation and not just slapping a closed door onto an article. The Internet is inherently not a safe space, and I've seen people suggesting 500/30 to make WP such a place, which can't happen without closing off the open-edit fundamental system. It might take more work and for editors and admins to show patience and restraint, but if we close off Knowledge, the experiment has failed. --

9658:

edit, and they'll give up in frustration. Now, 30/500 locks out quite a lot of people who I wouldn't call 'newbies', and who I imagine are quite competent in making a protected edit request, but a lot of good faith newbies will simply not know how to make an edit request, or have the patience to make one, so even if there are technically ways for anyone to get their constructive edit onto a protected page, what any form of protection (even semi) does in reality is lock out most people who fail the criteria completely.

6327:

been granted ECP through an Arbcom case, Gamergate for example, then the ECP is an Arbcom action, with the authority of the whole committee, and not an unilateral action by an admin. An Arbcom action such as this already requires a majority vote by the committee before being performed. As for the subsection notification, the requirement is like a block review. It's posted as a new thread, the community reviews, the discussion is closed once consensus supports or opposes the ECP action then it is archived as normal.

2995:. Conceptually, I hate the idea of restricting editing from new users on certain pages. Practically, I acknowledge the necessity. That being said, this is a less restrictive option than full protection, and it adequately addresses the weaknesses of semi-protection. There are cases of vandalism, BLP violations, highly visible pages, etc. where this will be useful temporary measure of protection. I agree with the comments above that this should be used sparingly and only after lesser forms of protection have failed. 1968:- 30/500 protection would definitely be more effective against persistent sockpuppetry than semi-protection (i.e. "4/10 protection") in that it would take a full month for a sock to gain auto-extended confirmed status. However, I would add the caveat that community-imposed 30/500 should last no longer than 60–90 days, after which ArbCom would have to authorize indefinite 30/500 protection. Option C goes too far, and Option A doesn't give admins the flexibility to impose 30/500 in an emergency. — 3117:. For the purposes of sockpuppetry, 30/500 should work wonders. We can't keep making expensive edit filters for each and every issue of sockpuppetry, and no one is having fun combing through revision histories fact checking every change. Same rules apply with 30/500 – don't protect preemptively and use it only when necessary. The flexibility of having a new form of protection at our disposal is only going to make things easier, save us a lot of headaches, and still allow articles to develop 5542:

occasions despite it being permanently semi protected. High profile editors (who are not administrators) shouldn't have to put up the extra harassment from disgruntled editors and vandals. User pages should be allowed to be 'sacrosanct'. There is no 'need' for anyone and everyone to edit my user page. It's bad enough that user talk pages are routinely vandalised, but to then allow it to also occur to user pages, despite semi protection, definitely requires a different policy response.

9140:

for this protection to be justified is if there is consistent disruption from sock puppet accounts who are not vandals but disruptive editors, even then you bar every new potential good faith editor just because some people are ban evading socks. Full protection is almost always is a result of content disputes that turn into edit wars, if you replace full protection with EC protection, you may be helping one side of the conflict or another, depending which side has EC editors more

4662:

sockpuppetry, the disruptive nature of the edits isn't immediately visible to editors not familiar with the situation or where the article has a high edit rate. Full protection, whilst highly effective at stopping disruption, also prevents almost all legitimate editing as well, and is rarely applied outside specific circumstances such as edit wars between established editors. With safeguards I think it is appropriate to have an alternative available for these rare situations.

2084:- I can understand seing Option C as too vague and/or too far away from the wiki idea. If semi-protection doesn´t work get the 30/500 authorized by the ARBCOM and everything is fine. And the addition of usage against sockpuppetry makes absolute sense to me. What I would think about is making the 30/500 temporary at first, like automatically downgrading it to semi-protection after a month or something like that; with the option to easily renew and lengthen it if necessary. ... 857:- I feel that this policy should not have even be discussed in the first place. We do not need further confusion to brand new users who have just joined Knowledge. As such, we must remember about people who actually help Knowledge, but have only just created a Knowledge account, and how this policy, if one were such to exist, affect those people. See discussion below for more details. (And yes, my account is just 3 months old at the time of editing, hence the support.) -- 7690:

who will make tons of typo corrections as I see them, but I absolutely agree that there will be many editors out there who feel the way you do—for whom amassing 500 edits using automated tools or for such trivial wastes of time as searching for typos is an absurd concept, and the fact that they plod along at their own pace, making fewer but more important edits, provides no reason why they shouldn't have the same right as '30/500' users to edit controversial pages.

8906:

editors are no longer blocked by admins when they revert a wave of sockpuppets. This has dramatically reduced the effectiveness and thus number of sockpuppets, though these puppetmasters are now putting in 500 mostly minor edits and waiting 30days per account to again disrupt the encyclopedia. I think those accounts clearly owned by previously blocked editors who quickly pass 30/500 to disrupt the topic area should be blocked just as their previous accounts were.

2171:- pages experiencing persistent sock-puppetry lack the safeguards to really do anything effective. Similarly, since I've been fairly active in outing sock and meat puppets, I know that they get smarter - they don't keep attempting the same obvious edits, meaning classifying them as socks is more difficult. They also learn pretty easily how to use different IP addresses. Creating this statute will help minimize tendentious editing from socks, as well as vandalism. 8066:'encyclopedia anyone can edit' thing seriously. We do not want to stop IP editing, and we do not want to discourage new editors. But there are an increasing number of cases of sockpuppetry and disruption where ECP could help us. We are experienced at this, and we understand how long and what type of protection is best. Please assume good faith in the admin corps. We really are here to help the encyclopedia, and we want the best for the project and the movement. 3889:- given that the assumption here is that semiprotection has failed, and the only other option currently is full protection, this seems a reasonable halfway house and I don't see the harm in adding it to administrators' arsenal when combating vandalism. Assuming it doesn't get applied in cases where semiprotection would have done, of course. That can be monitored in the early days of it being used, but we generally assume our admins are sensible people. — 9228: 8829: 10155:. At the least, I think we've agreed that we don't need to automate posting new sections. Admins may be expected to manually make a post for any applications of ECP that could be debatable (as opposed to ArbCom-related matters), but I still think the transcluding the bot report will suffice. And rest assured I won't kill this bot task :) If I do or if Tool Labs blows up you can still rely on the link the header of the report that brings you to 8126:

warring because it forces discussion. It would be horribly inappropriate to lock one side out of the page as a substitute for discussion. I'm not talking about abuse from an involved admin. I'm talking about an admin who responds to an RFPP request or AN3 report and may be tempted to try the new lower protection level before full protection without considering the ramifications. This is the main reason I'm not supporting Option C as written. ~

331:. This option will obviously fail, but I will cast my vote for what I believe is correct. Admins don't need more practically unrestrained discretionary power, especially considering that this is a rather powerful level of protection. If we are to use this type of protection for purposes other than Arbitration Enforcement, the criteria for doing so should be specific, not a sweeping mandate for discretionary use "whenever necessary." 7561:

right, we run into the same issue with full protection all the time. Fortunately with ECP the fallback is not as significant (full to none vs ECP to none). I don't know how long it'd take for a core solution to happen, but I've meaning to propose a bot-automated report of full protections that have expired, perhaps pinging the protecting admin. This would be a straightforward task to implement, and the same could be done for ECP

9434:

being disruptive or were being managed easily by existing rules. Since it has been applied it has effectively disenfranchised any new editor from taking part in the discussion without considerable work. Given that there was no evidence provided that there was a problem that semi-protection wasn't already handling, we've managed to prevent new editors from taking part in discussion with no significant sign of reduced disruption.

8374:

respondents to fully-protected edit requests. I'd only support PC2 if we separated out the reviewer PC1 and reviewer PC2 user rights (with the PC2 needing to be requested by current reviewers). Specifically, any editor with a history of edit warring should not be able to review PC2 revisions for obvious reasons, but we've never had cause to heavily consider that when granting that flag up until now. ~

4380:. I'm in favor of any shifts in policy in the direction of asking our editors to prove their dedication and dependability. I'm favor of any new policy that moves us away from the idea that anyone can edit anonymously, which I realize was necessary during 2003–13 to build momentum and mass but which is no longer so good for the encyclopedia, in my opinion. Option C is a step in the right direction. 1656:. I'll go on record as being around 130/1200 and having no idea what's going on half the time - editcount might suggest I'm not a sockpuppet but I don't feel terribly qualified. For example, to my uninformed mind this sounded like a perfectly reasonable and useful tool. Then I read through comments like I was being warned by the ghost of wikifuture. So, strongly oppose B and C, and support A 407:. I actually support wider use than just approval by the arbitration committee, but both options B and C are too lenient as they allow it to be imposed at the discretion of a single user so this is the only option I can support. In my view the restriction should be applied only with the prior consensus of multiple independent administrators that other methods have failed or are not appropriate. 1695:

understand that to a seasoned editor, 500 edits is nothing, but if I continue at this rate, I will have clearance to re-edit some of the articles I've already made contributions to in four more years. I don't think that the miniscule benefits Option C produces outweigh the damage to the morale of new editors or infrequent editors, so I will support using this as infrequently as possible.

7998:, and is found to be ineffective, then 30/500 limitation may be imposed? The present language grants unlimited and arbitrary power to impose 30/500 limitation wherever semi-protection might otherwise apply. Is this what the proponent and supporters want? If not, and the language is intended as a proviso, then it should be rewritten, substituting "if" or "where" for "given that". 6432:- If this action needs posting at AN, why not just have a bot trigger a posting everytime it's used. Either on the main AN page, or a sub page. That way, everyone will get an idea of whether it looks like it's being used too liberally. If it's only a once in a while usage, then it's no problem for an uninvolved editor to click on the link and see if it warrants a second look. 1552:

experienced editors who spend most of their time pushing their POV that is not supported by reliable sources, these folks know all rules of Knowledge and are looking for an angle to ban other editors. These persistent POV pushers and ethnic warriors need to identified and banned from editing, the newcomers that make positive contributions need to find a welcoming atmosphere.--

6622:

become as widespread as semi-protection: with full vs. semi-protection, many active non-admins will argue against full protection. This is not the case when choosing between ECP and semi-protection, since the newcomers ECP restricts are unlikely to speak out against it. Knowledge is failing to attract as many new editors as in the past; ECP will only exacerbate the decline.

8148:. Almost every day there's a request for protection from someone who wants their 'side' to prevail in an content dispute with an IP while disguising it as an attempt to control disruption, and we always have to be sure we're not locking out someone who has a real problem with content. If admins understand the protection policy – and we do – there's no need to add your text. 891:- I am against this level of protection as a whole. The community doesn't get a direct say about the arbitration committee's use of it as a remedy, but it can and should strike it down as a community approved protection level. Use of this level of protection, especially allowing wider applications, is against the Knowledge's core value of being "the 💕 that anyone can edit". 4166:. As the Knowledge content grows, so does the need for enhanced control over content grow with it, especially the professional attempts to abuse the encyclopedia for promotional purposes. This comes as a much needed intermediary protection level between semi and full protection and I see no need whatsoever for notification to be posted in a subsection of AN for review - 9301:). His usual preferred method of getting around semi is to make 10 edits to his user page and then jump into vandalizing without warning, so that his sleeper isn't found before he can get to the semi-protected articles. Here, he made 115 edits to his userpage (which have now been deleted), apparently got bored, and made a single vandalizing edit to an unprotected page ( 51:

best chance of establishing a consensus and making the best use of the time that the hundreds of participants have invested. I should also thank all the participants, especially those who provide insightful rationales and those who do not yet meet the criteria for 'extend confirmed', who brought a different perspective that would otherwise have been easy to overlook.

3961:, newcomers and topic-experts can always post drafts or suggestions to the talk page, which is what WP:BRD requires and is likely on contentious topics; vandalism and edit warring by new accounts and socks is a growing problem, which exhausts constructive new/old contributors and admins; for other reasons see my comment in the "Impact on newcomers" discussion section. 952:

are in their critical learning-the-ropes stage) because of disruption by identifiable & bannable bad actors is a terrible solution, but it's just what Option C (and to a lesser extent Option B) propose. I can accept an extraordinary exception in the case of truly intractable and highly disruptive sockpuppetry directed at a single article (i.e. Option B).

8298:

is that they have absolutely no stake in whether this is implemented, because ECP will not affect them in the least. They will still be able to freely edit all ECP-protected articles, even though new users are locked out. I find this very concerning. Note that my object here is not to revive the PC2 discussion, but rather to use it a contrasting example.

6096:- I don't feel like ArbCom should have to be tasked with making decisions about page protection-- admins can be trusted to do this, so option A doesn't jive well with me. I think there does need to be a responsive measure for folks who try to game the system with sockpuppetry and sleeper accounts intended to circumvent the semi-protection process. 5725:. The essential point is "given that semi-protection has proven to be ineffective". Under present circumstances, if semi-protection fails, the options are either to let the disruption continue or to stop all non-admin editors from editing. The option of stopping a limited range of editors will sometimes be a lesser evil than either of those two. 6311:. Need clarification on "Notification is to be posted in a subsection of AN for review, unless the topic is already authorized for 30/500 protection by the Arbitration Committee." What does this mean? Will this be a general notification permanently posted at AN, or is this to be posted every time it's used? Wording is open to interpretation. 9717:

to obstruct improvement)? In some circumstances I can understand temporarily putting this protection in place, but, all six of these currently have no expiry date set (in other words are indefinitely protected). I also find it interesting that all six of these 30/500 protections were set within two weeks of the first (6th to 18th April 2016).

8163:, though. Does it not make sense to provide similar guidance for 30/500? Alternatively, the existing guidance could be relocated somewhere that isn't specific to only one protection level. This isn't only applicable to the admins protecting pages, but also to newer editors who seek to understand the protection policy and how it's applied. ~ 9527:

continued use of new, disruptive accounts where other methods (such as semi protection) have not controlled the disruption. This provision does not apply to a page or topic area which has been placed under 30/500 protection by the Arbitration Committee." I've been taking this to mean that 30/500 is implicitly an arb enforcement tool. --

125:, with guidance related to over- or mis-use, but that this not come fully into force until the mass message to administrators has been sent out. I further recommend that a review of extended-confirmed protection (excluding arbitration enforcement) be done in three months' time to establish whether its use is living up to expectations. 680:

bay, but this isn;t aimed at socks, or disruptive IPs, but 30/500 states that certain editors aren't considered to be experienced enough to even discuss the topic. Given that Option A already sees it applied to talk pages, I'm concerned that any further opening up of its use will see far wider and even less careful application. -

4565:

seems to be unnecessary bureaucracy, and a bit lop-sided. An Option D to allow this protection to be used at admin discretion without the need to report the action at AN would have been helpful, and I would have supported that option. I do feel, however, that whenever any form of protection is applied that a message, such as

1063:. We already have an intermediate category between full-protection and semi-protection - Pending Changes Level 2. However, the community overwhelming rejected the implementation of PC2, citing unnecessary bureaucracy / hierachy and fears over widespread usage as reasons of opposition. Same applies for 30/500 protection. -- 6740:

indefinite ECP applied. What the RFC is asking is whether Admins should be allowed to apply limited duration (at least that should be thrust of it) ECP to articles that are seeing heavy disruption from new accounts, sock accounts, IP's and sleepers. If ECP is not necessary, then the fall back position is semi protection.

642:. 500/30 is an extreme form of protection which disallows a very wide swathe of the editors. There should be first a serious examination of the results of the 500/30 protection on the areas it has been used, before expanding it any further. Absent this review, I am unwilling to extend it any further than it already has. 4569:, should be placed on the talkpage to give guidance to those users impacted on what they can do. Accounts impacted by Extended confirmed protection can apply to have their user rights adjusted to edit through the protection, and such information should be placed on the talkpage advising such users they can apply at 768:- I worry, with other editors, that B and C (unchecked) risk creating an undue burden on new users. 500 edits is a lot to ask of a newbie, and I fear this protection will discourage a fair bit of useful and productive content creation. I recommend reading the comments below the voting section, which inform my vote. 7665:

whereas some have been creating new (or vastly improved) graphics for articles into which I put a lot of work; and I have never vandalised, been rude, or engaged in an edit war. I feel that (a) I have earned my right to make good-faith improvements to articles, and (b) I shouldn't have to, beyond auto-verification.

1184:. Let's not increase a trend that is gradually destroying Knowledge as it becomes less accessible and more bureaucratic. Also a basic life principle is to use the minimum force required. We don't need to give admins greater powers. I fail to see why we need this high bar of protection without ArbCom authorization. 3939:, two of our most heated topic areas. It makes sense that this should be effective in less complicated topics which experience the same forms of disruption. Fills the critical gap between where semiprotection is ineffective and full protection is unwarranted. Inherently support any option but strongly prefer C. 1910:: Option C is vague, creates more caste and encourages editors to put "this user has extendedconfirmed permission" userboxes (more hat collecting!), and gives too much power to silence newcomers. Semi-protection works just fine for most cases. I support use only to stop paid advocates and other sockpuppets. 2260:

full protection (if not more) for the next year or so, and afterwards the admins will have made necessary adjustments to community feedback to know which articles should go under which protection. Cases on the fence between semi/pending and full are precisely the ones that would benefit from 30/500 anyways.

9628:(is that how you ping? I'll consider that a ping because I have no clue how to wiki) but it's a great point that it deserves to be mentioned again. The talk page is NOT under 20/500, only the article. If edits can be requested and discussion is encouraged to new users who don't fit 30/500 they can do so. 4995:

must have XX number of days with edits. This would then prevent someone from gaining edit access by simply making 500 edits on one day for the purpose of crossing the threshold. - - - Another thought: is it possible to apply additional limits to editors with, say, X number of bans in the past 12 months?

1163:. The average EC-protected page today sees a new editor go through the trouble of an edit request at a rate of once per year. Let's hope, under option B or C, sock puppeteers don't figure out they can disrupt Knowledge for new editors on a large scale by baiting admins into EC-protecting popular pages. 10101:

I don't like the idea of an additional noticeboard. We already have so many freaking noticeboards that they're losing their effectiveness. Eyes are glazing over at the sheer number of noticeboards one needs to watch. I really think transclusion of MusikBot's report in a section of AN will be fine. If

9716:

I would be concerned with all of them. The 30/500 sanction on talk pages makes it difficult for many (possibly most) editors to actually contribute to those pages in any meaningful way. Like I said, 30/500 on the article page I can understand. But, for the talk page what does this achieve (other than

9575:

It was implemented as a result of the ARBPIA3 remedy, so it did originate as an arb enforcement tool, but I think we've posted up, down, and sideways now that the standards laid out a couple of months ago were for AE/DS use and it's up to the community to decide what else to use it for (if anything).

9526:

states that "The Arbitration Committee has authorized use on articles reasonably construed as belonging to the Arab-Israeli conflict and as an arbitration enforcement. In its use as an arbitration enforcement, extended confirmed protection may only be applied in response to persistent sockpuppetry or

9350:

for daring to moderate) Not to mention some article regulars made several visits to the AE since the implementation of the rule. Let's be real, will it be effective in some articles where there is an insistent sock or socks who make disruptive edits? Yes. Will it be effective against POV warriors and

9338:

The Gamergate controversy concerns issues of sexism and progressivism in video game culture, stemming from a harassment campaign conducted primarily through the use of the Twitter hashtag #GamerGate. Gamergate is used as a blanket term for the controversy, the harassment campaign and actions of those

9310:

All of this seems to indicate that 30/500 is capable of working against sockpuppetry. Since this is the first time (to my knowledge) the community has authorized 30/500 outside of arbitration enforcement, this might be a useful case study to inform the positions of editors on how we should use 30/500

9014:

in mainspace. His only interest seemed to be to get people to sign his guestbook to earn the {{User X}} Guestbook Barnstar. (Not to embarrass the editor, he has already been warned and has promised to change.) Is this what we want to encourage new editors to do to inflate their edit counts? Secondly,

9001:

I hate the generalization that ECP makes. Editors are always going on about how "edit count doesn't matter", then come on RFCs and say another thing entirely. Compared to other editors, I've done rather poorly on the edit count basis, and a third of my edits are in user space. But my point is that if

7885:

A significant number of articles ending up under ECP would only mean that semi protection has failed anyway ("given that semi-protection has proven to be ineffective"). Under a more conservative interpretation of option C (read as "only use this if semi has failed, i.e. instead of full protection"),

6909:

for an example. If Option C passes, then may I suggest an explicit time limit on the protection, with indef 500/30 only allowed via ArbCom directives. I see many people saying that it is "a good alternative to full-protection": but full-protection is typically only used for a short duration, till the

6841:

I knew this was where we were heading since the first proposal of this protection, and warned about the slippery slope. Edit count is becoming a wiki currency, perhaps always kinda was but never so profoundly. Let me tell you another problem with this protection, people will immediately be suspicious

6781:

before framing the policy that governs the practical use of the added protection. Step 1: You are allowed to do this. Step 2: This is the scope and here are your limitations. It'd be somewhat pointless if a policy was created and then the community consensus was "sorry you're not allowed to use ECP".

6707:

There is a reason why these all have Arbcom cases. What has come out of the Gamergate is that the admin corps needs a new tool to deal with disruption. Autoconfirmed is easily gamed and protection might be too strong. There's not been an intermediate protection level that lets newbies who have picked

6567:

I'd like to see a change to Options B or C to add "... unless the topic is already authorized for 30/500 protection by the Arbitration Committee or community discussion at AN or ANI." If the community has reviewed multiple articles related to a topic area and endorsed the 30/500 protection on each of

6390:

No objection from me. My thinking was in the early days of it, there probably won't be that many requests for ECP so the first bunch of them may (or may not?) be worth putting past the community, but after that it would be as you and HighinBC indicate, that only those objected to would be reviewed on

5246:

was repeatedly vandalized because of current events and placed under administrator access only protection level, preventing many legitimate editors from working on the article. Although it's no longer protected at that level, in the worst case, lengthy periods of vandalism would severely limit editor

4994:

with modification of 30/500: Auto-protection will reduce activity by casual bad actors, but determined ones will spend a couple hours making 500 edits to cross the threshold. Rather than (or in addition to) the total number of edits, include a parameter that looks at number of edit DAYS. For example,

3906:- Amakuru says it nicely above: under this formulation, it would be a useful mid-level of protection, with the risk of it being too restrictive kept in check by a) requirements for prior attempts of solving by semi, and b) we do assume admins to be both conservative and accountable in this regard. -- 3432:

above. Yes, this is introducing additional complexity into the protection options; but to strike a healthy balance between preventing disruption and encouraging constructive contributions, wider use of such protection would be helpful. Of course, it should only be used if semi-protection is not going

2263:

2. Unlike full that locks out everyone and semi that does not lock out anyone for long, 30/500 has real potential to lock out of editing one side of an edit war while the other remains. I am ready to believe most admins are aware of such issues, but if "most" is 90% it still means a few of them could

2259:

1. 30/500 allows a downgrade from full, which is good in general (less protection is better most of the time), but it also allows an upgrade from semi/pending when no admin would have been willing to impose full. I think this does not matter, because 30/500 is likely to come under as much scrutiny as

1453:

Thanks for asking to clarify, that was a little poorly phrased - I am not. I'm supporting (lengthy if necessary) periods of full protection to combat consistent edit warring over content disputes from real editors. And I'm supporting continuing to use the existing counter-sockpuppetry tools to combat

1273:

per Andrew Davidson (!). Already we have admins using ECP where it is not allowed. You can bet that if we loosen the policy, some admins will, out of a combination of ignorance and not caring, apply this inappropriately, neglect to notify AN as option C envisages, and so on. I would support an option

789:

blue-locked article, especially when I see the warnings of sanctions and other woes promised on disruptive editors. Even making a minor edit e.g. spelling would make me cringe. And even without the ArbCom warnings, I think the protection itself is intimidating to newbies who are terrified of making a

9796:

For the hell of it I want to point out that as an admin I have no interest whatsoever in using a new level of protection, so this is going to go right along side pending changes and super-protect as a new tool I neither wanted nor plan to use. Keep that in mind: you can role it out all you want, but

9605:

effective – contentious topic areas where civil POV pushers have not been adequately dealt with by the community or ArbCom. 30/500 will never fix issues in those topic areas (although they may lessen them). Note also that I'm supporting Option B, not Option C, as I can't think of any appropriate use

8920:

You only care to enforce ECP for people you deem are "worst editors," don't get me wrong I don't assume you are pushing a POV and allowing only the editors who share your POV while reporting others, but you have to agree that it may be used as such and is a broken system to begin with. You in effect

8880:

The environment which the extended confirmed policy creates is highly toxic. It assumes bad faith for all potential editors and locks them out, not for lack of merit, but for an arbitrary edit count and a tenure, in turn the editors who are participating in an ECP area are much more willing to throw

8805:

I've been a Knowledge editor for 10 years now and haven't reached 500 edits yet. On the other hand, I have yet to attempt to edit a protected page and been denied, so I don't think it is that harmful as is; I don't object to it staying as currently, but I do feel as though 500 edits is a lot. I've

8297:

That is exactly my point. Experienced editors who habitually vote in RfCs would naturally be much more inclined to support this because it has no effect on them. A good deal of experienced editors had a personal stake in opposing PC2, because it would subject their edits to review. However, the fact

8277:

I didn't participate in the PC2 discussions because they were during a health break for me; I'm on the fence about it in concept, and I can see some practical difficulties with it as we're set up now. Rob correctly points out one of them. The biggest one to me, though, is that if we enable PC2 we're

8030:

We don't necessarily need to try semi first. If I look at a revision history and see that there are numerous confirmed users causing disruption, I know that semi won't be effective. That is proven purely by the edit counts of the abusers. If we see that disruption is from unconfirmed users, no admin

7814:

confirmed users (blocks proved ineffective), so it was fully protected, but Yaris noticed ECP would do the job just fine so extended confirmed users can still add redirect sorting, or what have you. Next, one could conceivably have good reason to protect user pages and Knowledge pages under ECP, for

7769:

for topics authorized by ArbCom. This is why the pages you've seen under ECP thus far are of indefinite duration (not that I completely endorse this practice). This will not be the case for general disruption like edit wars, sockpuppetry and vandalism. ECP is only to be used if semi has proven to be

6878:

long time editors in both controversial and mundane topics as they try to navigate the minefields. Personally, I don't think Knowledge can return to glory without a serious trimming of policies and guidelines and a serious review of every member of the administration, and this change is antithetical

6846:

exactly like that, and it wont be the last I assure you. With this RFC going the way it is, we will be throwing the AGF out of the window and the articles with this protection will be OWNED spaces. I sometimes understand the frustration of an editor who works in a contentious area, or an admin. It's

6725:

Yes there is a reason why these all have arbcom cases, and it's not the newcomers. Yes there might be a certain amount of disruption from newcomers especially when the topic is hot. But lets not pretend that newcomers are like children and the experienced editors are the adults trying to keep order.

5335:

I believe it provides a much-needed extra layer of protection. As long as it is used as a last resort, the impact on new users will be minimal, and as someone who is involved in vandal fighting, this would be particularly useful in preventing especially pernicious vandals or those seeking to use the

5265:

Either we trust those entrusted with the mop, or we don't. As with any other action (from what I understand) taken by an administrator, if the community disagrees with their usage of any specific tool, the action can be undone. The consequence of error if an administrator improperly applies 30/500

2240:

I do not agree with most of the blanket opposes to C. 30/500 is harsh, but it is less harsh than full protection. Moreover, a new level of protection is instruction creep, but it will exist anyways (or so it seems), be it admin action or ArbCom, so the proposal does not add to complexity. (Actually,

2028:

based on the proof presented; the process there is already "requester and admin" for patrolling admins. As always, the discretion and accountability lies with the administrator. If admins go around placing protection without making a determination of sockpuppetry (or if they make such determinations

448:

here for now – My thoughts tend to align with Altamel's comment in the general discussion section below. I'm mostly concerned that if this becomes widely used, it will have a negative impact on our newer editors. With regards to an intermediary between semi-protection and full protection, we already

357:

said above, Option C gives far too much discretion to admins. This RfC does little to prevent 30/500 protection from being used as frequently as semi-protection, and I am concerned that extended confirm protection will drive away the good-faith new contributors that Knowledge needs for its long-term

75:

The obvious aside, the job of a discussion closer is to sum up the discussion, to pick out common themes, and to help provide recommendations based on those for further refinement or to bring the issue to a final conclusion. So, first, there was a common feeling—or perhaps more an acknowledgement in

10070:

I envision the report being at the top of the noticeboard, which should fit nicely next to the table of contents which is typically very long. This to me would be quite visible. The idea I think is to start a discussion when someone disputes the use of ECP. At the rate we're seeing it being applied

10055:

As a start, individual sections would be helpful to give ECP notifications some visibility. In time, this can then be migrated into a transclusion of the report. I don't know if others would want a report at the top of the noticeboard right from the start. Perhaps by then a new noticeboard would be

9931:

I join TomStar in noting that I will never use this level of protection. ArbCom instituted this new "extended confirmed" usergroup by fiat. Seeing that unlimited admin use will now become official policy, new users will be increasingly shut out as it is applied in a liberal, over-the-counter manner

9891:

I have to disagree. We also have to consider the class of pages where we previously wouldn't have used full protection but wouldn't have been able to control the disruption either. This is mostly true with sockpuppetry. It's obviously not customary to fully protect articles for long periods of time

9657:

is an absolute disgrace, but that's not under the community's control.) However, while this reassures me slightly, I still don't think it's a very nice compromise. If a newbie comes across an ECP-protected article and wants to edit it, all they'll see is that the system won't let them make a normal

9355:

by the editors? Hell yes. Will it discourage the new editors and, with the widespread usage, further decrease the already dwindling number of new editors? Absolutely. One more thing, this was supposed to be a consensus rather than a majority rule. And I see a lot of editors casting votes, but not a

9345:

What a marvelous sentence! So many buzz words, you have to read it several times to even make sense of it... And it gets no better in article body. This sanction made the Gamergate article a space owned by a handful of editors, scaring off admins and editors alike.(Latest attempt, I believe, was to

9287:

shows various IPs used by Nikita requesting the addition of false information to the article (which is his typical MO). All of them have been declined, preventing active disruption to the article. Further, you can see him asking when the 30/500 protection will expire, which suggests he doesn't feel

9139:

Why would you use full protection against vandalism? Semi effectively deters any vandal. Since the vandalism is a blockable offense, even if the hypothetical vandal was determined enough to create new accounts(which would have to be auto-confirmed first) they would easily be dispatched. Only reason

8373:

I've actually reviewed PC2 more recently and don't think I'd support it anymore in its current form. I was unclear on what exactly PC2 was when I previously gave my opinion, and I'm now concerned that the reviewer user right wasn't granted to reviewers with the intent for them to serve as basically

8183:

to add the same text as in the semi subsection, but since we haven't finished this RFC yet it doesn't make any sense to do it. Honestly, though, this RFC was open to suggestions and the draft was open and advertised for editing for almost a month before I published it. Over 100 editors have weighed

8125:

I would hope this would be incredibly obvious to all admins, but can we include text in Option C indicating that extended confirmed protection is never appropriate in response to a content dispute where one side is extended confirmed and the other is not? Full protection "works" in response to edit

8102:

users"? This requires that semi-protection has proven ineffective but also allows for the edge case where the disruption is being caused by users which semi wouldn't work on. It doesn't make sense to require the step of semi-protecting an article where the accounts being used to edit it wouldn't be

7900:

You say it will be, like full protection, always temporary. That's great, can we write that down clearly in the proposal so as to avoid any future misunderstandings? It would also be helpful to note that it's not appropriate to use ECP in content disputes, just to be on the safe side. Currently the

7836: 7790:

has no expiry which I think is problematic and will be going forward without strict rules). The irony of it being used on caste articles is not lost especially when applied indefinitely. I'd prefer a much stricter non-arbcom article time limit so as not to make the restriction a characteristic of

7689:

This is exactly the sort of viewpoint that we need to see more of, but our RfCs will always have an inbuilt bias against users like you—casual editors who would probably voice strong opposition were they aware of the proposal. For me, 500 edits was nothing, because I'm a sort of spammy-style editor

7496:

That is a step in the right direction, thanks. However, I still have my doubts with how vigorously protection duration guidelines will be enforced. Part of the reason why long-length full protection is so rare is because sysops recognize only 1,296 Knowledge accounts will be able to edit that page,

7035:

What need is there to wait—why not create it now? If there is an edit request template for the higher-level full protection, what good reason would there be to not create a template for this type? We should never create a system in which any admin can unilaterally impose protection and consequently

6858:

I would add that although vandalism commonly comes from IPs and new users, on unprotected pages it is often the IPs and new users (in other words, casual readers) who spot the vandalism and remove it. On the other hand, it will be much more difficult to vandalize a 500/30 protected page, but if the

6613:

This proposal is being voted on by the people it would affect the least: we are approaching this RfC through an enormous blind spot. Who among us has fewer than 500 edits or can remember what it was like to be a newcomer? This proposal will drive away new users, and here's why: 500 edits seems like

5058:

almost certainly a lesser challenge than 500 edits / 30 days since registering. However, I do wonder whether this complexity—and in particular the discussion and consensus required to implement your idea—is warranted for what I believe is such a small-scale problem (a couple of persistent vandals).

4564:

as a useful tool, especially against misguided single-purpose accounts. The amount of users impacted by semi-protection is significant, and those impacted by full protection even more so, yet we don't require implementation of those protections to be logged at AN, so requiring this one to be logged

3362:

primaries over the last few months. The Republican one was using the pending changes mechanism and the Democratic one was semi-protected for several periods; both articles were susceptible to 1RR and discretionary sanctions. None of these approaches were very effective in controlling the outpour of

2901:

Like others, if this option is chosen I think some guidance is warranted. While I agree with the general sentiment that this should be viewed as a tool when semi-protection is not sufficient and full protection might be overdoing it, I prefer not to be so explicit as to require evidence of a failed

2589:

we should only use this sparingly as a short-term measure for really heated issues that it would be difficult for administrators to otherwise keep on top of. We shouldn't create barriers to editing for new and occasional contributors, lest it become another gentle step away from the original vision

2319:

Knowledge has proven itself time and again to be a pure democracy regardless of the weight of arguments, and therefore option C will be implemented. The problem (as with a certain vote in my country not too long ago), is that while people are clear on what they don't want (a simple-to-game system),

1615:

ECP was always a necessary evil based on the otherwise unenforceable Arbcom decision, but anything else is just scope creep. The kind of editor willing to wait four days to make a disruptive edit is not the kind of editor you want trying to sneak 500 edits into the encyclopedia prior to disruption.

1422:

In almost all cases where 30/500 is being proposed, the use of full protection, with policy written as it already is currently, is more appropriate. The issue of stratification should carry a lot of weight - the ability to edit an ECP article is a powerful tool, and which editors do we want to give

839:

users so as to prevent ownership, and that it is the still contentious but less visited articles that actually benefit from protection from drive-by edits. This level of protection isn't useful against vandalism anyway. Allowing admins to lock people out of their pet articles without supervision is

679:

I am a bit ambivalent about the use of this on articles - I don't like it, but it is another tool to consider. What I don't like is the use of this rule on talk pages. There it disenfranchises new editors from even involving themselves in the discussion. Semi-protection serves to keep most socks at

552:

option in your !vote. Option A, the current policy, is probably the most restrictive, not explicitly allowing sysops to apply ECP for sockpuppetry / disputes, whereas the other options do. Also, does the software really prevent application of extended confirmed for a duration other than indefinite?

424:

At this point we are moving from "encyclopedia anyone can edit" to "encyclopedia anyone can edit unless it's a contentious topic." I don't think it's a useful sanction at all, it's just a tool for owning the article by the regulars of Knowledge who are not necessarily the experts of the subject and

71:

This is borne out not just by the number of participants supporting option C (though it is worth noting that almost twice as many people supported option C as supported option A and B combined), but by the detailed rationales that many of the participants left, and it was these—rather than drive-by

9486:

But the current wording states that the duration will be no different than semi or full protection, that it will be proportional to the disruption. In reality, it will most likely be used like semi protection level 2, and we know how many indefinitely semi protected articles we have. I recommended

9054:

It has been found that, although the majority of edits are performed by experienced users, the majority of bytes are written by inexperienced users. These editors lacking extended confirmation should not be penalized for the small minority of vandals. It is easier to revert vandalism than it is to

8957:

I do not deny the frustrating nature of contributing in a contentious area, and sympathize with you even though I've never edited in that area. But this protection is fundamentally flawed and it's the antithesis of Knowledge. Furthermore this protection, while it may reduce the socking, encourages

8394:

As far as I'm concerned, PC2 + semi should be available right now as an option for pages subject to extreme disruption. And yet... here we are. Even if PC2 were available, however, 30/500 would be valuable as another tool in the chest. Pages that would otherwise be subject to full protection might

7869:

My fear is that, in time, there will be as many ECP articles as semi articles, which will impact the project severely. The current proposal says it would be used against "any form of disruption" Also the duration is said to be like semi or full protection. I think the option C should be amended to

7479:

this. It's impossible to think that we could as a functioning open encyclopedia allow indefinite extended confirmed protection to be applied haphazardly. The protection duration is relative to the disruption, just as it is with semi, PC and full protection. Template protection on the other hand is

7314:

Well, I think these accidental uses are a preview of what we will see if B or C is passed(which is likely,) a beta test if you will. Notice that their expiration dates are indefinite, which I believe will be the norm. Full protection by it's nature has to be short termed, ECP is more like the Semi

6926:

A good example, digging into the past, would have been the MMA (Mixed martial arts) articles that, for a time, showed up at ANI virtually every week. There was a great deal of disruption from a lot of new accounts and IP's largely due to off wiki forums, so many articles were semi'd however, there

6621:

Now, I see many users have asked that ECP be used only rarely, or when semi-protection fails. But besides the AN notification, nothing in this proposal would actually discourage admins from excessively applying ECP. Although this RfC sells ECP as an alternative to full-protection, ECP could easily

6407:

I strongly object. If this measure is to be used "sparingly", as many supporting option C have indicated, the notifications will be occasional and will not clutter the noticeboard. If ECP is used so frequently that the number of notifications is cluttering the noticeboard, we need to reexamine the

6326:

As a disclaimer, I was the one that proposed the addition of the notification requirement during the village pump idea lab discussion. The idea, in my mind, was to require admins to post the levying of ECP on any given article for community review. The exception above means that if the article has

3859:

you are very focused on improving a particular article, thus the need for exemptions; I've sometimes worked all day long on an article in a text editor without any edits showing on WP itself). I support this stuff at all because the lengths that PoV pushers and programmatic vandals will go to, and

2417:

Option B would be a good choice. Sockpuppetry is a huge problem here that need to be dealt with. I don't see the need for option C because we already have simi-protection and pending changes which works fine. Lets not make editing for the newcomers more difficult to contribute to the encyclopedia.

1694:

I joined Knowledge last year and have made somewhere around 100 edits by now. While I feel like this tool would be useful in blocking sockpuppets, the people who it would affect the most would be people like me: good faith editors who aren't very avid and do what they can to help every so often. I

1348:

Nupedia was an encyclopedia that only experts could edit, but this led to very low levels of recruitment, and ultimately both worse articles and far, far fewer of them. These protection mechanisms take us back towards the Nupedia model in small steps after the giant leap towards openness Knowledge

951:

and strongly oppose Option C. If semi has failed to control disruption on any particular article, there must be autoconfirmed editors that are causing the disruption. The best course of action is to take those editors to ANI and get a page ban or topic ban. Locking out many uninvolved editors (who

9761:

The difficulty is that allows people to suggest changes, but generally those are turned down quickly. To be involved in the discussion about the direction of the article you need access to the talk page. We're going to see a lot of cases of 30/500 being applied to talk pages, which is something I

9679:

Why are the talk pages being placed under the 30/500 restriction. That to me seems quite foolish. It prevents discussion on the article for many editors absolutely. If the article needs protection to prevent vandalism, POV pushing or what have you then that is fine. But to lock editors out of the

9433:

The GamerGate article is a good example. Before 30/500 was applied, semi-protection was working. In the two months leading up to the restriction, very few editors who would have failed that restriction were taking part, there was no revdel, and those editors who didn't meet 50/300 were either not

8892:

with some editors assuming very bad faith. But you created this environment.Yes the autoconfirmed is easily gamed, and this protection is not, but who do you think you are barring more? Dispassionate new contributors, or the disruptive POV warriors who are willing to work their way to ECP? And by

8669:

or no CONEXCEPT, I will make it clear that I oppose this level of protection. In the end, it will become another means for the increase of stratification and administrative power, which I do not believe in. It simply is not ArbCom's business to be creating new classes of users by fiat. It's about

7841:

The current wording for the time limit clarification is "protection does not differ from semi or other forms of protection." But the semi and full protection are applied very differently, that is, semi protection tends to be longer while full protection is much shorter. I would ask the ECP to be

7664:

I agree that this is likely to have an adverse effect. I'm a fairly casual Wikipedian, I've been here since 2007 and thought I'd amassed hundreds of edits - but it turns out to be 94. To me, and I suspect *many* others, 500 edits is the same as full protection. Some of my edits have been gnoming,

5541:

Having a finer grained response is a good idea, especially when semi does not prove effective. In regards to user pages, these pages, IMHO, should only be ever edited by the owing user and by admins when there is a breach of policy. I have had my user page used in an inappropriate fashion on many

5127:

authority vested in Admins and Bureaucrats--blocking vandals, protecting pages, etc. Nor is it completely true that it's "an encyclopedia anyone can edit"--some are blocked from editing because of vandalism or use of sockpuppets. The persistent vandalism I've seen on some pages is ridiculous and

4661:

if semi-protection proves to be ineffective at preventing disruption, then the only available tools we have right now are pending changes protection and full protection. Pending changes protection is not available or not useful in a wide range of situations, such as where the disruption is due to

3624:

This adds another tool to the admin's chest, which could be useful in stopping the sorts of problems that currently slip through the cracks. However, it's only useful if admins can actually use it. The more rules governing its use, the more work it will take for an admin to implement it, and thus

3112:

I trust our admins will use this form of protection wisely, just as we do with other levels. It is nonsensical and contrary to our mission to resort to full protection when the lesser evil 30/500 would adequately control the disruption, and allow more contributors to edit. You might have found me

2066:

I am concerned, except in a few situations, about the message that this sends that newcomers are automatically less trustworthy than established editors. I think the best way to prevent new but autoconfirmed editors from with editing things they do not yet have the competence for is mentoring and

1861:

for a relatively small minority of editors. But since the extended-confirmed editor who imposes it will still be able to edit (and all his Knowledge buddies will too), he will underestimate the downside of imposing it, and do so too often. Many of the !votes for Option C appear to confirm this. -

50:

This was a lengthy RfC and took quite some reading. Thank you for your patience in awaiting a close. First of all, thanks are due to the initiators for getting the discussion underway; it was a discussion that needed to be had at some point and starting with a properly structured RfC gives us the

8930:

Right now the uniqueness of the ARBPIA3 allows you to permit the casual good faith editors because not all pages of I/P conflict is physically ECP'ed, that is assuming the established editors wont favor casual editors who support their POV. But it wont be the case for articles with ECP in place,

8905:

All ARBPIA articles fall under 30/500, but new accounts and IPs often edit in the area as most articles are not actually locked down under 30/500. I and other users only care to enforce 30/500 in the topic area for the worst editors and not at all for the casual editor. Under this system serious

8077:

Administrators already have the power to fully protect the article, which is far stronger a protection level than semi or ECP; any "if-then-else" or "if-and-only-if" approach is overly restrictive. Admins who regularly patrol RFPP and are experienced in applying protection should be, by default,

7924:

This may have been answered above but could someone clarify how extended protections are removed? Do they require a consensus at AN or can it be done at the discretion of an administrator? Or is it cannot be removed until it's time limit has expired and what about in the case whereby it has been

5650:

this level of protection would be useful. Sock puppet editors often do pointless edits just to get autoconfirmed, so semi-protection is not a huge barrier for them. I do not see a good reason for restricting this to areas favoured by Arbcom. It is much fairer if it can be applied by community

4546:

I'd like to see this used rarely, only when all lesser options have been exhausted. The concerns about discouragement to new editors, well valid, ignore the fact that higher levels of protection only have more of the same effect. Oh, and no userboxes. This isn't a matter for pride, only safety.

1551:

The reason I say this is that we need to encourage people to contribute to Knowledge. After 11 years as a user with over 20,000 edits I have found that there are folks that show up out of the blue and make positive contributions, we need to welcome and encourage them. On the other hand there are

1186:

This RfC is biased, with options B & C saying "semi-protection has proven to be ineffective", which is an (apparently successful) attempt to lead the reader to accept those options. The statement is not true in any universal sense; at best semi-protection has only proven to be ineffective in

933:

I support as limited implementation of protections as possible. As a new(ish) editor, coming across and article with any type of protections is still intimidating, and it definitely discourages me from editing, as I don't want to run afoul of whatever incident led to the protections in the first

54:

To business. Let me fist state the obvious. Of the three options presented here, option C is by far and away the most popular. While closing discussions is not merely a matter of counting heads, administrators are not entitled to a supervote and cannot ignore such a large groundswell of opinion.

10195:

We should specify that users who meet the 30/500 criteria can have any page in their userspace except their talkpage placed under extended confirmed protection upon request as an anti-vandalism/sockpuppetry/defamation measure. The value in allowing new users to edit another editor's userpage is

9050:

I took a random sample of 20 (out of ~120) users who voted for Option C. The result: most accounts were several years old, about 30-40% claimed to have made several thousand edits, and a few were administrators. I'm afraid that the people who are voting for C are not representative of Knowledge

7560:

I'm not sure technical limitations should warrant malpractice. Here we are effecting editor engagement and an article's ability to develop, and that should have priority. Patrollers are quick to re-request the appropriate protection, especially if the disruption is truly that severe; but you're

6904:

Can the multitude of people who support Option C, give a few examples of how the current none-semi-full protection system falls short on some articles? In practice, 500/30 has only been used so far as an "indefinite" (or very long duration) measure. I am concerned that this might become the new

6819:

Option C is a terrible precedent. Knowledge is the encyclopedia anyone can edit, and Option C purposely works against that. While there are points where semi can fail and full is not sufficient, requiring 500/30, and the current cases outlined by ArbCom seem reason (though I still object to how

6480:

The notification needn’t be set in stone; there’s nothing to prevent revisiting the procedure in a few months should it become a waste of time on the one hand, or be deemed inadequate on the other. I think it’s only prudent to have some ‘peer review’ under proposals B & C until a pattern of

5057:

Ah, thank you. I understand now. I still don't approve of 500/30 in the cases you support them, but I do agree that the 10 would in theory be an improvement and defend against sockpuppets who amass sleeper accounts, while not blocking any good faith users for whom editing on 10 separate days is

4743:

for examples of this happening. When it happens, semi-protection is no longer effective. Full protection is an option, but is probably too restrictive. ECP seems to me to be a good pragmatic alternative to full protection, and if applied like this will be a constructive countermeasure to sneaky

4643:

I'm a fairly new editor with less than 500 edits, but I'm not really worried about not being able to edit articles because of ECP. I mainly edit math articles, and only a tiny number of those are even semi-protected. None of the articles I have been interested in editing so far have even been

2704:

I'm in favour of admins having more fine-grained tools to deal with disruption like this. I would much prefer protecting an article with this protection level to fully protecting it. However, as others have said above, I think this should only be used when semi-protection has been tried and has

1080:

because there is unfortunately no option for opposing 30/500 protection completely at this stage. Knowledge is supposed to be the encyclopedia that anyone can edit. I fear that this new 30/500 tool, in the hands of ArbCom, administrators, or other “trustworthy” authority figures, will regularly

508:

option A in lieu of abolishing it altogether. Marginalized editors are less likely to create accounts that can be used to harass them. Silencing them with this protection policy is another form of victimization. This includes sexual harassment where female editors don't wish to edit except as

10003:

Option C, which is (unfortunately) the option being approved overwhelmingly, actually requires that a notice be posted to AN for review every time an article is protected with EPC. We must keep to this requirement and set up a mechanism to post these notifications—it is necessary that at least

8787:

Apparently my "indented" opposes above mean that arbcom has decided on the issue. It is beyond our humble ability to protest. The man behind the curtain has decided. Tell me folks, when did we decide to accept arbitrary rules? Gosh...."we" voted for them? Its kinda like the old joke: they have

7745:

Many of the option C supporters have either mentioned 500/30 ECP as intermediate between semi- and full protection. Both of those protections usually have a short duration. Some have even stated using ECP only for a short period to stop disruption. This is not the current experience. ECP is

5519:

where one would otherwise use full protection instead. Requiring posting to AN for review is not a bad idea, but I'd further suggest that it be only be used as a substitute for full protection against vandalism. Effectively relegate full protection of articles to content disputes. More full

4722:

Much needed to combat sockpuppetry. New editors are going to be turned off by the hostility inherent on the pages this would be used for already. A deterrence for new editors directly editing in these areas might be a good thing, while encouraging editors to learn and meet the requirements for

2826:, administrators already do a very good job on applying the most appropriate, minimally necessary, level of protection with their current toolset. 500/30 will just be another tool to allow a more efficient protection in some cases - and I trust that it will only be used where really necessary. 9844:

If option C passes (which is looks like it's on track to), there really needs to be some guidance for admins that ECP should only be used in cases where the page would've been fully protected if ECP didn't exist, and for a duration equivalent to how long the page would've had full protection.

9419:

Community consensus or not, this protection has been in place on Gamergate controversy article for more than a year. If we are to discuss the long term effects of this protection, that's your patient zero. And I think it's a prime example of what an ECP'ed article will look like give or take,

6708:

up some experience continue while telling complete newbies "this article has seen some issues, we'd like you to test the waters in less conflict prone articles before diving in here" as opposed to Semi protection or protection which basically prevents all newbies from contributing altogether.

3500:

support. The 500 edits also must be main space only, and still present, not reverted, etc. - far too easy to game otherwise. 30-500 is the content equivalent of a large IP address range block, a relatively blunt instrument affecting innocent and value adding editors too. Will there also be

104:

Similarly, that those of us who are long past the threshold for 'extended confirmation' will simply forget that the vast majority of people cannot edit articles under extended confirmed protection. I recommend (though this is a personal recommendation, not one based on the discussion) that we

66:

Allow use to combat any form of disruption (such as vandalism, edit wars, etc.) on any topic, given that semi-protection has proven to be ineffective. Notification is to be posted in a subsection of AN for review, unless the topic is already authorized for 30/500 protection by the Arbitration

9387:

Along the same lines, you could also argue that semi protect could have the same impact, and yet the regular limited duration deployment has not proven to be detrimental in any way except to drive off the disruptive editor who has a short attention span. ECP is to drive off the somewhat more

6739:

One thing you may have missed is that the RFC is not about the topics that Arbcom has jurisdiction over but to grant admins discretionary use of ECP in lieu of semi protection, which is very rarely applied indefinitely. The articles Arbcom have jurisdiction over has, if I remember correctly,

2607:

and agree with KaisaL. We should only be using this as little as possible and only as a short-term measure unless further authorized. I especially like the notification part of this option so that any uses of this level can have community input. If further authorization is required it can be

2495:

option C. It seems to me that option B is the main reason why this protection level was created. Implementation of option C will definitely result in Knowledge appearing to be hostile to newcomers, which is the exact opposite that this site needs to continue to maintain quality content. Many

1817:

I have read the section "Impact on newcomers" on this page, and I think edit count is not a good parameter. Given edit count is already in use as a parameter, I support option A, as B or C would lend even more weight to edit count. I hope a more meaningful parameter will be found eventually.

9652:

I agree completely that talk pages of ECP-protected articles should be left unprotected, so 30/500 doesn't completely lock out those who don't yet pass the criteria, and I imagine basically everyone in this RfC, whichever option they supported, would agree. (For what it's worth, I think the

8065:

Just today I saw an RFPP request for several pages that are being disrupted by a sockfarm of users that will all be autoconfirmed in the next 72 hours. That's one example of the kind of thing we're trying to stop, and that's how ECP will be useful to us. As administrators, we take the whole

7854:

Treating ECP as a substitute for Full Protection for vandalism is why I support option C: full protection for vandalism rewards trolls who want articles locked and punishes all non-admin editors. And if an article has a lot of new editors who want to make changes, using ECP instead of full

6412:

the community to monitor the use of this protection method. Just waiting for someone to object is not a good alternative, since the users with fewer than 500 edits that would be unable to edit an ECP article are unlikely to voice a complaint at AN, or even know what that noticeboard is for.

7649:

Comments: Articles with serious quality issues, such as largely unsourced or poorly sourced (blogs/non-RS), should not be subject to ECP or only for very short periods. Else, ECP will be protecting articles with amazing OR or fascinatingly absurd POVs with no sources cited, and preventing

8616:

One could as easily say that "if full protection is necessary, then Knowledge has failed" -- yet judicious use of full protection has been with Knowledge nearly since its inception. The small number of fully protected pages has not conferred major damage upon the openness of the project.

3589:

This is simply another tool to use, a level between semi-protected and full protection. Certainly it's better to use this than full protection on an article. However, I believe that using this should be avoided on talk pages, even when there are concerns about persistent sock-puppetry.

5959:- We're not gonna ban IP editing and require registration and sign-in-to-edit in my lifetime, it would seem. Blocking IPs is at best an inexact science and creates a great deal of collateral damage. Sockpuppetry can't be stopped but can be slowed. This is another tool for the arsenal. 8078:

given the benefit of the doubt that they will assess the situation and do their own due diligence before protecting an article. The addition of the community review requirement is to ensure there is oversight of their actions, since ultimately, admins are answerable to the community.

5038:, you are missing my point; thus, I did not explain sufficiently. My point is that it takes little effort to set up accounts, then wait 30 days to use one of them to make 500 bogus edits to vex the intent of auto-protection. However, if one was ALSO required to have at least, say, 10 8252:

I fully support PC2, but as I see it, ECP is currently the path of least resistance. We've not even established that PC2 should exist yet, and that's not necessarily a trivial thing. I just checked, and one of the current pending changes reviewers isn't yet extended confirmed. It's

5412:

You're welcome to move to the moral oppose section, but the community cannot overturn an ArbCom remedy. ArbCom has mandated that this protection level be implemented on certain articles. The community can restrict itself from applying it beyond that, but we can't restrict ArbCom. ~

4680:. As a cross-wiki editor, I pretty much agree with what's been said above. The need for a (yet another) protection level has been obvious for some time. Therefore, pioneering ECP on en.wiki would be beneficial for all (larger) Wikimedia projects, at least in terms of policy making. 3213:. I think that this option is the best of the three, but it should be used as little as possible: after every possible semiprotect or pending changes method has been exhausted, and even then, under strict scrutiny from both admins and non-admins—ideally, almost a one to one ratio. 1930:– I originally supported the creation of 30/500 protection on the assumption that its use wouldn't be expanded beyond Arbcom-initiated areas, and I'm a little disappointed that this is being rushed towards the door of being used as "just another semi-protection level" already... -- 9506:, the protecting admin, who I'm almost certain would consider lowering the length to something in the realm of 3–6 months. Nikita is absurdly persistent, so the lengthy protection period is justified, but indefinite is a bit much. I doubt indefinite 30/500 was intentional here. ~ 9458:

May I also add that this "per community consensus" case study ECP's duration is set to indefinite, much like any other ECP'ed article we have.(which we all know likely to be infinite.) Gives confidence that it will be used with serious discretion and for short periods of time...

5195:") would be a bad idea though, at that point it's really a pointless whack-a-mole, as determined vandals will eventually find their way around, and it will just end up hurting good faith editors even more, but I believe 30/500 is a good compromise for when it's really necessary. 5429:

The community most certainly can overturn an arbcom ruling. If it wants to it can entirely get rid of ArbCom. I agree in principle that such a move would be very unlikely to be good for anyone, and it isn't going to happen here, but it can be done and don't go saying otherwise.

5317:

Provides a much better alternative when semi-protection fails (but does not warrant a full protection), which I have witnessed on multiple occasions where it simply didn't stop sockpuppetry, vandals and trolls (since the requirements of becoming auto-confirmed is very easy). —

3272:

cases, not necessarily established by Arbcom or consensus, that this should be used to protect pages/topics on a permanent or semi-permanent (~6 months–1 year) basis, given multiple periods of short-term 30/500 protection and subsequent semi-protection has proven ineffective.

2921:

As others have said: another tool in the toolkit. If semi-protection doesn't work, this is definitely better than giving full protection to articles as it would allow edit requests to still be fulfilled. ECP isn't used often enough to warrant its existence otherwise, I think.

9914:

This is a silly argument; if you choose to use a protection level sub-optimally, that's your choice, but that doesn't mean it's ineffective for improving the encyclopedia. That's like throwing away a bar of gold and using that as your proof that gold isn't worth anything. ~

6341:

I think it should only be posted if someone has a problem with it to avoid cluttering the noticeboard. If nobody takes issue with the protection why take up space? It should be like a block review, we don't post every block for review just the ones someone takes issue with.

7809:

is an excellent one; This is a redirect that will not form a new article since it's merely a grammatical variation of the target article, so indefinite duration is not really inappropriate (though I would have gone with something more brief). We saw repeated vandalism from

697:

I support this option. The EC protection should be used only for ARBCOM approved articles. If another article is heavily vandalized, then fully protect and open an ARBCOM case to switch to EC protection. Perhaps ARBCOM should develop a fast-track system for EC protection?

8931:

which will only leave the sock masters who are patient enough to EC their way to the articles, and the occasional good faith editors who just passed 500/30 will be lumped together with these disruptive editors. Tell me what is the benefit of having this proteciton again?

6113:

Per Blackmane, MER-C, MusikAnimal, Carrite, and many others above. I've been fighting sockmasters for years, and they can be very creative and tough to handle. New tools that help to protect content and aid productive editing are a welcome addition to the project for me.

4864:. Re-evaluating indefinite fully-protected pages would be good but a large job. It could be incremental by suggesting that admins who service a protected-update-request on a talk page should at the same time consider lowering the page's protection to extended confirmed.-- 9170:

include vandalism (first, even). But with ECP for vandalism, then full protection would only be for content disputes (and the few other instances like generic image names). And please don't put words into my mouth, I said nothing about using ECP for content disputes.

9185:

I didn't mean you specifically would use it as such, It was a general statement, and I apologize if that was not clear. You can't though, guarantee that the admins will not use it for content disputes, even if unintentionally, being lulled by the experienced editors.

9118:) an admin sees your edit request on the talk page." If we use ECP as a substitute for full protection for vandalism, it would reduce this. Using ECP against vandalism instead of full protection, any extended confirmed user would be able to carry out edit requests. 5464:

The arbitration process is not a vehicle for creating new policy by fiat. The Committee's decisions may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be

4120:, with the idea that it is basically full protection with more users that can edit; the the page will be uneditable for a vast majority. Of course the majority of people in this RfC will be extendedconfirmed anyway, so won't notice - we have to remember the newbies. — 1193:. RfCs that depend on people adding their name to the discussion without contributing anything that hasn't already been said are fundamentally flawed and in violation of policy. Like this whole "votes followed by discussion" format - the "votes" section is supposed to 8696:

Obviously this will not make any difference, but I believe I must show my colours. Because I believe this kind of exclusionist protections and sanctions will be the downfall of Knowledge, maybe not now but a few years from now... And I want to make my position clear.

8195:

That's perfectly fine. I agree that boldly adding this would be appropriate. I'm just trying to avoid the almost inevitable cry of "But Option C said 'edit wars'!" in a month. I did participate somewhat at the village pump thread, but that language was introduced on

7939:

Given the expectation that Admin levied ECP, except ArbCom authorised ECP, would be time limited, it would be removed at the end of the time limit. Alternatively, I (taking a punt here) expect that requests for removal can be made to WP:RFPP or, failing that, WP:AN.

6905:

default "semi-protection" measure which is often used for an indefinite duration. This has resulted, in some cases, an indef semi-protection on an article for years after the original vandalism/sockpuppetry, simply because nobody switched it off. See the history of

4820:- I think it's beneficial to have a protection level between semi and full. This protection would have been extremely useful for some cases in the past where full protection was applied for content issues instead. One I can recall off the top of my head is the whole 8942:

If you had edited in the ARBPIA area you would have made thousands of reverts, filed hundreds of reports, been blocked by naive admins, and been called various racial slurs hundreds of times, due to socking. I wish you had been there years ago, then you would know.

1134:, where this level of protection was applied indefinitely to resolve a matter of petty vandalism. Such casual use indicates a risk that the project will gradually get locked up and so prevent new editors from making the edits which would enable them to qualify for 658:

I have struck my vote on the explicit assurances made that the tool use would not be indefinite in general. And as mentioned in the RfC, the tool should only be used when semi-protection etc. has failed. I do not see anything inherently wrong with this proposition.

8893:

chance someone who is a good faith editor edits after becoming an ECP, he or she will be met with extreme failure to AGF because of this environment you are creating here. I ask all the Wikipedians who care about this experiment to reconsider. I am, humbly yours,

6592:

We discussed that (see the talk page). We left it out because anyone is free to bring up anything at AN at any time, including ECP for a page, as evidenced by the discussion that closed earlier this week. This is strictly about administrator discretion using ECP.

1216:. Vandalism, sockpuppetry, edit wars, etc. can be combated otherwise such as temporarily banning single editors from specific articles etc. I don't think this policy change is really needed and think that it should only be considered if it's truly badly needed. -- 9973:

of non-30/500 users, and knowing how things work around here it was inevitable that it would eventually be made a technical protection level (although it shouldn't have been, because as we see now its usage is being rapidly expanded beyond the original purpose).

2976:. The current option between either semi-protection or full protection is too broad; there are some cases where semi-protection doesn't help and full protection halts all meaningful contributions. 30/500 is a good alternative, and should be used far more often. 10113:

I also think that transcluding MusikBot's report is the best approach. Katie is absolutely right that talking to the admin should always be step #1. Only when that fails to produce a satisfactory resolution should we start an endorse vs. overturn discussion at

9892:

when combating long-term sneaky sockpuppetry, but it's also not ideal to leave them unprotected. Long-term blue locks can be a solution when all else fails. I fail to think of any situation usually requiring full protection where 30/500 would be appropriate. ~

111:

As with any other protection, extended confirmed protection should be set for the shortest practicable duration (the initiators apparently believed this to be a given—as did I initially—but there was some confusion over it so it bears repeating in the closing

9471:

And thus, we have the RFC. For those non-Arbcom EC protected articles/pages, I expect that there will be no grandfathering of protection levels and that those pages will have protection levels reduced or readjusted to be in line with the outcomes of the RFC.

7628:

We don't need a follow up discussion on what durations to go with for ECP. The philosophy of minimum effective administrative action is already in practice and I have every reason to believe competent admins will do no different with a new form of protection

6973: 9015:

I think this will just serve to perpetrate a society where the elites only get more elite, and the rest sink into oblivion. When a non-EC editor spots an error on a blue-locked article, who's going to have to edit it? An EC editor. Which is going to inflate

4773:

An effective "happy medium" between full protection and semi-protection is long overdue, IMO. I believe this would fit the bill for those occasions when full protection is unwarranted and semi-protection fails to quench the problem of persistent and rampant

8711:

determinedly (refer back to my post under "Option A" and to what the few other opposers have said above). Judging by the responses to this RfC so far, obviously I don’t think my position will matter at this stage, but I must stand up for my convictions.

490:

Keep as is, I don't see any problem with requiring the committee approval for the 30/500. I also agree with points made about use of 30/500 intimidating new users and inspiring them to raise their edit count rather than edit only when they see a need.

10152: 7609:

as I'd rather be more focused on the actual question which the RFC frames. The discussion has already deviated from the main question. While the concern of ECP duration certainly needs to be addressed, my opinion is that it doesn't need to be addressed

7063:

These things already exist and should be working - if they are not then they should be fixed. I just logged on with my alt account that is not 500/30 - trying to edit a ECP goes to the "edit request" dialog just like full protected, and uses template

6614:

an insurmountable barrier to the average good-faith new user or IP (whereas making 10 edits for autoconfirm is quite achievable). To seasoned editors like us, 500 edits is nothing, but keep in mind new users are unsure of how to edit and may have been

8473:) If we expand this permission for more general use, it may also be appropriate to bundle the access permission to the existing bot usergroup. Bots may already be manually flagged if their operator qualifies, but do not autopromote. Any thoughts? — 8881:

the AGF away. In part because of the most likely correct assumption that anyone willing to fulfill the requirements for ECP just to edit an article must have at the very least very passionate opinions about the article subject. I've already given an

8143:

It is obvious to admins, particularly those of us who regularly work RFPP and AIV, that semi-protection is never appropriate in a content dispute when one is not autoconfirmed and the other is not. This is no different, and it's already written into

2654:

Option B is too specific, because this could be used fine to prevent issues that don't necessarily have anything to do with socking. I do of course agree that this should only be utilized in major issues where semi-protection has proven ineffective.

9113:

What about the environment that full protection for vandalism creates? It tells trolls "if you fuck with us enough, we'll crawl in our shells and not allow anyone except admins to edit." It tells non-admins "you can only edit these pages when (or

2678:

as preferable to either rampant, calculated vandalism or full protection. I join KaisaL's comments that this should only be used when it's truly necessary as, unlike semi-protection, this excludes a significant part of our user base. I think a new

4010:- Given the clarification of duration in the comments below (I had presumed that 30/500 would always be indefinite, which I now know is wrong), I now support option C. Admins need a tool between semi- and full-protection, and this is that tool. — 2150:. I'm concerned about making editing too difficult for new editors. It seems to me that the rationale of socking makes sense as being something where semi-protection really does not work. If there were to be a consensus among more than one admin 199: 180: 8348:

As BU Rob13, I support both and the community is happy to accept 30/500 thanks to GamerGate. PC2 makes more sense as it enables contributors to limit content disputes but there's far more trust in the admin corps than there is in the reviewers.

2338:. This option combines the merits of Option A with additional but limited protection. With Option C, editors with good intentions but few edits (myself included) could be locked out of making key edits on important articles. Therefore I also 9019:

edit count even more. In the future, should the community decide they want a 1-year 1000-edit restriction, the EC editor will benefit while the non-EC editor is locked out once again while he could have edited and overcome this restriction.

7670:

I understand that some articles need semi- or full protection, but 30-500 seems just a re-branding of full protection with less oversight, allowing people to effectively take ownership of an article, either in bad faith or in misguided good

6796:

I should clarify that I meant to say, "given that there is no limitation, there will be instances where admins extend confirm protect articles indefinitely." I do believe that in most cases, admins will protect for a shorter period of time.

3363:

craziness, leaving a volunteer army of level-headed editors to sort the mess repeatedly. With a 30/500 protection, knee-jerk reactions from drive-by editors would have been channelled to the appropriate talk page debates or edit requests. —

5122:

and I don't even have 500 edits yet. I'm going to stir the pot here, but I think we editors need to admit that, in spite of some of the above comments, Knowledge isn't a "pure democracy"; it has to police itself to some extent and there is

1475:

for most of the reasons already stated. It's easier to undo bad edits then to produce good edits, admins will be too aggressive in implementing this protection and it will result in turning off editors from making improvements to articles.

1291:

The current policy is working fine. Edit warring, vandalism, edit wars and/or persistent sockpuppetry can be resolved by an admin. Options B and C propose changes that may make problems worst rather then improve the current situation.( See

1274:

allowing general use of ECP with prior community authorisation, however this was already provided for by the RFC which introduced ECP and in one case (the Nikita troll) has been used. Note to closer: please see my discussion section below.

8294:

The biggest to me, though, is that if we enable PC2 we're giving the reviewers much more control over content. ... An edit by an established user...would have to be approved. ... hat rankles some people that might not be so rankled about

1330:

I'm for A because I'm against B&C. I'm against B&C because they could prevent editing by people new to Knowledge of an article because of a single bad actor. It's like banning all cars on a road because a single driver is being

5266:

is far less than that of an inappropriate deletion, or even of an IP block. I understand the arguments against 30/500 in its entirety, however I have trouble with the "it needs to be a separate bit/it is too easily misused" argument.

9600:

I highlight this case study because I see the value of 30/500 being combating sockpuppetry. This is the first time it has been deployed for that specific purpose, bar none. In a sense, 30/500 is being used currently in the area it is

9383:

It may not stop them, but it will certainly slow them down and invariably most of these editors have such a slavish adherence to their M.O. that by the time they reach EC status, they will have let slip who they are and will be dealt

87:

Concerns that reckless or naive admins will over-use the new protection level and use it in cases where it is not appropriate (which is a possibility with ~1200 admins, but I hope one that can be addressed through the reviews at AN).

6776:

You are correct that the RFC does not say this. That is outside the scope of the RFC when admins aren't even permitted to apply ECP in the first place. The community needs to come to a consensus that actually permits admins to do so

6451: 6842:

of anyone with just above 500 edits who participate in an ECP'ed article. I mean anyone who is willing to take the time to edit 500 times and wait a month just to be able to edit a topic must have an agenda, right? I actually saw a

10102:

someone has an issue, they can then raise it with the individual admin (which should always be the first step, as some of these are turning out to be simple errors – I almost did it myself the other day) or in its own AN section.

7848: 3995:. Devolution of power to admins is generally good. The criterion that semi must have been proven ineffective and the requirement for AN notification (thus opening up scrutiny) are sufficient procedural safeguards against misuse. 8047:

In that case, why bother with a written policy at all? Option C pretends to establish some kind of standard, but it really just authorizes administrators to do whatever they think is best with the power placed in their hands.

1852:

as less bad than B & C. That some editors see ECP as preferable to full protection because less restrictive suggests that it will be overused. Full protection is used sparingly because it's so obviously restrictive. ECP is

6873:

As an occasional IP editor and long time reader, I have to agree with the concerns here. Many often ask how we can improve editor numbers on Knowledge, yet additional bureaucracy like this does little but discourage newcomers

6859:

Wikipedians using anti-vandalism tools fail to spot it immediately, we can no longer depend upon casual readers to revert vandalism that has fallen through the cracks. This is a feature, and not a bug of the open-edit system.

5685:- Having previously dealt with situations where throwaway autoconfirmed accounts were vandalising topics that were already being heavily edited (making full protection a hinderance), I believe that this measure can be useful. 3375:- given that the current main alternative when semiprotection doesn't seem enough is full protection, it seems silly to have a greater threshold for the use of ECP than FP, which seems to be the gist of the other two options. 9731:

They all refer to a very broad arbcom remedy that is not just for articles but "any page", so it is really beyond the "community use" that is being discussed in this RfC. Please note, editors may request edits to such pages

4241:

As somebody who primarily works in counter-vandalism on Knowledge, I feel as if this is yet another small step to combat the issue. Sockpuppet editing is very common and this should help minimise the number of these events.

2399:

to enforce in discreetionary matters unless there's a "serious" issue (subjectively speaking). So I think Option C won't really change anything (despite the naysayers), and as Option A is by default no change, I support B.

1349:

was. I fear that this and other quality controls have reduced recruitment, and could explain much of the slowdown in Knowledge's growth. I therefore don't want to make this very strict protection mechanism too easy to use.

7901:

wording of proposal C is that it can be used against any kind of disruption, which includes content disputes gone wild. I still don't think ECP is a good idea, but at least we can minimize the damage done by it this way.

425:

might be the bigger problem. Funny thing is, WP fought creationists, Scientologists and climate change deniers and it was a stupid Hashtag that needed such draconian protection. And I remember why. It happened because an

7674:

If an article needs strong protection, give it full protection. If it needs less protection, give it semi or nothing. 30 days is a reasonable request for new but genuine editors; 500 edits is an insurmountable hurdle.

3069:. I regularly (as "on an almost daily basis") see cases where semi-protection isn't enough, and it's far from only cases of vandalism, but also POV-pushing, persistent addition of unsourced material and BLP-violations. 237: 188: 3479:

available. (No real difference between B and C.) (Yes some process overhead and constraints to reduce the non arbcom use of the process. Knowledge is and must remain essentially a responsible editors free for all.

2447:, I'm aware that this point that this is likely pissing into the wind, but I would prefer caution before adopting this wholesale. If this limited trial is successful then we could look at "Option C" down the track. 433:

the newcomers, who, short time later, topic banned from the subject. This sanction is a massive failure to assume good faith and should not be used anywhere. But if it is, it should at least be authorized by arbcom.

6512:

Will probably cast a vote soon... I hope that EC-P can effectively counter the sockpuppet accounts that are used to counter semiprotection i.e. accounts making 10 dummy edits and waiting 4 days to disrupt. (ex. see

5453:

interesting conflict if the community ever got together and formed a consensus to "overturn" a ruling of the Arbitration Committee. Generally, ArbCom decisions are understood to override community consensus—see the

9932:

to any vandalized page. Our current editor retention is dismal, and the statistics show it, but changes continue to be passed which simply make the environment even more stratified and hostile than it is already.

9277: 4740: 1597:

as the lesser of the levels of intrusiveness and complication. I agree that a new level of protection is needed. But initially, err on the side of caution. It can always be expanded if that becomes necessary.

5853:

Most of the important articles are written (although there is always need for more), so attention needs to shift from creating new articles towards protecting from vandalism the ones that are well established.

3335:– the more protection options, the better, and we need something in between semi- and full protection. I can also see this being useful for very high-traffic articles (e.g. after the death of Michael Jackson). 9701:

this is applied to, all claiming to be protected under the authority of arbcom sanctions. You may contact the protecting administrator to point out the specific authority for any one you are concerned with. —

4207:

can disrupt the pace. Clearly, it's a last resort short of full protection and the ability to apply it should be limited to trusted admins and a clear-cut set of criteria, but Options A and B are too limited.

1497:

users, and 1.4 million active users, so only those in the most active 1-2% of users can edit. I try to edit and help where I can on wikipedia, and have had an account for aaages, but don't have 500 edits yet.

9416:

Thank you, I raise these issues because I see this protection to be detrimental to Knowledge, especially in the long run. And of course I know everyone who comment on this RFC do so with the best intentions.

9261: 10246:

I also supported option A, but an exception for user space makes good sense, particularly when we note that administrators (including me) can and do fully protect their own user spaces without controversy.

6568:

them, the community should eventually be allowed to make the determination that 30/500 is appropriate within the general topic area and future review isn't necessary unless someone disputes the protection.

9487:

above in the discussion that the wording should be changed to state that duration should be set not like semi, but like the full protection which is almost always limited, but it did not get any traction.

9273: 8323:

PC2 is complicated to administer, and somewhat confusing. (so is PC1, but the combination would make them yet more confusing). EPC has the advantage of being self-operating and immediately understandable.

3317:

We need to have tougher rules on editor's use of vandalism, disruptive editing, edit war and sock puppetry. This one is the best option, but I think it should be only used when it's absolutely necessary.

1454:

sockpuppetry, i.e. SPI, semi-protection, etc. I'm not supporting using extended periods of full protection to combat sockpuppetry; that too would be throwing the baby out with the bathwater in my opinion.

9465: 7870:

state exactly which kind of circumstances it is appropriate rather than giving a general description like "to combat any form of disruption." and caution admins never to place indefinite ECP on articles.

3860:

their numbers and even coordination, have all increased, even as the number of casual vandals has gone down since the novelty of Colbert, et al., telling audiences to vandalize WP as a joke has worn off.

2642:. From what I can observe, 500/30 has worked well in curbing disruption to Gamergate and caste-related articles. Semi-protection is no longer effective against persistent sockmasters, vandals and trolls. 8742: 4051:- this would be the most effective addition and as stated - halfway between the ineffective semi-protection and the most effective full protection. Another tool against the usual flavors of foolishness. 8996: 8547: 993:, similar to the community's authority to impose "discretionary sanctions"-similars – I may be adding that as an option to this RfC – but no single admin should be able to impose ECP on their say-so. 9322: 8657: 258:

Allow use to combat any form of disruption (such as vandalism, edit wars, etc.) on any topic, given that semi-protection has proven to be ineffective. Notification is to be posted in a subsection of

7315:

that it can be used in long periods because the article is technically open to edits. Caution to anyone who see this as a lesser evil. Also someone who has no job never fails to amaze the occupied.

5398:

So much for the public part of WP. I have no tin foil hat but WP (and its "Arbitration committee") does begin to resemble animal farm. Noting that there was no choice for no such protection at all.

5148:

As long as it's used in accordance with the protection policy, I see no issue with this, it's a useful protection level when semi-protection does not suffice but full protection would be excessive.

9064: 7755: 7412:. The only time an indefinite duration is appropriate is for topics authorized by ArbCom, and even then it's no hard requirement. Usage of 30/500 will follow that of any protection level – use the 6010:

Like others, I see it as less restrictive than an uncontroversial power available to all admins, and a useful option for the appropriate case. I do think notification at RFPP should be sufficient.

8899: 7224: 9232: 8833: 8703: 6035:- I'm going to pile on also. My reasons are mostly the same as those expressed above by MjolnirPants and MusikAnimal. This will be another useful tool and semi-protection is too easy to game. - 9045: 6075:- I see it as an alternative between full- and semi-protection. Time limited. Few good contribs will be banned, but mostly a newbie and a high controversial issue ... it doesn't fit together. -- 5848: 359: 9070:

I would wager that many of those users you sampled would also be well experienced in, or personally exposed to, the disruption that led to the RFC. Might I consider you spend a month or two on

8779: 8434: 6374:

I agree. I think require notification in every instance may be overkill. We obviously need to monitor make sure it doesn't get overused but there are better mechanisms than counting AN posts.--

6237: 4269:

remove the requirement for posting a notification to AN review, we don't do that for full protection so there's no point in doing so for 30/500 - especially considering that full protection is

470:

Recognizing that 500/30 is needed at times, this should only be determined after evaluating the case to know that semi really is not working and other forms of admin actions can't handle it. --

78:

there is a consensus that extended-confirmed protection should not be used as a first resort, and possibly only where full protection would be necessary were it not for the new protection level

9220: 8688: 5863: 9522:

Reduced to six months. This discussion should also determine if these kinds of protects fall under arbitration enforcement. I've gotten a couple responses indicating that they don't, However

8806:

created a dozen or so pages, fixed a couple hundred typos and errors, added some sources, commented on some consensus discussions, and in 10 years I'm at 350 or so edits total. 500, really?

8797: 5283:- Would be fine with Option B as well, but I think the added flexibility in Option C may be beneficial in some other situations, and I trust that the flexibility would be used appropriately. 989:'s point should resonate with everyone here: 500 edits is quite a lot to a newcomer. I may support cases where the community reaches a consensus (at AN, for example) for imposition of ECP on 10288: 7542:

I can see why long EPP may be jumped to - technical limitation of not allowing stacked protections and having to watch to put back on something else if needed prior to the new expiration. —

5520:

protection = less editing = discouraged editors but more encouraged trolls. Less full protection = more editing = more editors and more discouraged trolls. The only exception I can see is

2496:

protected pages are major pages, which are often the ones where new users will first try to edit Knowledge. Making that an immediate locked door will no doubt turn those new editors away. --

9307:

Multiple CU checks have been run on Nikita since 30/500 was deployed. None of them have uncovered accounts that appear to be successfully making their way toward extended confirmed status.

9304:) which got him blocked. No similar account has been found since then. I've been monitoring new user pages to check for any that have an unusual number of edits, and nothing has popped up. 9292:

recall him making edit requests or requesting information about the expiry time on semi-protected articles; he just used sleeper accounts to get around the semi-protection without comment.

8815: 6200: 3703:

I am concerned that this new privilege could be abused and used to keep away newcomers but as many others have said, semi-protection is easily gamed and does not stop persistent vandalism.

2237:, as much as I would have liked to support option C. (And scrap the automatic posting at AN for review, if someone that is actually editing the article disagrees they can raise the issue.) 10256: 9127: 7321: 7309: 6847:

easy to lose perspective and see the IP's and New editors as a disruption, but they are what makes this project what it is now. You are breaking the Knowledge albeit with good intentions.

6369: 3625:

admins will be more reluctant to use it. This, in addition to the restrictions those rules represent on their face could severely strip this option of usefulness if regulated too tightly.

588:

No, the most restrictive (from a new editor's point of view) is option C. Option A is where ArbCom is going to use ECP. Option C is where ArbCom and any perceived disruption will use ECP.

9585: 9192: 9180: 9146: 7907: 7895: 7880: 7864: 9103: 8721: 8404: 8312: 5915: 5715: 627: 598: 576: 10220: 10108: 9825: 9493: 9481: 9426: 9411: 9397: 9206: 8964: 8952: 8937: 8915: 8582: 8385: 7659: 7491: 7455: 7387: 6732: 6223: 5828: 5757: 5407: 5204: 5157: 785:- Normally I don't get involved in these kinds of things, but I don't like this kind of protection at all. As a recently extended confirmed editor myself, I still shy away from editing 669: 652: 105:

consider putting a red background in the edit window as we do for admins editing fully protected pages and template editors editing protected templates, or some similar visual reminder.

10241: 10043: 9617: 9517: 9366: 9267: 8513: 8502: 8284: 8211: 8190: 8174: 8154: 8072: 7252: 7237: 7030: 6693: 6599: 10096: 10082: 10065: 9988: 9960: 9839: 9637: 8626: 8042: 7965: 7640: 7623: 7196: 6936: 6892: 6868: 6671: 6583: 5172: 4534: 4483: 10170: 9946: 8060: 7826: 7800: 7781: 7684: 7583: 7572: 7548: 7427: 7401: 6958:- Is there any possibility of creating a suitable method for non-extended-confirmed users to suggest changes to a 30/500-protected article? For semi-protected pages, users can place 6505: 6400: 6124: 3671: 2865:

where semiprotection has clearly proven ineffective. We should always be using the least drastic measure; most garden variety vandalism sprees and the like can be handled with semi.

2385: 2245:

the complexity...) And finally, newbies are underrepresented in the decision-making that takes place here, but (1) it does not mean the decision reached will be wrong and (2) so are

1313:

Lots of votes in the other two sections betray misgivings like "not to be used too frequently" and "only in the right circumstances". It's easy to see that this is a slippery slope.

9756: 9742: 9726: 9708: 9450: 8272: 7530: 7510: 7347: 7084: 7058: 6853: 6757: 6469: 6385: 3561: 9926: 9860: 8364: 8087: 8025: 7740: 7730: 7706: 6999: 6352: 5792: 5778: 5424: 321: 10127: 9689: 8114: 7129: 7114: 7099: 6806: 6791: 6771: 6441: 6336: 6162: 6147: 2056: 1541: 9903: 9771: 9747:

Huh, sorry, I had been entirely unaware that this existed. I don't need to use it (am extended confirmed). It's not exactly the most user friendly system but at least it exists.

6422: 5934: 3268:

as long as this is used as a last resort (i.e. after multiple blocks have been ineffective), and not as a default measure for persistent disruption. I do believe however that in

2001:

requires diffs and proof before they take on a case. This well-meant option requires no proof, and relies on the judgement of the requester and admin. Too much room for error.

1984: 1463: 1448: 1239:

I accept the occasional need for 30/500 protection, but not its extension as proposed in B or C. Those who propose this change need to make a stronger case for why it is needed.

175:(also known as "30/500 protection") is a new level of article protection that only allows edits from accounts at least 30 days old and with 500 edits. The automatically assigned 6832: 5074: 5052: 5029: 2010: 1805: 1779: 9886: 9674: 9559: 9536: 8335: 7949: 6618:

by unnecessary warning templates on their talk page. The more frequently a newcomer encounters ECP-locked pages, the more they will conclude that Knowledge does not want them.

207: 9010:

supporters are making the generalization that edit count shows how useful you are on Knowledge. Yesterday I encountered an editor with more than 3,000 edits, with only around

8010: 5444: 3510: 3473: 2571:

This is a great intermediate option between semi and full and would cause minimal to no disruption since we already have an edit request system in place for protected pages --

1366:

or rather definitely oppose the other ones. The latest comment (as I write) on option C says it all about what the current majority thinks Knowledge should be headed towards:

10146: 9733: 7075: 7105: 4363:

as additional variables would be beneficial, such as when dealing with long-term abuse/sockpuppetry where the existing alternatives would be far more restrictive. Regards,

3571:- we trust admins to full-protect, delete and block, so we can trust them to do this and not use it as a "kick out everyone I don't like in a content dispute" magic button. 3529: 2534:

One more option in the toolkit. Sockmasters, vandals, trolls etc have been getting more savvy lately, so as they get trickier so must the toolkit evolved to deal with them.

6762:

Nothing in this RfC says ECP can only be applied for a limited duration. And given that there is no limitation, admins will extended confirm protect articles indefinitely.

2138:- Without prejudice to Option C if proven to not be effective - the impact on (legitimate) new editors is likely to drive editors away from the project in frustration. -- 1112: 9951:

On a point of fact, false. ArbCom applied the 30/500 restriction to the ARBPIA zone. It was a community decision to implement this using a usergroup and protection level.

8611: 2329: 9845:

Otherwise, despite the best intentions of admins like you, I can see it greatly increasing the number of pages that a majority of Knowledge editors are unable to edit. --

9159:

Semi protection deters the common "can I really do this?" vandals, but it doesn't stop the sort of sockpuppeting vandals (those are not exclusive categories) you find at

5486: 4086: 4433:

ECP limitation to sockpuppetry/disputes bureaucratically, even with logs. However, if ECP instances are not notified, I'd go with current policy, which is the cleanest.

8868: 8184:

in on the options given. We cannot keep amending it now and expect any kind of consensus. If Option C passes, I give you my word that I will add that text to BLUELOCK.

6920: 4697:

Unswayed by the 'this destroys Knowledge, the encyclopedia anyone can edit' and 'scares off the newbies' mantras. A useful tool for dealing with LTA and sock puppetry.

2256:

I see two arguments against 30/500 as admin action, and the second one is what pushes me to support B as a "trial option" before going full C (my clear second choice).

9698: 7090: 4618: 2987: 2029:

with no regard to proof), then that's an issue of tool misuse. I don't believe I've ever been convinced that a rule shouldn't be made because people could break it. ~

794:

reading Knowledge policies and editing my user space before starting to make constructive edits. While not fully supporting this, I agree that it's by far better than

721: 10205: 8862: 6717: 6447: 1160: 10022: 6984: 6560: 1844: 8526: 8470: 7476: 6634: 6211: 6135: 5767: 4614:

in limited situations - mainly for sockpuppetry and tendentious editing by SPAs - as per MusikAnimal. It's another useful tool, but it shouldn't be used in excess.

1767: 183:

with the primary intention of enforcing various arbitration remedies that prohibit editors under the "30 days/500 edits" threshold to edit certain topic areas. The

5985: 4856: 4404: 2563: 526:. Option C is too restrictive. While Option B is better than Option C, there should also be an expiry date or a mechanism in place to allow the removal of 30/500. 8246: 8137: 7171:

on the talk page of an ECP page, and the template doesn't actually care – it senses the editprot level on the target and picks up on the fact that it's ECP anyway

4765: 4635: 3104: 2715: 1305: 1172: 866: 7746:

generally applied as a permanent page restriction. Is option C only attractive if there is a commitment to expirations similar to full and semi expirations? --

7364:" perhaps, that doesn't get packaged to sysops by default. Who would grant this permission? Bureaucrats? I personally don't see this happening any time soon. — 6292: 4744:

vandalism from gaming autoconfirmed socks. Option C also gives the option for other scenarios in which it may be needed, without the need for full ArbCom cases.

3770:

Obviously the best option. This serves as a very reasonable intermediate step between semi and full protection and I see next to no risk in extending its usage.

3420: 1147: 6320: 5694: 5642: 5554: 4960: 4835: 3987: 3970: 3136:

So much time is wasted combatting persistent vandalism, POV-pushing, etc.; time that could be spent on creating new content. More flexible tools can only help.

3061: 2351: 2314: 2142: 1729: 95:'s suggestion on the talk page to send a mass message to all admins informing them of the policy for use of extended confirmed protection is one I endorse, and 9576:

Given how often this comes up, it might be worth tweaking the policy text - but I guess it'll be edited to reflect the result of this RfC eventually anyway...

8197: 5677: 5390: 4421: 3327: 3145: 2871: 2359:(moved from option C) – I changed my mind, actually I don't think there are really any valid uses outside sockpuppetry that can't be dealt with in other ways. 2076: 1922: 1322: 777: 440: 9810: 7246:

usages, and some accidental usages. For any specific page that you think is improperly protected, please start on the protecting administrators talk page. —

5740: 5597: 5257: 5139: 4460: 4355: 4260: 4060: 3762: 3640: 3164: 2634: 2578: 2180: 2093: 1036: 973: 283: 6182: 5533: 4972:

created and used to get around 30/500 should be blocked on-sight unless consensus is established that they are not the sock accounts that they appear to be.

4714: 4570: 4389: 4372: 4324: 4002: 3881: 3442: 3260: 3128: 2933: 2742:

as a useful and relatively benign tool that should be available when full protection would otherwise deprive established content editors from participating.

2670: 1686: 1507: 1485: 827: 536: 8479: 6703:

Many newcomers are diving into the most contentious and bitter of dispute areas, Israel Palestine, India Pakistan, Syria, American Politics, Gamergate, etc.

6104: 5951: 5901: 5889: 5114: 4905: 4873: 4812: 4606: 4285: 4112: 3953: 3847: 3581: 3308: 3291: 3184: 3038: 2913: 2893: 2368: 2163: 1283: 704: 345: 6258: 6088: 5605:

a useful too that can provide an additional measure of protection to controversial pages. I don't see a reason why use has to be limited to Arbcom only. --

5309: 5009:

Am I missing something here or do you not understand what 30/500 is? The "30" means "account must have been created at least 30 days ago". So yes, someone

4932: 4783: 4731: 4653: 4233: 4216: 4158: 3695: 3227: 3205: 3022: 2951: 2835: 2814: 2543: 2451: 2130: 1704: 1607: 1561: 1494: 1397: 1204: 883: 743: 416: 306: 9351:

SPA's who are willing to put in the time and reach 500/30? Nope.(even if they are sock accounts of banned users.) Will it make it easy for articles to be

5614: 5580: 5511: 5004: 4986: 4948: 4800: 4753: 4585: 4043: 4026: 3815: 3346: 3277: 3239: 3081: 2853: 2763: 2751: 2519: 2040: 1827: 1669: 1231: 1055: 760: 518: 6002: 5968: 5524:: applying it to a user page when that user (who has extended confirmed status but is not an admin or template editor) requests it for their user page. 5292: 5234: 5097: 5043:

30-day account and use it just for a single purpose one day. It would take at least 10 days of effort to get there. Get it? So, this would be 30/500/10.

4689: 4672: 4307: 4195: 3923: 3898: 3599: 3403: 2968: 2734: 2696: 2439: 2409: 2293: 2274: 2210: 1959: 1758: 1589: 1524: 1432: 1358: 1265: 925: 500: 371: 6275: 6050: 6027: 5660: 4888: 4556: 3832: 3616: 3489: 2617: 2599: 2505: 2483: 2471: 1945: 1895: 1878: 1648: 1631: 961: 943: 849: 399: 9402:

I also want to point out that I'm not arguing with you because I think you're wrong. In fact, I think you raise excellent points and worthy of debate.

8016:

Excellent point. While I still prefer Option A myself, I'd feel better about C if we agree that semi-protection and/or pending changes be tried first.

7712: 7676: 6067: 5349: 5042:

in one's history, then this takes much more effort, because it requires making at least one edit on 10 different days. Thus, one could not take a : -->

4316: 4140: 3792: 2797: 2646: 1477: 1414: 1248: 1072: 908: 689: 482: 5371: 5327: 5275: 3744: 3711: 3461: 2780: 2113: 1090: 1019: 453:. But PC2 has been rejected every time it's come up. I'm still thinking, but I'm very hesitant to extend 30/500 beyond our most strife-torn articles. 383:

outweighs them. I agree strongly with the sentiments of Altamel and Biblioworm, both of whom phrased their concerns much more eloquently than I have.

10136:

is very useful (watchlisted!) - however any bot operator can freely stop their bot any time, for any (or no) reason. If consensus is that a posting

7933: 5196: 5164: 5149: 4598: 4332:- I've felt for a while that a usable intermediate between semiprotection and edit=sysop was needed. This seems like it'll accomplish exactly that.-- 3367: 3005: 2360: 2229: 1383: 1340: 462: 143: 84:

There is little appetite to see extended confirmed protection become commonplace, and certainly not anything like as commonplace as semi-protection.

4881:

The current restriction on use is silly bureaucratic policy-nazi nonsense and we need to do away with that sort of self-inflicted handicap.--v/r -

5906:

I most certainly agree on that. Userspace pages, controversial pages, pages targeted by sockpuppets and such should have this kind of protection.

6454:

will give us what we need, but it'd be nice to have a clean automated report to some subpage that we can transclude wherever we want, namely AN.

1677:

there's plenty of modes of protection as is, and extended confirmed protection is strict enough that it should be used as sparingly as possible.

7954:

Yes, non-ArbCom usage of ECP works like any other protection level and can be removed at admin discretion, requested at RFPP, or simply expire

10225:

I supported option A, but I agree that userspace should be an exception and anyone should be able to request ECP within their own userspace.

4824:

outrage when Zayn left. It would be useful for articles about current events, which are particularly vulnerable to edit warring or vandalism.

1190: 8671: 3299:

With Knowledge's size and fewer active editors, tougher protection is needed against inappropriate behavior like vandalism and edit-warring.

2460:. Option C is too vague, which introduces the potential for misuse. A clear demarcation of when it would be okay to use—i.e. passing through 2959:- It's the best of the options being offered, but I'm unsure of how effective it will be over the long haul. But it's better than nothing. 7577:

I'm not saying it is a good reason - just that I see where it may happen...I was just thinking of bot options too--will ping your talk. —

4940:

as a way to control certain types of disruption. However, instead of cluttering an existing admin page with compulsory notifications, an

3752:

Forcing the use of ECP to be confirmed by a review at AN and only allowing its use proportionally seem like reasonable restrictions. ----

509:

anonymous IPs. Reject expanding this as it would be detrimental to efforts to attract diverse contributions and close the gender gap. --

8713: 5039: 4840:

Yes, but I'd agree with EventHorizon, we should review all Fully protected pages and see which ones can step down to extended confirmed.

2982: 1437:

Are you suggesting using lengthy periods of full protection to combat sockpuppetry? Just want to make sure I'm reading this correctly. ~

1082: 7973: 4094:, as a finer-grain protection level that is both a relatively low bar for constructive editors and a relatively high bar for vandals. 3823:- I have confidence in the admins to use this in a proper way. It can be a usefull tool inbetween semi- and full-protection. Sincerely, 3536:

already exist and are being monitored. Just wanted to mention to avoid any possible duplication of processes in case folks were confused

2395:- The problem with discretionary power is not that it is prone to misuse, but that it is discretionary, and I have seen more of a trend 10211:

I consider myself one of the loudest voices in opposition to ECP, but I have no objection to DavidLeighEllis' sensible proposal above.

6990:

Feel free to create a RFC for this question after this one is complete. Adding things in to a structured RFC usually just causes chaos

2843:

Though I think posting at AN every time it is used is excessive. I think it can just be posted there when someone takes issue with it.

2376:

So much for the public part of WP. I have no tin foil hat but WP (and its "Arbitration committee") does begin to resemble animal farm.

1532:

So much for the public part of WP. I have no tin foil hat but WP (and its "Arbitration committee") does begin to resemble animal farm.

1997:

that make the claim it's sockpuppetry. Maybe it is, maybe it isn't, but the article history shows IP edits and/or redlink accounts.

10018: 9984: 9942: 8684: 8308: 8261:, to be fair, but what even happens from a technical standpoint when that occurs? Can the reviewer review edits but not make them? ~ 8242: 7054: 2551:

as an obvious intermediate to semi and full, which, being less restrictive, should not be subject to more use-restriction than full.

341: 271: 10032:. An individual section heading for each new protection will be overkill, I think, but I can make that happen too of we really want 7855:

protection allows more editors to carry out edit requests, reducing the amount of time before someone can carry out those changes.

2680: 10140:

be placed on every use, - expect this step will be missed, especially if anyone is used to someone else's bot doing it for them. —

8425:

full protection, with no apparent end in sight. These are exactly the sort of situations in which PC2 + 30/500 might prove useful.

5215: 2045:

While Option C goes way too far, in my opinion, its preferable to Option A by a wide margin. Option C is my clear second choice. ~

7978:

Option C would allow 30/500 limitation, "given that semi-protection has proven to be ineffective". As written, this is a general

7501:, I see many indefinitely-semi'd articles that should probably have been unlocked years ago. I can provide examples upon request. 6646:-Oh, I see you want to contribute to something related to the Israeli–Palestinian conflict, excuse me but you first have to edit 5930: 5469: 3607:

Per MusikAnimal. Not only has this proven effective in contentious areas, it is also a more precise option than full protection.

1391:

Current policy seems to be working fine. Changing it is unnecessary and prevents new editors from contributing to the wikipedia.

730:: The 30/500 protection was created for extraordinary circumstances, and should remain limited to extraordinary circumstances. ~ 4913:

a very useful tool as long as it is the most appropriate lowest level of protection (that is, that semi protection won't work).

1639:

Let's keep things as they are, I don't see how options B and C will help, they seem to just create more committees and rules. --

4174:

assume that our admins act in good faith and to imply their work needs additional control is an expression of mistrust; as per

259: 249: 7223:

By the way am just misunderstanding this or are some admins already using ECP for articles that weren't sanctioned by arbcom.

108:

At least one editor cautioned against over-using the new protection level and starting an "arms race" with disruptive editors.

10159:. That lists all protection chronologically. The bot report merely allows you to "watch" for changes and transclude the page 9379:

rather than by Arbcom. ECP on Gamergate is under Arbcom jurisdiction so should be considered in a separate context. You ask:

9051:

editors in general, especially since most people would be unlikely to vote on this page, let alone know about its existence.

8418: 277:

For clarity, please support only one option. Supporters of option C may inherently support option B unless stated otherwise.

6191:

This to me is the "In case of emergency, break glass" option to deal with vandalism when semi-protection just won't cut it.

5628: 4597:

in very strict circumstances. Many newer users (such as myself) who do not meet the criteria will be put off contributing.

3354:– This would have spared myriads of editor hours and heaps of reader frustration had it been applied to the articles about 3046:

per Randy Kryn. I support the fullest possible implementation to protect the hard work our content contributors have made.

2218:

I think we might want to expand it further in the future, as with C, but we should get some more experience with it first.

1720:

can edit; users are encouraged to . Currently, there are 28,741,544 editors on Knowledge, yet only 25,247 of them are ECP.

10298:

Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

10156: 5993:

Seems the most reasonable tool against people with good intentions but lack of understanding of the Knowledge guidelines.

2188:- I don't think that Option B is perfect, but I think it has the right idea behind it. The other options are not better. 985:

ArbCom has not authorized it. This creep is not OK. We don't need to alienate and bite newcomers more than we already do.

7279: 6884: 5385: 3235:- This is a more precise tool than full protection, it should be permitted for use in more situations rather than fewer. 2325: 9288:

himself capable of vandalizing the article until it's gone. Having dealt with this sockmaster quite a bit before, I can

297:

As the lesser of evils. I am against this type of protection in general, and prefer the old "nothing-semi-full" system.

10283: 9256: 8857: 8410: 7382: 7304: 7191: 6555: 6526: 6498: 5926: 5823: 5163:

Moved to Option B – I changed my mind, even though this option seems to have the most !votes so it may end up passing.

5013:

make 500 edits in a day to cross the threshold, but only if they had also waited a month since creating their account.

4941: 4529: 4455: 4341: 4082: 3758: 3556: 622: 571: 8738: 2683:

level that held changes by users who weren't extended-confirmed (instead of merely confirmed) may be a better option.

717: 8498: 8409:

By the way, extended full protection of articles due to extreme disruption is not a hypothetical. Right now, we have

7721: 7123:- anyone who is extended confirmed that is interested in following these requests may want to watchlist that page. — 6917: 4644:

semi-protected. A new editor who is serious about improving Knowledge can easily find interesting articles to edit.

4507:

may be able to handle the task, so if the RfC passes for B/C, can perhaps have an implementation discussion post-RfC

4034:- As long as this is used responsibly, I think it's a very good addition as a step between semi and full protection. 3872: 3501:

exceptions allowed for those who can demonstrate good behaviour but do not have 500 edits ? as per ip range blocks ?

2249:

in the instances where the drinking and driving ages get decided. Newbies might be as intelligent as veteran editors

666: 649: 206:

This request for comment seeks to establish such a community process for the use of extended confirmed protection. A

23: 6608: 7068: 5885: 3579: 3522: 3180: 1493:

for the least bad option. Having 30/500 protection will turn away all but the most elite of users. There are 24608

5568:-an article on a controversial subject attracting a lot of disruptive editing by throw-away autoconfirmed accounts 5179:

Though probably not in the scope for this RfC, I would support making it 30/500/10 which would make it harder for

3978:. I expect that admins who choose to employ these tools will be responsive and flexible in response to concerns. 604:

Ahh I see... looked at this from the wrong perspective. (we serve editors after all) Thanks for letting me know —

10133: 10029: 9680:

discussions on the article's talk page as well, that's too much. I can hardly think of any reason to ever do so.

9280:. Now that it's been "in action" for two weeks, we can start to take a look at whether it appears to be working. 8985: 8889: 6948:

The edit request process should already be working - if it is broken it does not need to wait for this RfC to fix

5876:

as autoconfirmation is too easy to achieve, and admins should be able to combat vandals without full protection.

4924: 9998: 3285:, except that I see no need to ask for review on AN. Better to handle it as a protection option like any other. 6514: 4981: 4180:'It should be like a block review, we don't post every block for review just the ones someone takes issue with' 4019: 3811: 2321: 1977: 1187:

specific circumstances, and even that is disputable, since page protection is not the only tool in the toolbox.

274:. The one exception is topics authorized by the Arbitration Committee, which are often protected indefinitely. 270:, extended confirmed protection does not differ from semi or other forms of protection in that the duration is 17: 9606:

outside of sockpuppetry. If Option C passes, I'll be scrutinizing such applications of 30/500 very closely. ~

8821: 8573:. For the most restrictive implementation measure of extended confirmed protection, I would support option A. 8120: 1716:-the majority of edits are made by good-faith but low edit count users. Knowledge was founded as "the 💕 that 1181: 9548:

Mind clarifying the above? That's not the way I read that passage, but it does seem to be a valid reading. ~

8992: 8543: 6518: 5844: 4368: 4073: 3918: 2771:: Perfect where ever recurring semi P is insufficient, full P too restrictive, or pending P inappropriate. - 1840: 8734: 7786:

I'm concerned because even outside the lines articles have very long time or no expiry (the example article

6303: 5218:

and other popular articles need this type of protection when semi-protection is not helpful in these cases.

713: 10008:

degree of accountability be maintained here. Could we have a bot (such as Cyberbot) take on this function?

7166: 7074:. Additionally, if the talk page is protected such as with that gamergate page - the edit request goes to 7008: 6962: 6533:

dummy edits on their userpage or sandbox, that would be detrimental to this project. EC-P will likely make

6020: 5897:

nice for userspace pages, extremely controversial pages, pages targeted by sockpuppeteers and many more. --

1936: 1873: 1095:"because there is unfortunately no option for opposing 30/500 protection completely at this stage." Indeed. 916:

per arguments above, in particular because I'm worried about the possibility of this being over-applied. --

8882: 8223: 6843: 2879:

Much too easy to create new accounts. "Anyone can edit" should really be "Anyone can edit, responsibly".--

8603: 5981: 5668:- should clearly be useful, and will help admins deal with awkward situations on controversial articles. 4847: 4401: 4186:

protect articles under some circumstances (e.g. vandalism sprees), but that would be another discussion.

1104: 900: 176: 10190: 10056:

created to furnish ECP with a home and individual cases can then be pulled from there to AN for review.

9381:

Will it be effective against POV warriors and SPA's who are willing to put in the time and reach 500/30?

4203:: Best option to deal with sockpuppets, IP-hopping vandals, trolls and all the other ways users who are 9654: 9581: 9302: 9090:

for a sample of the environment that necessitates protection of whatever level. The various entries at

8958:

the ownership of articles which is another big problem, at the end It is more trouble than it's worth.

6969: 6529:. as far as I'm aware this is happening quite a bit) If they start to create sleeper accounts and make 4631: 4615: 3736: 3100: 2977: 2479:

can't really think of may times that 30/500 would really help, other than sock and arbcom sanctions --

1301: 1168: 1027:. I'd leave well enough alone, our existing protection should deter most socks and bad-faith accounts. 1015: 862: 7837:

ECP should be treated exactly like Full Protection and further clarification on when to use is needed.

4896:

As another intermediate level in protection that admins have available to fight persistent vandalism.

3153:- This will prevent vandalism from socks on pages, and works much better than having Semi-Protection. 3030:, and, given the persistence of some vandals, I'd raise the edits to 1,000 (and erect a wall and have 1993:- "for persistent sockpuppetry where semi-protection has proven to be ineffective" I've seen several 262:

for review, unless the topic is already authorized for 30/500 protection by the Arbitration Committee.

252:

for review, unless the topic is already authorized for 30/500 protection by the Arbitration Committee.

10201: 9356:

lot of arguments for the pros and cons of this protection. I really wish Knowledge was a place where

8622: 8430: 8400: 6288: 6233: 6196: 4346: 3416: 3359: 3355: 1156: 1143: 191:

that established expectations for use of the protection within the scope of arbitration enforcement.

99:

is to be commended for volunteering his bot to assist with tracking new uses of the protection level.

9791: 6654:

articles to be eligible! Because, after all, a good editor is an editor with the highest edit count.

4068:

It would need to be a last resort rather than a first; but that's merely the kind of judgement that

10071:

now, we're going to see a lot of headings with little or no discussion, cluttering the noticeboard

9284: 9060: 8988: 8561:

Prohibiting edits from users with less than 30 edits and 500 days tenure is a remedy passed by the

8556: 8539: 8357: 7655: 7515:

No need to provide examples. Ask the protecting admin about it, and if you get no response post at

7158: 7150: 7120: 6569: 6534: 5840: 5736: 5635: 5593: 4364: 4351: 3983: 3966: 3533: 3054: 2347: 2310: 1836: 1725: 8452: 3931:- although I don't follow either topic closely, this protection framework has proven effective in 10196:

extremely low. Even if otherwise required, AN posting should not be necessary in this situation.

9821: 9006:

right now, I might be at 1500 edits at the end of the month. But I don't want to. And the Option

8494: 8486: 8414: 7018: 6888: 5911: 5673: 4566: 4417: 3323: 3141: 2072: 1917: 1318: 773: 8986:

https://en.wikipedia.org/Wikipedia_talk:Arbitration/Requests/Enforcement#WP:ARBPIA3.23500.2F30_2

5748:. With Knowledge's increasing maturity, protection against vandals must be made more effective. 4944:

should be available to see what pages are ESProtected. Such a list would be more useful anyway.

3943: 2590:

of a free and open encyclopedia. That said, it's a tool that would be eminently useful to have.

10276: 10013: 9979: 9937: 9797:

if I won't use it then it is essentially no more effective towards improve the encyclopedia as

9502:

allow ECP with "Arbitration enforcement" as the reason and "indefinite" as the length. Pinging

9249: 8977: 8850: 8679: 8647: 8303: 8237: 7498: 7375: 7297: 7184: 7049: 6548: 6485: 6358: 5977: 5816: 5440: 5367: 5135: 4842: 4522: 4448: 4398: 4337: 4258: 4056: 3634: 3549: 3159: 2630: 2552: 2176: 2089: 1950:

I'd prefer to see how we go with this for a while before we give all 851 admins carte blanche.

1032: 615: 564: 336: 4229: 194:

The protection policy currently states that extended confirmed protection may only be applied

10132:

Important note: Bots, and their edits, are the responsibility of an editor. I do think that

9835: 9577: 9543: 9329: 9176: 9164: 9123: 9033: 8767: 8099: 7891: 7860: 7725: 7680: 6914: 6906: 6178: 5529: 5128:

helps no one, only to tie up Admins and editors who might otherwise contribute good content.

4928: 4762: 4729: 4705: 4627: 4468:

I strongly support the use of a bot here. Possibly on a transcluded subpage of AN similar to

4385: 4320: 4023: 3999: 3869: 3438: 3429: 3253: 3094: 2928: 2708: 2663: 1981: 1682: 1578: 1503: 1481: 1297: 1164: 858: 815: 663: 646: 594: 532: 138: 8594:

We could revoke its implementation as a level of protection, but not the restriction itself.

8566: 7919: 4791:

Given the balance between persistent vandalism and defense against this, a reasonable tool.

196:

in topic areas authorized by the Arbitration Committee or as a result of community consensus

10252: 10197: 9956: 9752: 9722: 9685: 8618: 8426: 8396: 7345: 6640:

Absolutely right, It's easy to ask this kind of sanctions if you know you wont be effected.

6380: 6284: 6283:

This level of protection should be useable by the community wherever reasonably necessary.

6229: 6207: 6192: 6102: 5947: 5881: 5859: 5788: 5753: 5200: 5168: 5153: 5110: 4901: 4869: 4602: 4281: 4103: 3949: 3577: 3412: 3304: 3193: 3177: 2941:

As this is a preferable option over full protection in many cases. The admins that work at

2908: 2885: 2525: 2364: 2159: 1901: 1515:

Such powers should be used only when absolutely necessary, and determined by Arbitration. -

1279: 1139: 934:

place. Increasing the use of protections discourages the participation of the casual user.

702: 288: 158: 3093:

need when semi won't do. I've been longing for this option for years and now is the time!

8: 10092: 10061: 9830:

And if option C goes through, I don't plan on ever using full protection for vandalism.

9806: 9477: 9438: 9407: 9393: 9202: 9099: 9056: 8948: 8911: 8793: 8666: 8570: 8351: 8083: 8021: 7945: 7651: 7619: 7516: 7397: 6995: 6968:

on the article's talk page to request edits, but many 30/500 article talk pages (such as

6932: 6787: 6753: 6713: 6396: 6332: 6254: 6153: 6115: 6082: 5711: 5688: 5623: 5543: 5455: 5403: 5305: 4957: 4920: 4825: 4779: 4649: 4214: 4149: 3979: 3962: 3691: 3222: 3201: 3048: 3018: 2831: 2810: 2539: 2381: 2343: 2306: 2139: 2126: 1721: 1700: 1603: 1557: 1537: 1201: 879: 874:

I'm not a fan of this protection level except when invoked by ArbCom after deliberation.

835:

I tend towards the view that these hyper-contentious articles ought to be protected from

412: 362:

section for my full reasoning. I can live with Option B, but I strongly oppose Option C.

302: 9328:

Why would you consider that as a case study when we have the patient zero, the infamous

9295:

Nikita attempted to make a sleeper account to get around extended confirmed protection (

10104: 9817: 9488: 9460: 9421: 9361: 9187: 9141: 8959: 8932: 8894: 8698: 8507:

Was just reverting this! Looks like a "bug", will follow up on VPT with phab ticket. —

8490: 8280: 8186: 8180: 8150: 8068: 8057: 8007: 7902: 7875: 7843: 7796: 7751: 7600: 7470: 7439: 7316: 7259: 7232: 7140: 7026: 6848: 6748:, this may be something we missed when framing the RFC at the Village Pump discussion. 6743: 6727: 6666: 6595: 6344: 6298: 5907: 5669: 5610: 5576: 5507: 5380: 5048: 5000: 4978: 4796: 4750: 4582: 4413: 4039: 4015: 3805: 3469:

provided at least five admins all agree at AN, and there is also an actively patrolled

3341: 3319: 3137: 3075: 2866: 2845: 2747: 2427: 2068: 1973: 1913: 1823: 1665: 1314: 1227: 1050: 769: 756: 514: 435: 313: 279: 172: 150: 9736:

for these pages - which is where the "submit an edit request" will land if clicked. —

9339:

participating in it, and the loosely organized movement that emerged from the hashtag.

6408:

use of ECP, not get rid of the notifications. The point of the AN notifications is to

1737:- Semi and full are still the correct choice for "whenever necessary" is necessary. 10266: 10216: 9876: 9734:

Knowledge:Requests_for_page_protection#Current_requests_for_edits_to_a_protected_page

9633: 9357: 9239: 8840: 8811: 7506: 7365: 7287: 7174: 7076:

Knowledge:Requests_for_page_protection#Current_requests_for_edits_to_a_protected_page

6864: 6802: 6767: 6630: 6538: 6482: 6437: 6418: 6316: 6219: 6143: 6058:- I became less active in Knowledge because of sockpuppets, so I prefer this option. 5998: 5964: 5806: 5774: 5732: 5589: 5288: 5248: 5231: 5180: 5131: 5093: 4761:. This would be very useful on article prone to attracting POV-pushing sockpuppets. — 4685: 4512: 4469: 4438: 4333: 4304: 4243: 4204: 4191: 4182:. On the other hand, I do see a possible case for partially unbundling the right to 4052: 3914: 3894: 3753: 3661: 3627: 3595: 3539: 3396: 3155: 2964: 2724: 2690: 2626: 2572: 2405: 2305:. Let's give option B a try and see how well it goes before moving on to Option C. 2289: 2172: 2085: 2006: 1955: 1795: 1775: 1748: 1520: 1459: 1428: 1354: 1261: 1028: 970: 921: 605: 583: 554: 496: 367: 7266: 4225: 10235: 10163: 10075: 10050: 10036: 9850: 9831: 9668: 9172: 9134: 9119: 9023: 8757: 8562: 8035: 7958: 7887: 7856: 7819: 7774: 7716: 7700: 7633: 7565: 7537: 7523: 7484: 7448: 7420: 7119:

And additionally, there is a bot generated list of these that should be present at

6911: 6462: 6271: 6174: 6016: 5656: 5525: 5459: 5068: 5023: 4885: 4698: 4552: 4435:

Adding: I can't imagine notifications (at AN) enforced well. Should be bot-handled)

4381: 3996: 3936: 3863: 3843: 3828: 3612: 3506: 3485: 3434: 3248: 3121: 2923: 2657: 2613: 2595: 2501: 1940: 1891: 1868: 1678: 1644: 1621: 1574: 1499: 1009: 957: 939: 845: 805: 739: 660: 643: 589: 543: 527: 393: 222:

Allow use only for topics authorized by the Arbitration Committee (current policy).

184: 130: 96: 4170:

exists and it is most unlikely that unilateral use by admins will be abusive - we

10262: 10248: 10009: 9975: 9952: 9933: 9767: 9748: 9718: 9694: 9681: 9446: 9352: 8675: 8299: 8233: 7435: 7342: 7144: 7045: 6828: 6375: 6097: 6063: 5943: 5898: 5877: 5855: 5800: 5784: 5764: 5749: 5521: 5343: 5188: 5106: 4897: 4865: 4809: 4276: 4135: 4099: 4072:

is meant to prove, and that we assume to our admistrators every day in any case.

3940: 3932: 3787: 3572: 3300: 3286: 3174: 3035: 2903: 2880: 2793: 2418:

Also, if option C was implemented, then there will be huge amount of requests at

2264:

be misled into such an action. The potential for drama just seems too high to me.

2155: 1570: 1410: 1275: 1244: 1123: 1068: 699: 685: 478: 380: 354: 332: 245: 213: 92: 7089:

Note: talk protection should be extremely rare - it is currently only in use on

7044:—we certainly don't need an RfC for the creation of every little obvious thing. 5570:

These may be less commmon, but that is why posting to AN for review makes sense.

10261:

If this userspace suggestion becomes policy, good opportunity to mention it at

10088: 10057: 9802: 9473: 9403: 9389: 9347: 9198: 9095: 9079: 9071: 8944: 8907: 8789: 8717: 8471:

Knowledge:Village_pump_(technical)#My_bot_can.27t_edit_extended_protected_pages

8160: 8079: 8017: 7941: 7931: 7615: 7462: 7393: 7041: 6991: 6928: 6783: 6749: 6709: 6615: 6392: 6328: 6250: 6131: 6077: 5707: 5437: 5399: 5364: 5323: 5301: 5271: 4969: 4915: 4775: 4725: 4645: 4209: 4167: 4107: 3728: 3709: 3687: 3456: 3214: 3197: 3014: 2947: 2942: 2827: 2823: 2806: 2776: 2535: 2448: 2377: 2302: 2122: 2109: 1713: 1696: 1599: 1573:(and I don't invoke it that often). I agree with what SteveStrummer said, too. 1553: 1533: 1392: 1213: 1198: 1086: 875: 732: 430: 408: 298: 9197:

Hence the requirement that use of ECP needs community review upon activation.

7765:

to state the duration chosen should be no different than that of semi/PC/full

6657:-Oh you are an expert on the subject you say? You have no interest in editing 5502:

Makes sense and is a logical addition in my view. Safeguards appear adequate.

311:

The old system is "nothing-full", semi-protection is a more recent invention.

10141: 10123: 9916: 9893: 9737: 9713: 9703: 9607: 9566: 9549: 9523: 9507: 9312: 9160: 9091: 9083: 9075: 8578: 8508: 8474: 8375: 8331: 8262: 8201: 8164: 8127: 8104: 8049: 7999: 7792: 7747: 7578: 7555: 7543: 7480:

for highly visible templates, which are intrinsically protected indefinitely

7271: 7270:(for example) would fall into Option B (minus the post/review), and so would 7247: 7243: 7228: 7136: 7124: 7109: 7094: 7079: 6981: 6688: 6573: 6455: 5606: 5572: 5503: 5482: 5414: 5184: 5044: 4996: 4973: 4945: 4821: 4792: 4745: 4575: 4490: 4473: 4175: 4069: 4035: 4011: 3801: 3800:

eminently sensible suggestion...and I was considering proposing this myself.

3337: 3274: 3236: 3114: 3090: 3070: 2760: 2743: 2514: 2461: 2419: 2225: 2046: 2030: 2025: 1994: 1969: 1819: 1661: 1438: 1379: 1336: 1217: 1127: 1045: 752: 510: 458: 450: 360:

Knowledge:Request_for_comment/Extended_confirmed_protection_policy#Discussion

8978:

https://en.wikipedia.org/search/?title=User:HistoryWrite&oldid=702887766

8875:

I mentioned this before, but I think it should be discussed more thoroughly.

8646:

too many rights for editing articles as it is. Don't add more complexity. --

8159:

The place it's written into the protection policy is under the guidance for

2625:

another useful tool for admins that will be useful in vandalism fighting. -

10212: 10115: 9867: 9647: 9629: 9087: 8807: 8145: 7986:. Is that the intended meaning, or does the proponent mean for it to be a 7502: 7466: 6860: 6798: 6763: 6626: 6433: 6414: 6312: 6215: 6139: 5994: 5960: 5805:

Indented your second !vote here. You seem to be vote #42 as of this post —

5770: 5702:

Give an admin a shotgun and suddenly everything needs shooting. I support

5474: 5284: 5243: 5219: 5089: 4681: 4665: 4294: 4187: 3908: 3890: 3652: 3591: 3376: 2960: 2685: 2431: 2401: 2285: 2269: 2189: 2021: 2002: 1998: 1951: 1786: 1771: 1764: 1739: 1584: 1516: 1455: 1424: 1350: 1293: 1257: 1180:. It is becoming harder and harder for newbies to contribute to Knowledge, 986: 917: 492: 363: 241: 236:

where semi-protection has proven to be ineffective (similar to what ArbCom

118: 3013:. This is a good protection scheme when full protection is unwarranted. -- 2121:- I agree that along with this, there should be a set expiration as well. 10229: 9846: 9662: 7694: 7004:

What Blackmane said. We should create a category and template similar to

6662: 6651: 6625:

TL;DR: ECP will be used excessively and drive away good-faith newcomers.

6267: 6037: 6011: 5653: 5062: 5035: 5017: 4882: 4548: 3824: 3686:- Good alternative to full protection when semi-protection isn't enough. 3608: 3502: 3481: 2609: 2591: 2497: 2480: 2465: 2246: 1931: 1887: 1863: 1640: 1617: 1495:

https://en.m.wikipedia.org/Wikipedia:User_access_levels#Extendedconfirmed

953: 935: 841: 387: 179:

was created for this purpose. The protection level was created following

9233:

Knowledge talk:Requests for comment/Extended confirmed protection policy

8834:

Knowledge talk:Requests for comment/Extended confirmed protection policy

7614:. The RFC discussion is already getting bogged down in policy minutiae. 5976:

This will allow the most amount of problems to be solved and combatted.

981:. No, I am highly opposed to the imposition of 30/500 by a single admin 9763: 9625: 9570: 9528: 9503: 9442: 8597: 8531:

If anybody opposes extended confirmed protection policy, comment here.

8229: 7806: 7787: 6821: 6658: 6647: 6059: 5338: 4315:- a good balance of extra power with extra check by obligatory review. 4121: 3771: 2789: 2643: 1406: 1240: 1135: 1131: 1130:. Looking at existing usage of this feature, we find it being used on 1098: 1064: 894: 681: 471: 4148:

as another option to be used with care in helping to stop disruption.

3411:

This will be a vital tool in trying to help with vandalism and socks.

248:

30/500 applications). Notification is to be posted in a subsection of

9498:

This is a Twinkle mistake, most likely. Currently, Twinkle is set to

9375:

patient zero. They were the first one against which ECP was deployed

8258: 8254: 7926: 6974:

Knowledge:Administrators' noticeboard/30/500-protection edit requests

6680: 5431: 5358: 5319: 5267: 3721: 3704: 3451: 2772: 2102: 1003: 995: 8888:

People are already discussing the ineffectiveness of 500/30 at the

4293:

I see no reason not to make it a additional tool for admins to use.

10119: 10087:

Are you envisioning something like the WP:CENT notifications list?

9798: 8589: 8574: 8326: 5478: 3364: 2996: 2220: 1375: 1332: 1256:

I believe that this is the best plan in order to combat vandalism.

454: 9816:

But if other admins use it, what you decide to do isn't relevant.

8976:

This is a good example of the flaw inherent to the 30/500 system:

228:

Allow use only for topics authorized by the Arbitration Committee

9371:

In the context of how ECP is being looked at in this RFC, Nikita

6976:

or similar might work, but there would be a lot or disruption on

6173:

Support as a last resort in situations where all else has failed

1835:

The other options would place a substantial burden on newcomers.

8788:

decided what you are...they are now only discussing your price.

8098:

Why not rewrite this as "given that the disruption is caused by

5566:-an edit war between one new-but-autoconfirmed editor and one IP 1374:

of the encyclopedia anyone can edit, come on, let's be serious.

7157:

quiet, and typically there are ~1–2 requests per week, whereas

5473:—that is, policies created to enforce other policies, like the 9276:

was closed with consensus to deploy 30/500 in response to the

8980:

It was posted at the Arbitration/Requests/Enforcement page by

7356:

would need to change, and ECP protection would need to be its

5622:

more measures to deal with disruption beyond semi-protection.

4429:, with acknowledgement for Option A. I think it's not easy to 4412:

This would certainly improve on the present state of affairs.

167: 7352:

To implement your not-every-admin suggestion, the permission

7106:

Category:Knowledge extended-confirmed-protected edit requests

6643:-Hello new user, welcome to the encyclopedia anyone can edit! 3530:

Category:Knowledge extended-confirmed-protected edit requests

2154:

applying it to a page, I could support a revised option C. --

840:

obviously an invitation to article ownership on a new level.

8981: 5706:

30/500 level, but start with the most limited applications.

4956:, Option C is fine for me but I generally support Option D. 802:. I don't think this kind of environment is a friendly one. 9332:

article. Let's just look at the first sentence of the lede:

9163:

or during organized attacks (which do occur). This is why

7605:

x2. Personally, I'm not focused on the duration of the ECP

6684: 4497: 9297: 9283:

In response to the initial use of this protection level,

9221:

Appeal to closer: delayed implementation and notification

5942:

The better of the three options, admins please use wisely

5562:. This could be very useful in dealing with, for example 5467:

The real brain exercise occurs when one of the community

5379:. We need another option between semi and full. Regards, 4397:

No reason not to. It will greatly help the encyclopedia.

2723:

Net positive - useful for admins to combat disruption. -

72:

or "pile-on" votes—to which I paid particular attention.

9388:

determined, but no less disruptive/destructive editor.

5242:

More granularity is better. Just recently, for example,

4723:

extended confirmed in less controversial areas first.

2945:

are competent enough to use this new option with care. —

2204: 1191:

Knowledge is supposed to be about discussion, not voting

1138:. Tight controls seem necessary to mitigate this risk. 9969:

protection level. But ArbCom basically created the new

8485:

The permission is already bundled to the bot group per

7872:

I've missed this reply, apologies for the late response

6391:

the noticeboards. WP:Requests for ECP board anyone...?

4503: 2197: 1405:

seems unneeded and is yet another lock on our content.

5564:-an edit war between two new-but-autoconfirmed editors 5105:

You could make it 90/1000, and I'd be fine with it. -

2190: 9268:

Does extended confirmed protection work? A case study

7078:. Is there some part of this that is not working? — 4741:

Knowledge:Sockpuppet investigations/Никита-Родин-2002

4739:

Unfortunately autoconfirmed can be easily gamed. See

4571:

Knowledge:Requests for permissions/Extended confirmed

548:

By your wording, it sounds like you probably meant a

204:

Criteria for community use have not been established.

5839:

Could you please explain what you mean by maturity?

3192:. In fact, I think this protection level would be a 2861:, though I still hope to see it used sparingly, and 751:- As per what was stated above including DHeyward.-- 80:. Other recurring themes worth picking out include: 43:

Subsequent comments should be made in a new section.

7741:

Time limit clarification based on Option C comments

5458:section of the consensus policy. However, what the 1155:Scaring off the newbies isn't a mantra, it's math. 7770:insufficient and full protection is inappropriate 7024:anyway, but that's outside the scope of this RFC. 5193:You could make it 90/1000, and I'd be fine with it 2253:, but they have less experience with those issues. 1368:You could make it 90/1000, and I'd be fine with it 8538:If this is necessary, then Knowledge has failed. 3840:Makes sense and is a logical addition in my view 3113:doing it even though the policy says not to, per 2342:unless A or B is tried and found unsatisfactory. 8885:for this exact attitude of assuming bad faith. 4968:with the caveat that I think accounts that were 4808:- incredibly useful tool, per all of the above. 7392:What is the problem with giving ECP to admins? 7286:to do the damage at that page. (confounding) — 6266:, all the other options are bureaucracy creep. 1182:for many reasons in addition to page protection 790:mistake. I know this because I spent literally 9965:I already knew that ArbCom did not create the 3172:because semiprotection is too easy to game. -- 449:have one that isn't so restrictive as 30/500: 8869:The Environment Created by Extended Confirmed 6883:can edit, but that's neither here nor there. 6155: 6117: 4151: 9002:I decided to start inflating my edit count 8982:https://en.wikipedia.org/User:Malik_Shabazz 8527:Oppose extended confirmed protection policy 7104:Additionally, these should be appearing in 6879:to what was built as the encyclopedia that 5214:Many articles, such as those involving the 4224:As vandals evolve, we should evolve too. -- 2422:, and it would also encourage users to add 8395:benefit from PC2 + 30/500 simultaneously. 7761:Sorry for being unclear. I've updated the 2424:this user has extendedconfirmed permission 9022: 8756: 7444:as this is in response to their concerns 7408:30/500 protection (or ECP) is absolutely 6782:Now that would be a right waste of time. 991:one article, or a specific group of edits 804: 6665:? You shameless SPA, get out of here!!! 6537:more active and worthy of monitoring. — 5216:2016 United States Presidential election 2251:(or arguably more, bunch of Wikiaholics) 1768:You have already voted, but for Option C 208:discussion at the village pump ideas lab 8571:beyond the remit of community consensus 8462:This is a tech bug, following up on VPT 3719:Makes sense in the present scenario. -- 2024:, any admin can already block socks at 272:proportional to the disruption observed 14: 9801:was for improving Coca-Cola's profit. 8751:Per my reasons when supporting Option 8670:time that editors read and apply this 6972:) are also 30/500 protected. Creating 2464:—would introduce a needed check here. 1189:Why is my point not numbered? Because 8419:Mass killings under Communist regimes 8103:affected by that protection level. ~ 7225:See the list of EC protected articles 3247:- Good alternate to full protection. 2759:Good alternative to full protection. 2299:Support Option B, but oppose Option C 1770:. Which vote would you like to keep? 6458:would be happy to do this for us :) 5651:consensus as proposed by Option C.-- 3450:as long as it is applied carefully. 37:The following discussion is closed. 7280:Special:CentralAuth/JeremyCubsfan98 6446:I was going to say the same thing. 3095:<<< SOME GADGET GEEK : --> 30: 9762:tend to strongly disagree with. - 9643:Your ping will work, as does this: 8411:List of social networking websites 7149:I've been actively monitoring the 6527:Special:Contributions/South Morang 6249:. For so many reasons given above 2805:Combat those vandalism is better. 2284:- based on review of the options. 31: 10308: 9278:sockpuppetry of Никита-Родин-2002 8984:. The full conversation is here: 8565:for certain topic areas (notably 5728:The editor who uses the pseudonym 5339: 5249: 5187:. Extending it even further like 2241:making 30/500 admin action would 121:be updated with the wording from 57:there is a consensus for option C 10294:The discussion above is closed. 10019:WikiProject Reforming Knowledge. 9985:WikiProject Reforming Knowledge. 9943:WikiProject Reforming Knowledge. 9226: 8827: 8685:WikiProject Reforming Knowledge. 8309:WikiProject Reforming Knowledge. 8243:WikiProject Reforming Knowledge. 7055:WikiProject Reforming Knowledge. 5344: 2513:A is not enough, C is too much. 342:WikiProject Reforming Knowledge. 210:produced the following options. 202:). However, it also states that 10134:User:MusikBot/ECPMonitor/Report 10030:User:MusikBot/ECPMonitor/Report 9034: 9030: 9025: 8768: 8764: 8759: 7994:semi-protection has been tried 7711:While I don't fully agree with 3650:Support - Pile-on, per above. 1857:restrictive as full protection 816: 812: 807: 177:"extended confirmed" user right 8730: 7974:Option C: Finding or proviso? 7925:applied indefinitely? Thanks, 6515:Special:Contributions/Rack3515 4178:in the cmments section below: 18:Knowledge:Requests for comment 13: 1: 7274:I think. But apparently EC-P 6519:Special:Contributions/Rah2882 5225: 4509:Oh and congrats on the mop :) 2110: 2103: 1658:so long as it is not overused 173:Extended confirmed protection 9094:would also be enlightening. 8731:the reasons I already stated 7762: 3254: 3249: 1157:5–10 edit requests per month 7: 7414:shortest effective duration 6228:Striking my comment, oops! 5300:Useful protection level. -- 5220: 3194:good default for user pages 144:18:46, 12 August 2016 (UTC) 10: 10313: 10289:20:44, 9 August 2016 (UTC) 10257:09:55, 9 August 2016 (UTC) 10242:09:39, 9 August 2016 (UTC) 10221:03:57, 9 August 2016 (UTC) 10206:02:34, 9 August 2016 (UTC) 10171:16:16, 8 August 2016 (UTC) 10147:02:40, 7 August 2016 (UTC) 10128:21:04, 6 August 2016 (UTC) 10109:13:31, 3 August 2016 (UTC) 10097:05:47, 3 August 2016 (UTC) 10083:20:36, 1 August 2016 (UTC) 10066:07:00, 1 August 2016 (UTC) 9904:17:04, 5 August 2016 (UTC) 9887:15:58, 5 August 2016 (UTC) 9861:15:22, 5 August 2016 (UTC) 9655:Talk:Gamergate controversy 9360:were actually followed... 9224: 8825: 8627:04:19, 6 August 2016 (UTC) 8435:02:54, 9 August 2016 (UTC) 8405:02:44, 9 August 2016 (UTC) 8386:00:42, 2 August 2016 (UTC) 8365:00:27, 2 August 2016 (UTC) 8200:when I was on vacation. ~ 7731:22:14, 2 August 2016 (UTC) 6970:Talk:Gamergate controversy 6293:04:11, 6 August 2016 (UTC) 6276:19:52, 2 August 2016 (UTC) 6259:15:55, 2 August 2016 (UTC) 6238:14:37, 2 August 2016 (UTC) 6224:14:34, 2 August 2016 (UTC) 6201:12:56, 2 August 2016 (UTC) 6183:05:57, 2 August 2016 (UTC) 6163:05:52, 2 August 2016 (UTC) 6148:04:32, 2 August 2016 (UTC) 6125:02:43, 2 August 2016 (UTC) 6105:23:24, 1 August 2016 (UTC) 2822:From occasional visits at 2520:23:30, 2 August 2016 (UTC) 2506:14:26, 1 August 2016 (UTC) 1896:21:12, 4 August 2016 (UTC) 1879:15:05, 2 August 2016 (UTC) 1845:20:16, 1 August 2016 (UTC) 1806:16:04, 2 August 2016 (UTC) 1780:14:49, 2 August 2016 (UTC) 1306:15:19, 14 July 2016‎ (UTC) 268:duration of the protection 148: 10044:21:07, 30 July 2016 (UTC) 10023:20:26, 30 July 2016 (UTC) 9989:21:36, 25 July 2016 (UTC) 9961:21:30, 25 July 2016 (UTC) 9947:21:24, 25 July 2016 (UTC) 9927:19:27, 22 July 2016 (UTC) 9840:17:14, 22 July 2016 (UTC) 9826:10:25, 22 July 2016 (UTC) 9811:10:05, 22 July 2016 (UTC) 9772:01:39, 22 July 2016 (UTC) 9757:11:54, 21 July 2016 (UTC) 9743:11:48, 21 July 2016 (UTC) 9727:11:36, 21 July 2016 (UTC) 9709:11:24, 21 July 2016 (UTC) 9690:09:56, 21 July 2016 (UTC) 9675:20:56, 20 July 2016 (UTC) 9638:19:09, 20 July 2016 (UTC) 9618:06:26, 20 July 2016 (UTC) 9586:00:15, 21 July 2016 (UTC) 9560:13:51, 20 July 2016 (UTC) 9537:07:59, 20 July 2016 (UTC) 9518:06:26, 20 July 2016 (UTC) 9494:04:08, 20 July 2016 (UTC) 9482:23:42, 19 July 2016 (UTC) 9466:09:44, 19 July 2016 (UTC) 9451:08:04, 19 July 2016 (UTC) 9427:07:05, 19 July 2016 (UTC) 9412:06:19, 19 July 2016 (UTC) 9398:05:56, 19 July 2016 (UTC) 9367:04:54, 19 July 2016 (UTC) 9323:18:32, 17 July 2016 (UTC) 9262:19:48, 21 July 2016 (UTC) 9207:04:52, 25 July 2016 (UTC) 9193:22:44, 23 July 2016 (UTC) 9181:14:54, 23 July 2016 (UTC) 9147:05:17, 23 July 2016 (UTC) 9128:17:10, 22 July 2016 (UTC) 9104:00:04, 20 July 2016 (UTC) 9065:23:55, 19 July 2016 (UTC) 9046:06:27, 14 July 2016 (UTC) 8997:06:14, 14 July 2016 (UTC) 8965:17:18, 14 July 2016 (UTC) 8953:15:20, 14 July 2016 (UTC) 8938:03:27, 14 July 2016 (UTC) 8916:02:43, 14 July 2016 (UTC) 8900:01:59, 14 July 2016 (UTC) 8863:19:50, 21 July 2016 (UTC) 8816:15:50, 27 July 2016 (UTC) 8798:01:43, 23 July 2016 (UTC) 8780:08:16, 11 July 2016 (UTC) 8743:03:08, 11 July 2016 (UTC) 8722:04:34, 10 July 2016 (UTC) 8704:03:42, 10 July 2016 (UTC) 8514:21:34, 10 July 2016 (UTC) 8503:21:33, 10 July 2016 (UTC) 8480:21:29, 10 July 2016 (UTC) 8336:22:18, 23 July 2016 (UTC) 7908:02:40, 28 July 2016 (UTC) 7896:14:16, 26 July 2016 (UTC) 7881:04:07, 25 July 2016 (UTC) 7865:17:04, 22 July 2016 (UTC) 7707:16:34, 17 July 2016 (UTC) 7685:00:47, 13 July 2016 (UTC) 7360:permission then, called " 6893:02:22, 12 July 2016 (UTC) 6506:07:10, 14 July 2016 (UTC) 6089:21:31, 31 July 2016 (UTC) 6068:07:28, 31 July 2016 (UTC) 6051:20:09, 30 July 2016 (UTC) 6028:15:51, 30 July 2016 (UTC) 6003:20:20, 29 July 2016 (UTC) 5986:14:22, 29 July 2016 (UTC) 5969:14:09, 29 July 2016 (UTC) 5952:23:34, 28 July 2016 (UTC) 5935:00:36, 28 July 2016 (UTC) 5916:21:18, 31 July 2016 (UTC) 5902:20:15, 27 July 2016 (UTC) 5890:08:29, 27 July 2016 (UTC) 5864:09:16, 28 July 2016 (UTC) 5849:09:06, 28 July 2016 (UTC) 5829:23:52, 27 July 2016 (UTC) 5793:22:31, 27 July 2016 (UTC) 5779:14:36, 27 July 2016 (UTC) 5758:07:21, 27 July 2016 (UTC) 5741:13:48, 26 July 2016 (UTC) 5716:23:42, 25 July 2016 (UTC) 5695:18:30, 25 July 2016 (UTC) 5678:18:12, 25 July 2016 (UTC) 5661:03:35, 25 July 2016 (UTC) 5643:08:02, 24 July 2016 (UTC) 5615:00:07, 24 July 2016 (UTC) 5598:11:11, 23 July 2016 (UTC) 5581:08:46, 23 July 2016 (UTC) 5555:05:38, 23 July 2016 (UTC) 5534:16:58, 22 July 2016 (UTC) 5512:13:56, 22 July 2016 (UTC) 5487:17:29, 28 July 2016 (UTC) 5445:23:30, 23 July 2016 (UTC) 5425:03:17, 22 July 2016 (UTC) 5408:00:06, 22 July 2016 (UTC) 5391:15:39, 21 July 2016 (UTC) 5372:15:25, 21 July 2016 (UTC) 5350:13:56, 21 July 2016 (UTC) 5328:22:22, 20 July 2016 (UTC) 5310:19:54, 20 July 2016 (UTC) 5293:19:28, 20 July 2016 (UTC) 5276:17:36, 19 July 2016 (UTC) 5258:19:07, 18 July 2016 (UTC) 5247:access to the article. – 5235:17:46, 17 July 2016 (UTC) 5205:16:59, 17 July 2016 (UTC) 5173:14:00, 20 July 2016 (UTC) 5158:14:14, 17 July 2016 (UTC) 5140:04:16, 17 July 2016 (UTC) 5115:00:10, 17 July 2016 (UTC) 5098:20:41, 16 July 2016 (UTC) 5075:16:11, 17 July 2016 (UTC) 5053:16:01, 17 July 2016 (UTC) 5030:12:08, 16 July 2016 (UTC) 5005:14:55, 14 July 2016 (UTC) 4987:12:52, 14 July 2016 (UTC) 4961:11:21, 14 July 2016 (UTC) 4949:09:17, 14 July 2016 (UTC) 4933:05:23, 14 July 2016 (UTC) 4906:23:22, 13 July 2016 (UTC) 4889:05:47, 13 July 2016 (UTC) 4874:05:31, 13 July 2016 (UTC) 4857:15:53, 12 July 2016 (UTC) 4836:12:58, 12 July 2016 (UTC) 4813:05:27, 12 July 2016 (UTC) 4801:05:23, 12 July 2016 (UTC) 4784:19:15, 11 July 2016 (UTC) 4766:15:48, 11 July 2016 (UTC) 4754:12:35, 11 July 2016 (UTC) 4732:11:24, 11 July 2016 (UTC) 4715:22:38, 10 July 2016 (UTC) 4690:21:58, 10 July 2016 (UTC) 4673:18:41, 10 July 2016 (UTC) 4654:06:30, 10 July 2016 (UTC) 4636:02:56, 10 July 2016 (UTC) 3562:05:03, 10 July 2016 (UTC) 3511:12:10, 14 July 2016 (UTC) 2484:03:36, 27 July 2016 (UTC) 2472:20:08, 26 July 2016 (UTC) 2452:09:51, 26 July 2016 (UTC) 2440:16:25, 25 July 2016 (UTC) 2410:18:44, 24 July 2016 (UTC) 2386:00:04, 22 July 2016 (UTC) 2369:14:00, 20 July 2016 (UTC) 2352:23:32, 19 July 2016 (UTC) 2330:00:11, 16 July 2016 (UTC) 2322:StillWaitingForConnection 2315:14:36, 10 July 2016 (UTC) 1828:13:32, 31 July 2016 (UTC) 1759:00:07, 31 July 2016 (UTC) 1730:13:44, 28 July 2016 (UTC) 1705:14:35, 27 July 2016 (UTC) 1687:06:11, 27 July 2016 (UTC) 1670:22:55, 26 July 2016 (UTC) 1649:18:58, 26 July 2016 (UTC) 1632:17:23, 26 July 2016 (UTC) 1608:23:37, 25 July 2016 (UTC) 1590:01:43, 25 July 2016 (UTC) 1562:16:04, 24 July 2016 (UTC) 1542:00:02, 22 July 2016 (UTC) 1525:15:42, 20 July 2016 (UTC) 1508:15:51, 19 July 2016 (UTC) 1486:03:35, 19 July 2016 (UTC) 1464:05:45, 19 July 2016 (UTC) 1449:20:05, 18 July 2016 (UTC) 1433:19:22, 18 July 2016 (UTC) 1415:00:20, 18 July 2016 (UTC) 1398:20:30, 17 July 2016 (UTC) 1384:02:44, 17 July 2016 (UTC) 1359:02:01, 17 July 2016 (UTC) 1341:02:12, 16 July 2016 (UTC) 1323:06:02, 15 July 2016 (UTC) 1284:15:06, 14 July 2016 (UTC) 1266:06:20, 14 July 2016 (UTC) 1249:08:41, 13 July 2016 (UTC) 1232:17:42, 12 July 2016 (UTC) 1205:00:16, 11 July 2016 (UTC) 1173:08:34, 11 July 2016 (UTC) 1148:09:51, 10 July 2016 (UTC) 181:this community discussion 140:Penny for your thoughts? 10296:Please do not modify it. 9285:Talk:The Who discography 8689:22:16, 9 July 2016 (UTC) 8658:21:13, 9 July 2016 (UTC) 8612:22:35, 9 July 2016 (UTC) 8583:15:12, 9 July 2016 (UTC) 8548:09:51, 9 July 2016 (UTC) 8313:22:03, 9 July 2016 (UTC) 8285:21:48, 9 July 2016 (UTC) 8273:20:40, 9 July 2016 (UTC) 8247:20:16, 9 July 2016 (UTC) 8212:19:13, 8 July 2016 (UTC) 8191:18:59, 8 July 2016 (UTC) 8175:18:45, 8 July 2016 (UTC) 8155:10:25, 8 July 2016 (UTC) 8138:03:20, 8 July 2016 (UTC) 8115:03:16, 8 July 2016 (UTC) 8088:02:59, 8 July 2016 (UTC) 8073:21:05, 7 July 2016 (UTC) 8061:20:51, 7 July 2016 (UTC) 8043:20:15, 7 July 2016 (UTC) 8026:16:53, 7 July 2016 (UTC) 8011:16:21, 7 July 2016 (UTC) 7966:20:45, 6 July 2016 (UTC) 7950:15:55, 6 July 2016 (UTC) 7934:15:46, 6 July 2016 (UTC) 7849:22:47, 7 July 2016 (UTC) 7827:21:48, 6 July 2016 (UTC) 7801:08:24, 6 July 2016 (UTC) 7782:00:46, 6 July 2016 (UTC) 7756:00:24, 6 July 2016 (UTC) 7660:12:55, 6 July 2016 (UTC) 7641:00:01, 6 July 2016 (UTC) 7624:23:50, 5 July 2016 (UTC) 7584:02:09, 6 July 2016 (UTC) 7573:02:05, 6 July 2016 (UTC) 7549:01:40, 6 July 2016 (UTC) 7531:23:48, 5 July 2016 (UTC) 7511:23:01, 5 July 2016 (UTC) 7492:21:38, 5 July 2016 (UTC) 7456:21:19, 5 July 2016 (UTC) 7428:21:17, 5 July 2016 (UTC) 7402:20:35, 5 July 2016 (UTC) 7388:17:06, 5 July 2016 (UTC) 7348:16:30, 5 July 2016 (UTC) 7322:04:57, 5 July 2016 (UTC) 7310:04:42, 5 July 2016 (UTC) 7272:example page you mention 7253:04:21, 5 July 2016 (UTC) 7238:04:13, 5 July 2016 (UTC) 7200:04:13, 5 July 2016 (UTC) 7197:04:00, 5 July 2016 (UTC) 7161:sees about 6–8 per day. 7130:03:45, 5 July 2016 (UTC) 7121:User:AnomieBOT/EPERTable 7115:03:42, 5 July 2016 (UTC) 7100:03:47, 5 July 2016 (UTC) 7085:03:39, 5 July 2016 (UTC) 7059:03:29, 5 July 2016 (UTC) 7031:02:11, 5 July 2016 (UTC) 7000:01:29, 5 July 2016 (UTC) 6985:01:18, 5 July 2016 (UTC) 6937:15:15, 5 July 2016 (UTC) 6921:09:33, 5 July 2016 (UTC) 6869:16:39, 5 July 2016 (UTC) 6854:02:33, 5 July 2016 (UTC) 6833:01:13, 5 July 2016 (UTC) 6807:03:17, 8 July 2016 (UTC) 6792:02:46, 5 July 2016 (UTC) 6772:01:47, 5 July 2016 (UTC) 6758:01:34, 5 July 2016 (UTC) 6733:00:15, 5 July 2016 (UTC) 6718:22:59, 4 July 2016 (UTC) 6694:22:18, 4 July 2016 (UTC) 6672:21:49, 4 July 2016 (UTC) 6635:18:52, 4 July 2016 (UTC) 6600:18:23, 4 July 2016 (UTC) 6584:16:30, 4 July 2016 (UTC) 6561:16:15, 4 July 2016 (UTC) 6535:User:AnomieBOT/EPERTable 6470:18:35, 4 July 2016 (UTC) 6442:16:39, 4 July 2016 (UTC) 6423:16:30, 4 July 2016 (UTC) 6401:14:51, 4 July 2016 (UTC) 6386:14:39, 4 July 2016 (UTC) 6370:13:44, 4 July 2016 (UTC) 6353:13:40, 4 July 2016 (UTC) 6337:13:12, 4 July 2016 (UTC) 6321:12:52, 4 July 2016 (UTC) 5088:The best of all worlds. 4619:20:29, 9 July 2016 (UTC) 4607:13:28, 9 July 2016 (UTC) 4586:07:44, 9 July 2016 (UTC) 4557:05:49, 9 July 2016 (UTC) 4535:07:21, 9 July 2016 (UTC) 4484:04:54, 9 July 2016 (UTC) 4464:03:08, 9 July 2016 (UTC) 4461:03:06, 9 July 2016 (UTC) 4422:22:16, 8 July 2016 (UTC) 4405:20:56, 8 July 2016 (UTC) 4390:19:41, 8 July 2016 (UTC) 4373:19:18, 8 July 2016 (UTC) 4356:18:40, 8 July 2016 (UTC) 4325:17:12, 8 July 2016 (UTC) 4308:11:58, 8 July 2016 (UTC) 4286:10:35, 8 July 2016 (UTC) 4267:Support and additionally 4261:09:09, 8 July 2016 (UTC) 4234:05:38, 8 July 2016 (UTC) 4217:04:12, 8 July 2016 (UTC) 4196:00:21, 8 July 2016 (UTC) 4159:22:00, 7 July 2016 (UTC) 4141:21:07, 7 July 2016 (UTC) 4113:16:06, 7 July 2016 (UTC) 4087:15:38, 7 July 2016 (UTC) 4061:02:16, 7 July 2016 (UTC) 4044:01:52, 7 July 2016 (UTC) 4027:00:29, 7 July 2016 (UTC) 4003:16:10, 6 July 2016 (UTC) 3988:15:01, 6 July 2016 (UTC) 3971:14:14, 6 July 2016 (UTC) 3954:14:09, 6 July 2016 (UTC) 3924:12:16, 6 July 2016 (UTC) 3899:09:43, 6 July 2016 (UTC) 3882:09:15, 6 July 2016 (UTC) 3848:07:39, 6 July 2016 (UTC) 3833:06:54, 6 July 2016 (UTC) 3816:03:50, 6 July 2016 (UTC) 3793:23:23, 5 July 2016 (UTC) 3763:21:59, 5 July 2016 (UTC) 3745:18:40, 5 July 2016 (UTC) 3712:18:29, 5 July 2016 (UTC) 3696:18:00, 5 July 2016 (UTC) 3672:17:56, 5 July 2016 (UTC) 3641:17:33, 5 July 2016 (UTC) 3617:17:15, 5 July 2016 (UTC) 3600:16:45, 5 July 2016 (UTC) 3582:15:39, 5 July 2016 (UTC) 3534:User:AnomieBOT/EPERTable 3490:15:22, 5 July 2016 (UTC) 3462:13:17, 5 July 2016 (UTC) 3443:12:45, 5 July 2016 (UTC) 3421:12:40, 5 July 2016 (UTC) 3404:12:21, 5 July 2016 (UTC) 3368:08:03, 5 July 2016 (UTC) 3347:07:46, 5 July 2016 (UTC) 3328:04:41, 5 July 2016 (UTC) 3309:02:29, 5 July 2016 (UTC) 3292:02:17, 5 July 2016 (UTC) 3278:00:50, 5 July 2016 (UTC) 3261:00:20, 5 July 2016 (UTC) 3240:23:22, 4 July 2016 (UTC) 3228:22:45, 4 July 2016 (UTC) 3206:22:39, 4 July 2016 (UTC) 3185:22:37, 4 July 2016 (UTC) 3165:20:35, 4 July 2016 (UTC) 3146:20:09, 4 July 2016 (UTC) 3129:18:31, 4 July 2016 (UTC) 3105:18:27, 4 July 2016 (UTC) 3082:18:22, 4 July 2016 (UTC) 3062:18:18, 4 July 2016 (UTC) 3039:18:02, 4 July 2016 (UTC) 3023:17:15, 4 July 2016 (UTC) 3006:16:29, 4 July 2016 (UTC) 2997: 2988:16:20, 4 July 2016 (UTC) 2969:14:55, 4 July 2016 (UTC) 2952:14:48, 4 July 2016 (UTC) 2934:14:39, 4 July 2016 (UTC) 2914:14:36, 4 July 2016 (UTC) 2894:14:32, 4 July 2016 (UTC) 2872:13:43, 4 July 2016 (UTC) 2854:13:38, 4 July 2016 (UTC) 2836:11:04, 4 July 2016 (UTC) 2815:09:38, 4 July 2016 (UTC) 2798:09:23, 4 July 2016 (UTC) 2781:09:09, 4 July 2016 (UTC) 2764:08:04, 4 July 2016 (UTC) 2752:07:48, 4 July 2016 (UTC) 2735:07:26, 4 July 2016 (UTC) 2716:07:25, 4 July 2016 (UTC) 2697:07:07, 4 July 2016 (UTC) 2671:06:21, 4 July 2016 (UTC) 2647:05:37, 4 July 2016 (UTC) 2635:04:36, 4 July 2016 (UTC) 2618:03:01, 4 July 2016 (UTC) 2600:02:05, 4 July 2016 (UTC) 2579:01:45, 4 July 2016 (UTC) 2564:01:43, 4 July 2016 (UTC) 2544:01:17, 4 July 2016 (UTC) 2294:21:11, 9 July 2016 (UTC) 2275:15:29, 9 July 2016 (UTC) 2230:04:32, 8 July 2016 (UTC) 2211:02:06, 9 July 2016 (UTC) 2181:19:08, 7 July 2016 (UTC) 2164:19:25, 6 July 2016 (UTC) 2143:03:36, 6 July 2016 (UTC) 2131:20:43, 5 July 2016 (UTC) 2114:16:42, 5 July 2016 (UTC) 2094:11:55, 5 July 2016 (UTC) 2077:19:11, 4 July 2016 (UTC) 2057:13:27, 6 July 2016 (UTC) 2041:14:57, 4 July 2016 (UTC) 2011:14:52, 4 July 2016 (UTC) 1985:09:05, 4 July 2016 (UTC) 1960:08:51, 4 July 2016 (UTC) 1946:04:39, 4 July 2016 (UTC) 1923:03:50, 4 July 2016 (UTC) 1161:70–80 EC-protected pages 1113:22:24, 9 July 2016 (UTC) 1091:09:23, 9 July 2016 (UTC) 1073:04:35, 9 July 2016 (UTC) 1056:07:19, 8 July 2016 (UTC) 1044:per Masem and DHeyward. 1037:02:00, 8 July 2016 (UTC) 1020:16:20, 7 July 2016 (UTC) 974:14:56, 7 July 2016 (UTC) 962:07:07, 7 July 2016 (UTC) 944:20:51, 6 July 2016 (UTC) 926:19:22, 6 July 2016 (UTC) 909:18:33, 6 July 2016 (UTC) 884:14:14, 6 July 2016 (UTC) 867:13:15, 6 July 2016 (UTC) 850:11:11, 6 July 2016 (UTC) 828:08:32, 6 July 2016 (UTC) 778:05:17, 6 July 2016 (UTC) 761:21:08, 5 July 2016 (UTC) 744:19:56, 5 July 2016 (UTC) 722:18:27, 5 July 2016 (UTC) 705:16:13, 5 July 2016 (UTC) 690:12:41, 5 July 2016 (UTC) 670:07:44, 6 July 2016 (UTC) 653:09:23, 5 July 2016 (UTC) 628:16:27, 5 July 2016 (UTC) 599:16:22, 5 July 2016 (UTC) 577:15:45, 5 July 2016 (UTC) 537:06:03, 5 July 2016 (UTC) 519:05:30, 5 July 2016 (UTC) 501:22:10, 8 July 2016 (UTC) 483:01:15, 5 July 2016 (UTC) 463:21:36, 4 July 2016 (UTC) 441:21:26, 4 July 2016 (UTC) 417:20:55, 4 July 2016 (UTC) 400:20:32, 4 July 2016 (UTC) 372:19:15, 4 July 2016 (UTC) 346:15:16, 4 July 2016 (UTC) 322:13:42, 4 July 2016 (UTC) 307:08:11, 4 July 2016 (UTC) 284:00:31, 4 July 2016 (UTC) 40:Please do not modify it. 9377:per community consensus 8487:Special:ListGroupRights 8415:Syed Mohsin Nawab Rizvi 7278:didn't do its job. See 7153:since around May. It's 7069:edit extended-protected 5336:Wiki for promotion... - 4567:Template:Semi-protected 3523:edit extended-protected 2430:has pointed out above. 451:pending changes level 2 246:discretionary sanctions 242:arbitration enforcement 234:persistent sockpuppetry 55:Therefore, I find that 10157:Special:ProtectedPages 8179:I would boldly change 7499:Special:ProtectedPages 7362:extended-protect-pages 7339:Comment about Option C 6212:You have already voted 6136:You have already voted 5927:Gary "Roach" Sanderson 5768:You have already voted 429:editor could not stop 69: 9624:It was brought up by 9330:Gamergate controversy 8735:Mario Castelán Castro 8563:Arbitration Committee 8257:'s alternate account 7982:that semi-protection 7282:, who made 500 edits 7242:There have been some 7163:You can actually put 5783:Sorry, I lost count. 4774:trolling/vandalism.-- 4501:mentioned below that 4431:enforce/monitor/gauge 4278:Satellizer el Bridget 3636:Tell me all about it. 2978:Colonel Wilhelm Klink 714:Mario Castelán Castro 185:Arbitration Committee 117:I recommend that the 61: 10153:talk page discussion 10028:We could transclude 7996:in a particular case 6910:dispute cools down. 5586:Extra Strong Support 5470:enforcement policies 3496:Changing my vote to 2301:. I'm a big fan of 1784:This one :P thanx, 9699:currently six pages 9439:The Who discography 9055:write new content. 8989:BorkBorkGoesTheCode 8569:) and is therefore 8557:BorkBorkGoesTheCode 8540:BorkBorkGoesTheCode 7726:If not, let me know 7167:edit semi-protected 7009:edit semi-protected 6963:Edit semi-protected 6609:Impact on newcomers 5841:BorkBorkGoesTheCode 4495:Yeah, makes sense. 3474:edit request 30-500 2608:discussed there. -- 1837:AntiCompositeNumber 6679:At least it's not 5460:arbitration policy 1372:the exact opposite 358:survival. See the 10021: 9987: 9945: 9924: 9901: 9884: 9644: 9615: 9557: 9515: 9320: 9311:going forward. ~ 9274:discussion at ANI 9041: 8876: 8775: 8687: 8610: 8567:WP:ARBPIA3#500/30 8523: 8522: 8383: 8311: 8270: 8245: 8209: 8172: 8135: 8112: 8052:J. D. Crutchfield 8002:J. D. Crutchfield 7604: 7213: 7212: 7201: 7172: 7057: 6696: 6581: 6570:WP:NOTBUREAUCRACY 6351: 6350: 6309:Option C question 6086: 6025: 6023:So let it be done 6018: 5978:Emir of Knowledge 5730: 5475:protection policy 5422: 5326: 4984: 4510: 4481: 4399:ThePlatypusofDoom 4139: 3922: 3784: 3742: 3669: 3637: 3460: 3401: 3290: 3087:Strongly Support! 3004: 2870: 2852: 2851: 2676:Tentative support 2340:strongly oppose C 2252: 2054: 2038: 1944: 1803: 1756: 1446: 1111: 1002: 907: 823: 742: 381:instruction creep 344: 320: 319: 119:Protection Policy 91:Further to this, 24:Knowledge:ECP2016 22:(Redirected from 10304: 10287: 10279: 10240: 10169: 10168: 10166: 10144: 10107: 10081: 10080: 10078: 10054: 10042: 10041: 10039: 10017: 9983: 9941: 9920: 9897: 9885: 9881: 9874: 9872: 9857: 9740: 9706: 9673: 9651: 9642: 9611: 9578:Opabinia regalis 9574: 9553: 9547: 9544:Opabinia regalis 9533: 9511: 9491: 9463: 9424: 9364: 9316: 9300: 9264: 9260: 9252: 9230: 9229: 9190: 9144: 9138: 9043: 9042: 9038: 9037: 9031: 9028: 9027: 8962: 8935: 8897: 8874: 8865: 8861: 8853: 8831: 8830: 8822:Option D, et al? 8777: 8776: 8772: 8771: 8765: 8762: 8761: 8701: 8683: 8654: 8651: 8606: 8600: 8595: 8593: 8560: 8511: 8477: 8458: 8457: 8379: 8363: 8360: 8354: 8307: 8283: 8266: 8241: 8205: 8189: 8168: 8153: 8131: 8121:Content disputes 8108: 8071: 8041: 8040: 8038: 7984:is not effective 7964: 7963: 7961: 7929: 7905: 7878: 7846: 7825: 7824: 7822: 7780: 7779: 7777: 7705: 7639: 7638: 7636: 7598: 7581: 7571: 7570: 7568: 7559: 7546: 7541: 7529: 7528: 7526: 7490: 7489: 7487: 7474: 7454: 7453: 7451: 7443: 7426: 7425: 7423: 7386: 7378: 7363: 7355: 7319: 7308: 7300: 7269: 7263: 7250: 7244:out-of-the-lines 7235: 7199: 7195: 7187: 7170: 7162: 7148: 7127: 7112: 7097: 7082: 7073: 7067: 7053: 7036:block even edit 7029: 7023: 7017: 7013: 7007: 6967: 6961: 6944: 6943: 6907:Imaginary number 6851: 6825: 6747: 6730: 6691: 6678: 6669: 6598: 6577: 6572:and all that. ~ 6559: 6551: 6502: 6495: 6492: 6489: 6468: 6467: 6465: 6383: 6378: 6367: 6364: 6361: 6349: 6343: 6160: 6159: 6122: 6121: 6087: 6080: 6046: 6043: 6040: 6021: 6017: 5827: 5819: 5804: 5726: 5693: 5691: 5659: 5640: 5638: 5552: 5551: 5550: 5443: 5434: 5418: 5370: 5361: 5346: 5341: 5322: 5255: 5229: 5224: 5073: 5028: 4977: 4854: 4850: 4845: 4832: 4829: 4763:Compassionate727 4748: 4728: 4712: 4703: 4668: 4628:NinjaRobotPirate 4578: 4533: 4525: 4508: 4506: 4500: 4494: 4477: 4459: 4451: 4349: 4302: 4279: 4255: 4212: 4181: 4156: 4155: 4133: 4131: 4130: 4111: 3946: 3912: 3911: 3880: 3790: 3785: 3778: 3743: 3739: 3735: 3731: 3726: 3724: 3707: 3670: 3666: 3659: 3657: 3639: 3635: 3632: 3560: 3552: 3537: 3527: 3521: 3478: 3472: 3454: 3430:Mr. Stradivarius 3428:essentially per 3397: 3344: 3289: 3258: 3251: 3225: 3220: 3127: 3126: 3124: 3060: 3057: 3051: 3003: 3001: 2931: 2926: 2911: 2906: 2891: 2883: 2869: 2850: 2844: 2732: 2731: 2728: 2711: 2710:Mr. Stradivarius 2695: 2693: 2688: 2666: 2660: 2561: 2558: 2555: 2517: 2469: 2437: 2434: 2336:support option B 2272: 2250: 2208: 2203: 2196: 2111: 2107: 2050: 2034: 1934: 1921: 1876: 1871: 1866: 1804: 1800: 1793: 1791: 1757: 1753: 1746: 1744: 1628: 1442: 1395: 1298:FockeWulf FW 190 1165:Matt Fitzpatrick 1107: 1101: 1096: 1053: 1048: 1000: 903: 897: 892: 859:JaventheAlderick 825: 824: 820: 819: 813: 810: 809: 738: 735: 630: 626: 618: 587: 575: 567: 547: 475: 438: 398: 340: 318: 312: 282: 161: 141: 135: 42: 27: 10312: 10311: 10307: 10306: 10305: 10303: 10302: 10301: 10300: 10299: 10277: 10273: 10239: 10226: 10198:DavidLeighEllis 10193: 10164: 10162: 10160: 10142: 10103: 10076: 10074: 10072: 10048: 10037: 10035: 10033: 10001: 9999:AN notification 9923: 9900: 9877: 9868: 9866: 9851: 9794: 9738: 9704: 9672: 9659: 9645: 9614: 9564: 9556: 9541: 9531: 9514: 9489: 9461: 9422: 9362: 9319: 9296: 9270: 9265: 9250: 9246: 9237: 9235: 9227: 9223: 9188: 9142: 9132: 9035: 9024: 8960: 8933: 8895: 8871: 8866: 8851: 8847: 8838: 8836: 8828: 8824: 8785:Strongly Oppose 8769: 8758: 8699: 8652: 8649: 8619:DavidLeighEllis 8609: 8604: 8598: 8587: 8554: 8529: 8524: 8509: 8475: 8463: 8455: 8427:DavidLeighEllis 8397:DavidLeighEllis 8382: 8358: 8352: 8350: 8279: 8269: 8228:Someone above ( 8226: 8208: 8185: 8171: 8149: 8134: 8123: 8111: 8067: 8036: 8034: 8032: 7976: 7959: 7957: 7955: 7927: 7922: 7903: 7876: 7873: 7844: 7839: 7820: 7818: 7816: 7775: 7773: 7771: 7743: 7729: 7704: 7691: 7634: 7632: 7630: 7579: 7566: 7564: 7562: 7553: 7544: 7535: 7524: 7522: 7520: 7485: 7483: 7481: 7460: 7449: 7447: 7445: 7433: 7421: 7419: 7417: 7376: 7372: 7361: 7353: 7317: 7298: 7294: 7265: 7257: 7248: 7233: 7229:example article 7214: 7185: 7181: 7164: 7134: 7125: 7110: 7095: 7080: 7071: 7065: 7025: 7021: 7015: 7011: 7005: 6965: 6959: 6949: 6849: 6823: 6741: 6728: 6689: 6667: 6611: 6594: 6580: 6549: 6545: 6500: 6493: 6490: 6487: 6463: 6461: 6459: 6381: 6376: 6365: 6362: 6359: 6306: 6304:AN notification 6301: 6285:DavidLeighEllis 6230:RickinBaltimore 6208:RickinBaltimore 6193:RickinBaltimore 6154: 6116: 6076: 6044: 6041: 6038: 6024: 5925:per Xxanthippe 5817: 5813: 5798: 5689: 5686: 5652: 5636: 5634: 5548: 5546: 5544: 5462:states is that 5436: 5432: 5421: 5388: 5363: 5359: 5072: 5059: 5027: 5014: 4852: 4848: 4843: 4830: 4827: 4746: 4724: 4711: 4706: 4699: 4666: 4576: 4523: 4519: 4502: 4496: 4488: 4480: 4449: 4445: 4345: 4296: 4277: 4244: 4239:Pile-on support 4210: 4188:Kudpung กุดผึ้ง 4179: 4150: 4129: 4126: 4122: 4098: 4078: 3944: 3907: 3878: 3861: 3788: 3777: 3772: 3761: 3737: 3733: 3729: 3722: 3720: 3705: 3662: 3653: 3651: 3628: 3626: 3550: 3546: 3525: 3519: 3517: 3476: 3470: 3413:RickinBaltimore 3342: 3223: 3215: 3122: 3120: 3118: 3055: 3049: 3047: 2985: 2929: 2924: 2909: 2904: 2886: 2881: 2788:. Makes sense. 2729: 2726: 2725: 2709: 2691: 2686: 2684: 2681:pending changes 2664: 2658: 2576: 2559: 2556: 2553: 2528: 2515: 2467: 2435: 2432: 2270: 2053: 2037: 1911: 1904: 1874: 1869: 1864: 1796: 1787: 1785: 1749: 1740: 1738: 1622: 1588: 1445: 1393: 1110: 1105: 1099: 1051: 1046: 906: 901: 895: 817: 806: 740:problem solving 733: 616: 612: 603: 581: 565: 561: 541: 473: 436: 397: 384: 291: 278: 216: 200:this discussion 189:passed a motion 170: 165: 164: 157: 153: 139: 131: 47: 38: 29: 28: 21: 20: 12: 11: 5: 10310: 10293: 10292: 10291: 10259: 10244: 10233: 10223: 10192: 10189: 10188: 10187: 10186: 10185: 10184: 10183: 10182: 10181: 10180: 10179: 10178: 10177: 10176: 10175: 10174: 10173: 10000: 9997: 9996: 9995: 9994: 9993: 9992: 9991: 9929: 9921: 9912: 9911: 9910: 9909: 9908: 9907: 9906: 9898: 9854: 9828: 9793: 9790: 9789: 9788: 9787: 9786: 9785: 9784: 9783: 9782: 9781: 9780: 9779: 9778: 9777: 9776: 9775: 9774: 9666: 9653:protection of 9621: 9620: 9612: 9598: 9597: 9596: 9595: 9594: 9593: 9592: 9591: 9590: 9589: 9588: 9554: 9512: 9456: 9455: 9454: 9453: 9435: 9431: 9430: 9429: 9417: 9400: 9385: 9342: 9341: 9334: 9333: 9317: 9269: 9266: 9225: 9222: 9219: 9218: 9217: 9216: 9215: 9214: 9213: 9212: 9211: 9210: 9209: 9165:WP:FULLPROTECT 9152: 9151: 9150: 9149: 9109: 9107: 9106: 9057:Mooseandbruce1 8974: 8973: 8972: 8971: 8970: 8969: 8968: 8967: 8925: 8924: 8923: 8922: 8870: 8867: 8826: 8823: 8820: 8819: 8818: 8800: 8782: 8746: 8724: 8706: 8691: 8660: 8637: 8636: 8635: 8634: 8633: 8632: 8631: 8630: 8629: 8602: 8528: 8525: 8521: 8520: 8519: 8518: 8517: 8516: 8465: 8464: 8461: 8456: 8454: 8451: 8450: 8449: 8448: 8447: 8446: 8445: 8444: 8443: 8442: 8441: 8440: 8439: 8438: 8437: 8389: 8388: 8380: 8368: 8367: 8353:Chris Troutman 8339: 8338: 8320: 8319: 8318: 8317: 8316: 8315: 8288: 8287: 8267: 8225: 8224:PC2 protection 8222: 8221: 8220: 8219: 8218: 8217: 8216: 8215: 8214: 8206: 8169: 8132: 8122: 8119: 8118: 8117: 8109: 8096: 8095: 8094: 8093: 8092: 8091: 8090: 8075: 8054: 8004: 7975: 7972: 7971: 7970: 7969: 7968: 7921: 7918: 7917: 7916: 7915: 7914: 7913: 7912: 7911: 7910: 7871: 7838: 7835: 7834: 7833: 7832: 7831: 7830: 7829: 7742: 7739: 7738: 7737: 7736: 7735: 7734: 7733: 7719: 7698: 7672: 7667: 7666: 7662: 7652:Ms Sarah Welch 7647: 7646: 7645: 7644: 7643: 7596: 7595: 7594: 7593: 7592: 7591: 7590: 7589: 7588: 7587: 7586: 7458: 7406: 7405: 7404: 7390: 7335: 7334: 7333: 7332: 7331: 7330: 7329: 7328: 7327: 7326: 7325: 7324: 7255: 7211: 7210: 7209: 7208: 7207: 7206: 7205: 7204: 7203: 7202: 7117: 7102: 7033: 7019:edit protected 7002: 6951: 6950: 6947: 6942: 6941: 6940: 6939: 6902: 6901: 6900: 6899: 6898: 6897: 6896: 6895: 6836: 6835: 6816: 6815: 6814: 6813: 6812: 6811: 6810: 6809: 6737: 6736: 6735: 6705: 6704: 6701: 6700: 6699: 6698: 6697: 6655: 6644: 6641: 6610: 6607: 6606: 6605: 6604: 6603: 6602: 6587: 6586: 6578: 6564: 6510: 6509: 6508: 6477: 6476: 6475: 6474: 6473: 6472: 6427: 6426: 6425: 6405: 6404: 6403: 6372: 6305: 6302: 6300: 6297: 6296: 6295: 6278: 6261: 6244: 6243: 6242: 6241: 6240: 6226: 6171: 6170: 6169: 6168: 6167: 6166: 6165: 6152:Oops. Thanks. 6091: 6070: 6053: 6030: 6022: 6005: 5988: 5971: 5954: 5937: 5920: 5919: 5918: 5892: 5871: 5870: 5869: 5868: 5867: 5837: 5836: 5835: 5834: 5833: 5832: 5831: 5720: 5719: 5718: 5690:The Voidwalker 5680: 5663: 5645: 5617: 5600: 5583: 5571: 5569: 5567: 5565: 5563: 5557: 5536: 5514: 5497: 5496: 5495: 5494: 5493: 5492: 5491: 5490: 5489: 5449:It would be a 5419: 5384: 5374: 5352: 5330: 5312: 5295: 5278: 5260: 5237: 5209: 5208: 5207: 5183:accounts, per 5177: 5176: 5175: 5117: 5100: 5083: 5082: 5081: 5080: 5079: 5078: 5077: 5066: 5021: 4989: 4963: 4958:KGirlTrucker81 4951: 4942:automatic list 4935: 4908: 4891: 4876: 4859: 4838: 4815: 4803: 4786: 4768: 4756: 4734: 4717: 4707: 4692: 4675: 4656: 4638: 4621: 4609: 4588: 4559: 4541: 4540: 4539: 4538: 4537: 4478: 4424: 4407: 4392: 4375: 4358: 4327: 4310: 4288: 4264: 4236: 4222:Strong support 4219: 4198: 4161: 4143: 4127: 4118:Barely support 4115: 4089: 4074: 4063: 4046: 4029: 4005: 3990: 3980:TenOfAllTrades 3973: 3963:Ms Sarah Welch 3956: 3926: 3901: 3884: 3876: 3858: 3850: 3835: 3818: 3795: 3773: 3765: 3757: 3747: 3714: 3698: 3681: 3680: 3679: 3678: 3677: 3676: 3675: 3619: 3602: 3584: 3566: 3565: 3564: 3515: 3514: 3513: 3498:very very weak 3464: 3445: 3423: 3406: 3370: 3349: 3330: 3312: 3294: 3280: 3263: 3242: 3230: 3208: 3187: 3167: 3148: 3131: 3107: 3089:Just what our 3084: 3064: 3050:Chris Troutman 3041: 3025: 3008: 2990: 2981: 2971: 2954: 2936: 2916: 2896: 2874: 2856: 2838: 2817: 2800: 2783: 2766: 2754: 2737: 2718: 2699: 2673: 2649: 2637: 2620: 2602: 2581: 2574: 2566: 2546: 2527: 2524: 2523: 2522: 2508: 2486: 2474: 2455: 2442: 2412: 2390: 2389: 2388: 2354: 2344:Mooseandbruce1 2332: 2317: 2307:NewYorkActuary 2303:incrementalism 2296: 2279: 2278: 2277: 2267: 2266: 2265: 2261: 2254: 2232: 2213: 2183: 2166: 2145: 2133: 2116: 2096: 2079: 2069:Happy Squirrel 2061: 2060: 2059: 2051: 2035: 2015: 2014: 2013: 1988: 1948: 1925: 1903: 1900: 1899: 1898: 1881: 1847: 1830: 1812: 1811: 1810: 1809: 1808: 1735:Strong Support 1732: 1722:Joshualouie711 1707: 1689: 1672: 1651: 1634: 1625: 1610: 1592: 1582: 1564: 1546: 1545: 1544: 1510: 1488: 1470: 1469: 1468: 1467: 1466: 1443: 1420:Strong support 1417: 1400: 1386: 1361: 1343: 1325: 1308: 1286: 1268: 1251: 1234: 1214:User:ONUnicorn 1207: 1197:discussion. ·· 1188: 1185: 1175: 1150: 1117: 1116: 1115: 1103: 1075: 1058: 1039: 1022: 976: 964: 946: 928: 911: 899: 886: 869: 852: 830: 780: 763: 746: 725: 707: 692: 674: 673: 672: 656: 635: 634: 633: 632: 631: 521: 503: 485: 465: 443: 419: 402: 391: 377:Strong support 374: 348: 326: 325: 324: 290: 287: 266:Regarding the 264: 263: 253: 223: 215: 212: 169: 166: 163: 162: 154: 149: 147: 114: 113: 109: 106: 102: 101: 100: 85: 48: 46: 45: 33: 32: 15: 9: 6: 4: 3: 2: 10309: 10297: 10290: 10285: 10282: 10280: 10272: 10271: 10270: 10264: 10260: 10258: 10254: 10250: 10245: 10243: 10238: 10237: 10232: 10231: 10224: 10222: 10218: 10214: 10210: 10209: 10208: 10207: 10203: 10199: 10191:User requests 10172: 10167: 10158: 10154: 10151:See also the 10150: 10149: 10148: 10145: 10139: 10135: 10131: 10130: 10129: 10125: 10121: 10117: 10112: 10111: 10110: 10106: 10100: 10099: 10098: 10094: 10090: 10086: 10085: 10084: 10079: 10069: 10068: 10067: 10063: 10059: 10052: 10047: 10046: 10045: 10040: 10031: 10027: 10026: 10025: 10024: 10020: 10015: 10011: 10007: 9990: 9986: 9981: 9977: 9972: 9968: 9964: 9963: 9962: 9958: 9954: 9950: 9949: 9948: 9944: 9939: 9935: 9930: 9928: 9925: 9919: 9913: 9905: 9902: 9896: 9890: 9889: 9888: 9882: 9880: 9873: 9871: 9864: 9863: 9862: 9858: 9856: 9848: 9843: 9842: 9841: 9837: 9833: 9829: 9827: 9823: 9819: 9818:Peter coxhead 9815: 9814: 9813: 9812: 9808: 9804: 9800: 9773: 9769: 9765: 9760: 9759: 9758: 9754: 9750: 9746: 9745: 9744: 9741: 9735: 9730: 9729: 9728: 9724: 9720: 9715: 9712: 9711: 9710: 9707: 9700: 9696: 9693: 9692: 9691: 9687: 9683: 9678: 9677: 9676: 9671: 9670: 9665: 9664: 9656: 9649: 9641: 9640: 9639: 9635: 9631: 9627: 9623: 9622: 9619: 9616: 9610: 9604: 9599: 9587: 9583: 9579: 9572: 9568: 9563: 9562: 9561: 9558: 9552: 9545: 9540: 9539: 9538: 9535: 9534: 9525: 9521: 9520: 9519: 9516: 9510: 9505: 9501: 9497: 9496: 9495: 9492: 9490:Darwinian Ape 9485: 9484: 9483: 9479: 9475: 9470: 9469: 9468: 9467: 9464: 9462:Darwinian Ape 9452: 9448: 9444: 9440: 9436: 9432: 9428: 9425: 9423:Darwinian Ape 9418: 9415: 9414: 9413: 9409: 9405: 9401: 9399: 9395: 9391: 9386: 9382: 9378: 9374: 9370: 9369: 9368: 9365: 9363:Darwinian Ape 9359: 9354: 9349: 9344: 9343: 9340: 9336: 9335: 9331: 9327: 9326: 9325: 9324: 9321: 9315: 9308: 9305: 9303: 9299: 9293: 9291: 9286: 9281: 9279: 9275: 9272:On July 1, a 9263: 9258: 9255: 9253: 9245: 9244: 9243: 9234: 9208: 9204: 9200: 9196: 9195: 9194: 9191: 9189:Darwinian Ape 9184: 9183: 9182: 9178: 9174: 9169: 9166: 9162: 9158: 9157: 9156: 9155: 9154: 9153: 9148: 9145: 9143:Darwinian Ape 9136: 9131: 9130: 9129: 9125: 9121: 9117: 9112: 9111: 9110: 9105: 9101: 9097: 9093: 9089: 9085: 9081: 9077: 9073: 9069: 9068: 9067: 9066: 9062: 9058: 9052: 9048: 9047: 9044: 9039: 9029: 9018: 9013: 9009: 9005: 8999: 8998: 8994: 8990: 8987: 8983: 8979: 8966: 8963: 8961:Darwinian Ape 8956: 8955: 8954: 8950: 8946: 8941: 8940: 8939: 8936: 8934:Darwinian Ape 8929: 8928: 8927: 8926: 8919: 8918: 8917: 8913: 8909: 8904: 8903: 8902: 8901: 8898: 8896:Darwinian Ape 8891: 8886: 8884: 8878: 8877: 8864: 8859: 8856: 8854: 8846: 8845: 8844: 8835: 8817: 8813: 8809: 8804: 8801: 8799: 8795: 8791: 8786: 8783: 8781: 8778: 8773: 8763: 8754: 8750: 8747: 8744: 8740: 8736: 8732: 8728: 8725: 8723: 8719: 8715: 8710: 8707: 8705: 8702: 8700:Darwinian Ape 8695: 8692: 8690: 8686: 8681: 8677: 8673: 8668: 8664: 8661: 8659: 8656: 8655: 8645: 8641: 8638: 8628: 8624: 8620: 8615: 8614: 8613: 8607: 8601: 8591: 8586: 8585: 8584: 8580: 8576: 8572: 8568: 8564: 8558: 8553: 8552: 8551: 8550: 8549: 8545: 8541: 8537: 8534: 8533: 8532: 8515: 8512: 8506: 8505: 8504: 8500: 8499:contributions 8496: 8492: 8491:Jo-Jo Eumerus 8488: 8484: 8483: 8482: 8481: 8478: 8472: 8467: 8466: 8460: 8459: 8436: 8432: 8428: 8424: 8420: 8416: 8412: 8408: 8407: 8406: 8402: 8398: 8393: 8392: 8391: 8390: 8387: 8384: 8378: 8372: 8371: 8370: 8369: 8366: 8361: 8355: 8347: 8346: 8345: 8344: 8343: 8342: 8341: 8340: 8337: 8333: 8329: 8328: 8322: 8321: 8314: 8310: 8305: 8301: 8296: 8292: 8291: 8290: 8289: 8286: 8282: 8276: 8275: 8274: 8271: 8265: 8260: 8256: 8251: 8250: 8249: 8248: 8244: 8239: 8235: 8231: 8213: 8210: 8204: 8199: 8194: 8193: 8192: 8188: 8182: 8178: 8177: 8176: 8173: 8167: 8162: 8158: 8157: 8156: 8152: 8147: 8142: 8141: 8140: 8139: 8136: 8130: 8116: 8113: 8107: 8101: 8100:autoconfirmed 8097: 8089: 8085: 8081: 8076: 8074: 8070: 8064: 8063: 8062: 8059: 8055: 8053: 8050: 8046: 8045: 8044: 8039: 8029: 8028: 8027: 8023: 8019: 8015: 8014: 8013: 8012: 8009: 8005: 8003: 8000: 7997: 7993: 7989: 7985: 7981: 7967: 7962: 7953: 7952: 7951: 7947: 7943: 7938: 7937: 7936: 7935: 7932: 7930: 7909: 7906: 7904:Darwinian Ape 7899: 7898: 7897: 7893: 7889: 7884: 7883: 7882: 7879: 7877:Darwinian Ape 7868: 7867: 7866: 7862: 7858: 7853: 7852: 7851: 7850: 7847: 7845:Darwinian Ape 7828: 7823: 7813: 7808: 7804: 7803: 7802: 7798: 7794: 7789: 7785: 7784: 7783: 7778: 7768: 7764: 7760: 7759: 7758: 7757: 7753: 7749: 7732: 7727: 7723: 7718: 7714: 7710: 7709: 7708: 7703: 7702: 7697: 7696: 7688: 7687: 7686: 7682: 7678: 7673: 7669: 7668: 7663: 7661: 7657: 7653: 7648: 7642: 7637: 7627: 7626: 7625: 7621: 7617: 7613: 7608: 7607:at this point 7602: 7601:edit conflict 7597: 7585: 7582: 7576: 7575: 7574: 7569: 7557: 7552: 7551: 7550: 7547: 7539: 7534: 7533: 7532: 7527: 7518: 7514: 7513: 7512: 7508: 7504: 7500: 7495: 7494: 7493: 7488: 7478: 7472: 7471:KrakatoaKatie 7468: 7464: 7459: 7457: 7452: 7441: 7440:Darwinian Ape 7437: 7431: 7430: 7429: 7424: 7415: 7411: 7410:not permanent 7407: 7403: 7399: 7395: 7391: 7389: 7384: 7381: 7379: 7371: 7370: 7369: 7359: 7351: 7350: 7349: 7346: 7344: 7340: 7337: 7336: 7323: 7320: 7318:Darwinian Ape 7313: 7312: 7311: 7306: 7303: 7301: 7293: 7292: 7291: 7285: 7281: 7277: 7273: 7268: 7261: 7260:Darwinian Ape 7256: 7254: 7251: 7245: 7241: 7240: 7239: 7236: 7234:Darwinian Ape 7230: 7226: 7222: 7221: 7220: 7219: 7218: 7217: 7216: 7215: 7198: 7193: 7190: 7188: 7180: 7179: 7178: 7168: 7160: 7156: 7152: 7146: 7142: 7141:KrakatoaKatie 7138: 7133: 7132: 7131: 7128: 7122: 7118: 7116: 7113: 7107: 7103: 7101: 7098: 7092: 7088: 7087: 7086: 7083: 7077: 7070: 7062: 7061: 7060: 7056: 7051: 7047: 7043: 7039: 7034: 7032: 7028: 7020: 7010: 7003: 7001: 6997: 6993: 6989: 6988: 6987: 6986: 6983: 6979: 6975: 6971: 6964: 6957: 6953: 6952: 6946: 6945: 6938: 6934: 6930: 6925: 6924: 6923: 6922: 6919: 6916: 6913: 6908: 6894: 6890: 6886: 6885:50.32.227.204 6882: 6877: 6872: 6871: 6870: 6866: 6862: 6857: 6856: 6855: 6852: 6850:Darwinian Ape 6845: 6840: 6839: 6838: 6837: 6834: 6830: 6826: 6818: 6817: 6808: 6804: 6800: 6795: 6794: 6793: 6789: 6785: 6780: 6775: 6774: 6773: 6769: 6765: 6761: 6760: 6759: 6755: 6751: 6745: 6744:KrakatoaKatie 6738: 6734: 6731: 6729:Darwinian Ape 6724: 6723: 6722: 6721: 6720: 6719: 6715: 6711: 6702: 6695: 6692: 6686: 6682: 6677: 6676: 6675: 6674: 6673: 6670: 6668:Darwinian Ape 6664: 6660: 6656: 6653: 6649: 6645: 6642: 6639: 6638: 6637: 6636: 6632: 6628: 6623: 6619: 6617: 6601: 6597: 6591: 6590: 6589: 6588: 6585: 6582: 6576: 6571: 6566: 6565: 6563: 6562: 6557: 6554: 6552: 6544: 6543: 6542: 6536: 6532: 6528: 6524: 6520: 6516: 6507: 6504: 6503: 6497: 6496: 6484: 6479: 6478: 6471: 6466: 6457: 6456:User:MusikBot 6453: 6449: 6445: 6444: 6443: 6439: 6435: 6431: 6428: 6424: 6420: 6416: 6411: 6410:actively prod 6406: 6402: 6398: 6394: 6389: 6388: 6387: 6384: 6379: 6373: 6371: 6368: 6356: 6355: 6354: 6348: 6347: 6340: 6339: 6338: 6334: 6330: 6325: 6324: 6323: 6322: 6318: 6314: 6310: 6294: 6290: 6286: 6282: 6279: 6277: 6273: 6269: 6265: 6262: 6260: 6256: 6252: 6248: 6245: 6239: 6235: 6231: 6227: 6225: 6221: 6217: 6213: 6209: 6205: 6204: 6203: 6202: 6198: 6194: 6190: 6186: 6185: 6184: 6180: 6176: 6172: 6164: 6161: 6158: 6151: 6150: 6149: 6145: 6141: 6137: 6133: 6129: 6128: 6127: 6126: 6123: 6120: 6112: 6108: 6107: 6106: 6103: 6101: 6100: 6095: 6092: 6090: 6084: 6079: 6074: 6071: 6069: 6065: 6061: 6057: 6054: 6052: 6048: 6047: 6034: 6031: 6029: 6026: 6019: 6015: 6014: 6009: 6006: 6004: 6000: 5996: 5992: 5989: 5987: 5983: 5979: 5975: 5972: 5970: 5966: 5962: 5958: 5955: 5953: 5949: 5945: 5941: 5938: 5936: 5932: 5928: 5924: 5921: 5917: 5913: 5909: 5908:BattleshipMan 5905: 5904: 5903: 5900: 5896: 5893: 5891: 5887: 5883: 5879: 5875: 5872: 5865: 5861: 5857: 5852: 5851: 5850: 5846: 5842: 5838: 5830: 5825: 5822: 5820: 5812: 5811: 5810: 5802: 5797: 5796: 5794: 5790: 5786: 5782: 5781: 5780: 5776: 5772: 5769: 5766: 5762: 5761: 5759: 5755: 5751: 5747: 5744: 5743: 5742: 5738: 5734: 5729: 5724: 5721: 5717: 5713: 5709: 5705: 5701: 5698: 5697: 5696: 5692: 5684: 5681: 5679: 5675: 5671: 5670:Chiswick Chap 5667: 5664: 5662: 5658: 5655: 5649: 5646: 5644: 5641: 5639: 5632: 5631: 5627: 5626: 5621: 5618: 5616: 5612: 5608: 5604: 5601: 5599: 5595: 5591: 5587: 5584: 5582: 5578: 5574: 5561: 5558: 5556: 5553: 5540: 5537: 5535: 5531: 5527: 5523: 5518: 5515: 5513: 5509: 5505: 5501: 5498: 5488: 5484: 5480: 5476: 5472: 5471: 5466: 5461: 5457: 5452: 5448: 5447: 5446: 5442: 5439: 5435: 5428: 5427: 5426: 5423: 5417: 5411: 5410: 5409: 5405: 5401: 5397: 5394: 5393: 5392: 5387: 5382: 5378: 5375: 5373: 5369: 5366: 5362: 5356: 5353: 5351: 5348: 5347: 5342: 5334: 5331: 5329: 5325: 5321: 5316: 5313: 5311: 5307: 5303: 5299: 5296: 5294: 5290: 5286: 5282: 5279: 5277: 5273: 5269: 5264: 5261: 5259: 5256: 5254: 5253: 5245: 5241: 5238: 5236: 5233: 5230: 5228: 5223: 5217: 5213: 5210: 5206: 5202: 5198: 5194: 5190: 5186: 5182: 5178: 5174: 5170: 5166: 5162: 5161: 5160: 5159: 5155: 5151: 5147: 5143: 5142: 5141: 5137: 5133: 5130: 5126: 5121: 5118: 5116: 5112: 5108: 5104: 5101: 5099: 5095: 5091: 5087: 5084: 5076: 5071: 5070: 5065: 5064: 5056: 5055: 5054: 5050: 5046: 5041: 5037: 5033: 5032: 5031: 5026: 5025: 5020: 5019: 5012: 5008: 5007: 5006: 5002: 4998: 4993: 4990: 4988: 4983: 4980: 4975: 4971: 4967: 4964: 4962: 4959: 4955: 4952: 4950: 4947: 4943: 4939: 4936: 4934: 4930: 4926: 4922: 4918: 4917: 4912: 4909: 4907: 4903: 4899: 4895: 4892: 4890: 4887: 4884: 4880: 4877: 4875: 4871: 4867: 4863: 4860: 4858: 4855: 4851: 4846: 4839: 4837: 4834: 4833: 4823: 4822:One Direction 4819: 4816: 4814: 4811: 4807: 4804: 4802: 4798: 4794: 4790: 4787: 4785: 4781: 4777: 4772: 4769: 4767: 4764: 4760: 4757: 4755: 4752: 4749: 4742: 4738: 4735: 4733: 4730: 4727: 4721: 4718: 4716: 4713: 4710: 4704: 4702: 4696: 4693: 4691: 4687: 4683: 4679: 4676: 4674: 4671: 4670: 4669: 4660: 4657: 4655: 4651: 4647: 4642: 4639: 4637: 4633: 4629: 4625: 4622: 4620: 4617: 4613: 4610: 4608: 4604: 4600: 4596: 4592: 4589: 4587: 4584: 4583: 4580: 4579: 4572: 4568: 4563: 4560: 4558: 4554: 4550: 4545: 4542: 4536: 4531: 4528: 4526: 4518: 4517: 4516: 4505: 4499: 4492: 4487: 4486: 4485: 4482: 4476: 4471: 4467: 4466: 4465: 4462: 4457: 4454: 4452: 4444: 4443: 4442: 4436: 4432: 4428: 4425: 4423: 4419: 4415: 4414:Albrecht Conz 4411: 4408: 4406: 4403: 4400: 4396: 4393: 4391: 4387: 4383: 4379: 4376: 4374: 4370: 4366: 4362: 4359: 4357: 4353: 4348: 4343: 4339: 4335: 4331: 4328: 4326: 4322: 4318: 4314: 4311: 4309: 4306: 4303: 4301: 4300: 4292: 4289: 4287: 4284: 4283: 4282: 4280: 4272: 4268: 4265: 4263: 4262: 4259: 4256: 4254: 4253: 4251: 4248: 4240: 4237: 4235: 4231: 4227: 4223: 4220: 4218: 4215: 4213: 4206: 4202: 4199: 4197: 4193: 4189: 4185: 4177: 4173: 4169: 4165: 4162: 4160: 4157: 4154: 4147: 4144: 4142: 4137: 4132: 4125: 4119: 4116: 4114: 4109: 4105: 4101: 4097: 4093: 4090: 4088: 4085: 4084: 4083: 4079: 4077: 4071: 4067: 4064: 4062: 4058: 4054: 4050: 4047: 4045: 4041: 4037: 4033: 4030: 4028: 4025: 4021: 4017: 4013: 4009: 4006: 4004: 4001: 3998: 3994: 3991: 3989: 3985: 3981: 3977: 3974: 3972: 3968: 3964: 3960: 3957: 3955: 3951: 3947: 3942: 3938: 3934: 3930: 3927: 3925: 3920: 3916: 3910: 3905: 3902: 3900: 3896: 3892: 3888: 3885: 3883: 3874: 3871: 3868: 3866: 3856: 3854: 3851: 3849: 3846: 3845: 3839: 3836: 3834: 3830: 3826: 3822: 3819: 3817: 3813: 3810: 3807: 3803: 3799: 3796: 3794: 3791: 3786: 3783: 3782: 3776: 3769: 3766: 3764: 3760: 3759:contributions 3755: 3751: 3748: 3746: 3740: 3732: 3725: 3718: 3715: 3713: 3710: 3708: 3702: 3699: 3697: 3693: 3689: 3685: 3682: 3674: 3673: 3667: 3665: 3658: 3656: 3648: 3647: 3646: 3645: 3644: 3643: 3642: 3638: 3633: 3631: 3623: 3620: 3618: 3614: 3610: 3606: 3603: 3601: 3597: 3593: 3588: 3585: 3583: 3580: 3578: 3576: 3575: 3570: 3567: 3563: 3558: 3555: 3553: 3545: 3544: 3543: 3535: 3531: 3524: 3516: 3512: 3508: 3504: 3499: 3495: 3494: 3493: 3492: 3491: 3487: 3483: 3475: 3468: 3465: 3463: 3458: 3453: 3449: 3446: 3444: 3440: 3436: 3431: 3427: 3424: 3422: 3418: 3414: 3410: 3407: 3405: 3402: 3400: 3395: 3394: 3391: 3388: 3385: 3382: 3379: 3374: 3371: 3369: 3366: 3361: 3357: 3353: 3350: 3348: 3345: 3340: 3339: 3334: 3331: 3329: 3325: 3321: 3320:BattleshipMan 3316: 3313: 3310: 3306: 3302: 3298: 3295: 3293: 3288: 3284: 3281: 3279: 3276: 3271: 3270:very specific 3267: 3264: 3262: 3259: 3257: 3252: 3246: 3243: 3241: 3238: 3234: 3231: 3229: 3226: 3221: 3218: 3212: 3209: 3207: 3203: 3199: 3195: 3191: 3188: 3186: 3183: 3182: 3179: 3176: 3171: 3168: 3166: 3163: 3161: 3157: 3152: 3149: 3147: 3143: 3139: 3138:Peter coxhead 3135: 3132: 3130: 3125: 3116: 3111: 3108: 3106: 3102: 3098: 3092: 3088: 3085: 3083: 3080: 3079: 3078: 3074: 3073: 3068: 3065: 3063: 3058: 3052: 3045: 3042: 3040: 3037: 3034:pay for it). 3033: 3029: 3026: 3024: 3020: 3016: 3012: 3009: 3007: 3002: 3000: 2994: 2991: 2989: 2984: 2979: 2975: 2972: 2970: 2966: 2962: 2958: 2955: 2953: 2950: 2949: 2944: 2940: 2937: 2935: 2932: 2927: 2920: 2917: 2915: 2912: 2907: 2900: 2897: 2895: 2892: 2890: 2884: 2878: 2875: 2873: 2868: 2867:Seraphimblade 2864: 2860: 2857: 2855: 2849: 2848: 2842: 2839: 2837: 2833: 2829: 2825: 2821: 2818: 2816: 2812: 2808: 2804: 2801: 2799: 2795: 2791: 2787: 2784: 2782: 2778: 2774: 2770: 2767: 2765: 2762: 2758: 2755: 2753: 2749: 2745: 2741: 2738: 2736: 2733: 2722: 2719: 2717: 2714: 2713: 2712: 2703: 2700: 2698: 2694: 2689: 2682: 2677: 2674: 2672: 2669: 2667: 2661: 2653: 2650: 2648: 2645: 2641: 2638: 2636: 2632: 2628: 2624: 2621: 2619: 2615: 2611: 2606: 2603: 2601: 2597: 2593: 2588: 2585: 2582: 2580: 2577: 2570: 2567: 2565: 2562: 2550: 2547: 2545: 2541: 2537: 2533: 2530: 2529: 2521: 2518: 2512: 2509: 2507: 2503: 2499: 2494: 2493:strong oppose 2490: 2487: 2485: 2482: 2478: 2475: 2473: 2470: 2463: 2459: 2456: 2453: 2450: 2446: 2443: 2441: 2438: 2429: 2428:Esquivalience 2426:userboxes as 2425: 2421: 2416: 2413: 2411: 2407: 2403: 2398: 2394: 2391: 2387: 2383: 2379: 2375: 2372: 2371: 2370: 2366: 2362: 2358: 2355: 2353: 2349: 2345: 2341: 2337: 2333: 2331: 2327: 2323: 2318: 2316: 2312: 2308: 2304: 2300: 2297: 2295: 2291: 2287: 2283: 2280: 2276: 2273: 2268: 2262: 2258: 2257: 2255: 2248: 2244: 2239: 2238: 2236: 2233: 2231: 2227: 2223: 2222: 2217: 2214: 2212: 2209: 2207: 2202: 2201: 2195: 2194: 2187: 2184: 2182: 2178: 2174: 2170: 2167: 2165: 2161: 2157: 2153: 2149: 2146: 2144: 2141: 2140:sandgemADDICT 2137: 2134: 2132: 2128: 2124: 2120: 2117: 2115: 2112: 2108: 2106: 2100: 2097: 2095: 2091: 2087: 2083: 2080: 2078: 2074: 2070: 2065: 2062: 2058: 2055: 2049: 2044: 2043: 2042: 2039: 2033: 2027: 2023: 2020:. Addressing 2019: 2016: 2012: 2008: 2004: 2000: 1996: 1992: 1989: 1987: 1986: 1983: 1979: 1975: 1971: 1967: 1963: 1962: 1961: 1957: 1953: 1949: 1947: 1942: 1938: 1933: 1929: 1926: 1924: 1919: 1915: 1914:Esquivalience 1909: 1906: 1905: 1897: 1893: 1889: 1885: 1882: 1880: 1877: 1872: 1867: 1860: 1856: 1851: 1848: 1846: 1842: 1838: 1834: 1831: 1829: 1825: 1821: 1816: 1813: 1807: 1801: 1799: 1792: 1790: 1783: 1782: 1781: 1777: 1773: 1769: 1766: 1762: 1761: 1760: 1754: 1752: 1745: 1743: 1736: 1733: 1731: 1727: 1723: 1719: 1715: 1711: 1708: 1706: 1702: 1698: 1693: 1690: 1688: 1684: 1680: 1676: 1673: 1671: 1667: 1663: 1659: 1655: 1652: 1650: 1646: 1642: 1638: 1635: 1633: 1629: 1627: 1619: 1614: 1611: 1609: 1605: 1601: 1596: 1593: 1591: 1586: 1580: 1576: 1572: 1568: 1565: 1563: 1559: 1555: 1550: 1547: 1543: 1539: 1535: 1531: 1528: 1527: 1526: 1522: 1518: 1514: 1511: 1509: 1505: 1501: 1496: 1492: 1489: 1487: 1483: 1479: 1474: 1471: 1465: 1461: 1457: 1452: 1451: 1450: 1447: 1441: 1436: 1435: 1434: 1430: 1426: 1421: 1418: 1416: 1412: 1408: 1404: 1401: 1399: 1396: 1390: 1387: 1385: 1381: 1377: 1373: 1369: 1365: 1362: 1360: 1356: 1352: 1347: 1344: 1342: 1338: 1334: 1329: 1326: 1324: 1320: 1316: 1315:SteveStrummer 1312: 1309: 1307: 1303: 1299: 1295: 1290: 1287: 1285: 1281: 1277: 1272: 1269: 1267: 1263: 1259: 1255: 1252: 1250: 1246: 1242: 1238: 1235: 1233: 1229: 1225: 1224: 1220: 1215: 1211: 1208: 1206: 1203: 1200: 1196: 1192: 1183: 1179: 1176: 1174: 1170: 1166: 1162: 1158: 1154: 1151: 1149: 1145: 1141: 1137: 1133: 1129: 1125: 1121: 1118: 1114: 1108: 1102: 1094: 1093: 1092: 1088: 1084: 1079: 1076: 1074: 1070: 1066: 1062: 1059: 1057: 1054: 1049: 1043: 1040: 1038: 1034: 1030: 1026: 1023: 1021: 1017: 1014: 1011: 1008: 1005: 998: 997: 992: 988: 984: 980: 977: 975: 972: 968: 965: 963: 959: 955: 950: 947: 945: 941: 937: 932: 929: 927: 923: 919: 915: 912: 910: 904: 898: 890: 887: 885: 881: 877: 873: 870: 868: 864: 860: 856: 853: 851: 847: 843: 838: 834: 831: 829: 826: 821: 811: 801: 797: 793: 788: 784: 781: 779: 775: 771: 770:Vesuvius Dogg 767: 764: 762: 758: 754: 750: 747: 745: 741: 737: 736: 729: 726: 723: 719: 715: 711: 708: 706: 703: 701: 696: 693: 691: 687: 683: 678: 675: 671: 668: 665: 662: 657: 655: 654: 651: 648: 645: 641: 636: 629: 624: 621: 619: 611: 610: 609: 602: 601: 600: 597: 596: 593: 592: 585: 580: 579: 578: 573: 570: 568: 560: 559: 558: 551: 545: 540: 539: 538: 535: 534: 531: 530: 525: 522: 520: 516: 512: 507: 504: 502: 498: 494: 489: 486: 484: 480: 476: 469: 466: 464: 460: 456: 452: 447: 444: 442: 439: 437:Darwinian Ape 432: 428: 423: 420: 418: 414: 410: 406: 403: 401: 396: 395: 390: 389: 382: 378: 375: 373: 369: 365: 361: 356: 352: 349: 347: 343: 338: 334: 330: 327: 323: 317: 316: 310: 309: 308: 304: 300: 296: 293: 292: 286: 285: 281: 275: 273: 269: 261: 257: 254: 251: 247: 243: 239: 235: 231: 227: 224: 221: 218: 217: 211: 209: 205: 201: 197: 192: 190: 186: 182: 178: 174: 160: 156: 155: 152: 146: 145: 142: 136: 134: 127: 126: 124: 120: 110: 107: 103: 98: 94: 90: 89: 86: 83: 82: 81: 79: 73: 68: 65: 60: 58: 52: 44: 41: 35: 34: 25: 19: 10295: 10275: 10268: 10267: 10234: 10228: 10194: 10137: 10005: 10002: 9970: 9966: 9917: 9894: 9879:open channel 9878: 9869: 9852: 9795: 9667: 9661: 9608: 9602: 9550: 9529: 9508: 9499: 9457: 9380: 9376: 9372: 9358:its policies 9337: 9313: 9309: 9306: 9294: 9289: 9282: 9271: 9248: 9241: 9240: 9167: 9115: 9108: 9053: 9049: 9021: 9016: 9011: 9007: 9004:legitimately 9003: 9000: 8975: 8890:AE talk page 8887: 8879: 8873: 8872: 8849: 8842: 8841: 8802: 8784: 8755: 8752: 8748: 8726: 8708: 8693: 8667:WP:CONEXCEPT 8662: 8648: 8643: 8639: 8535: 8530: 8468: 8422: 8376: 8325: 8293: 8263: 8227: 8202: 8165: 8128: 8124: 8105: 8051: 8001: 7995: 7991: 7987: 7983: 7979: 7977: 7923: 7840: 7811: 7766: 7744: 7699: 7693: 7611: 7606: 7517:WP:UNPROTECT 7475:I've boldly 7413: 7409: 7374: 7367: 7366: 7357: 7338: 7296: 7289: 7288: 7283: 7275: 7183: 7176: 7175: 7154: 7037: 6980:page, too. – 6977: 6955: 6954: 6903: 6880: 6875: 6844:conversation 6778: 6706: 6663:Garden hoses 6624: 6620: 6612: 6574: 6547: 6540: 6539: 6530: 6522: 6511: 6499: 6486: 6429: 6409: 6345: 6308: 6307: 6280: 6263: 6246: 6188: 6187: 6156: 6118: 6110: 6109: 6098: 6093: 6072: 6055: 6036: 6032: 6012: 6007: 5990: 5973: 5956: 5939: 5922: 5894: 5873: 5815: 5808: 5807: 5745: 5733:JamesBWatson 5727: 5722: 5703: 5699: 5682: 5665: 5647: 5633: 5629: 5624: 5619: 5602: 5590:VarunFEB2003 5585: 5559: 5538: 5516: 5499: 5468: 5463: 5456:WP:CONEXCEPT 5450: 5433:Carl Fredrik 5415: 5395: 5376: 5360:Carl Fredrik 5354: 5337: 5332: 5314: 5297: 5280: 5262: 5252:FenixFeather 5251: 5250: 5244:Taylor Swift 5239: 5226: 5221: 5211: 5192: 5145: 5144: 5132:Foreignshore 5129: 5124: 5119: 5102: 5085: 5067: 5061: 5022: 5016: 5010: 4991: 4965: 4954:Weak Support 4953: 4937: 4914: 4910: 4893: 4878: 4861: 4841: 4826: 4817: 4805: 4788: 4770: 4758: 4736: 4719: 4708: 4700: 4694: 4677: 4664: 4663: 4658: 4640: 4623: 4611: 4594: 4590: 4581: 4574: 4561: 4543: 4521: 4514: 4513: 4474: 4463: 4447: 4440: 4439: 4434: 4430: 4427:Weak support 4426: 4409: 4394: 4377: 4360: 4334:Newbiepedian 4329: 4312: 4298: 4297: 4290: 4275: 4274: 4273:, not less. 4270: 4266: 4257: 4252: 4249: 4247: 4245: 4238: 4221: 4200: 4183: 4171: 4163: 4152: 4145: 4123: 4117: 4095: 4091: 4081: 4080: 4075: 4065: 4053:Challenger l 4048: 4031: 4007: 3992: 3975: 3958: 3928: 3903: 3886: 3864: 3852: 3841: 3837: 3820: 3808: 3797: 3780: 3779: 3774: 3767: 3754:Patar knight 3749: 3716: 3700: 3683: 3664:open channel 3663: 3654: 3649: 3630:MjolnirPants 3629: 3621: 3604: 3586: 3573: 3568: 3548: 3541: 3540: 3497: 3466: 3447: 3425: 3408: 3398: 3392: 3389: 3386: 3383: 3380: 3377: 3372: 3351: 3336: 3332: 3314: 3296: 3282: 3269: 3265: 3255: 3244: 3232: 3216: 3211:Weak Support 3210: 3189: 3173: 3169: 3156:Class455fan1 3154: 3150: 3133: 3109: 3086: 3077: 3076: 3071: 3066: 3043: 3031: 3027: 3010: 2998: 2992: 2973: 2957:Weak support 2956: 2946: 2938: 2918: 2898: 2888: 2882:☾Loriendrew☽ 2876: 2862: 2858: 2846: 2840: 2819: 2802: 2785: 2768: 2756: 2739: 2720: 2707: 2706: 2701: 2675: 2656: 2651: 2639: 2627:Yellow Dingo 2622: 2604: 2586: 2583: 2568: 2548: 2531: 2510: 2492: 2488: 2476: 2457: 2444: 2423: 2414: 2396: 2392: 2373: 2356: 2339: 2335: 2298: 2281: 2242: 2234: 2219: 2215: 2205: 2199: 2198: 2192: 2191: 2185: 2173:DaltonCastle 2168: 2151: 2147: 2135: 2118: 2104: 2098: 2086:GELongstreet 2081: 2063: 2047: 2031: 2017: 1990: 1965: 1964: 1927: 1907: 1886:per Bilorv. 1883: 1858: 1854: 1849: 1832: 1814: 1798:open channel 1797: 1788: 1751:open channel 1750: 1741: 1734: 1717: 1709: 1691: 1674: 1657: 1653: 1636: 1623: 1612: 1594: 1566: 1548: 1529: 1512: 1490: 1472: 1439: 1419: 1402: 1388: 1371: 1367: 1363: 1345: 1327: 1310: 1294:Cobra effect 1288: 1270: 1253: 1236: 1222: 1218: 1209: 1194: 1177: 1152: 1119: 1077: 1060: 1041: 1029:Jjjjjjdddddd 1024: 1012: 1006: 994: 990: 982: 978: 971:Hexafluoride 966: 948: 930: 913: 888: 871: 854: 836: 832: 803: 799: 795: 791: 786: 782: 765: 748: 731: 727: 709: 694: 676: 639: 637: 614: 607: 606: 595: 590: 584:Andy M. Wang 563: 556: 555: 549: 533: 528: 523: 505: 487: 467: 446:Weak support 445: 426: 421: 404: 392: 386: 376: 350: 328: 314: 294: 276: 267: 265: 255: 233: 229: 225: 219: 203: 195: 193: 171: 132: 128: 122: 116: 115: 77: 74: 70: 63: 62: 56: 53: 49: 39: 36: 10165:MusikAnimal 10077:MusikAnimal 10051:MusikAnimal 10038:MusikAnimal 9832:Ian.thomson 9792:Observation 9437:Looking at 9173:Ian.thomson 9135:Ian.thomson 9120:Ian.thomson 9026:MediaKill13 8803:Mild oppose 8790:Juan Riley 8760:MediaKill13 8181:WP:BLUELOCK 8037:MusikAnimal 7960:MusikAnimal 7888:Ian.thomson 7857:Ian.thomson 7821:MusikAnimal 7776:MusikAnimal 7713:Cosmogoblin 7677:Cosmogoblin 7635:MusikAnimal 7567:MusikAnimal 7538:MusikAnimal 7525:MusikAnimal 7486:MusikAnimal 7450:MusikAnimal 7422:MusikAnimal 7038:suggestions 6912:Kingsindian 6659:Broomsticks 6652:Garden hose 6464:MusikAnimal 6448:Special:Log 6377:S Philbrick 6268:Max Semenik 6175:Atlantic306 5526:Ian.thomson 5400:Juan Riley 4701:Bellerophon 4498:MusikAnimal 4382:Binksternet 4365:Yamaguchi先生 4317:Staszek Lem 3865:SMcCandlish 3435:Vanamonde93 3123:MusikAnimal 2905:S Philbrick 2889:(ring-ring) 2659:Omni Flames 2378:Juan Riley 1679:Pianoman320 1575:Enterprisey 1534:Juan Riley 1500:cannywizard 1478:M. A. Bruhn 837:established 808:MediaKill13 661:Kingsindian 644:Kingsindian 591:OhanaUnited 544:OhanaUnited 529:OhanaUnited 427:experienced 133:HJ Mitchell 97:MusikAnimal 10249:BethNaught 9953:BethNaught 9749:Mr rnddude 9719:Mr rnddude 9697:there are 9695:Mr rnddude 9682:Mr rnddude 9346:the admin 9298:Soundblack 8453:Bots (bug) 8423:indefinite 7990:, so that 7788:Disgusting 7717:Greatedits 7436:Sir Joseph 7343:Sir Joseph 7267:Disgusting 7145:Biblioworm 6648:Broomstick 6430:Suggestion 6299:Discussion 6099:I JethroBT 5944:Xyzspaniel 5878:Jjamesryan 5856:Xxanthippe 5801:Xxanthippe 5785:Xxanthippe 5765:Xxanthippe 5750:Xxanthippe 5197:nyuszika7h 5189:Pocketthis 5165:nyuszika7h 5150:nyuszika7h 5107:Pocketthis 4898:VMS Mosaic 4866:R. S. Shaw 4810:Neutrality 4751:(Mrjulesd) 4709:talk to me 4599:Situphobos 4470:WP:AALERTS 4271:more harsh 4205:WP:NOTHERE 4100:Tom.Reding 3941:Ivanvector 3844:Whats new? 3574:Ritchie333 3360:Democratic 3356:Republican 3301:Xxanthippe 3224:parlez moi 3036:Randy Kryn 3032:Britannica 2705:failed. — 2361:nyuszika7h 2156:Tryptofish 1583:(formerly 1370:. This is 1276:BethNaught 1136:incumbency 1132:disgusting 700:Sir Joseph 238:stipulated 168:Background 159:WP:ECP2016 93:BethNaught 67:Committee. 10089:Blackmane 10058:Blackmane 9967:technical 9865:Agreed. 9803:TomStar81 9474:Blackmane 9404:Blackmane 9390:Blackmane 9348:Wordsmith 9231:Moved to 9199:Blackmane 9096:Blackmane 8945:Sepsis II 8908:Sepsis II 8832:Moved to 8650:Amaryllis 8080:Blackmane 8018:StevenJ81 7942:Blackmane 7722:I hope so 7616:Blackmane 7477:clarified 7463:Blackmane 7394:MartinZ02 7264:the page 7159:SPERTable 7155:very very 7151:EPERTable 6992:Blackmane 6929:Blackmane 6784:Blackmane 6750:Blackmane 6710:Blackmane 6687:again. — 6681:Shrubbery 6393:Blackmane 6329:Blackmane 6251:Bluehotel 6157:INeverCry 6132:INeverCry 6119:INeverCry 6078:Keysanger 5708:Dmforcier 5465:enforced. 5302:Wario-Man 5040:Edit-days 4974:Hijiri 88 4970:obviously 4916:Callanecc 4831:horizon51 4776:JayJasper 4646:Jrheller1 4226:Pokéfan95 4211:Montanabw 4153:INeverCry 3937:WP:ARBPIA 3802:Cas Liber 3688:MartinZ02 3457:reactions 3433:to help. 3198:Funcrunch 3015:Coemgenus 2828:GermanJoe 2807:SA 13 Bro 2536:Blackmane 2449:Lankiveil 2123:DrkBlueXG 1714:Gpapazian 1697:Gpapazian 1600:Dmforcier 1554:Woogie10w 1394:Full Rune 1331:reckless. 1212:- as per 1199:gracefool 1140:Andrew D. 876:StevenJ81 734:ONUnicorn 550:different 409:Thryduulf 299:Debresser 256:Option C: 226:Option B: 220:Option A: 187:recently 112:remarks). 64:Option C: 10263:WP:UPROT 10143:xaosflux 9799:new coke 9739:xaosflux 9714:Xaosflux 9705:xaosflux 9567:BU Rob13 8653:Gardener 8642:We have 8510:xaosflux 8476:xaosflux 7812:multiple 7793:DHeyward 7748:DHeyward 7612:just yet 7580:xaosflux 7556:Xaosflux 7545:xaosflux 7432:Pinging 7249:xaosflux 7137:Gladamas 7126:xaosflux 7111:xaosflux 7096:xaosflux 7081:xaosflux 6982:Gladamas 6956:Proposal 6690:xaosflux 6523:possibly 6483:Odysseus 6452:category 6450:and the 6434:— Maile 6357:Agreed. 6346:HighInBC 6313:— Maile 5886:contribs 5630:.paint ~ 5625:starship 5607:Tom (LT) 5573:Yaris678 5522:WP:UPROT 5504:Pincrete 5386:contribs 5185:Drdaviss 5045:Drdaviss 4997:Drdaviss 4925:contribs 4853:Chequers 4793:HGilbert 4577:SilkTork 4504:MusikBot 4491:BU Rob13 4342:contribs 4176:HighInBC 4036:Garzfoth 4012:Jkudlick 3933:WP:ARBGG 3919:contribs 3853:This one 3812:contribs 3275:Gladamas 3237:James086 3072:Thomas.W 2983:Mistakes 2961:— Maile 2847:HighInBC 2761:Armbrust 2744:Jclemens 2526:Option C 2516:IronDuke 2003:— Maile 1970:Jkudlick 1937:contribs 1902:Option B 1820:Carystus 1662:Reidgreg 1571:WP:CREEP 1124:WP:CREEP 983:anywhere 872:Support. 753:Catlemur 511:DHeyward 315:HighInBC 289:Option A 151:Shortcut 123:option C 10269:Andy W. 10213:Altamel 9870:Mlpearc 9648:Sethyre 9630:Sethyre 9242:Andy W. 9080:WP:RFPP 9072:WP:ANEW 9017:his/her 8883:example 8843:Andy W. 8808:Felisse 8672:userbox 8198:June 30 8161:WP:SEMI 7988:proviso 7980:finding 7920:Removal 7807:example 7763:options 7503:Altamel 7469:, and 7467:Altamel 7368:Andy W. 7354:protect 7290:Andy W. 7177:Andy W. 7143:, and 7091:6 pages 7042:Be bold 6861:Altamel 6799:Altamel 6764:Altamel 6627:Altamel 6541:Andy W. 6525:(!AGF) 6415:Altamel 6360:Timothy 6281:Support 6264:Support 6247:Support 6216:Altamel 6189:Support 6140:Altamel 6111:Support 6094:Support 6073:Support 6056:Support 6033:Support 6008:Support 5995:Baldusi 5991:Support 5974:Support 5961:Carrite 5957:Support 5940:Support 5923:Support 5895:Support 5874:Support 5809:Andy W. 5771:Altamel 5746:Support 5723:Support 5683:Support 5666:Support 5648:Support 5620:Support 5603:Support 5560:Support 5539:Support 5517:Support 5500:Support 5377:Support 5355:Support 5333:Support 5315:Support 5298:Support 5285:Rlendog 5281:Support 5263:Support 5240:Support 5212:Support 5191:says (" 5181:sleeper 5146:Support 5120:Support 5103:Support 5090:Kiltpin 5086:Support 4992:Support 4966:Support 4938:Support 4911:Support 4894:Support 4879:Support 4862:Support 4818:Support 4806:Support 4789:Support 4771:Support 4759:Support 4747:--Jules 4737:Support 4720:Support 4695:Support 4682:Qweedsa 4678:Support 4667:Hut 8.5 4659:Support 4641:Support 4624:Support 4612:Support 4591:Support 4562:Support 4544:Support 4515:Andy W. 4441:Andy W. 4410:Support 4395:Support 4378:Support 4361:Support 4330:Support 4313:Support 4291:Support 4246:Patient 4201:Support 4168:WP:RFPP 4164:Support 4146:Support 4092:Support 4076:Muffled 4066:Support 4049:Support 4032:Support 4008:Support 3993:Support 3976:Support 3959:Support 3929:Support 3909:Elmidae 3904:Support 3891:Amakuru 3887:Support 3838:Support 3821:Support 3798:Support 3768:Support 3750:Support 3717:Support 3701:Support 3684:Support 3655:Mlpearc 3622:Support 3605:Support 3592:Mamyles 3587:Support 3569:Support 3542:Andy W. 3467:Support 3448:Support 3426:Support 3409:Support 3373:Support 3352:Support 3333:Support 3315:Support 3297:Support 3287:SarahSV 3283:Support 3266:Support 3245:Support 3233:Support 3190:Support 3170:Support 3151:Support 3134:Support 3110:Support 3091:WP:MVPs 3067:Support 3044:Support 3028:Support 3011:Support 2993:Support 2974:Support 2943:WP:RFPP 2939:Support 2919:Support 2899:Support 2877:Support 2859:Support 2841:Support 2824:WP:RfPP 2820:Support 2803:Support 2786:Support 2769:Support 2757:Support 2740:Support 2721:Support 2702:Support 2652:Support 2640:Support 2623:Support 2605:Support 2584:Support 2573:Cameron 2569:Support 2554:Timothy 2549:Support 2532:Support 2511:Support 2489:Support 2477:Support 2458:Support 2445:Support 2415:Support 2402:MSJapan 2393:Support 2357:Support 2286:Kierzek 2282:Support 2271:Tigraan 2235:Support 2216:Support 2186:Support 2169:Support 2148:Support 2136:Support 2119:Support 2099:Support 2082:Support 2064:Support 2022:Maile66 2018:Support 1966:Support 1952:Jenks24 1928:Support 1908:Support 1884:Support 1850:Support 1833:Support 1815:Support 1789:Mlpearc 1772:Altamel 1765:Mlpearc 1742:Mlpearc 1710:Support 1692:Support 1675:Support 1654:Support 1637:Support 1613:Support 1595:Support 1585:APerson 1567:Support 1549:Support 1517:Phiselm 1513:Support 1491:Support 1473:Support 1456:Jhugh95 1425:Jhugh95 1403:support 1389:Support 1364:Support 1351:Amaurea 1346:Support 1328:Support 1311:Support 1289:Support 1271:Support 1258:Iazyges 1254:Support 1237:Support 1210:Support 1178:Support 1153:Support 1120:Support 1078:Support 1061:Support 1042:Support 1025:Support 987:Altamel 979:Support 967:Support 949:Support 931:Support 918:Gimubrc 914:Support 889:Support 855:Support 833:Support 783:Support 766:Support 749:Support 728:Support 710:Support 695:Support 677:Support 640:Support 608:Andy W. 557:Andy W. 524:Support 506:Support 493:Felisse 488:Support 468:Support 422:Support 405:Support 364:Altamel 351:Support 329:Support 295:Support 214:Options 10236:(talk) 10230:Bilorv 10010:Biblio 9976:Biblio 9934:Biblio 9847:Ahecht 9669:(talk) 9663:Bilorv 9524:WP:ECP 9161:WP:LTA 9092:WP:LTA 9084:WP:ANI 9076:WP:AIV 8749:Oppose 8727:Oppose 8709:Oppose 8694:Oppose 8676:Biblio 8663:Oppose 8640:Oppose 8536:Oppose 8469:(c.f. 8421:under 8417:, and 8300:Biblio 8234:Biblio 7767:except 7701:(talk) 7695:Bilorv 7671:faith. 7046:Biblio 6881:anyone 6616:bitten 6382:(Talk) 6363:Joseph 6013:Xymmax 5899:Laber□ 5700:Oppose 5657:(talk) 5654:Toddy1 5547:moreno 5545:David. 5396:Oppose 5345:Verbum 5069:(talk) 5063:Bilorv 5036:Bilorv 5024:(talk) 5018:Bilorv 4726:Adrian 4549:Tamwin 4402:(Talk) 4305:(talk) 4070:WP:RFA 3997:Deryck 3825:Taketa 3609:Mizike 3532:, and 3503:Aoziwe 3482:Aoziwe 3338:Graham 3250:Slight 3115:WP:IAR 2925:Kieran 2910:(Talk) 2730:ASTILY 2610:Majora 2592:KaisaL 2557:Joseph 2498:Iamozy 2481:Aunva6 2420:WP:RFP 2374:Oppose 2247:minors 2243:reduce 2152:before 2026:WP:SPI 1995:WP:RFP 1991:Oppose 1932:IJBall 1888:4nn1l2 1859:except 1718:anyone 1641:OMouse 1618:Ahecht 1569:, per 1530:Oppose 1128:WP:NVC 954:A2soup 936:UiLego 842:Mangoe 792:months 431:biting 394:(talk) 388:Bilorv 355:Biblio 333:Biblio 10116:WP:AN 10105:Katie 9971:class 9764:Bilby 9732:here: 9626:Bilby 9603:least 9571:NeilN 9504:NeilN 9443:Bilby 9384:with. 9353:owned 9290:never 9088:WP:AN 8599:Godsy 8332:talk 8281:Katie 8230:Dps04 8187:Katie 8151:Katie 8146:WP:PP 8069:Katie 7805:Your 7276:still 7027:Katie 6779:first 6596:Katie 6060:Zezen 5381:James 5324:talk. 5011:could 4849:Spiel 4828:Event 3518:Yes, 3256:Smile 3219:slava 3097:: --> 3096:: --> 2930:Tribe 2790:Nsk92 2644:MER-C 2575:11598 2226:talk 1999:WP:SI 1579:talk! 1407:Hobit 1223:uture 1100:Godsy 1065:Dps04 1052:flyer 996:Kevin 896:Godsy 682:Bilby 353:. As 280:Katie 198:(per 16:< 10278:talk 10265:. — 10253:talk 10217:talk 10202:talk 10138:must 10124:talk 10093:talk 10062:talk 10014:talk 10006:some 9980:talk 9957:talk 9938:talk 9855:PAGE 9853:TALK 9836:talk 9822:talk 9807:Talk 9768:talk 9753:talk 9723:talk 9686:talk 9634:talk 9582:talk 9569:and 9530:Neil 9500:only 9478:talk 9447:talk 9408:talk 9394:talk 9251:talk 9203:talk 9177:talk 9168:does 9124:talk 9100:talk 9061:talk 9036:talk 8993:talk 8949:talk 8912:talk 8852:talk 8812:talk 8794:talk 8770:talk 8739:talk 8729:per 8718:talk 8714:Hftf 8680:talk 8623:talk 8605:CONT 8579:talk 8544:talk 8495:talk 8431:talk 8401:talk 8359:talk 8304:talk 8295:ECP. 8259:Rdiw 8255:Widr 8238:talk 8084:talk 8058:Talk 8022:talk 8008:Talk 7946:talk 7928:Mkdw 7892:talk 7861:talk 7797:talk 7752:talk 7681:talk 7656:talk 7620:talk 7507:talk 7438:and 7398:talk 7377:talk 7299:talk 7284:just 7186:talk 7108:. — 7093:. — 7050:talk 7014:and 6996:talk 6978:that 6933:talk 6889:talk 6865:talk 6824:ASEM 6803:talk 6788:talk 6768:talk 6754:talk 6714:talk 6685:Path 6683:and 6661:and 6650:and 6631:talk 6550:talk 6438:talk 6419:talk 6397:talk 6366:Wood 6333:talk 6317:talk 6289:talk 6272:talk 6255:talk 6234:talk 6220:talk 6197:talk 6179:talk 6144:talk 6083:talk 6064:talk 6045:coxn 5999:talk 5982:talk 5965:talk 5948:talk 5931:talk 5912:talk 5882:talk 5860:talk 5845:talk 5818:talk 5789:talk 5775:talk 5754:talk 5737:talk 5712:talk 5674:talk 5611:talk 5594:talk 5577:talk 5530:talk 5508:talk 5483:talk 5451:very 5404:talk 5320:AYTK 5306:talk 5289:talk 5272:talk 5268:PGWG 5227:olta 5201:talk 5169:talk 5154:talk 5136:talk 5125:some 5111:talk 5094:talk 5049:talk 5034:Yes 5001:talk 4946:Zero 4929:logs 4921:talk 4902:talk 4870:talk 4844:Ϣere 4797:talk 4780:talk 4686:talk 4650:talk 4632:talk 4603:talk 4595:only 4593:but 4553:talk 4524:talk 4472:? ~ 4450:talk 4418:talk 4386:talk 4369:talk 4352:logs 4338:talk 4321:talk 4299:corn 4250:Zero 4230:talk 4192:talk 4184:semi 4172:must 4136:Talk 4108:dgaf 4104:talk 4057:talk 4040:talk 3984:talk 3967:talk 3950:talk 3935:and 3915:talk 3895:talk 3829:talk 3806:talk 3781:warm 3723:QEDK 3706:Mkdw 3692:talk 3613:talk 3596:talk 3551:talk 3507:talk 3486:talk 3452:shoy 3439:talk 3417:talk 3399:TALK 3358:and 3324:talk 3305:talk 3217:Dsch 3202:talk 3181:7754 3178:chen 3160:talk 3142:talk 3101:talk 3056:talk 3019:talk 2965:talk 2948:Ruud 2863:only 2832:talk 2811:talk 2794:talk 2777:talk 2773:DVdm 2748:talk 2687:Rebb 2665:talk 2631:talk 2614:talk 2596:talk 2560:Wood 2540:talk 2502:talk 2491:and 2466:Tito 2433:Ayub 2406:talk 2382:talk 2365:talk 2348:talk 2326:talk 2311:talk 2290:talk 2177:talk 2160:talk 2127:talk 2105:Crow 2090:talk 2073:talk 2007:talk 1956:talk 1941:talk 1918:talk 1892:talk 1841:talk 1824:talk 1776:talk 1726:talk 1712:per 1701:talk 1683:talk 1666:talk 1660:. - 1645:talk 1626:PAGE 1624:TALK 1604:talk 1558:talk 1538:talk 1521:talk 1504:talk 1482:talk 1460:talk 1429:talk 1411:talk 1380:talk 1355:talk 1337:talk 1319:talk 1302:talk 1280:talk 1262:talk 1245:talk 1228:talk 1169:talk 1159:for 1144:talk 1126:and 1122:per 1106:CONT 1087:talk 1083:Hftf 1069:talk 1033:talk 1004:L235 958:talk 940:talk 922:talk 902:CONT 880:talk 863:talk 846:talk 818:talk 774:talk 757:talk 718:talk 686:talk 617:talk 566:talk 515:talk 497:talk 474:ASEM 459:talk 413:talk 368:talk 337:talk 303:talk 244:and 240:for 232:for 10284:ctb 10120:Mz7 9918:Rob 9895:Rob 9609:Rob 9551:Rob 9509:Rob 9314:Rob 9257:ctb 9086:or 9012:200 8858:ctb 8644:far 8590:Mz7 8575:Mz7 8377:Rob 8327:DGG 8264:Rob 8203:Rob 8166:Rob 8129:Rob 8106:Rob 7383:ctb 7358:own 7305:ctb 7192:ctb 6876:and 6575:Rob 6556:ctb 6531:500 5824:ctb 5735:" ( 5687:-- 5479:Mz7 5416:Rob 5340:Pax 5222:Red 4616:GAB 4530:ctb 4475:Rob 4456:ctb 4295:AIR 4124:crh 3879:ⱷ≼ 3875:≽ⱷ҅ 3842:-- 3756:- / 3557:ctb 3365:JFG 2999:ERK 2692:ing 2587:But 2462:SPI 2436:407 2397:not 2221:DGG 2206:com 2048:Rob 2032:Rob 1440:Rob 1376:LjL 1333:War 1296:.) 1241:Adh 1047:SST 1001:aka 798:or 787:any 623:ctb 572:ctb 455:Mz7 10255:) 10227:— 10219:) 10204:) 10161:— 10126:) 10118:. 10095:) 10073:— 10064:) 10034:— 10016:) 9982:) 9959:) 9940:) 9922:13 9899:13 9859:) 9838:) 9824:) 9809:) 9770:) 9755:) 9725:) 9688:) 9660:— 9636:) 9613:13 9584:) 9555:13 9513:13 9480:) 9449:) 9410:) 9396:) 9373:is 9318:13 9238:— 9236:– 9205:) 9179:) 9126:) 9116:if 9102:) 9082:, 9078:, 9074:, 9063:) 8995:) 8951:) 8914:) 8839:— 8837:– 8814:) 8796:) 8741:) 8733:. 8720:) 8682:) 8674:. 8665:. 8625:) 8581:) 8546:) 8501:) 8497:, 8433:) 8413:, 8403:) 8381:13 8334:) 8306:) 8268:13 8240:) 8207:13 8170:13 8133:13 8110:13 8086:) 8056:| 8033:— 8024:) 8006:| 7992:if 7956:— 7948:) 7894:) 7874:. 7863:) 7817:— 7799:) 7772:— 7754:) 7724:| 7692:— 7683:) 7658:) 7631:— 7622:) 7563:— 7521:— 7509:) 7482:— 7465:, 7446:— 7418:— 7400:) 7231:) 7173:— 7169:}} 7165:{{ 7139:, 7072:}} 7066:{{ 7052:) 7040:. 7022:}} 7016:{{ 7012:}} 7006:{{ 6998:) 6966:}} 6960:{{ 6935:) 6891:) 6867:) 6831:) 6805:) 6790:) 6770:) 6756:) 6716:) 6633:) 6579:13 6521:, 6517:, 6460:— 6440:) 6421:) 6399:) 6335:) 6319:) 6291:) 6274:) 6257:) 6236:) 6222:) 6214:. 6210:: 6199:) 6181:) 6146:) 6138:. 6134:: 6066:) 6049:\ 6001:) 5984:) 5967:) 5950:) 5933:) 5914:) 5888:) 5884:| 5862:) 5847:) 5795:. 5791:) 5777:) 5760:. 5756:) 5739:) 5714:) 5676:) 5637:KO 5613:) 5596:) 5588:- 5579:) 5549:72 5532:) 5510:) 5485:) 5441:📧 5438:💌 5420:13 5406:) 5389:) 5383:(/ 5368:📧 5365:💌 5308:) 5291:) 5274:) 5232:📱 5203:) 5171:) 5156:) 5138:) 5113:) 5096:) 5060:— 5051:) 5015:— 5003:) 4985:) 4982:やや 4931:) 4927:• 4923:• 4904:) 4872:) 4799:) 4782:) 4688:) 4652:) 4634:) 4605:) 4573:. 4555:) 4511:— 4479:13 4437:— 4420:) 4388:) 4371:) 4354:) 4350:· 4347:X! 4344:· 4340:· 4323:) 4242:-- 4232:) 4194:) 4128:23 4059:) 4042:) 4022:• 4018:• 4014:• 4000:C. 3986:) 3969:) 3952:) 3945:🍁 3917:· 3897:) 3862:— 3857:or 3831:) 3814:) 3694:) 3615:) 3598:) 3538:— 3528:, 3526:}} 3520:{{ 3509:) 3488:) 3477:}} 3471:{{ 3441:) 3419:) 3387:ge 3343:87 3326:) 3307:) 3204:) 3196:. 3175:Rs 3144:) 3119:— 3103:) 3021:) 2986:) 2980:(| 2967:) 2834:) 2813:) 2796:) 2779:) 2750:) 2633:) 2616:) 2598:) 2542:) 2504:) 2468:xd 2408:) 2384:) 2367:) 2350:) 2334:I 2328:) 2313:) 2292:) 2228:) 2200:it 2193:Br 2179:) 2162:) 2129:) 2092:) 2075:) 2052:13 2036:13 2009:) 1980:• 1976:• 1972:• 1958:) 1939:• 1912:— 1894:) 1875:is 1870:ll 1865:Ne 1855:as 1843:) 1826:) 1778:) 1728:) 1703:) 1685:) 1668:) 1647:) 1630:) 1616:-- 1606:) 1581:) 1560:) 1540:) 1523:) 1506:) 1484:) 1462:) 1444:13 1431:) 1413:) 1382:) 1357:) 1339:) 1321:) 1304:) 1282:) 1264:) 1247:) 1230:) 1221:ix 1202:💬 1195:be 1171:) 1146:) 1089:) 1071:) 1035:) 1018:) 960:) 942:) 924:) 882:) 865:) 848:) 776:) 759:) 720:) 688:) 553:— 517:) 499:) 481:) 461:) 415:) 385:— 370:) 339:) 305:) 260:AN 250:AN 230:or 137:| 59:: 10286:) 10281:· 10274:( 10251:( 10215:( 10200:( 10122:( 10091:( 10060:( 10053:: 10049:@ 10012:( 9978:( 9955:( 9936:( 9883:) 9875:( 9849:( 9834:( 9820:( 9805:( 9766:( 9751:( 9721:( 9684:( 9650:: 9646:@ 9632:( 9580:( 9573:: 9565:@ 9546:: 9542:@ 9532:N 9476:( 9445:( 9406:( 9392:( 9259:) 9254:· 9247:( 9201:( 9175:( 9137:: 9133:@ 9122:( 9098:( 9059:( 9040:) 9032:( 9008:C 8991:( 8947:( 8910:( 8860:) 8855:· 8848:( 8810:( 8792:( 8774:) 8766:( 8753:A 8745:. 8737:( 8716:( 8678:( 8621:( 8608:) 8596:— 8592:: 8588:@ 8577:( 8559:: 8555:@ 8542:( 8493:( 8489:. 8429:( 8399:( 8362:) 8356:( 8330:( 8302:( 8236:( 8082:( 8020:( 7944:( 7890:( 7859:( 7795:( 7750:( 7728:) 7720:( 7679:( 7654:( 7618:( 7603:) 7599:( 7558:: 7554:@ 7540:: 7536:@ 7505:( 7473:: 7461:@ 7442:: 7434:@ 7396:( 7385:) 7380:· 7373:( 7307:) 7302:· 7295:( 7262:: 7258:@ 7227:( 7194:) 7189:· 7182:( 7147:: 7135:@ 7048:( 6994:( 6931:( 6918:♚ 6915:♝ 6887:( 6863:( 6829:t 6827:( 6822:M 6801:( 6786:( 6766:( 6752:( 6746:: 6742:@ 6712:( 6629:( 6558:) 6553:· 6546:( 6501:9 6494:7 6491:4 6488:1 6436:( 6417:( 6395:( 6331:( 6315:( 6287:( 6270:( 6253:( 6232:( 6218:( 6206:@ 6195:( 6177:( 6142:( 6130:@ 6085:) 6081:( 6062:( 6042:u 6039:t 5997:( 5980:( 5963:( 5946:( 5929:( 5910:( 5880:( 5866:. 5858:( 5843:( 5826:) 5821:· 5814:( 5803:: 5799:@ 5787:( 5773:( 5763:@ 5752:( 5731:" 5710:( 5704:a 5672:( 5609:( 5592:( 5575:( 5528:( 5506:( 5481:( 5402:( 5304:( 5287:( 5270:( 5199:( 5167:( 5152:( 5134:( 5109:( 5092:( 5047:( 4999:( 4979:聖 4976:( 4919:( 4900:( 4886:P 4883:T 4868:( 4795:( 4778:( 4684:( 4648:( 4630:( 4601:( 4551:( 4532:) 4527:· 4520:( 4493:: 4489:@ 4458:) 4453:· 4446:( 4416:( 4384:( 4367:( 4336:( 4319:( 4228:( 4190:( 4138:) 4134:( 4110:) 4106:⋅ 4102:( 4096:~ 4055:( 4038:( 4024:s 4020:c 4016:t 3982:( 3965:( 3948:( 3921:) 3913:( 3893:( 3877:ᴥ 3873:¢ 3870:☏ 3867:☺ 3827:( 3809:· 3804:( 3789:♠ 3775:S 3741:) 3738:C 3734:☕ 3730:T 3727:( 3690:( 3668:) 3660:( 3611:( 3594:( 3559:) 3554:· 3547:( 3505:( 3484:( 3459:) 3455:( 3437:( 3415:( 3393:s 3390:r 3384:g 3381:a 3378:W 3322:( 3311:. 3303:( 3273:– 3200:( 3162:) 3158:( 3140:( 3099:( 3059:) 3053:( 3017:( 2963:( 2887:☏ 2830:( 2809:( 2792:( 2775:( 2746:( 2727:F 2668:) 2662:( 2629:( 2612:( 2594:( 2538:( 2500:( 2454:. 2404:( 2380:( 2363:( 2346:( 2324:( 2309:( 2288:( 2224:( 2175:( 2158:( 2125:( 2088:( 2071:( 2005:( 1982:s 1978:c 1974:t 1954:( 1943:) 1935:( 1920:) 1916:( 1890:( 1839:( 1822:( 1802:) 1794:( 1774:( 1763:@ 1755:) 1747:( 1724:( 1699:( 1681:( 1664:( 1643:( 1620:( 1602:( 1587:) 1577:( 1556:( 1536:( 1519:( 1502:( 1480:( 1458:( 1427:( 1409:( 1378:( 1353:( 1335:( 1317:( 1300:( 1278:( 1260:( 1243:( 1226:( 1219:F 1167:( 1142:( 1109:) 1097:— 1085:( 1067:( 1031:( 1016:c 1013:· 1010:t 1007:· 999:( 956:( 938:( 920:( 905:) 893:— 878:( 861:( 844:( 822:) 814:( 800:C 796:B 772:( 755:( 724:. 716:( 684:( 667:♚ 664:♝ 650:♚ 647:♝ 638:# 625:) 620:· 613:( 586:: 582:@ 574:) 569:· 562:( 546:: 542:@ 513:( 495:( 479:t 477:( 472:M 457:( 411:( 366:( 335:( 301:( 129:— 26:)

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

Knowledge

:Requests for comment/Extended confirmed protection policy - Knowledge

Index