Misplaced Pages

:Bureaucrats' noticeboard: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 13:01, 17 November 2017 editThingg (talk | contribs)Extended confirmed users71,378 editsm Request for removal of my admin rights← Previous edit Latest revision as of 16:16, 10 January 2025 edit undoArcticocean (talk | contribs)Edit filter managers, Administrators46,270 edits Resysop request (Arcticocean): responded 
Line 1: Line 1:
{{Short description|Notices of interest to bureaucrats}}
{{pp-move-indef|small=yes}}
<noinclude>{{#if:{{PROTECTIONLEVEL:edit}}|{{pp|small=yes}}}}{{User:MiszaBot/config
{{pp-move-indef}}
{{User:MiszaBot/config
|archiveheader = {{talkarchivenav}} |archiveheader = {{talkarchivenav}}
|maxarchivesize = 250K |maxarchivesize = 250K
|counter = 36 |counter = 50
|minthreadsleft = 0 |minthreadsleft = 0
|minthreadstoarchive = 1 |minthreadstoarchive = 1
|algo = old(5d) |algo = old(7d)
|archive = Misplaced Pages:Bureaucrats' noticeboard/Archive %(counter)d |archive = Misplaced Pages:Bureaucrats' noticeboard/Archive %(counter)d
}}{{/Header}}<br style="clear:both;"> }}</noinclude>
{{/Header}}<br style="clear:both;">


__TOC__
== Resysop request (JzG) ==
{{Archive top}}
* {{Userrights|JzG}}
Thanks for switching off the sysop bit back in April. Please re-enable now. <b>]</b> <small>(])</small> 23:59, 10 November 2017 (UTC)
*:BN self request ]. — ] <sup>]</sup> 00:27, 11 November 2017 (UTC)
:Happy news! :D <span style="font-size:12pt;background:black;padding:1px 4px">]&nbsp;]</span> 00:28, 11 November 2017 (UTC)
:{{done}} Welcome back. — ] <sup>]</sup> 00:21, 12 November 2017 (UTC)
:: Thank you. <b>]</b> <small>(])</small> 07:34, 12 November 2017 (UTC)
{{archive bottom}}


== Lost access to account == == Desysop request (Ferret) ==
* {{Userrights|AuburnPilot}}
Hello, all! At some point I apparently added two-factor authentication to my main account, though I don't honestly recall doing it. As such, I don't have a means to obtain authentication codes and no longer have access to my admin account. I'm not sure what the procedure is in this situation, but I don't expect I'll ever be able to access the account again, so it might be best to remove the admin bit. Otherwise, I suppose it'll be removed eventually due to inactivity. I have email enabled on both accounts if some verification is needed. Best, --] ] 19:31, 11 November 2017 (UTC)
* I think this is a Phabricator thing, not a bureaucrat one. Given we can be certain that ] is the same person as ]. ] (], ]) 20:03, 11 November 2017 (UTC)
* I've temporary removed +sysop, per your request above. There are a few options, will reply below in a moment. — ] <sup>]</sup> 00:07, 12 November 2017 (UTC)
* Options:
*# Verify this is actually a 2FA issue
*## Are you successfully logging in with your password, but then getting the 2FA prompt?
*# Regain control of your 2FA account
*## Consider what device(s) you may have enrolled in 2FA with and see if they still have authentication clients on them
*## Enrolling in 2FA includes a generation of "scratch codes" - perhaps you wrote these down somewhere as it asked you to
*# Establish strong support that your alt account is under control of the same person that had control of your admin account - then:
*## We could move your admin access to another account
*## You could petition a developer to remove your 2FA configuration : This is generally not supported (c.f. <small>])</small>, but is technically possible.
*### Example ticket ],
:— ] <sup>]</sup> 00:12, 12 November 2017 (UTC)
::Thanks for the quick response! It's definitely a 2FA issue as I'm getting asked for a verification code when logging into the site. Unfortunately, the device I would have used at the time was issued by the company I previously worked for and is no longer in my possession (wiped clean and returned upon leaving the company about 5 months ago).
::As for proving the connection between accounts, I'm sure there are several people I've been in contact with off project who could confirm and I have no issue with a CU comparing IPs. I also provided a committed identity at some point in the past. It should be in the deleted history of the userpage for my main account (now to remember the string! haha). Thanks! --] ] 03:03, 12 November 2017 (UTC)
:::OK, so that clears #1, and #2. Assuming you want to be an admin again, #3 will be needed, do you want to go for the ''move to a new account'' or ''beg a dev'' route? Your deleted CI begins with "c0e6" and was from 2007 - this would be useful for either. — ] <sup>]</sup> 03:24, 12 November 2017 (UTC)
:::{{Checkuser needed|done=yes}} - QCU request placed to request comparison while there is current data. — ] <sup>]</sup> 15:45, 12 November 2017 (UTC)
:::* I have {{u|AuburnPilot}} and {{u|AuburnPiIot}} on the same IP with the same UA. There is one anon edit to reset the password for the alt account. I believe this is indeed AuburnPilot. :-) <span style="color: #9932CC">]<sup>]</sup></span> 16:22, 12 November 2017 (UTC)
::::Thank you ] - next step is up to AuburnPilot. — ] <sup>]</sup> 16:24, 12 November 2017 (UTC)


