Misplaced Pages

talk:Requests for adminship: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 17:36, 28 May 2006 editOne (talk | contribs)Extended confirmed users9,370 edits →New: when should I start?: - answer← Previous edit Revision as of 17:44, 28 May 2006 edit undoBootblack (talk | contribs)125 edits I meant my ability to vote in RfANext edit →
Line 408: Line 408:
:See ] and ]. Also, showing a lot of early interest in becoming an admin is a red-flag for many people. —] (]) 17:35, 28 May 2006 (UTC) :See ] and ]. Also, showing a lot of early interest in becoming an admin is a red-flag for many people. —] (]) 17:35, 28 May 2006 (UTC)
:Well, if you're ''voting'', start at about 125 edits. If you're ''running'', wait until about 2,500 good edits if you're nominating yourself, or until somebody else nominates you. ] 17:36, 28 May 2006 (UTC) :Well, if you're ''voting'', start at about 125 edits. If you're ''running'', wait until about 2,500 good edits if you're nominating yourself, or until somebody else nominates you. ] 17:36, 28 May 2006 (UTC)
::I mis-communicated. I meant as regards my participation in the voting process. I never thought of standing for the job of an administrator - with 2 days as a registered user and with hardly 100 edits, only a fool shall think of the same. Right now, I want to know about by ability to vote in the RfA. --] 17:44, 28 May 2006 (UTC)

Revision as of 17:44, 28 May 2006

Shortcut
  • ]

Archives

Desyssoping mechanisms

There's been some talk on this page in the last week or two about the need for a system for removing people from the adminship. Earlier, someone suggested that all adminships have a sunset clause that requires admins to be reconsidered once per year. This was widely opposed as unworkable (given that there are 800+ admins) and undesireable, since it would mean that admins have to think more about politics than policy.

I'm sure I'm not the only one, however, who's seen admins who have behaved very badly and who, if the community had known how they were going to act, would never have passed the RfA process. I'm also sure that I'm not the only one who thinks that there should be some mechanism by which the community, whose consensus bestowed sysoppery, might take it away. (There is, to my mind, a strange assymetry to our system in that it is community concensus that creates admins, but only ArbCom that can undo this).

What I see as a potential mechanism (which I'd like to hear your thoughts on) would be a two-stage process. First, a petition-like stage which would require that if a certain number of wikipedians-of-good standing (say 25? 50? some proportion of admin's RFA vote? recent admin vote?) sign on as requesting a review, the admin in question would be submitted to a new RfA process (or perhaps a RfA-like process). Perhaps an ArbCom/Jimbo approval to follow? Anyway, tell me what you think. Bucketsofg✐ 13:12, 19 May 2006 (UTC)

It's up to once a week, I see. Kim Bruning 13:34, 19 May 2006 (UTC)
Perhaps we need a page containing links to all the proposal pages and archived talk pages where we've discussed these things. We can use a Wikilink to such a page to respond to these now-weekly proposals. --Deathphoenix ʕ 13:38, 19 May 2006 (UTC)
I agree, Bucketsofg. I suggested this same type of system on the admin accountability proposal page. joturner 13:36, 19 May 2006 (UTC)
Oops. Should have known that something similar had been suggested. Given the number who are against having a community-based mechanism in the discussion you link, my guess is that any change is a dead letter. Bucketsofg✐ 13:42, 19 May 2006 (UTC)
Pretty much. If an admin's actions are bad enough to warrant desysopping, take it to the ArbCom. I haven't seen any indication that they're overloaded with desysopping requests—so until there's an indication that they can't handle it, they seem to be the logical route. TenOfAllTrades(talk) 13:51, 19 May 2006 (UTC)
Ditto. Johnleemk | Talk 14:24, 19 May 2006 (UTC)
I agree. Also, many of the accusations of rouge admin performance are based on the fact that there is disagreement over some fundamental policies of Misplaced Pages, and how those policies should be enforced, and how fast such enforcement should be (fast gives the appearance of being recklessly out of process). It is important to have people who understand the finer points of policy and process to make the desysop decisions, to distinguish between real rouge performance and the mere appearance of rogueness, and ArbCom fits the bill nicely. NoSeptember 14:38, 19 May 2006 (UTC)
Were any actions taken based on the feedback, Jo ? "Someone should have the authority to temporarily de-admin problematic admins", for instance, was voted 40-18. Tintin (talk) 14:20, 19 May 2006 (UTC)
Jimbo has that authority, as does Danny of the WP:OFFICE. Stewards have the technical ability, though they exercise it rarely and only in clear-cut cases (obviously insane or compromised account). The recent examples I can think of ended up before ArbCom for review anyway. TenOfAllTrades(talk) 14:50, 19 May 2006 (UTC)
ArbCom has that authority as well, and I imagine they could pass an injunction fairly quickly if truly needed. Christopher Parham (talk) 15:01, 19 May 2006 (UTC)
In an emergency, where there is question of an admins actions, the developers will desysop; they will, in some cases, do so more quickly than stewards will. There are plenty of mechanisms to have someone desysopped (including several of us who have home and mobile phone numbers of stewards and developers) if they really need to be; the fact of the matter is, there are very few cases where someone should be desysopped without an arbitration case or direct-intervention from Jimbo. Essjay (Talk • Connect) 15:21, 19 May 2006 (UTC)
And this is when we ask how many developers and stewards you have been caught stalking :), seriously though I agree with Essjay that there are plenty of fallbacks in place and adding a new one would cause more problems that it would solve. Pegasus1138 ---- 19:46, 19 May 2006 (UTC)
I'm swear not stalking..."DANNY! MARRY ME! PLEEEEEEEEASE!" </stalker> Essjay (Talk • Connect) 00:19, 20 May 2006 (UTC)
"That's hot!" Ok... seriously, is there actually a problem here about not being able to get hold of devs or stewards? ++Lar: t/c 01:48, 20 May 2006 (UTC)
Seems like this emergency desysopping has only been used on Ævar Arnfjörð Bjarmason before. So there's no big deal if we don't have a formal quick desysopping process. Kimchi.sg 04:58, 20 May 2006 (UTC)
I think Jimbo desysopped several (ungefahr 5?) people recently during the pedophile controversy. So there have been more than just Ævar. -lethe 06:55, 22 May 2006 (UTC)
He did, indeed, in fact, his only actions as a steward have been to desysop people in his capacity as "the safety valve." However, they weren't really security-related desysoppings (Avar's was, irreversible image deletions were taking place, and there was no response to requests to explain), but rather, desysoppings to stop a wheel war from sucking in more people. There wasn't any reason to thing any permanent damage would be done to the project (permanent damage meaning things like permanent loss of images, or irreversible page history merges, or DOS consequences from deleting huge pages, etc.); the real danger was that we could lose valuable contributors due to the heated actions that were being taken. So, "social" security concerns, not "technical" security concerns. Essjay (Talk • Connect) 00:57, 23 May 2006 (UTC)

new angle

I agree with all that's been said so far, but I had a different idea: we should have a mechanism to desysop admins that have gone on the record in saying that they are leaving Misplaced Pages and they do not intend to return. I mean, if the person has decided to kick the bucket once and for all, there seems to be no purpose in keeping the flag for that account, which may also end up compromised sometime in the future. Recently, Carbonite announced that he was leaving, and requested to be desysopped, but Radiant also left and the account still has sysop status. I would think some time would be allowed to pass, so that it can be confirmed that the user wasn't just blowing off steam and had no intention to actually leave the project — say, after a couple of months without editing following the statement that s/he was leaving? Redux 02:00, 20 May 2006 (UTC)

A couple of months is a tad too short. Ta bu shi da yu announced he wanted to leave last year, but came back after 2 months or so. Kimchi.sg 04:53, 20 May 2006 (UTC)

Emergency desysopping was used in the case of the Great Pedophile Userbox Wheel War (or GPUWW). Basically, a few of us arbcomers who were around notified Jimbo that an emergency was brewing, and based on the recommendations we gave him, he desysopped them until we could address it in a case. Raul654 05:04, 20 May 2006 (UTC)

