Wikipedia:MONITOR

☆ Save On Wikipedia ↗
Requests for adminship and bureaucratship update
RfA candidateSONS %StatusEnding (UTC)Time leftDups?Report
TechnoSquirrel69 171 0 1 100 Open 17:15, 30 June 2026 2 days, 19 hours no report
Chipmunkdavis 183 0 0 100 Open 10:32, 30 June 2026 2 days, 12 hours no report
The current time is 22:05, 27 June 2026 (UTC). —
Requests for adminship and bureaucratship update
RfA candidateSONS %StatusEnding (UTC)Time leftDups?Report
TechnoSquirrel69 171 0 1 100 Open 17:15, 30 June 2026 2 days, 19 hours no report
Chipmunkdavis 183 0 0 100 Open 10:32, 30 June 2026 2 days, 12 hours no report
The current time is 22:05, 27 June 2026 (UTC). —

Requests for adminship (RfA) is one of two processes by which the Wikipedia community decides who will become administrators (also known as admins), who are users with access to additional technical features that aid in maintenance. Users can either submit their own requests for adminship (self-nomination) or may be nominated by other users. Please be familiar with the administrators' reading list, how-to guide, and guide to requests for adminship before submitting your request. Also, consider asking the community about your chances of passing an RfA.

This page also hosts requests for bureaucratship (RfB), where new bureaucrats are selected.

If you are new to participating in a request for adminship, or are not sure how to gauge the candidate, then kindly go through this mini guide for RfA voters before you participate.

Administrator elections, the other process to confer adminship, take place every five months.[1] Prospective administrators may freely choose which process to use. The next administrator election is scheduled for October 2026.

About administrators

The additional features granted to administrators are considered to require a high level of trust from the community. While administrative actions are publicly logged and can be reverted by other administrators just as other edits can be, the actions of administrators involve features that can affect the entire site. Among other functions, administrators are responsible for blocking users from editing, controlling page protection, and deleting pages. However, they are not the final arbiters in content disputes and do not have special powers to decide on content matters, except to enforce community consensus and Arbitration Committee decisions by protecting or deleting pages and applying sanctions to users.

About RfA

Recent RfA, RfBs, and admin elections ()
Candidate Type Result Date of close Tally
S O N/A %
Bonadea AE Elected 20 May 2026 384 58 104 87
Asukite AE Elected 20 May 2026 371 57 118 87
Bobby Cohn AE Elected 20 May 2026 364 56 126 87
Sammi Brie AE Elected 20 May 2026 414 82 50 83
Ca AE Elected 20 May 2026 361 76 109 83
Drm310 AE Elected 20 May 2026 337 72 137 82
Reconrabbit AE Elected 20 May 2026 356 80 110 82

The community grants administrator access to trusted users, so nominees should have been on Wikipedia long enough for people to determine whether they are trustworthy. Administrators are held to high standards of conduct because other editors often turn to them for help and advice, and because they have access to tools that can have a negative impact on users or content if carelessly applied.

Nomination standards

The only formal prerequisite for adminship is having an extended confirmed account on Wikipedia (500 edits and 30 days of experience).[2] However, the community usually looks for candidates with much more experience, and those without are generally unlikely to succeed at gaining adminship. The community looks for a variety of factors in candidates and discussion can be intense. To get an insight of what the community is looking for, you could review some successful and some unsuccessful RfAs, or start an RfA candidate poll.

If you are unsure about nominating yourself or another user for adminship, you may first wish to consult a few editors you respect to get an idea of what the community might think of your request. There is also a list of editors willing to consider nominating you. Editors interested in becoming administrators might explore adoption by a more experienced user to gain experience. They may also add themselves to Category:Wikipedia administrator hopefuls; a list of names and some additional information are automatically maintained at Wikipedia:List of administrator hopefuls. The RfA guide and the miniguide might be helpful, while Advice for RfA candidates will let you evaluate whether or not you are ready to be an admin.

Nominations

To nominate either yourself or another user for adminship, follow these instructions. If you wish to nominate someone else, check with them before making the nomination page. Nominations may only be added by the candidate, or added after the candidate has signed the acceptance of the nomination.

Please do not transclude the RfA page until after the nomination has been accepted by the candidate, and the page, and its questions, has been filled out to the candidate's satisfaction. Be aware that the process will start the moment the RfA is transcluded to this page.

Notice of RfA

Some candidates display the {{RfX-notice}} on their userpages. Also, per community consensus, RfAs are to be advertised on MediaWiki:Watchlist-messages and Template:Centralized discussion. The watchlist notice will only be visible to you if your user interface language is set to (plain) en.

Expressing opinions