{{rfplinks|Ferret}}
==== Move access ====
:From: <code>]</code>
:To: <code>]</code>
Thanks again, all! By random chance, my admin account was still logged in on the PC in my home office, but I'm still unable to disable the two factor authentication since I can't generate a code. Once this login token expires, I'll be right back in the same spot. It seems like the easiest option would be to simply move the admin access to a different account. ]: do you think it would be too confusing to flip the bit on the sock account (]) I was using above? Thanks, --]&nbsp;] 23:14, 14 November 2017 (UTC)
*That is possible - standard 24 hour hold for community comments. — ] <sup>]</sup> 00:51, 15 November 2017 (UTC)
*'''No issues with this at all''' I think we can file this under purely routine housekeeping. With 2FA this sort of thing is going to happen from time to time. Because my 2FA is limited to a single device I am always worrying that if something were to happen to it I might get locked out. To that end I have the emergency log in codes in a separate place and I created another account w/o administrator rights so I could log in in case I did not have immediate access to my computer. -] (]) 02:10, 15 November 2017 (UTC)
*:{{Re|Ad Orientem}} if you saved your initial two-factor secret key (or re-register and get a new one) you can activate your 2FA on multiple devices. Storing those scratch codes securely is wise! — ] <sup>]</sup> 04:33, 15 November 2017 (UTC)
*Responding to advertisement at ], '''no issues''' as well. AuburnPilot has confirmed that this is them using the original account and by CU. ]] 03:39, 15 November 2017 (UTC)
*No concerns. ] (]) 03:43, 15 November 2017 (UTC)
**While asking a dev to disable 2FA is an option, I actually think the preferable option is a transfer of rights. I get the scrutiny part, but we should not make it a practice to recommend dev's undoing 2FA, even when CU confirms that the accounts are the same. It is meant to be difficult to break for security reasons, and setting as a principle that we do not disable it except under very rare circumstances beyond the person's control would be a good thing. Since this is also the preference of AuburnPilot, we should just transfer the access between accounts. ] (]) 15:43, 15 November 2017 (UTC)
*'''No concerns''' - any account which can prove themselves to be the same person may ask to have the rights transfered to it. We approve the person at RFA, not the account. ] ] 08:19, 15 November 2017 (UTC)
*No worries about this, but we do need a better way of dealing with lost 2fa and transferring 2fa to a new device. It's there anything in phab already related to this? ] (]) 08:32, 15 November 2017 (UTC)
*: Does not seem to be the case.--] (]) 08:38, 15 November 2017 (UTC)
*::Transferring 2FA to another device is not hard. I've done it multiple times with my device. It's just that people don't always remember to do so. This is WHY the instructions tell you to print and safeguard the scratch codes, which provides further evidence that people don't read instructions. :) ] and related tickets capture some of the problems with regard to problems and the recovery processes. There are also several community wishlist proposals on the topic of 2FA, which I encourage you to vote for when the voting process begins. —] (] • ]) 12:37, 15 November 2017 (UTC)
*:::{{re|TheDJ}} I recently went through four phones in about a month (due to a series of ridiculous incidents involving badminton, OTA updates and alcohol). Each time, I had to disable 2FA and re-enable it to transfer from one phone to another. Unless I missed something in the process, disabling and re-enabling 2FA makes all your existing scratch codes useless and it generates you a new set. So every time you want to move to a new device, you have to redo your scratch code storage.
*:::Other providers who use 2FA have a way of transferring code generation from one device to another, so long as you both know the password and have either a scratch code or a working code generator. ] (]) 13:54, 16 November 2017 (UTC)
*::::{{re|GoldenRing}} you should be able to store and reuse your 2FA secret to add additional devices. What is difficult is that it is only shown during enrollment. — ] <sup>]</sup> 14:13, 16 November 2017 (UTC)
*'''No concerns'''. ] (]) 13:46, 15 November 2017 (UTC)
*'''No concerns.''' <small>Except for the detestable blue and orange in the editor's sig. ]] 13:54, 15 November 2017 (UTC)</small>
*Recovering/disabling the 2FA seems like a better option to me, otherwise '''no concerns'''. ] ] 14:32, 15 November 2017 (UTC)
*No concerns, although getting dev to disable the 2FA does seem like a better option because of the history. Being an admin, this is likely more important than not, for the ease of researching past actions, etc. I would strongly prefer the dev route if possible. ] - ] 15:32, 15 November 2017 (UTC)
*Ha, AuburnPilot is still around! NO BLOCK AND DESYSOP JUST TO PISS HIM OFF AND RESTORE AFTER ]! Bwahaha. Also, this has me worried a little bit--if I have a similar screw-up I'm not sure what I would do. ] (]) 15:41, 15 November 2017 (UTC)
**{{re|Drmies}} it worries me also. Make sure you have copies of your scratch codes, and I'd say if you need to use one, you should then turn of 2FA and do it again, getting new scratch codes. That may be being over cautious, but no one wishes to lose their account. ] ] 17:26, 15 November 2017 (UTC)
***Doug, I don't even remember what "scratch codes" were, precisely. I think I may have something saved on my computer at home, maybe. ] (]) 17:33, 15 November 2017 (UTC)
****] if u dont have them, simply disable 2FA and enroll once more —] (] • ]) 17:38, 15 November 2017 (UTC)
*****...though after all that bother, ] is a little concerning! ] (]) 13:58, 16 November 2017 (UTC)
**<small>'''Support''' 2-way I-ban for {{u|Tide rolls}}/{{u|Drmies}} (clearly socks) and {{u|AuburnPiIot}} due to...] ;) ]] 19:48, 15 November 2017 (UTC)</small>
***<small>], I'm sorry I just blocked . ] (]) 19:51, 15 November 2017 (UTC)</small>
***Confession: I may hold a degree from the greatest university in the state of Alabama, but I will forever be a Bama fan thanks to being raised by parents and siblings who graduated from UA. I was definitely the guy going to class on Auburn's campus wearing a hat signed by ]. --] ] 21:29, 15 November 2017 (UTC)
*'''No Concern''' and I'd suggest that we probably have enough comments above for the rights to be switched now. <small><span style="border:1px solid #0000ff;padding:1px;">]&nbsp;:&nbsp;] </span></small> 17:48, 15 November 2017 (UTC)
*'''Concern''' as a matter of procedure. I would prefer that AuburnPilot recovers their original account through Phabricator. The Wikimedia Foundation has technical staff with a lot more tools at their disposal than what CheckUsers have to determine if the original owner is in control of the account. Why not leave this to the experts? Now, I am sure that AuburnPilot and AuburnPiIot are the same person. I just don't think that a vote of random community members is how this sort of case should be handled. -- ] (]) 20:58, 15 November 2017 (UTC)
*'''Thanks''' to everyone who has taken the time to comment! I haven't been too active recently but it's good to be back around the site. Reading all the comments above, I see some concerns regarding admin access being moved from one account to another. My preference is simply for whatever is easier for those required to do the work cleaning up my mistake in not maintaining the authentication access for the account. From my chair, it seems easier to move the access but I'm not familiar with Phabricator and haven't the slightest clue if the devs would be willing to remove 2FA. Regardless, I'm open to whatever option requires the least inconvenience on others! Best, --] ] 21:20, 15 November 2017 (UTC)
*:I think it's just me concerned with moving the access. Moving access is certainly the easier option, and there is clear consensus here for that to happen. But I still feel that account security issues should be handled by the people who are paid to handle account security issues, rather than decided by a vote of 15 people with limited access to the information required to make an informed comment on the situation. -- ] (]) 21:49, 15 November 2017 (UTC)
*{{ping|AuburnPilot}} would you please open a phab ticket to request a 2FA disabled, reference this conversation. Should it be delayed or refused, access moving is still on the table. — ] <sup>]</sup> 23:54, 15 November 2017 (UTC)
**Done (]). --]&nbsp;] 00:44, 16 November 2017 (UTC)
** {{ping|Xaosflux}} 2FA disabled. --]&nbsp;] 01:04, 16 November 2017 (UTC)
*{{done}} {{ping|AuburnPilot}} as there has been plenty of time and you have successfully recovered your account I've restored your prior +sysop bit, the move is no longer needed. {{re|Ajraddatz}} and {{re|Cyp}} your process points are important, but I think they are bigger than enwiki. Other then ] a meta: discussion may be the place to drive this forward, as it is a global issue. — ] <sup>]</sup> 03:06, 16 November 2017 (UTC)
==== FYI ====
I dropped the sysop bit for a while and this automatically removed 2FA (which is not enabled for ordinary users). So all that's actually needed if this happens again I think is to desysop, gain access to the account and request resysop, then set up a new 2FA. That's what happened for me, anyway. The original 2FA token was no longer usable. <b>]</b> <small>(])</small> 13:00, 17 November 2017 (UTC)


