Wikipedia:Bureaucrats' noticeboard

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.

Click here to add a new section

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.

Crat tasks
RfAs	0
RfBs	0
Overdue RfBs	0
Overdue RfAs	0
BRFAs	16
Approved BRFAs	0

Requests for adminship and bureaucratship update

No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)

It is 20:33:37 on November 30, 2024, according to the server's time and date.

Inactive admins for June 2015

The following admins can be desysopped for inactivity:

• @pple (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}
• Dlohcierekim (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}
• Wayward (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

Thanks to all of them for their service to Wikipedia. Graham87 09:43, 1 June 2015 (UTC)

I've done Dlohcierekim & Wayward. Can't do @pple - looks like that will need to be done by a steward, due to the username Worm^TT(talk) 10:12, 1 June 2015 (UTC)

@Worm That Turned: Typing #3685614 into the username field should work to remove the admin rights (it just did when I tested it to get onto the removal screen). That's the user ID for that user per this API query, and that's basically how the stewards would do it anyway. Graham87 10:30, 1 June 2015 (UTC)

@Worm That Turned: Service. —DerHexer (Talk) 10:39, 1 June 2015 (UTC)

Thank you both - didn't even occur to me! Now done Worm^TT(talk) 12:12, 1 June 2015 (UTC)

Wikipedia:Arbitration/Requests/Case/Sockpuppet investigation block

Pursuant to this decision of the Arbitration Committee, please remove admin tools from Chase me ladies, I'm the Cavalry (current rights · rights management · rights log (local) · rights log (global/meta) · block log). For the Arbitration Committee, L235 (t / c / ping in reply) 17:42, 9 June 2015 (UTC)

 Done Acalamari 18:43, 9 June 2015 (UTC)

Bad RfA

http://en.wikipedia.org/wiki/Wikipedia:Requests_for_adminship/habibisgreat

• Editor habibisgreat has been blocked for vandalism (blanking pages). BMK (talk) 05:14, 11 June 2015 (UTC)

Request for reinstatement of sysop rights

Hi all - I'd like to request a reinstatement of my sysop rights. They were previously stripped (and my account blocked) after I had a technical compromise simultaneous to health issues that prevented me from immediately dealing with the technical isssue and requesting GorillaWarfare block my account, and have since locked down my system. I realize this is a slightly atypical situation, but feel that postinghere requesting reinstatement is likely to still be teh most transparent route. Kevin Gorman (talk) 14:44, 11 June 2015 (UTC)

Hi Kevin. Not sure I've got this right, but it looks like you were desysopped just a week ago by an ArbCom representative. As such, I don't think we should resysop without ArbCom say-so. --Dweller (talk) 15:02, 11 June 2015 (UTC)

Although performed at the behest of an arb member (and I would expect arb to be consulted before reinstating the rights,) they were removed at my own request (since I couldn't immediately secure my own accounts, I asked GW to take action.) Although I would expect arbcom to have input here, since they were removed at self-request and were not removed under a shade, it seemed more appropriate/transparent to request restoration and discussion here than through private lists. (GW is aware I posted here, as I imagine is the rest of arbcom by this point.) Kevin Gorman (talk) 15:14, 11 June 2015 (UTC)

Kevin, as this request was made at the behest of an arb member, we will be waiting for an arb member to re-instate. Worm^TT(talk) 15:23, 11 June 2015 (UTC)

I certainly expect the 'crats to wait on arbcom confirmation it's okay to and have no problem with it :) I just felt like it would be a little more in the wiki-way to place a request about it on a public board, rather than email arbcom-l and the crats lists independently. Realistically, I'm hoping it won't a particularly challenging discussion - I reached out once I knew an account had been compromised to prevent any damage to the wiki, asked for me rights to be stripped, and then remedied the situation as I could (which involved voluntary giving up of privs while not under the shadow of wrongdoing. In full disclosure, one of my blocks was challenged to ANI during this, but it was upheld.). Felt like BN was a better place for a discussion of restoration of rights not taken away under the shadow of wrongdoing than elsewrhere would've been, since it really is a 'crat matter. Kevin Gorman (talk) 15:47, 11 June 2015 (UTC)

Seems sensible. Hopefully, they'll give us a quick answer. --Dweller (talk) 16:00, 11 June 2015 (UTC)

Thanks, WTT. ArbCom is aware of this request and we are currently discussing it. Salvio ^{Let's talk about it!} 15:25, 11 June 2015 (UTC)

(del/undel) 17:40, 4 June 2015 Addshore (talk | contribs | block) changed group membership for User:Kevin Gorman from edit filter manager, course campus volunteer, course coordinator, course instructor, course online volunteer and administrator to edit filter manager, course campus volunteer, course coordinator, course instructor and course online volunteer (Temporary desysop per private communication with the Arbitration Committee. GW)

I've alerted GorillaWarfare to this, happy to follow Arbcom's instructions in this matter. Worm^TT(talk) 15:08, 11 June 2015 (UTC)

Thanks for doing, that Worm That Turned. I should have thought of it in the first instance. --Dweller (talk) 15:38, 11 June 2015 (UTC)

• Can it conclusively be said that the correct user is now in control of the account? –xeno^talk 19:38, 11 June 2015 (UTC)

Slowly threading answers as I can, but yes, we certainly can. I'm more than willing to voice/video/verify with Keilana (a well-regarded admin,) Molly (a current arbcom member,) NF (a current arbcom member, and any number of WMF'ers who have met me in person. Threading in replies one by one to avoid complex edit conflicts. Kevin Gorman (talk) 21:50, 11 June 2015 (UTC)

Request for reinstatement of sysop rights (discussion)

• comment An admin that takes security matters lightly and allows his account to be compromised shouldn't have his privileges reinstated without going through a fresh RfA. Adminship is a position of trust and such incidents affect the truthworthiness of a person significantly enough to invalidate any vote of confidence from before the incident. Does the community trust Kevin Gorman not to have his account compromised again and is therefore willing to restore his admin access? Only a reconfirmation rfa can determine that. It would be highly irresponsible to just reenable Gorman's admin access like it's nothing and I strongly oppose that course of action. 72.88.208.18 (talk) 18:00, 11 June 2015 (UTC)

  Umm...what? A compromised account can happen to anyone. It can happen to me, it can happen to a CU, as scary that sounds. His account could have been compromised because he inadvertently went to a Wikipedia mirror, logged in, and unwittingly gave away his username and password in the process. I just saw in the news today that a hacker broke into a governmental mainframe, made himself an admin, and messed around.—^cyberpower_Chat:Online 18:21, 11 June 2015 (UTC)

Your first edit being here is suspicious. What do you have against this user? Dustin (talk) 18:28, 11 June 2015 (UTC)

Have you previously edited under other IPs? As a user? I don't have proof that you have, but the fact that you make your first edit an "oppose" to this user having his sysop rights restored casts some serious doubt. Dustin (talk) 18:29, 11 June 2015 (UTC)

The correct question would be - 'what do you have against admins who get their accounts compromised having their admin access restored like it's nothing'. I don't think it's worth asking though. As for your other questions, they belong on my talk page, not here. 72.88.208.18 (talk) 18:36, 11 June 2015 (UTC)

(edit conflict) Being an admin or not has nothing to do with, for example, getting by our home broken into and your laptop (containing various passwords) stolen. I don't know if that's what happened here, it's just an example of how "an account can be potentially compromised". Nowhere does it imply the user was negligent. ☺ · Salvidrim! · ✉ 18:24, 11 June 2015 (UTC)

Details are irrelevant. Even if you think otherwise, you have absolutely no way of knowing for sure how the account got compromised. The only thing we know for sure is that it did happen, and the question is - what now? My answer: have Gorman run a reconfirmation rfa. Anything else would be just outright irresponsible. 72.88.208.18 (talk) 18:45, 11 June 2015 (UTC)

Actually, I think the main question to ask is has this happened in the past and how was it handled then? Bureaucrats should know whether the proper step is to grant admin powers back, have the admin go through a reconfirmation RfA or some step that hasn't been mentioned here yet. Unless there are extraordinary circumstances (and you say that the details are irrelevant), this case should be handled in a way that similar cases have been resolved. Liz ^{Read! Talk!} 19:03, 11 June 2015 (UTC)

You think? And what if similar cases in the past were handled the wrong way? It's better to use common sense than to waste time analyzing precedents here. 72.88.208.18 (talk) 19:29, 11 June 2015 (UTC)

What exactly would users be judging at a reconfirmation RfA? Surely all they would be evaluating is whether the user will avoid their account being compromised in the future - something no one can judge. Sam Walton (talk) 19:34, 11 June 2015 (UTC)

If we go that route then we have no option but to deny Gorman's request for resysopping. Not a bad idea at all, frankly. And no, his ability to keep his account secure isn't what would be judged at his rfa - we already know he can't be trusted to do that. The way I see it, we'd mainly be looking at Gorman's use of admin tools so far to determine whether the benefit of allowing him to continue holding the mop sufficiently offsets the risks associated with his account getting compromised again. 72.88.208.18 (talk) 19:52, 11 June 2015 (UTC)

What you're saying is essentially, is that if someone were able to hack the bank servers and managed to get a hold of your back account, and started spending with it, that you can't be trusted to keep your bank account secure, and therefore should not be granted a loan. That doesn't sound very fair, not to mention a complete lack of WP:AGF.—^cyberpower_{Chat:Limited Access} 20:26, 11 June 2015 (UTC)

The WP:RESYSOP procedure asks the bureaucrat to ensure the account is not compromised at the time of the request for re-instatement and that the user did not resign "for the purpose, or with the effect, of evading scrutiny of their actions that could have led to sanctions"; it doesn't give bureaucrats an active veto to refuse to restore adminship on the belief that the requesting user no longer holds the complete trust of the community. –xeno^talk 19:46, 11 June 2015 (UTC)

Xeno, as usual, is right. --Dweller (talk) 19:59, 11 June 2015 (UTC)

Except WP:RESYSOP isn't a policy, it's part of an information page. On the other hand, Wikipedia:Administrators#Security is a policy, and it reads 'Discretion on resysopping temporarily desysopped administrators is left to bureaucrats' and 'In certain circumstances, the revocation of privileges may be permanent' - you can and should deny requests and direct the requester to the rfa page in cases like this one where the decision to resysop is bound to cause controversy if it's made without a reconfirmation rfa. 72.88.208.18 (talk) 20:05, 11 June 2015 (UTC)

(edit conflict) You're the only one who seems to think this is controversial. It comes off more like an anonymous smear campaign. Ed ^{[talk] [majestic titan]} 20:09, 11 June 2015 (UTC)

A smear campaign you say? Where's the smearing though, other than in your above message? 72.88.208.18 (talk) 20:18, 11 June 2015 (UTC)

Interesting. @FT2: regarding this change, was there any particular discussion surrounding it? (I think I may have found it here: Wikipedia:Bureaucrats' noticeboard/Archive 9#Readdition of administrator flag) –xeno^talk 20:19, 11 June 2015 (UTC)

Wikipedia:Requests for comment/Resysopping practices may provide some guidance here. –xeno^talk 20:39, 11 June 2015 (UTC)

There is a previous discussion on this topic here: Wikipedia:Bureaucrats' noticeboard/Archive 6#Re-adminning compromised accounts. –xeno^talk 19:38, 11 June 2015 (UTC)

Where they were resysopped. There is no reason that Kevin shouldn't be resysopped promptly here. Ed ^{[talk] [majestic titan]} 20:09, 11 June 2015 (UTC)

• I would like to remind that 72.88.208.18 our sock puppet policy says "Undisclosed alternative accounts are not to be used in discussions internal to the project.". This includes logging out and posting as an IP. Please log into your regular account if you wish to participate in this discussion. Chillum 20:10, 11 June 2015 (UTC)

• Without presupposing anything at all here, the Arbitration Committee, when it removes someone's tools, has the responsibility to set reasonable situation-specific criteria for their return. There may be more to this story than meets the eye, and I would discourage everyone from jumping to conclusions here. I'd suggest that the 'crats might want to hat this discussion until such time as there is a response from the Arbitration Committee. Risker (talk) 20:55, 11 June 2015 (UTC)
  • For what it's worth, I agree with Risker. Newyorkbrad (talk) 21:47, 11 June 2015 (UTC)
    • As a direct friend of Molly who happened to be in off-wiki contact with her when this occurred, it shouldn't matter two bits whether I made the request myself, had any other trusted editor make the request, or approached a friend, who happens to be an arbitrator, asking her to make the request for me. Frankly, I think arbcom would be creating de novo policy if they were to treat this case differently than other temporary compromised accounts, which would be a pre big change to the scope of arbcom, and the kind of thing to be determined in a major venue and not ex post facto on one particular case. Criiminy, we regularly resysop people who hae been gone for >6 months without a peep, and challenging a temporary compromised account.. Kevin Gorman (talk) 22:01, 11 June 2015 (UTC)
    • From what I read at Wikipedia talk:Arbitration Committee#Kevin Gorman - compromised account desysop and block, and GW's note in Kevin's unblock log ([1]), this is probably safe to do now, but waiting for word from GW or another arb is emminently sensible. Risker or Brad, you could hat it yourself, but what happens if a non-crat hats a discussion on "their" board? You might get "accidentally" renamed or something... --Floquenbeam (talk) 21:58, 11 June 2015 (UTC)

My only thought is that Kevin said (above) that he is replying to comments here. Although I think this portion of the discussion doesn't need to be addressed by him. Liz ^{Read! Talk!} 22:00, 11 June 2015 (UTC)

• • • (edit conflict) ArbCom are still discussing this - it is a slightly atypical situation which is why it is taking us time, but please bear with us. I am not able to share anything more, but we do have more information than is public. I have no objection to any 'crat hatting discussion of this at their discretion. I will say I am disappointed by the IP's users tone. Thryduulf (talk) 22:04, 11 June 2015 (UTC)