::IRC is not a big mess, I am there all the time. Most of the claims of abuse from that channel come from people who don't even go there. It is all very exaggerated, it is just a place for admins to get advice from each other. Seriously the most recent issue with IRC is based on an incident '''months ago'''. [[User talk:Until(1 == 2)|1 != 2]] 16:02, 6 January 2008 (UTC)
::IRC is not a big mess, I am there all the time. Most of the claims of abuse from that channel come from people who don't even go there. It is all very exaggerated, it is just a place for admins to get advice from each other. Seriously the most recent issue with IRC is based on an incident '''months ago'''. [[User talk:Until(1 == 2)|1 != 2]] 16:02, 6 January 2008 (UTC)
:::::Event in question take place December 22, 2007.[http://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_arbitration/IRC/Evidence&diff=prev&oldid=180688915] Silly 'Zilla thought that was less than "'''months ago'''", regret Zilla can only count to 3! Little [[User:Until(1 == 2)]] can count to months? Clever! [[User:Bishzilla|<font face="comic sans ms"><font color="cyan"><i><b><big>bishzilla</big></b></i></font></font>]] ''[[User talk:Bishzilla|<font color="magenta"><sub><small>R</small></sub>OA<big>R<big>R!<big>!</big></big></big></font>]]'' 17:11, 6 January 2008 (UTC).
:::It's a shame people don't get excited on-wiki over all of the constructive things that happen there. [[User talk:John Reaves|John Reaves]] 16:04, 6 January 2008 (UTC)
:::It's a shame people don't get excited on-wiki over all of the constructive things that happen there. [[User talk:John Reaves|John Reaves]] 16:04, 6 January 2008 (UTC)
::::That'll be the day... '''[[User:Majorly|<span style="color:#002bb8">Majorly</span>]]''' (''[[User talk:Majorly|talk]]'') 16:09, 6 January 2008 (UTC)
::::That'll be the day... '''[[User:Majorly|<span style="color:#002bb8">Majorly</span>]]''' (''[[User talk:Majorly|talk]]'') 16:09, 6 January 2008 (UTC)
To contact bureaucrats to alert them of an urgent issue, please post below. For sensitive matters, you may contact an individual bureaucrat directly by e-mail.
You may use this tool to locate recently active bureaucrats.
The Bureaucrats' noticeboard is a place where items related to the Bureaucrats can be discussed and coordinated. Any user is welcome to leave a message or join the discussion here. Please start a new section for each topic.
This is not a forum for grievances. It is a specific noticeboard addressing Bureaucrat-related issues. If you want to know more about an action by a particular bureaucrat, you should first raise the matter with them on their talk page. Please stay on topic, remain civil, and remember to assume good faith. Take extraneous comments or threads to relevant talk pages.
If you are here to report that an RFA or an RFB is "overdue" or "expired", please wait at least 12 hours from the scheduled end time before making a post here about it. There are a fair number of active bureaucrats; and an eye is being kept on the time remaining on these discussions. Thank you for your patience.
To request that your administrator status be removed, initiate a new section below.
It is 13:11:49 on June 5, 2024, according to the server's time and date.
Revoking rollback
We've had a proposal going on for some time about granting rollback for non administrators. It's clear sysops would need to grant the permission (and userrights has been updated to allow this to happen) but would the bureaucrats' be willing to take on the responsibility of removing the permission? We would need to do this in response to misuse of the tool, I'm still looking at ways this could be done, but removal per a consensus on AN/I is probably the easiest way to do it, and obviously, this would be a discussion that you would have to evaluate the consensus for. This would stop the drama potential with admins granting and revoking userrights. Anyway, is this something you'd be happy to take on? Ryan Postlethwaite 21:22, 29 December 2007 (UTC)[reply]
(Note: I'd still personally prefer to see Bureaucrats remove and grant. Maybe by setting up a page similar to Wikipedia:Changing username. If, after the initial "rush" of requests, this turns out to over-burden our current bureaucrats, then I'm sure that we could add a few to the fold : ) - jc37 21:56, 29 December 2007 (UTC)[reply]
Why can't admins remove them? It's the same as blocking/unblocking, delete/undelete, protect/unprotect. All admins should be able to reverse other admins' actions. Majorly (talk) 22:12, 29 December 2007 (UTC)[reply]
I also don't think it is a good idea for admins not to be able to undo their own or each others actions. Not to mention the different in the number of admins vs the number of 'crats. I would prefer that admins can do both, or that crats can do both. 1 != 2 22:14, 29 December 2007 (UTC)[reply]
I agree totally with Majorly. If admins end up wheel warring on the granting or removal of these rights then shame on them, and off to RFC or ANI. After all, granting a rollback button is way down the scale from granting or removing editing rights (i.e. the block tool) and we all have the ability to do both right now. Pedro : Chat 22:25, 29 December 2007 (UTC)[reply]
All due respect, there was a reason this was posted on the Bureaucrat's noticeboard. : - ) The finer details can and will be discussed elsewhere; the point of this post was to gauge bureaucrats' thoughts. --MZMcBride (talk) 22:28, 29 December 2007 (UTC)[reply]
*makes mental note* Pedro and Majorly agreed on something :) Majorly (talk) 22:31, 29 December 2007 (UTC)[reply]
:) does happen! Pedro : Chat 22:32, 29 December 2007 (UTC)[reply]
At the expense of turning this into a Mockzilla thread, the ability for Bureaucrats to remove the rollback privilege could very easily be implemented through tweaking LocalSettings to read $wgRemoveGroups['bureaucrat'] = array( 'rollback', 'bot' );. Just a point :) Anthøny 01:42, 5 January 2008 (UTC)[reply]
Well, no that wouldn't work, since there isn't a rollback group at the moment. You would also need $wgGroupPermissions['rollback']['rollback'] = true as well. And that is nearly twice as much work! :P Let it be known it is not a technical issue though. Prodegotalk 03:13, 5 January 2008 (UTC)[reply]
I think I could more or less speak for all (or at least enough) of us and say that we would be willing to work on removing the right if necessary and the community wants us to. If the workload was high, I'm sure we would have no trouble finding qualified candidates to become new bureaucrats. On the side note, I'm sympathetic to the position that if admins are given the ability to give out the right, they should be able to remove it too since once you can give it, removing it is less than blocking. But giving the right out is something more, so I'm not fully decided on who should give it out. But that's another discussion. - TaxmanTalk 14:43, 2 January 2008 (UTC)[reply]
Admin bit
The following discussion is an archived debate. Please do not modify it. Subsequent comments should be made in a new section.
Hi, I resigned uncontroversially after nearly a year as a sysop on 3 October. I had an RFA about a month later, which I had to withdraw because of false allegations being made about me. However, I think any bureaucrat can see that the RFA probably would have passed had I not withdrawn it, and the accusations hadn't been made. Since the RFA was voluntary in the first place, and at least two bureaucrats (namely Raul654 and Deskana) have stated their intentions that I need not have another RFA (and another RFA would just cause too much drama), I'd like to ask for my sysop bit back. Thanks. Majorly (talk) 15:48, 30 December 2007 (UTC)[reply]
I object. I believe the prior withdrawn RfA creates controversial circumstances; and that, having once submitted oneself for re-judgment by the community, one cannot later ask for the bit back through summary means after withdrawing that RfA. Xoloz (talk) 15:51, 30 December 2007 (UTC)[reply]
Um, I was not aware that such kind of restrictions were placed on users who stood up for re-confirmation RfAs. Reconformation RfAs are voluntary, just like "admins open to recall". It is finally up to the volunteers whether they stand by them or not. — Nearly Headless Nick{C} 17:14, 30 December 2007 (UTC)[reply]
Dunno whether it makes any difference to the crat, but I endorse Majorly's comments, and believe he should be fully able to regain hsi bit at any time he desires. -- Anonymous DissidentTalk 15:53, 30 December 2007 (UTC)[reply]
To expound, I think we should really question whether Majorly himself is terribly controversial, and whether his RFA was failing before Gmaxwell made that rather rash and controversial comment that caused Majorly's RFA to sink, and caused him to withdraw. Also, as Majorly has stated, his RFA would still probably have passed, despite the fierce arena it had become at the time of closure. -- Anonymous DissidentTalk 16:12, 30 December 2007 (UTC)[reply]
Xoloz, please appreciate this problem. I'm in a catch-22 situation here. If I request people will complain that I'm running again, and oppose me. If I don't run, people will complain that I'm not running, and object to resysopping. What am I supposed to do? Majorly (talk) 15:55, 30 December 2007 (UTC)[reply]
I do appreciate the difficulty, but I believe that the community's judgment always deserves paramount consideration, and that the failed RfA creates significant doubt whether its judgment on you is (or can be) known without another RfA. If a b'crat says you must go to RfA, I don't believe any reasonable commenter would hold that fact against you. Xoloz (talk) 15:58, 30 December 2007 (UTC)[reply]
To be even clearer, I don't blame you for asking here for your bit back -- the situation is clearly confused and unprecedented (I think, anyway). I simply object to the granting of the summary request, because I believe that controversy does exist, and that a new RfA is the best, most transparent, most accurate way forward. Xoloz (talk) 16:03, 30 December 2007 (UTC)[reply]
I think Majorly probably just qualifies as non-controversial and that this request can be granted. However, this does conflict with my general belief which is: if in doubt => WP:RFA. GDonato (talk) 16:02, 30 December 2007 (UTC)[reply]
I am not going to restore Majorly's admin bit per my comments in answer to question question 7 on my RfB. I think I'm too close both to Majorly and to the events of the reconfirmation to be seen as impartial in making such a determination. I would like to make a couple of points, firstly I would note that although Raul654 and Deskana have expressed opinions supporting the restoration of the bit without RfA, Cecropia and Secretlondon came to the opposite conclusions: [1], [2].
Secondly, I personally support Raul654's assessment of the situation [3]. Majorly's reconfirmation contained a clear consensus that he should be an amdinistrator up until Gmaxwell (a developer and Commons checkuser) made an accusation that Majorly and User:Matthew were the same person. Such an accusation is highly prejudicial and prompted a growing shift of opinion that caused Majorly to withdraw the RfA. Gmaxwell's conclusions, will made in good faith, were not supported by the checkusers who reviewed them on-wiki (Raul654 and Deskana). They are also contradicted by the fact that a number of administrators (myself, RyanPostlethwaite, Steel359 and Wimt) were with Majorly at a meetup in Manchester when Matthew made a number of edits to Wikipedia and between us are certain Majorly could not have made those edits. Accusations of abusive sockpuppetry from a trusted source have a serious chilling effect. In this case, I support the view that it would be wrong to treat Majorly's reconfirmation RfA as a withdrawn attempt. In m opinion, it should be regarded as a nulity given that the accusations that derailed it have not proved possible to confirm (quite the opposite). I would be entirely happy with another bureaucrat restoring Majorly's admin access. WjBscribe 16:12, 30 December 2007 (UTC)[reply]
Just wondering: do you believe that the community is incapable of judging the (in)validity of GMaxwell's case against Majorly? Is that judgment not best made by consensus at RfA? I'll add that several commenters, including myself, raised issues with Majorly's judgment wholly unrelated to GMaxwell's accusation, also, and that the peremptory withdrawl prevented those (debatable, but open) points from being heard for seven days. Xoloz (talk) 16:24, 30 December 2007 (UTC)[reply]
On the contrary, if I thought tthat would pose a problem - an RfA would be needed. Bureaucrats should not approve the returning of rights to people who are likely to have trouble reaching consensus at RfA. I don't think there's going to be any such problem here and a large section of the community opposes reconfirmation RfAs that are not necessary. In this case I believe the result of the next RfA is pretty much a foregone conclusion, that the last RfA was likely to pass in any event and that the concern which lead to it being withdrawn has now proved unfounded. There a good reason to regard the RfA as void and I don't see anything positive coming out of a further RfA. Which is why were I free to act, I believe I would return the tools. WjBscribe 16:52, 30 December 2007 (UTC)[reply]
Sorry to jump in but thought I may add from another perspective. From what I remember of Majorly's RFA, a number of users were concerned that he had gone through the RFA process - was talk of it being more of a slap-on-the-back process than anything else. I believe I opposed on those grounds, as I felt at the time there was no need for the RFA as he could just have been given his bit back as he gave it up under uncontroversial circumstances. However, due to the fact it did go to RFA (and ignoring the GMaxwell allegations) I would now feel uncomfortable if it didn't go to RFA this time. The recent Mercury situation has, if nothing else, reminded that the community has to be able to take such decisions. Just my thoughts, take them or leave them. Whitstable (talk) 16:35, 30 December 2007 (UTC)[reply]
You're forgetting Mercury resigned under a cloud of controversy. I didn't. The only controversy was because Gmaxwell thought it necessary to claim I was a sockpuppet. That isn't my fault is it? During an admin's time, he or she is bound to make errors, as I have. Some people won't let these minor slips go, and look at the positive side of things. I performed well over 5000 admins logs iirc. I never once abused my tools, and wouldn't dream of it. The concerns other than Gmaxwell's were incredibly minor ones. Particularly regarding Kurt Weber's block, whom I spoke to in private about it. Xoloz, who has been particularly vocal here, has opposed both my RFBs, only just went neutral on my original RFA and opposed my RFA (and steward candidacy too). Perhaps that says something about him. Not only that, he opposed per Friday, another editor who has always opposed me, whose rationale was an incredibly poor one, in my view - it makes it seem like I blocked Kurt - all I did was agree a block would be fine, if he never edited the encyclopedia. As it happened, he had not been editing it at the time, and was only opposing self nom RFAs. Majorly (talk) 16:48, 30 December 2007 (UTC)[reply]
Majorly is entitled to resysopping on request under the circumstances. There was no controversy regarding him at the time he resigned, and there is no allegation that he resigned to avoid something like an impending arbitration against him, which is really what the "controversial circumstances/under a cloud" rule was designed to deal with. Meanwhile, I hope we have learned something about the danger of unnecessary "confirmation" RfAs. Newyorkbrad (talk) 16:57, 30 December 2007 (UTC)[reply]
Hear, hear! WjBscribe 17:01, 30 December 2007 (UTC)[reply]
Personally I think the admin bit should be given. Only if B's decide otherwise a RfA would be in order. This is no where near the Mercury situation and a RfA would be a waste of peoples time. Agathoclea (talk) 17:05, 30 December 2007 (UTC)[reply]
While the RFA would probably have resulted in a pass, while I have no doubt the accusations were wide of the mark, etc, it still remains true that the RFA closed early and did not result in Majorly being appointed an admin. My personal view - and it is only that - is that by using the RFA method Majorly lost his chance of using this method, of just asking for it back. This situation raises questions - is it now being suggested that "confirmation" RfAs are not relevant and can be overruled by Bureaucrats? If 300 had opposed the "confirmation" RfA and just 10 supported, would this method now being used still be acceptable? I have no problems with Majorly getting the bit back, there is no risk at all of any abuse of the tools, etc, and I would support at RFA. But I cannot stress enough how much I feel the RFA process is needed for the sake of transparency and clarification. Whitstable (talk) 17:09, 30 December 2007 (UTC)[reply]
Hi Whitstable, although I appreciate your concerns, I would like to disagree with your opinion. There is evidence abound that the RfA process is broken, and it is not be as transparent as you might assume it to be. To illustrate, I could request a desysop on my account right now, and then stand for reconfirmation. In all probability, the RfA would not pass. — Nearly Headless Nick{C} 17:22, 30 December 2007 (UTC)[reply]
Yes, you're right - the system is flawed and needs fixing, and urgently. But it remains the only system we have. Anyway, I'm sure we all have more important things to do than worry about whether an ex-admin who would make a good admin should be made one or not! Whitstable (talk) 17:29, 30 December 2007 (UTC)[reply]
This debate is unneeded. Majorly was an administrator and he resigned voluntarily. Now he is asking for the tools. There was no controversy with regard to the usage of admin tools. The controversy was created because there was difference in opinion. There is no evidence of sysop abuse among many other things. I urge the bureaucrats considering this request, not to delay this any further and not deprive the encyclopedia the services which it can receive from a capable and dedicated user. — Nearly Headless Nick{C} 17:15, 30 December 2007 (UTC)[reply]
I see no cloud of controversy regarding Majorly. The AfDRfA was not lost, it was canceled. I see no reason why the admin bit should not be returned. 1 != 2 17:18, 30 December 2007 (UTC)[reply]
AfD = Administrators for deletion? This admin thing must be riskier than I thought ;-) NoSeptember 17:35, 30 December 2007 (UTC)
I am going to, reluctantly, go against the general consensus here. Although I strongly support Majorly's return to adminship, I think that he should go through an RfA. It is essential that all administrators should have the full support and confidence of the community. The fact that the participants in this discussion have not been unanimous, and that some people have opposed the immediate return of the tools, suggests that there is some controversy involved. If Majorly chooses to go through an RfA, I will vote Support; however, I must express my opposition to the return of his tools without an RfA. This is a point of principle, in the interests of democracy, accountability and transparency. Admins are servants of the community and must always, always, defer to the will of the community. WaltonOne 18:10, 30 December 2007 (UTC)[reply]
Give him the bit back and save the drama. It's only a website boys and girls. Pedro : Chat 19:38, 30 December 2007 (UTC)[reply]
Yup, there seems to be some confusion to what is controversial in my thread and this one. Give it back to him, there was no cloud. Mercury 20:20, 30 December 2007 (UTC)[reply]
I support the return of Majorly's tools and object to some points made by Walton. A significant portion of opposition against Majorly's last RfA was that he was, essentially, a narcissist and needed "a pat on the back," which is not a legitimate concern here. If we were to take the last RfA and apply it in the current atmosphere, the removal of "oppose because he wants to feel good" votes would leave a legitimate consensus. Unanimity is unnecessary, a single oppose does not spell a death knell to community support. This isn't the Polish-Lithuanian Commonwealth. Secondly, Wikipedia isn't a democracy, and the votes are not equal for good reason. Thirdly, admins can override community consensus if it contradicts policy; while this is a rare action, it has happened before. Adins are not slaves to the community, but they serve first and foremost the encyclopedia, then the community. —Kurykh 20:57, 30 December 2007 (UTC)[reply]
I received many of the same kind of opposes (i.e. the "no pat on the back" ones) in my reconfirmation RfA. I agree that it is not a strong rationale, but editors are entitled, in good faith, to vote however they wish on an RfA. In the cases of myself and Majorly, some editors (e.g. User:Neil, who opposed both RfAs) felt that our choice to seek reconfirmations was evidence of some kind of insecurity or of an unsuitable temperament for adminship. While I strongly disagree with them, I did not, and do not, believe that such votes should be removed or discounted. Every vote made by an established user in good faith should be counted equally. There is no "right" or "wrong" answer on an RfA, only different opinions; there are no fixed criteria for adminship. And so the outcome on an RfA should be determined democratically.
With regards to your third point, yes, admins should apply policy where policy conflicts with the consensus on a particular discussion. However, the reason for this is that the policies are the result of a much broader consensus than that which exists in any individual discussion. Ultimately, all legitimate rules on Wikipedia derive from community consensus (except those relating to Wikipedia's legal obligations). There are many issues where editors can disagree, in good faith, about what is best for the encyclopedia. In such a case, an admin should not do what they personally believe is best for the encyclopedia; they should obey the community consensus, even if they believe that the consensus is wrong. WaltonOne 11:54, 31 December 2007 (UTC)[reply]
Some thoughts
Firstly, I think it's fair to say that Majorly's RfA would have passed prior to the incident involving Gmaxwell. At 04:34, 8 November 2007 (UTC), the last revision before Gmaxwell's post, the RfA sat at a comfortable 152/22/15. All major apparent issues had been extensively discussed (arguments about the merit of the RfA, which in any case should be ignored at this juncture per Kurykh at 20:57; the block-endorsement of Kmweber; accuracy with blocks; and a handful of others). Therefore, I personally feel it is safe to say that without the checkuser investigation the RfA would have continued along a similar line and ultimately been successful, hence why I suggested the RfA be suspended pending further investigation when the issue developed on November 8.
Normally, I'd agree that having an RfA nullifies ones' ability to simply ask for the tools back, especially when said discussion results in there being no clear consensus to (re-)promote. However, while I personally don't know if they're true or not, the allegations have yet to be proven. There is no consensus amongst checkusers that they are sockpuppets, or said consensus hasn't been announced and acted on if one exists, as if there was the Matthew account and very likely the Majorly one would be blocked for abusive sockpuppetry. Without this consensus of those "with the information", Majorly should be afforded the assumption of good faith. Looking at this in hindsight, there is absolutely no way that a block on the Majorly and Matthew accounts would have stuck based solely on behavioural evidence, and I suspect the administrator who took any action like that would be desysopped. What we have is an inconclusive result of a checkuser investigation, insufficient evidence based on behavioural contributions, and the fact that Majorly should have a right to be treated in good faith.
So, we have an RfA which would otherwise have passed (see paragraph one) which was unfortunately derailed (with no intention of partitioning malice on anyone involved, especially Gmaxwell, because assuming good faith applies there also) by an unfortunate incident involving accusations of checkuser-confirmed sockpuppetry which inevitably wasn't endorsed by consensus (see paragraph two). I think these extraordinary circumstances should mean that the RfA be nullified when considering it in this situation. If Majorly was a run-of-the-mill candidate and a similar situation developed, I'm sure there would have been grounds for the RfA to be restarted without the input of those citing the checkuser evidence. The equivalent here is to ignore the result of the RfA, which was withdrawn and not failed (although this is, admittedly, less of an important distinction from where I sit compared to the other two points), and repromote as there is no doubt that Majorly resigned under non-controversial circumstances.
All-in-all, I support Majorly getting administrator access returned without an RfA, although given there is some dispute over it ( whether it is non-controversial is disputed), it may be a better idea to have a consensus of bureaucrats agree that this case falls under the speedy-repromote criteria rather than one bureaucrat acting on their own judgement.
Respectfully, Daniel 23:48, 30 December 2007 (UTC)[reply]
I previously stated that Majorly is welcome to resume adminship at any time (on his steward candidacy), and I intend to keep that promise. Input from other bureaucrats first would be ideal. --Deskana(talk) 23:52, 30 December 2007 (UTC)[reply]
I agree with your, WJB's and Raul's assessments. — Dan | talk 01:35, 31 December 2007 (UTC)[reply]
I support Majorly being granted the tools, having mistakingly opposed his RfA. —Dihydrogen Monoxide 03:30, 31 December 2007 (UTC)[reply]
An observation: Since there seems to be some conflicting opinions among 'crats, I would absolutely recommend that in this particular case, a formal consensus check be carried out and consensus reached and stated as such. Normally the "one crat doesn't overturn what another one says" works great, but not this time. Given the (deplorable) edit warring over footnote applicability that was occurring on Wikipedia:Former administrators about this matter, I suspect that crystal clarity would be highly beneficial here. Further, perhaps the 'crats might want to review the footnotes being used on that page to see if they convey exactly what they ought to with as little ambiguity as possible. Note I personally express no opinion on which 'crats I agree with in this matter. ++Lar: t/c 17:52, 31 December 2007 (UTC)[reply]
No someone just give him his bit back already. No need for all this fuss. Theresa Knott | The otter sank 18:36, 31 December 2007 (UTC)[reply]
Were there not two revelations of sockpuppetry? One of which was rejected, but one of which was acknowledged. Though it's claimed that the use of the latter was "legitimate sockpuppetry" has this been investigated and determined to be the case? I do realize this is complicated by the circumstances under which it was revealed and unsure how this relates to whether or not the sockpuppetry was legitimate. I don't know how to discuss this without being vilified, and probably blocked, so I won't comment further until I have guidance from someone else on whether or not discussion of this topic is permissible. --JayHenry (talk) 18:37, 31 December 2007 (UTC)[reply]
No more formal process is needed. This is one purpose for which the BN was set up for. We have participation of multiple crats in this thread, There is no quorum requirement, so no need to contact any inactive crats, and all the non-crat opinion is appreciated as well. NoSeptember 18:46, 31 December 2007 (UTC)
Maybe I wasn't being specific enough. Do I have permission to discuss the second case of sockpuppetry or would doing so be considered a privacy violation? Is it illegitimate for an editor such as myself to discuss because of the circumstances under which it was revealed? Is it simply considered irrelevant to the case at hand. --JayHenry (talk) 18:54, 31 December 2007 (UTC)[reply]
My reply above was to Lar. As for your question, not knowing the nature of your information, I'd suggest you email it to Raul654 and Deskana, who were previously involved as checkusers in this case, and they can advise you. NoSeptember 19:07, 31 December 2007 (UTC)
I have no information that is not present in Wikipedia logs. Therefore I am unwilling to discuss anything in secret. I have made clear my concern and if discussion of the behavior of the acknowledged sockpuppet is verboten than so be it. I do feel that Majorly was treated unfairly by Gmaxwell and I'm unwilling to exacerbate that situation with secret memoranda. The best disinfectant for a dark and moldy room is never more darkness. Respectfully, --JayHenry (talk) 19:41, 31 December 2007 (UTC)[reply]
Majorly announced his retirement from Wikipedia in September 2007. He continued to edit sporadically under Majorly, but at the same time, he was editing (RC patrol, mostly) under a legitimate sockpuppet account. He "retired" his sockpuppet, and returned to his normal level of editing as Majorly. The sockpuppet account was not controversial by any means, and Majorly did not violate any part of WP:SOCK. Majorly did not give up his tools under controversial circumstances, and his RfA would have surely passed, had the sockpuppetry accusations (from Gmaxwell) not been made. I know that some people have issues with Majorly's attitude, but if you examine his admin logs, you will see that he has never abused the tools. Nishkid64 (talk) 20:19, 31 December 2007 (UTC)[reply]
I personally do not feel that the sockpuppet was used completely within the bounds of WP:SOCK. Both participated at the RedirectCleanupBot RFA in which one left a support comment, and the other initially removed an oppose vote and mocked the opposer at a noticeboard. While the main account was still editing the other initiated an editor review that, considering the primary account was an active administrator, could be considered a sham. Both participated at WP:RFA and WT:RFA in September and October. Other than the one mentioned above they refrained from commenting on the same RFA, but significantly in my mind, both opposed attempts at reform on WT:RFA. In some of the sock's last edits it had a conversation with the main account. My main concern is that both were active in RFAs at the same time. I see no legitimate reason to have multiple accounts participating at RFA more or less simultaneously. --JayHenry (talk) 21:22, 31 December 2007 (UTC)[reply]
(I should clarify that the comment removed from the RFA ultimately did turn out to be a sockpuppet of a banned user and it was correctly discounted.) --JayHenry (talk) 21:34, 31 December 2007 (UTC)[reply]
I didn't participate with my main account on the bot RFA, and I'm unsure where you think I did. I specifically made sure I didn't do things like that. I had intended to drop Majorly, but didn't, for reasons I don't know. It was wrong of me to continue editing with Majorly, but I made sure I didn't skew consensus in any way with my comments. Your last point about the conversation. It was a case of using the wrong account, and forgetting to log in. I admit that it was a mistake to use a sockpuppet, especially continuing to edit. I had wanted to start over and drop Majorly eventually, but never got round to it, hence the editor review, but that is a minor point really. However, I never double voted, or backed myself up with the other (with the exception of when I used the wrong account), so I believe I followed the policy perhaps not to the letter, but in spirit. Majorly (talk) 21:43, 31 December 2007 (UTC)[reply]
Seems I did. But I never actually left a comment there, so it's minor in my view. Majorly (talk) 21:47, 31 December 2007 (UTC)[reply]
This is all getting rather protracted now, but as I was just looking at it myself, here is your editWhitstable (talk) 21:46, 31 December 2007 (UTC)[reply]
Diff. I'm willing to accept that this was a relatively harmless lapse. If the higher-ups have no concerns then I'm not going to push this any more. I have no axe to grind, and I think you were a good admin. --JayHenry (talk) 22:05, 31 December 2007 (UTC)[reply]
Yes, I struck my above comment. I supported with Majorly, and with my other account I removed a trolling comment from a SPA. I personally don't see it as a problem. What would be a problem is if I had supported with both, or voted with both, or left comments with both. But since I only did with Majorly, I personally think it's not a problem. Whatever the case, it's extremely minor in the long run of things. As I said above, I never abused my admin tools, and that is what this is all about. Majorly (talk) 22:11, 31 December 2007 (UTC)[reply]
Before it happens I'd like politely ask that no one to mention my other account's name. Everyone who needs to know knows already, and I'd rather it wasn't revealed here. Thanks in advance. Majorly (talk) 22:14, 31 December 2007 (UTC)[reply]
I dunno
While I personally have no opinion on whether User:Majorly should be trusted with the tools, this discussion seems a bit hazy.
While I personally think we should allow bureaucrats the leeway to use "administrative discretion" (or, if wanted, "bureaucrat consensus"), that hasn't been the general consensus in the past (the carnildo controversy, for example).
I also think that it's been contentious as to whether an admin who has given up their tools, and subsequently gone through a (presumably needless) RfA, may still be granted the tools after that RfA fails or is withdrawn.
So, as the header says, I dunno... Though it seems to me that any action outside a new RfA would be controversial at the very least.
With all that in mind, perhaps Majorly should just consider going through a new RfA to spare the community the disruption? I dunno. It's a judgement call, and one where I'm not sure any answer is "right". - jc37 18:39, 31 December 2007 (UTC)[reply]
To be fair, the only controversy involved here (and the reason for the RfA being withdrawn) was a statement that has been proven, beyond all shadow of a doubt, to be false (and the RfA was passing until the false information was presented, which tainted the RfA). I consider the matter to be muddied only by irrelevant details, and would consider yet another reconfirmation RfA to be more "disruptive" than just giving him the bit back. My two cents. EVula// talk // ☯ // 18:50, 31 December 2007 (UTC)[reply]
i know
Someone press the button, more no more process is required here. I don't think it will set precedent. Mercury 18:58, 31 December 2007 (UTC)[reply]
Did you mistype and mean "no more process"? Newyorkbrad (talk) 21:47, 31 December 2007 (UTC)[reply]
Thank you. I typed fast. Mercury 21:51, 31 December 2007 (UTC)[reply]
Bit restored
Pursuant to my previous comment (that the RFA should have and would have passed, had it not been for Gmaxwell's allegations which later turned out to be unfounded, and thus is null and void) and to the discussion here, I have restored Majorly's admin bit. Raul654 (talk) 22:12, 31 December 2007 (UTC)[reply]
Thanks a lot Raul. I'll take all concerns from above into account, and from my RFA also, and will hopefully make me a better admin, and editor. Regards, Majorly (talk) 22:16, 31 December 2007 (UTC)[reply]
Excellent decision, Raul654. Acalamari 04:27, 1 January 2008 (UTC)[reply]
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made in a new section.
Special:Userrights
Just a note to let other bureaucrats know that Special:Userrights has been made available to us. Needless to say we can only use it to add +sysop or +bureaucrat, not to remove them. I just used it to promote User:Jon513 as Special:Makesysop wasn't working. WjBscribe 16:58, 30 December 2007 (UTC)[reply]
Interesting, it doesn't work quite the way I thought it would. I tried it on myself and it showed me as having no user groups, and only being able to add bot. I kind of expected it to show my rights but not allow their removal. That's one way of accomplishing the goals of the situation though. It's nice. --Deskana(talk) 18:13, 30 December 2007 (UTC)[reply]
Are Makesysop and Makebot dead now, if so we can update the interface to refer to the new page. — xaosfluxTalk 22:41, 30 December 2007 (UTC)[reply]
Does it show anywhere the user's current usergroups? If not, a bug report may be in order. --uǝʌǝsʎʇɹnoɟʇs(st47) 22:43, 30 December 2007 (UTC)[reply]
WJBscribe, do you mean you can't access it or there is a bug? Voice-of-All 23:46, 30 December 2007 (UTC)[reply]
What is wrong with Special:Makesysop? Voice-of-All 23:01, 30 December 2007 (UTC)[reply]
Special:Makesysop and Special:Makebot were ugly hacks designed to give limited access. Special:Userrights now has the flexibility to control which groups can set which permissions, so there is no real reason not to use it. If we were ever to create a new usergroup (*cough*Rollback*cough*), with the old system we would need to write another special page to grant and revoke it. With Special:Userrights, this is no longer necessary. -- Cobi(t|c|b) 23:06, 30 December 2007 (UTC)[reply]
. . . yes, I know. I was referring to User:WJBscribe's comment that "it wasn't working". Voice-of-All 23:46, 30 December 2007 (UTC)[reply]
Not technically a 'crat issue but to avoid forking this, on Special:Specialpages User rights management should be moved to the Restricted special pages section. — xaosfluxTalk 00:11, 31 December 2007 (UTC)[reply]
The makesysop problems seem to be due to double escaping, which I fixed on SVN. Voice-of-All 00:16, 31 December 2007 (UTC)[reply]
Any objections to me updating the instructions to suggest we use the shiny new Special:Userrights rather than Makesysop and Makebot? Warofdreamstalk 02:54, 31 December 2007 (UTC)[reply]
Can you actually make bots through userrights at the moment? Voice-of-All 03:28, 31 December 2007 (UTC)[reply]
Assuming Meta-Wiki is the same, bots can be made through Userrights. Majorly (talk) 03:32, 31 December 2007 (UTC)[reply]
Interestingly enough, Makesysop still works over at Meta-Wiki, along with Userrights. I guess I can use either :) Majorly (talk) 02:59, 31 December 2007 (UTC)[reply]
Hmm, can you use userrights to set a +bot and +sysop at the same time, or +bot when +sysop exists? Maxim(talk) 16:05, 31 December 2007 (UTC)[reply]
Yes, userrights can assign as many rights are as allowed by the group in question. In this case, bureaucrats have the ability to change rights from (none) to bot, bureaucrat, sysop in one swoop. Not that they ever would anyways. Mediawiki default however, if the developers put different restrictions, feel free to correct me. --Charitwotalk 16:13, 31 December 2007 (UTC)[reply]
There is no technical method in place to allow such restrictions. --uǝʌǝsʎʇɹnoɟʇs(st47) 17:39, 31 December 2007 (UTC)[reply]
Great, I've updated the instructions. Warofdreamstalk 15:58, 1 January 2008 (UTC)[reply]
Sysop bit
Please restore my sysop bit. I requested it removed when I took a wikibreak and was unsure of if/when I would return to active editing and admin duties, under non-controversial circumstances (entirely self-prompted). If you have any questions or concerns, please let me know. Cheers! Vassyana (talk) 09:08, 2 January 2008 (UTC)[reply]
Welcome back Vassyana :) Indeed, I can attest that there was absolutely nothing controversial about the removal in Vassyana's case. Cheers, Daniel 10:29, 2 January 2008 (UTC)[reply]
Yup, completely uncontroversial - and fortunately for us Vassyanas wikibreak wasn't too successful and she's still been actively editing :-) Ryan Postlethwaite 11:53, 2 January 2008 (UTC)[reply]
It seems that whether one uses Special:Makebot or Special:Userrights for Bot flagging affects which log the action ends up in. For example:
Warofdreams flags and unflags a test account using Special:Userrights - the change is logged at Special:Log/rights
I flag a recently approved Bot using Special:Makebot - the change is logged at Special:Log/makebot
I guess the question is whether there is value in keeping the record of Bot flagging actions separate from other changes in user rights. If so, then bureaucrats should continue using Special:Makebot or the developers need to be asked to adjust the way in which granting/revoking Bot status using Special:Userrights is logged if that is possible. WjBscribe 16:09, 2 January 2008 (UTC)[reply]
Bot is a user right just like any other, so will be in the user rights log. I'd personally prefer the bots to be in their own log - the rights log should be for people, in my view. Of course, it is not up to me, but I think they should be separate still. Majorly (talk) 16:15, 2 January 2008 (UTC)[reply]
The log of bot flags says big and bold that it's deprecated and that the pages "do not exist", however they obviously are still there and functional. I'm assuming the devs will be removing them soon and that notice was premature. So I guess continuing to use Special:Makebot won't make a difference until it's, infact, gone. --Charitwotalk 17:25, 2 January 2008 (UTC)[reply]
I changed it to be it to be big and bold under the assumption makebot and makesysop don't work, but I may be completely wrong here. Of course, I'm not a 'crat so I can't go to those pages myself to be completely certain, but I recall WJBsribe saying that makesysop doens't work.. Maxim(talk) 17:36, 2 January 2008 (UTC)[reply]
I did say that Makesysop didn't work - its unclear though whether that's a glitch or a permanent thing. Voice of All looked into it and thought it was a glitch that he'd probably now fixed, but it would need someone to be due to be promoted for me to check (I can still access the interface, but got an error message when I tried to use it last time). Special:Makebot seems to still be working as usual though. WjBscribe 17:42, 2 January 2008 (UTC)[reply]
(ec) I guess wait for confirmation on when the pages will "cease to exist", or in this case on when Makebot will cease to function, it's just a matter of where to change the rights. I personally think they should be all flagged using Special:Userrights, but that's the 'crats discretion seeing as how Makebot, for now, is still fully functional. --Charitwotalk 17:45, 2 January 2008 (UTC)[reply]
From what I've read / heard, Makebot and Makesysop will be officially deprecated as soon as the UI for Special:Userrights doesn't suck so much. Brion said he didn't want anyone to be forced to use Special:Userrights until the UI had been improved. --MZMcBride (talk) 19:38, 2 January 2008 (UTC)[reply]
Can the text at the top of the bot status log be changed to reflect that then? --Charitwotalk 21:45, 2 January 2008 (UTC)[reply]
What with the addition of the $wgAddGroups and $wgRemoveGroups fields to MW 12.0, it appears the MakeBot extension is now defunct and all setting of rights will be done via Special:Userrights. This has been on the cards for a while now :) Anthøny 14:23, 3 January 2008 (UTC)[reply]
Did you read any of this conversation? As of my last comment, Special:Makebot was still fully functional, and Special:Makesysop wasn't working, both per WJBscribe. --Charitwotalk 14:26, 3 January 2008 (UTC)[reply]
Special:Makesysop worked fine at 11 o'clock this morning. WjBscribe 18:06, 3 January 2008 (UTC)[reply]
Humm, I was going off this comment[5]. --Charitwotalk 19:14, 3 January 2008 (UTC)[reply]
Sure - I just thought I would not that it has now started working again since then. It seems it was a glitch, not a deliberate move to stop Makesysop being used. WjBscribe 19:18, 3 January 2008 (UTC)[reply]
It wasn't deliberate. One of the sysadmins changed the functionality of & in URLs, which inadvertently caused Makesysop to stop working. The Makesysop extension was fixed and synced to the site; the timing was merely coincidence. As I said, both extensions will stop being used when the UI of Special:Userrights is cleaned up. --MZMcBride (talk) 21:34, 3 January 2008 (UTC)[reply]
Is there a good place for me to ask for Bot flaggings and deflaggings to be kept in a separate log? Or is that unlikely to be possible? WjBscribe 21:47, 3 January 2008 (UTC)[reply]
I was kinda hoping there already was one :-) ... WjBscribe 22:24, 3 January 2008 (UTC)[reply]
It would be an exception to do that, since as far as Special:Userrights is concerned it would be: if right = bot, log in bot log, else, use user rights. And hypothetically, since this is possible now, what if someone were to set rights for someone +bot +bureaucrat +sysop? Where would that go? (or for that matter, +bureaucrat +bot or +sysop + bot? Prodegotalk 03:12, 4 January 2008 (UTC)[reply]
Prodego, you know beans are bad for a well balanced Wikipedia diet right? --Charitwotalk 14:48, 4 January 2008 (UTC)[reply]
Well, I think it's a pretty good and safe idea to raise a potential issue with a proposal - at the moment, beans aren't an issue as using the new method gives a useful single log of the two together, while using the old set-up it isn't an issue, as it would require two very different actions. Warofdreamstalk 16:52, 4 January 2008 (UTC)[reply]
I can't see how it really is a problem that bureaucrats can now make users that are only bureaucrats (not sysop), or make sysop/bot combo accounts. I don't really think that there was ever a real issue that they would do it, so I don't even know why that was coded in the 'Make' extensions. But it is a problem with the double log issue, since it might happen on other wikis. Prodegotalk 03:21, 5 January 2008 (UTC)[reply]
Not being able to make sysop/bot accounts proved an irritation with User:RedirectCleanupBot as a steward was needed to give it its Bot flag. As to the log issue, its always seemed useful to me to have a separate log of bot flaggings so they don't get lost in the busier user rights log but its not essential. As to the problem of how to log the giving of Bot status and another status, would it be a problem if that showed up in two logs - both the userrights and a separate Bot log? Alternatively could we make the user rights log more sortable, allowing users to look only at entries in the user rights log that involve a particular right? WjBscribe 13:59, 5 January 2008 (UTC)[reply]
That sounds an excellent proposal - and if more rights are later added, it will be all the more useful. Warofdreamstalk 18:46, 5 January 2008 (UTC)[reply]
Yes, sortability would be very nice, and I think it might be doable. The double logging would be messier, we should probably try to avoid that. Prodegotalk 18:48, 5 January 2008 (UTC)[reply]
Sortability seems better from a user point of view. If it's manageable from a developer point of view that would be great. WjBscribe 00:33, 6 January 2008 (UTC)[reply]
Mentioning #admins in congratulatory notes
I was wondering how you guys felt about mentioning Wikipedia:IRC channels/wikipedia-en-admins in the notes you leave on user talk pages after a successful RfA. I think it's a good idea and that we should try and let every admin know about it and try and get as many admins as possible to have access. John Reaves 03:58, 6 January 2008 (UTC)[reply]
I would oppose promoting IRC in any way, since it is just a huge mess. Prodegotalk 04:17, 6 January 2008 (UTC)[reply]
A brief mention in passing may not be such a huge problem; a note such as "On an aside, if you are interested, I can also give you access to #admins on IRC" -- Anonymous DissidentTalk 10:55, 6 January 2008 (UTC)[reply]
It's no problem at all. A good idea, in fact, to reduce the idea of a "cabal" channel. Majorly (talk) 12:35, 6 January 2008 (UTC)[reply]
I've done this for quite a while. As far as I'm concerned, all admins are welcome in the channel and any admin who asks for access will get it from me. IRC isn't a huge mess because it's IRC, it's a huge mess because people are making it a huge mess, and to be honest I think the IRC Arbitration case proves that; it's actually a productive channel and when I was a new admin I got a lot of help from more experienced admins via that channel. I personally encourage bureaucrats to mention the admins channel to people. --Deskana(talk) 14:02, 6 January 2008 (UTC)[reply]
IRC is not a big mess, I am there all the time. Most of the claims of abuse from that channel come from people who don't even go there. It is all very exaggerated, it is just a place for admins to get advice from each other. Seriously the most recent issue with IRC is based on an incident months ago. 1 != 2 16:02, 6 January 2008 (UTC)[reply]
Event in question take place December 22, 2007.[6] Silly 'Zilla thought that was less than "months ago", regret Zilla can only count to 3! Little User:Until(1 == 2) can count to months? Clever! bishzillaROARR!! 17:11, 6 January 2008 (UTC).[reply]
It's a shame people don't get excited on-wiki over all of the constructive things that happen there. John Reaves 16:04, 6 January 2008 (UTC)[reply]
That'll be the day... Majorly (talk) 16:09, 6 January 2008 (UTC)[reply]
Well I won't - I don't see any of the IRC channels as a positive influence on the wiki.. I've never been in #admins and don't intend to. Secretlondon (talk) 16:33, 6 January 2008 (UTC)[reply]
Please do not post advertisements in RFA messages, or anywhere else on Wikipedia. Promotion of some chat room is an advertisement. Friday(talk) 16:41, 6 January 2008 (UTC)[reply]