The original post by Bucketsofg was not about such emergencies but about those are invicil and who if they stood for an RfA now, would be soundly defeated. Tintin (talk) 05:24, 20 May 2006 (UTC)

Normally, a user who makes a personal choice to leave, and actually does leaves, doesn't come back any time soon — leave it to Ta bu shi da yu to subvert that rule ;). If there are more common cases of users who state for the record that they are leaving for good and return after a couple of months or so, then we could wait a longer period, naturally (although it is also possible that the account be desysopped for security reasons and, if the user ever returns, s/he could request to be resysopped upon his or her return). I believe Raul was referring to Carbonite's situation. If I recall correctly, Carbonite declined an offer to be resysopped, saying that he had actually requested to be desysopped already, that he was leaving and had no intention of changing his mind. Carbonite's been inactive since February 11 (or so), but there's no issue there because the account has had the admin flag removed. To return to my other example, Radiant has been inactive since February 7, that is, over three months (closer to four months by now). Since the user left a very clear statement that he was leaving, retaining the admin status for the account seems pointless at best. Any accounts with admin access in a similar situation should be desysopped, but we don't have a system in place to make this happen — and it's not just admins: Optim left Misplaced Pages in March of 2004 with a clear statement that he was leaving for good. It took us nearly two years to remove his Bureaucrat access, and the account still holds admin access, despite being inactive for 2 years and 2 months (at the time of this post). Redux 05:43, 20 May 2006 (UTC)
Wasn't Zoe gone for a year before returning? Essjay (Talk • Connect) 06:01, 20 May 2006 (UTC)
I see no need to remove access for any position held by inactive users except those that could be misused covertly or unreversably if they fell in the wrong hands (namely, developers and checkusers). There is no real risk with admins or bureaucrats. Creating a new policy for a non-issue seems unnecessary. NoSeptember 13:07, 20 May 2006 (UTC)
But did Zoe go on the record to say something like I'm leaving for good? Because that's the instance I'm talking about. I don't know: it's been said time and again that, although almost every admin activity can be reverted, misuse of the tools consistently can cause a lot of trouble around. In this case, it would be about a possible compromise in the account that has been abandoned by the user. And in any case, it would serve us to keep things in check: an admin is a trusted user who has the tools in order to do maintenance work, even if just occasionaly. A user who has left for good, and left a clear statement to that effect, is not going to be using the tools, and it's not as if desysopping an account is a laborous opperation that requires rebooting the servers. It's particularly simple when it comes to applying objective criteria (user declared that s/he was leaving for good / user did leave — not edited anymore) to someone who's not even interested in the project (let alone Adminship) anymore. Quite simply, it doesn't hurt anyone, it keeps the admin community "up to date" and it may even prevent occasional/eventual problems. Remembering: we could make it so that the rare departed users who end up returning can request resysopping of their accounts (subject to some kind of community approval, maybe RfA-like) upon their return. Redux 15:15, 20 May 2006 (UTC)
They can say whatever they want, but unless they specifically request to be desysopped, why should we act as if they had? When was the last time an inactive admin went on a destructive spree? And if it happened, wouldn't we just take care of it promptly like any other problem admin? NoSeptember 15:24, 20 May 2006 (UTC)
Actually, I would say that when an Administrator, who is supposed to be a dedicated user, declares of his or her own will, for reasons that are his or her own, the s/he is leaving Misplaced Pages, and then actually leaves, that would pretty much mean that they forfeit any kind of privilege (not the best word, but it's late where I am...) that they had had bestowed upon them as dedicated users, which they are not anymore, by choice. Redux 01:46, 21 May 2006 (UTC)
Hm...I left for a month at the end of last year...Should I be included in your list of undedicated users? Essjay (Talk • Connect) 02:14, 21 May 2006 (UTC)
And, what if someone was forced to leave for 6 months because of, say, health problems that they didn't want to share with the whole world? Just let sleeping dogs lie. If they come back, great! If they don't, they aren't hurting anyone. If they come back to hurt someone, they can then be blocked and ArbCommed. --Mark Neelstin 02:17, 21 May 2006 (UTC)

Guys, again, I'm referring exclusively to users who go on the record saying that they are leaving for good for reasons that are their own (most say they're "outraged" by something, or just that they've "lost interest"). This does not apply to users who take extended wikibreaks or users that vanish misteriously (the latter because we could never be sure of what happened). Redux 02:44, 21 May 2006 (UTC)

Yeah, but often people decide to come back, and then what? Make them go through the RfA process again? Who is is hurting to leave these users be? I just don't see much of a point. --Mark Neelstin 02:56, 21 May 2006 (UTC)
Stupid computer... something went awry and submitted the page without my wanting to. My first missed edit summary in like 7 or 8 months! Argh! Harumph! Oh well, the new streak starts now. --Mark Neelstin 02:59, 21 May 2006 (UTC)
I don't know of users who have left on the terms I've just mentioned that decided to come back. And the proposal includes a waiting period designed to make sure that the disgruntled Admin wasn't just blowing off steam in the wake of a very unpleasant episode. Consider this rhetorical question: would you support the RfA of a user who had gone on the record saying that they no longer care for the project (and meant it)? This is why the proposal would apply only to this particular situation. Hey, let's desysop Mark for forgetting the edit summary! ;) Redux 03:08, 21 May 2006 (UTC)
Well, if they really meant it, and they aren't coming back, what is so egregious as to desysop them? If they really meant it, they aren't coming back to cause trouble, so rather than create some new policy or procedure, why not just move them to the "Inactive Administrators" list and forget about them? Why do they need to be desysoped? Is their tool retention injurious to anyone? And I would understand about the missing summary thing :-( Addendum: And for the record, I didn't "forget" it, some combination of keys and clicks caused it to submit before I had finished writing it... I had written "ore", but wanted to write "More" and somehting got messed up. I know it doesn't matter to anyone, but I was so proud, and it was some freak thing (i.e. not "forgetting") --Mark Neelstin 03:13, 21 May 2006 (UTC)

Well, it's not that it's injurious. It's a point of order. After all, Adminship is not an entitlement, and this should not apply just to users who are not yet admins but want to be. It serves no purpose for the community to have an admin who has said in so many words that s/he doesn't want to be involved with the project anymore. In the odd case that the user should return after a long period (exceeding the waiting period in the proposal), s/he would (should?) have to go through some kind of process to regain admin access (maybe an abbreviated RfA?). It's only fair: if one leaves saying one doesn't cares about the project anymore, then it would be expected that some kind of evidence be provided that the user has gone back on this entirely before Adminship can be restored. Plus, an account with admin access that's been abandoned, left unattended, it's a liability. Maybe not today, maybe not tomorrow. But some day.... Redux 03:38, 21 May 2006 (UTC)

"I don't know of users who have left on the terms I've just mentioned that decided to come back." Hello Redux, nice to meet you, my name is Essjay. Essjay (Talk • Connect) 03:45, 21 May 2006 (UTC)
Did you state for the record (on a wikipedia page — possibly your user page — and not IRC or something) that you were leaving for good and you didn't want to have anything to do with the project anymore? And if you did, you came back a month later, which would be well within the "observation period" before anyone would have suggested that you be desysopped on these terms had this proposal been in effect at the time. That is: nothing would have happened. Redux 03:55, 21 May 2006 (UTC)
Yes, I did. Quite a few people can attest to the fact that I did. I had no intention of returning, and wouldn't have if it hadn't been for about four very close friends I've made here who spent a month having email conversations with me, and my partner, who spent a month trying to convince me that it was worthwhile to do (the same partner who's vote in my RfB was described as "worthless").
My point in this is to point out what people tend to forget: Be very careful what you say, because you don't know who you're talking about when you make a blanket statement. Your comment about admins who leave being undedicated did include me, because it was a blanket statement directed at everyone who fits the criteria stated (desire to permanently leave, coupled with the corresponding action), and it did hurt me, because I don't think I or a lot of the others who fit in the same group you painted with a single brush deserve to be described as "undedicated." I'm not angry, I'm not going to scream and yell, but I am hurt by it; I don't think that was your intent at all, it was an unfortunate consequence of a very broad blanket statement.
My hope was that you would recognize the hint given, specifically, that you were treading into territory where you were very likly to unknowingly hurt and/or offend a lot of people who do a lot of work to keep this site running. It's fine to put forth a proposal, it's fine to support desysopping people, and it's great that you've put a lot of thought into it and made consideration for special cases. The comments in question left the realm of the proposal, however, to make a blanket claim: Any admin who decides to leave the project, and does so, is not a dedicated user. That covers a lot of people, and it hurts.
Just to clarify: It has nothing to do with whether or not the proposal would have applied in my or anyone else's case; it is about the fact that we were included in the group labeled "undedicated users." Essjay (Talk • Connect) 04:16, 21 May 2006 (UTC)

