Wikipedia:Bureaucrats' noticeboard: Difference between revisions

Content deleted Content added

Inline

Revision as of 18:26, 27 February 2021

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

WP:BN
WP:BNB

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

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

It is 14:49:15 on May 23, 2024, according to the server's time and date.

Voluntary Admin Removal \ WGFinley

I gained my bit in a much different time on WP and it appears the community has changed greatly during that time and I have lost touch with it. Therefore, I'm requesting that my access to admin tools be removed. --WGFinley (talk) 11:41, 20 February 2021 (UTC)[reply]

I've done that for you WGF. Thank you for your time as an admin. Noting here, for the record, the discussion at ANI: [1]. SilkTork (talk) 13:11, 20 February 2021 (UTC)[reply]

SilkTork, please provide a permanent link or it doesn't do much for the record. Your link is already dead. Bishonen | tålk 09:48, 25 February 2021 (UTC).[reply]

this should do Ϣere SpielChequers 09:55, 25 February 2021 (UTC)[reply]

That was a sad read, more than anything else. :( Acalamari 11:13, 25 February 2021 (UTC)[reply]

Interface Admin for AmandaNP & DeltaQuadBot

AmandaNP: AmandaNP (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)}

Hi all. I have had requests from a few people over time for an easy way to update js code on Wikipedia while still having a proper bug/code review/versioning system behind it. I just filed Wikipedia:Bots/Requests for approval/DeltaQuadBot 9. But to be able to edit other user's JS files, the bot will need interface admin permissions.
Policy also requires that I have the Int admin flag myself. I have assisted users with diagnosing and slightly modifying js/css code before, but I'll admit, I can't directly code in JavaScript. That being said, that wouldn't be my use for it. As a bot developer that solidly knows python and PHP, I can still clearly read JS and know what I'm screwing around with before I do it. I would not intend to edit any sitewide scripts or ones that affect a large amount of people. Just to assist getting this bot up and standard diagnosing of users having issues with scripts and their JS files. I'm also happy to answer any questions. -- Amanda (aka DQ) 23:03, 24 February 2021 (UTC)[reply]

Standard 48-hour hold for new IADMIN flags. @AmandaNP: this access requires that you have WP:2FA enabled on your account, do you have this yet? — xaosflux ^Talk 00:07, 25 February 2021 (UTC)[reply]

Yes, have had it on for a long time now. -- Amanda (aka DQ) 05:03, 25 February 2021 (UTC)[reply]

Done. Primefac (talk) 18:26, 27 February 2021 (UTC)[reply]

DeltaQuadBot

DeltaQuadBot (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)}

Not done @AmandaNP:, your bot request will need to pass WP:BRFA first. We won't need another 48 hour hold for the bot assuming your primary account has access. You will need to enroll your bot account in WP:2FA as well. — xaosflux ^Talk 00:07, 25 February 2021 (UTC)[reply]

Oh ok, figured that still required it's own discussion here. No worries. -- Amanda (aka DQ) 05:03, 25 February 2021 (UTC)[reply]

Desysop again please (Boing! said Zebedee)

I took back the admin tools last year to help with the demands brought by the Covid-19 pandemic, which was putting pressure on existing admins. The need appears to have eased off since then, and I've performed very few admin actions in that area in 2021 (just a couple of blocks that were promptly addressed and reversed). I also have important personal priorities over the next few months, and removing all those Covid pages from my watchlist would greatly reduce the distraction. So please disable my admin tools again. Boing! said Zebedee (talk) 09:22, 25 February 2021 (UTC)[reply]

Done - thanks for your work Boing! said Zebedee Worm^TT(talk) 09:40, 25 February 2021 (UTC)[reply]

