Wikipedia:Bureaucrats' noticeboard
|
|
|
|
1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
|
This page has archives. Sections older than 7 days may be automatically archived by Lowercase sigmabot III. |
For sensitive matters, you may contact an individual bureaucrat directly by e-mail.
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.
| RfA candidate | S | O | N | S % | Status | Ending (UTC) | Time left | Dups? | Report |
|---|---|---|---|---|---|---|---|---|---|
| Numberguy6 | 0 | 0 | 0 | 0 | Open | 01:36, 1 June 2024 | 6 days, 3 hours | no | report |
 | It is 22:02:37 on May 25, 2024, according to the server's time and date. |
Epbr123
As an FYI to other crats, I've desysoped Epbr123 per this announcement. For what it's worth, I try to avoid using multiple hats like so, but I've not yet found a steward to lock the account so this solves some of the issues. Maxim(talk) 02:52, 20 November 2021 (UTC)
- The account is locked now. For what it's worth, the "not yet found a steward" was more of a Maxim issue than a steward issue. :-/ Maxim(talk) 03:15, 20 November 2021 (UTC)
- Well, that was interesting. Kudos on the reaction time, which was impressive. Pretty sure WP:IAR applies to tool use in cases like this. In fact, that is kind of the purpose of IAR. Dennis Brown - 2¢ 13:35, 20 November 2021 (UTC)
- IMO it should be permissible to for any crat to unilaterally desysop an account they believe to be compromised, so long as they immediately notify ArbCom afterwards. No need to wait. Suffusion of Yellow (talk) 20:28, 20 November 2021 (UTC)
- With the removal of the
unblockselfpermission back in 2018 (see T150826), there shouldn't really be any need for that. The account can be blocked by any admin (even if the compromised account managed to block other admins since they can always block the one who blocked them) and ArbCom can then decide under WP:LEVEL1 which works quite fast anyways (the whole Epbr123 thing happened within a couple of hours while it was night here).Regards SoWhy 21:36, 20 November 2021 (UTC)- With the nature of Wikipedia's permissions, and probably the exact issues that Maxim mentions above, I believe it will always be a good idea to remove sysop from a blocked compromised admin as soon as possible. I remember confirming this the last time I was blocked. -- zzuuzz (talk) 21:46, 20 November 2021 (UTC)
- With the removal of the
Voluntarily resigning my administrative permissions
- Sancho (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)
Hello, I haven't been doing much administrative work. As suggested by the message left by User:JJMC89 bot, I would like to voluntarily resign my administrative permissions. Sancho 03:18, 23 November 2021 (UTC)