I'm very sorry if I've hurt anyone's feelings, that was certainly not my intention. I'm always very careful with how a word my remarks, exactly because this method of communication makes misunderstandings very easy to happen. Since I seem to have fallen short this time, I would like to clarify a couple of things: 1) From the very beginning, the idea included a waiting period to make sure that the user would follow through with the decision to leave Misplaced Pages. Everyone and anyone is entitled to venting steam, obviously, and in the process we can do and/or say things that we wish we hadn't once we cool off, or at least we reconsider what we've said, and it no longer represents our views. It would be preposterous to suggest that someone should be desysopped immediately after posting a note saying that they were leaving, simply because there's no way to make sure that this is a final decision — and obviously, such a decision is not usually made in a completely serene state of mind; most users do it in the aftermath of a very unpleasant situation; 2) Let me clarify something, I did not mean that anyone who has ever left Misplaced Pages is an "undedicated user". A user who leaves, but decides to return, doesn't become less dedicated because s/he once thought of leaving, or left for a while. It's not like we're getting paid here. And as for the user that left and didn't return, this doesn't cancel the user's past as a valued member of this community. I never saw this proposal as any kind of judgement on the character of anyone who's left. However, and logically, a user who is gone cannot be a dedicated user while s/he is gone — and if they're never returning... Doesn't mean that they weren't, or that they couldn't be again. The comment in question, and all of my comments in this thread, is referring to users who left of their own will and, this is central, stayed gone: taking the already-used example of Optim: he was a great user, and very dedicated; but when I refer to him, I must say that he was a dedicated user, not that he is, since he's gone,and for over two years now. The proposal is to desysop users who are gone and are extremely unlikely to return, but if they happened to return, they would be entitled to seek resysopping of their accounts, naturally. And the idea that they'd need to go through a revalidation process (RfA-like?) is just a suggestion at this point. Maybe no revalidation would be necessary. The user could simply post at the Bureaucrats' noticeboard and link to his successful RfA and the user rights log showing his sysopping following it (proof that he was an admin). And again, this would all be in the odd possibility that the user did return — remembering: this is not about a user who said s/he was leaving but didn't, or returned relatively soon after, this would be users who declared they were leaving and didn't return for an impressive amount of time (six months? a year?).
Once again, I apologize for any offense or discomfort that any comment of mine might have caused. Sorry, this got a little long :P Redux 06:01, 21 May 2006 (UTC)

I don't see any real risk of abuse of old admin accounts, and the costs appear to outweight the benefits IMO. A desysoped admin would still have to rerequest the mop (even if only at the 'crats noticeboard), and this can take time. An admin willing to take up the slack immediately should be able to, and there's no real proof that old admin accounts have gone berserk. (Though this will undoubtedly happen eventually, the chances of it are very remote.) Johnleemk | Talk 08:23, 21 May 2006 (UTC)
Yeah, I don't think this idea of desysopping people who say they they may leave the project will yield any benefits. I am amazed to see how often suggestions involving all kind of rules attempting to fix what ain't broken show up on this page. Oleg Alexandrov (talk) 08:33, 21 May 2006 (UTC)
I would suggest leaving aside the "clear statement" that someone is not returning which I find problematic, and bump the whole thing up to year. Simply, if an admin doesn't edit for twelve months, they get desysopped. And not as a punitive thing but rather to reflect that changes in policy need to be absorbed if such a person came back. An admin returning today after twelve months would think AfD is still VfD, not have a clue about WP:PROD, be unaware of changes to CSD criteria (and the debates behind them), and also know nothing about semi-protect. Perfectly reasonable to say "edit for a month or two and then re-apply if you want". Marskell 08:41, 21 May 2006 (UTC)
Those are minor issues which don't merit desysoping. AfD had a name change, but that's as far as the changes went. (I stopped closing VfDs/AfDs for 1.5 years, and when I came back adjusting to the situation was a snap.) PROD is self-explanatory, and an admin who didn't get it would have the good sense not to muck with it. The CSD criteria may be a bit problematic, but most admins would have the good sense to provide a reason for speedying articles to prevent confusion amongst those unaware of the CSDs. (And besides, what harm would an admin unaware of the new CSDs do? At worst, she'd avoid speedying articles we're allowed to.) And semi-protection? The interface is self-explanatory. A returning admin would just go "Cool, new features!" (The interface doesn't call it "semi-protect", btw - it gives a self-explanatory title listing classes of users which will be banned from editing the page.) None of these changes are fundamental enough to make it worth forcing an admin to go through RfA again. If most admins use common sense and act with the encyclopaedia's interests at heart (WP:IAR/WP:SNOW), things will be fine. Johnleemk | Talk 09:13, 21 May 2006 (UTC)

I believe that, with a waiting period anywhere between six months and a year before desysopping a "departed" admin, the cases of returning Admins (desysopped) would be quite rare. I would also say that this proposal has nothing to do with "trying to fix what is not broken". It's not broken, but nor is it perfect. I don't believe anyone here claims that it is. The purpose is to try to improve the system, and we need not wait until it's on the verge of collapse before we make any kind of change in the status quo.
I maintain that the only people affected by this would be admins who went on the record saying that they were leaving and did not edit anymore, i.e. they left for good (verified by not editing for an impressive amount of time). I wouldn't support desysopping a user who has just stopped editing without any kind of explanation, because, as others have already brought up, there could be any reason for that (sickness, overwhelming "real life" obligations, etc). It's quite different from a user who leaves with a statement like "yes, I'm leaving for good because I've lost all faith in the project". Once we verify that the user is indeed gone, this becomes an extreme case where maintaining Adminship for the account has no purpose. Desysopping in this situation is not complicated or laborous. The criteria are objective and the procedure, not really complicated. Still, it could be a useful step to leave a warning message in the user's talk page, something like "this account is about to be desysopped due to (...)", so that there would still be one last chance in the unlikely case that the user was considering returning.
Again, I'd like to make it clear that the proposal is not to simply desysop inactive users. Only those who left with a declaration that they were indeed leaving for good for whatever reason and, most importantly, stayed gone. Redux 15:45, 21 May 2006 (UTC)

"We need not wait until it's on the verge of collapse before we make any kind of change in the status quo". In short, Misplaced Pages is in grave motal danger, and only rules, and yet more rules, are the only thing which can save her. :)
I believe it is rules, rather than anything else are the greatest problem, they may simply suffocate this project. You may be right, a time may come when a rogue admin or compromised admin account may inflict irreversible damage to Misplaced Pages, such as deleting a huge amount of pictures which were not cached by the server. But that's unlikely. I think we are fine the way we are, and attempts at "perfection" usually make things worse, not better. Oleg Alexandrov (talk) 01:49, 22 May 2006 (UTC)
I really don't believe that not treating adminship like an entitlement would be instruction creep — as a further note: our article on instruction creep is at Meta; on Meta, an admin can be desysopped simply for being inactive for a relatively short period of time; The page on Meta administrators also states that sysop-hood is not a lifetime status. By no measure is that regarded as instruction creep (or else there's a grave double standard at work over there, something which I don't believe anyone would claim). It is a question of policy. As I said in a response to Mark earlier, even if nothing bad is about to happen, there's still a question of logic and organization. This proposal seemed — to me, obviously — rather reasonable because it would concern only an extreme case. I still have other great arguments, but since there seems to be no interest in actually implementing the proposal (except for my own :P), I believe this can be dropped. Redux 05:27, 22 May 2006 (UTC)