Hi Bureaucrats. I'm requesting the removal of my administrator rights as of January 1, 2025, as I will be generally retiring. I would like my previous rights (autopatrolled, extended confirmed user, page mover, pending changes reviewer, rollbacker and template editor) restored. I would have waited a little closer to request but might not be online the next couple days. Thank you! -- ] (]) 17:49, 30 December 2024 (UTC)
== Resignation from the Arbitration Electoral Commission ==
:I've emailed Arbcom separately about checkuser, just as info! -- ] (]) 17:54, 30 December 2024 (UTC)
{{archive top|Thank you, notice left at ]. — ] <sup>]</sup> 18:17, 14 November 2017 (UTC)}}
:Per your wishes, I have removed the tools. I realise this is a day or so early, so if you do need to use the tools in the meantime I can revert
Since self-nominations for the ] started, and I am unfortunately still listed as a party of a pending ArbCom case, I obviously can not serve on the Electoral Commission per ]. I thereby resign and request the bureaucrats to call one of the two ]. Thank you.--] (]) 08:46, 12 November 2017 (UTC)
:On a personal note, I'm sad to see you go. Thank you for your service. '''] <sup>(] • ])</sup>''' 19:13, 30 December 2024 (UTC)
:Thank you for the update, I endorsed some candidates, but ] had already named ] as the first successor. DoRD, are you still willing to perform this function? — ] <sup>]</sup> 15:10, 12 November 2017 (UTC)
::Thank you for your years of service, ]. Enjoy your retirement! <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 19:15, 1 January 2025 (UTC)
::Thanks for the ping, and I'm in contact with the two remaining commissioners. ​—] (])​ 16:18, 14 November 2017 (UTC)
:::Indeed. Appreciate all you've done to get us here. ] (]) 22:37, 3 January 2025 (UTC)
:::{{re|DoRD}} Is that a "yes" ? — ] <sup>]</sup> 16:30, 14 November 2017 (UTC)
::::Oh, sorry, yes it is. ​—] (]) 16:39, 14 November 2017 (UTC) :], thank you for all your service, and thanks especially for being such a great mentor, colleague, and friend. ] (]) 18:21, 5 January 2025 (UTC)
:{{done}} — ] <sup>]</sup> 18:17, 14 November 2017 (UTC)
{{Archive bottom}}


==Query==
== Request for removal of my admin rights ==
So, are we losing ZERO administrators in January 2025 due to inactivity (see ])? When was the last month that happened? I guess most inactive admins have already lost their privileges (there was a big group in ]) and we are down to just active admins, well, at least active in editing if not admin work. That Criterion 2 made a big impact.


Happy New Year, everyone! <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 19:26, 1 January 2025 (UTC)
I'm sad to have to ask this but I'm not realistically going to have enough free time in at least the next couple years to be really active here and I don't want to potentially create a problem for the site. I just saw the bot's notification that I haven't been active in a year and I think that's as good a sign as any that I should give them up. I realize I can probably do so myself, but honestly I can't remember how. . :-) I've already updated my user page accordingly. Thanks for your help! <font color="#3300ff">]</font><sup><font color="#33ff00">]</font></sup><sup><font color="#ff0033">]</font></sup> 13:01, 17 November 2017 (UTC)

:October 2023? ] (]) 20:28, 1 January 2025 (UTC)
:]. — ] <sup>]</sup> 20:58, 1 January 2025 (UTC)
::I think we may have indeed at least approached a time when inactivity desysops will go down to almost nothing. I think this is the first time that I can say I think our standard for admin activity are sufficient and are working as intended. It's been a long road. ] ] 00:09, 2 January 2025 (UTC)
:::Careful not to mistake a data point for a trend. ] (]) 03:51, 2 January 2025 (UTC)
::::True, I've just causally observed it, I haven't kept stats, but when the latest round of inactivity rules were established we were seeing about three per month. We're still seeing that some months, but other months there are just one or two, and apparently this month, none. I have also noticed an uptick in admins voluntarily handing in tools but I haven't got stats for that either. On the other hand, we may be losing as many as seven next month. ] ] 21:08, 2 January 2025 (UTC)
:::::All desysoppings of administrators due to inactivity have been logged by month at ] since shortly after the process started. ] (]) 03:17, 3 January 2025 (UTC)

A more useful statistic would be drawn from the actual admin action logs from the admins lost due to inactivity over the last 14 years. It would reveal just how significant their loss was - or wasn't. A random check I just made tends to show that many of them hardly ever used their tools at all. This might bust the myth that the attrition is as critical as the community is led to believe. Many admins also lost interest in the use of the tools shortly after passing their RfA, which could lead one to believe that there is a certain ] to be gained with having one's signature highlighted in yellow everywhere - active or not. ] (]) 04:00, 3 January 2025 (UTC)

:I was poking around the admins due to be desysopped under criterion two next month, and one of them hasn't used an admin tool in eleven years. ] ] 16:24, 3 January 2025 (UTC)
:It has probably always been true that the 80-20 rule applies. Looking at , a few admins performed thousands of logged admin actions last year, while there is a quick drop as you go down the list, with a long tail of admins with a very low number (or none) of logged admin actions. Rather than worrying about how many admins we have, we need to worry about retaining the small number of admins that do most of the admin work. ] 16:25, 3 January 2025 (UTC)
::An important aspect to keep in mind is that there are plenty of administrative tasks that don't log admin actions, such as declining unblock requests, declining protection requests, processing entries at ], and a number of other tasks (with those just being the ones that sprung to mind for me). While I'm sure we all know this, I wanted to mention it for anybody reading that hadn't considered that the raw numbers aren't everything. I can think of a number of admins with less than a thousand actions last year who had more of an impact than I did with my 18 thousand+ actions (fifth overall for non bots). ] (]) 19:06, 3 January 2025 (UTC)
:::I know, but I suspect that <s>most</s> <u>very few</u> admins that have few or no logged actions are instead performing a lot of unlogged admin tasks. Personally, I don't remember performing any unlogged admin tasks last year, and I try not to assume that I'm unique. ] 21:55, 3 January 2025 (UTC)
::::I think the "not all admin actions are logged" argument is perhaps relevant in the short term, but if you haven't found occasion to preform any logged actions in over a decade, I find it highly unlikely you are doing admin work and just never, ever see a reason to use the tools. ] ] 03:23, 4 January 2025 (UTC)
:::::Yeah, to be entirely clear, I don't think there's a niche of admins doing no admin actions but working exclusively in admin areas that don't log actions.
:::::I know that a few users who process submissions at ], such as Fayenatic london and Ymblanter, don't have their entire efforts and work reflected by the action count. My point was to illustrate that the numbers themselves don't necessarily reflect the actual work put in by some admins in general. ] (]) 16:06, 4 January 2025 (UTC)
:::: We already have an edit filter logging edits to protected pages. We should ideally set up edit filters for all of the other types of unlogged "admin" action, along the same vein, and kibosh this entire concept. ] ] 03:25, 4 January 2025 (UTC)
:::::You mean like closing XFD discussions or assessing unblocks, etc., as ] notes above? - <b>]</b> 14:53, 4 January 2025 (UTC)
:::::: Yes. ] ] 16:21, 4 January 2025 (UTC)
:::::::Still not seeing it. What admin is active in closing AFDs, but never deletes anything, or is active in reviewing unblock requests, but never unblocks anyone? ] ] 07:11, 6 January 2025 (UTC)
:::::If an admin !votes at RFA and especially if they nominate, I would be very disappointed if they hadn't checked the candidates deleted edits. So that's one area where an admin might be using the tools without any recent logged admin actions. Looking at those stats I seem to do hundreds of edits for every logged admin action, and in recent years that ratio may have increased to around a thousand edits per admin action. But I like to think most of my 7,000 or so logged admin actions have been useful. '']]<span style="color:#CC5500">Chequers</span>'' 08:38, 5 January 2025 (UTC)

== ] problem ==
{{atop|1='''Jokes have no place on Misplaced Pages.''' Because I am an extremely, extremely serious person, I have blocked JavaHurricane and desysopped Sennecaster. <span style="font-family:courier"> -- ]</span><sup class="nowrap">&#91;]]</sup> <small>(])</small> 07:11, 6 January 2025 (UTC)}}
Hi, I was checking the page and found that one '''oppose''' vote is found in the ''support'' section. @] closed it at 230-0-0. But as per @]'s vote on support no. 207, it should be ended as 229-1-0. I didn't expected that administrators or monitor @] has overlooked it. Can this issue be fixed? {{small|(P.S.: I don't know whether should I brought this in BN or AN but as I think RfAs are handled by Crats, so I brought it here.)}} -- ☮️Counter-Strike:Mention 269🕉️<sup>(] ● ] ● ])</sup> 06:55, 6 January 2025 (UTC)

:Tagging @] for informing this. ☮️Counter-Strike:Mention 269🕉️<sup>(] ● ] ● ])</sup> 06:56, 6 January 2025 (UTC)
::I also sense that JavaHurricane was making a joke—{{tq|poor judgement because of running late for mop?}}, clearly a joke. ] (]) 07:00, 6 January 2025 (UTC)
: It's a joke. ] ] 06:56, 6 January 2025 (UTC)
::I apologize for not getting that joke and wasted my time bothering you all. I got it well now. ☮️Counter-Strike:Mention 269🕉️<sup>(] ● ] ● ])</sup> 07:02, 6 January 2025 (UTC)
{{abot}}

== A discussion on Signpost ==

There is a discussion on an article on Signpost that maybe of interest to bureaucrats, on whether it is appropriate of an admin should close his own re-request for adminship as a sign of resigning. ]

I took the position that it is inappropriate for the said admin to do so. ] (]) 04:18, 7 January 2025 (UTC)

:Opposition to your stated position has been unanimous over the two days since you posted it. There's nothing for 'crats to do here. ] ] 06:59, 7 January 2025 (UTC)
:I don't see how it would be inappropriate to withdraw your own RfA. ] (]) 11:36, 7 January 2025 (UTC)
::@], AIUI the issue ] has is not with withdrawing, but with ''closing the discussion'' following (or at the same time as) withdrawal. In the linked discussion I've given a lengthy reply why I don't regard that as inappropriate either, but the distinction may be important to you (or others reading this). ] (]) 13:09, 7 January 2025 (UTC)
:::Thanks @], that is a bit less straight forward than I originally thought. ] (]) 13:12, 7 January 2025 (UTC)
My 2¢: In general one should avoid closing discussions they've participated in (or are ''about'' them) but I see no problem whatsoever with withdrawing from an RfA and closing it as withdrawn. It would be a different matter if (for example) someone started an AN/I discussion, it started to boomerang, and they closed it with a "nevermind" before they received any warnings or sanctions... but that's very different from what Graham did. Kudos to him for saving the 'crats a step with the paperwork. ] (]) 18:54, 7 January 2025 (UTC)

:100% agree with 28bytes. -- ] 11:47, 8 January 2025 (UTC)
:No concerns with someone withdrawing an RFA and doing the paperwork for it, however for a RECALL RFA this would only be acceptable if immediate notice is also left here (as was done in ]). — ] <sup>]</sup> 15:37, 8 January 2025 (UTC)

== Resysop request (Arcticocean) ==

* {{rfplinks|Arcticocean}}
* Previous username: AGK

Hello. I requested self-removal of my sysop permissions in June 2021. At that time, I was becoming too busy in real life to regularly contribute to Misplaced Pages, a situation made worse by the COVID-19 pandemic. I returned as a regular contributor to Misplaced Pages some months ago but have been taking time to catch up on changes in the community. Although I remained occasionally active whilst away, I felt it important not to request the tools back until I was sure of still being in touch with the community's standards. As I'm now permanently back and have been for some time, I am requesting restoration of my sysop permissions. With thanks, ] 15:14, 9 January 2025 (UTC)

*Desysop request is at ]. – ] <small>(])</small> 15:43, 9 January 2025 (UTC)
*Last admin action appears to be May 2021. — ] <sup>]</sup> 16:02, 9 January 2025 (UTC)

<small>Is it too late to appoint them to this year's ArbCom? --] (]) 14:47, 10 January 2025 (UTC)</small>

<small>Yes 8-) -- ] (]) 14:50, 10 January 2025 (UTC)</small>

:<small>Yes it's too late, or yes that was an uncharacteristically good idea? Or both? --] (]) 14:56, 10 January 2025 (UTC)</small>

::<small> I'm enjoying my retirement from that role, although the arbitrator's pension isn't what it used to be. ] 15:04, 10 January 2025 (UTC)</small>
:::<small>(slightly - just slightly - sinister tone) It's not necessarily up to you...--] (]) 15:14, 10 January 2025 (UTC)</small>
:{{done}}. ] (]) 15:16, 10 January 2025 (UTC)

Many thanks! ] 16:15, 10 January 2025 (UTC)

Latest revision as of 16:16, 10 January 2025

Notices of interest to bureaucrats

Advice, administrator elections (AdE), requests for adminship (RfA), bureaucratship (RfB), and past request archives
Administrators
Bureaucrats
AdE/RfX participants
History & statistics
Useful pages
Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles,
content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards
    Centralized discussion
    Bureaucrat tasks
    Archiving icon
    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



    This page has archives. Sections older than 7 days may be automatically archived by Lowercase sigmabot III.
    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 17
    Approved BRFAs 0
    Requests for adminship and bureaucratship update
    No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)
    It is 18:19:36 on January 10, 2025, according to the server's time and date.


    Desysop request (Ferret)

    Ferret (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs · rfar · spi · cci) (assign permissions)

    Hi Bureaucrats. I'm requesting the removal of my administrator rights as of January 1, 2025, as I will be generally retiring. I would like my previous rights (autopatrolled, extended confirmed user, page mover, pending changes reviewer, rollbacker and template editor) restored. I would have waited a little closer to request but might not be online the next couple days. Thank you! -- ferret (talk) 17:49, 30 December 2024 (UTC)

    I've emailed Arbcom separately about checkuser, just as info! -- ferret (talk) 17:54, 30 December 2024 (UTC)
    Per your wishes, I have removed the tools. I realise this is a day or so early, so if you do need to use the tools in the meantime I can revert
    On a personal note, I'm sad to see you go. Thank you for your service. Lee Vilenski 19:13, 30 December 2024 (UTC)
    Thank you for your years of service, Ferret. Enjoy your retirement! Liz 19:15, 1 January 2025 (UTC)
    Indeed. Appreciate all you've done to get us here. BusterD (talk) 22:37, 3 January 2025 (UTC)
    ferret, thank you for all your service, and thanks especially for being such a great mentor, colleague, and friend. Drmies (talk) 18:21, 5 January 2025 (UTC)

    Query

    So, are we losing ZERO administrators in January 2025 due to inactivity (see Misplaced Pages:Inactive administrators#January 2025)? When was the last month that happened? I guess most inactive admins have already lost their privileges (there was a big group in 2023) and we are down to just active admins, well, at least active in editing if not admin work. That Criterion 2 made a big impact.

    Happy New Year, everyone! Liz 19:26, 1 January 2025 (UTC)

    October 2023? Ymblanter (talk) 20:28, 1 January 2025 (UTC)
    Aug 2024. — xaosflux 20:58, 1 January 2025 (UTC)
    I think we may have indeed at least approached a time when inactivity desysops will go down to almost nothing. I think this is the first time that I can say I think our standard for admin activity are sufficient and are working as intended. It's been a long road. Beeblebrox 00:09, 2 January 2025 (UTC)
    Careful not to mistake a data point for a trend. Floquenbeam (talk) 03:51, 2 January 2025 (UTC)
    True, I've just causally observed it, I haven't kept stats, but when the latest round of inactivity rules were established we were seeing about three per month. We're still seeing that some months, but other months there are just one or two, and apparently this month, none. I have also noticed an uptick in admins voluntarily handing in tools but I haven't got stats for that either. On the other hand, we may be losing as many as seven next month. Beeblebrox 21:08, 2 January 2025 (UTC)
    All desysoppings of administrators due to inactivity have been logged by month at Misplaced Pages:Inactive administrators since shortly after the process started. Graham87 (talk) 03:17, 3 January 2025 (UTC)

    A more useful statistic would be drawn from the actual admin action logs from the admins lost due to inactivity over the last 14 years. It would reveal just how significant their loss was - or wasn't. A random check I just made tends to show that many of them hardly ever used their tools at all. This might bust the myth that the attrition is as critical as the community is led to believe. Many admins also lost interest in the use of the tools shortly after passing their RfA, which could lead one to believe that there is a certain social capital to be gained with having one's signature highlighted in yellow everywhere - active or not. Kudpung กุดผึ้ง (talk) 04:00, 3 January 2025 (UTC)

    I was poking around the admins due to be desysopped under criterion two next month, and one of them hasn't used an admin tool in eleven years. Beeblebrox 16:24, 3 January 2025 (UTC)
    It has probably always been true that the 80-20 rule applies. Looking at , a few admins performed thousands of logged admin actions last year, while there is a quick drop as you go down the list, with a long tail of admins with a very low number (or none) of logged admin actions. Rather than worrying about how many admins we have, we need to worry about retaining the small number of admins that do most of the admin work. Donald Albury 16:25, 3 January 2025 (UTC)
    An important aspect to keep in mind is that there are plenty of administrative tasks that don't log admin actions, such as declining unblock requests, declining protection requests, processing entries at WP:CFDS/Working, and a number of other tasks (with those just being the ones that sprung to mind for me). While I'm sure we all know this, I wanted to mention it for anybody reading that hadn't considered that the raw numbers aren't everything. I can think of a number of admins with less than a thousand actions last year who had more of an impact than I did with my 18 thousand+ actions (fifth overall for non bots). Hey man im josh (talk) 19:06, 3 January 2025 (UTC)
    I know, but I suspect that most very few admins that have few or no logged actions are instead performing a lot of unlogged admin tasks. Personally, I don't remember performing any unlogged admin tasks last year, and I try not to assume that I'm unique. Donald Albury 21:55, 3 January 2025 (UTC)
    I think the "not all admin actions are logged" argument is perhaps relevant in the short term, but if you haven't found occasion to preform any logged actions in over a decade, I find it highly unlikely you are doing admin work and just never, ever see a reason to use the tools. Beeblebrox 03:23, 4 January 2025 (UTC)
    Yeah, to be entirely clear, I don't think there's a niche of admins doing no admin actions but working exclusively in admin areas that don't log actions.
    I know that a few users who process submissions at WP:CFDS, such as Fayenatic london and Ymblanter, don't have their entire efforts and work reflected by the action count. My point was to illustrate that the numbers themselves don't necessarily reflect the actual work put in by some admins in general. Hey man im josh (talk) 16:06, 4 January 2025 (UTC)
    We already have an edit filter logging edits to protected pages. We should ideally set up edit filters for all of the other types of unlogged "admin" action, along the same vein, and kibosh this entire concept. * Pppery * it has begun... 03:25, 4 January 2025 (UTC)
    You mean like closing XFD discussions or assessing unblocks, etc., as Hey man im josh notes above? - jc37 14:53, 4 January 2025 (UTC)
    Yes. * Pppery * it has begun... 16:21, 4 January 2025 (UTC)
    Still not seeing it. What admin is active in closing AFDs, but never deletes anything, or is active in reviewing unblock requests, but never unblocks anyone? Beeblebrox 07:11, 6 January 2025 (UTC)
    If an admin !votes at RFA and especially if they nominate, I would be very disappointed if they hadn't checked the candidates deleted edits. So that's one area where an admin might be using the tools without any recent logged admin actions. Looking at those stats I seem to do hundreds of edits for every logged admin action, and in recent years that ratio may have increased to around a thousand edits per admin action. But I like to think most of my 7,000 or so logged admin actions have been useful. ϢereSpielChequers 08:38, 5 January 2025 (UTC)

    Misplaced Pages:Requests for adminship/Sennecaster problem

    Jokes have no place on Misplaced Pages. Because I am an extremely, extremely serious person, I have blocked JavaHurricane and desysopped Sennecaster. -- Tamzin (they|xe|🤷) 07:11, 6 January 2025 (UTC)

    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.


    Hi, I was checking the page and found that one oppose vote is found in the support section. @AmandaNP closed it at 230-0-0. But as per @JavaHurricane's vote on support no. 207, it should be ended as 229-1-0. I didn't expected that administrators or monitor @Tamzin has overlooked it. Can this issue be fixed? (P.S.: I don't know whether should I brought this in BN or AN but as I think RfAs are handled by Crats, so I brought it here.) -- ☮️Counter-Strike:Mention 269🕉️ 06:55, 6 January 2025 (UTC)

    Tagging @Sennecaster for informing this. ☮️Counter-Strike:Mention 269🕉️ 06:56, 6 January 2025 (UTC)
    I also sense that JavaHurricane was making a joke—poor judgement because of running late for mop?, clearly a joke. The AP (talk) 07:00, 6 January 2025 (UTC)
    It's a joke. * Pppery * it has begun... 06:56, 6 January 2025 (UTC)
    I apologize for not getting that joke and wasted my time bothering you all. I got it well now. ☮️Counter-Strike:Mention 269🕉️ 07:02, 6 January 2025 (UTC)
    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.

    A discussion on Signpost

    There is a discussion on an article on Signpost that maybe of interest to bureaucrats, on whether it is appropriate of an admin should close his own re-request for adminship as a sign of resigning. Misplaced Pages talk:Misplaced Pages Signpost/2024-12-24/Opinion

    I took the position that it is inappropriate for the said admin to do so. SYSS Mouse (talk) 04:18, 7 January 2025 (UTC)

    Opposition to your stated position has been unanimous over the two days since you posted it. There's nothing for 'crats to do here. Beeblebrox 06:59, 7 January 2025 (UTC)
    I don't see how it would be inappropriate to withdraw your own RfA. Hey man im josh (talk) 11:36, 7 January 2025 (UTC)
    @Hey man im josh, AIUI the issue SYSS Mouse has is not with withdrawing, but with closing the discussion following (or at the same time as) withdrawal. In the linked discussion I've given a lengthy reply why I don't regard that as inappropriate either, but the distinction may be important to you (or others reading this). Thryduulf (talk) 13:09, 7 January 2025 (UTC)
    Thanks @Thryduulf, that is a bit less straight forward than I originally thought. Hey man im josh (talk) 13:12, 7 January 2025 (UTC)

    My 2¢: In general one should avoid closing discussions they've participated in (or are about them) but I see no problem whatsoever with withdrawing from an RfA and closing it as withdrawn. It would be a different matter if (for example) someone started an AN/I discussion, it started to boomerang, and they closed it with a "nevermind" before they received any warnings or sanctions... but that's very different from what Graham did. Kudos to him for saving the 'crats a step with the paperwork. 28bytes (talk) 18:54, 7 January 2025 (UTC)

    100% agree with 28bytes. -- Amanda (she/her) 11:47, 8 January 2025 (UTC)
    No concerns with someone withdrawing an RFA and doing the paperwork for it, however for a RECALL RFA this would only be acceptable if immediate notice is also left here (as was done in Misplaced Pages:Bureaucrats'_noticeboard/Archive_50#Desysop_request_(Graham87)). — xaosflux 15:37, 8 January 2025 (UTC)

    Resysop request (Arcticocean)

    Hello. I requested self-removal of my sysop permissions in June 2021. At that time, I was becoming too busy in real life to regularly contribute to Misplaced Pages, a situation made worse by the COVID-19 pandemic. I returned as a regular contributor to Misplaced Pages some months ago but have been taking time to catch up on changes in the community. Although I remained occasionally active whilst away, I felt it important not to request the tools back until I was sure of still being in touch with the community's standards. As I'm now permanently back and have been for some time, I am requesting restoration of my sysop permissions. With thanks, arcticocean ■ 15:14, 9 January 2025 (UTC)

    Is it too late to appoint them to this year's ArbCom? --Floquenbeam (talk) 14:47, 10 January 2025 (UTC)

    Yes 8-) -- Avi (talk) 14:50, 10 January 2025 (UTC)

    Yes it's too late, or yes that was an uncharacteristically good idea? Or both? --Floquenbeam (talk) 14:56, 10 January 2025 (UTC)
    I'm enjoying my retirement from that role, although the arbitrator's pension isn't what it used to be. arcticocean ■ 15:04, 10 January 2025 (UTC)
    (slightly - just slightly - sinister tone) It's not necessarily up to you...--Floquenbeam (talk) 15:14, 10 January 2025 (UTC)
     Done. Primefac (talk) 15:16, 10 January 2025 (UTC)

    Many thanks! arcticocean ■ 16:15, 10 January 2025 (UTC)

    Categories: