Wikipedia:Bureaucrats' noticeboard

Bureaucrats' noticeboard archives

1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37, 38, 39, 40
41, 42, 43, 44, 45, 46, 47, 48, 49

This page has archives. Sections older than 5 days may be automatically archived by .

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

Shortcuts

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	13
Approved BRFAs	0

Requests for
bureaucratship update
No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)

It is 10:53:10 on April 27, 2024, according to the server's time and date.

Desysop request

Could someone please remove my admin bit? --Boson (talk) 11:15, 14 November 2018 (UTC)[reply]

Have done so, restoring your previous user rights. Hope all is well. Worm^TT(talk) 11:24, 14 November 2018 (UTC)[reply]

Thank you! Everything is OK, but I will not be able to devote as much time to the project as I had intended. --Boson (talk) 12:48, 15 November 2018 (UTC)[reply]

Desysop of Fred Bauder

I note that, about a week ago, bureaucrat

WP:IAR

. Relevant comments:

Discussion has been fragmented, making it difficult to follow. The situation as a whole raises questions of the proper boundaries between bureaucrats, the arbitration committee, stewards, the community as a whole, and to a lesser extent the election coordinators and election commission since the initial dispute took place on a page related to the elections.

I believe it is important that exceptional actions such as this be noted here so that all bureaucrats are aware of them. I also believe that further discussion with the wider community would be valuable and would hope that Maxim will participate. If this page is not the most suitable venue for that discussion, perhaps links to more suitable pages could be provided.

The Uninvited Co., Inc. 21:31, 16 November 2018 (UTC)[reply]

It is my view that, to a far greater extent than other activities at Wikipedia, the role of

WP:SNOW after 15-1 opposition. The provision allowing bureaucrats to de-sysop only those accounts where there is evidence that the account has been compromised barely passed, and has not since been amended. The intent at the time was to reserve these exceptional emergency cases to the stewards

.

There is further discussion at

WP:IAR

to de-sysop an admin under certain circumstances. The discussion did not have wide participation, however, and did not lead to any sort of consensus.

I would also like to observe that I have reviewed Wikipedia:Former administrators/reason/for cause and do not believe that there has been any previous example of a bureaucrat de-sysopping anyone for cause in the absence of clear instructions from the Arbitration Committee. The most recent similar situations were in 2006-2008 and were performed by Jimbo Wales (talk · contribs), and were controversial. I may have missed some cases since those that were ultimately resolved with the affected individual being re-sysopped are not indexed anywhere and are therefore difficult to find. The Uninvited Co., Inc. 22:32, 16 November 2018 (UTC)[reply]

There is an arbitration case on the matter: Wikipedia:Arbitration/Requests/Case/Fred Bauder. Maxim_(talk) 22:35, 16 November 2018 (UTC)[reply]

I believe I included a link to the case at the top of the section. Do you believe that discussion should take place on the case pages? The Uninvited Co., Inc. 22:36, 16 November 2018 (UTC)[reply]

Here is good. Apparently I suck at reading today. :p Maxim_(talk) 22:40, 16 November 2018 (UTC)[reply]

That's OK, my writing skills have been iffy all week. The Uninvited Co., Inc. 22:46, 16 November 2018 (UTC)[reply]

I've been assuming that the case would discuss the role of bureaucrats and have been reserving my (non-privileged, ordinary editor) analysis for its workshop. However if the bureaucrats would like to have the discussion here, then that's fine, too. Thanks for your historical info. isaacl (talk) 00:01, 17 November 2018 (UTC)[reply]

I think the way Maxim handled it, immediately and publicly posting their reasoning to the arbitration committee, was sufficient to make the IAR perfectly permissible, even for a crat.
talk) 23:00, 16 November 2018 (UTC)[reply
]

Given that the so-called 'emergency' (whether or not it was an emergency- it had been 3 hours since the reblock and Fred has not unblocked himself again?) has subsided, shouldn't the permissions be restored to ultimately be decided on by the committee? Barring an injunction, temporary desysop motion, or similar... –xeno^talk 23:13, 16 November 2018 (UTC)[reply]
There is an arbcom motion in effect. -- KTC (talk) 23:25, 16 November 2018 (UTC)[reply]
Thank you. –xeno^talk 23:28, 16 November 2018 (UTC)[reply]