I don't see taking admin accounts away from these inactive users as something to pursue. The only real effect I figure it would have is it might deter them from coming back, and we don't want that. I'm much more interested in the idea of having policy enforcement by the community regarding active admins. Everyking 10:39, 22 May 2006 (UTC)

Hmm. I see my name mentioned here.  :) Yes, I was gone for more than a year. I took a long break, got a life (so much for that), and poked around again on Misplaced Pages, noticing that the person who had made life a living hell for me around here was no longer participating as frequently. I felt the time was right to come back. I don't see why somebody who has had the community's support to become an admin loses that support if they take a break for a while. User:Zoe| 18:52, 22 May 2006 (UTC)

I would agree to de-admin someone after a few months of inactivity. There is a small security risk in having an empty empowered account lying around unmonitored. Once an admin comes back, it gives them a chance to get back into the groove of any new quarks that are going on. That person should have plenty of community support and it shouldn’t be a big deal making the request. — Preceding unsigned comment added by Supercoop (talk • contribs)

No, no. It wasn't meant to desysop people who take a break. Only users who declare that they are leaving for good and do indeed leave — as verified by extended absense, for months, or a year, but the user would have had to have made an inequivocal declaration that s/he was leaving for good, with no intention to return for whatever reason. Breaks and "misterious disappearances" were not covered by this proposal. Just to clarify, since the proposal is not going anywhere anyway. Redux 19:23, 22 May 2006 (UTC)
True - I was trying to address the concerns in the entire thread. An admin that leaves is certainly inviting hackers to brute force that users account. However, I would go further and say that after two months of being inactive, that Admin is removed from the admin list. If that users returns within a year or two then automatically re-admin that person. After a year or two, too many things can change and that would require getting back into the groove and going through a new RfA. (make sure I sign it this time) --Supercoop 20:50, 22 May 2006 (UTC)

I know this discussion has wanned, but perhaps there could be some middle ground. What if instead of desysopping anyone, the accounts were just blocked (hear me out) with a note placed on their talk page to the effect of "your dormant admin account may have been a liablility, and was therefore blocked. If you would like to be reinstated place {{adminunblock}} (or whatever) on your talk page and it will be dealt with." That way we don't have an admin come back and just start deleting things, etc. The actual process could be changed up a bit, but perhaps the idea is valid. Comments? --You Know Who 17:05, 23 May 2006 (UTC)

I'm in favour of not removing sysop rights unless some transgression has occurred. Is there an actual case where this rule would have been useful? Or is this just a rule for the sake of it? Stephen B Streater 17:33, 23 May 2006 (UTC)
A standard block has no effect on an administrator. The only way to shut off their sysop powers is to remove those powers. Ingoolemo  17:39, 23 May 2006 (UTC)
So are there any cases where this would have been used? Stephen B Streater 17:50, 23 May 2006 (UTC)
You mean if there are cases of admins that have been inactive for an impressive amount of time? Several, if not many. But as Ingoolemo said, technically, a standard block is not effective on an administrator. Redux 17:58, 23 May 2006 (UTC)
No - I mean cases where an absent admin has returned to wreak havoc. Stephen B Streater 18:00, 23 May 2006 (UTC)
D'oh. I was confusing what the devs had put in place. Didn't the devs a while back put a feature in so that admins who were blocked couldn't use rollback? Well, I guess I thought that meant they couldn't perform other admin functions as well. But of course. My mistake. --You Know Who 19:38, 23 May 2006 (UTC)

Ah, ok. I can't remember any instance, but the underlying purpose would be prevention, not punishment. Besides, as I see it, the real danger would be that an account that has been abandoned is an account that could be hacked. That is to say, a different individual behind the wheel. Someone who never earned adminship having instant access to the tools. I mean, if my account was hacked tomorrow, I'd notice immediately, since I log in at least once a day. I would take steps to resolving the situation, but a person who's left completely would not be here to inform us that it is not him or her opperating the account. Once more, I must bring back the notion that the original proposal I presented would affect only accounts whose owners had made an inequivocal declaration that they were leaving with no intention to return, and did indeed leave (impressive absence, i.e. no editing for a long time). I believe it would be reasonable to assume that an account in that situation has been left completely unatended. And, from the logical point of view, there's the lack of purpose in maintaining admin access for an abandoned account. Redux 18:13, 23 May 2006 (UTC)

I have to admit this is convincing. I would like a simple re-admin procedure for former admins to reflect their previous contributions and likely helpful future contributions. Stephen B Streater 18:25, 23 May 2006 (UTC)

Administrator Review

My apologies if this has been brought up before, or already exists, but what about an administrator review? Within six months, a new admin is brought under review by a pre-selected group of experienced admins/bureaucrats, and they discuss what this user has done since they were sysopped, and whether that user should continue being an admin. They will be reviewed again in six months, and all active admins will be reviewed once a year after that. Emergency reviews can be held as well. I think this would help keep the number of rouge admins to a minimum. Thoughts? --D-Day) 12:03, 20 May 2006 (UTC)

This is a solution looking for a problem. Show me evidence that we need to spend our volunteer's time on this proposal. FloNight 12:17, 20 May 2006 (UTC)
If you have a look at admin disputes at Rfc and ArbCom, I think you'll see where I'm coming from. Plus there have been concerns over Admin actions in the Userbox debate as well. --D-Day) 12:21, 20 May 2006 (UTC)
  • Sure, and handled by ArbCom for the most part. Also, such a body would have to review >900 admins per year. That's a huge body of work for little gain. I agree; this is a solution looking for a problem. --Durin 12:46, 20 May 2006 (UTC)
How would this review have prevented such disputes? We're letting the wedge cases define how we deal with the vast majority of admins whose actions are uncontroversial. In any case, unofficial reviews of individual actions often go on at AN or ANI; I see no need to bureaucratise this. Johnleemk | Talk 12:51, 20 May 2006 (UTC)
We didn't elect bureaucrats to be ArbCom members (except those few who we actually did elect to both positions). Keep bureaucrats for the front end job of creating admins, and leave it to ArbCom or Jimbo to uncreate them. NoSeptember 13:12, 20 May 2006 (UTC)
Uh...I don't think D-Day suggested 'crats would be in charge of desysoping. Anyway, I'd favour giving them such powers for emergency disputes, but as Essjay and Raul have noted above, it seems it'd be easier to attract Jimbo's, a steward's, or a dev's attention. Johnleemk | Talk 13:15, 20 May 2006 (UTC)
Yes, the more people who have emergency desysop powers, the more problematic it will be. Even Danny and Jimbo did not perfectly coordinate the Eloquence situation. There is always someone around as it is now. NoSeptember 13:44, 20 May 2006 (UTC)

What's wrong with ArbCom? Is there something about it that doesn't work and I'm completely missing? As far as I can tell, a system of Admin review already exists - people complain, take it to ArbCom, they review it and act accordingly. If ArbCom is somehow broken, then that's a completely different discussion and should be held over there. --Tango 15:52, 20 May 2006 (UTC)

I think the complaint is that the arbcom doesn't get a case till long over it's gone over the edge and it takes a blatant act of insanity or massive violation of policies and guidelines before the arbcom or anyone else for that matter acts. Pegasus1138 ---- 15:57, 20 May 2006 (UTC)
If people have a problem with that, why don't they bring cases to ArbCom sooner? Are ArbCom actually refusing to hear the cases, or are they not being told about them? --Tango 16:13, 20 May 2006 (UTC)
I think it's a little of both, for good reasons the arbcom is afraid of accepting cases too early when there are better solutions possible and instead it seems like they're accepting some of them only after the damage has been done. On the other hand people are also reluctant to bring up arbcom cases until all else has failed so the arbcom either doesn't know about it or they more likely know about it due to discussions on AN, AN/I, or any number of another places but can't do anything about it until it's brought up officially as a case. Pegasus1138 ---- 16:34, 20 May 2006 (UTC)
While there's certainly a perception that that is the case, I think reality is very different. Name me one blatant mop abuser who hasn't been hauled in front of the arbcom. Also, the arbcom can (and often does) issue temporary injunctions during the period of the case which prevent further action(s) being taken, so if a case is accepted, the accused admin will typically be placed on admin action parole or something of the sort for the duration of the case. Johnleemk | Talk 16:27, 20 May 2006 (UTC)
First of all, the prospect of reviewing the nearly 1,000 admins on Misplaced Pages every 6 months would be a full-time job. Beyond that, is there really a need? Do you feel there are a sizable amount of inept admins that are running around blocking and deleting out of control? Furthermore, this would start to encourage further encourage people to play politics, which there is enough of already. --tomf688 (talk - email) 02:06, 22 May 2006 (UTC)
Essentially, this proposal is to scrap tenure for admins and up- a system which has both considerable benefits and drawbacks (much as in the academic world). I haven't seen a persuasive toting up of the pros and cons in favor of making the switch. --maru (talk) contribs 04:58, 22 May 2006 (UTC)
In the end, this (and most proposeals like it) are probably all created with the same very small set of admin in mind. As much as I call for volountary admin reform, three cases (or five, or pick your own small number) almost certainly isn't enough reason to re-wash every other good, average, or null admin. Working the existing system combined with ArbCom being slightly more willing to slap down is probably all that is required. - brenneman 11:34, 22 May 2006 (UTC)

