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, 50
51

This page has archives. Sections older than 7 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	11
Approved BRFAs	0

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

It is 00:06:17 on June 9, 2025, according to the server's time and date.

Wikipedia:Inactive administrators/2025#June 2025

The following inactive administrators are being desysoped due to inactivity. Thank you for your service.

Criteria 1 (total inactivity): (none)

Criteria 2 (100 edits/5-year rule)

NuclearWarfare (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Last logged admin action: Dec 2021

— xaosflux ^Talk 00:44, 1 June 2025 (UTC)[reply]

Btw, why is the reason "procedural removal dur to inactivity per Special:Permalink/1293310648#Wikipedia:Inactive_administrators/2023#November_2023 at WP:BN"? —— Eric Liu_{（Talk・Guestbook）} 06:53, 1 June 2025 (UTC)[reply]

I believe it was a mistake. Xaosflux accidentally copied the wrong link. – DreamRimmer ■ 07:29, 1 June 2025 (UTC)[reply]

OK, cf. discussion last month. —— Eric Liu_{（Talk・Guestbook）} 09:20, 1 June 2025 (UTC)[reply]

I was watching for that too - going to purge my autocomplete buffer now, I'll fix that entry. — xaosflux ^Talk 11:25, 1 June 2025 (UTC)[reply]

Purged that buffer, thank you for the note, apologies for any confusion. — xaosflux ^Talk 11:28, 1 June 2025 (UTC)[reply]

👍 —— Eric Liu_{（Talk・Guestbook）} 15:36, 1 June 2025 (UTC)[reply]

Recall petition certified (Bbb23)

Bbb23 (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Around six hours ago, a petition to initiate recall proceedings against Bbb23 reached the necessary 25 signatures, and has been closed as certified. Bbb23 indicated in that thread that they won't be standing for a reconfirmation RfA – I'll leave it to the 'crats on whether they want to change Bbb23's admin flag to sunset in 30 days from the closure of the petition or, absent a post from Bbb23 here, wait until the 30 days are up to discuss this again. Many thanks. theleekycauldron (talk • she/her) 21:51, 6 June 2025 (UTC)[reply]

Courtesy link: Bbb23's statement (Non-bureaucrat comment) 184.152.65.118 (talk) 04:19, 7 June 2025 (UTC)[reply]

As Bbb23 explicitly said they are not resigning, no action right now. There is plenty of time for them to change their mind. If they don't, just drop a request here after it sunsets. — xaosflux ^Talk 09:25, 7 June 2025 (UTC)[reply]

Exactly what Xaosflux said. I think in practice we should only really require a post here for one of two situations. 1. The time limit has elapsed, we need to remove the flag, or 2. There is a resignation of the tools.

Either way, it should be when there is an action that we can take. Lee Vilenski ^{(talk • contribs)} 11:45, 7 June 2025 (UTC)[reply]

For what it is worth I do not mind a notice about a recall petition reaching certification, as I pay much more attention to this page than the recall pages. I do agree with the others here that telling us that we have discretion as to what to do, when that's already in our mandate, does seem a little unnecessary ;-) Primefac (talk) 19:11, 7 June 2025 (UTC)[reply]

I don't mind a notice here that something is going on. My response above was just that I wouldn't take any immediate action. — xaosflux ^Talk 20:23, 7 June 2025 (UTC)[reply]

Barkeep49 had requested notifications on this page when recall petitions close in favour of a re-request for adminship. Bureaucrats do have the responsibility of communicating with the admin in question in order to understand their plans. isaacl (talk) 19:25, 7 June 2025 (UTC)[reply]

(edit conflict) While obviously the crats have discretion to take no action yet, and I'm not one of them, is there any reason not to set the admin bit to expire in a month the moment a recall petition hits certification? If they RRFA and it passes, then a crat will be around to remove the expiry (and probably it's a good thing for the ceritified-but-failed recall to be present in the rights log in the name of accountability), and if not then it avoids the need to do something later when it falls off everyone's attention spans. Prior to the technical invention of temporary rights, temp rights were granted socially on other wikis via processes like m:Steward requests/Permissions/Approved temporary/m:Steward requests/Global permissions/Approved temporary, and a look at the history of those pages shows regular weeklong overages, several months-long ones, and one case that was forgotten about for five whole years. So we should save the trouble and push the button now rather than having to remember later. * Pppery * _{it has begun...} 19:32, 7 June 2025 (UTC)[reply]

The "do something later" part is what would be problematic; if I am reading your proposal right, after getting notification of a certified recall, we would flip the bit on the user's mop to expire in 30 days. Okay, so they run an RRFA, and they start it on the 29th day. Now we have to extend their temporary bit another seven days so that it doesn't expire during the RRFA. Let's say that it goes to a 'crat chat, so we have to extend again. It's easier to flip the bit when it's time to flip the bit rather than predict when it should happen and keep updating things. Primefac (talk) 19:40, 7 June 2025 (UTC)[reply]

Agree, no need to act early - there are at least 25 people that are following the recall, I have no doubt at least one of them would post here if it lapses. — xaosflux ^Talk 20:22, 7 June 2025 (UTC)[reply]

Not sure why this is an issue. Is there a concern that there won't be a crat immediately online at the 30-day mark? Are you concerned that some harm will come to Wikipedia if the tools aren't removed until 30 days + 1-2 hours? If so, what harm are you concerned about? -- Euryalus (talk) 00:44, 8 June 2025 (UTC)[reply]

Euryalus, this whole process, from the initial AN discussion to the recall petition to its closure, happened very quickly, like over a period of 48 hours or so. It was like there was a fire lit under some members of the community. It would not surprise me if there weren't editors wanting this all to be concluded IMMEDIATELY. Liz ^{Read! Talk!} 03:55, 8 June 2025 (UTC)[reply]

Hi Liz! Yes I noticed the short time frame but them's the rules of recall, there's no minimum time for a petition. Just curious why that rush extends to a member of Arbcom also coming to BN to make the case for yanking the tools on the dot of 30 days. But if there's no answer I won't press it. - Euryalus (talk) 08:12, 8 June 2025 (UTC)[reply]

I wouldn't say I'm in a rush, Euryalus, and my arb hat and boots are strictly for arb work. I also don't have a super-vested interest in trying to prevent Bbb23 from holding the tools for a second longer than 30 days – you're right, that'd be pretty silly. I do care a fair amount about how the community recall process will take shape, given that I was one of many people who helped facilitate its creation; I saw that Bbb23 noted their intent to let their adminship expire, and suggested to the crats that they could act on that now if they wanted to. Primefac raised some concerns on why that might end up creating more work that it gets out of the way, and I thought they and the other 'crats made good points – I wasn't pushing hard for it then and I'm not now. Recall is just a new process and it's helpful to figure out what our standard practices is going to be. I hope that answers your questions, but if it doesn't, my talk page is always open. theleekycauldron (talk • she/her) 19:15, 8 June 2025 (UTC)[reply]

IntAdmin bot trial

DeadbeefBot II (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)}

A bot has been given a trial period for the purpose of syncing Git repositories to Wikipedia, which necessitates giving it interface administrator privileges for the duration of the trial (30 days or 30 edits). Any feedback, comments, or concerns should be expressed at the BRFA. Primefac (talk) 13:26, 8 June 2025 (UTC)[reply]

@Primefac have you informed the operator that they must enroll that account in 2FA? — xaosflux ^Talk 15:18, 8 June 2025 (UTC)[reply]

@Xaosflux: I have now enrolled the bot account with 2FA. dbeef [talk] 15:25, 8 June 2025 (UTC)[reply]

Thanks! — xaosflux ^Talk 15:26, 8 June 2025 (UTC)[reply]

Dbeef, I did a double-take when I read this, I didn't know you changed your username recently. Liz ^{Read! Talk!} 17:01, 8 June 2025 (UTC)[reply]