Wikipedia talk:Requests for adminship/Archive 105

message: As the statistics from the wannabe_kate tool is posted on each RfA's discussion page, is it possible to get this automatically done, or is that too much of a hassle. (Probably is, if it is just a quick task, and there *aren't* that many RfAs.) Also, is there a quick way to do it, as I find if I just copy and paste the statistics, it does not leave a sufficient gap between the number and what it is referring to, and I have to go through and Tab to get a space in between. Phgao 06:46, 19 September 2007 (UTC)
replies: text: I get the feeling mathbot could do it if we really asked nicely - he already adds the ESU link. Dihydrogen Monoxide (H2O) 07:33, 19 September 2007 (UTC)
replies: text: Another thing, what is admin revert? ( you mentioned it on a RfA) Phgao 09:20, 19 September 2007 (UTC)
replies: text: An admin revert or "rollback" is when an admin clicks a link and it reverts the edit on the server. Unlike a user script such as twinkle which edits the previous version, a rollback is a separate server command rather than an edit that has the same effect. It's marginally faster than twinkle or popups, and leaves an automatic summary, but there's nothing really special about it considering popups and twinkle especially. Oh and it also undoes all of the edits by the last user until the previous user. So I made 3 edits to a page then someone clicked rollback it would undo all 3 of my edits. James086Talk | Email 09:27, 19 September 2007 (UTC)
replies: text: Also, it's possible to do a rollback in such a way that neither the rollback nor the edits it reverts show up in Recent Changes; this is hardly ever used (its only purpose is to restore Recent Changes from a flood attack). --ais523 13:10, 19 September 2007 (UTC)

text: I just do it by hand; it's not that hard. Kids these days and their bots and their automated tools and their rock and roll... why, back when I was a boy, if somebody twinkled an article, we'd block 'em! Damn whippersnappers... EVula // talk // ☯ // 19:27, 19 September 2007 (UTC)
replies: text: And get off my lawn. Raymond Arritt 20:31, 19 September 2007 (UTC)
replies: text:  :D Indeed, I prefer to do RC patrol by hand as well, although tagging for CSD is done using twinkle! Phgao 05:56, 20 September 2007 (UTC)
replies: text: <EVula> You mean I'm not the only one who does RC patrol (and everything else) by hand? :) Shalom Hello 17:57, 20 September 2007 (UTC)
replies: text:  Not me! I patrol RC with AVT, then rollback with twinkle! It's all about the scriptage, baby! J-ſtanTalkContribs 18:56, 20 September 2007 (UTC)

text: The closest thing I come to an automated editing tool is the rollback feature. :) EVula // talk // ☯ // 18:58, 20 September 2007 (UTC)
replies: text:  Which is uncool :) J-ſtanTalkContribs 02:30, 21 September 2007 (UTC)
replies: text:  Which is faster, as well, as I don't have to wait for all the javascript junk to load... yeah, I'm an old fart, apparently, but there's nothing like the good old days. Back then, we would scroll the RC feed by hand, and we wouldn't have any of the fairy stuff these kids have today. Back when I was your age, we would actually stand side-by-side cleaning up with the mop and the flamethrower, and have a drink while getting warm over a bonfire in quiet nights... ah, the good old days. Too bad that the kids of today don't know anything about that, they just use whatever script thingie is cooler and they go on their merry way. They don't know what life truly is, I'm telling you. Titoxd(?!? - cool stuff) 08:01, 21 September 2007 (UTC)
thread_title:  Discussion Page 

message: I propose that bureaucratship as a special status should be abolished, and all administrators should be given bureaucrat tools in addition to their admin tools. I have several arguments in favour of this proposal.
*Firstly, it already works this way on many other wikis, notably Spanish Wikipedia. They have not experienced any problems as a result of this situation, and (AFAIK) there are no proposals over there to change to our system. I realise their wiki is smaller; however, a larger wiki is all the more reason not to concentrate power in the hands of a small group.
*I realise many people will argue that a rogue 'crat account can do much more damage than a rogue admin account, so the position has to be exclusive. However, I don't think the RfB process necessarily helps in this regard. In general, anyone who passes RfA is already a trusted user, and gives the impression of being sane and balanced; someone who can fool the community into thinking they're trustworthy enough to pass an RfA is likely to be able to do exactly the same thing on an RfB. Furthermore, the Essjay incident shows that we can, and do, promote people to bureaucratship without being 100% certain of their trustworthiness, just as we do for adminship. So the argument that RfB helps avoid rogue 'crat accounts doesn't hold water.
*People often argue that only the 'crats can determine "consensus" on a controversial RfA (see this post made by a current bureaucrat). However, I disagree with this. Administrators already close XfDs and other community discussions, and we are trusted with discretionary authority in sensitive areas such as page protection and blocking users. Anyone who is trustworthy and intelligent enough to perform admin duties, is trustworthy and intelligent enough to close RfAs.
*It is also a well-publicised fact that standards for adminship now on English Wikipedia are higher than they used to be, and higher than on most other wikis. Thus, if Spanish Wikipedia admins (and their counterparts on many other projects) can automatically be trusted with the 'crat tools, then why can't we be?
I realise this proposal has been brought up in the past, and failed. However, consensus can change, and I hope the community will read my arguments and take note of the compelling reasons why we should do this. WaltonOne 18:48, 20 September 2007 (UTC)
replies: text: Weak oppose. Sounds like a good idea (I too have made a proposal dealing with crats, though not in the same way), but we need to have a much higher sense of trust in these users at RfB, higher than at RfA. I feel that if we abolish Bureaucratship, standards for RfA will skyrocket, and a lot of good users who deserve to have the mop and bucket won't get it because it comes with the wrenches. J-ſtanTalkContribs 19:03, 20 September 2007 (UTC)

text: I think that, for a proposal like this to work, we'd need to also implement an easier system for de-adminship. (not saying that I disagree with you on any particular point, I'm just saying that I don't think it'd get community support without an easier system of checks and balances) EVula // talk // ☯ // 19:09, 20 September 2007 (UTC)

text: I strongly oppose this proposal. There's only been a handful of bureaucrats promoted in the past year or two. There's obviously not consensus to create any more crats than needed (the exact number is frequently debated). While it may work well on the Spanish Wikipedia, I highly doubt it would scale to a project this large. The main effect of this proposal would be to make it virtually impossible to become an admin. Chaz Beckett 19:15, 20 September 2007 (UTC)

text: Haven't you proposed this before? Anyway, this would cause RFA standards to raise. As much as you can argue that it really shouldn't (and I agree with that), the practicality is that it would. So we'd end up with really high adminship standards, basically solving nothing (not that I think there's anything to solve anyway). --Deskana (talk) 19:16, 20 September 2007 (UTC)
replies: text: Here's an idea. Put in an RFB for every administrator. Something like Wikipedia:Requests for bureaucratship/All administrators. Incase anyone can't tell, I am actually being serious. --Deskana (talk) 19:20, 20 September 2007 (UTC)
replies: text: Do you mean have a vote (OK, !vote) on them as a whole, or work through the 1300 saying yes or no to each? BTW, if Wikipedia:Requests for adminship/Penwhale stays the same it will have exactly 75% support, so we'll get to test 'crat discretion in its purest form —  iridescent (talk to me!) 19:27, 20 September 2007 (UTC)
replies: text: One for all admins. That's the way to promote all users to admins. It'd never pass, which makes the communities views on promoting all admins to bureaucrats pretty obvious. --Deskana (talk) 19:29, 20 September 2007 (UTC)