:-( Ritchie333 ^(talk) ^(cont) 19:12, 25 February 2021 (UTC)[reply]

what Ritchie said ^^ :-( — Ched (talk) 21:07, 25 February 2021 (UTC)[reply]

Compromised sysop account - DYKUpdateBot

Hello, I just locked DYKUpdateBot as compromised. This account holds local sysop permissions, so I decided to inform bureaucrats in case they wish to take any local action. Best, Martin Urbanec (talk) 19:58, 25 February 2021 (UTC)[reply]

@Shubinator: please review and reply about this situation. ArbCom can review the WP:LEVEL1 situation. — xaosflux ^Talk 20:02, 25 February 2021 (UTC)[reply]

Ya I saw nothing in crat policy to tell us to desysop, so i'll leave that to ArbCom. I blocked the account at least for local accountability before the account is restored. Also blocking DYKHousekeepingBot (talk · contribs) per stewards saying it's out too. -- Amanda (aka DQ) 20:05, 25 February 2021 (UTC)[reply]

Arbcom emailed to review the situation. — xaosflux ^Talk 20:04, 25 February 2021 (UTC)[reply]
@AmandaNP: Did you mean to enable autoblock? The bot runs on toolforge. Suffusion of Yellow (talk) 20:06, 25 February 2021 (UTC)[reply]

Forgive me for being dense, but a quick look through the contributions doesn't reveal anything that would mandate an obvious emergency. I assume there's something else going on here that I don't get. Ritchie333 ^(talk) ^(cont) 20:07, 25 February 2021 (UTC)[reply]

@Ritchie333: there is a private tech report about this that a sysadmin acted upon. — xaosflux ^Talk 20:12, 25 February 2021 (UTC)[reply]

I didn't, just realized and took it back off. I don't see anything obvious either through local CU, but I'm assuming something on the steward end triggered it. -- Amanda (aka DQ) 20:08, 25 February 2021 (UTC)[reply]

Yeah, if this is WP:BEANS then that's fine by me - I just think it's worth spelling it out because a lot of people submit DYKs and won't necessarily be up to speed on what stewards do. Ritchie333 ^(talk) ^(cont) 20:11, 25 February 2021 (UTC)[reply]

This is a BEANS situation for sure. Bush's baked honey maple flavored, I think. CaptainEek ^{Edits Ho Cap'n!}⚓ 20:13, 25 February 2021 (UTC)[reply]

Somewhat ironic that Xaosflux linked to a private report, which is the very definition of BEANS Ritchie333 ^(talk) ^(cont) 20:21, 25 February 2021 (UTC)[reply]

Tickets like this have limited access, and only members of the correct ACL can see it. But agree, posting the link was unwise, or at least ironic. QuiteUnusual (talk) 20:39, 25 February 2021 (UTC) [reply]

Meh. We rely too much on security through obscurity. --In actu (Guerillero) ^{Parlez Moi} 20:41, 25 February 2021 (UTC)[reply]

The report number was already publicly posted, I'll remove it from above since others are concerned though. — xaosflux ^Talk 20:42, 25 February 2021 (UTC)[reply]

Note: It's me who published the ticket ID for the first time (see the lock reason). Alone, the ticket number does not provide any information, unless you are a member of the correct Phabricator group. --Martin Urbanec (talk) 21:00, 25 February 2021 (UTC)[reply]

Can confirm, legitimate concern. ArbCom is examining the issue. CaptainEek ^{Edits Ho Cap'n!}⚓ 20:12, 25 February 2021 (UTC)[reply]
Thanks for the ping User:Xaosflux. Who should I talk with to get this resolved? I'm working on replying to a Cloud Services email, not sure if I also need to talk with ArbCom. Shubinator (talk) 06:36, 26 February 2021 (UTC)[reply]
- @Shubinator: while the sysadmins w/ Cloud Services may unlock you - you will need to contact ArbCom about getting sysop access restored. They will generally want to discuss with you security practices related to WP:SECUREADMIN. — xaosflux ^Talk 11:05, 26 February 2021 (UTC)[reply]
  See WP:RETURN for more details. Regards So Why 11:08, 26 February 2021 (UTC)[reply]

Level 1 desysop of DYKUpdateBot

Under the Level 1 desysopping procedures, the administrator permissions of DYKUpdateBot (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) have been temporarily removed as a suspected compromised account.

Supporting: Barkeep49, Bradv, CaptainEek, Maxim, Worm That Turned

For the Arbitration Committee, Barkeep49 (talk) 20:23, 25 February 2021 (UTC)[reply]

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Level 1 desysop of DYKUpdateBot

Bureaucrat note: -sysop per LEVEL1 request completed. — xaosflux ^Talk 20:26, 25 February 2021 (UTC)[reply]

Restoration of privileges to DYKUpdateBot

DYKUpdateBot (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)}

DYKUpdateBot (talk · contribs) is granted administrative permissions on the English Wikipedia following the securing of its passwords by the operator.

For the Arbitration Committee, – bradv🍁 23:18, 26 February 2021 (UTC)[reply]

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Restoration of privileges to DYKUpdateBot

Done Permissions restored. -- Amanda (aka DQ) 23:30, 26 February 2021 (UTC)[reply]

meta:Special:Redirect/logid/40270399 (note of GUNLOCK). — xaosflux ^Talk 23:31, 26 February 2021 (UTC)[reply]

The violent imagery surrounding global locks is always interesting (glocked, gunlocked). ProcrastinatingReader (talk) 23:45, 26 February 2021 (UTC)[reply]

Or, possibly, a meaningless coincidence. Beeblebrox (talk) 23:49, 26 February 2021 (UTC)[reply]

@@ Line 30: / Line 30: @@
 :Standard 48-hour hold for new IADMIN flags.  {{ping|AmandaNP}} this access requires that you have [[WP:2FA]] enabled on your account, do you have this yet? — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 00:07, 25 February 2021 (UTC)
 ::Yes, have had it on for a long time now. -- [[User talk:AmandaNP|<span style="color:white;background-color:#8A2DB8"><b>Amanda</b></span>]] <small>[[User:AmandaNP|(aka DQ)]]</small> 05:03, 25 February 2021 (UTC)
+:::{{done}}. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 18:26, 27 February 2021 (UTC)
 ;DeltaQuadBot
 :{{rfplinks|DeltaQuadBot}}