But... I LIKE Rouge admins. Kim Bruning 03:27, 23 May 2006 (UTC)

Demandation

You know, I am still waiting for my own Adminship!
All the sweet and good edits I have been doing!
I need a adminship, when I have one, I can be get the respect I need!

>x<ino 17:05, 20 May 2006 (UTC)
If you're really serious about that, then simply follow the instructions. Given your past and on-going conflicts with other users, I personally doubt that an attempt would be successful though. -- g026r 17:28, 20 May 2006 (UTC)
Ugh. These 4 lines scream to me "Do not make me an admin, I'm immature." Period. You don't become an admin to "get respect", you have to be respected before you become one. Kimchi.sg 18:12, 20 May 2006 (UTC)
I concur. I feel somewhat the same way, but I don't feel the need for more respect from other users. Whatever they give me (if they do...) is fine with me. Also, "be get the respect" is awful grammar. --M1ss1ontomars2k4 | T | C | @ 04:14, 21 May 2006 (UTC)
Several reasons I would vote no if you were nom'ed: "Demandation" is not a word; this edit violates WP:CIVIL and WP:NPA; and it seems that the only reason you want to be a mod stems from these three edits. Want respect? We'll give it when you earn it. Want adminship? Show us that it's about the encyclopedia, not about you. RadioKirk talk to me 18:40, 20 May 2006 (UTC)
Two more reasons why Xino will not be an admin any time soon... RadioKirk talk to me 20:54, 20 May 2006 (UTC)
Xino is this some kind of joke? Sonic Hog 22:34, 20 May 2006 (UTC)
I'd like to point out the RfC regarding Xino, which contains a somewhat clearer description of his behaviour than the links already presented. I'm guessing Xino wants to become an admin so he can block and/or ignore other users, and myself. RandyWang (/rants) 01:09, 21 May 2006 (UTC)
Yes, this certainly explains a lot, thank you. On the other hand, this edit provides new insight into User:HappyVR... RadioKirk talk to me 01:55, 21 May 2006 (UTC)
Agreed: it certainly does. RandyWang (/rants) 02:01, 21 May 2006 (UTC)

And what would you all think, feel and say when I am a admin? It will be a L.O.L in your face and asses.

And as for you RandyWang, you can suck that RfC in your cheap skinny ass!

>x<ino 08:55, 22 May 2006 (UTC)
Really? What exactly are you planning to do "when I am a admin"? RadioKirk talk to me 13:18, 22 May 2006 (UTC)

Hmmmm- the way we've been voting on "indecorous language" issues, you might want to rephrase . . . Cheers :) Dlohcierekim 09:00, 22 May 2006 (UTC)

Xino, your case has been submitted for arbitration. Now may not be the most appropriate time to make personal attacks - particularly, it may be a bad idea to suggest that I suck anything, RfC or otherwise. Furthermore, as others have said: if you'd like to become an admin, and believe that you'd be successful, why don't you request adminship for yourself? RandyWang (/rants) 09:55, 22 May 2006 (UTC)
Xino was blocked indefinitely after this edit. Conscious 19:49, 22 May 2006 (UTC)

Demandation. You know, I like that word. I may have to start using it. "My demandations have not been met, prepare to face my wrath!" User:Zoe| 22:09, 22 May 2006 (UTC)

Ut oh. Zoe and a new shiny word. :-) Kim Bruning 03:30, 23 May 2006 (UTC)

Templates for Adminiship

Are these templates valid? I remember such things being deleted on TfD several times before:

70.51.9.190 19:41, 20 May 2006 (UTC)

I don't see why they would be invalid they're perfectly acceptable and are quite informative in knowing who isn't an admin but wants to be one. Pegasus1138 ---- 20:00, 20 May 2006 (UTC)
IMO, if someone needs to advertise their hope to be an admin, they're not ready. Either wait for someone to nominate you, ask someone to nominate you, or nominate yourself. — Ilyanep (Talk) 01:19, 21 May 2006 (UTC)
By the same token, perhaps {{User wikipedia/Anti-Administrator}} would be inappropriate either, considering that no one has to accept nomination, and the RfA doesn't even gets listed unless the potential candidate accepts. In theory, no one needs to post that they "don't want to be an administrator" via a template. Redux 01:38, 21 May 2006 (UTC)
I think people who use the anti-administrator template due it less as an informative action that they don't want to be an admin and more of a sign of protest against adminship and the admin process itself... just from where I've seen that template used. Pegasus1138 ---- 03:48, 21 May 2006 (UTC)

I don't think they do any harm, but they don't serve any real purpose. It's basically the same as asking someone to nominate you, which I don't like - you might as well nominate yourself and they can vote support, because it's the same thing. It's just an attempt to manipulate RfA since a lot of people are more critical of self-noms. --Tango 10:29, 21 May 2006 (UTC)

Agreed. I guess maybe some people who would like to be admins but don't feel they are ready would find the templates useful, but that's about it. Johnleemk | Talk 11:09, 21 May 2006 (UTC)
They might also be useful for someone who is often confused with an admin, would, as Johleemk says, like to be one someday, but is not for whatever reason, ready or able to stand for RfA. I can imagine that the 30th "You aren't an admin? Would you like to be?" message probably leads one to really appreciate such a template. For the most part, they aren't hurting anyone, they're not being forced on anyone, and nobody is required to look at them (for that matter, if someone *really* hates it, we can set a div id for it and clear it out via thier CSS). In most cases like this, it's better to just leave it alone, rather than stir people up by telling them what they can and can't have; I don't think any of us can really argue that it's hurting Misplaced Pages, and certainly not anywhere near as much as a revival/ratcheting up of the user template war would. Essjay (Talk • Connect) 11:28, 21 May 2006 (UTC)
In that case revise the wording to "No, I am not an administrator yet. Yes, I would like to be one. Stop asking!" :P — Ilyanep (Talk) 03:28, 23 May 2006 (UTC)

Misplaced Pages:Requests for adminship/Jesus on Wheels

Can a 'crat please close this? It wasn't on the main RFA page and needless to say the candidate will not pass. DGX 19:23, 22 May 2006 (UTC)

I was BOLD and delisted this as WP:SNOW and probable trolling. But yes, a crat should probably close it, or perhaps just delete it. --Doc 19:32, 22 May 2006 (UTC)

Deleted. Essjay (Talk • Connect) 00:51, 23 May 2006 (UTC)

Agreed. Restore and archive. RadioKirk talk to me 13:19, 23 May 2006 (UTC)
Agreed. Undelete it. --Tango 15:55, 23 May 2006 (UTC)
Agreed, I heartily endorse this event or product. While he's been warned about the dangers of having a username like that, he should still be allowed the rights of a normal editor, albeit one who will tend to be watched a little more (like another user who had "WOW" in his name, WOW junkie or something like that). In fact, as of now, he is still indef blocked for his name. Looks like the blocking admin isn't online right now, but I don't know if I want to wheel war over this. I'm going to post on WP:AN about this case. --Deathphoenix ʕ 17:03, 23 May 2006 (UTC)
I've undeleted. I don't know exactly what archiving old RfAs entails, so I've not done that. -lethe 17:01, 23 May 2006 (UTC)
Fine, duly chastized. Will find something else to do. Essjay (Talk • Connect) 20:09, 24 May 2006 (UTC)
  • It's constructive criticism, meant in good faith. Please take it as such. I well recognize that bureaucrats tend to be targets of complaints. The above isn't a complaint per se, but more a request that we handle that situation differently. --Durin 13:02, 25 May 2006 (UTC)