text: Uhh, no. The big problems is that if admins can give admin bits, then some guy goes nuts and gives Willy on Wheels the admin bit, and he gives it to every vandal on AIV, and on and on. It is not about a special type of person. The separation exists you can give someone access, without giving the ability to give other people access. It is not about classes of people, it is about security. ((1 == 2) ? (('Stop') : ('Go')) 19:56, 20 September 2007 (UTC)
replies: text: I agree with 1 == 2 here. Anything an admin can be done can be reverted by another admin. So, when an account is compromised, we can play cleanup until they are desysopped. Now, if a crat account would get compromised, the first thing they would go to do in my opinion is sysop everybody they could find (all there vandal friends) who would in turn promote all there vandal friends and this would be MUCH MUCH more detrimental to this project and much more difficult to clean up. Instead of one compromised admin acocunt, we could have 100's easily, deleting, blocking and that would be a HUGE mess to clean up. I strongly oppose maming all admins crats. Chrislk02 (Chris Kreider) 20:22, 20 September 2007 (UTC)

text: Bigger problem: rogue adminicrat bots.  We saw in the last few months some rogue/compromised admins.  Imagine a rogue/compromised adminicrat bot handing out the admin bit to everyone on the planet.  Get 10 of those running on bots constantly re-opping each other and there's nothing a steward could do.  Bad idea.  Very, very bad idea. --B 20:15, 20 September 2007 (UTC)
replies: text: ...which is exactly why I don't think this could happen without a strong de-opping process in place. EVula // talk // ☯ // 20:21, 20 September 2007 (UTC)

text: Yep, B is correct.  Given that bureaucrats can bureaucrat other users, this could essentially create a case where the compromised account could create more compromised bureaucrat accounts faster than a steward can control the situation. -- Renesis (talk) 20:24, 20 September 2007 (UTC)

text: This is ridiculous in my eyes, I'm sorry. Wikipedia as a whole has been operating excellently with this permission for several years now. RFB is a trial I think is needed to show that an administrator really is ready for the next permission upwards. If this were to happen, we would face the chance of rogue bureaucrats, or, at least, users with that amount of power. Why change this system of operation? It is certainly not broken. These extra tools should be reserved to those with that extra knowledge of policy, that extra amount of experience; those that have earned the trust of the community, through RFB, to have those tools. -- Anonymous DissidentTalk 22:33, 20 September 2007 (UTC)

text: Just for clarification, I was always a douchebag. the_undertow talk 17:44, 24 September 2007 (UTC)
replies: text: Well then, that gives me hope. :) LaraLove 17:51, 24 September 2007 (UTC)

