Wikipedia:Bureaucrats' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Lee Vilenski (talk | contribs) at 07:19, 1 December 2022 (→‎Suspension of admin privs - Nancy: Perms removed.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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.

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 all of them keep an eye on the time remaining on these discussions. Thank you for your patience.

To request your administrator status to be removed, initiate a new section below.

Crat tasks
RfAs 0
RfBs 0
Overdue RfBs 0
Overdue RfAs 0
BRFAs 16
Approved BRFAs 0
Requests for adminship and bureaucratshipupdate
No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)
It is 00:55:46 on March 27, 2023, according to the server's time and date.

Resysop request (TheresNoTime)


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.

TheresNoTime (t · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma· non-automated edits · BLP edits · undos · rollbacks · logs (blocks · rights · moves) · rfar · spi) (assign permissions)(acc · ap · fm · mms · npr · pm · pcr · rb · te)


I wish to request the reinstatement of my sysop permissions (and ideally the IA I had at the time, but that can wait/be a separate request if needed).

For transparency, I resigned a couple of weeks ago during the closing day(s) of this ArbCom case (see also this motion in said case). Many thanks — TheresNoTime (talk • they/them) 20:08, 21 November 2022 (UTC)Reply[reply]

  • Standard minimum 24-hold for comments apply. As linked above, arbcom has not imposed any prohibition from skipping RfA as a result of their case; however the policy requirement of If there were serious questions about the appropriateness of the former admin's status as an administrator at the time of resignation certainly still applies. At the time of resignation (2022-11-01T12:19:08) there was an open arbcom case that was in the voting stage. The votes at the time were in favor of admonishment for serious breaches of Wikipedia's administrative norms and of the CheckUser policy, but were unanimously opposed to desysoping. So now it needs to be determined if this policy criteria was active or not. I can see an argument that the prohibiting criteria was in effect, in that a case is by nature a "serious question"; however I can also see arguments that it was not in effect in that the desysop remedy vote was failing meant that this was no longer "at question". Comments welcome below. — xaosflux Talk 20:46, 21 November 2022 (UTC)Reply[reply]
    As far as my own !cratvote, I'm leading toward support restore; the purpose of the "cloud" rule is primarily so that an admin under scrutiny doesn't avoid additional scrutiny by resigning - as further investigation could be a huge time sink for everyone involved. In this specific case, neither the investigation nor possible removal remedies appear to be impacted by the resignation. — xaosflux Talk 20:55, 21 November 2022 (UTC)Reply[reply]
  • I agree with Xaosflux, above. I see nothing that would prevent the admin bit from being retwiddled. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 21:07, 21 November 2022 (UTC)Reply[reply]
  • Not a crat, but I agree with everyone above that this can go through. * Pppery * it has begun... 21:11, 21 November 2022 (UTC)Reply[reply]
  • This is not a typical "under a cloud" case where we don't know what the outcome would have been. ArbCom said "don't desysop". If TNT hadn't resigned, they'd still be an admin right now, and anyone who had a problem with that fact would have to start a second ArbCom case. The fact that TNT did resign is irrelevant. Suffusion of Yellow (talk) 21:21, 21 November 2022 (UTC)Reply[reply]
    I actually think you're eliding an important point. The WP:CLOUD metaphor is not one specific ArbCom thing but rather ...the purpose, or with the effect, of evading scrutiny of their actions that could have led to sanctions (quoted from WP:RESYSOP). In terms of ArbCom's opinion in this particular case, it may be pretty clearly and cleanly decided (e.g. the WP:RESYSOP footnote citing Wikipedia:Requests for arbitration/Scientology#Return of access levels), but there are more to clouds than just ArbCom and there is more to scrutiny than just whether or not ArbCom still has desysop-ing on the table. Without opining on the case at hand, it's not irrelevant that someone resigns the tools. ArbCom removing the tools is a difficult step to clear, but there being murky/cloudy circumstances around someone is intentionally a lower standard. Bureaucrats saying "This could be dodgy, spend a week at RfA" is supposed to be an intermediate between "Clearly no issues" and "ArbCom took the tools away." One could think another has a cloud but support them at RfA, and bureaucrats have room outside of "is there an ArbCom PD that could pass?" ~ Amory (utc) 22:11, 21 November 2022 (UTC)Reply[reply]
    I'm not aware of any non-case proceedings that were open in parallel at the time of the resignation (and generally the community abandons pursuing community sanctions once it has been escalated to arbcom) - but if there were and such a discussion was cut short because of the resignation, that could be its own issue. (Anyone wanting to present this please provide permalinks). — xaosflux Talk 22:34, 21 November 2022 (UTC)Reply[reply]
    Sorry, wasn't meaning to imply there were any here, I don't think there were/are (beyond the PD talk, etc.). Just noting that there's more than just AC (or should be) for this sort of thing. ~ Amory (utc) 23:09, 21 November 2022 (UTC)Reply[reply]
    My understanding of resignation under a cloud is that it is not limited to resolutions in an ArbCom case; the phrasing used is serious questions about the appropriateness of the former admin's status as an administrator at the time of resignation. If serious questions about whether TNT's violation of involved made their status as an administrator inappropriate existed in the broader community at the time of resignation, then an automatic reapproval may not be appropriate. BilledMammal (talk) 01:37, 22 November 2022 (UTC)Reply[reply]
  • No concerns from me. NW1223<Howl at meMy hunts> 21:25, 21 November 2022 (UTC)Reply[reply]
  • Speaking with my arb hat on and not with my crat hat on and explicitly not voting as a crat because I believe it would be inappropriate to do so. I do not believe the committee would have desysopped, we had unanimously disagreed with doing so at the time of resignation, and there was a majority. What's more, the Arbcom requirement from over a decade ago that a person cannot be automatically resysopped after quitting during a case did not consider the scenario that we had already disagreed with with a desysop. WormTT(talk) 22:12, 21 November 2022 (UTC)Reply[reply]
    I have to agree with Worm here. This was a unique situation in that we had already explicitly voted not to remove the admin bit just before it was resigned. I'm pretty sure that "unprecedented" can be taken literally here and that therefore the cloud rule simply does not apply. Beeblebrox (talk) 03:45, 22 November 2022 (UTC)Reply[reply]
  • I don't have any issues with restoring the toolset - with the usual delay of course. I am a bit worried about the context of what went on, and would stress to TNT to not go down the same road. I've not read all of the arbcom case that is associated with this, but it's very clear that there was no want to remove the tools, and at the time it was stated that the tools weren't "on the line" (so to speak). Disgression is the better part of Valor. There's no policy reason why the toolset can't be returned for a voluntary removal like this. Lee Vilenski (talkcontribs) 22:18, 21 November 2022 (UTC)Reply[reply]
    I feel like my hand is involved when it comes to this, so I won't be touching the buttons, but I think Lee made precisely the point I was coming to make. -- Amanda (she/her) 22:41, 21 November 2022 (UTC)Reply[reply]
    @Lee Vilenski: just FYI, it's "discretion", as in being discrete; see wikt:discretion and indeed wikt:discretion is the better part of valour. HJ Mitchell | Penny for your thoughts? 12:08, 22 November 2022 (UTC) </pedantry> If you're okay with more pedantry, I'll just fix your own misspellings... Primefac (talk) 12:14, 22 November 2022 (UTC)Reply[reply]
  • Based on the circumstances of the (self-)desysop and the feedback from the committee regarding it, I have to agree with my fellow ’crats that this request should be granted after the standard hold. Welcome back, TNT. 28bytes (talk) 03:30, 22 November 2022 (UTC)Reply[reply]
  • My vote would be to restore the admin tools for reasons I will explain in a moment; however, I'm not sure we should be voting to restore before we discuss if this request is one that comes under "In doubtful cases, re-granting will be deferred until a broader community discussion takes place and is closed.". Also, just for clarity, it would be helpful if TheresNoTime stated that they did not resign in order to avoid "imminent exposure, scrutiny or sanction".
    My own reading of the situation, and why I am in favour of restoring the tools, is that given that TNT had requested the case be held in public, and that at the time of the request the ArbCom desyop proposal was not passing, I can't see how the request could be motivated to avoid scrutiny or sanction. They had requested public scrutiny, and they were not going to be sanctioned by having the tools removed. I personally regard temporarily resigning the tools in a stressful situation to be a sensible and applaudable decision, and something that all admins should consider doing when faced with stress.
    However, as I say, I am reluctant to apply my vote until we have decided if this request should be classed as a "doubtful case". I think it is a "doubtful case", but at the same time I doubt if there would be sufficient objections from the community to a resysop to justify holding a "broader community discussion", and so having such a discussion could be seen as unnecessarily bureaucratic. So my inclination is that a broader discussion is not warranted; however, I would welcome more thoughts on this, and particularly input from the community as to if a broader discussion is something desired. SilkTork (talk) 10:08, 22 November 2022 (UTC)Reply[reply]
    It could be argued that what we are having now is a "broader community discussion" given that this is a discussion among members of thecommunity that is broader than just the crats. Obviously it's not as broad as one at somewhere like AN would be, let alone RFA, but if the rules intended to specifically mandate an RFA they would explicitly refer to RFA rather than a vague phrase like "broader community discussion". Thryduulf (talk) 11:51, 22 November 2022 (UTC)Reply[reply]
    In your experience Thryduulf, is there so far greater community input into this request than normal? If so, I think I could agree with your argument. SilkTork (talk) 12:27, 22 November 2022 (UTC)Reply[reply]
    If we consider all resysop requests then yes this clearly has more interaction than normal. I think it would be more relevant to consider resysop requests as falling into two types - (1) those that are obviously not at all controversial and (2) others (including this request). The reason for the split being that very few people see any need or benefit to commenting on type 1 requests (in all cases discounting post-restoration "welcome back" type comments). Considering the set of type 2 requests I would say this is at the high end of the normal range. Thryduulf (talk) 12:44, 22 November 2022 (UTC)Reply[reply]
    I don't think it's a good idea to simply label this discussion, after the fact, as a broader community discussion. The members of the community that like to discuss these matters know that the bureaucrats have the responsibility of evaluating the circumstances of how administrative privileges are relinquished, and this influences participation in what is generally considered a bureaucrat discussion. A community discussion should be announced as such in suitable venues, inviting greater participation. isaacl (talk) 22:21, 22 November 2022 (UTC)Reply[reply]
    In response to the request for clarity (it would be helpful if TheresNoTime stated that they did not resign in order to avoid "imminent exposure, scrutiny or sanction".), I certainly didn't do so to avoid further scrutiny. As I saw it, the result was a "done deal", and all "exposure, scrutiny or sanctions" had been levied. On a more cautious note, that situation put me over my own "red line" in regards to my health, at which point resignation was not only a matter of being upset, but peace of mind. — TheresNoTime (talk • they/them) 12:51, 22 November 2022 (UTC)Reply[reply]
    Thanks for that TheresNoTime. That is exactly how I viewed it, and also why I felt at the time that your request should be immediately actioned. Given all the circumstances, including Thryduulf's observation that this discussion could well serve as the "broader community discussion", I can't see any reasonable impediment to the tools being restored. SilkTork (talk) 13:52, 22 November 2022 (UTC)Reply[reply]
    @SilkTork I'd say this discussion itself satisfies a "broader discussion", and would support any reasonable extensions in the minimum time requested. — xaosflux Talk 16:30, 22 November 2022 (UTC)Reply[reply]
  • I don't see how ArbCom could have been more explicit that this is fine, and I am happy to see TNT return to adminship. —Kusma (talk) 10:22, 22 November 2022 (UTC)Reply[reply]
  • The case had reached its apex at the time that TNT had resigned, and it did not seem that the outcome would have been altered in any way as a result of her resigning or not resigning. WP:CLOUD states that cloudiness is determined when there seems a plausible chance their resignation was in part designed to evade or frustrate formal discussion of their conduct. The formal discussion had concluded. No further recriminations were pursued by the community, as they very well could have done so. Restoration of rights should be a done deal here. --🌈WaltCip-(talk) 14:19, 22 November 2022 (UTC)Reply[reply]

There's clear consensus here. Restoring the mop. --Dweller (talk) Old fashioned is the new thing! 22:21, 22 November 2022 (UTC)Reply[reply]

Is this a joke? An admin resigns for misusing the mop, and is given the mop back by a simple request? For the record, I would appreciate confirmation that TheresNoTime didn't also misuse the mop in my one and only interaction with her, at FormalDude's talk page, in which she threatened me with her very admin-ness. Posting on mobile, so can't provide diffs right now. But this is absolutely not an acceptable situation, by any stretch of the imagination. TheresNoTime should be required to go through the entire RfB process from scratch, with her recent conduct in full view for everyone to see. Homeostasis07 (talk/contributions) 02:39, 23 November 2022 (UTC)Reply[reply]
TheresNoTime did not resign for misusing the mop, she resigned in part for misusing checkuser tools, which she has not gotten (and will not get) back here. * Pppery * it has begun... 02:49, 23 November 2022 (UTC)Reply[reply]
These are the diffs I believe Homeostasis07 is referring to — Special:Diff/1077914768, Special:Diff/1077916517, Special:Diff/1077917307, Special:Diff/1077918276 (and the permalink talk section for ease of reading). I don't personally believe that I misuse[d] the mop in that interaction (nor do I believe I threatened [them] with [my] very admin-ness) — TheresNoTime (talk • they/them) 02:54, 23 November 2022 (UTC)Reply[reply]
"despite an administrator telling you not to" and "I won't ask you again" coupled with a threat to take me to ANI for daring not to do exactly what you say is most definitely a threat. And thanks for confirming that you did indeed use the tools on me during that interaction. There was absolutely no reason for you to believe my account was in any way compromised, or that I was in any way colluding with any other user in that interaction. This user does not deserve reinstatement. Homeostasis07 (talk/contributions) 03:38, 23 November 2022 (UTC)Reply[reply]
"thanks for confirming that you did indeed use the tools on me during that interaction" - what are you on about..? — TheresNoTime (talk • they/them) 03:42, 23 November 2022 (UTC)Reply[reply]
"I don't personally believe I misuse[d] the mop in that interaction" = you used the tools but don't believe it was a misuse. It's clearly a longstanding pattern of tool abuse; you use the tools on any user you disagree with. Homeostasis07 (talk/contributions) 03:47, 23 November 2022 (UTC)Reply[reply]
@Homeostasis07: I think you may have misunderstood my statement — when I said "I don't personally believe that I "misuse[d] the mop" in that interaction", I meant that seeing as I clearly didn't take any administrative actions during that interaction, I couldn't have misused the tools... as they weren't used? — TheresNoTime (talk • they/them) 03:50, 23 November 2022 (UTC)Reply[reply]
I want specific confirmation from someone else that TheresNoTime didn't access my personal details through the CheckUser tool on March 28 last. I have no interest in continuing the current pedantic nonsense with her above. If anything, her behavior here is confirmation she does not deserve reinstatement. Homeostasis07 (talk/contributions) 03:59, 23 November 2022 (UTC)Reply[reply]
No one has used the CheckUser tool on your account. Izno (talk) 04:02, 23 November 2022 (UTC)Reply[reply]
@Homeostasis07: I'm sorry if any of this came across as pedantic. As has now been confirmed to you, I've never used any "tools" on your account. I'd appreciate an apology, as most of what you've said is fairly baseless. — TheresNoTime (talk • they/them) 04:08, 23 November 2022 (UTC)Reply[reply]


  • No objections, contingent on the +admin passing above. — xaosflux Talk 20:52, 21 November 2022 (UTC)Reply[reply]
  • No objections here, either, provided the admin bit is retwiddled. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 21:07, 21 November 2022 (UTC)Reply[reply]
  • Comment in principle I have no objection to TNT regaining all tools, I argued as much before the case kicked off. But I do think we should establish categorically that the ArbCom would not have been minded to revoke any tools had the case continued. This is purely to not establish a precedent that you can "resign under a cloud" at a point in time when a vote appears to be in your favour and then later roll back in purely on that basis.  — Amakuru (talk) 21:21, 21 November 2022 (UTC)Reply[reply]
  • Given that the circumstances of the resignation were completely unrelated to TNT's being an interface administrator, arbcom were not considering (nor was there any reason why they would consider) removing that permission, and there were (to my knowledge) no discussions about their actions as an interface admin at the time they resigned the tools, I can see no reason why this bit shouldn't be restored if they are reinstated as an administrator. Whether they should be reinstated as an administrator is something I have not yet formed an opinion on. Thryduulf (talk) 01:10, 22 November 2022 (UTC)Reply[reply]
  • If admin bit is restored then the intadmin bit should also be restored. SilkTork (talk) 10:10, 22 November 2022 (UTC)Reply[reply]
    In a proper bureaucracy, wouldn't that need an extra 24 hours wait, as only admins can apply for intadmin?Kusma (talk) 10:15, 22 November 2022 (UTC)Reply[reply]
    IntAdmin can be restored immediately upon request by any admin who previously held the permission, so... no. Primefac (talk) 10:18, 22 November 2022 (UTC)Reply[reply]
    I should have known we have a rule for this. Anyway, no objections. —Kusma (talk) 10:23, 22 November 2022 (UTC)Reply[reply]

Restored. --Dweller (talk) Old fashioned is the new thing! 22:23, 22 November 2022 (UTC)Reply[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 (Eddie891)

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.

Eddie891 (current rights · rights management · rights log (local) · rights log (global/meta) · block log)
Hi, I was de-sysop'ed upon request about a month ago. While I'm not interested in going into great detail about my personal life, I have been going through some mental issues regarding depression and pretty serious suicidal ideation. I requested de-adminship in the throes of that as a way of both cutting myself off from things I enjoyed and ensuring that I did not do something with the tools that I regretted.
I have been working to address those issues and think I'm in a much better (though still not perfect) place right now on the balance. I do feel ready to request the toolset again and hopefully become somewhat (re)involved with the community I have grown to appreciate so much. I don't think this would constitute a resignation under a cloud, and I don't think anything major has changed that would stand in the way of this request, but respect the communities judgment on both counts. Best, Eddie891 Talk Work 21:42, 25 November 2022 (UTC)Reply[reply]
Happy to hear you are feeling a bit better. I don't see any issues - regular 24 hour hold for comments. Lee Vilenski (talkcontribs) 22:47, 25 November 2022 (UTC)Reply[reply]
 Done. Primefac (talk) 07:45, 27 November 2022 (UTC)Reply[reply]

Admitenttly im a bit hesitant because they are in the middle of some personal issues and regaining his tools might worsen his condition,i would much rather prefer a level-headed admin but i am open to being subject to other opinions-- (talk) 07:27, 27 November 2022 (UTC)Reply[reply]

That's irrelevant to the decision here. In principle we know nothing about the private lives or situations of our editors, and they have no bearing on decisions made on-wiki. Eddie will be judged by their contributions here, and the fact that they've chosen to divulge the health issues they've been facing does not change that. Wishing you all the best and glad you're feeling somewhat better, @Eddie891:.  — Amakuru (talk) 08:39, 27 November 2022 (UTC)Reply[reply]
In principle we know nothing until someone elects to tell us. There is nothing in the rules to inhibit the return of the tools, though it is appropriate to take greater care in some situations, such as when a user tells us they were concerned they may misuse the tools, and are "still not perfect". Personally, I would have liked a bit more discussion with Eddie to find out how secure they are (I did email them yesterday, though they have not responded). In situations like this, the return of the tools could aid someone's recovery, and I hope that is the case here. I echo Amakuru's sentiment, and wish Eddie all the best. SilkTork (talk) 11:08, 27 November 2022 (UTC)Reply[reply]
I'm willing to go into greater depth over email, but just a note that I do feel capable of acting on-wiki in as level headed a manner as ever. And I would expect my actions to be held to the same standard as any other user, so my contributions will hopefully reflect this. Eddie891 Talk Work 17:40, 27 November 2022 (UTC)Reply[reply]
Eddie and I have spoken over email, and I am confident they will continue to use the tools in a responsible manner. That they had the courage and good sense to hand them in when they were in crisis is a strong indicator that Eddie can be trusted. I will repeat what I have said previously, that I respect every admin who has the good sense to hand in the tools when they are under stress in any way. And we don't need to know the reasons. SilkTork (talk) 18:24, 27 November 2022 (UTC)Reply[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.

Suspension of admin permissions (Alex.muller)

Alex.muller (t · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma· non-automated edits · BLP edits · undos · rollbacks · logs (blocks · rights · moves) · rfar · spi) (assign permissions)(acc · ap · fm · mms · npr · pm · pcr · rb · te)

Hi there - unfortunately I don't have time to be involved in the project at the moment. Following WP:INACTIVITY please feel free to remove my admin permissions. Thanks! Alex Muller 09:26, 29 November 2022 (UTC)Reply[reply]

I've done that, thanks for all you've done as an admin. Hope we see you back again at some point in the future. ϢereSpielChequers 09:37, 29 November 2022 (UTC)Reply[reply]
Job Done.png Job Done
Awarded to Alex Muller for good services as an admin, and for resigning the tools in a noble manner. SilkTork (talk) 11:02, 29 November 2022 (UTC)Reply[reply]
Fun fact for Alex: It looks like the above request was your 11,111th edit. As much as I hope you have time for Wikipedia again in the future, kudos on stepping away in style. :) — Rhododendrites talk \\ 20:35, 29 November 2022 (UTC)Reply[reply]

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

  1. Andrew Yong (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    Last admin log: February 2017
  2. Dbenbenn (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    Last admin log: July 2011
  3. DESiegel (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    Last admin log: November 2021
  4. Xdamr (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    Last admin log: May 2015
xaosflux Talk 00:34, 1 December 2022 (UTC)Reply[reply]

Notice - large number of pending admin removals for next month

Due to the new admin requirements, there are a very large number of admins listed at Wikipedia:Inactive administrators/2023. This was expected, but can be quite striking to see. If anyone sees any thing wrong with the reporting, please bring it up sooner than later. Thank you! — xaosflux Talk 00:43, 1 December 2022 (UTC)Reply[reply]

It is rather striking to see a list that long, but it really drives home the point of the new rule: having that many admins who are not actively engaged with the community is not a good thing, as we've seen again and again. That's not to say anyone on that list is a problem, rather that none of them are a problem yet. The lowest numbers on there are two admins who have made seven edits in the last five years, and some that have not used admin tools in over a decade. One thing that did jump out at me is Xdamr, who is already listed in the above section for removal this month. Beeblebrox (talk) 01:09, 1 December 2022 (UTC)Reply[reply]
@Beeblebrox thanks for the note, should fall off during the next bot run - will watch for it. — xaosflux Talk 01:28, 1 December 2022 (UTC)Reply[reply]
Thanks for the headsup. For those of us who've been around a while it's an extraordinary list, and not just because of the length. 131? That more than decimates the admin corps... BusterD (talk) 01:39, 1 December 2022 (UTC)Reply[reply]
The whole point of doing this is that these folks already are not admins. What it does is make itr clearer how many admins there actually are. Beeblebrox (talk) 02:07, 1 December 2022 (UTC)Reply[reply]
You are quite correct. I was bemoaning the number despite my qualification. My first admin coach is on the list and several editors who were important influences. BusterD (talk) 02:26, 1 December 2022 (UTC)Reply[reply]
It is sort of sad to see so many names on that list that I remember as very active at one time. Of course, I've had my low activity spells as well (just 17 edits in all of 2017), but I came back. Donald Albury 02:31, 1 December 2022 (UTC)Reply[reply]
In your lowest 5-year period (2013-2017), you made 837 edits. That's more than 8 times as many as would be required to not get desysopped under these rules, and I would argue that factor matters. * Pppery * it has begun... 02:39, 1 December 2022 (UTC)Reply[reply]
Three on the list are still active around the movement, which is good (the developer folks I could identify, Tim, Aaron, and Hashar). I daresay they're being useful still. Izno (talk) 03:22, 1 December 2022 (UTC)Reply[reply]

Removal of admin permissions (Pathoschild)

Pathoschild (current rights · rights management · rights log (local) · rights log (global/meta) · block log)

Hi! Feel free to remove my admin permissions per the new inactivity rules. I'm still around for Synchbot, but I'm no longer active as an admin. —Pathoschild (talk) 02:10, 1 December 2022 (UTC)Reply[reply]

 Done Thank you for your long service, Pathoschild. Acalamari 02:19, 1 December 2022 (UTC)Reply[reply]
Thank you for helping us get where we are, Pathoschild. BusterD (talk) 02:27, 1 December 2022 (UTC)Reply[reply]

Suspension of admin privs - Nancy

Nancy (t · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma· non-automated edits · BLP edits · undos · rollbacks · logs (blocks · rights · moves) · rfar · spi) (assign permissions)(acc · ap · fm · mms · npr · pm · pcr · rb · te)
Hi there - with regret I find that (not so) recent changes in my life mean that I no longer have the time to contribute to the project as an editor let alone as an admin. It has been some years (a pedant may point out that it has been a decade) since I was active on a daily basis; writing articles, deleting articles and all points in between. I find therefore that I must reluctantly request the suspension of my admin access per WP:INACTIVITY
It was great fun and tremendously fulfilling to have been a part of the project, especially in the early days, and I hope the door can remain open for a return at some point.
Many thanks and kindest regards, Nancy (talk) 03:46, 1 December 2022 (UTC)Reply[reply]
 Done Thank you for your service, and resigning the bit with decorum. I've given you rollbacker rights, which you had previously, let me know if you want this removed also. Lee Vilenski (talkcontribs) 07:19, 1 December 2022 (UTC)Reply[reply]