All Wikipedians—including those without an account or not logged in ("anons")—are welcome to comment and ask questions in an RfA. Numerated (#) "votes" in the Support, Oppose, and Neutral sections may only be placed by editors with the extended confirmed right.[3] Other comments are welcomed in the general comments section at the bottom of the page, and comments by editors who are not administrators or extended confirmed may be moved to this section if mistakenly placed elsewhere.

If you are relatively new to contributing to Wikipedia, or if you have not yet participated on many RfAs, please consider first reading "Advice for RfA voters".

There is a limit of two questions per editor, with relevant follow-ups permitted. The two-question limit cannot be circumvented by asking questions that require multiple answers (e.g. asking the candidate what they would do in each of five scenarios). The candidate may respond to the comments of others. Certain comments may be discounted if there are suspicions of fraud; these may be the contributions of very new editors, sockpuppets, or meatpuppets. Please explain your opinion by including a short explanation of your reasoning. Your input (positive or negative) will carry more weight if supported by evidence.

To add a comment, click the "Voice your opinion" link for the candidate. Always be respectful towards others in your comments. Constructive criticism will help the candidate make proper adjustments and possibly fare better in a future RfA attempt. Note that bureaucrats have been authorized by the community to clerk at RfA, so they may appropriately deal with comments and !votes which they deem to be inappropriate. You may wish to review arguments to avoid in adminship discussions. Irrelevant questions may be removed or ignored, so please stay on topic.

The RfA process attracts many Wikipedians and some may routinely oppose many or most requests; other editors routinely support many or most requests. Although the community currently endorses the right of every Wikipedian with an account to participate, one-sided approaches to RfA voting have been labeled as "trolling" by some. Before commenting or responding to comments (especially to Oppose comments with uncommon rationales or which feel like baiting) consider whether others are likely to treat it as influential, and whether RfA is an appropriate forum for your point. Try hard not to fan the fire. Remember, the bureaucrats who close discussions have considerable experience and give more weight to constructive comments than unproductive ones.

Discussion, decision, and closing procedures

Most nominations will remain active for a minimum of seven days from the time the nomination is posted on this page, during which users give their opinions, ask questions, and make comments. This discussion process is not a vote (it is sometimes referred to as a !vote, using the computer science negation symbol). At the end of the discussion period, a bureaucrat will review the discussion to see whether there is a consensus for promotion. Consensus at RfA is not determined by surpassing a numerical threshold, but by the strength of rationales presented. In practice, most RfAs above 75% support pass.

In December 2015 the community determined that in general, RfAs that finish between 65 and 75% support are subject to the discretion of bureaucrats (so, therefore, almost all RfAs below 65% will fail). However, a request for adminship is first and foremost a consensus-building process.[4] In calculating an RfA's percentage, only numbered Support and Oppose comments are considered. Neutral comments are ignored for calculating an RfA's percentage, but they (and other relevant information) are considered for determining consensus by the closing bureaucrat.

In nominations where consensus is unclear, detailed explanations behind Support or Oppose comments will have more impact than positions with no explanations or simple comments such as "yep" and "no way".[5] A nomination may be closed as successful only by bureaucrats. In exceptional circumstances, bureaucrats may extend RfAs beyond seven days or restart the nomination to make consensus clearer. They may also close nominations early if success is unlikely and leaving the application open has no likely benefit, and the candidate may withdraw their application at any time for any reason.

If uncontroversial, any user in good standing can close a request that has no chance of passing in accordance with WP:SNOW or WP:NOTNOW. Do not close any requests that you have taken part in, or those that have even a slim chance of passing, unless you are the candidate and you are withdrawing your application. In the case of vandalism, improper formatting, or a declined or withdrawn nomination, non-bureaucrats may also delist a nomination. A list of procedures to close an RfA may be found at WP:Bureaucrats. If your nomination fails, then please wait for a reasonable period of time before renominating yourself or accepting another nomination. Some candidates have tried again and succeeded within three months, but many editors prefer to wait considerably longer before reapplying.

Monitors

In the 2024 RfA review, the community authorized designated administrators and bureaucrats to act as monitors to moderate discussion at RfA. The monitors can either self-select when an RfA starts, or can be chosen ahead of time by the candidate privately. Monitors may not be involved with the candidate, may not nominate the candidate, may not !vote in the RfA, and may not close the RfA, although if the monitor is a bureaucrat they may participate in the RfA's bureaucrat discussion if there is one. In addition to normal moderation tools, monitors may remove !votes from the tally or from the discussion entirely at their discretion when the !vote contains significant policy violations that must be struck or otherwise redacted and provides no rational basis for its position – or when the comment itself is a blockable offense. The text of the !vote can still be struck and/or redacted as normal. Monitors are encouraged to review the RfA regularly. Admins and bureaucrats who are not monitors may still enforce user conduct policies and guidelines at RfA as normal.[6]

Current nominations for adminship

The current time is 22:05:15, 27 June 2026 (UTC)


if nominations have not updated.


TechnoSquirrel69

Voice your opinion on this candidate (talk page) (171/0/1); Scheduled to end 17:15, 30 June 2026 (UTC)

Monitors:

Nomination

TechnoSquirrel69 (talk · contribs) – It is my pleasure to (finally) nominate TechnoSquirrel69 for adminship. TS69 first came to my attention at WP:PERM/AP, where he frequently nominates editors and meticulously examines the editing history of existing nominees. His sound judgement makes decisions much easier for patrolling admins. Other work stemming from their New page patrolling is equally excellent: TS69’s CSD log shows high-quality tagging for instance.

Their content work is also outstanding, and includes an FA that grew out of a WP:Women in Red drive, and further work to combat systemic bias on Wikipedia includes their role as a coordinator of the Developing Countries WikiContest. TS69 communicates kindly but firmly, and would make a great addition to the admin corps. I hope you will join me in supporting him for adminship. In solidarity, —Femke (talk) 🐦 16:51, 23 June 2026 (UTC)

Co-nomination statement

At WCNA 2025, I had the pleasure of meeting TechnoSquirrel69; he was given at least 8 lighthearted but serious offers for nominations during the conference, myself included. After caching the nomination offer over the wintertime, I'm overjoyed to put TechnoSquirrel forward for adminship alongside Femke. Like her, I noted his diligence at requests for autopatrolled, where he was consistently respectful, calibrated quickly to existing standards, and significantly reduced admin workload while simultaneously encouraging and teaching other editors how to write better articles. Beyond what Femke mentioned, he does excellent work at WP:DYK, which my own forays into promoting and checking queues have seen no issues, squirrels away at NPP and WP:AFC, organizes local meetups, and provides high quality XFD participation. TechnoSquirrel is at his core a kind, competent, and community-building editor that would do fantastic with administrator tools. Sennecaster (Chat) 16:57, 23 June 2026 (UTC)

Candidate, please indicate acceptance of the nomination here: I'm honored to have Femke and Sennecaster's nominations — I accept! I have not edited for pay. TechnoSquirrel69 (talk) 17:01, 23 June 2026 (UTC)

Questions for the candidate

Dear candidate, thank you for offering to serve Wikipedia as an administrator. Please answer these questions to provide guidance for participants:

1. Why are you interested in becoming an administrator?
A: Over the years, I've found myself working in many areas adjacent to administrative tasks. My main reason for running is so I can better contribute in these areas with extra buttons: I would be able to close XfDs as delete, deal with patently inappropriate pages I encounter at new pages patrol, make urgent changes on cascade-protected pages for Did you know, or action requests for permissions. If given a mop, I will not be wanting for places to use it. TS
2. What are your best contributions to Wikipedia, and why?
A: Writing articles was my first love on this website, and I consider myself to be, first and foremost, a content contributor. I'm very proud of my work on my largest projects: Castle in the Sky, Princess Mononoke, and The Snow Queen (Kernaghan novel). The latter's FAC taught me a lot about navigating the high expectations for featured articles, including deeper understanding of copyright policies and prose standards. On the back end, I helped establish and coordinate the Developing Countries WikiContest, a project to fight systemic bias in the encyclopedia; we're now coming up on our third annual installment! I've also found scouting out possible nominees for Editor of the Week to be highly rewarding. TS
3. Have you been in any conflicts over editing in the past or have other users caused you stress? How have you dealt with it and how will you deal with it in the future?
A: Some disputes are unavoidable on Wikipedia, and when they happen I strive to see the best in other editors, even when faced with less-than-ideal behavior, in the belief that we have the common goal of improving the encyclopedia. One incident in which I commented on a request for autopatrolled escalated into a disagreement with the requestor. Though it got under my skin, I made sure to step away until I could respond with my better judgement on my side. For a more recent example, an ANI thread was opened relating to a mass message request I handled. I accepted responsibility for my part in the error, politely but firmly argued against the proposed administrative actions I felt were unnecessary, and deferred to my more experienced colleagues when they joined the conversation. TS

You may ask optional questions below. There is a limit of two questions per editor. Multi-part questions are disallowed, but you are allowed to ask follow-up questions related to previous questions. Make sure to use level-five section headers, not boldface.

Optional question from TonyBallioni
4. Would you mind addressing your block log? Particularly the recent account compromise, but I think the older block would also be useful to get some context behind.
A: Thanks for your question, TonyBallioni! From what I was told by volunteer functionaries and WMF Trust and Safety (which was, understandably, limited by their non-disclosure agreements), an attacker exploited a security vulnerability with several accounts at once, including my own. This vulnerability was not in my control; I had otherwise taken every step to secure my account, including a strong password, a recovery email, and two-factor authentication. (Barkeep's comment below is correct. Thanks, Barkeep!) The attacker never succeeded at accessing my account, but it was nevertheless blocked and globally locked for safety until the vulnerability was patched.
My previous block, from five years ago, was for cause. As a new editor, I had yet to develop an understanding of Wikipedia's copyright policies, and uploaded several copyright-infringing illustrations for the drafts I was working on. After I understood where I'd gone wrong, I apologized and successfully appealed the block. The incident left me with a heightened awareness of Wikipedia's stance on copyright compliance, and I've since grown much more familiar with the area as a new pages patroller. TS
Optional question from Ritchie333
5. I'm not bothered about the recent block; that can happen to active administrators too, but I want to discuss more about the older one. I don't recall seeing a RfA candidate (or at least one with a likelihood of passing) with an indefinite good faith block for violating policy, even if it was five years ago, particularly when the blocking administrator said "You were blocked for repeatedly violating (emphasis mine) the non-free content policy by using non-free media ". Can you explain briefly, were you warned about non-free content policy before being blocked, and what have you understood about this since then, and do you have examples illustrating this?
A: Hey Ritchie333! I'm happy to elaborate. Some of the details escape me as this was some time ago, but part of the learning curve as a new editor was becoming acquainted with the edit history page, something I didn't fully grasp at that point. The block was over my editing at Mirror (Porter Robinson song) (then in draftspace). Without realizing a bot was automatically removing it, due to my ignorance of the history page, I repeatedly restored the song's cover art, thinking there had been some kind of error. As I mentioned, I took the time to understand the policies involved and appealed the block.
I've since become familiar with navigating copyright concerns as a new pages patroller. I always use Earwig's copyvio detector to catch obvious cases of plagiarism, and I sometimes go a step further and investigate for close paraphrasing (example) if necessary. If I discover a violation, I remove the offending text and request revision deletion under RD1, or tag it for full deletion under CSD G12. I'm also comfortable with assessing copyright with images. In addition to the file-related tagging in my enwiki CSD log, my log on Commons may also be relevant. TS
Optional question from Daniel Case
6. What led you to seek adminship via RfA rather than election?
A: Thanks for your question, Daniel! I don't have any special reasons beyond the themes you've likely heard in discussions about AELECT already: I prefer that the (!)voting is public, I feel the community has more time to make an informed decision, I liked having control over the scheduling of my run, etc. I do believe AELECT has been a resounding success — the scores of talented editors who now have the tools are testament to it — it just wasn't for me! TS
Optional question from NYC Guru
7. Under what conditions would you block a new user indefinitely?
A: Thanks for your question, NYC Guru. As I mentioned above, I try to assume good faith for as long as possible, even with disruptive editors. Regardless of the user's experience, most disruption can be handled using our system of escalating warnings. If the editor continues their poor behavior after being sufficiently warned, they can be seen to the door. However, in cases of severe abuse, an indefinite block may be warranted immediately to prevent further damage. This would have to rise above the level of petty vandalism; threats of physical harm or legal action are examples. TS
Optional question from Least Action
8. What made you interested in WP:PERM/AP in the first place?
A: Hey Least Action, thank you for your question! I noticed in my first few months as a new pages patroller that I consistently ran into well-written articles from the same creators, particularly if I was going down the line in a single topic area. Giving these editors autopatrolled would clearly have a multiplicative effect in reducing the ever-mounting backlog at NPP. I had heard from administrators working that queue that nominations and second opinions from active NPP-ers were often useful in their decision-making, so decided to pitch in where I could. I found that I enjoyed this alternative patrolling workflow of checking a single user's body of work and, as a bonus, more than once found worthy Editor of the Week recipients in the process! TS
Optional question from asilvering
9. If you (as a Wikipedia editor) were an animal, what animal would you be? (Sciuridae excepted, that's cheating.)
A: Contrary to what the username would suggest, I don't actually identify much with squirrels as a person, though it's nevertheless a pleasure to be sharing the RfA stage with another Sciuridae-themed candidate! As an editor, however, I can't deny a significant overlap with the WikiSquirrel style as I frequently flit from topic to topic with my interests. That's cheating, though, so I also feel quite editorially dog-like (though not WikiDog-like!). Every once in a while, I pick a topic and remain loyal to it — for example, I've been stewarding Castle in the Sky since I became an active editor, and hope to take it to FAC soon! Thanks for your question, asilvering. :) TS
Optional question from InfernoHues
10. If you could go back in time and give yourself advice as a beginning editor, what would it be?
A:


Discussion


Please keep discussion constructive and civil. If you are unfamiliar with the nominee, please thoroughly review his contributions before commenting.

Numerated (#) "votes" in the "Support", "Oppose", and "Neutral" sections may only be placed by editors with an extended confirmed account. All other comments are welcome in the "general comments" section.

Support
  1. First! Pennecaster (Chat with Senne) 17:17, 23 June 2026 (UTC)
  2. Been keeping an eye on this one for a while, support. ~delta {talkcont🇰🇷🎢} 17:20, 23 June 2026 (UTC)
  3. Yes! --DoubleGrazing (talk) 17:23, 23 June 2026 (UTC)
  4. Sure. I've had plenty of positive experiences with this user. Gommeh (talk! sign!) 17:27, 23 June 2026 (UTC)
  5. Obviously GreenLipstickLesbian💌🧸 17:33, 23 June 2026 (UTC)
  6. As nom, In solidarity, —Femke (talk) 🐦 17:34, 23 June 2026 (UTC)
  7. Support haven't had a bad experience when interacting with them, no concerns from me. LuniZunie(talk) 17:39, 23 June 2026 (UTC)
  8. Support I especially enjoyed reading Capitol Hill mystery soda machine. Rolluik (talk) 17:44, 23 June 2026 (UTC)
  9. Support We seem to have a habit of doing RfAs in batches as of recent. fanfanboy (blocktalk) 17:57, 23 June 2026 (UTC)
  10. Support, nothing but positive impressions from his prolific and constructive work at DYK. Dclemens1971 (talk) 17:57, 23 June 2026 (UTC)
  11. Unhesitating support. I've worked with TS69 before, and been impressed with their calm and diligence. They've done excellent content work and excellent project-space work, and they are a natural addition to the admin corps. I would have nominated if that had not been thoroughly redundant. Vanamonde93 (talk) 18:08, 23 June 2026 (UTC)
  12. Support. Bgsu98 (Talk) 18:12, 23 June 2026 (UTC)
  13. Support Zzz plant (talk) 18:16, 23 June 2026 (UTC)
  14. Support - I've both met the candidate in person and seen his work on wiki and have no issues with this candidacy. The noms pretty much sum it up. The only significant block (aside from the suspected account compromise, which was thankfully resolved quickly) was from over five years ago, I don't think it is a problem today if the problem hasn't recurred. Epicgenius (talk) 18:19, 23 June 2026 (UTC)
  15. finally!!! I've been hoping TechnoSquirrel would run for a long time – nothing but good things to say about him and his DYK work. he's sharp, diligent, kind, and always willing to hold himself to account – I have full confidence in TS and I'd be delighted to see what someone with his skills could do with a mop. theleekycauldron (talk • she/her) 18:21, 23 June 2026 (UTC)
  16. Elli (talk | contribs) 18:28, 23 June 2026 (UTC)
  17. Support! Chaotic Enby (in solidarity · talk · contribs) 18:31, 23 June 2026 (UTC)
  18. I've been badgering TS69 to run since last year, so glad that they finally have gone for it! -- Sohom (talk) 18:34, 23 June 2026 (UTC)
  19. Long overdue! Extraordinary Writ (talk) 18:38, 23 June 2026 (UTC)
  20. I have had nothing but good experiences of our friend here. ⹃Maltazarian parley ∨ {\displaystyle \lor } {\displaystyle \lor }investigate 18:40, 23 June 2026 (UTC)
  21. This is an editor I have run into several times and I can recall being impressed with their work, Support. Lynch44 18:41, 23 June 2026 (UTC)
  22. Reasonable response to my question. Thanks for being willing to answer it directly even as others had already responded to the main part. TonyBallioni (talk) 18:42, 23 June 2026 (UTC)
  23. Support, extremely overdue. Best, Staraction (talk · contribs) 18:49, 23 June 2026 (UTC)
  24. Support Good answer to block question: TS69 stumbled with first edits, recovered appropriately after the block. — rsjaffe 🗣️ 18:55, 23 June 2026 (UTC)
  25. Support In solidarity, Blue-Sonnet (I'm listening) 19:02, 23 June 2026 (UTC)
  26. Support, naturally. UpTheOctave!  8va? 19:03, 23 June 2026 (UTC)
  27. Support Looks fine. EggRoll97 (talk) 19:05, 23 June 2026 (UTC)
  28. Support. Absolutely! Trusted noms and they do good work. CoconutOctopus talk 19:12, 23 June 2026 (UTC)
  29. Support. Aoba47 (talk) 19:18, 23 June 2026 (UTC)
  30. Kusma (talk) 19:19, 23 June 2026 (UTC)
  31. Flock yes. charlotte 👸♥ 19:23, 23 June 2026 (UTC)
  32. ~~ AirshipJungleman29 (talk) 19:23, 23 June 2026 (UTC)
  33. I've had the pleasure to meet him in person and he's a lovely lad and would make a great admin. CaptainEek Edits Ho Cap'n! 19:25, 23 June 2026 (UTC)
  34. Support! A kind, productive contributor who will do well with the tools. GoldRomean (talk) 19:28, 23 June 2026 (UTC)
  35. Excited to see him finally go for the mop. I anticipate him being a great admin. In solidarity, QuicoleJR (talk) 19:35, 23 June 2026 (UTC)
  36. Support Cicada1010 (talk) 19:51, 23 June 2026 (UTC)
  37. Support Don't see why not. LightlySeared (talk) 20:10, 23 June 2026 (UTC)
  38. Support Rhododendrites talk \\ 20:11, 23 June 2026 (UTC)
  39. Support FaviFake (talk) 20:12, 23 June 2026 (UTC)
  40. Support EaglesFan37 (talk) 20:15, 23 June 2026 (UTC)
  41. Support A nice person that should have already been an administrator. Vacant0 (talk contribs) 20:16, 23 June 2026 (UTC)
  42. Support Rand Freeman talkin solidarity 20:26, 23 June 2026 (UTC)
  43. Excellent candidate. Thank you for running. Toadspike [Talk] 20:47, 23 June 2026 (UTC)
  44. Absolutely! I have always been impressed with TS69’s wide range of talents, from content creation to his work countering systemic bias through the Developing Countries WikiContest. But most importantly, I love how he makes it his mission to spread kindness, whether through his frequent nominations at editor of the week or giving thoughtful barnstars to others.

    For what it's worth, I'll put my name down as another functionary who can confirm the compromised account was not his fault in any way. At all. He did everything right. Best, HouseBlaster (talk • he/they) 20:53, 23 June 2026 (UTC)
  45. Support. Gog the Mild (talk) 20:56, 23 June 2026 (UTC)
  46. Easy support. TS has been a patient and diligent editor whose expertise will be put to great use with mop in hand. ThaesOfereode (talk) 20:57, 23 June 2026 (UTC)
  47. Ingenuity (talk) 21:00, 23 June 2026 (UTC)
  48. Support. Thought he already was an admin! Chocmilk03 (talk) 21:04, 23 June 2026 (UTC)
  49. Support. I have no serious concerns. thunkii (talk) 21:05, 23 June 2026 (UTC)
  50. Support. Wait, he's not an admin? —TWOrantulaTM (enter the web) 21:36, 23 June 2026 (UTC)
  51. Support Mfield (Oi!) 21:50, 23 June 2026 (UTC)
  52. Support. Squirrels are cool, and this user has also done great collaboratory work on the backend side of Wikipedia. — Vigilant Cosmic Penguin 🐧(talk | contribs) 21:53, 23 June 2026 (UTC)
  53. Support Chipmunks, squirrels - any other competent and effective woodland creatures want to put themselves forward today? Girth Summit (blether) 22:42, 23 June 2026 (UTC)
    Reconrabbit unfortunately already elected. ~2026-28744-62 (talk) 12:24, 24 June 2026 (UTC)
  54. Support! In solidarity, nil nz 22:44, 23 June 2026 (UTC)
  55. Support: Thank you for stepping up! YuniToumei (talk) 23:32, 23 June 2026 (UTC)
  56. Support. He is helpful at peer reviews, and I am confident he will do well as an administrator. Z. Patterson (talk) 23:35, 23 June 2026 (UTC)
  57. Support! I had the great pleasure of meeting TechnoSquirrel earlier this year at an editor's meetup and was greatly impressed by the breadth of his wiki knowledge, ready and confident answers to questions, and helpful feedback on others' edits. I am confident he will be an awesome admin! :) silviaASH (inquire within) 23:55, 23 June 2026 (UTC)
  58. Very easy support, and thrilled to do so. I've consistently been impressed with TS's content (I was lucky enough to review both GAs mentioned above) and his admin-adjacent work—and especially his conduct—speaks for itself. I know he will continue to do great work as an admin. Rhain he
    him
    00:30, 24 June 2026 (UTC)
  59. Support. This one's been ready for the mop for going on two years now. In solidarity, asilvering (talk) 00:31, 24 June 2026 (UTC)
  60. Support. Fully qualified candidate. Newyorkbrad (talk) 00:41, 24 June 2026 (UTC)
  61. Ternera (talk) 00:42, 24 June 2026 (UTC)
  62. Support I have no worries. 1brianm7 (talk) 00:49, 24 June 2026 (UTC)
  63. Support toby (t)(rw) 01:00, 24 June 2026 (UTC)
  64. Support Cielquiparle (talk) 01:03, 24 June 2026 (UTC)
  65. Support TarnishedPathtalk 01:06, 24 June 2026 (UTC)
  66. Support, indeed. ~SG5536B 01:12, 24 June 2026 (UTC)
  67. Support - InfernoHues (talk) 01:12, 24 June 2026 (UTC)
  68. Support Opm581 (talk | he/him) 01:18, 24 June 2026 (UTC)
  69. Support ARandomName123 (talk)Ping me! 02:21, 24 June 2026 (UTC)
  70. Support Whonting (talk) 02:29, 24 June 2026 (UTC)
  71. Support Adding my support to a worthy candidate. Hawkeye7 (discuss) 02:57, 24 June 2026 (UTC)
  72. Support based on their advanced usage rights so far, especially as a template editor. Let me expand on something from the nomination statements above. Sennecaster mentioned that "he does excellent work at WP:DYK, which my own forays into promoting and checking queues have seen no issues ...". TS himself says that, as an admin, he could "make urgent changes on cascade-protected pages for Did you know". The context, for those unfamiliar with the Wikipedia:Did you know hooks, is that before they appear on the main page, the hooks are arranged into sets initially built in preparation areas (preps). Any editor can nominate articles, propose hook facts, approve those hooks, or build the prep sets. These sets are then double-checked and promoted to queues by an admin or template editor (this was previously an admin-only task, but that was resulting in burnout). TS built plenty of preps, applied for template editor permissions to promote preps, and then promoted plenty of sets from prep to queue. These queued sets rotate forward on a mostly daily basis until each set rotates into {{Did you know}}, which is transcluded onto the main page, so TS has already edited Main Page content, albeit indirectly. However, the main page templates and the next 48 hours of queued sets are all admin protected. If someone spots an issue at WP:ERRORS, they will usually be commenting on one of these three admin-protected sets. When editors have brought up concerns, TS has responded appropriately,[example] but currently has to rely on other editors to implement changes. This is all positive, but something I think bodes well for admin tool usage is that template editor privileges for DYK sets also technically enable an editor to change any template-protected page, including many heavily transcluded templates (e.g. {{Location map}}). TS technically could have just done this, but instead sought consensus in the same way that any editor would normally have to apply if they did not already have the permission. I think this shows much consideration and respect for other editors. Rjjiii (talk) 03:32, 24 June 2026 (UTC)
  73. SupportPharyngealImplosive7 (talk) 04:12, 24 June 2026 (UTC)
  74. Support. ShadowBallX (talk) 05:03, 24 June 2026 (UTC)
  75. Support – TechnoSquirrel is an exceedingly thoughtful contributor who I am sure will make a great administrator. Being a squirrel is a big plus too. Vermont (🐿️🏳️‍🌈) 05:05, 24 June 2026 (UTC)
  76. ~ Jenson (SilverLocust 💬) 05:58, 24 June 2026 (UTC)
  77. Glad to Support. Volten001 06:01, 24 June 2026 (UTC)
  78. Support. Excellent content contributions. TechnoSquirrel69's efforts to counter systemic bias through the Developing Countries WikiContest are commendable. — Newslinger talk 06:15, 24 June 2026 (UTC)
  79. Support Chlod (say hi!) 06:38, 24 June 2026 (UTC)
  80. Support, the effort TechnoSquirrel69 puts into DYK, carefully checking articles they promote and raising issues they find in a clear manner, shows judgement, content knowledge, and communication. Coordination of DCWC is another volunteer position I have seen their work in for a few years now. A mop would be likely be well handled. CMD (talk) 06:43, 24 June 2026 (UTC)
  81. Support – not a username I recognised, but I'm impressed by the noms and answers to questions. Graham87 (talk) 07:49, 24 June 2026 (UTC)
  82. Why not? Best, Reading Beans, Duke of Rivia 07:52, 24 June 2026 (UTC)
  83. Support. A very talented editor, and has run a tight ship at DCWC! Generalissima (talk) (it/she) 08:17, 24 June 2026 (UTC)
  84. Support Huge Support, have an encounter with him a couple of times. Destinyokhiria (talk / cont) 09:14, 24 June 2026 (UTC)
  85. Support Clear net positive. -Kj cheetham (talk) 09:32, 24 June 2026 (UTC)
  86. Support. Does good, careful work. He's made some mistakes, but has learned from them (and if you never make a mistake, you're not doing anything worth doing.) I think he will make a very good and thoughtful admin. Entirely off topic, I find it quite amusing that we currently have both a squirrel and a chipmunk at RfA together. Seraphimblade Talk to me 09:44, 24 June 2026 (UTC)
  87. Trusted, competent. ~ ToBeFree (talk) 10:11, 24 June 2026 (UTC)
  88. Support absolute support, nothing else. 🍗TheNuggeteer🍗 (My "blotter") 10:27, 24 June 2026 (UTC)
  89. Support, obviously. RoySmith (talk) 11:06, 24 June 2026 (UTC)
  90. Support, no issues here. Let'srun (talk) 11:16, 24 June 2026 (UTC)
  91. Support, glad to see this name nominated. Good luck with the mop, TS. — ♠ Ixtal ( T / C ) Non nobis solum ♠ 12:05, 24 June 2026 (UTC)
  92. SupportIn solidarity, Penn65 talk 12:09, 24 June 2026 (UTC)
  93. Support Hey man im josh (talk) 12:17, 24 June 2026 (UTC)
  94. Support Kowal2701 (talk, contribs) 12:28, 24 June 2026 (UTC)
  95. Support. My past experiences seeing this candidate around have involved them taking on complicated tasks and doing them skillfully. Would be a good admin. ModernDayTrilobite (talkcontribs) 13:31, 24 June 2026 (UTC)
  96. Support: See only indications that they would be a fine admin. Not sure I've interacted at all with them, but I'll take the glowing reviews of their work and conduct as evidence the project will benefit from them having the mop. Best of luck, ~ Pbritti (talk) 14:00, 24 June 2026 (UTC)
  97. sapphaline (talk) 14:07, 24 June 2026 (UTC)
  98. Support Has clue, is polite. Doubleplus good. --Goldsztajn (talk) 14:14, 24 June 2026 (UTC)
  99. Support Synpath 14:16, 24 June 2026 (UTC)
  100. Support Looks like a dedicated editor to me mike_gigs talkcontribs 14:17, 24 June 2026 (UTC)
  101. Support. A constant and active member of Editor of the Week. Always takes the time to acknowledge others. 100% community builder.Buster Seven Talk (UTC) 14:20, 24 June 2026 (UTC)
  102. Support: I've seen him around, didn't even realize he wasn't an admin.  Bait30  Talk 2 me pls? 14:28, 24 June 2026 (UTC)
  103. Support. S5A-0043🚎(Talk) 14:42, 24 June 2026 (UTC)
  104. Support thank you for volunteering ~ In solidarity 🦝 Shushugah (talk) 15:04, 24 June 2026 (UTC)
  105. Support. sure, per noms TheresNoTime (talk • they/them) 15:30, 24 June 2026 (UTC)
  106. Another enthusiastic support for another clueful and experienced candidate. Very pleased to see two RfAs running simulataneously for two great editors who would make excellent admins. HJ Mitchell | Penny for your thoughts? 16:13, 24 June 2026 (UTC)
  107. Supportzmbro (talk) (cont) 16:14, 24 June 2026 (UTC)
  108. Support. MSincccc (talk) 16:14, 24 June 2026 (UTC)
  109. Support! I especially appreciate TechnoSquirrel's diligence with DYK. — Chao Garden 🌱 ~ say hello 16:56, 24 June 2026 (UTC)
  110. Support Fathoms Below (talk) 17:29, 24 June 2026 (UTC)
  111. Support :) DaniloDaysOfOurLives (talk) 18:00, 24 June 2026 (UTC)
  112. Support --Minoa (talk) 19:48, 24 June 2026 (UTC)
  113. Support - no concerns. GiantSnowman 20:15, 24 June 2026 (UTC)
  114. Support Yes!!! --📎 JackFromWisconsin (talk | contribs) 20:53, 24 June 2026 (UTC)
  115. Support, looks good. I am bad at usernames (talk · contribs) 21:22, 24 June 2026 (UTC)
  116. Support. I like the way the candidate has handled questions during the RfA. Good combination of content and technical experience. --Tryptofish (talk) 22:23, 24 June 2026 (UTC)
  117. Nice --Guerillero Parlez Moi 22:38, 24 June 2026 (UTC)
  118. Support Justiyaya 22:58, 24 June 2026 (UTC)
  119. Support We met at WCNA 2025; he will be an asset to the mop corps. Complex/Rational 23:10, 24 June 2026 (UTC)
  120. Support no cause to deny a rfa. – robertsky (talk) 23:26, 24 June 2026 (UTC)
  121. Support Riley1012 (talk) 00:10, 25 June 2026 (UTC)
  122. Support - trustworthy editor. PhilKnight (talk) 03:59, 25 June 2026 (UTC)
  123. Support I like folk who learn from their mistakes. Everything else tells me that he'll make good use of the tools. -MPGuy2824 (talk) 05:06, 25 June 2026 (UTC)
  124. Support Will be fine. Risker (talk) 05:14, 25 June 2026 (UTC)
  125. Support Seems to be a good addition. Jordano53 05:51, 25 June 2026 (UTC)
  126. Support Yup KylieTastic (talk) 10:09, 25 June 2026 (UTC)
  127. Support, no concerns. ScottishFinnishRadish (talk) 11:27, 25 June 2026 (UTC)
  128. Support - Great answers to questions, no other concerns. Ritchie333 (talk) (cont) 12:27, 25 June 2026 (UTC)
  129. Support I am happy to help uplift those in my clade (and I always like seeing your name at PERM!) -- Reconrabbit (talk) 12:35, 25 June 2026 (UTC)
  130. Support – no words needed, a great user and seemingly great person. CoryGlee 12:58, 25 June 2026 (UTC)
  131. I support this candidate. Shoutout to User:Ritchie333--thanks for weighing in here old friend. Drmies (talk) 13:01, 25 June 2026 (UTC)
  132. Support with excitement! Bobby Cohn 🍁 (talk) 14:23, 25 June 2026 (UTC)
  133. Support will be a net-positive to the project. « Gonzo fan2007 (talk) @ 15:09, 25 June 2026 (UTC)
  134. Support ScalarFactor (talk) 17:01, 25 June 2026 (UTC)
  135. Support, experienced user, trust without issue. Star Mississippi 17:40, 25 June 2026 (UTC)
  136. Support: only good things to say from various interactions around this place. UndercoverClassicist T·C 18:06, 25 June 2026 (UTC)
  137. Support - good candidate. -- Ajraddatz (talk) 18:33, 25 June 2026 (UTC)
  138. might as well support DS (talk) 18:55, 25 June 2026 (UTC)
  139. Support Tenshi! (Talk page) 19:24, 25 June 2026 (UTC)
  140. Support — Clueful, kind, experienced. Choucas 🐦 20:10, 25 June 2026 (UTC)
  141. Support Giulio 22:17, 25 June 2026 (UTC)
  142. Support  Yue🌙 (talk) 23:56, 25 June 2026 (UTC)
  143. Support. Thanks for being willing to wield the mop! Loopy30 (talk) 00:19, 26 June 2026 (UTC)
  144. Support Bringingthewood (talk) 02:13, 26 June 2026 (UTC)
  145. Support Looks good, no concerns. - RevelationDirect (talk) 02:15, 26 June 2026 (UTC)
  146. Support ULPS (talkcontribs) 05:26, 26 June 2026 (UTC)
  147. Support. Competent hardworking editor, some great content work, I've seen them around at DYK and other places, and will be a great addition to the admin corps. Cheers   Amakuru (talk) 07:18, 26 June 2026 (UTC)
  148. Support good editor I've had great experiences with, very good candidate for adminship jolielover♥talk 07:30, 26 June 2026 (UTC)
  149. Support after a quick look. -- Least Action (talk) 14:54, 26 June 2026 (UTC)
  150. Support Good candidate,— Diannaa 🍁 (talk) 15:30, 26 June 2026 (UTC)
  151. Support, precious --Gerda Arendt (talk) 16:04, 26 June 2026 (UTC)
  152. Support. MCE89 (talk) 16:57, 26 June 2026 (UTC)
  153. Support - I encouraged Techno to run for admin last year and was very glad to see that they finally did so! Nothing but positive things to say here :). ThadeusOfNazereth(he/him)Talk to Me! 17:59, 26 June 2026 (UTC)
  154. Support Divinations (talk) 18:35, 26 June 2026 (UTC)
  155. Support without any concerns. Cordless Larry (talk) 19:54, 26 June 2026 (UTC)
  156. Support I totally get the explanation for the non-free content in a draft article, not a big deal.Pawnkingthree (talk) 20:45, 26 June 2026 (UTC)
  157. Support I know this user from DYK. Strong candidate; thank for standing. Will make a fine admin. Schwede66 21:46, 26 June 2026 (UTC)
  158. SupportKurtis (talk) 21:47, 26 June 2026 (UTC)
  159. Support per answers to questions and experience. --NYC Guru (talk) 23:17, 26 June 2026 (UTC)
  160. Support. Beta Beta Beta - talk 02:46, 27 June 2026 (UTC)
  161. Support Overdue. The Knowledge Pirate (talk) 05:03, 27 June 2026 (UTC)
  162. Support with lots of work on DYK promoting hooks! JuniperChill (talk) 08:19, 27 June 2026 (UTC)
  163. SupportCool – DreamRimmer 11:02, 27 June 2026 (UTC)
  164. Support with no concerns. Great candidate. Wozal (talk) 11:31, 27 June 2026 (UTC)
  165. Support. I trust you. --Rosiestep (talk) 13:12, 27 June 2026 (UTC)
  166. Support - Has the right temperament, is knowledgeable, and trustworthy. Would make a great admin. Netherzone (talk) 13:54, 27 June 2026 (UTC)
  167. Support Think their really nice as a user. Would support them being an admin (even though I thought they were already) Theeverywhereperson talk here In solidarity! 14:53, 27 June 2026 (UTC)
  168. Support Very happy to endorse. Thank you for taking the mop. --Crystallizedcarbon (talk) 14:56, 27 June 2026 (UTC)
  169. Support Best wishes Josey Wales Parley 15:14, 27 June 2026 (UTC)
  170. Support Very qualified candidate who answered all their questions well and I trust the noms. I am also not convinced by the argument put fourth by the neutral voter. GothicGolem29 (Talk) 17:17, 27 June 2026 (UTC)
  171. Support Wishing you the best from North Carolina! Johnson524 18:03, 27 June 2026 (UTC)
Oppose


    Neutral
    1. Has a rigid interpretation of guidelines. See Wikipedia talk:Did you know#Jacob Huesman. TechnoSquirrel69 thinks "In 2017, [Huesman] competed with undrafted rookie Shane Smith for the Giants' fullback position" is a controversial statement for a BLP. ~WikiOriginal-9~ (talk) 16:37, 24 June 2026 (UTC)
      TechnoSquirrel pulled that DYK because WP:NYPOST was being used as a source for sports-related BLP info, which seems like a pretty reasonable position, considering that the Post is marked as "generally unreliable for factual reporting". — Chao Garden 🌱 ~ say hello 17:04, 24 June 2026 (UTC)
      You knowingly cited at least two NYP articles in a BLP. I'm assuming you knew that the NYP is considered GUNREL, and I think you probably knew editors would object to its use. Instead of changing the citation and asking for the article to be returned to the queue, which is what a reasonable person would do, you've chosen to be petty and address this at RfA. voorts (talk/contributions) 15:03, 25 June 2026 (UTC)
      TechnoSquirrel69 ultimately agreed that the Post's sports coverage was reliable.Bagumba (talk) 15:33, 25 June 2026 (UTC)
      Well, then this is even more of a non-issue. voorts (talk/contributions) 16:03, 25 June 2026 (UTC)
      It was not resolved until after this issue was mentioned here. —Bagumba (talk) 16:06, 25 June 2026 (UTC)
      Storm in a teacup, this. ~~ AirshipJungleman29 (talk) 22:52, 25 June 2026 (UTC)
      There's no other citation to change it to. ~WikiOriginal-9~ (talk) 19:44, 25 June 2026 (UTC)


    General comments
    • @TonyBallioni: while the block was appropriate at the time under policy, there was nothing TechnoSquirrel69 could have done to avoid the situation. This is not at all similar to previous situations where a compromise happened due to things like reusing passwords. I don't want to reveal something that I know by virtue of being a checkuser and which is covered by the ANPDP, so if there's more public information on that situation I hope Techno or someone else will post it here. Best, Barkeep49 (talk) 17:53, 23 June 2026 (UTC)
      • Thanks. I gathered that from the history in the diffs, so I’m not overly concerned. I just generally prefer people to be proactive when discussing their block log so felt it worth raising as a question. TonyBallioni (talk) 18:05, 23 June 2026 (UTC)
      • As the blocking admin, I'd just vouch for what Barkeep49 said. This was a very unusual situation which I can't really go into. In the interests of transparency, the block was related to some global stuff. There's also some talk page chat. -- zzuuzz (talk) 18:24, 23 June 2026 (UTC)

    Chipmunkdavis

    Voice your opinion on this candidate (talk page) (183/0/0); Scheduled to end 10:32, 30 June 2026 (UTC)

    Monitors:

    Nomination

    Chipmunkdavis (talk · contribs) – It is a rare thing for me to introduce a candidate for adminship who has been editing longer than I have, but that is my happy task today. Chipmunkdavis, or CMD, is a veteran of Wikipedia. He has accumulated more than 77,000 edits over his 16 years on the project, concentrating on creating and improving content. His 12 Good Articles include heavyweight topics like the Politics of the Philippines. He has also been a voice of reason and calm in discussions of some fraught sociopolitical topics, which is where I first noticed him (some examples: , , , , , ). CMD is well-placed to chip in with the admin toolset in content-adjacent areas, like DYK and new page review, and in dispute resolution. Their experience will make them a great asset to the admin corps, and I hope you join me in supporting them. Vanamonde93 (talk) 05:24, 23 June 2026 (UTC)

    Co-nomination statement 1

    It's my pleasure to co-nominate Chipmunkdavis for adminship. In addition to the GA highlighted by Vanamonde93, CMD's other GAs include big topics like Malaysia, Timor-Leste and Papua New Guinea; they were twice a prize winner twice in The Core Contest. Their article creation spans a large diversity of topics, from the Asphendou Cave petroglyphs to the Noken system, which has resulted in an impressive 72 DYK nominations. This, together with experience building DYK prep sets, gives me confidence they will be able to quickly pick up further administrative tasks at DYK.

    We've crossed paths quite a few times in climate-change related articles, and I have always been impressed with their calm and concise communication style, including when discussions run hot. I believe they would be a strong and steady addition to the administrator team, and I commend them to the community for consideration. In solidarity, —Femke (talk) 🐦 06:21, 23 June 2026 (UTC)

    Co-nomination statement 2

    Chipmunkdavis is excellent at staying cool in heated discussions and focusing on the evidence. This can be seen in his work on some of our most important articles, highlighted by my colleagues above, but also in his work at AfD. On many occasions, CMD's thorough and nuanced overview of the situation determines the outcome of a discussion (1, 2, 3). At Isaac Newton's apple tree, the closer mentioned CMD and another editor by name for providing a decisive argument. At Mount Baya, CMD identified likely citogenesis, which significantly improved on the nomination statement and resulted in the article being redirected. CMD's close analysis of sources and dedication to verifiability can be seen plenty of other discussions (4, 5, 6, 7). This is what we need in our admins: the patience to examine potential issues in detail and the ability to recognize the best outcome for the encyclopedia. Toadspike [Talk] 07:40, 23 June 2026 (UTC)

    Candidate, please indicate acceptance of the nomination here: I accept this nomination, and am grateful to my nominators. I have never edited for pay, although I have received travel grants from the WMF to attend events. I have no other active or past accounts.

    Questions for the candidate

    Dear candidate, thank you for offering to serve Wikipedia as an administrator. Please answer these questions to provide guidance for participants:

    1. Why are you interested in becoming an administrator?
    A: I have become increasingly aware that whenever I add to an administrative backlog (such as AIV, RfPP, CSD), I am passing work onto others. I would like to reduce that burden slightly. I do not expect to be immediately rushing into any particular area, even those I am already familiar with. However, I hope to contribute further as I become more familiar with the tools, such as at the aforementioned backlogs, as well as DYK, and perhaps SPI and CCI.
    2. What are your best contributions to Wikipedia, and why?
    A: My answer to this probably changes as often as my contributions. Recently, I was able to develop some articles about Papua New Guinea to mark the country’s 50th anniversary of independence, submitting them to a few areas of the main page. I had a six-article DYK in October, including a mix of new articles and x5 expansions, which I was quite happy with finishing within the DYK time limit. Going further back, I have managed to participate in a couple of WP:The Core Contests. On the backend side, I try to spend time helping out with the GAN and DYK processes, including helping manage reviews, and at one point clearing up all the duplications on the GA lists.
    3. Have you been in any conflicts over editing in the past or have other users caused you stress? How have you dealt with it and how will you deal with it in the future?
    A: I am often conflict-averse, but have been involved in various disagreements and discussions since I began editing. My initial exposure to Wikipedia dispute resolution was a huge discussion about how to list sovereign states, which involved many editors and went through multiple rounds of discussion. However, it remained broadly civil and produced a stable consensus that has held for over a decade since. I have taken principles learned then to heart, and have continued to learn, especially following lapses. Key lessons I took on board include that editing per consensus means willingness to accept decisions you are not 100% aligned with, that sometimes there are big questions which simply don't have a 'right' answer, and that the community manages to work things out in the end.

    You may ask optional questions below. There is a limit of two questions per editor. Multi-part questions are disallowed, but you are allowed to ask follow-up questions related to previous questions. Make sure to use level-five section headers, not boldface.

    Optional question from EggRoll97
    4. A user has requested that a page be unprotected. The page has been semi-protected for the last 5 years, was originally indefinitely protected, and the original protecting admin is no longer engaged in editing Wikipedia. No CTOPS concerns apply to the page. How do you proceed if you were to determine what to do with this page?
    A: In general, page protection is not an ideal state due to limiting the number of potential edits. Examining such a request would require checking the history leading up to the protection, the level of disruption that may have occurred since, and the reason for the request. Assuming no active admins were involved and there had been little disruption over the five years, a WP:TRYUNPROT would seem a reasonable request, and I would keep an eye on the results. CMD (talk) 15:04, 23 June 2026 (UTC)
    Optional question from Andrew D.
    5. I've noticed your account name before and always found it mildly puzzling because it sounds like it means something but I couldn't place it. Please explain its origin or meaning.
    A: Disappointingly, there's no particular origin or meaning. It's a random name chosen only to be a random name. CMD (talk) 05:12, 24 June 2026 (UTC)
    Optional questions from In solidarity Wikipedian12512 (Talking is fine | contribs)
    6. An editor (for this purpose, let’s say any LTA that socks) suddenly apparently stops socking. A while later (let’s say a year), they reach out to you with a request to forward an apology to the community, which seems heartfelt. They say they will wait more time, at your discretion, as to when to request to be unblocked, or, if you say so, will stop trying to edit entirely. What do you do?
    A. As a general best practice, I would advise any blocked editor to post any messages to the community on their user talkpage. Ideally, if socking is involved, this would be on their original account. The timing for an editor to request an unblock and whether someone edits at all are not not under the control of a particular admin, but I would make sure the blocked editor is aware of the WP:STANDARDOFFER. CMD (talk) 09:28, 24 June 2026 (UTC)
    7. An admin suddenly blocks you. You have little idea what it was for, and the reason given is that “You have repeatedly made blocks without checking user contributions”. Over the past week, the behaviour of the blocking admin seems a bit off sometimes, and the editing times are shifted. What do you do?
    A. Slightly shifted editing times and slightly off behaviour are indicators of a potential issue, and that would be an unusual (and ineffective) block rationale. It is likely that such actions would be noticed by other (unblocked) admins who would be more able to raise the issue with the community, but if not, this sounds like a situation that may require contacting Arbcom/CUs, either from my user talkpage or via email. If the blocking account is carrying out other immediate disruption, a preventative block may be useful until details become clearer. CMD (talk) 09:28, 24 June 2026 (UTC)
    Optional question from Diannaa
    8. I would love to know which of your article improvements won prizes in the Core Contest.
    A: My successful entries in that respect were joint third place for improving Dili in 2021, and joint second place for improving Timor-Leste in 2022. After a bit more subsequent work I was able to get both to GA. CMD (talk) 04:21, 25 June 2026 (UTC)
    Optional question from Daniel Case
    8. A user requests protection for Quilting in Israel, an article the history shows they created several days ago and have been the only editor of so far. They include "Arbitration enforcement" in the request, meaning that they want the Palestine-Israel contentious-topics provisions — indefinite extended-confirmed protection, 1RR, and ECR in talk page discussions — applied. What's your response and why?
    A: WP:ARBECR allows for a topic area to be placed under preventative protection (outside of talk pages). My understanding of the WP:PIA ARBCOM remedies is that pages related to the Arab Israeli conflict can be ECR protected under such measures. Not every article relating to Israel falls under the Contentious Topic scope, so the content of the hypothetical quilting article is important. Pre-emptive protection remedy only applies to articles "strictly within" the topic area, a very tight consideration. As a general note, such protection is intended to prevent disruption, rather than hindering the normal collaborative editing process. CMD (talk) 03:48, 26 June 2026 (UTC)
    Optional questions from NYC Guru
    9. Under what conditions would you block a new user indefinitely?
    A: It would be uncommon to block a new user indefinitely. This would mean a situation where welcomes and warnings, and later other more limited restrictions, have failed or are inapplicable. An account that has purely harassed others or used extreme invective, showing no hint of good faith or positive contributions, may require such a preventative restriction. Besides that, WP:NLT is a bright-line issue. CMD (talk) 04:17, 26 June 2026 (UTC)
    Optional question from Least Action
    10. How much do you give weight to content creation while evaluating a user's editing experience?
    A: There are different tasks that need doing on Wikipedia, and different people do them at different times. Content creation is often a very helpful way to gain and demonstrate experience, but its weight will vary based on the situation and the sort of experience being looked for. CMD (talk) 04:20, 26 June 2026 (UTC)
    Optional question from Robertsky
    11. You have received information in confidence that an editor have been canvassing here and also come to know that they have a track record of doing so elsewhere in the movement. What would you do as an admin?
    A: This may vary a lot depending on the specifics. Being accountable as an administrator requires being able to explain your actions, and relying on confidential information may make this difficult. I would be unlikely to take individual action without consultation with other admins or prior understanding of the situation. There may be some circumstances where evidence should be passed on to WP:COIVRT or ARBCOM. CMD (talk) 08:13, 26 June 2026 (UTC)
    Optional question from asilvering
    12. If you (as a Wikipedia editor) were an animal, what animal would you be? (Sciuridae excepted, that's cheating.)
    A: Somewhat of an unbearable exception. There's no need to pigeonhole editors, so strictly categorise them, or lionise one over the otter. Have a hartebeest. CMD (talk) 08:22, 26 June 2026 (UTC)

    Discussion


    Please keep discussion constructive and civil. If you are unfamiliar with the nominee, please thoroughly review their contributions before commenting.

    Numerated (#) "votes" in the "Support", "Oppose", and "Neutral" sections may only be placed by editors with an extended confirmed account. All other comments are welcome in the "general comments" section.

    Support
    1. Of course. Toadspike [Talk] 10:34, 23 June 2026 (UTC)
    2. Been waiting for this one. See also: the ‘kind of already thought they were an admin’ test. Eddie891 Talk Work 10:39, 23 June 2026 (UTC)
    3. Support Hey man im josh (talk) 11:07, 23 June 2026 (UTC)
    4. Support Vacant0 (talk contribs) 11:21, 23 June 2026 (UTC)
    5. Support. Always attentive to details in high- and low-visibility areas. -- Reconrabbit (talk) 11:28, 23 June 2026 (UTC)
    6. Support, I trust all 3 nominators immensely and everything looks great here. CoconutOctopus talk 11:44, 23 June 2026 (UTC)
    7. Support more please. Regards, --Goldsztajn (talk) 11:51, 23 June 2026 (UTC)
    8. Support If there is space for more co-noms, I would have gladly joined in. – robertsky (talk) 11:54, 23 June 2026 (UTC)
    9. Support: I've always been impressed by their demeanor before. :) Pennecaster (Chat with Senne) 11:56, 23 June 2026 (UTC)
    10. Support - per seeing their work and demeanor over a long period of time. Excellent candidate. Highly trusted nominators on top of that. 78.26 (spin me / revolutions) 12:02, 23 June 2026 (UTC)
    11. Support, per nominators and own experiences. I’m surprised CMD isn’t an admin given their tenure (I would love to further expand but I currently have very limited time). Icepinner (Come to Hakurei Shrine!) 12:29, 23 June 2026 (UTC)
    12. Support, not sure we have crossed paths but strong noms and running through my normal checks looks like a good candidate. KylieTastic (talk) 12:30, 23 June 2026 (UTC)
    13. Support, in addition to doing well when I've seen Chipmunkdavis aroundif you can get nominations from the three I see here, you're most certainly doing something right. Seraphimblade Talk to me 12:33, 23 June 2026 (UTC)
    14. Support - no doubt that they will be an excellent addition to the admin corps. Cheers, SunloungerFrog (talk) 13:01, 23 June 2026 (UTC)
    15. Support. Wait, you're telling me CMD is not an admin yet? OhanaUnitedTalk page 13:27, 23 June 2026 (UTC)
    16. Support - Promising candidate. Good responses to the questions to boot mike_gigs talkcontribs 13:29, 23 June 2026 (UTC)
    17. Support Zzz plant (talk) 13:32, 23 June 2026 (UTC)
    18. Support. S5A-0043🚎(Talk) 13:44, 23 June 2026 (UTC)
    19. Support, precious --Gerda Arendt (talk) 14:04, 23 June 2026 (UTC)
    20. Support. Lynch44 14:05, 23 June 2026 (UTC)
    21. Support - easy one. Rhododendrites talk \\ 14:16, 23 June 2026 (UTC)
    22. Support - Long time coming. CMD has done a lot of great work to keep the community in line and written many articles, the latter which is a great plus. Have fun with the mop, CMD. Seloloving (talk) 14:35, 23 June 2026 (UTC)
    23. Yes please. • a frantic turtle 🐢 solidarity 14:38, 23 June 2026 (UTC)
    24. Support slam dunk. — rsjaffe 🗣️ 14:43, 23 June 2026 (UTC)
    25. I checked a random sample of this candidate's contributions, and found nothing of concern.—S Marshall T/C 14:45, 23 June 2026 (UTC)
    26. SupportPharyngealImplosive7 (talk) 14:52, 23 June 2026 (UTC)
    27. Support — Strong nomination, trust nominators on candidate. — ♠ Ixtal ( T / C ) Non nobis solum ♠ 14:55, 23 June 2026 (UTC)
    28. Support. A user I immediately recognize as knowledgeable and coolheaded, CMD would be a great addition to the admin corps. ModernDayTrilobite (talkcontribs) 14:56, 23 June 2026 (UTC)
    29. Support Intothatdarkness 14:56, 23 June 2026 (UTC)
    30. Support! In my interactions with him, I've known CMD to be nothing but a patient, knowledgeable, and competent editor. TechnoSquirrel69 (talk) 15:10, 23 June 2026 (UTC)
    31. Support Another member of the "I thought you were already" club. RoySmith (talk) 15:13, 23 June 2026 (UTC)
    32. Support -- LCU ActivelyDisinterested «@» °∆t° 15:14, 23 June 2026 (UTC)
    33. Support, very impressed by the candidate's work at DYK and seems like they will be a positive addition to the admin corps. Dclemens1971 (talk) 15:19, 23 June 2026 (UTC)
    34. Ooh, very exciting, I've known CMD for many many years, since I was working on Rwanda and we were both active in the WikiProject Countries space. An excellent Wikipedian, more than competent to wield the mop, and thanks for stepping up to help.   Amakuru (talk) 15:21, 23 June 2026 (UTC)
    35. Support Gråbergs Gråa Sång (talk) 15:27, 23 June 2026 (UTC)
    36. Support will be a net-positive to the project. « Gonzo fan2007 (talk) @ 15:28, 23 June 2026 (UTC)
    37. Support belatedly, as nominator. Vanamonde93 (talk) 15:29, 23 June 2026 (UTC)
    38. Support with pleasure! 📎 JackFromWisconsin (talk | contribs) 15:42, 23 June 2026 (UTC)
    39. Support as good a candidate as can be. Rand Freeman talkin solidarity 15:44, 23 June 2026 (UTC)
    40. Support — a longstanding contributor with a cool, calm demeanor every time I see them around :). GoldRomean (talk) 15:54, 23 June 2026 (UTC)
    41. Support: Thank you for your work! YuniToumei (talk) 15:56, 23 June 2026 (UTC)
    42. Support Rolluik (talk) 16:08, 23 June 2026 (UTC)
    43. Support Love to see new admins with a couple of GAs under their belt 😄 In addition to the above, I'm happy to support! Johnson524 16:15, 23 June 2026 (UTC)
    44. Support, more belatedly as nom. In solidarity, —Femke (talk) 🐦 16:18, 23 June 2026 (UTC)
    45. Support. Clear net positive, keeps his cool. PMC (talk) 16:29, 23 June 2026 (UTC)
    46. ~~ AirshipJungleman29 (talk) 16:29, 23 June 2026 (UTC)
    47. Support! —TWOrantulaTM (enter the web) 16:31, 23 June 2026 (UTC)
    48. Support, a tireless contributor. Thepharoah17 (talk) 16:32, 23 June 2026 (UTC)
    49. Support! Destinyokhiria (talk / cont) 16:35, 23 June 2026 (UTC)
    50. Support, per all above. Best, Staraction (talk · contribs) 16:35, 23 June 2026 (UTC)
      Wonderful answer to Q12 . Best, Staraction (talk · contribs) 13:15, 26 June 2026 (UTC)
    51. That would be affirmative. Resoundingly. --DoubleGrazing (talk) 16:41, 23 June 2026 (UTC)
    52. Has a clue; not a jerk. Best, Reading Beans, Duke of Rivia 16:45, 23 June 2026 (UTC)
    53. Support per nom TheBirdsShedTears (talk) 16:51, 23 June 2026 (UTC)
    54. Support ULPS (talkcontribs) 16:56, 23 June 2026 (UTC)
    55. Support, don't think I've participated at RfA before, but CMD is seriously a model editor, not an overstatement. Kowal2701 (talk, contribs) 17:11, 23 June 2026 (UTC)
    56. Support, this one's obvious. I'm excited for the impact CMD will have on the project as an administrator. --tony 17:15, 23 June 2026 (UTC)
    57. Support thank you for volunteering and improving global coverage that serves our global audience. ~ In solidarity 🦝 Shushugah (talk) 17:18, 23 June 2026 (UTC)
    58. Support ~delta {talkcont🇰🇷🎢} 17:20, 23 June 2026 (UTC)
    59. Support. Maw Htun Aung (edit | talk | history | protect | delete | links | watch | logs | views) would be in poorer shape were it not for CMD's patience, diligence, assistance at {{Did you know nominations/Maw Htun Aung}}. Rotideypoc41352 (talk · contribs) 17:22, 23 June 2026 (UTC)
    60. In my interactions with CMD I particularly appreciated when they would be comfortable leaving room for uncertainty. Good luck! --Joy (talk) 17:23, 23 June 2026 (UTC)
    61. Support. Excellent content contributions and experience in resolving content disputes. — Newslinger talk 17:29, 23 June 2026 (UTC)
    62. Support Oh good! --Elmidae (talk · contribs) 17:30, 23 June 2026 (UTC)
    63. Best of luck! GreenLipstickLesbian💌🧸 17:35, 23 June 2026 (UTC)
    64. Support - great candidate. Gommeh (talk! sign!) 17:37, 23 June 2026 (UTC)
    65. Support LuniZunie(talk) 17:40, 23 June 2026 (UTC)
    66. Up here Supporting someones RfA rn. fanfanboy (blocktalk) 17:56, 23 June 2026 (UTC)
    67. Support. I honestly thought he was already an administrator. Bgsu98 (Talk) 18:10, 23 June 2026 (UTC)
    68. Support per noms. From previous experience interacting with CMD, the candidate is helpful and trustworthy. Epicgenius (talk) 18:19, 23 June 2026 (UTC)
    69. Elli (talk | contribs) 18:29, 23 June 2026 (UTC)
    70. Support! Chaotic Enby (in solidarity · talk · contribs) 18:31, 23 June 2026 (UTC)
    71. Support very happily. Extraordinary Writ (talk) 18:39, 23 June 2026 (UTC)
    72. Support Consistently impressed with their contributions to DYK and elsewhere. As a side note, every time I see someone say "I thought they already were an admin" I'm reminded that people somehow edit without a username highlighter. DrOrinScrivello (talk) 18:44, 23 June 2026 (UTC)
    73. Ingenuity (talk) 18:45, 23 June 2026 (UTC)
    74. Support - happy to have a such a prolific and proficient Wikipedian added to the admin pool. C679 18:50, 23 June 2026 (UTC)
    75. Support Looks good to me. Happy with the answer to Q4, personally, which demonstrates a familiarity with one of the core areas they intend to be active in. EggRoll97 (talk) 19:00, 23 June 2026 (UTC)
    76. Support In solidarity, Blue-Sonnet (I'm listening) 19:01, 23 June 2026 (UTC)
    77. Support, thank you for running. UpTheOctave!  8va? 19:05, 23 June 2026 (UTC)
    78. Kusma (talk) 19:13, 23 June 2026 (UTC)
    79. Support. Aoba47 (talk) 19:19, 23 June 2026 (UTC)
    80. Yay! charlotte 👸♥ 19:23, 23 June 2026 (UTC)
    81. Support--Ymblanter (talk) 19:26, 23 June 2026 (UTC)
    82. I unironically thought CMD was already an admin. Well, let's fix that oversight. In solidarity, QuicoleJR (talk) 19:40, 23 June 2026 (UTC)
    83. Support NicheSports (talk) 19:40, 23 June 2026 (UTC)
    84. Support Cicada1010 (talk) 19:52, 23 June 2026 (UTC)
    85. Support happily. --Grnrchst (talk) 19:59, 23 June 2026 (UTC)
    86. Support without a question. LightlySeared (talk) 20:11, 23 June 2026 (UTC)
    87. Support FaviFake (talk) 20:11, 23 June 2026 (UTC)
    88. You love to see it! theleekycauldron (talk • she/her) 20:14, 23 June 2026 (UTC)
    89. Support per nom. Best of luck! signed, A Random Hylian (Parry)(swing) 20:22, 23 June 2026 (UTC)
    90. Support EaglesFan37 (talk) 20:52, 23 June 2026 (UTC)
    91. Super excited to see this :) HouseBlaster (talk • he/they) 20:55, 23 June 2026 (UTC)
    92. Support. Gog the Mild (talk) 20:59, 23 June 2026 (UTC)
    93. Support. I have no serious concerns. thunkii (talk) 21:03, 23 June 2026 (UTC)
    94. Saw the name, already know they'll do great in the role. Ed [talk] [OMT] 21:10, 23 June 2026 (UTC)
    95. Support Passes my (minimal) standards for content, know of no reason to oppose.--Wehwalt (talk) 21:17, 23 June 2026 (UTC)
    96. Support Pretty decent editor based on my memory. ✶Quxyz✶ (talk) 21:19, 23 June 2026 (UTC)
    97. Support. Cheers, Chocmilk03 (talk) 21:20, 23 June 2026 (UTC)
    98. Obvious support. Bishonen | tålk 21:46, 23 June 2026 (UTC).
    99. Support Mfield (Oi!) 21:50, 23 June 2026 (UTC)
    100. Support. User is a chipmunk, but also the GOAT of geography editors. His content work is incredible, and his work in some heavy-hitting areas demonstrates clear commitment to and understanding of Wikipedia's policy. — Vigilant Cosmic Penguin 🐧(talk | contribs) 21:51, 23 June 2026 (UTC)
    101. Support Solid. Ceoil (talk) 22:26, 23 June 2026 (UTC)
    102. Support. Yes, yes, yes. I didn't have to think for long about this one. --Tryptofish (talk) 22:34, 23 June 2026 (UTC)
    103. Splendid Girth Summit (blether) 22:39, 23 June 2026 (UTC)
    104. Support! In solidarity, nil nz 22:44, 23 June 2026 (UTC)
    105. Support. Would make a good addition. Mellk (talk) 22:51, 23 June 2026 (UTC)
    106. Support. Easy support. Aircorn (talk) 23:38, 23 June 2026 (UTC)
    107. Support without question. --SHB2000 (talk) 23:41, 23 June 2026 (UTC)
    108. Support; overdue. In solidarity, Iseult Δx talk to me 00:13, 24 June 2026 (UTC)
    109. Support, no concerns. ScottishFinnishRadish (talk) 00:15, 24 June 2026 (UTC)
    110. Support. Finally. In solidarity, asilvering (talk) 00:25, 24 June 2026 (UTC)
    111. Support. Fully qualified candidate. Newyorkbrad (talk) 00:35, 24 June 2026 (UTC)
    112. Ternera (talk) 00:41, 24 June 2026 (UTC)
    113. Support I've only seen good stuff 1brianm7 (talk) 00:46, 24 June 2026 (UTC)
    114. Support Thought already was an admin. DYK needs you. Cielquiparle (talk) 00:55, 24 June 2026 (UTC)
    115. Support toby (t)(rw) 00:58, 24 June 2026 (UTC)
    116. Support. TarnishedPathtalk 01:03, 24 June 2026 (UTC)
    117. Support - InfernoHues (talk) 01:11, 24 June 2026 (UTC)
    118. Support Opm581 (talk | he/him) 01:11, 24 June 2026 (UTC)
    119. Support obviously, because of their excellent work on Wikipedia so far. ~SG5536B 01:25, 24 June 2026 (UTC)
    120. Support ARandomName123 (talk)Ping me! 02:14, 24 June 2026 (UTC)
    121. Support Whonting (talk) 02:28, 24 June 2026 (UTC)
    122. Supprt No concerns. Hawkeye7 (discuss) 02:59, 24 June 2026 (UTC)
    123. Support My first thought was "If CMD is nominating them they're probably a good candidate" followed by "wait CMD is the candidate? I thought they already were." -- LWG talk (VOPOV) 04:46, 24 June 2026 (UTC)
    124. ~ Jenson (SilverLocust 💬) 04:59, 24 June 2026 (UTC)
    125. Support. Best wishes. Volten001 05:41, 24 June 2026 (UTC)
    126. "Thought you were already an admin when I first met you" is a common statement, though this time I agree with it. Support. Those fishery articles aren't going to patrol themselves. Chlod (say hi!) 06:34, 24 June 2026 (UTC)
    127. Support – Great answers to the questions and noms; nothing to complain about here. Graham87 (talk) 07:58, 24 June 2026 (UTC)
    128. Support. Really an inspiration with the article on Papua New Guinea - I was very happy to review that. Generalissima (talk) (it/she) 08:19, 24 June 2026 (UTC)
    129. Support. Have seen a lot of good and sensible work. Martinevans123 (talk) 08:32, 24 June 2026 (UTC)
    130. Support Another net positive -Kj cheetham (talk) 09:33, 24 June 2026 (UTC)
    131. Support Calm and sensible person. His vital articles and works are really good. 100% support. 🍗TheNuggeteer🍗 (My "blotter") 10:29, 24 June 2026 (UTC)
    132. SupportIn solidarity, Penn65 talk 12:10, 24 June 2026 (UTC)
    133. sapphaline (talk) 14:07, 24 June 2026 (UTC)
    134. Support: There's a lot to like about CMD and they clearly have all the prerequisites for adminship. They have a commitment to Wikipedia's encyclopedic vision that will serve the admin corps well. Best, ~ Pbritti (talk) 14:12, 24 June 2026 (UTC)
    135. Support. A contributor who is passionately echoing and zeroing in on the spirit of Wikipedia and consensus in the underpoliced venues and avenues. Ong Kai Jin (talk) 14:48, 24 June 2026 (UTC)
    136. Support. also sure, also per noms TheresNoTime (talk • they/them) 15:31, 24 June 2026 (UTC)
    137. Support. Great editor. Very surprised they one aren't already. Metaviva (talk) 15:40, 24 June 2026 (UTC)
    138. Enthusiastic support. You've always give me the impression of being clueful wherever we've interacted. HJ Mitchell | Penny for your thoughts? 16:10, 24 June 2026 (UTC)
    139. Support. MSincccc (talk) 16:11, 24 June 2026 (UTC)
    140. Support No concerns Ritchie333 (talk) (cont) 18:54, 24 June 2026 (UTC)
    141. Support Pawnkingthree (talk) 19:42, 24 June 2026 (UTC)
    142. Support --Minoa (talk) 19:48, 24 June 2026 (UTC)
    143. Support - no concerns. GiantSnowman 20:16, 24 June 2026 (UTC)
    144. Support. Answers were quite good. In solidarity Wikipedian12512 (Talking is fine | contribs) 21:04, 24 June 2026 (UTC)
    145. Support, looks good. I am bad at usernames (talk · contribs) 21:21, 24 June 2026 (UTC)
    146. Support, for another 2009 OG. Azyrii (talk) 22:12, 24 June 2026 (UTC)
    147. --Guerillero Parlez Moi 22:39, 24 June 2026 (UTC)
    148. Support, seems clueful --SarekOfVulcan (talk) 23:49, 24 June 2026 (UTC)
    149. Support - trustworthy editor. PhilKnight (talk) 03:58, 25 June 2026 (UTC)
    150. Support - I don't show up here very often, but this is one where I genuinely am surprised the user is not already an admin. Risker (talk) 05:09, 25 June 2026 (UTC)
    151. Support Jordano53 05:55, 25 June 2026 (UTC)
    152. Support Surprised that this nomination didn't happen earlier.-- Least Action (talk) 11:07, 25 June 2026 (UTC)
    153. Support Excellent candidate.— Diannaa 🍁 (talk) 13:09, 25 June 2026 (UTC)
    154. Support I'm so glad to see this. You'll be a great admin. Clayoquot (talk | contribs) 13:38, 25 June 2026 (UTC)
    155. Suport with excitement! Bobby Cohn 🍁 (talk) 14:23, 25 June 2026 (UTC)
    156. Support ScalarFactor (talk) 17:01, 25 June 2026 (UTC)
    157. Support Strongly! Chipmunkdavis has been a stellar editor for years and will make an excellent administrator. RegentsPark (comment) 17:56, 25 June 2026 (UTC)
    158. Support -- Ajraddatz (talk) 18:34, 25 June 2026 (UTC)
    159. Support Tenshi! (Talk page) 19:23, 25 June 2026 (UTC)
    160. Support Giulio 22:15, 25 June 2026 (UTC)
    161. Support. Thanks for being willing to take the mop. Loopy30 (talk) 00:03, 26 June 2026 (UTC)
    162. Support, Rjjiii (talk) 00:57, 26 June 2026 (UTC)
    163. Support, strong contribution history. Nikkimaria (talk) 01:34, 26 June 2026 (UTC)
    164. Support Bringingthewood (talk) 02:14, 26 June 2026 (UTC)
    165. Support Looks good, no concerns. - RevelationDirect (talk) 02:16, 26 June 2026 (UTC)
    166. (t · c) buIdhe 03:15, 26 June 2026 (UTC)
    167. No notes Elias 🦗🐜 [Chat, they chattin', they chat] 05:41, 26 June 2026 (UTC)
    168. Support strong candidate jolielover♥talk 07:33, 26 June 2026 (UTC)
    169. Support. MCE89 (talk) 16:59, 26 June 2026 (UTC)
    170. Support, of course. Cordless Larry (talk) 19:45, 26 June 2026 (UTC)
    171. SupportKurtis (talk) 21:48, 26 June 2026 (UTC)
    172. Support Another user who I know from DYK. Steady editor. Schwede66 21:51, 26 June 2026 (UTC)
    173. Support per answers to questions and experience. --NYC Guru (talk) 23:18, 26 June 2026 (UTC)
    174. Support per nom and others. Mesocyclonic93 (t)(c) 01:56, 27 June 2026 (UTC)
    175. Support No reason not to. The Knowledge Pirate (talk) 05:02, 27 June 2026 (UTC)
    176. Support JuniperChill (talk) 08:20, 27 June 2026 (UTC)
    177. Support. Have frequently seen them around and I would trust them with the toolset. gurkubondinn 12:34, 27 June 2026 (UTC)
    178. Support. I trust you. --Rosiestep (talk) 13:13, 27 June 2026 (UTC)
    179. Support. -SmokeyJoe (talk) 13:39, 27 June 2026 (UTC)
    180. Support Josey Wales Parley 15:34, 27 June 2026 (UTC)
    181. Support happy to support this candidate. Every time I see them around wiki they contribute in a calm measured manor and with the trusted noms and their good articles I have no doubt they will make a great admin. GothicGolem29 (Talk) 17:04, 27 June 2026 (UTC)
    182. Support Fathoms Below (talk) 17:25, 27 June 2026 (UTC)
    183. Support. Frost 17:51, 27 June 2026 (UTC)
    Oppose


      Neutral
        General comments

        I'm not sure some of the questions at this RfA were necessary. I thought "What is the purpose of your username" had been done to death, and as for Q7 - has that ever actually happened? Ritchie333 (talk) (cont) 18:55, 24 June 2026 (UTC)

        My reason for Q7 was more of a gauge of character- if CMD was too quick too block such an admin, then I would have opposed. In solidarity Wikipedian12512 (Talking is fine | contribs) 21:38, 24 June 2026 (UTC)
        CMD could not block even if he wanted to, being blocked himself. I would have thought an unblock request was in order, but what would I know? Hawkeye7 (discuss) 04:01, 25 June 2026 (UTC)
        Actually, you can block the admin who blocked you: Wikipedia:Blocking_policy#Against_the_blocking_administrator. If an admin account is compromised or goes haywire, this is one way to stop that. In solidarity, —Femke (talk) 🐦 05:20, 25 June 2026 (UTC)
        sounds like a mutually destructive option. Admins blocking each other. – robertsky (talk) 06:04, 25 June 2026 (UTC)
        Used to happen in the old days! I don't think a blocked admin account can block. Nor can an admin unblock themself anymore. I would have taken the question as asking for the appealing a block procedure. Hawkeye7 (discuss) 08:09, 25 June 2026 (UTC)
        Yes, a blocked admin can block the account that blocked them. For precisely this reason. In solidarity, asilvering (talk) 18:46, 25 June 2026 (UTC)
        I was surprised it was a random choice -- I was assuming it was a Chip Davis reference. SarekOfVulcan (talk) 23:50, 24 June 2026 (UTC)
        Honestly, if someone who foresaw that Lourdes would be a terrible admin only has a fun question to ask at RfA, that's a good sign. Rotideypoc41352 (talk · contribs) 18:29, 26 June 2026 (UTC)

        About RfB


        Requests for bureaucratship (RfB) is the process by which the Wikipedia community decides who will become bureaucrats. Bureaucrats can make other users administrators or bureaucrats, based on community decisions reached here, and remove administrator rights in limited circumstances. They can also grant or remove bot status on an account.

        The process for bureaucrats is similar to that for adminship above; however the expectation for promotion to bureaucratship is significantly higher than for admin, requiring a clearer consensus. In general, the threshold for consensus is somewhere around 85%. Bureaucrats are expected to determine consensus in difficult cases and be ready to explain their decisions.

        Create a new RfB page as you would for an RfA, and insert

        {{[[Template:RfB|subst:RfB]]|User=<var   style="padding-right: 1px;"  >Username</var>|Description=<var   style="padding-right: 1px;"  >Your description of the candidate.</var> ~~~~}}

        into it, then answer the questions. New bureaucrats are recorded at Wikipedia:Successful bureaucratship candidacies. Failed nominations are at Wikipedia:Unsuccessful bureaucratship candidacies.

        At minimum, study what is expected of a bureaucrat by reading discussions at Wikipedia talk:Requests for adminship including the recent archives, before seeking this position.

        While canvassing for support is often viewed negatively by the community, some users find it helpful to place the neutrally worded {{RfX-notice|b}} on their userpages – this is generally not seen as canvassing. Like requests for adminship, requests for bureaucratship are advertised on the watchlist and on Template:Centralized discussion.

        Please add new requests at the top of the section immediately below this line.

        Current nominations for bureaucratship

        There are no current nominations.

        For RfA participants

        History and statistics

        Removal of adminship

        Noticeboards

        Permissions

        Footnotes

        1. permanently authorised in an RfC held in early 2025
        2. Candidates were restricted to editors with an extended confirmed account following the discussion at Wikipedia:Requests for adminship/2024 review/Phase I § Proposal 25: Require nominees to be extended confirmed.
        3. Voting was restricted to editors with the extended confirmed right following the discussion at Wikipedia:Requests for adminship/2024 review/Phase I § Proposal 14: Suffrage requirements.
        4. The community determined this in a May 2019 RfC.
        5. Historically, there has not been the same obligation on supporters to explain their reasons for supporting (assumed to be "per nom" or a confirmation that the candidate is regarded as fully qualified) as there has been on opposers.
        6. Wikipedia:Requests for adminship/2024 review/Phase I#Proposal 17: Have named Admins/crats to monitor infractions and Wikipedia:Requests for adminship/2024 review/Phase II/Designated RfA monitors