It's the wiki concept working at its best - Essjay boldly deleted it, it turned out concensus disagreed, someone undeleted it and no harm was done. Perfect. The whole point of a wiki is that nobody is perfect, so we work together to achieve something closer to perfection. --Tango 13:13, 25 May 2006 (UTC)
Absolutely. :) RadioKirk talk to me 13:43, 25 May 2006 (UTC)
I'm glad so many agree. I guess I'm off the hook for reversing this bureaucrat action without telling anyone ;-) (yes, this is tongue in cheek) NoSeptember 14:00, 25 May 2006 (UTC)

Snowballing

I was just wondering yesterday if any RfA had ever met the 80% OPPOSE mark. Right now there are two that have gone way beyond. One candidate does not respond. The other is RIGHT and refuses to withdraw. Why would the ‘crats not pull such lopsided RfA’s? :) Dlohcierekim 16:06, 23 May 2006 (UTC)

  • Plenty of RfAs have had more than 80% oppose. Quite a number have had 100% oppose. There's been 60 since June of 2005 that have had 100% oppose. Of those 60, 23 have had 10 or more oppose votes. In general, there are a number of reasons to not withdraw clearly failing RfAs (see User:Durin/Withdraw policy for some). Some bureaucrats choose to withdraw clearly failing RfAs anyways. --Durin 16:17, 23 May 2006 (UTC)
I think this has been discussed earlier but I really feel there should be a basic standard for RFA candidates. Probably like 1000+ edits and atleast a month of Misplaced Pages activity. Otherwise we have WP:SNOW cases like Misplaced Pages:Requests for adminship/Piemanmoo occuring all the time. Thanks. Srikeit 16:33, 23 May 2006 (UTC)
  • This has been discussed more times than we can count. The general consensus has not been supportive enough of such ideas to implement them. Also note that WP:SNOW is not policy. --Durin 16:37, 23 May 2006 (UTC)
RE:User:Durin/Withdraw policy That's pretty much what I thought. I just feel sorry for the guy who is so caught up in his own rightness that he won't withdraw. Hopefully, he will listen and use it all constructively. Cheers. :) Dlohcierekim 16:41, 23 May 2006 (UTC)
I generally pull any RfA that has more than 10 votes, and 75% or more oppose. I will, however, leave a nomination for a bit if it hasn't had much time up, as there could be some issue that can be resolved and things will straighten out. I'm the only bureaucrat I've seen lately doing this on a regular basis; I don't know if the others aren't comfortable doing so, or if I just end up getting there first, or if I'm just not seeing them. Essjay (Talk • Connect) 20:05, 24 May 2006 (UTC)
I'll remove them early, but only if there are enough supporting factors that I can be confident they have no chance of succeeding. I consider most of the points Durin has outlined, and if there is evidence that the user and the community will not benefit from leaving it open, I close early. For example, a nominee with very little experience and recent vandalism, being blocked, or incivility or similar in the Rfa or extreme examples elsewhere. So typically that's going to involve few or no supports from at least somewhat experienced wikipedians and lots of opposes from similar. If those factors aren't too severe, I'll leave it for a while until the lack of a chance for success is clear, but in very obvious vandal nominations, I've closed them pretty quickly. - Taxman 20:22, 24 May 2006 (UTC)
I personally don't agree with the view that leaving them open is more beneficial than closing early, especially if it means losing good contributors, which it often does. RfA is not Misplaced Pages:Requests for Review of my general worth as a contributor and perhaps adminship but I really don't think so but great if it happens. It's for requesting adminship, period, and that's all it should be doing. Essjay (Talk • Connect) 22:08, 24 May 2006 (UTC)
  • I've been accumulating evidence on the page I referenced above showing that some users are upset about early removal. I'd like to see similar evidence (Yes, I know it exists) that we're forcing users away by leaving RfAs up, rather than making the presumption that it always happens. Personally, I still do not see the harm in asking the user to please withdraw, rather than slamming the door in their face in non-obvious vandalism cases. --Durin 12:59, 25 May 2006 (UTC)
While it's not a heavily used program at this point, users who are looking for feedback might be directed to Misplaced Pages:Editor review instead of using RFA for that feedback. NoSeptember 20:32, 24 May 2006 (UTC)

Quick Question

Why hasnt a bureaucrat closed Joturner's RFA? Its now twelve hours overtime, and oppose votes are now piling on from all directions. However if discounting the votes that were made after the ending time, he should be promoted, right? (It has been done in the past). Oran e (t) (c) (e) 20:43, 24 May 2006 (UTC)

Please see the BCrat's noticeboard for relevent discussion. --You Know Who 20:52, 24 May 2006 (UTC)

Sockpuppetry at Cool3's RfA

Just alerting RfA watchers regarding ongoing sockpuppetry at Cool3's RfA; copying the note I left there below:

This RfA has been voted on by three users with under a dozen edits -- Y-y-yoda (vote), David-wright (vote), Vandal buster 288 (vote) -- one of which has the same userpage styling as Cool3's previous RfA nominator (compare User:ErnestIsTheMan with User:Vandal buster 288).

~ PseudoSudo 00:05, 26 May 2006 (UTC)

Note that we shouldn't jump to conclusions that the nominee is the one with sock puppets; another RfA also had an issue and was confirmed via CheckUser that the candidate had nothing to do with it. Thanks! Flcelloguy (A note?)
For the record, I note that the aforementioned userpage styling is common among new users and retract any connection I may have implied regarding Cool3's involvement in the matter. ~ PseudoSudo 19:36, 27 May 2006 (UTC)
By the way... this is linked to the Exicornt vandal and EddieSegoura, from what I understand of it. See also WP:ANI. NSLE (T+C) at 06:09 UTC (2006-05-26)
In this, Checkuser confirmed sockpuppets. See the report here. --Calton | Talk 06:38, 26 May 2006 (UTC)

Code problems