While a desysopping in this situation is, in itself, not unreasonable or unprecedented, it should not be overlooked that crats quite simply do not have the authority to perform discretionary desysoppings, even in emergency situations. If there is a pressing reason to do so, meaning something so serious and urgent that it cannot wait for either Arbcom or a Steward to act, then sure, an IAR desysopping would be reasonable for the protection of the project. However, that's not what happened. Self-unblocking is an abuse of the tools, repeatedly doing so is an additional offense, and yes, these acts make one subject to desysopping. But, contrary to what a lot of people seem to think, it's not a bright line for desysopping, and while Fred was rightfully desysopped, nothing fundamentally gives crats the right to make that sort of judgment call, even though they have the technical ability. Yes, IAR is a thing, but I don't think it is all that reasonable to invoke IAR in order to usurp the authority to desysop, especially in a non-emergency situation where there is no risk of harm to the project. Tool misuse is scandalous, and tempers on all sides were already heated. An IAR desysop was an overreaction, and an understandable one that we can certainly let slide, but it was unnecessary, and while I have great respect for and confidence in our crats, including Maxim, and we should not let crats get into the habit of invoking IAR to perform discretionary desysops. Swarm talk 03:43, 17 November 2018 (UTC)[reply]
WP:VPPOL might be a better place to ask questions like, "Should bureaucrats be allowed to perform desysopings without direction from Arbcom?", and "If so, when?". WP:BN is a little backwater. --Izno (talk) 04:04, 17 November 2018 (UTC)[reply
]

I've said my 2c on the case page already, but wanted to add support to what Swarm said. I think it would be appropriate for a bureaucrat to do an emergency desysop IAR-style if the situation was ongoing, but once the threat of tool misuse (and particularly tool misuse that would harm the project) has passed, it should only be up to ArbCom to take action. I think it got struck in my comment on the case page, but I'll also reiterate that my concerns are not with Maxim or his actions, but rather what should be done in future cases. -- Ajraddatz (talk) 19:09, 17 November 2018 (UTC)[reply]
Perhaps the title, 'Bureaucrat', rather covers the issue, well; but maybe put this off until after the Arbitration Case. -- Alanscottwalker (talk) 20:22, 17 November 2018 (UTC)[reply]
I support Maxim's actions here. GAB^gab 20:32, 17 November 2018 (UTC)[reply]
For the record, I too support Maxim's action. The situation had been pulling in more and more different administrators, and it was clear that Fred Bauder was not interested in discussing things since he was simply unblocking himself within minutes. Maxim's action stabilized things and reduced disruption to the project. I wouldn't want to see bureaucrats routinely taking it upon themselves to de-sysop administrators that they deemed unruly, but this was an unusual situation. So in this particular case, I believe that Maxim showed good judgment. --El on ka 08:07, 18 November 2018 (UTC)[reply]

unblockself

Based on early comments lets not continue this here, if someone wants to propose this the right venue can be used - thank you for the replies. — xaosflux ^Talk 23:41, 17 November 2018 (UTC)[reply]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

BN is not the best venue, but since we are directly talking about issues realted to the (unblockself) permission - throwing out a feeler: What if we just removed this access from administrators (and perhaps adding it to bureaucrats to deal with issues of rogue admins)? — xaosflux ^Talk 21:40, 17 November 2018 (UTC)[reply]

The number of admins who accidentally block themselves or test blocks on themselves, and have to unblock themselves, far exceeds the number of rogue unblocks. Step hen 21:43, 17 November 2018 (UTC)[reply]

I would agree. I think the current situation is fine—if you screw up and block yourself or you're doing tests, sure, go ahead and unblock yourself. If someone else blocks you, then even if you think they're way out of line, you appeal the block, you don't just reverse it. Also, I recall some admins who did unblock themselves during the Robdurbar incident because the account was so clearly compromised; they weren't penalized in any way but were instrumental in keeping the problem in check. Seraphimblade ^{Talk to me} 21:58, 17 November 2018 (UTC)[reply]

Agreed. The tool should stay as is, admins who misuse it can be dealt with by arbcom, as is happening in this case.

talk) 21:59, 17 November 2018 (UTC)[reply

]

Adding a post-close idle thought, Stephen's point made me wonder if there would be a way in pemrs to undo your own selfblock but not other's blocks of you.
✉ 00:37, 18 November 2018 (UTC)[reply
]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Resysop request (Al Ameer son)

Al Ameer son (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 · fm · mms · npr · pm · pcr · rb · te)}

My administrative permissions Al Ameer son (current rights · rights management · rights log (local) · rights log (global/meta) · block log) were suspended for inactivity on 30 April 2018. I am requesting their reinstatement. I had been particularly busy in real life for that year or so, but I intend to remain active here pending unforeseen circumstances. I believe I have been responsible with these permissions and hope the board will restore them. Thank you, —Al Ameer (talk) 22:19, 17 November 2018 (UTC)[reply]

Everything seems to be in order here, admin access was used last year. Standard 24 hour hold for comments. — xaosflux ^Talk 23:40, 17 November 2018 (UTC)[reply]

Done, reviewed original RFA, request is within time window for automatic restoration of adminship. The Uninvited Co., Inc. 20:18, 19 November 2018 (UTC)[reply]