text: I don't think RfA's should be decided and closed by non-crats. Admin actions are often undone and argued about, I would hate for this to happen on some guys RfA. The 'crats have a very good track record of not reverting each other, something that cannot be said for admins. I don't think the current system has failed us, so a drastic change like this would more likely be to our detriment. In, my, opinion. ((1 == 2) ? (('Stop') : ('Go')) 20:55, 20 September 2007 (UTC)

text: Though, I don't see why rename and usurpation requests could not be handled by general consensus. ((1 == 2) ? (('Stop') : ('Go')) 20:56, 20 September 2007 (UTC)
replies: text: I think the reason that rename (and by extention, usurpation) is limited to 'crats is because it's a massive server drain (moreso when there are lots of edits to reattribute), and keeping it in a few hands has a very real benefit over the potential of having just any admin do it. EVula // talk // ☯ // 21:18, 20 September 2007 (UTC)
replies: text: I tend to think that the b'crat thing is less of a "special user" feature than the admin piece is.  mostly because it is so obvious how lame most of the b'crat work is.  The only part that requires high function is the closing of special disucssions (RfA's and similar).  The rest is just technical drugery that must be done by a highly trusted person.  I tend to think that people view the admin bit as a rank to obtain to be a "more important" user, as much more of that work is fairly highly visible.  While the official line is that the admin bit is "no big deal" in reality it is a rank to obtain, especially for newbies (until they realize what a drag it can be).  --Rocksanddirt 00:43, 21 September 2007 (UTC)

text: EVula, why would permitting admins do renames increase the server drain? Is the idea that we'd wheel-war with each other over whether a rename should be permitted?--Chaser - T 07:42, 21 September 2007 (UTC)

text: This makes no sense at all. There is no hierarchy of responsability, there's just fear that people will misuse the tools if we give them to everyone, and that's the only reason why we're not all developers. At least for me, this is what a wiki is all about. A.Z. 04:14, 21 September 2007 (UTC)
replies: text:  Well, it is called the principle of least privilege. Although in reality, most bureaucrat work is menial in nature (renaming/usurpation/flagging bots) and only the RfA closure could be consider a "status" by the definition you are using. In a way,  I would support splitting the bureaucrat class to 'promote' and 'rename' privileges, as they are more granular. But then, that's probably just me. Titoxd(?!? - cool stuff) 07:46, 21 September 2007 (UTC)
replies: text: No, it's not just you :) However, I don't see that change as being implemented. Compartmentalization of privileges is a good thing :) SQL(Query Me!) 09:03, 21 September 2007 (UTC)

text: We wouldn't need to add another technical user level between regular user and admin. We could just trust the many established regular non-admin users with more responsibilities than at present. Like I said, we could pass over some of the decision-making powers to trusted non-admins, while leaving admins to carry out the actual technical tasks. Just an extra idea to fill in some of the holes in the main proposal. WaltonOne 14:06, 21 September 2007 (UTC)
replies: text: That doesn't address the fact that administrative backlogs will be harder to clear, unless there is another technical user level. The thing is, admins aren't trusted as much as bureaucrats so if admins start getting the bureaucrat tools, the level of trust required to be an admin increases; promotion rates drop and therefore administrative backlogs (CSD especially) will grow. Sure we can handle CSD now, it's usually kept below 100 articles, but there is a need to keep promoting admins (or some other type of user with the ability to delete) otherwise it will build up over time. AfD could be handled by non-admins for all "keep" results, but even if they were to speedy tag the articles, the deleting admin would still need to check that the AfD has been closed properly. I think the load on administrators would become large and unmanagable. I support the idea of having trusted users to handle various tasks however, I don't see why admins have better judgement than non-admins who are experienced in the wiki-ways. James086Talk | Email 14:52, 21 September 2007 (UTC)

text: I'll be a rebel here, and say that I love Walton's idea. What amazes me is how people immediately think to themselves "What could go wrong with this". So OK, there's a "rouge" bureaucrat around. What of it - there's probably loads of rouge admins around who get away with abuse everyday. And remember the occasions that an account has gone "bad" are very, very low. And did any of them use bots to delete hundreds of pages, or block hundreds of users or whatever? I don't recall. They deleted, perhaps ten pages before they were stopped. Of course I agree we should have a de-admin process (most other projects do) just in case but the amount of worry over nothing makes me laugh. If we trust them to be an admin, we can trust them to be a 'crat. * Aillema 12:04, 21 September 2007 (UTC)

text: *The problem with this proposal is that it doesn't go far enough. Making everyone a 'crat can overburden the stewards. Therefore, we need to make everyone stewards as well ... OK, not everyone -- you need to speak at least two languages to be a steward, and I respect that. So we should keep the multi-language requirement, but include Leet, Pig Latin, Parseltonque, Elvish. Preshly, Javascript and C++ as qualifying languages. This would expand our reach to more linguistic communities and be more democratic as well. -- Cecropia 05:04, 12 October 2007 (UTC)
replies: text:  Oh, yes. I would also include the language that Cthulu speaks, but I don't know what it's called and I'm afraid to ask. -- Cecropia 05:04, 12 October 2007 (UTC)

text: Ohhhh everyone a steward! That will solve everything, the community will have full say(but please include Engrish in the list of acceptable languages). Lets have a poll on it. ((1 == 2) ? (('Stop') : ('Go')) 05:07, 12 October 2007 (UTC)
replies: text: Everyone a steward?? That is ludicrous. A rogue steward could do an immense amount of damage. Passing an RFA would be nigh impossible. Steward is supposed to be the position of highest trust, excluding that of dev., a position bestowed upon only a few of those extremely well-versed in policy and who are experienced. Stewardship is also a position that's scope reaches far past en.wiki. I would be very strongly opposed to that idea. -- Anonymous DissidentTalk 05:21, 12 October 2007 (UTC)
thread_title: Abolish bureaucratship as a special status

message: (If the analysis below misinterprets the crux of the matter here, I would appreciate enlightenment.)
Based on the title assigned to this discussion, I wonder if this is really so much about the tools as the — real or perceived — "status" for Bureaucrats. In other words, is the effort really to abolish a possible "some are more equal than others" structure? --Aarktica 20:49, 20 September 2007 (UTC)
replies: text: I don't think RfA's should be decided and closed by non-crats. Admin actions are often undone and argued about, I would hate for this to happen on some guys RfA. The 'crats have a very good track record of not reverting each other, something that cannot be said for admins. I don't think the current system has failed us, so a drastic change like this would more likely be to our detriment. In, my, opinion. ((1 == 2) ? (('Stop') : ('Go')) 20:55, 20 September 2007 (UTC)

text: Though, I don't see why rename and usurpation requests could not be handled by general consensus. ((1 == 2) ? (('Stop') : ('Go')) 20:56, 20 September 2007 (UTC)
replies: text: I think the reason that rename (and by extention, usurpation) is limited to 'crats is because it's a massive server drain (moreso when there are lots of edits to reattribute), and keeping it in a few hands has a very real benefit over the potential of having just any admin do it. EVula // talk // ☯ // 21:18, 20 September 2007 (UTC)
replies: text: I tend to think that the b'crat thing is less of a "special user" feature than the admin piece is.  mostly because it is so obvious how lame most of the b'crat work is.  The only part that requires high function is the closing of special disucssions (RfA's and similar).  The rest is just technical drugery that must be done by a highly trusted person.  I tend to think that people view the admin bit as a rank to obtain to be a "more important" user, as much more of that work is fairly highly visible.  While the official line is that the admin bit is "no big deal" in reality it is a rank to obtain, especially for newbies (until they realize what a drag it can be).  --Rocksanddirt 00:43, 21 September 2007 (UTC)

text: EVula, why would permitting admins do renames increase the server drain? Is the idea that we'd wheel-war with each other over whether a rename should be permitted?--Chaser - T 07:42, 21 September 2007 (UTC)

text: This makes no sense at all. There is no hierarchy of responsability, there's just fear that people will misuse the tools if we give them to everyone, and that's the only reason why we're not all developers. At least for me, this is what a wiki is all about. A.Z. 04:14, 21 September 2007 (UTC)
replies: text:  Well, it is called the principle of least privilege. Although in reality, most bureaucrat work is menial in nature (renaming/usurpation/flagging bots) and only the RfA closure could be consider a "status" by the definition you are using. In a way,  I would support splitting the bureaucrat class to 'promote' and 'rename' privileges, as they are more granular. But then, that's probably just me. Titoxd(?!? - cool stuff) 07:46, 21 September 2007 (UTC)
replies: text: No, it's not just you :) However, I don't see that change as being implemented. Compartmentalization of privileges is a good thing :) SQL(Query Me!) 09:03, 21 September 2007 (UTC)
thread_title:  Status defined 

message: OK, so there's no consensus for this proposal so far. But, in the hope of changing everyone's mind, I'd like to address a couple of the objections people have made.
*We don't need hundreds more bureaucrats, the existing ones aren't overworked. That's irrelevant. This proposal isn't about making things run more smoothly; it's about decentralising power. It's about (as A.Z sensibly noted) the need to get rid of this idea of a "hierarchy" and "status". At the moment, bureaucrats have far too much power. 
*A rogue 'crat account is more dangerous than a rogue admin account, so it should be more exclusive. I addressed this already. The RfB process is no more likely than the RfA process to weed out untrustworthy people, as demonstrated by Essjay. Basically, someone who can game the system enough to pass RfA without being trustworthy can do exactly the same at RfB.
*The existing 'crats have a good track record of not reverting each other. Firstly, this is because bureaucrats can't wheel-war, as they can't take away sysop privileges, only grant them. Secondly, I don't think their unanimity is necessarily a good thing. When a small elite group has a "bureaucrat chat" and comes to a unanimous decision, it isn't necessarily in line with what the community wants.
*It would drive RfA standards even higher. Possibly, but this would be outweighed by the benefits of decentralising power. I also think we could counteract this by reducing the workload of admins, by transferring more admin functions to non-admins; although certain technical functions (e.g. deletions and blocks) can only be performed by admins, there are decision-making functions that experienced non-admins could be trusted with. For instance, we could start allowing trusted non-admins to close any XfD discussion (not just snowball keeps) and, if the result was Delete, to tag the article for speedy and wait for it to be deleted by an admin. 
Basically, my main reason for wanting this is that having special status and hierarchy is not a good thing. Wikipedia seems more and more to be structured like the Jedi Order; the inscrutable Jedi Council (bureaucrats) deliberate amongst themselves in secret, examining those who face the Trials (RfA) and deciding whether to admit them to the rank of Jedi Knight (admin). On the other hand, the young and inexperienced Padawan learners (non-admins), who actually do a lot of the work, have little power or influence and are increasingly disenfranchised. (I know the analogy is inexact, but it illustrates just what is wrong with Wikipedia's power structure.) WaltonOne 10:24, 21 September 2007 (UTC)
replies: text: We wouldn't need to add another technical user level between regular user and admin. We could just trust the many established regular non-admin users with more responsibilities than at present. Like I said, we could pass over some of the decision-making powers to trusted non-admins, while leaving admins to carry out the actual technical tasks. Just an extra idea to fill in some of the holes in the main proposal. WaltonOne 14:06, 21 September 2007 (UTC)
replies: text: That doesn't address the fact that administrative backlogs will be harder to clear, unless there is another technical user level. The thing is, admins aren't trusted as much as bureaucrats so if admins start getting the bureaucrat tools, the level of trust required to be an admin increases; promotion rates drop and therefore administrative backlogs (CSD especially) will grow. Sure we can handle CSD now, it's usually kept below 100 articles, but there is a need to keep promoting admins (or some other type of user with the ability to delete) otherwise it will build up over time. AfD could be handled by non-admins for all "keep" results, but even if they were to speedy tag the articles, the deleting admin would still need to check that the AfD has been closed properly. I think the load on administrators would become large and unmanagable. I support the idea of having trusted users to handle various tasks however, I don't see why admins have better judgement than non-admins who are experienced in the wiki-ways. James086Talk | Email 14:52, 21 September 2007 (UTC)

text: I'll be a rebel here, and say that I love Walton's idea. What amazes me is how people immediately think to themselves "What could go wrong with this". So OK, there's a "rouge" bureaucrat around. What of it - there's probably loads of rouge admins around who get away with abuse everyday. And remember the occasions that an account has gone "bad" are very, very low. And did any of them use bots to delete hundreds of pages, or block hundreds of users or whatever? I don't recall. They deleted, perhaps ten pages before they were stopped. Of course I agree we should have a de-admin process (most other projects do) just in case but the amount of worry over nothing makes me laugh. If we trust them to be an admin, we can trust them to be a 'crat. * Aillema 12:04, 21 September 2007 (UTC)

text: *The problem with this proposal is that it doesn't go far enough. Making everyone a 'crat can overburden the stewards. Therefore, we need to make everyone stewards as well ... OK, not everyone -- you need to speak at least two languages to be a steward, and I respect that. So we should keep the multi-language requirement, but include Leet, Pig Latin, Parseltonque, Elvish. Preshly, Javascript and C++ as qualifying languages. This would expand our reach to more linguistic communities and be more democratic as well. -- Cecropia 05:04, 12 October 2007 (UTC)
replies: text:  Oh, yes. I would also include the language that Cthulu speaks, but I don't know what it's called and I'm afraid to ask. -- Cecropia 05:04, 12 October 2007 (UTC)

text: Ohhhh everyone a steward! That will solve everything, the community will have full say(but please include Engrish in the list of acceptable languages). Lets have a poll on it. ((1 == 2) ? (('Stop') : ('Go')) 05:07, 12 October 2007 (UTC)
replies: text: Everyone a steward?? That is ludicrous. A rogue steward could do an immense amount of damage. Passing an RFA would be nigh impossible. Steward is supposed to be the position of highest trust, excluding that of dev., a position bestowed upon only a few of those extremely well-versed in policy and who are experienced. Stewardship is also a position that's scope reaches far past en.wiki. I would be very strongly opposed to that idea. -- Anonymous DissidentTalk 05:21, 12 October 2007 (UTC)
thread_title: What I meant

message: There has been more talk recently about a deadminship system. How about this simple policy: "If, following a Request for Comments, a bureaucrat determines that there is a consensus to remove an admin's admin status, they may do so." No new system is required, we just use the existing RFC system, which is already used to complain about rouge admins (I know it doesn't work, but that's mainly because it doesn't change anything - this would fix that). There is no vote, just a standard RFC with lots of healthy discussion (no need to officially make it a discussion about deadminship - just state your opinion and if enough people agree, then that's it). RfCs aren't closed like RfAs after a certain amount of time with a "yes" or a "no", the crat just comes along at whatever time they feel appropriate and removes the admin status if they think there is a consensus. If they don't think there is one, they just do nothing. If a crat removes the admins status and someone disagrees, they can go to ArbCom. If no crat removes the status, someone can still go to ArbCom. All this system requires is adding one line to the policy on RFCs and getting a sysadmin to give crats the power to remove adminship. --Tango 17:15, 21 September 2007 (UTC)
replies: text: I'm not sure RFC is the proper place to discuss blocks, article bans, desysops, etc, because RFCs are "requests for comment", and should only be used for getting outside opinions on a matter, and not for actual remedies. We could possibly expand WP:CSN so that proposals to desysop may be raised there. Giving crats the power to remove adminship wouldn't be that difficult, by the way. Melsaran 17:19, 21 September 2007 (UTC)
replies: text: While CSN is still kind of a work in progress, I think that would be the place to add those potential deadminship discussions.  Those discussions would definately need lots of participation.  --Rocksanddirt 17:29, 21 September 2007 (UTC)

text: RFCs are about gathering input from various editors.  A crat could then choose to act on that input.  Even if crats don't get the technical ability to literally do this themselves, a steward would do it if the crat requested it and pointed them to the discussion where consensus was established.  Friday (talk) 17:25, 21 September 2007 (UTC)

text: I like this idea, though perhaps CSN would be better than RFC. There would need to be an extremely strong consensus for removal of rights though... like you need to pass an RFB. --Deskana (talk) 17:27, 21 September 2007 (UTC)
replies: text: Really?  That sounds tougher than getting desysopped by arbcom, in which case this process probably isn't at all useful.  I would think that if there's significant consensus that someone has misused the tools and has continued to do so after being asked to stop, that should be enough.  Friday (talk) 17:37, 21 September 2007 (UTC)
replies: text: I agree with that. --Deskana (talk) 17:38, 21 September 2007 (UTC)

text: That's probably not such a bad thing. Misusing the tools is one thing, proving that continued misuse is actually damaging the project is quite another. Arbcom aren't great at this, but having them decide whether the misuse is so great and so dangerous that desysopping is the only solution is considerably better than letting a bunch of idiots start an RfC as a means to an end, a way to desysop someone that's crossed them is quite another. Nick 17:55, 21 September 2007 (UTC)
replies: text: Admin recall has, in my view, already demonstrated that such frivolous complaints are easily recognized as such.  Friday (talk) 18:00, 21 September 2007 (UTC)

text: Why does any crat have to do it? Why there needs to be consensus to do it? Why not allow any editor to start another RfA for any user? A.Z. 17:32, 22 September 2007 (UTC)
replies: text: That would cause chaos. We can't do a full RfA every time someone disagrees with an admin action. --Tango 20:00, 22 September 2007 (UTC)
replies: text: The RfA is not supposed to happen every time someone disagrees with an admin action. Do you think that only bureaucrats have common sense?  A.Z. 20:15, 22 September 2007 (UTC)
replies: text: That's the wrong question. We don't need one non-crat to have common sense, we need *all* non-crats to have common sense, and that is, most certainly, not the case. --Tango 21:05, 22 September 2007 (UTC)
replies: text: No, we don't. We could close the RfA (or leave it there: if it's a stupid recall, few people will support desysopping anyway). We could even have a permanent RfA for everyone. Do you believe all bureaucrats have common sense? A.Z. 21:11, 22 September 2007 (UTC)
replies: text: Dealing with the RfAs would waste a lot of time. A permanent RfA for everyone has been suggested before, but is a completely different suggestion to the once being discussed here. Since RfB is so strict, I think we can probably assume all crats have a decent amount of common sense. --Tango 01:50, 23 September 2007 (UTC)
replies: text: I support Tango's modified proposal.  If a Bureaucrat calls a RfA on an admin, and the RfA fails, the admin is desysoped by policy.--Fahrenheit451 00:49, 24 September 2007 (UTC)
thread_title: RfC

message: If we have an easy way to take admin tools from people, we'll be able to have ten times more administrators than we have now. This is the main reason why I think we should have such a system. People's criteria for giving admin status will be much more liberal, because they will be able to take the tools if someone turns out to be a bad administrator. Nowadays, a lot of people don't become administrators not because they wouldn't be good administrators, but because they couldn't prove beyond a reasonable doubt that they are going to be good administrators. Many users who could be helping Wikipedia more by having more technical access are not administrators because people fear that abusive people get the tools —eternal tools. By the way, people's high criteria for giving tools aren't even that good at their job: even people who have proved they can be trusted and gained consensus among the community to have the tools some times turn out to be tool abusers, so this is one more reason to have a system to easily take the tools from someone. I think something unbureaucratic like the RfAs would be good, requiring an RfA-like consensus. Some people fear that these would become a "request for lynching", but I disagree that people would do that. If some few people did that, this would have no consequences anyway, because a consensus would be required. I also think that, if we have an easy system to take the tools from people, we will be able to give the tools to everyone that doesn't have a consensual opposition from the community, which means we could invert the RfA's: if people have 40% support and 60% opposition, they should become administrators, and should stop being administrators only when they have 25% support and 75% opposition, like a banned editor: all editors get editing tools nowadays, and they only lose them when there's consensus to do it. A.Z. 16:01, 22 September 2007 (UTC)
replies: text: Hear, hear. (Except for the last point; I don't think we should lower the percentage threshold for RfAs, it should stay at 70-80% Support. I just think that standards would naturally reduce, if we had a community desysopping procedure. The level of trust needed would be less.) WaltonOne 16:09, 22 September 2007 (UTC)

text: Yeah easy come easy go is a good way to operate. Will also stop the whole "they are an admin they are better and deserve better treatment" part in its tracks. ViridaeTalk 02:09, 23 September 2007 (UTC)
replies: text: Good idea and explanation A.Z.  I think a two-thirds majority should be the quota to pass RfA under an easier and quicker desysop process.  80% is absurdly excessive. Puts an prospective admin into a position of ass-kisser/apple polisher to get that sort of approval. --Fahrenheit451 01:02, 24 September 2007 (UTC)
replies: text:  As it stands, the threshold is 70-75 percent, which seems ok. I also don't see a large problem with the RfA system (other than editcountitis). We seem to have few problems with the admins already. For the problems we do have, there's CAT:AOR and WP:RFC/ADMIN. For serious things, we have ArbCom. I wouldn't be opposed to a Removal system, but we should not create it for the purpose of lowering RfA standards so that they can be removed more easily. I think the removal process should be the same as the current process, but with the opposite goal. Maybe, before we do anything drastic, maybe we should give desysop privileges to crats. J-ſtanTalkContribs 01:53, 24 September 2007 (UTC)
thread_title: If the tools are taken away easily, they are also given out easily

message: RFA is not a mess. People make in into one because they want to create a problem where none exists.Rlevse 16:12, 22 September 2007 (UTC)
replies: text: Read my post above. As it stands, the process is very poor; because we have no procedure for desysopping, there are lots of admins who bend the rules and get away with it (sometimes driving editors away in the process), and, likewise, because admins are so hard to remove, RfA standards keep going higher and higher, leading to good editors failing to pass RfA. If we had an "easy sysop, easy desysop" approach, the encyclopedia would be much healthier. WaltonOne 16:28, 22 September 2007 (UTC)
replies: text: Yet another solution looking for a problem. ((1 == 2) ? (('Stop') : ('Go')) 16:34, 22 September 2007 (UTC)
replies: text: I didn't saying anything about desysop, just RFA, meaning becoming a sysop.Rlevse 16:36, 22 September 2007 (UTC)
replies: text: Walton was referring to RFA. He said: "the process is very poor; because we have no procedure for desysopping, there are lots of admins who bend the rules and get away with it (sometimes driving editors away in the process), and, likewise, because admins are so hard to remove, RfA standards keep going higher and higher, leading to good editors failing to pass RfA." A.Z. 17:01, 22 September 2007 (UTC)
replies: text: Bending the rules is a problem?  You have gotta be kidding.  Someone who doesn't know how to bend the rules is generally going to be way more harmful than someone who does.  Friday (talk) 17:04, 22 September 2007 (UTC)
replies: text: To some extent, bending the rules is fine where common sense is involved. However, I was referring to those admins who perform controversial actions out-of-process, behave incivilly, or otherwise commit infractions of policy which, under the present system, are not severe enough to lead to them getting desysopped. At the moment, you have to do something really bad to actually get desysopped (rather like academic tenure), and that isn't a healthy situation IMO - if nothing else, it drives RfA standards higher because admins, once promoted, are so hard to remove. WaltonOne 17:54, 22 September 2007 (UTC)
replies: text: Sure, I agree with that.  Arbcom wants a smoking gun.  We should be able to remove sysop permissions whenever there's consensus to do so.  The knee-jerk reaction is always "But then all it takes are trolls or problem editors making noise, and a good sysop will get their bit removed."  That's simply bullshit.  We already know how to separate unfounded complaints from legitimate ones.  Do people really think our crats would be unable to do this job?  Friday (talk) 18:00, 22 September 2007 (UTC)

text: Can I have an example of an admin who the community thinks should be desysoped and arbcom has refused? ((1 == 2) ? (('Stop') : ('Go')) 18:17, 22 September 2007 (UTC)
replies: text: That's not the main point. There are people that the community would think that are good administrators and that are not administrators today because people have too high criteria for giving admin tools. People have high criteria for giving admin tools because there's no easy way to take out the tools. If more people became administrators, there would be less of a feeling that administrators are a separate group. Wikipedia would be, as Walton said, healthier.A.Z. 18:30, 22 September 2007 (UTC)

text: Adminship is already too much of a popularity contest. People have high criteria for admins tools because they have the potential for damage, misuse of tools already results in de-admining. What this new system is more likely to notice is when an admin becomes unpopular, because if it had to do with the use of the tools then it could be dealt with under the existing system. ((1 == 2) ? (('Stop') : ('Go')) 02:27, 23 September 2007 (UTC)
replies: text: They could be, but they aren't necessarily. An Arbcom case against an admin causes lots of drama, and takes lots of work, especially with all the other dispute resolution it requires. Usually, it just isn't worth the time. Who knows how many cases of admin abuse we don't know about because nobody cares enough to go through an Arbcom case? -Amarkov moo! 02:36, 23 September 2007 (UTC)

text: Good, de-admining someone should be dramatic, it should require effort, it should require people to care enough, and it certainly should require an attempt at dispute resolution. ((1 == 2) ? (('Stop') : ('Go')) 03:30, 23 September 2007 (UTC)
replies: text: No. Absolutely not. You know what that sounds like to people who have a complaint? "Oh, you think that this admin is being abusive. Here, jump through all these hoops. If you don't want to waste your time jumping through our always annoying and occasionally arbitrary hoops, then you don't care enough about his abuse so we won't do anything. Nyah nyah." -Amarkov moo! 05:43, 23 September 2007 (UTC)
replies: text: I agree strongly with Amarkov here. At the moment, you basically have to go on a rampage in order to actually get involuntarily desysopped. Plenty of admins get away with day-to-day incivility, biting new users, out-of-process deletions, and other minor infractions, and receive nothing more than a formal slap on the wrist. We need a situation in which complaints against admins are handled fairly, consistently and speedily. The current system creates problems for everyone; for one thing, it means that good candidates find it hard to pass RfA, and have to jump through arbitrary hoops, because we're all so reluctant to hand out the admin tools, since it's so hard to take them away again. We need to move over to an "easy sysop, easy desysop" culture, in which granting adminship is really viewed as no big deal, and taking it away is not viewed as analogous to capital punishment. WaltonOne 13:24, 23 September 2007 (UTC)

text: Amarkov I just don't think of dispute resolution as a set of hoops. They are not arbitrary, but are designed to find a voluntary resolution before resorting to the blunt force of removing the tools. If there are specific people who the community feels should not be a sysop, but still are then they should be addressed directly, but I still have not seen how arbcom has failed to regulate admin abuse. Frankly incivility is not abuse of admin powers, it is a regular behavioral problem that can be handled the same way for admins and no-admins alike. ((1 == 2) ? (('Stop') : ('Go')) 16:26, 23 September 2007 (UTC)
replies: text: But removing the tools is not always a brute force tactic if nothing else works, sometimes it's the goal. If I think an admin is being abusive, I want their acess to the tools removed until such time as they demonstrate they will not abuse the tools. "Yes he did something wrong, but he said he would stop" doesn't work for me when admin abuse is involved. Why do I need to go through a long painful RfC to show that I will accept no intermediate solution? -Amarkov moo! 17:36, 23 September 2007 (UTC)
replies: text: If I may make an observation of this discussion on Deadminship, I have noticed that discussion for reform in removing adminship suffers from the same problem as discussion for reform in granting adminship. There is no agreement on a better method than what we have now. For example, many people believe that desysnopping should be reformed, but there is plenty of arguing on how to do it. Looking at the previous part of the discussion, some support having a RfC with a bureaucrat determining consensus of removing adminship. Others wish for something like the Community Sanction Noticeboard for removing adminship. After plenty of discussion, there are many who say that neither of these methods are practical. There are also plenty of people who are fine with the desysnopping procedure as it is and want no reform at all. Compare these suggestions to various forms of RfAs at Wikipedia:Requests for adminship/Moralis using an AfD format and Wikipedia:Requests for adminship/Matt Britt using an RfC format. These were both popular suggestions for RfA to become and the consensus for them after being tested practically was that they both are definitely not good ways for RfAs to operate under. There was absolutely no consensus on how to grant adminship back in March when this talk page was ablaze with discussion. It seems the same is true today with discussing on how to remove adminship. I doubt that a consensus on how to take away adminship will come of this discussion. Perhaps it will and I am wrong, but there sure doesn't appear to be a consensus right now. Captain panda 18:10, 23 September 2007 (UTC)
replies: text:  I tried going over to the reform page, but all we had were some sucky ideas and some less sucky ideas. I guess it was just fun to see how the community felt about how we thought wikipedia should run. We had no consensus to change, and RfA remains, for the most part, static. But one quick question: how were those RfA formats you gave us chosen? Like, who said, "Hey, you know what would be cool? If this is what an RfA looked like"? J-ſtanTalkContribs 19:48, 23 September 2007 (UTC)
thread_title: No problem exists

message: Just came across Wikipedia:Requests for adminship/williebruciestewie, not sure what's up with that- isn't listed on the RfA page and looks like it's only partially filled out. OSbornarf 23:49, 21 September 2007 (UTC)
replies: text: Well, pages often take a couple of days from creation to transclusion. That said, this RFA has zero chance of passing. willibruciestewie is too new. -- Flyguy649 talk contribs 23:51, 21 September 2007 (UTC)
replies: text: Ah- thanks. OSbornarf 00:01, 22 September 2007 (UTC)
thread_title:  [[Wikipedia:Requests for adminship/williebruciestewie]] 

message: I suggest we add  to the RfA template, as it keeps signing things that need not be signed, such as questions (see  for an example). --Agüeybaná 23:59, 21 September 2007 (UTC)
replies: text: tough call, as people also forget to add their name to stuff and it is important in some places.  --Rocksanddirt 00:05, 22 September 2007 (UTC)
replies: text: Then the community can add  when that happens, but, right now, it's doing more damage than it is helping the process. --Agüeybaná 00:06, 22 September 2007 (UTC)
replies: text: I agree with Rocksnaddirt - the questions make up only a small part of the RfA, and for the rest of it we really don't need unsigned patrollors... Dihydrogen Monoxide (H2O) (Drought) 03:17, 22 September 2007 (UTC)

text: Besides, when asking an optional question you're supposed to sign, as far as I know. Dihydrogen Monoxide (H2O) (Drought) 03:17, 22 September 2007 (UTC)

text: I can't remember the last time I actually saw the signing bot screw up on something like that (especially since signing your question isn't a terrible idea). Might be a bit of a jump-o'-the-gun here. EVula // talk // ☯ // 05:13, 22 September 2007 (UTC)

text: I don't see why SineBot is signing the rfas isn't I ment to just do talk pages? --Chris   G   05:17, 22 September 2007 (UTC)
replies: text: I've opted out of SineBot myself. I've not noticed an instance in an RfA where I felt there was an inappropriate sign, but I'm one to go back and amend my comments for spelling mistakes or add additional bullets in a review for GA, and it's bad about signing those, which is inappropriate, in my opinion. I'm not sure that would be a problem in an RfA, though. LaraLove 05:31, 22 September 2007 (UTC)
thread_title:  &#123;&#123;nobots&#125;&#125; 

message: To cure editcountitis, how about we remove the wannabe kate link on the RfAs? I understand the lack of success of proposals, and I know this probably won't pass, but I wanted to generate some more discussion on the fight against heightening edit count standards in RfA. J-ſtanTalkContribs 19:51, 23 September 2007 (UTC)
replies: text: I'd be against that - ignoring the edit count, it's the best way to see which articles the user's put a lot of work into, which projects/pages they're active on, etc. Plus, it would encourage more people to use WannabeKate direct, which wreaks havoc on the server —  iridescent (talk to me!) 20:03, 23 September 2007 (UTC)
replies: text:  Isn't wreaking havoc on the server a bad thing? Otherwise, I understand your point. J-ſtanTalkContribs 20:08, 23 September 2007 (UTC)
replies: text: I think what Iridescent is saying is that when someone goes to an RfA page and wants to see the edit count of the user and there is no edit count listing on the talk page, that person has to go and make a special request for the edit count himself or herself. If, say, 10 people do this instead of it only happening once, that makes quite a difference. Captain panda 20:13, 23 September 2007 (UTC)
replies: text: I see. Thanks! J-ſtanTalkContribs 20:30, 23 September 2007 (UTC)

text: Please keep the editing stats.  They are useful and convenient.  You can't make people think right by withholding info. - Jehochman  Talk 20:22, 23 September 2007 (UTC)
replies: text: And my point is what are they really useful for? Edit count standards are rising, and so I proposed to lower them by not making them as public as they are now. Also, I am not trying to make others think right by keeping the info from them, I am trying to encourage people to review the quality of their contribs instead of the amount. Someone can make 30 vandal-edits to a page (it's possible, though unlikely), have that show up on their wannabe kate report, and be praised for the amount of work they've done on it. This isn't right. we should be reviewing contribs more. J-ſtanTalkContribs 20:30, 23 September 2007 (UTC)
replies: text: I agree with J-stan, and see posting the Wannabe Kate stats as a WP:BEANS violation. "Please don't base your vote on the numbers we're posting on every RfA talk page." rspeer / ɹəədsɹ  21:09, 23 September 2007 (UTC)

text: And I agree with Iridescent.  I find the WannabeKate analysis quite useful to see what articles and Wikispaces the candidate is most involved with.  This gives you something to look for when you go through their contributions.  There is useful info there, aside from the raw numbers, which I agree are of limited probative value.--Kubigula (talk) 21:22, 23 September 2007 (UTC)

text: I also agree with not removing them. Yes it is true they do not tell you everything you should know of a candidate in an RFA; but WannabeKate does provide me with a good starting point on what a candidate generally does on Wikipedia beyond total edit count, which is useful when looking through their contributions. If the WannabeKate results are removed from the talk page of RFA candidates in the future, I and others will simply use WannabeKate direct instead,  which as already said, is not that helpful to the server. Camaron1 | Chris 21:52, 23 September 2007 (UTC)
replies: text:  And my proposal let's people really go through their contributions to find all the useful info you mentioned is on WK. Also, just for clarity, my proposal does away with posting the stats on the talk page as well as removing the link on the project page. J-ſtanTalkContribs 21:54, 23 September 2007 (UTC)
replies: text:  We could still plug their name into Wannabe Kate. LaraLove 13:53, 24 September 2007 (UTC)
replies: text:  Well the point isn't to keep this info from people, it's to discourage people from using WK. Right now, it's just there. You can click on it, and no one will say anything. If you go to WK and plug it in, what does that say about your contrib reviewing style? J-ſtanTalkContribs 14:55, 24 September 2007 (UTC)

text: Well I don't think Wannabe Kate really is that bad; it is how people use the information, not the information itself which seems to be the problem here - and it has been established WK is a useful starting point for some when looking at a candidate. Saving a link to WK is simple enough so I don't think removing all evidence of its existence from an RFA is going to make much of a difference in practise. I prefer the idea of creating a tool to give more information beyond that given by WK - as suggested below. Camaron1 | Chris 17:14, 24 September 2007 (UTC)
replies: text:  Yeah, maybe RfA should stay the same, but someone should make a tool as an alternative to WK. It just shows the most edited pages, edit summary usage, and participation in XfDs and AIV. J-ſtanTalkContribs 17:20, 24 September 2007 (UTC)
replies: text: There is no point in blaming the information when people mis-use the information. What we need is more information so that edit counts are not the only summary available. I am working on a tool right now that will estimate the block rate of reports a user has made to AIV. ((1 == 2) ? (('Stop') : ('Go')) 15:39, 24 September 2007 (UTC)
replies: text:  Yeah, maybe instead of removing the stats altogether (which I admit is a bit extreme), maybe we just need another tool. We could keep the WK stats, and if you wish, you could just use another tool. J-ſtanTalkContribs 16:19, 24 September 2007 (UTC)

text: That sounds like a great idea to me, (1 == 2). Would certainly save time. LaraLove 17:32, 24 September 2007 (UTC)

text: Definately not. We need that to see how often they use the edit summary, use Wikipedia and to identify areas they work well in and the areas they don't. It is so very useful, and to get rid of it would be bordering on madness. Lradrama 17:31, 24 September 2007 (UTC)
replies: text: Agreed.  It's a useful tool.  It covers far more than simple edit count.  What's more important than edit count is how and where those edits were done, and this is a good record of that.  Of course it could be better, but for now it's what we've got. I see no reason not to use it. - Kathryn NicDhàna ♫♦♫ 19:17, 27 September 2007 (UTC)
replies: text: This has been touched on already but I'd like to reiterate: the tool is far more useful to me than mere edit count. Which articles are in the various lists, eyeballing the proportions of where the edits are, and easily going to the most worked on articles is very helpful. Of course there are aspects of WannabeKate which could really be improved. It's a little like an ax compared to a utility knife: a bit awkward and unwieldy for some tasks. (Oh, really nice comparison, Pigman... You a serial killer or what?) Pigman 20:32, 27 September 2007 (UTC)

text: Would it be possible to make a counter that can display the median byte addition or subtraction for a user's edits to a given article? Or the cumulative byte addition or subtraction of a user's edits to an article? Those, too, would be imperfect measures, but they might help differentiate between articles that a user has expanded considerably and those to which he or she has just reverted vandalism.--Danaman5 21:43, 27 September 2007 (UTC)
thread_title:  A proposal (yes, I know the infamy of RfA proposals) 

message: Is there a principal somewhere that people making RfA comments should disclose any past disputes or involvements they may have had with the nominee?  I think this would help prevent retaliation and improve transparency. - Jehochman  Talk 20:22, 23 September 2007 (UTC)
replies: text: I can't speak for everyone, but unless it was particularly memorable, I certainly couldn't say for sure who I have & haven't been in conflict with - if a user runs for adminship, and I forget that I reverted their addition of unsourced content to Parsnip in January, then when someone brings the fact up it makes me look like I'm trying to hide something. Don't see how it would work. —  iridescent (talk to me!) 20:38, 23 September 2007 (UTC)
replies: text: Nothing can eliminate common sense.  A de minimus interaction like that, especially if you don't even remember it, wouldn't count.  But you make a good point.  In any case, past involvements can be highlighted and the comments can be judged on that basis. - Jehochman  Talk 01:50, 24 September 2007 (UTC)
replies: text: The more experienced a Wikipedian gets, the more disputes he/she will have (it's quite inevitable) and the less likely one will be able to pick a particular incident out from memory. Lradrama 17:29, 24 September 2007 (UTC)
replies: text: Absolutely. There are only two editors I distinctly remember having serious disputes with, but I know I've had plenty in the course of my wiki-career (though I've had a lot more post-adminship than pre-adminship). EVula // talk // ☯ // 17:33, 24 September 2007 (UTC)
replies: text: As is evident by your insult collection. LaraLove 17:55, 24 September 2007 (UTC)
replies: text: Gosh, EVula I just noticed. --Тhε Rαnδom Eδιτor 23:23, 24 September 2007 (UTC)

text:  Only 95 insults? You must be new here. Titoxd(?!? - cool stuff) 07:46, 25 September 2007 (UTC)
replies: text: I haven't updated it in a while. :P Eventually, some of the insults just became repetitions (c'mon, I don't need to document every time I'm called gay... if I did, I'd never get any editing done). EVula // talk // ☯ // 13:40, 25 September 2007 (UTC)
replies: text: Yes, gay is quite a common name Wikipedian's get called. However, another regularly recurring one seems to be do you have a life? I'm so fed up of that now. :-( Lradrama 13:43, 25 September 2007 (UTC)
replies: text: My personal favourite is "You have 36DD man boobs" —  iridescent (talk to me!) 15:32, 26 September 2007 (UTC)
thread_title: Ever optimistic about making improvements

message: This template is on every RfA page, and 1) not protected (I'd say semi protect) and 2) not substituted. Either it need to be subst, or protected. Also, shouldn't the templates on most RFA pages be substed to begin with? CO2 02:24, 25 September 2007 (UTC)
replies: text: I just semi-protected the template. EVula // talk // ☯ // 02:41, 25 September 2007 (UTC)
replies: text: Why must it be subst? It's going to create a mess in the edit box. Please note that there's no policy or guideline saying that these signature templates should be subst. --Agüeybaná 02:42, 25 September 2007 (UTC)
thread_title:  [[Template:Usercheck-short]] 

message: On Special:Statistics as of a few minutes ago, there are now 1,336 admins on Wikipedia. The next admin will become the 1,337th user to become admitted as administrator on Wikipedia. This is one "leet" milestone. --Let Us Update Special:Ancientpages. 07:37, 25 September 2007 (UTC)
replies: text: So? -- Anonymous DissidentTalk 07:39, 25 September 2007 (UTC)

text: Hehe, cute. ~ Riana ⁂ 07:42, 25 September 2007 (UTC)
replies: text: I am still confused. So it relates to l33t... -- Anonymous DissidentTalk 07:44, 25 September 2007 (UTC)
replies: text:  1337 = leet in 13375|°34|< :P ViridaeTalk 07:45, 25 September 2007 (UTC)

text: Very funny. :) EVula // talk // ☯ // 13:41, 25 September 2007 (UTC)
replies: text: I'm very disappointed that I am not the l33t admin! Damn. It would have been so fitting! (I was L33tLara in the gaming world for many years. My Y!im handle remains as such! :p) LaraLove 16:32, 25 September 2007 (UTC)
replies: text: Anyone remember who was admin 666? Pascal.Tesson 18:24, 25 September 2007 (UTC)
replies: text: It seems to have been Shimgray. Kat Walsh (spill your mind?) 04:04, 27 September 2007 (UTC)

text: Heh, and that leaves anyone who really cares that much to go make a request on meta and then turn around and ask for their bit back before the 'crats get to the next likely promotion. Um, oops.--Chaser - T 06:46, 26 September 2007 (UTC)

text: So Ronnotel is the 1,337th admin then? I just checked Special:Statistics a minute ago and saw that we now have 1,337 administrators. If he is, then my congrats goes out to him for being a "leet" administrator! --Let Us Update Special:Ancientpages. 10:23, 26 September 2007 (UTC)
replies: text: He is indeed. Neil ム 10:53, 26 September 2007 (UTC)

text: ...not to be a dick or anything (not that it's ever stopped me before), but you do realize that Jaranda isn't the first admin to have their sysop bit removed (by any process), correct? If we're talking about the total number of sysops ever, we're well past 1337. EVula // talk // ☯ // 19:54, 26 September 2007 (UTC)
replies: text: I mentioned Jaranda because he left about a week ago.  I do know that other admins have been desysopped before.  User:Chick Bowen/Desysop is good reading. hbdragon88 21:18, 26 September 2007 (UTC)
replies: text: See Wikipedia: Former administrators for a full list. Captain panda 21:21, 26 September 2007 (UTC)

text: |_33T --Deskana (talk) 11:09, 26 September 2007 (UTC)

text: Special:Contributions/1337 ? :) Pedro :  Chat   15:54, 26 September 2007 (UTC)

text: 42. Oh, wait... Titoxd(?!? - cool stuff) 19:34, 26 September 2007 (UTC)
replies: text: Truly elite people use every letter, the correct letters and adhere to accepted grammatical standards. ((1 == 2) ? (('Stop') : ('Go')) 19:51, 26 September 2007 (UTC)
replies: text: Looks like it could be User:Ronnotel. bibliomaniac15 00:13, 27 September 2007 (UTC)

text: The system itself does not number admins, it only numbers users and has admin flags on them. So really, you are all welcome to count it any way you like. ((1 == 2) ? (('Stop') : ('Go')) 03:08, 27 September 2007 (UTC)
thread_title:  The next admin is the 1,337th. 

message: I just realized something. We have a short cut to the main RFA page, so why not to RFAs. Let's just say for example, Wikipedia:Requests for adminship/Nat. A bot could come along and create WP:RFA/Nat when the RFA was listed. Any opinions on the idea. --Тhε Rαnδom Eδιτor 20:44, 29 September 2007 (UTC)
replies: text: Nah, too many redirects from mainspace. GDonato (talk) 20:52, 29 September 2007 (UTC)

text: I don't know if shortcuts to individual RFAs would be really useful. The only time a shortcut would be used is during the 7-day period that the RfA is active. Moreover, in order to be aware of the shortcut's existence, one would have to be aware of the active RfA request. Black Falcon (Talk) 20:55, 29 September 2007 (UTC)
replies: text: Don't really see the point - it's not like typing WP:RFA and clicking on the relevant entry in the contents is that hard —  iridescent (talk to me!) 21:05, 29 September 2007 (UTC)
replies: text:  While I do enjoy shortcuts (I just ignore WP:WTF :), I agree with Black Falcon. It would be impractical. J-ſtanTalkContribs 21:10, 29 September 2007 (UTC)

text: Black Falcon already voiced my objects. Minimal amount of use from such redirects. EVula // talk // ☯ // 21:12, 29 September 2007 (UTC)

text: Some shortcuts exist already, e.g. WP:RFA/Aecis, WP:RFA/Emico, WP:RfA/Llama man. None of the shortcuts were created by the candidate of the RFA. Redirecting from mainspace is not an issue, since all they should be marked with :Category:Unprintworthy redirects, and besides begin with WP: (which mirrors should ignore). However, this doesn't seem too useful, since "Wikipedia:Requests for adminship/Candidate" is already a very predictable formula to find an RFA. As Black Falcon mentioned, the shortcuts will not have much utility after 7 days. GracenotesT § 21:14, 29 September 2007 (UTC)
replies: text: Whoa, I forgot I made that redirect (it actually was made by me, the candidate). I think I'll delete it. — Malcolm (talk) 21:18, 29 September 2007 (UTC)
replies: text:  (ec) I agree with the above comments, in that it will only be useful for seven days, and editors will have to be aware of the specific RfA taking place to use it, which means he/she will have probably participated before then. Users who wish to monitor discussions after they comment on them can simply watch the nomination sub-page, or use the User:Tangotango/RfA Analysis/Report template. Shortcuts would require creating and deleting pages over and over. - Mtmelendez (Talk|UB|Home) 21:17, 29 September 2007 (UTC)

text: Ah, I see, your account was renamed. (Why didn't I think of that?) GracenotesT § 21:23, 29 September 2007 (UTC)
replies: text: What would be classified as controversial? --Тhε Rαnδom Eδιτor 23:37, 1 October 2007 (UTC)

text: WP:WATCH or WP:BN is probably a much more useful shortcut to remember... 64.126.24.12 18:03, 2 October 2007 (UTC)
thread_title:  Shortcuts 

message: Is there some reason we're allowing this RFA to run? In any other scenario, someone would have snowballed it closed long ago. Sean William  @ 16:07, 1 October 2007 (UTC)
replies: text: I'm confused to. It was removed at one point and readded.Rlevse 16:11, 1 October 2007 (UTC)
replies: text: there is ongoing discussion at WP:BN Ronnotel 16:19, 1 October 2007 (UTC)

text: [ec] See Wikipedia:Bureaucrats' noticeboard#Heads up for discussion about it. EVula // talk // ☯ // 16:20, 1 October 2007 (UTC)
thread_title:  [[Wikipedia:Requests for adminship/Kelly Martin 2]]