I just noticed a few minuutes ago that all of a sudden, an unknown force (can't find anyone in the history) nowikied the "Discuss Here" edit link so that it wouldn't work. I was wondering if I'm just going crazy or if some new software or something is being implemented. Thanks, Master of Puppets 13:03, 26 May 2006 (UTC)

It's working fine now. I'm not aware of any reason that could have caused a temporary problem. Maybe your browser is rebelling against you? ;) Redux 13:18, 26 May 2006 (UTC)
No, because all of them had mysterious <nowiki>s in the edit link. When I edited that out, it went away. Strange. Master of Puppets 13:20, 26 May 2006 (UTC)
Indeed. I had thought that whatever it was had gone away on its own. Now, going through the histories, I see you fixed it. Very strange indeed. If it was a transcluded template, I'd say someone had edited it, but that's not the case. It's as if someone had edited each RfA to add the nowiki code, but the history doesn't show it. I'll have to ponder a bit more about this one. But it is odd. Redux 14:39, 26 May 2006 (UTC)
Didn't you know, Misplaced Pages is haunted. you just had a sighting ;-). NoSeptember 14:44, 26 May 2006 (UTC)
Spooky. <8O Redux 15:32, 26 May 2006 (UTC)
Maybe the code Misplaced Pages runs on changed or something, and it just did that involuntarily. I'm no programming whiz, but as all of them changed at the same time and there is no history of it, I'm thinking something internal. Notified Rob Church to see what he thinks. Master of Puppets 16:01, 26 May 2006 (UTC)
It's not odd, it just appears that people are forgetting to follow step 2 as per WP:RFA/N. So, it's not that the <nowiki>'s were put in, it's that the nominator forgot to take them out in the first place. (And I don't think you can take them out in the original {{rfa}} template, as if you do, the subst's for date/time/and name will be done at that point, which isn't what we want) Regards, MartinRe 16:17, 26 May 2006 (UTC)
I don't believe that that's what happened here, though. If the nominators/candidates had forgotten to adapt the code, the links would have been missing from the start. But they weren't. It was all fine until all the links were disabled at once, it seems. As Master of Puppets said, this was most likely something internal that inserted the code in all the links simultaneously — or it's the ghosts of Misplaced Pages playing a trick on us *shivers* ;) Redux 17:07, 26 May 2006 (UTC)
Very curious. I did notice something when I was glancing through the histories, namely that {{fullurl: acts differently in depending on if it's in called in /w or /wiki (e.g. vs {{Rfa}}, even though they are the same version. I'm guessing from the examples in m:Help:Variable that a {{fullurl: with parameters will adjust the url from /wiki to /w in order to edit, so I don't know what it's supposed to do on a page that's already /w. (it currently breaks the link, which is what was reported here, so I wonder if they are connected. I must keep an eye on the technical list archives, I hate unsolved riddles! :) Regards, MartinRe 00:49, 27 May 2006 (UTC)
It's most likely this. Titoxd 06:00, 27 May 2006 (UTC)

Duplicate voter reporting bot

I've wrapped up my RfA Analysis tool (see the archive) in a bot. Basically, it uses the same functions as the tool to analyze all current RfAs at specific intervals (once every 3 hours or so), and posts the results at User:Tangotango/RfA Analysis/Report, in a similar fashion to User:Dragons flight/RFA summary. It doesn't make any edits elsewhere, and all the nominations are downloaded in a single export operation, so server load shouldn't be too high. I have two uses for the report in mind: transclusion in Misplaced Pages:RFA summary, or watchlisting by users interested in weeding out duplicate votes. I also hope it will be useful for bureaucrats. The bot isn't automatically triggered at the moment - may I have some feedback before embarking on that? Cheers, Tangotango 15:05, 26 May 2006 (UTC)

Depending on your code base, it might make sense to merge our two products and do everything at once? I am presently doing everything in Python. Dragons flight 15:37, 26 May 2006 (UTC)
I had the same thought, but unfortunately I'm using PHP. I'm wondering whether it's possible for my bot to fill in the extra columns (Possible duplicate voters and Details) after your bot's done its work. In any case, the code for my RfA Analysis library (which the toolserver tool and the bot share) is available here. Cheers, Tangotango 16:44, 26 May 2006 (UTC)
If you don't merge, then run your bots at different times (one at the top of the hour, one at the bottom of the hour, for example) so we can always get up to date info :-). NoSeptember 16:53, 26 May 2006 (UTC)
But if you do that, the bot that runs at the bottom of each hour and that at the top of the following hour will be way too close together (except for the top of the very first hour). I don't suppose we need so many updates.. Redux 17:12, 26 May 2006 (UTC)
New RfAs (in their first day of listing) pick up votes very quickly, and one never knows just when one wants to check the current status of RfAs. So why not have frequent updates? It's not a big strain on the servers. NoSeptember 17:34, 26 May 2006 (UTC)
I must say you have done a wonderful job creating this tool. There must be a bunch of relieved bureaucrats sitting now that they don't need to go over every RFA with a magnifying glass. Anyway there are still a few places the tools goes haywire, although I don't think there can be much you can do about it.
  • Here in Zappa.jake's RFA User:TBC's (3rd) oppose vote gets a "Sig not found" as he has written out a list of reasons to oppose.
  • Here in Compuerjoe's RFA User:Admrboltz's sig (12th Support) just doesn't register. I guess this is because of his sig having some formatting problems.
  • Here in Bookofjude's RFA User:Mboverload's vote (124th Support) gives the dreaded "Sig not found" as he didn't sign his initial comment but indented another comment & then signed it.
Anyway I hope you don't mind me nitpicking here, but I feel you have made a fine tool here & I really want to help you make it better. The bot is an excellent development. I've already added a link of that to my page. Although does the orignal tool also have a replication lag? Because I wall analysing Axiomm's RFA & as of now (17:47, 26 May 2006 (UTC)) it says that I'm the only neutral voter, whereas actually User:Gurch has also voted neutral. Anyway thanks again. Srikeit 17:47, 26 May 2006 (UTC)
So, this has all been a plot to fool us into thinking we don't need bureaucrats anymore. Aha! It won't work, a bot can never take over the job of a bureaucrat. This evil plot will never succeed ;-). NoSeptember 18:04, 26 May 2006 (UTC)
Thanks for all your comments. Srikeit, thank you for your continued interest in RfA Analysis :) I've fixed Admrboltz's signature handling issue. I'm well aware of the other two errors - they're caused by the user inserting a newline before their signature. I am not sure whether to deal with this as they could easily well be comments by different people - especially in Mboverload's case, the extra indentation appears as if somebody else added the comment in response to the original one. As for someone like TBC who writes a lot on one RfA, it's unlikely that they will accidentally vote again on the same one. (Yes yes, these are poor excuses ;)) An "unsure but possibility of duplicate vote" flag might be in order.
As for the lag Srikeit cites, there is no replication lag with the toolserver tool. (it doesn't use the toolserver database) I'm not sure what caused the issue - if it happens again, please let me know.
NoSeptember: A historical version of all RfAs sounds interesting. But, as you say, I'll need to fix up the signature handling before doing that. P.S. I've moved the source to - live versions of the source will appear there now -- Tangotango 05:19, 27 May 2006 (UTC)
I've just voted in Brendenhull2's RFA. The tool has not yet registered my vote as of now (05:37, 27 May 2006 (UTC)) . Check it out quick you may catch it! ;) Srikeit 05:37, 27 May 2006 (UTC)
Source retrieval function changed to use Special:Export. The lag should be fixed. (I hope) — Tangotango 06:04, 27 May 2006 (UTC)
New reports will now use shades of colours to represent the various percentages. A list of colours is available here. - Tangotango 15:38, 27 May 2006 (UTC)

Voting icons

Apparently voting icons are appearing on RfAs (e.g. Image:Symbol support vote.svg). They seem relatively rare right now, but if AfD is any indication, and I'm sure it is, they'll be all over the place in a few days. On AfD they were pretty effectively nipped in the bud as soon as they started becoming omnipresent. I do recall they've been rejected in the past... I think people might want to think twice before jumping on this bandwagon. --W.marsh 16:47, 27 May 2006 (UTC)

Just a reminder for those who weren't here the last time icons were brought up—here's why icons are discouraged at RfA:
  • They're annoying to editors with slower computers (adding hundreds of graphics to a long page can make page rendering and scrolling take a very long time, or just crash altogether).
  • They're an unnecessary use of bandwidth. User-side caching tends to limit the impact here, but why use it when we don't have to?
  • Icons are pointless on this page, since votes are already sorted into support/oppose/neutral sections.
  • Focusing on the voting aspect of the RfA rather than the discussion is discouraged from a philosophical standpoint.
TenOfAllTrades(talk) 17:09, 27 May 2006 (UTC)
On the plus side they are pleasing to the eye, like oasis among the bare sands of plain text.  Grue  17:33, 27 May 2006 (UTC)
Once every vote has them, they will be far from pleasing or an oasis among the sands filled with murky waters of blue, green and red mathematical symbols used to denote one's approval or disapproval of a particular candidate. Johnleemk | Talk 18:07, 27 May 2006 (UTC)
I hate them. Let's get rid of them, quickly. Fut.Perf. ☼ 18:20, 27 May 2006 (UTC)
I'm new to RFA, but I'm already against them. They bring out some comments more than others (but not in a way which depends on the merit of the comments), and don't work properly on my mobile phone. Stephen B Streater 19:01, 27 May 2006 (UTC)
PS I think the interesting names are OK because they are not aligned on the left hand side a the start of each comment. Stephen B Streater 19:03, 27 May 2006 (UTC)

On a related note - why do we say Support when it's already under a support header? "Strong Support" and "Weak Support" might be useful (people disagree), but "Support" adds absolutely nothing... I don't think there's any real way to change it - "old habits die hard"... How did it start, anyway? Just a hang over from pages that don't separate votes? --Tango 23:00, 27 May 2006 (UTC)

It has always been part of RfA tradition! Maybe if we stop, just writing a reason for support/oppose then the four tildes, it will spread across all users! Gizza 23:17, 27 May 2006 (UTC)
Don't break tradition! :-) Just keep the bold text and abolish the voting icons. They are really annoying. —Mets501 23:37, 27 May 2006 (UTC)
Um, who says the "vote" has to be bolded? There's no reason to, in fact, except to encourage the idea that RFA is a straight numbers count. Nobody has to add any sort of formatting to their comment.--Sean Black 01:39, 28 May 2006 (UTC)
I too am opposed to a widespread use (or any use, for that matter, although sparse use is...sufferable) of those icons, but how could we prevent its widespread effectively without entering the much-dreaded helm of instruction creep? Redux 02:38, 28 May 2006 (UTC)
I think the only solution that doesn't involve instruction creep would be to wait and hope they don't become widespread. I don't see any other way to avoid it... Fetofs 02:53, 28 May 2006 (UTC)
I never bold support or oppose, if I use those words at all. Instead, I leave a brief comment or explain the rationale for my vote. Johnleemk | Talk 10:09, 28 May 2006 (UTC)

Remove every voting icon you see and leave a message on the user's talk page telling them to knock it off. There aren't too many of them doing it yet. --Cyde↔Weys 02:58, 28 May 2006 (UTC)

I personally don't mind them; as long as everyone is not doing it, its ok. But I agree with Fetofs; we should probably just wait until the trend dies off. Master of Puppets 03:01, 28 May 2006 (UTC)
I too agree with Fetofs. This discussion itself lets people know that the use of these voting icons is discouraged. The users viewing this, in most probability, will not use them in the future. Rather than getting into a conflict, we can wait for the trend to wear off. It isn't very widespread now anyway. Srikeit 03:39, 28 May 2006 (UTC)
You pointed out my ideas better than myself :) Fetofs 13:15, 28 May 2006 (UTC)

Just be careful, when purging, to be nice in the way you do it. Those icons *are* standard other places, like Commons, and people who are more familiar with RfA there may use them by default, without realizing the vehement opposition of this community. Essjay (Talk • Connect) 05:20, 28 May 2006 (UTC)

In fact, they seem to be used everywhere except English Misplaced Pages.  Grue  09:22, 28 May 2006 (UTC)
They're not that standard on Commons, AFAIK. Most places where I've come across them, at the most half of all votes have them. Johnleemk | Talk 10:09, 28 May 2006 (UTC)
I was thinking of Template:Administrators/Requests_and_votes, the Commons equivalent of RfA...I see almost 100% use. Essjay (Talk • Connect) 10:21, 28 May 2006 (UTC)

I'd shy away from actually removing them from existing comments. Altering of signed comments really is an extreme step, and I know I don't take it very well. However, a nice clear note on the user's talk page about why it's not-so-good has almost always worked for me. I've had on more than a few occasions people I left such notes with turn around and ask other people not to use voting symbols. No reason to play the hard man and get people's backs up when there's no reason to. - brenneman 10:31, 28 May 2006 (UTC)

I believe that the icons are being used only sporadically around here as of yet. There's no reason for us to start worrying too much about it now. Unless it becomes a real issue, with a significative number of people using them to post here, we needn't be coming up with orchestrated manners of dissuading those few who do for whatever reason lest it becomes instruction creep. There doesn't appear to be reason for us to go as far as altering other users' comments at this point. Redux 11:57, 28 May 2006 (UTC)
Looks nice, but for me this is really a matter less of reading but of writing. I don't want to have to remember any more code than the three apostrophes in order to be able to vote anywhere. '''Support''' is just the maximum number of keystrokes I'm willing to invest, and I'd hate to have to remember anything more, be it the name of a template, or the name of an image, or html code, whatever. And I want to see clean text in the edit window too. Fut.Perf. ☼ 12:38, 28 May 2006 (UTC)
The idea was never to make icons mandatory for participating in RfA. It was in the sense of whether icons should be banned or tolerated, but the bottom line is that there is no fix format for participating in RfA. The three apostrophes themselves are about tradition, or praxis, but no one has to bold the first word of the entry for it to count. Trying to impose a format for participating would be classic instruction creep. Redux 12:49, 28 May 2006 (UTC)
See my response to Grue above. It looks tacky and gets on your nerves once every vote has it. Johnleemk | Talk 14:37, 28 May 2006 (UTC)
What is the purpose of images next to the votes anyway? The bolded Support or Oppose should be sufficient. It seems quite contradictory to me to discourage the use of images in signatures partially since they clutter the page, but allow vote images that, well, clutter the page. joturner 14:45, 28 May 2006 (UTC)
-

I can't believe, 4 years after the arrival of broadband, Misplaced Pages is still worried about bandwidth. Nathan is an angel.

+

Anwar 15:31, 28 May 2006 (UTC)

I, and presumably you, and many Misplaced Pages users are fortunate enough to have broadband. Plenty of people don't. There's no reason to make it harder for non-broadband users to participate in RfA. I agree, "support" or "oppose" is more than sufficient. FreplySpang 15:51, 28 May 2006 (UTC)

Early Close Guideline Proposal

I have drafted a guideline that will help bureaucrats make decisions about when RfA's should be closed early. This is in response to the community becoming divided as to whether bureaucrats should close RfAs early and at what stage they should be closed. The proposal is here. DarthVader 22:31, 27 May 2006 (UTC)

Proposal for quasi-protection

(Apologies, but I feel like because this proposal tangentially deals with RfA, I should bring it up here. Thanks!) Hello, all: I've written up Misplaced Pages:Quasi-protection policy, a proposal similar to semi-protection that would effectively limit sleeper accounts used to vandalize articles linked from the Main Page. I know that I've written a lot, and at first glance, the proposal may seem daunting. However, I truly believe that this would immensely improve Misplaced Pages and implore you to read it through and offer your thoughts on the talk page. Thanks! Flcelloguy (A note?) 22:50, 27 May 2006 (UTC)

Misplaced Pages:Requests for adminship/Zappa.jake

(Have made this subsection an indented section of the QPP due to possible application of QPP to cases like this in future...)

I've taken the step of semiprotecting this RFA, due to ongoing AOL IP vandalism that continually forges signatures and votes. It's gone on since the start of this RFA. The last time I did this (Quadell's RFB), I was criticised, but here I don't think there's a better way to deal with this vandalism. NSLE (T+C) at 03:49 UTC (2006-05-28)

I don't think the result will be controversial on this RfA either way. Stephen B Streater 08:54, 28 May 2006 (UTC)

Closure of RFAs by non-bureaucrats

I would like to point out that, although it has become rare, non-bureaucrats are permitted and indeed encouraged to close nominations that clearly lack community support. They are also permitted to close borderline cases after several days have elapsed and no bureaucrat has chosen to promote (though currently this never happens). Bureaucrats are given the exclusive authority to promote successful candidates. While we can and often do remove failing nominations, the community at large still has the right to do this as well. The Uninvited Co., Inc. 11:51, 28 May 2006 (UTC)

New: when should I start?

I have been using wikipedia for months, but registered only yesterday, and have around 60/70 edits only. When I shall be ready to participate in RfA? Please give me an idea. Thanks. --Bootblack 17:32, 28 May 2006 (UTC)

See WP:GRFA and Misplaced Pages:Requests for adminship/Standards. Also, showing a lot of early interest in becoming an admin is a red-flag for many people. —Bunchofgrapes (talk) 17:35, 28 May 2006 (UTC)
Well, if you're voting, start at about 125 edits. If you're running, wait until about 2,500 good edits if you're nominating yourself, or until somebody else nominates you. SushiGeek 17:36, 28 May 2006 (UTC)
I mis-communicated. I meant as regards my participation in the voting process. I never thought of standing for the job of an administrator - with 2 days as a registered user and with hardly 100 edits, only a fool shall think of the same. Right now, I want to know about by ability to vote in the RfA. --Bootblack 17:44, 28 May 2006 (UTC)