Wikipedia:Arbitration Committee/CheckUser and Oversight/2018 CUOS appointments/CU

Ivanvector (CU)

 * Nomination statement


 * Hello Wikipedians! I'm Ivanvector, and I'm applying for the checkuser permission. I have been a sockpuppet investigations clerk for two years and an administrator almost as long. I'm seeking access to checkuser obviously to aid in my SPI work – although there is not often a backlog in requests awaiting checkuser these days, there is a persistent backlog of “open” cases which often require checkuser attention in the course of investigation. As a clerk I endorse or request (self-endorse) checkuser probably about 10-20 times a week, and I’m keenly familiar with what checkusers can and cannot do from many interactions with the team. We also have a significant backlog of users interested in clerk training, which I would like to help with. Aside from SPI, I have experience in networking and technicalities of the internet from working with networked computers throughout my professional life as well as deploying home and small office networks. I’m familiar with both IPv4 and IPv6 subnet masking, and I’m currently one of 24 administrators listed in the “willing to make range blocks” category. Professionally, I work in accounting and finance, especially in payroll and benefits administration, which involves handling individuals’ very sensitive confidential information such as banking information, details of health issues, and immigration matters. I am very well-versed in handling and protecting such information, including tactful and respectful ways to decline requests for access. I look forward to your questions and comments.

Standard questions for all candidates

 * 1) Please describe any relevant on-Wiki experience you have for this role.
 * As mentioned in my nomination statement, I have been a sockpuppet investigations clerk fully for just over two years (June 2016, training started December 2015) and an administrator almost as long (December 2016). I already regularly interact with many of the current checkusers both on- and off-wiki, and I'm familiar with the sort of information that can be gleaned from the tool, as well as (vaguely) how checkusers publish their results on the public wiki and what the various CU tags mean. I'm fairly consistently active at SPI and also frequently comment on issues related to the [ab]use of multiple accounts in many areas of project space.
 * 1) Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
 * Professionally, I am an accountant and currently also payroll and benefits administrator for a medium-sized tech-driven manufacturer. I regularly handle confidential private and sensitive employee information in the course of my work. I'm also familiar with IPv4 networks and network address translation from years of home and occasional professional network maintenance, large IT projects and software deployment, and I have some working knowledge of IPv6 through my work in SPI.
 * 1) Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
 * I do not. I have never applied for nor held any of these permissions on any wiki, nor OTRS.

Comments

 * Comments may also be submitted to the Arbitration Committee privately by emailing . Please note that the candidate will be provided the opportunity to respond to a paraphrased version of any emailed comments; the sender's name will not be provided.


 * Oppose There numerous issues which I would prefer detailing by naming only two cases that involved you as an SPI clerk:-
 * NadirAli: You noted in his block notice that he was blocked because he was "editing from alternate accounts and while logged out". Block log entry made by you says "using multiple accounts and editing while logged out". You blocked this long term sockmaster for only 3 months when standard duration is indef block.
 * You significantly changed your statement when site ban was proposed on WP:AN. You claimed that "accounts are blocked for being sockpuppets of each other, not for being sockpuppets of NadirAli." You were reminded of your own statements on WP:AN along with new evidences that how these accounts are socks of NadirAli however your replies were unconvincing and couldn't change your earlier rational that NadirAli had "evidently created sockpuppet accounts in violation of an Arbcom-imposed unblock condition". The user was sitebanned in the same thread for reasons that included sock puppetry.
 * StLouis2: This user was reported as a sock on Sockpuppet investigations/StLouis2/Archive and you clerked in his this case even though you were involved in content dispute with the reporting editor (Masterpha2) as well as the suspect (StLouis2).
 * CU stated that StLouis2 is abusing proxies and "I was almost tempted to block the account for looking so suspicious." However you acquitted the suspects and this was contrary to the behavioral evidence provided by multiple editors as well as the policy on open proxies that the account should be blocked if they are found abusing proxies to circumvent policy. This account was later given a checkuserblock-account block by Courcelles for sock puppetry, following an ANI report.
 * These examples show that you have been evaluating technical evidence or behavioral evidence only when it suits you in place of evaluating them on their merits. I can in fact substantiate more examples but above two are clearly enough for establishing that you are not qualified for CU permission. Lorstaking (talk) 04:29, 18 September 2018 (UTC)


 * Support I disagree with the above comments and think that Ivanvector adheres strongly to the good principle of "talk before you block". I also found his comments around the block of to be helpful and constructive, attempting to see all sides of the debate. Ritchie333 (talk)  (cont)  10:34, 18 September 2018 (UTC)
 * Are you sure? Ivanvector didn't talk Saqib before he blocked him for a week. I am not certainly raising issue with it but it was contrary to "talk before you block". In Nauriya's case, Ivanvector first claimed that Nauriya was found "unrelated" to Faizanali.007, though later struck his comments after I pointed it on his talk page that Nauriya had admitted Faizanli.007 to be his own account. Next day Ivanvector claimed that Nauriya has not socked "since 2013", contrary to the fact that Nauriya was evading his block for years. Numerous others including an uninvolved admin also disagreed with Ivanvector and verified that block evasion is sock puppetry. We cannot say this was a misunderstanding because block evaders have been already treated as socks and recently another editor was blocked by multiple admins for engaging in similar block evasion for years. Including this one, my above comment has described some other serious problems such as not taking action against a proxy abuser and changing own statements about sock puppetry of a long term sock abuser. Lorstaking (talk) 11:43, 18 September 2018 (UTC)


 * Support Mostly, per Ritchie. To add, my assessment of Ivan's past administrative actions have painted a picture of a thoroughly careful editor, who takes their time to assess the situation and act judiciously. I'm not sure why Ivan's decided to not answer the standard questions discretely, but notice that most of the responses are written within the nomination statement. All well, in my opinion, Lourdes  11:35, 18 September 2018 (UTC)
 * A matter of timing. I had already put my laptop away for the night when the page went live, and didn't see the email about it until this morning. Ivanvector (Talk/Edits) 12:17, 18 September 2018 (UTC)


 * Support Thoughtful admin with sound judgement. Extensive experience in SPI clerking is also a plus. –Ammarpad (talk) 13:34, 18 September 2018 (UTC)
 * Support Experienced SPI admin clerk, will do fine work as CU. Thank you for volunteering. Alex Shih (talk) 13:52, 18 September 2018 (UTC)
 * Support Displays the thoughtfulness and judgment I'd expect from a CU. -- Laser brain  (talk)  14:19, 18 September 2018 (UTC)
 * Suppport. Ivanvector's judgement as an SPI clerk has been solid. Vanamonde (talk) 14:27, 18 September 2018 (UTC)
 * Support, an excellent and experienced SPI clerk. GABgab 14:31, 18 September 2018 (UTC)
 * Support - good work at SPI, will be able to use the tools well. -- Ajraddatz (talk) 14:44, 18 September 2018 (UTC)
 * Support: Actively working at SPI is enough for me to support. Clear need and experienced with the process. Best of luck! &#8208;&#8208;1997kB (talk) 15:54, 18 September 2018 (UTC)
 * Support Excellent work as a SPI clerk, will really do well with the tools .  Kpg  jhp  jm  16:22, 18 September 2018 (UTC)
 * Support Experienced with the SPI process, thoughtful in his actions, qualified for CU. Ms Sarah Welch (talk) 18:11, 18 September 2018 (UTC)
 * oppose About 5 days ago, you were on an AN thread and you still edited even after it was closed and your edits post closure show that you were accusing a established editor with over 40k edits of "obvious meatpuppetry". You clearly violated WP:ASPERSIONS and WP:NPA there. It is even more concerning that you went ahead to edit war to restore this personal attack. Such battleground behavior is unsuitable from an admin or editor, let alone checkuser.desmay (talk) 19:57, 18 September 2018 (UTC)
 * Support - Fully qualified SPI worker, not to mention one of our most clueful admins. Exceptional candidate all around.  𝖘 𝔴𝔞𝔯𝔪  𝔛 00:17, 19 September 2018 (UTC)
 * Support - Trusted admin with SPI experience. Beyond My Ken (talk) 01:50, 19 September 2018 (UTC)
 * Support. Drmies (talk) 01:53, 19 September 2018 (UTC)
 * Support per Lorstaking: the willingness to reevaluate the evidence and speak up despite others having already made up their mind is an asset to the CU team, not a liability. --Rschen7754 04:37, 19 September 2018 (UTC)
 * Support Good tenure, clue, actual need for the tool. Widr (talk) 05:56, 19 September 2018 (UTC)
 * Support, would seem to be suited to this role. Fish +Karate 08:23, 19 September 2018 (UTC)
 * Support Right disposition and experience for this tool. Best, Barkeep49 (talk) 18:31, 19 September 2018 (UTC)
 * Support Proven competence, good attitude and will make good use of tool. -- Begoon 23:08, 19 September 2018 (UTC)
 * Support - No concerns about his suitability for the tool. Competent, reasonable and trusted. --  Dane  talk  03:54, 20 September 2018 (UTC)
 * Support — Experienced and competent admin with experience as an admin SPI clerk; no deal-breaking issue. Regards, SshibumXZ (talk · contribs). 09:09, 20 September 2018 (UTC)
 * Oppose - In spite of some of his good work, I consider this admin to be "biased" one, based on some very recent cases, some shown above, this admin has a tendency to use Admin tools in support of editors who share his POV and against the editors he appears to "have an axe to grind". Good sense would dictate that an admin who is (or can be reasonably seen as) involved in the dispute stay away from such cases and let other admins handle it for the sake of neutrality, but here we have an editor who decides to jump in, openly threaten and use his admin powers.
 * Also attempts to openly admonish editors who criticize and point out this improper behavior.
 * The disturbing StLouis2 SPI case above is just 2 months old.[Updated] Ivan was involved in the content dispute about text  on a page with Ivans own Edit Count of 25 and yet he goes on to Protect the page three times, and then Join SPI inspite of being in the dispute with Filer and the suspect, and then absolved the suspect (who was later blocked) blatantly disregarding WP:INVOLVE policy.
 * Everyone is aware that, there are a lot of "technical Grey areas", in the results of the CU tools and CUs and admins often decide on the results of the tools, based on their best judgement. I can easily imagine that such a biased admin after getting hold of CU will falsely convict opponents of sockpuppetry, and if an abuser happens to share the same POV as this admin, then absolve proxy abusers like he did in St Louis case.
 * Was seen trying too hard supporting problem users like NadirAli and dishing out ad hominem on editor reporting Nadir.
 * Reverted me 10 days back to restore a malicious slander from the harassment sock of a banned user against WP:BMB and WP:SOCKSTRIKE. One can easily see clear intentions, in his revert i.e. to support abusers who share his POV.
 * Openly badgering bullying and threatening "punitive blocks"
 * "It is not merely of some importance, but is of fundamental importance that justice should not only be done, but should manifestly and undoubtedly be seen to be done".-Lord Chief Justice Hewart in R v. Sussex Justices, ex parte McCarthy The confidence of the right-minded people is destroyed when they go away thinking that the judge was biased – that he had been influenced by the other party. The judge’s reputation for fairness and justice is shattered by this. It does not matter whether he did, in fact, favour one side unfairly.
 * All these reasons leads me to think this admin will "checkuser block" people liberally and be unwilling to consider appeals. Other admins don't have the powers to revert a CU block
 * I believe this will ultimately badly affect Wikipedia's neutrality with such editors being given such powers. Hence my oppose.-- D Big X ray ᗙ  14:15, 20 September 2018 (UTC)
 * What is "disturbing" about the Stlouis SPI case on Ivan's part? Your comment that he will falsely "convict" editors is absurd and in WP:NPA territory. If you believe Ivanvector is abusive, that seems like something you need to take to AN instead of making accusations here of things that have not happened. CHRISSY MAD  ❯❯❯  ¯\_(ツ)_/¯  14:25, 20 September 2018 (UTC)
 * - I am leaving a ping here for you to respond as your comment about the StLouis case is an actual personal attack and should be removed/redacted on your own volition. CHRISSY MAD  ❯❯❯  ¯\_(ツ)_/¯  14:48, 20 September 2018 (UTC)
 * I added more details in the line above, kindly take a relook. Please note that Wikipedia policies (WP:PROXY) support blocking of a proxy abuser (StLouis2) however Ivanvector absolved this user regardless of Ivan himself being involved in same content dispute, against the reporting editor (Masterpha), and the mass proxy abuse by StLouis2. This user StLouis2 was later blocked by a CU for his sockpuppetry, thankfully.  D Big X ray ᗙ  15:29, 20 September 2018 (UTC)
 * this diff is Ivan admitting their mistake, the others show no abuse in any manner and given there's been no discussion on that anywhere, this is still an unsubstantiated claim and personal attack. CHRISSY MAD  ❯❯❯  ¯\_(ツ)_/¯  15:49, 20 September 2018 (UTC)
 * , I agree with you. Ivan's protection of the page seems clearly involved. I would have trouted Ivan if I had known of this issue before (I'm actually surprised Ivan undertook this administrative action). To be transparent, I've trolled CUs like for undertaking involved CU blocks on socks that have edited pages that they themselves have edited in the past. I can understand your personal interaction with Ivan hasn't been in the positive – and you may be in your right to have this negative perspective. But administrators and CUs (like Bbb23 above) do make mistakes, and most accept the same and improve. This should not taint your view of their overall stellar contributions. I'm sure Ivan understands and appreciates the issues you have raised in the same light. Warmly,  Lourdes  15:54, 20 September 2018 (UTC)
 * " I've trolled CUs like Bbb23 Might you mean "trouted"? Trolling probably isn't going to be very helpful. Natureium (talk) 15:58, 20 September 2018 (UTC)
 * ("Trolled" is what I mean; and no, it wasn't very helpful, as you rightly estimated. Lourdes  16:01, 20 September 2018 (UTC))
 * Well,, I suppose I should reply to this. As usual there's more to the story than what is offered here, probably because DBigXray and Lorstaking have never edited that article but seem to have decided I'm their enemy. See Sockpuppet investigations/Masterpha/Archive for how I ended up at Opinion polling for the Pakistani general election, 2018. I watchlisted the page and was following a slow edit war over including the results of a poll conducted entirely over Facebook with no methodology. It was basically back-and-forth for months and the page had already been protected once, so rather than try technical restrictions again I decided to clean up some issues with the article myself - filling refs, consistent table formatting, scraping external links, and so on. I've often found that that's a better solution than admin button-pushing, it allows editors to see what might be a better way forward, and in this case it worked. Some editors had questions but nobody really objected, and the edit warring stopped. Later, around mid-June, the same Facebook pollster released another poll, and there were heated discussions on the talk page about which polls should be included. This was good, but there was an accompanying edit war, and semiprotected the page. Later it came across my watchlist with confirmed editors still carrying on the edit war, and I upgraded Melanie's protection to full (and see Talk:Opinion polling for the Pakistani general election, 2018 where she endorsed this). After that protection expired (protections always expire to no protection) the editors active on the page noted that IP vandalism resumed on the page, and pinged me (see the same discussion) to ask me to restore Melanie's protection, which I did on 9 July. On 11 July  created the StLouis2 SPI, and when I saw it I thought it would be best to handle it expeditiously as it was having a negative impact on collaboration on the article, you can see on the page how that went. I don't understand the objection about the open proxy: we can block an IP when it's identified as an open proxy but users with accounts are allowed to use a proxy to edit; some have no choice. We block them if they're disruptive - in my opinion at that time there was insufficient evidence, and I don't block users unless there's a good reason. The next day (12 July) I was pinged again to intervene, so I offered my opinion. After that there was a separate dispute over wording in the article's lede, which I proposed a solution to, but StLouis2 rightly pointed out that my edit was unhelpful, and so I added that null edit on 17 July to confirm I was wrong, because that thing was happening where other editors were reverting to my edit just because it was made by an admin. I hadn't really considered myself capital-I involved up to having made that proposed edit, since nothing I had done was really substantive. Afterwards, when there was edit warring over something else, I posted a protection request at RFPP that  actioned, and when that expired (to no protection) I restored MelanieN's original semiprotection again, which maybe I should have asked someone else to do but there's that "any admin would do this" point in WP:INVOLVED that seemed like it applied to this situation. And, yes, some months later  blocked StLouis2 as a checkuser action, but I have no more info about that than anyone else that's commenting.
 * Anyway, yes, this is an edge case, and I acknowledge that a very strict reading of WP:INVOLVED may dictate that I've erred, but I personally think that the article is better for it, and we're all here to build an encyclopedia, not bicker about strict interpretations of rules. If other editors think that my actions here were grossly out of line then so be it, but at least now you have the whole story. Ivanvector (Talk/Edits) 17:32, 20 September 2018 (UTC)
 * "if they're disruptive"? That is completely wrong because sock puppetry is itself one of the major forms of disruption and in any case the account in question was really disruptive. Lorstaking (talk) 18:06, 20 September 2018 (UTC)
 * I'm confused. Is everyone mad because he took no action based on inconclusive CU results that were not run by him, since he's not a CU? I'm all for blocking socks indefinitely but it's still better to not block an account where there is significant doubt. Kind of goes against Xray's inane theory that he will abuse the tools. Better to be conservative with the blocks than over-zealous, especially when there is technical evidence in dispute. CHRISSY MAD  ❯❯❯  ¯\_(ツ)_/¯  18:22, 20 September 2018 (UTC)
 * I think we can bring this discussion to a close here (or shift it to the talk page). Ivan's explanation is absolutely satisfactory and it makes no sense to simply let this discussion become an eyesore and a waste of reading space for future commenters. Might I request any passing editor to either collapse this discussion or shift it to the talk page in toto? Thanks, Lourdes  23:56, 20 September 2018 (UTC)


 * Support - No concerns. — Godsy (TALK CONT ) 20:08, 20 September 2018 (UTC)
 * Support Active and experienced SPI clerk, no concerns. Simplexity22 (talk) 23:25, 20 September 2018 (UTC)
 * Support Regardless of the controversy that he has recieved around being “involved” in a dispute between several editors and I, I have found him to be quite reasonable in his decisions and has never been biased. His experience at SPI will help. маsтегрна  таLк  08:16, 21 September 2018 (UTC)
 * Oppose You request topic ban from WP:ARBIPA on a dozen of editors without adding diffs for your claims and further state that you "would just ban everybody". But when the most disruptive user has been caught socking for a long time, you give him only 3 months block and then endlessly argue to falsify every inch of evidence provided against the now sitebanned user. Not to omit your filing of a frivolous AE report citing "ARBIPA topic" ban against a user after rejecting a legible SPI as "violation" of a topic ban after completely misreading the SPI yourself (for e.g. missing the self admission of one suspected account to be related to master). The user told you at least 2 times that it is not a topic ban violation and you refused to believe this simple fact and reacted in a combative manner.[ You realised that it was not a topic ban violation only after an admin told you that it is was not.It is unbelievable that it was only 1 week ago that you learned that Pakistani articles also falls under WP:ARBIPA, and surprisingly you were telling an arbitrator that what comes "under WP:ARBIPA" This means that you have been talking about ARBIPA for over 5 months and you don't even know the easiest definition of [[WP:ARBIPA]]. You don't think sock puppetry is "disruptive" or think it needs extra evidence of disruption to block an account than just socking (or socking with proxies) per your statements on this page. Your block of Adding The Truth as a sock of My Lord was disputed by nearly everyone who took time to review the unblock request on his talk page, including the reviewing admin. Adding The Truth could've been a sock of someone but not My Lord and thus your your block was incorrect that was based  on "inconclusive" checkuser and very circumstantial behavioral evidence. In the light of these latest incidents, I find it extremely uncomfortable to think that you should get this permission.  Razer ( talk ) 13:53, 21 September 2018 (UTC)
 * There's more to these claims, again, thus I encourage those reading to review for themselves:
 * Razer2115 claims that I "requested" topic bans, but I did not: in this AE discussion I endorsed the suggestions of several other administrators that a number of users should be sanctioned. Razer also claims that there was no evidence, but also linked to the edit in which I explained to that nearly two hundred diffs had already been provided in that discussion.
 * I thoroughly explained my rationale for blocking Adding The Truth (Sockpuppet investigations/My Lord/Archive), and expanded with respect to one of the more contestable points of my analysis on the user's talk page after being asked to do so. Of the administrators who commented, one explicitly agreed with the SPI finding, and four more were not entirely convinced of the exact sockpuppetry finding but declined to unblock for various reasons including probable meatpuppetry. In the end the user was advised to approach UTRS to disclose their supposed exonerating evidence which they would not discuss on-wiki, and since they remain blocked I presume they have not done so or the evidence was not so exonerating.
 * The SPI I supposedly "misread" (Sockpuppet investigations/MegaCyanide666/Archive) involved a blocked user who some time earlier had come logged-out to 's talk page inquiring about how to get unblocked. They disclosed their original account was blocked and mentioned they used multiple socks in the distant past. A discussion among several admins and checkusers which I was not involved in endorsed this user creating a new account as a WP:CLEANSTART noting the standard offer. Capitals00 later filed the SPI noting one of the supposed socks which was blocked two years earlier. Boing! explained that past sockpuppetry had been considered when offering the user a clean start, and this new finding would not invalidate that decision, so blocking would have effectively been wheel-warring and I was not going to do it. I also found Capitals00's evidence unconvincing.
 * In the same SPI, I noted that Capitals00 was under a topic ban which I believed applied to an article which the other user had been editing. Capitals00 insisted that was not the case, but did not attempt to explain why. I went to AE (Arbitration/Requests/Enforcement/Archive240) to request a review of that situation; when (who is not an admin) pointed out that the article was definitely not within the scope of the topic ban (an admittedly serious error on my part) I withdrew the request and apologized to Capitals00. That was not before another admin noted that, had the article been within the topic ban scope, reporting a user editing that page to SPI would have been considered a violation.
 * -- Ivanvector (Talk/Edits) 17:45, 21 September 2018 (UTC)
 * Comment - in regards to the AE above, while content wise this was clearly not ARBIPA - if one was examining the editors involved, and positions/rhetoric, it was quite similar to ARBIPA.Icewhiz (talk) 18:07, 21 September 2018 (UTC)
 * Ivanvector, I don't see any diffs in your AE statements, where you were requesting topic bans on editors.
 * My Lord was not Adding The Truth, that's the point. It is irrelevant to say that block can be right because the user didn't appealed to UTRS. One user wondered how it is possible for ATT to edit Wikipedia now. The judgement of blocking an editor had to be so clear that everyone could agree but here you had majority of users refuting your decision.
 * The discussion you are referring clearly didn't involved "several admins and checkusers", but only two admins unaware of the mass socking revealed in the SPI. The SPI filed by Capitals00 against MegaCyanide666 was definitely convincing since we don't expect anything more than knowing the fact that suspects made same edits, have suspicious timing of account creation, and not only resides in same city but even shares same pincode as evidenced by the details of their IPs which they used during block evasions. I find it pretty obvious that you didn't read the rest of the SPI, since you misread the very first sentences of the SPI. You rejected the whole SPI as mostly a topic ban violation when there was none. Boing! had admitted that MegaCyanide666 never revealed that he was KahnJohn27, but once we were aware that he is KahnJohn27 then the new account had to be blocked since there could be no unblock without a proper community discussion and/or unblock conditions given the mass socking. Some diffs of sock puppetry dated 14 May which indicates that he was socking even during that same day when he was making requests to resume his editing. WP:SO says that editor should not sock for at last 6 months. If we are going to encourage people use flimsy reasons like "I forgot password" then a time will come when we won't see any unblock requests on past accounts since blocked accounts returning after a community discussion are clearly more scrutinized than the newly created accounts and socks would better prefer the latter.
 * It is not a WP:CLEANSTART when the user is disrupting same subjects and articles that he did with his previous socks and "clean start is not permitted if there are active bans, blocks or sanctions." You are also wrong with your definition of "wheel-warring". It is not WP:WHEEL when you overturn an admin's action based on new evidence. It is "wheel-warring" when you restore an overturned admin action.
 * The scope of topic ban was easily understandable. It was already made clear for you that there could be no doubts over the scope since a bridge between India and Sri Lanka has nothing to do with wars and conflicts between India and Pakistan and you still refused to believe it until other users intervened. Lorstaking (talk) 04:45, 22 September 2018 (UTC)


 * Neutral-As much as some of the events (esp. Nadir Ali and St.Louis) are quite over-exaggerated (and that ARBIPA is a spectacle to administrate in;), they do have minimal merit.Coupled with his AE report against Capitals00 and blocking of Adding the Truth as MyLord's sock, his actions don't instill enough confidence to take me into the green zone. &#x222F; WBG converse 14:58, 21 September 2018 (UTC)
 * Support An all around superb user whose high competence and dedication to the project cannot be questioned. He is not afraid to do what he feels is in line with policy and right, even if it may be unpopular with some -- this is a virtue, not a vice. --Calthinus (talk) 20:49, 21 September 2018 (UTC)
 * Oppose. While I have seen Ivanvector's good grasp of admin tools and some spot-on decisions, his actions at User:AddingTheTruth have shaken my confidence both in his judgement and in the manner he engages (or does not) in dicussions. In the light of other – and serious – issues listed by User:Razer2115 and User:Lorstaking, I consider this nomination as done too early. I will gladly revisit if the nominee is re-nominated in 6 months' time. — kashmīrī  TALK  08:19, 22 September 2018 (UTC)
 * Support – This is clearly a qualified candidate. Mz7 (talk) 19:54, 22 September 2018 (UTC)
 * Support per Lorstaking. —SerialNumber54129  paranoia / cheap sh*t room 11:03, 23 September 2018 (UTC)
 * Lorstaking voted Oppose in this nomination. — kashmīrī  TALK  15:23, 23 September 2018 (UTC)
 * Yes, although there's slightly more to it than what the answer below might suggest, as it is generally a reflection on the paucity of the argument presented (which of course is why it is such a poor example in the first place, as that was in response to a forensic dissection of the candidate's suitability, rather than a blind misstatement as is the case here). Happy editing, everyone! —SerialNumber54129  paranoia / cheap sh*t room 18:18, 23 September 2018 (UTC)
 * I am not Serial Number 54129, so could not answer for sure, but editors do occasionally support/oppose based on the opposing (as in opposite to their) !votes. An example of this was BU Rob13's !vote on my RfA (support #39). -- The SandDoctor Talk 17:52, 23 September 2018 (UTC)


 * Support no concerns. -- The SandDoctor Talk 17:52, 23 September 2018 (UTC)
 * Support – Ivanvector has the experience, competency, & integrity required for the handling of CU. And he is not afraid to handle highly volatile & problematic areas for the overall betterment of the project. - NitinMlk (talk) 21:50, 23 September 2018 (UTC)
 * Support Ivanvector with the CU tool would transform the entire SPI process. Experienced, civil and hard-working. He has helped with his experience in fighting socking in difficult areas such as the Balkans and the Middle East. Ktrimi991 (talk) 23:35, 23 September 2018 (UTC)
 * Support experienced admin who looks at the bigger picture. Son of Kolachi (talk) 05:52, 24 September 2018 (UTC)
 * Oppose. It surprises me to see this application from Ivanvector here because of the kind of stunts he's been pulling of late. His conduct in recent months has been totally appalling. As per my reading of the oppose comments above and my personal observation: he has a) frequently feuded with a number of editors, b) acquitted (or attempted to acquit) long term abusers such as NadirAli and Nauriya by engaging in falsification of facts, and proxy abusing socks like StLouis2, c) protected pages and acted as an SPI admin clerk where he's WP:INVOLVED, d) frequently engaged in WP:NPA by casting aspersions on fellow editors (for example, as mentioned by User:Desmay, calling User:DBigXray an "obvious meatpuppet" without even a shred of evidence). All of this has happened before this appointment process began. These are significant misconduct issues, and make me believe that this candidate cannot be trusted with a permission like CheckUser at all. Finally, their own comments here gives the impression that they are far from having a fair understanding about policies such as clean start and wheel warring. Bharatiya  29  18:25, 25 September 2018 (UTC)
 * Support as entirely trustworthy. The opposing comments look to me like grudges that happen when an admin has been around long enough. --Tryptofish (talk) 19:02, 25 September 2018 (UTC)
 * Support: IvanVector has the necessary expertise and, as Son of Kolachi points out, the "bigger picture" view that is critical to the CU role. I think they would make an excellent CU. Waggie (talk) 03:21, 26 September 2018 (UTC)*Support RH cosm   (talk)  09:40, 27 September 2018 (UTC)
 * Support: IvanVector as a CU would be very helpful to the project so this should be a no-brainer. --regentspark (comment) 11:48, 27 September 2018 (UTC)
 * Support per everyone above - No concerns here, Trusted and competent. – Davey 2010 Talk 21:00, 28 September 2018 (UTC)

SQL (CU)

 * Nomination statement


 * Hi, I’m SQL. I’ve been an Administrator since 2007, and I am applying for Checkuser. I’m the developer of tools such as ISP Rangefinder, IPCheck, IPRange, and the original developer behind ACC, as well as an early usercompare tool on the old toolserver. I am a regular at CAT:RFU, UTRS, and one of the primary patrolling admins at WP:OPP. I would primarily use the tool at UTRS, and in reviewing unblocks on-wiki.

Standard questions for all candidates

 * 1) Please describe any relevant on-Wiki experience you have for this role.
 * In addition to the tools I've written mentioned above, I'm probably the most active admin at WP:OPP, and have a lot of experience testing / blocking proxies / webhosts. I'm also active at UTRS, and in reviewing unblocks on-wiki.
 * 1) Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
 * In the past I've worked in varying tiers doing cable internet tech support, as well as NOC / internal support.
 * 1) Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
 * No

Questions for this candidate

 * Earlier this year, you were involved in a discussion about Whaledad, a Dutch Wikipedia CU. While I do not dispute that Whaledad made a mistake, you called him a "clown". Do you think this will affect your ability to collaborate with CheckUsers from other wikis, even those you disagree with, while representing the English Wikipedia? --Rschen7754 03:11, 18 September 2018 (UTC)
 * I was irritated, and should have walked away and come back later. I'm typically blunt, but I don't believe that this would hinder cross-wiki communication. SQL Query me!  04:42, 19 September 2018 (UTC)
 * Which SPI cases do you think exemplify your work in this area? GABgab 14:32, 18 September 2018 (UTC)

Comments

 * Comments may also be submitted to the Arbitration Committee privately by emailing . Please note that the candidate will be provided the opportunity to respond to a paraphrased version of any emailed comments; the sender's name will not be provided.


 * Clear technical competence. Thoughtful and collaborative. I believe he'll be a good addition to the CheckUser team. –Ammarpad (talk) 05:10, 18 September 2018 (UTC)
 * Support No concern Hhkohh (talk) 05:14, 18 September 2018 (UTC)


 * Oppose I am concerned about this discussion where you had an argument with about whether it was appropriate to turn 's talk page access off after being blocked. The discussion got very heated and in my opinion you dug your heels in unnecessarily, advising Laser brain not to wheel war (when he would not be doing so by simply reversing your action after consensus) and later saying "But hey, let's not let facts get in the way of a good story, right?" This leads me to think you will checkuser block people liberally and be unwilling to consider appeals. Ritchie333</b> <sup style="color:#7F007F">(talk)  <sup style="color:#7F007F">(cont)  10:11, 18 September 2018 (UTC)
 * Oppose. This editor is obviously technically competent but my one interaction with them was unimpressive. At this thread, they removed an editor's TPA while and I were in the middle of challenging the basis for the request. Per WP:ADMINACCT, SQL was unable to provide a policy basis for their action other than saying it's the "norm" or suggesting such actions are discretionary (they are not). SQL went on to falsely menace me about wheel-warring. When I suggested I would undo the action if there was no policy basis for it, SQL suggested I would be wheel-warring. This is not correct. In addition to resisting challenges to their admin actions, I believe SQL is representative of a generally poor trend of shoot-first-ask-questions-later in our admin corps, and should not gain additional rights. -- Laser brain   (talk)  13:23, 18 September 2018 (UTC)
 * Oppose - No SPI experience. Beyond My Ken (talk) 01:50, 19 September 2018 (UTC)
 * Support Technically competent; no major *-ups in the past; highly active at opp, and with outstanding skills that will be a plus at the CU desk. Lourdes  10:13, 19 September 2018 (UTC)
 * Comment - As an uninvolved admin who spent a lot of time assessing the above-mentioned conflict in great detail, I thought SQL's conduct was reasonable throughout and it's unfair to use a legitimate dispute as ammunition against someone after the fact. The quote Ritchie provides above might be out-of-line if it were not an evidence-based refutation of a false accusation. It was a "grey area" in terms of policy; SQL was attempting straightforward enforcement of a block where a user was continuing to edit via proxy using their talk page. They felt this was an uncontroversial, common sense action, and a substantial percentage of the community agreed with their assessment. There is no clear policy guidance either way and the community was essentially split down the middle as to whether it valid in this case. Discussion lasted little over a day, and then SQL undid their own action in consideration of the opposition. Had SQL not overturned their own action, it would not have been overturned via my assessment of that discussion.  𝖘 𝔴𝔞𝔯𝔪  𝔛 17:38, 19 September 2018 (UTC)
 * Support Technical knowledge would be a benefit to the functionaries team. I agree with Swarm's assessment of SQL's actions in that dispute. Best, Barkeep49 (talk) 18:33, 19 September 2018 (UTC)
 * Oppose per Ritchie, LB and lack of relevant experience. -- Begoon 23:10, 19 September 2018 (UTC)
 * Neutral On one hand the comment on Meta was probably block-worthy for being a personal attack, but then that is the only comment I've seen after some digging. I am not convinced by the AN incident to oppose - it has too much recentism and politics involved in it to be convincing to me. On the other hand, all I see of relevant experience/rationale is OPP/unblock requests, and that is only somewhat relevant. So, neutral. --Rschen7754 05:56, 20 September 2018 (UTC)
 * Oppose — Per and . Regards, SshibumXZ (talk · contribs). 09:09, 20 September 2018 (UTC)
 * Neutral per Laserbrain. —SerialNumber54129  paranoia / cheap sh*t room 11:04, 23 September 2018 (UTC)
 * Oppose I was unimpressed by their conduct in the IHTS thread and it gives me concern about how they would handle future disputes. Pawnkingthree (talk) 14:24, 23 September 2018 (UTC)
 * Support per Ritchie333 and Laser brain. Nihlus  15:12, 24 September 2018 (UTC)
 * Neutral per Nihlus. &#x222F; <b style="color:#070">WBG</b> converse 13:54, 25 September 2018 (UTC)
 * Neutral while noting that there are concerns expressed by people with good judgment. --Tryptofish (talk) 19:03, 25 September 2018 (UTC)
 * Support: In their many years of service to Wikipedia, SQL has demonstrated excellent technical expertise, good judgement, and a willingness to handle difficult and complex situations, which CUs are often asked to do. I'm aware of the recent situation with IHTS, and remind folks that everyone is human, even administrators, CUs, and Arbs and I think Swarm addressed it quite well above. Waggie (talk) 03:04, 26 September 2018 (UTC)
 * Support. The only issue brought up here is the IHTS TP access one where the nominee perhaps misjudged the heat of arguments and acted too early, thus turning half of those debating against him/her (and this now reflects here). Other than that single issue, considering over a decade of administering, I see no compelling reasons not to trust them with extra tools. — kashmīrī  <sup style="font-family:Candara; color:#80F;">TALK  09:35, 26 September 2018 (UTC)
 * Support RH cosm   (talk)  09:42, 27 September 2018 (UTC)
 * Support Big fan, long time coming. It'd be great to have someone with his technical expertise on the CU roster. Drewmutt ( ^ᴥ^ ) talk  19:20, 28 September 2018 (UTC)
 * Oppose per Ritchie & BMK. – Davey 2010 Talk 21:01, 28 September 2018 (UTC)

Stwalkerster (CU)

 * Nomination statement


 * I would like to respectfully nominate myself for an open CheckUser position. I've been an admin for a decade, and while I'm not active around SPI itself, I have been involved in a few recent sockpuppetry cases (Imeghana17, Realmissvoodoo), and I am fairly active around ACC (since around June 2007), and I'm also on IRC. I am acutely aware that the CheckUser queue within the ACC tool has been fairly backlogged for quite some time, and there are simply not enough CheckUsers who look in on ACC. As a software developer, I have the technical background necessary to use the CU tool, and as one of the primary developers of the ACC tool, I'm also acutely aware of the privacy policy and both what it requires and what is generally good practice in addition.

Standard questions for all candidates

 * 1) Please describe any relevant on-Wiki experience you have for this role.
 * I have been the primary developer of the WP:ACC tool for many years (after taking over from SQL), and involved with ACC before the current tool was originally written. I've also been an admin here for a decade.
 * 1) Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
 * I'm a software developer by trade, having done a fair amount of network-capable application development. As such, I'm familiar with the HTTP protocol and the various headers which come with it including User-Agent and X-Forwarded-For. I'm also familiar with IP addressing, CIDR prefixes, etc as a result of sysadmin work I've done.
 * 1) Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
 * I do not hold advanced permissions anywhere of note (On testwiki I hold +crat) . I do not currently have access to OTRS; I formerly had access to info-en a number of years ago.

Questions for this candidate

 * You're not someone I'm familiar with, so I did a little digging. From what I can tell, your main work is ensuring that BLPs always have a source confirming their death. So I'm a little confused as to what you need checkuser for? <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  15:42, 18 September 2018 (UTC)
 * You are correct that most of my recent on-wiki edits are in that area, it's something I set up an recent changes monitoring tool for. However, this is not my main work; as I mentioned above, I'm mostly involved with the WP:ACC tool. Unfortunately, due to the sensitive nature of the data in the tool, the logs of activity within the tool are restricted to tool users only, so I understand how you may not be able to see the activity there.
 * In case you are unaware, we get a significant number of account requests from users who are blocked (mostly thanks to the standard block templates redirecting users to ACC), and in cases where there is a possibility that the intended target of a more serious IP-based block is requesting the account, or where an IP-based block is marked as a checkuser block, those requests must be handled by a checkuser. There are currently only 2-3 checkusers who occasionally look in on the ACC tool, and as such backlogs of requests which need checkuser attention grow and sit for weeks or months. Currently, there are 152 of these requests in waiting input from a checkuser, the oldest of which has been open for around four weeks. The ACC tool does need more active checkusers, and given my familiarity with the ACC process and technical knowledge, it makes sense for me to step up and tackle (and attempt to stay on top of) a backlog which needs attention. stwalkerster (talk) 16:53, 18 September 2018 (UTC)
 * You have made 406 edits since October 2012 till March 2018 as per this including 52 edits last year in 2017.Where you active  in the WP:ACC or in other areas during this period ?Pharaoh of the Wizards (talk) 20:38, 18 September 2018 (UTC)
 * I was fairly inactive from October 2012 through early 2016 due to other commitments at the time. I did remain semi-active doing development work for ACC during that time, but it was from early 2016 onwards, my activity has risen again, again centred around ACC both from a request handling perspective and a development/administration perspective. stwalkerster (talk) 20:04, 19 September 2018 (UTC)

Comments

 * Comments may also be submitted to the Arbitration Committee privately by emailing . Please note that the candidate will be provided the opportunity to respond to a paraphrased version of any emailed comments; the sender's name will not be provided.


 * Support Although they have been almost dead in their recent overall participation in community issues (or I may be absolutely wrong in this assessment), the editor has handled private information for innumerable years and presumably subscribes to or is the primary author of the zero tolerance philosophy for mistakes at ACC. No issues. Lourdes  11:24, 18 September 2018 (UTC)
 * Support - largely per Lourdes, can be trusted with access to nonpublic info and has a clear use-case for the bit. -- Ajraddatz (talk) 14:46, 18 September 2018 (UTC)
 * Support: Clear need of right and can be trusted with non-public info. Also the ACC CU queue have no regular CU, so it frequently gets backlogged, which also leads to ~2-3 months of waiting time for an account and could be very discouraging for new editor. &#8208;&#8208;1997kB (talk) 15:41, 18 September 2018 (UTC)
 * Support Civil everywhere, and excellent answer to question; obvious need for CheckUser. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  17:14, 18 September 2018 (UTC)
 * Support Technically able and generally competent, good use case TNTPublic (talk) 17:36, 18 September 2018 (UTC)
 * Support Clear need outlined. Possesses the competence required. –Ammarpad (talk) 17:39, 18 September 2018 (UTC)
 * Support. Drmies (talk) 01:54, 19 September 2018 (UTC)
 * Support - per the supporters above. Beyond My Ken (talk) 01:59, 19 September 2018 (UTC)
 * Support long-term admin and while community involvement is on the lower side I see enough to be comfortable supporting. --Rschen7754 04:28, 19 September 2018 (UTC)
 * Support, yes, no concerns and a clear need. <u style="text-decoration:none;font:1.1em/1em Arial Black;letter-spacing:-0.09em"><u style="text-decoration:none;color:#38a">Fish +<u style="text-decoration:none;color:#B44">Karate 08:22, 19 September 2018 (UTC)
 * Support-Why not? &#x222F; <b style="color:#070">WBG</b> converse 13:14, 19 September 2018 (UTC)
 * Support Has a good reason to request the tool. Natureium (talk) 14:19, 19 September 2018 (UTC)
 * Support Can be trusted, and has a reason. Vermont (talk) 16:18, 19 September 2018 (UTC)
 * Support Trusted, competent user who has a demonstrated record of respectful interaction with all.  Operator873 talk connect  17:51, 19 September 2018 (UTC)
 * Support - Has a convincing need.  𝖘 𝔴𝔞𝔯𝔪  𝔛 17:56, 19 September 2018 (UTC)
 * Support Will benefit the project in this role. Best, Barkeep49 (talk) 18:30, 19 September 2018 (UTC)
 * Support Ms Sarah Welch (talk) 21:47, 19 September 2018 (UTC)
 * Support -- Begoon 23:11, 19 September 2018 (UTC)
 * Support Seems reasonable. desmay (talk) 02:23, 20 September 2018 (UTC)
 * Support - I have worked with the candidate quite a bit at ACC and I understand how useful this tool would be to him. --  Dane <b style="color: #00AC1D;">talk </b> 03:51, 20 September 2018 (UTC)
 * Support — Per ; demonstrated need for the bit. Regards, SshibumXZ (talk · contribs). 09:09, 20 September 2018 (UTC)
 * Support Good answer. A Civil and reasonable editor handling admin duties for a long time who is ready to discuss his actions. No reason not to trust him with the tools.-- D Big X ray ᗙ  12:45, 20 September 2018 (UTC)
 * Support Has a clear and convincing need for the tool, no concerns. Simplexity22 (talk) 23:29, 20 September 2018 (UTC)
 * Clearly demonstrated need. Seems like a good candidate. — Godsy (TALK<sub style="margin-left:-2.0ex;"> CONT ) 04:51, 21 September 2018 (UTC)
 * Support I have no concerns and he has demonstrated a need for CU. -- The SandDoctor Talk 04:29, 23 September 2018 (UTC)
 * Support per humbleness :) Neutral, leaning oppose Insufficient activity to necessitate advanced permissions ultra, and thus no need of the extra tools. Not opposing on consideration of the candidate's content creation skills. —SerialNumber54129  paranoia / cheap sh*t room 11:13, 23 September 2018 (UTC)
 * I normally try and keep my head out of what i'm going to be voting on in the near future, but I need to clear up some factual inaccuracies. His 100 ACC actions dates back only to 2018-08-15. Their last 500 ACC actions dates back to 2018-05-17. The candidate may be to humble to mention the activity there. Since we have 198 current CU requests sitting at ACC, spanning back to 2018-08-22, and I've gone back to school, I'd like to get any help I can. They have sufficient recent experience in the area where it is most needed. -- Amanda  (aka DQ) 22:36, 23 September 2018 (UTC)
 * Thank you,, for drawing my attention to that: I have adjusted my vote accordingly. —SerialNumber54129  paranoia / cheap sh*t room 07:59, 24 September 2018 (UTC)


 * Neutral, leaning oppose. With all due respect to the nominee, I don't recall ever coming them across in discussions, despite me spending considerable time in SPI, ARV, AN, etc., and my edit count and account age comparable with theirs. So, I am not sure whether their level of admin activity jusitfies extra tools at this moment. — kashmīrī  <sup style="font-family:Candara; color:#80F;">TALK  14:55, 23 September 2018 (UTC)
 * Support per DQ is quite active at ACC and so has a clear need, no concerns Galobtter (pingó mió) 08:15, 24 September 2018 (UTC)
 * Neutral. A good rationale for requesting the permission, but not much recent experience with the editing community. On a broader note, I think I'm seeing a pattern where highly active candidates attract opposes because they've been highly visible, whereas a candidate who has had little attention, as here, gets easy supports. --Tryptofish (talk) 19:07, 25 September 2018 (UTC)
 * Support: Having worked with stwalkerster at ACC and on IRC for several years, I'm convinced that their technical ability is far above the threshold required for competently and correctly performing CU operations and evaluating the results. They also clearly understand the responsibility involved, and possess the demeanor and respect for the community and have the ability to respectfully work with others to resolve concerns. There's no question in my mind that they are an excellent candidate. Waggie (talk) 03:07, 26 September 2018 (UTC)
 * Support: clear need for the tool. <u style="font:1.1em/1em Arial Black"><u style="color:#7f2ed1">Flooded <u style="color:#bfa6d8"> with them <u style="color:#7f2ed1">hundreds 09:48, 26 September 2018 (UTC)
 * Support RH cosm   (talk)  09:43, 27 September 2018 (UTC)
 * Support Can be trusted with the CU tool . Kpg  jhp  jm  16:47, 28 September 2018 (UTC)
 * Support Would be great to have another CU resource active in IRC, beyond competent for the tool belt. Drewmutt ( ^ᴥ^ ) talk  19:23, 28 September 2018 (UTC)
 * Support - no concerns here. – Davey 2010 Talk 21:34, 28 September 2018 (UTC)

TonyBallioni (CU)

 * Nomination statement


 * Hi, I'm Tony. I've been an admin for about a year now, and I'm applying for CheckUser because I think I have experience in several areas that would be beneficial to the CheckUser team. In terms of how this tool would be useful to me: I have pretty broad experience with SPI, COIN/UPE work, UTRS, and several LTAs where SPI doesn't work as well so it requires private coordination with CheckUsers. I'm also involved across the Wikimedia movement as a global renamer, and in the past, I have worked pretty closely with sysops, CheckUsers, and stewards from other projects to combat cross-wiki socking and LTAs from various language groups, and having the CheckUser tool would be helpful in dealing with cross-wiki issues on large  a project that many en.wiki users aren't as familiar with.In terms of what I bring to the table: I've been one of the more active admins at SPI in the last year, and I am behaviorally familiar with many UPE farms and LTAs, and because of my work at COIN, I also am aware of the privacy guidelines in many of these difficult cases and am familiar with the guidelines for when running a CheckUser would be appropriate. I'm familiar with range blocks and with VPNs/open proxies, and feel I would be competent to operate the technical aspects of the CheckUser tool and would be able to learn anything that I'm not initially familiar with.

Standard questions for all candidates

 * 1) Please describe any relevant on-Wiki experience you have for this role.
 * As I noted in my nomination, I've been pretty active at SPI in the past year, and I typically handle a wide variety of cases there: from the undeclared paid editing farms to you more conventional vandals and POV-pushers. I also have experience dealing with several LTA cases where it's normal just to go to a CheckUser directly or block if it is a DUCK case. One of the other areas I hope to work in if appointed a CheckUser is unblocks and in particular UTRS. I'm fairly active in the UTRS system, and there can often be a delay in processing those CU requests. TonyBallioni (talk) 00:39, 18 September 2018 (UTC)
 * 1) Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
 * My background is in a sales-related industry which is part of the reason that I've been so involved in working on undeclared paid advertising front: I'm normally good at spotting it and also pretty good at telling when something is more of a good faith fan of something than an advertiser. Because there are a lot of these types of cases at SPI/WP:COIN and being handled by individual CheckUsers, I think this experience would be an asset to the CheckUser team from a behavioral standpoint. TonyBallioni (talk) 00:39, 18 September 2018 (UTC)
 * 1) Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
 * I'm a global renamer and also an OTRS member. I'm less active on OTRS than I used to be, but I have access to info-en and several of its subfeeds, including the quality one, as well as the permissions feed. TonyBallioni (talk) 00:39, 18 September 2018 (UTC)

Questions for this candidate

 * CheckUsers are often requested to cooperate with CheckUsers from other wikis as well as with stewards. While understandably you were upset over being accidentally blocked for being a spambot on nlwikiquote, you asked him to resign and threatened to get WMF involved. Later, you gave a reply to a steward that was in my opinion, dismissive and confrontational. Do you think this will affect your ability to collaborate with CheckUsers from other wikis or stewards, even those you disagree with? --Rschen7754 04:04, 18 September 2018 (UTC)
 * Hi,, I was actually was anticipating this question, and I'm happy to have the opportunity to address it. First, re: Whaledad, I was particularly mad there as it was apparent that he had blocked without even looking on the user page, he had issued no notification, and had cut off all avenues of appeal. For those who aren't aware, a global renamer being blocked on a project has the potential to cause technical glitches, and when I'd looked at his block log, this appeared to be the norm for him for other accounts, and I considered that not to be appropriate as an admin on a Wikimedia project. I discussed it with Trijnstel, who a steward who is a native Dutch speaker, and without revealing too much of our conversation, she told me that I should raise the issue with the Dutch ArbCom, I did. They disagreed and said some of the things that I had been told were true were not: I'm not a Dutch speaker and am not involved with the issues on that Wiki, so I was just glad they heard me. I've moved on: the local process played out, and I'm respectful of it.Re Matiia: while I 100% agree with you that many en users give a bad taste to others, I think it's also important to note that the respect needs to go both ways. I've had interactions with him in the past that caused me to read that statement as him trying to influence a local process on a project I have personally gotten the impression he isn't that fond of and without knowing many of the reasons why we do it the way we do. I don't think that is appropriate for a steward, especially at a discussion that is supposed to be about individual suitability for the role, which is why I spoke up. Looking back, I should have waited and commented more on these issues at the steward confirmations, because my commenting further distracted the discussion from being about 331dot and also wasn't fair to Matiia since he was honestly speaking his mind, and it shouldn't have been a forum where he might have had to be on the defense.As a whole, I think I have pretty good relations with the steward team. I have worked very closely with Alaa in the past on multiple cross-wiki socking issues between en.wiki and ar.wiki and helping with that is one of the areas that I do hope to further contribute. Speaking on a personal level, he's probably the single Wikimedian I trust most on any project, and I wish more admins on this project had stronger ties with users in other language groups, because I think it would be very enriching to the entire movement.I consider myself part of the global Wikimedia movement, and am very proud of my place in it, and am very respectful of the difference between different projects, having friends on many different home wikis. As a member of that global community, I will raise my voice when I have a concern, and I can be blunt when I think there is an issue, sometimes to a fault, but in the end, we are all here with the same goal in mind, and working for more interproject cooperation is a necessity and I strive for it whenever possible and would do the same as a CU, and to answer more directly your question: I'm willing to work with anyone to better any project, even if I disagree with them very strongly. I'm sorry to you and to others for the long reply, but I wanted to address it thoroughly because this is something that I care quite a lot about and I think it deserved a full explanation. TonyBallioni (talk) 04:15, 18 September 2018 (UTC)
 * Tony, you only succeeded your RfA last year, why did you apply for CU now? Hhkohh (talk) 05:10, 18 September 2018 (UTC)
 * I'd been encouraged by several users I respect to put my name forward. I also feel that I'm familiar enough with a lot of the sock farms and LTAs that we deal with regularly that I could be net-positive to the CU team. TonyBallioni (talk) 05:16, 18 September 2018 (UTC)
 * Do you have any comments as to your handling of this SPI? That, several users have perceived (and commented) that post-RFA, you've increasingly shifted to an authoritarian attitude (something I do not concur with), do you believe that such a feeling in the community coupled with incidents like this might adversely affect the confidence of the community in your actions, executed in the garb of a CU/functionary?  On a side-note, from my reminisces of his now-deleted user-page and other activities including editing-similarities, I think the duck-call was within the upper margin of discretion.   &#x222F; <b style="color:#070">WBG</b> converse 15:14, 21 September 2018 (UTC)
 * , thanks for the question. In regards to that incident, it was almost a year ago and was when I was new to patrolling SPI. I did not see enough to block on behavior alone, and administrators are responsible and accountable for their blocks as individuals, even if acting on the advice of an SPI clerk. Admins can and do regularly close SPIs without CU or clerk input, and in this case, I didn’t block because I didn’t see it and I try to be conservative when acting at SPI. I should have talked to the clerk in question first rather than closing unilaterally. I misunderstood the process at the time, but I don’t think I’ve ever done that again.Re: the authoritarian bit, I’ll admit the statements have me taken aback a bit: I’ve always been willing to make difficult blocks, but I’m also equally willing to put them up for community review and discuss it with anyone who thinks I’m wrong: I have always held strong opinions and been willing to express them, this was discussed pretty heavily at my RfA, but I am always open to other views and I think any examination of my record here shows that finding compromises and working solutions to problems on this project is my preference compared to enforcing my view of what should happen. Needless to say, if this many people perceive me in this way, then they all can’t be wrong, and I do need to take that into account and change my approach. In terms of community confidence, if I were still appointed I would do my best to show to those who opposed this that I am not the person they fear I am. My talk page is always open, now and in the future, for anyone to raise issues with me, either general or specific, and I will strive to address them. TonyBallioni (talk) 15:06, 22 September 2018 (UTC)
 * Thanks.I am satisfied enough:-) &#x222F; <b style="color:#070">WBG</b> converse 08:15, 23 September 2018 (UTC)
 * You were vehemently coercing and threatening someone to resign from CheckUser here just because he blocked you by mistake in a project you never edited before then (although no single evidence of CheckUser abuse was presented). Now, how do you think of your behavior on that page? –Ammarpad (talk) 16:41, 21 September 2018 (UTC)
 * Ammarpad, I think I was too forceful then, but I also think there were a lot of issues with that block and the circumstances surrounding it that caused me to be that way: it was made on a wiki that had no functioning process for reviewing whether admin actions were compatible with community trust and where the user in question was for the most part the only active admin, and a quick review of his block log showed that he regularly appears to block no edit accounts without notice and with talk page access and email access disabled: I found that practice objectionable because I think it is counter to the aims of WMF wikis, and yes, I got mad about it because it bothers me when people who hold advanced permissions do it in a way that has the potential to harm people who can’t speak up because they don’t understand our processes. The block was actually discovered by a nl.wp ArbCom member, before he was appointed a CheckUser, and seeing the appointment really concerned me because having looked at the block logs on nl.wikiquote, I did think there was a chance that he would overuse the new tool, even on users from other projects who have just one logged action on a Dutch project.That isn’t a justification for my being so forceful, but it does explain my state of mind and how I was thinking. As to how I view my conduct now, I should have either dropped the issue completely after being unblocked or just politely raised the concerns that similar blocks could also effect other good faith users from other projects in the future. It would have made the same point, and possibly actually had some impact rather than turning someone off. TonyBallioni (talk) 15:06, 22 September 2018 (UTC)

Comments

 * Comments may also be submitted to the Arbitration Committee privately by emailing . Please note that the candidate will be provided the opportunity to respond to a paraphrased version of any emailed comments; the sender's name will not be provided.


 * Support – TonyBallioni is one of those administrators whose judgment I trust instinctively. Although he is not always right (no one is always right), what he has to say will always make you think very carefully about your own position on the matter. As for the checkuser tool specifically, Tony would be a clear net positive. He's got a really good eye for the behavior patterns of a number of our LTAs, he can almost always be found in the IRC channel #wikipedia-en-admins, and he has a broad range of experience as an administrator at SPI. Finally, TonyBallioni is one of the most personable administrators I've had the pleasure to interact with on Wikipedia. I think the checkuser team will find that he'll be one of their most cherished colleagues. Mz7 (talk) 01:24, 18 September 2018 (UTC)
 * Support. I have had several interactions with Tony on a number of different issues. I haven't always agreed with him, but I have always found him reasonable and collaborative. Also, his knowledge of policy is as good as that of anyone I know. No hesitation here: if he's willing to do some of the messiest but most necessary work on Wikipedia, let him have at it. Vanamonde (talk) 04:21, 18 September 2018 (UTC)
 * Support – While I would have perhaps preferred Tony to run for the arbcom, given his wide contributions and the perceivable trust the community holds in him, this is a bit that, given to him, would benefit the project significantly. Lourdes  11:21, 18 September 2018 (UTC)
 * Support - I've interacted with Tony in many project areas including SPI, and have always found him to be insightful and careful, but always willing to tackle difficult situations. No concerns. Ivanvector (Talk/Edits) 12:22, 18 September 2018 (UTC)
 * Support — Not a jerk, has a clue — python coder (talk &#124; contribs) 12:27, 18 September 2018 (UTC)
 * Support Although Tony is a young admin, but I am confident that Tony will not abuse this tool Hhkohh (talk) 12:31, 18 September 2018 (UTC)
 * Oppose Although he has done a lot of good thing to me, but sometimes he is too excited and too young to have checkuser tool Hhkohh (talk) 14:33, 18 September 2018 (UTC)
 * (The young and excited Tony is doing good things to you, is he? Well, I'm mad now; he's never offered to do these good things to me. Lourdes  05:29, 20 September 2018 (UTC))


 * Oppose Tony has performed a number of blocks that I found to be quite bad, jumped into AE quickly after saying he was not interested in working there, and has caused at least one long standing contributor to leave the project. Mr Ernie (talk) 12:38, 18 September 2018 (UTC)
 * Those of us less familiar with the incident in question would find it helpful if you provided some diffs here. Vanamonde (talk) 14:31, 18 September 2018 (UTC)
 * Mr Ernie can correct me if I am wrong, but in regards to AE, I think they are probably referring to . Alex Shih (talk) 14:51, 18 September 2018 (UTC)
 * Vanamonde, he's likely referring to one of my first AE actions regarding . I'll be the first to admit that it was a mistake. I was a new admins who was trying to contain the disruption surrounding the Roy Moore issue last year. For those who aren't familiar, it was concerning a US political candidate who there were allegations of personal relationships with minors. I tried for a very narrowly construed topic ban as to allow a good content contributor more reign. What I saw as an obvious TBAN violation they did not, it went to AN on appeal, where it was upheld, but it went to ARCA, and after feedback from arbs I withdrew it. You can see it at WP:AELOG/2018 if you want background. In all honesty, it was one of the more enlightening moments of my time as an admin: I saw the negative impacts it had, how divisive it was, and how things that are clear to one person are not always clear to others. Tl;dr, it made me realize how powerful TBANs were and I'm generally reluctant to use them now unless absolutely necessary.I think if you look at AELOG, the only other TBAN I have placed since was on, and that was updating the previous one from a Trump ban that another admin had placed to a standard AP2 ban in part because I felt it was unclear and that it would be easier for him not to cross the line on it going forward. TonyBallioni (talk) 14:54, 18 September 2018 (UTC)
 * I see, thanks for the links. I do remember this sanction, I did not realise DHeyward retired afterwards. I haven't investigated the circumstances in detail, but given that Tony himself is saying it was a mistake, this isn't going to change my opinion. Vanamonde (talk) 15:02, 18 September 2018 (UTC)
 * Yes this is what I was referring to. I'm really bad at finding diffs, especially ones from ARCA that get archived to an old Arb case, which are themselves very difficult to find. Mr Ernie (talk) 20:14, 19 September 2018 (UTC)
 * No problem. By the way,, which were the blocks that you found to be "quite bad"? Although I am not aware of any bad blocks made by the candidate, I think this is an important point; CheckUsers will be making many controversial blocks that cannot be overturned easily, so any relevant history in regards to blocks will be a good point of reference. Alex Shih (talk) 20:49, 19 September 2018 (UTC)
 * Mainly the concern stems from the block of User:Elisa.rolle. In particular, the discussion here is what concerns me. raised points that I do not think were adequately answered. In the case of C/U blocks, editors normally don't have any chance to rebut like in this case where the block was reduced to a month. Mr Ernie (talk) 15:10, 20 September 2018 (UTC) - reping  due to typo... Mr Ernie (talk) 15:11, 20 September 2018 (UTC)


 * Oppose: Now, I am certain will receive both CU and OS, as they are fully qualified in terms of temperament, skillset and experience; under normal circumstances I would see no reason to oppose; however, with the feeling that community feedback receives relatively few weight when it comes to the final decision, I would like to voice my dissent based on two minor concerns that are more philosophical than practical.I also find the candidate's comment at Meta to be dismissive and confrontational; and I find the explanation here to be less than satisfactory: telling Matiia, who raised a legitimate concern, that they should probably not comment on the processes for a project that they aren't familiar with, because of your own established opinion towards their suitability as steward not completely relating to the request, does not exactly reflect the sentiment of being part of the global Wikimedia movement, in my opinion. This is not about whether or not one usually works well with the steward team; to me this is more about how this very example can be reflective on what enwiki administrators probably should not do when interacting with editors from other projects, for the very reasons that have already been stated.Moving on to the second concern: I don't really have any problem with an candidate saying that they are not interested in working at AE, and then become one of the more active administrators working in that area. Our interests can change, and that is perfectly fine and should be applauded. What I am slightly concerned about is the incremental shift in mindset from the candidate ever since they became an administrator in October 2017. Perhaps this is the natural consequence of being one of the more active administrators overall for the past year, but I find the increasing amount of bureaucratic tone of voice to be counter-productive; the functionaries team needs to be better connected with the community, and I don't see the need for another member that could be perceived as authoritative and inflexible. TL;DR: My main fear is that the candidate would step further away from the community if they become a member of the functionaries team, based on my observation on the pattern of their adminship and subsequent work. Alex Shih (talk) 13:50, 18 September 2018 (UTC)
 * (An absolutely honest and model feedback, which should probably be benchmarked. Lourdes  15:47, 18 September 2018 (UTC))


 * Support I have worked with Tony in a number of areas, not least putting forward some very successful RfA candidates, and I was particularly impressed at the tact and diplomacy he showed when managing, who has been blocked several times (since indefinitely and retired). The reasons for the block were backed up with policy, but ultimately this was a good faith editor who tried her best to write and improve the encyclopedia. Tony withstood the yelling from all sides and held his cool, and he was reasonable to consider a shortening of the block. I am confident I will be able to review CU blocks in the same amicable manner. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  15:22, 18 September 2018 (UTC)
 * Support Generally competent with a reasonable understanding of the tool - nothing which can't be learnt, and Tony has proven able to pick up a new role and roll with it. He's also the type to stop, think, and ask questions before diving in and hoping for the best TNTPublic (talk) 17:39, 18 September 2018 (UTC)
 * Oppose—Evidence of victim-blaming and supporting corrupt admin behaviour makes this a foolhardy proposition. <b style="color:darkgreen">Tony</b> (talk)  01:06, 19 September 2018 (UTC)
 * Support - Trusted admin with excellent judgment. Beyond My Ken (talk) 01:52, 19 September 2018 (UTC)
 * Support. Ah yes, the old "supporting corrupt admin behaviour": well, since apparently I do that too it makes sense I would support him. Also, Tony has clue and technical skill. Now, as for the other stuff--I am not impressed by the Meta comments but it's funny how frequently and easily those cultures clash. The conversation with Whaledad, yeah, I think Alex Shih has a point when he says that Tony sometimes stands on his stripes, as the Dutch would say, but it's worth noting that it was indeed a ridiculous block, and Tony wasn't the only one criticizing that admin. Drmies (talk) 02:03, 19 September 2018 (UTC)
 * Support This one is a close call as Tony has made some mistakes in interactions with other wikis, but I don't think it's anything that can't be overcome, and somewhat understandable since he was blocked, after all; furthermore something should be said for the candidate's willingness to go onto other wikis at all. Overall I think it would be a net positive. However, I would caution Tony to tread even more carefully in this regard should they be appointed, since functionaries do often impact other wikis' perception of the English Wikipedia. --Rschen7754 04:40, 19 September 2018 (UTC)
 * Support-Per Tony1. &#x222F; <b style="color:#070">WBG</b> converse 13:18, 19 September 2018 (UTC)
 * Reaffirming it, in light of Tony's reply to my question whilst concuring with Swarm and Mz7. &#x222F; <b style="color:#070">WBG</b> converse 08:15, 23 September 2018 (UTC)


 * Support Would be useful. Vermont (talk) 16:20, 19 September 2018 (UTC)
 * Support per Drmies and Ritchie333 and over 7100 admin actions in over 1 year.Pharaoh of the Wizards (talk) 16:57, 19 September 2018 (UTC)
 * Oppose I respect TonyBallioni, but I think put it into words well at the end of the second part of his comment. He's become more authoritarian than I'm comfortable with. Natureium (talk) 17:16, 19 September 2018 (UTC)
 * Oppose per partisan behavior on divise threads at the dramaboards. That's ok for an admin, but for advanced permissions someone more neutral is better. --Pudeo (talk) 17:59, 19 September 2018 (UTC)
 * This is the only one I really wish to address other than the one above since there were links asked for: I think the only blocks I have made that could be anywhere close to "partisan" are that I have blocked holocaust deniers and actual Nazis (and I think this has been my only interaction with you there.) These have all been endorsed by the community or other admins on review, and I don't think that it is bad thing for a functionary to take a strong stance against neo-Nazism. TonyBallioni (talk) 19:44, 19 September 2018 (UTC)
 * I don't know what Pudeo is alluding to; but if your reference is right, he may be referring to your unilateral and 'partisan' (as said by Pudeo) blocking of the editor while community discussion was going on at ANI, a discussion in which you had already participated. Do note that while I opposed your action initially, I later realized you were probably right in your actions. Perhaps Pudeo can fill in on this issue if they desire. Lourdes  05:43, 20 September 2018 (UTC)
 * I think he’s likely referring to this block, but the one you’re referring to is here. I’m fine with the community looking at both and I stand behind both. TonyBallioni (talk) 12:29, 20 September 2018 (UTC)
 * Fine if you wouldn't use CU tools on "suspected Nazis" in a more lax way disregarding due process because of your moral highground and strong stance. Yeah, neo-Nazis exist (IIRC there's one prominent Stormfront neo-Nazi who has done LTA sockpuppeting), but at times it seems like a McCarthyist hunt with people going back to see edits from 2011 for possible sympathies, or indeffing users who've had "Kek" in their username since they registered in 2015. Let's just say that there are more calm and objective ways to oppose extremists, and then there are more frantic and activist ways to do that. --Pudeo (talk) 13:55, 20 September 2018 (UTC)
 * Of course I wouldn’t use the CU tool based on that unless there was actual reason to believe socking existed. That would be a strong violation of the privacy policy and arguably the local CheckUser policy depending on the circumstances. Re: the 2011 edits, I don’t think I’ve ever looked that far back when making a block for anything. I also wouldn’t block for “Kek” unless there was other evidence the user was being disruptive as that can have a few meanings (I also generally oppose username policy blocks unless it is 100% clear that the user is acting disruptively.) A user simply being disruptive is not grounds for a CheckUser to be run unless there is reason to suspect abuse of multiple accounts. TonyBallioni (talk) 14:17, 20 September 2018 (UTC)
 * Oppose I respect TonyBallioni both as an editor and as an admin. I have learned from him. What I have not seen is the friendly user that was described at his RfA. Instead I have seen a well versed, thoughtful, active admin and editor who seems convinced enough of the correctness of their opinions that he can sometimes lack the humility and openness to other points of view I would hope to see from a Checkuser member of the functionaries team. Best, Barkeep49 (talk) 18:27, 19 September 2018 (UTC)
 * Oppose per Alex, and my own uneasiness about attitude post RFA. -- Begoon 23:13, 19 September 2018 (UTC)
 * Oppose — Per 's concerns about Tony's seemingly authoritarian attitude. Regards, SshibumXZ (talk · contribs). 09:09, 20 September 2018 (UTC); edited 09:10, 20 September 2018 (UTC).
 * Oppose - Needs more time as an administrator. Shows signs of being too aggressive for the advanced tools. Carrite (talk) 17:16, 20 September 2018 (UTC)
 * Oppose: Seems to be obsessed with power and authority vaunting. Second, no known clear evidence of on-wiki technical competence neither off-wiki as evidenced by answer to question number two. Activities at AE (where they declared they'd no interest while in RfA) and UPE made him to develop over suspicion habit, which then coupled with his apparent overconfidence may lead to big errors slipping under the radar due to CU privilege. There's likelihood of CheckUser actions leading to avoidable harm to the project in an attempt to reduce harm by a candidate like this.  –Ammarpad (talk) 18:40, 20 September 2018 (UTC)
 * To be fair, as to Trung, I didn't see where he had any misplaced overconfidence.He was supported by Arjaddatz (a quite respected steward), SA13Bro et al and that Trung was blocked for those very reasons, the entire following episode is weird.And, he immediately backed down once the role of ElectCom was pointed out. The outcome reverse-drama thay followed, in the thread, has got more to do with the fact that most of their bureaucrats and authority-figures have an immense liking for political correctness and a lack of common sense. Post reply addition:--And, that it is often a free-zone for those who have been shown the door from en-wiki. &#x222F; <b style="color:#070">WBG</b> converse 05:22, 22 September 2018 (UTC)
 * My friend. You don't see it, doesn't mean it's not there. Arjaddatz, as a Steward and long term Meta-Wiki user has greater moral, technical and authoritative responsibility to remove the comment, ask yourself why he didn't?, is it that he was afraid or was he being naive?. Why no one else but someone who later confessed that he'd overacted and he was newbie to Meta?. You then claim "he immediately backed down" after he was lectured about ElectCom. I see that, what else can he do? In this SPI, there's another example of both overconfidence and know-it-all comportment which deals directly with CheckUser and he has also backed down after proven wrong manifestly. Consistently exhibiting poor attitude and then apologizing after proven wrong is not a quality I want in a functionary. As a matter of fact, in that case, had it been TonyBallioni were a CheckUser at the time, then wouldn't have been able to contest the close and that means those socks (clear harm to Wikipedia) wouldn't have been blocked and would've been here with us. This further substantiate what I said in my earlier comment "there's likelihood of CheckUser actions leading to avoidable harm to the project in an attempt to reduce harm by a candidate like this."
 * Also your comment will have been better without the veiled insult to Meta "authority-figures" and bureaucrats, we are not discussing them here. –Ammarpad (talk) 07:43, 22 September 2018 (UTC)
 * I will leave a note that my entire point, in the above note, was solely w.r.t to the meta-incident and I did not find his behavior to be any problematic. But, obviously perceptions can vary:-) That I was the first user to invoke Binamra's SPI over here, I am obviously not much pleased as to that particular case. &#x222F; <b style="color:#070">WBG</b> converse 08:05, 22 September 2018 (UTC)
 * To put this in perspective, I have seen a whole lot worse from currently sitting functionaries on Meta. --Rschen7754 05:34, 22 September 2018 (UTC)
 * Really? I am baffled to see this from you Rschen7754. Existing of bad sitting functionaries on Meta is not justification to have one on English Wikipedia. Follow the right process to remove those "bad functionaries" there on Meta and let's not start even having them here on English Wikipedia else we end up like Meta (in your thought). Hopefully, now on EnWiki, we don't have any bad functionary, so let's not give room to be used as an example like the way you're using Meta now. –Ammarpad (talk) 07:43, 22 September 2018 (UTC)
 * No, I mean English Wikipedia functionaries behaving badly on Meta. --Rschen7754 07:45, 22 September 2018 (UTC)
 * Doesn't change much and my comment still stands. Follow the right process to remove/sanction those "English Wikipedia functionaries behaving badly on Meta" but don't use their perceived (subpar)behavior and justify adding someone who'll go on Meta and elsewhere and be threatening their functionaries with "I will seek your removal as an office action if need be" even though the user being threatened didn't abuse his CheckUser tools. In a saner climes, when we've something bad we try to reduce/mitigate it not add to make it worse. –Ammarpad (talk) 08:17, 22 September 2018 (UTC)
 * I’ll reply to this one because I think I can clarify my intent (not arguing, just shedding light): it appeared that there was a rough consensus to remove the Trung comments. Since it looked like there was, I acted upon it, not knowing about ElectCom because that was when I was new to meta. I reverted once it was clear people had issues with it. TonyBallioni (talk) 15:22, 22 September 2018 (UTC)


 * Oppose Terribly self-important, generally unpleasant know-it-all approach. Still wet behind the ears as an admin, yet quickly trying to collect all possible hats. Plus what Alex Shih writes above. Widr (talk) 19:39, 20 September 2018 (UTC)
 * Oppose basically per Mr. Ernie. I am aware of at least one bad block, and there have potentially been others based on comments above. In regard to temperament: Administrators are not community managers but rather community janitors; they do not direct the community but rather cleanup things as directed by the community. I think TonyBalloni would do well to remember that. That aside, I have a good working relationship with them but I feel it is due to much more compromise from my side than theirs. — Godsy (TALK<sub style="margin-left:-2.0ex;"> CONT ) 20:19, 20 September 2018 (UTC)
 * Oppose per the opposers above regarding the authoritarian attitude, proven by their recent comment on my talk page unnecessarily stating they'd "have no problem blocking" me despite me not doing anything to deserve such comment. I don't trust their judgment and think they would misuse the tools if given advanced permissions. <u style="font:1.1em/1em Arial Black"><u style="color:#7f2ed1">Flooded <u style="color:#bfa6d8"> with them <u style="color:#7f2ed1">hundreds 20:22, 20 September 2018 (UTC)
 * Oppose really does not inspire confidence in me. Unrelatedly, "For those who aren't aware, a global renamer being blocked on a project has the potential to cause technical glitches" isn't true AFAIK. Legoktm (talk) 07:19, 21 September 2018 (UTC)
 * Support Although some here are calling Tony "overconfident" or "authoritarian", my experience has been that he is a considerate guy who is willing to admit publicly on a noticeboard with tons of views that he was wrong and change positions after giving the concerns others had raised with him some thought. Sadly, this is really rare on wiki, and to me it speaks to the quality of his character as a contributor to the project. As for his other qualifications, I don't think they can be disputed.--Calthinus (talk) 20:54, 21 September 2018 (UTC)
 * Support - I've waiting to see if any legitimate issues would be brought up. None have, which is why I find it so unfortunate that Alex, who somehow thinks that his word doesn't carry weight, decided to explore his minor, "philosophical" concerns by opposing a candidate he felt was impeccably qualified, because some of his qualifiers such as "bureaucratic" or "authoritative and inflexible" have snowballed into a hard pile-on against Tony, including plenty of lovely, unsubstantiated accusations such as "supporting corrupt admin behaviour", "authoritarian", "partisan behavior", "attitude", "too aggressive", "obsessed with power and authority vaunting", "overconfidence", "self-important, generally unpleasant know-it-all approach", "trying to collect all possible hats", "authoritarian attitude", "think they would misuse the tools". Wow. Good show, everyone. I mean, look at all those diffs! That's a clear pattern of disruptive behavior, very conclusive and overwhelming, such strong evidence to support such strong accusations. Definitely not just a bunch of aspersions. Oh, and how nice that is ignoring Tony's perfectly reasonable clarification as to what he meant, and refuses to strike their misrepresentation of a comment they interpreted the wrong way. That's really special. /s I work alongside Tony on a regular basis, and the pile-on that's going on is not remotely a justified or accurate assessment of what kind of administrator Tony is. Tony is, though and through, a perfectly friendly and reasonable person, and a competent administrator with good judgment, who thoroughly helps the project and does his job well. He does not remotely deserve this level of personal attacks against his character. ( Swarm  ♠  talk ) 06:12, 22 September 2018 (UTC)
 * To be clear, I thought the way I did before Alex posted anything. I mentioned his comment only because I didn't know how best to state what I was thinking in a way that doesn't sound like "I just don't like him", because that isn't the case at all. Natureium (talk) 16:33, 22 September 2018 (UTC)
 * Yeah, I'm exceedingly disappointed with the tone of this discussion as well. I've interacted with Tony many times on IRC, and he's a friendly guy who is clearly here for the right reasons. When I asked him a few weeks ago whether he was going to go for checkuser, he said he wasn't really sure and was leaning against it. I was one of the users who pushed him towards getting it because I genuinely believe he would be a great help to Wikipedia with the tool. This is not at all a case of a young admin going power hungry, trying to collect all the hats. It's true that he is outspoken about his views when he thinks something isn't going right, but the Tony I'm familiar with does read your concerns and factors them into his thinking. Just the other day, at WT:INTADMIN, he asked me why I had re-opened a discusison I had closed, stating he was confused. After I replied with my reasoning, he responded in an open-minded manner. Mz7 (talk) 19:31, 22 September 2018 (UTC)
 * Well put - shit like this from people like Alex makes me wonder why I bother here. The pile-on bullshit is just the icing on the "what is wrong with Wikipedia" cake - TNT 💖 20:34, 22 September 2018 (UTC)
 * , you might want to re-consider your personal attack here. I offered an constructive opinion, and there is no basis for "shit like this from people like Alex". Alex Shih (talk) 22:40, 22 September 2018 (UTC)
 * I apologise if you took that as a personal attack - it isn't one. Perhaps now would be a good time to stop taking yourself so fucking seriously? - TNT 💖 22:45, 22 September 2018 (UTC)
 * I know that you and I are both frustrated that this isn’t going how we thought it would, but out of respect for Tony, I would suggest we tone this down. It is true that Tony is outspoken, and I guess he does give some editors the impression that he’s unwilling to reconsider his views. Now that he’s aware of this feedback, I’m sure it’ll be something he’ll think about moving forward. As I’ve stated, I don’t fully agree with this picture of Tony, but I would recommend following the path of least drama here. Mz7 (talk) 23:16, 22 September 2018 (UTC)
 * Second that. TNT, I can't picture you ever like what your above comment paints you as (I recall two years ago when I enquired why you hadn't run for the RfA, it was because you were – and are – absolutely calm in your disposition; do please not change that). Most warmly, Lourdes  23:31, 22 September 2018 (UTC)
 * Okay, and now we've got the civility police beating up on TNT, for speaking out against personal attacks and aspersions, while ignoring said personal attacks and aspersions immediately above. Great work, guys! ( Swarm ♠  talk ) 01:47, 23 September 2018 (UTC)
 * It's nothing like that Swarm. Both Mz7 and I support Tony's candidacy. If you believe Alex's statement is a personal attack on Tony, and everyone commenting here should subscribe to that viewpoint or be trouted, it's a narrow viewpoint that you should reconsider. Thanks, Lourdes  07:21, 23 September 2018 (UTC)
 * You claim that I made "lovely" and "unsubstantiated accusations." That's not true. 1. I don't consider them lovely, rather bitter. Truth is always bitter and hard to say; that's why some who tried to say it and at the same time want remain politically correct ended up with more than what they bargained for. 2. They are not unsubstantiated; they're. What I said is evident and further shown with extant diffs and I am not the only one who believe these diffs count for that. –Ammarpad (talk) 14:15, 23 September 2018 (UTC)


 * Support I doubt that Tony would abuse CU and see its addition to his proverbial toolset as a benefit to the project. -- The SandDoctor Talk 04:26, 23 September 2018 (UTC)
 * Support- &#x222F; <b style="color:#070">WBG</b> converse 08:15, 23 September 2018 (UTC)
 * Support per and the opposes generally.  —SerialNumber54129  paranoia / cheap sh*t room 11:21, 23 September 2018 (UTC)
 * Undecided. I somehow don't see much difference between "blocked by bot" and "blocked by TonyBallioni". It's as if a tank was rolling. Whereas I will always crave for human bureaucrats who are willing to read discussions and carefully balance all the opinions. But I am aware that we do not always get what we dream of. Hence, neutral. — kashmīrī  <sup style="font-family:Candara; color:#80F;">TALK  12:27, 23 September 2018 (UTC)
 *  Oppose  I do hold particular reservations about hat-collecting here, but this does not directly affect whether the candidate fits the job description. Instead, I am concerned about the sideways answer to the mandatory question asking about technical expertise. I've been behind the scenes are used a proper CU interface before (one mandatory requirement ought to be the ability to cope with large quantities of browser tabs), and the frontend is easy enough, but if one needs to dig deep, then they out to have some experience in networking matters. Tony does not answer the question, and gives no indication of technical competence. talk to ! dave 13:12, 23 September 2018 (UTC)
 * , if I might shed some light on that: we were asked to answer that question in private to ArbCom, and the public question I read as being about professional background: mine is not technical, and I would never claim it. Re: if I have the skill set: I consider myself to have a decent understanding of networking, IPv4/IPv6, geolocation, ranges, open proxies, and the technical limitations of the CheckUser tool in this regard. I’m comfortable making range blocks and will and have done them when needed in the past. I hope that sheds light on the answer. Sorry it was not meant to be evasive: I’d just answered that bit of the mandatory questions on the questionnaire ArbCom sends out, where it is listed separately than the professional background question. TonyBallioni (talk) 13:28, 23 September 2018 (UTC)
 * Fine, I'll support. talk to ! dave 14:29, 25 September 2018 (UTC)


 * Oppose I would like to see more experience as an admin before this right is granted. I would probably support in a year’s time. Pawnkingthree (talk) 14:43, 23 September 2018 (UTC)
 * For what it's worth, some of our most helpful checkusers, like NinjaRobotPirate and There'sNoTime, became checkusers after having been administrators for less than one year. Mz7 (talk) 21:19, 23 September 2018 (UTC)
 * Oppose per Widr and the hat-collecting. Nihlus  05:30, 24 September 2018 (UTC)
 * , I will re-ask about how you concluded that Tony was hat-collecting? Best, &#x222F; <b style="color:#070">WBG</b> converse 13:56, 25 September 2018 (UTC)
 * So you think Tony's got a "Terribly self-important, generally unpleasant know-it-all approach" and agree with someone who blocked everyone at my local library for two years. Nice. How on earth did you conclude that Tony was hat-collecting? <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  15:05, 24 September 2018 (UTC)
 * Yet another irrelevant commentary on someone else in a topic which has nothing to do with them. Widr is not the subject of this discussion; if you have something against him, might I suggest you handle it elsewhere. Nihlus  15:18, 24 September 2018 (UTC)
 * If you've got a problem with me Nihlus, take it to my talk page, or email, or better still over a pint in a pub. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  16:15, 24 September 2018 (UTC)
 * Given that your comment was a direct response to mine, my response here was appropriate. Nihlus  20:13, 24 September 2018 (UTC)


 * Support: trustworthy, dedicated contributor and admin; no concerns about granting the right. --K.e.coffman (talk) 05:35, 25 September 2018 (UTC)
 * Support, strongly. Exactly the right kind of user to be trusted with this permission. I'm really disappointed by all the opposes that I'm seeing, because I know from first-hand experience that this is an excellent candidate. --Tryptofish (talk) 19:09, 25 September 2018 (UTC)
 * Support: TonyBallioni and myself don't always see eye to eye on a variety of topics, but I strongly believe they have the technical expertise, demeanor, and respect for the responsibility that this position entails. They have an excellent understanding of policies, guidelines, and the importance of collaboration. Please accept this candidate. In reading through the discussion here, I think it mildly amusing that some of the opposes look like they should have Support in front of them, instead of Oppose. Waggie (talk) 03:10, 26 September 2018 (UTC)
 * Oppose per other opposers in general (seemingly authoritarian attitude, hat-collecting, etc.) <b style="color:#090">Semi</b><b style="color:#099">Hypercube</b> ✎ 22:30, 26 September 2018 (UTC)
 * Oppose approaches situations looking for trouble and then imposes his immutable viewpoint. Stephen 06:46, 27 September 2018 (UTC)
 * Support RH cosm   (talk)  09:44, 27 September 2018 (UTC)
 * Support as per everyone above - Trusted, clueful and competent admin who would make a great Checkuser, Easy support. – Davey 2010 Talk 21:39, 28 September 2018 (UTC)

Oshwah (CU)

 * Nomination statement


 * I am applying for the CheckUser and Oversight permissions to extend my participation with Wikipedia in order to protect the privacy of users and put a stop to disruption. I'll be available to help with processing requests that I see go unanswered on IRC, as well as help with the backlog at SPI and ACC. I've been an administrator for two years, and have been consistently active and available to help with requests as well as urgent matters on IRC and other communication methods. If you have any questions, please do not hesitate to ask and I'll be happy to answer them.

Standard questions for all candidates

 * 1) Please describe any relevant on-Wiki experience you have for this role.
 * My time has been mostly spent in recent changes patrolling and attempting to mentor and help new users on Wikipedia. I patrol recent changes and revert vandalism, respond to instances of long-term abuse, username violations, blatant sock puppetry, page protection requests, and (occasionally) AFD, AN3, and ANI. I'm also an ACC Tool Administrator on WP:ACC, and assist with processing account creation requests, as well as helping tool users with difficult or complex cases. I'm also an SPI clerk in training with DOrD and should hopefully be finished with the training soon - so far, I feel that it has gone very well and the processes and additional responsibilities that come with being an SPI clerk don't seem very difficult. I'm also highly active on IRC and I respond to requests for assistance and input from other users, and I respond to emergencies such as LTA activity, threats, blocking requests, revision deletion requests, and I make sure that the proper functionaries and channels are notified immediately depending on the issue.
 * 1) Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
 * My user page explains the extent of my background in a nutshell - I've grown up around computers and my IT-related experience goes very far back. I performed computer and network administration throughout my youth while in school, and held jobs in IT-related areas ever since. I have a BS in Computer Software Engineering Technology and a Minor in Applied Mathematics. I have extensive IPv4 and IPv6 experience that I actively use during my daily tasks at my current job, including networking, traffic routing, VPN, encryption, and security. I also have basic and advanced certification with Dell SonicWall firewalls and have written packet sniffing, ARP, and ICMP software GUIs and tools completely by myself using C++, Win32, and the WinPcap library.
 * 1) Do you hold advanced permissions (checkuser, oversight, bureaucrat, steward) on this or other WMF projects? If so, please list them. Also, do you have OTRS permissions? If so, to which queues?
 * I am an active ACC tool administrator. I don't have OTRS permissions, but that of course can change no problem if this is an issue.

Questions for this candidate

 * I guess I'll ask about the elephant in the room. Last year, you applied for both CU and OS, but were not granted the rights. What has changed about your application this year? (A few disclosures: sometimes unsuccessful candidates are not given specifics as to why their application was not successful, sometimes the outcomes of public votes differ from ArbCom appointment processes, and there has been no successful candidate for the exact same rights who has failed a previous ArbCom appointment process).
 * I believe that I've had time to grow into my role as an Administrator since the last application period. At the time, I was a new Administrator and I believe that this was the reason I was not granted the rights. I believe that since then, I've had time to mature and grow into the role and hence my judgment and use of the tools has more of a track record to be looked into.


 * Specifically for this right: why did you apply before completing your SPI clerk trainee period? --Rschen7754 02:58, 18 September 2018 (UTC)
 * I applied for the user rights in order to further my ability to assist with stopping sock puppetry, LTA activity, and disruption to the project. Many CUs were not clerks before they were appointed for the role; I consider it something that helps with overall experience.


 * Please could you explain why you have blocked the United States House of Representatives for a week, and have you informed the Wikimedia Foundation of this block? <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  20:02, 28 September 2018 (UTC)

Comments

 * Comments may also be submitted to the Arbitration Committee privately by emailing . Please note that the candidate will be provided the opportunity to respond to a paraphrased version of any emailed comments; the sender's name will not be provided.


 * Oppose I hope you can complete SPI clerk training first before you gain CU right Hhkohh (talk) 05:15, 18 September 2018 (UTC)
 * But most of our best checkusers were not SPI clerks before becoming checkusers. Why should this be necessary for Oshwah specifically? In fact, Ivanvector is the only candidate on this page who is a full SPI clerk; just being a trainee with sysop rights already puts Oshwah ahead of the pack. Oshwah clearly has administrative experience working at SPI, which I think you should take into consideration. Mz7 (talk) 07:51, 18 September 2018 (UTC)
 * I think he should gain more experience during training, I hope he can finish his SPI training as early as possible. If he reapplies after training, I think he will be an excellent Checkuser Hhkohh (talk) 10:30, 18 September 2018 (UTC)
 * Oppose I'm still not happy with Oshwah's "block first and ask questions later" attitude. I appreciate he does everything in good faith, but I think he needs to be dissuaded as far away as anything that could even be considered hat collecting as much as is possible. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  10:01, 18 September 2018 (UTC)
 * Support Anyone who contributes to the extent Oshwah has done and does, and anyone who can be the first (and perhaps only) administrator to reject my report at AIV, has his eyes placed wide open and is utmost trustworthy. All ok in my book. Lourdes  11:26, 18 September 2018 (UTC)
 * Oppose per Ritchie333 and per a few aggressive NLT blocks before discussion. Mr Ernie (talk) 12:43, 18 September 2018 (UTC)
 * Support He might still be training to be an SPI clerk, but as said some CheckUsers were never SPI clerks before applying. I think this candidate has enough dealing with LTA's and other sockpuppets to use this right responsibly. <b style="color:#090">Semi</b><b style="color:#099">Hypercube</b> ✎ 15:45, 18 September 2018 (UTC)
 * Support One of the most trustworthy administrators. He can always be trusted. And I will agree with . Knightrises10 (talk) 16:27, 18 September 2018 (UTC)
 * I think may not agree with you  ? <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk)  <sup style="color:#7F007F">(cont)  18:01, 18 September 2018 (UTC)
 * Tony1 threatened someone that if they reverted, "it becomes a legal issue". I don't know how anyone can possibly pretend that it wasn't a straightforward legal threat intended to have a chilling effect. As if anyone refers to AN/I as a "legal issue", or that it would be remotely reasonable to assume that's what someone who's threatening "legal issues" is referring to. Right. It's not even thinly veiled! No one just casually throws around a spectre of "legal issues" without understanding the meaning of the words they're using, particularly an old-school Wikipedian who damn well knows better. Of course, when you have 160k edits from 2005, a good admin should obviously understand that the words you say don't mean what they mean!  𝖘 𝔴𝔞𝔯𝔪  𝔛 06:01, 20 September 2018 (UTC)


 * Support Has done over 42000 admin actions since 2016 including over 24500 blocks overall can be fully trusted .Note that the user does Tough blocks .Pharaoh of the Wizards (talk) 21:33, 18 September 2018 (UTC)
 * Support - Oshwah has proven himself to be one of our finest admins, and one of the greatest assets to this project.  𝖘 𝔴𝔞𝔯𝔪  𝔛 00:19, 19 September 2018 (UTC)
 * Oppose—Oshwah does a lot of good, mostly routine work as an admin. But it's totally spoiled by the shoot-first attitude. After breaching site policy in a blocking, he then provides evidence that he is persuaded by herd-like backchannelled support by his admin friends that his breached either wasn't a breach or doesn't seem to matter. The very worst kind of admin to be given more power. I do not trust him. Absolutely not. <b style="color:darkgreen">Tony</b> (talk)  01:03, 19 September 2018 (UTC)
 * Support- Another trusted admin with good judgment. Beyond My Ken (talk) 01:53, 19 September 2018 (UTC)
 * Support We all make mistakes. He's a fine admin, active and has the competence required. Considering the number of blocks he made and overall unchallenged admin actions his mistakes appears infinitesimal and working in SPI clerking is not a pre-requisite for asking CU, making it ridiculous to hold them on this because they didn't finish so-called training. –Ammarpad (talk) 10:33, 19 September 2018 (UTC)
 * Support-per Ammarpad. &#x222F; <b style="color:#070">WBG</b> converse 13:20, 19 September 2018 (UTC)
 * Support More than enough experience, and is trustworthy and responsible enough to be a CheckUser. Vermont (talk) 16:21, 19 September 2018 (UTC)
 * Support Experienced, trustworthy, and personable... Oshwah has the prudent judgement and quick response desired for the position.  Operator873 talk connect  17:46, 19 September 2018 (UTC)
 * Support Experienced and competent admin. I highly trust him. Best, Barkeep49 (talk) 18:36, 19 September 2018 (UTC)
 * Weak Support Weak because the "shoot first, ask questions later" approach does still rear its head. I trust Oshwah to be aware of this and make efforts to control it. -- Begoon 23:17, 19 September 2018 (UTC)
 * Support - Oshwah is highly experienced and I have no concerns with him having the CU tool. I feel like he could benefit in his current Wikipedia tasks with the tool. --  Dane  <b style="color: #00AC1D;">talk </b> 03:45, 20 September 2018 (UTC)
 * Oppose — Per issues raised by and ; I would prefer for  to first complete his SPI clerk training. Notwithstanding that, I would like to thank Oshwah for performing the more tougher blocks on Wikipedia. Regards, SshibumXZ (talk · contribs). 09:09, 20 September 2018 (UTC); edited 12:34, 20 September 2018 (UTC) and 19:37, 20 September 2018 (UTC).
 * Ritchie333 and Tony1 are both raising single issue where Tony1 was blocked; so it's an issue not issues. And the block, although it was not unanimously approved it was not overturned either. I don't agree with it myself but at least some experienced administrators did like this. Later also Oshwah unblocked the user by himself . On your last point, we should know that  SPI clerk training in whole is not a pre-requisite for CU tools, so starting a training is a plus itself not otherwise. –Ammarpad (talk) 20:42, 20 September 2018 (UTC)
 * , oops, forgot to reply to you (don't have this page on my watchlist)! So, here goes nothing:—
 * As Ritchie333 wasn't talking about any block in particular and his language implied that the problem of Oshwah's blocking attitude spanned to multiple [controversial] blocks, I would like to assume that he meant more than was hence the usage of 'issues'. I apologise if it gave off the wrong impression to you.
 * While yes, being an SPI clerk is not a prerequisite for being a CU, applying for the bit whilst still training to be an SPI clerk does come off as hasty, to say the least.
 * Sidenote — If you reply to this message, please ping me, as I am not watching this page. Regards, SshibumXZ (talk · contribs). 20:01, 21 September 2018 (UTC)


 * Support - No concerns. They have one of the best temperaments of any Wikipedian I have come across. — Godsy (TALK<sub style="margin-left:-2.0ex;"> CONT ) 20:21, 20 September 2018 (UTC)
 * Support Oshwah has been the 9th most active admin since being granted the tools, including 26,085 (re)blocks. Given that, I don't find the few examples of mistaken blocks to be convincing of anything. Being an SPI clerk is not a prerequisite to becoming a CU, so I see starting training as a positive, not a negative. Oshwah is technically competent, trustworthy, and would make good use of the tool, IMO. Simplexity22 (talk) 00:42, 21 September 2018 (UTC)
 * This is a tough one. I don't put much stock into the fact that Oshwah was not successful in the last appointments round. (In the interests of disclosure, I did find myself in a similar category in the past, and did eventually serve as a functionary, but I'm not today by choice and am happily not.) Moreover, no editor has failed a previous CUOS appointment round and then run again for the same role as Oshwah has, so we have nothing to compare this candidacy to, and also no official statement as to why Oshwah failed. There is also no formal or informal requirement for SPI clerk training. There have been some successful appointed CUs that did not have it (and there were some not-so-successful ones that did not have it as well and could have really used it, I suppose). It is one of the vehicles where you show experience and rationale for using the tools, and the most relevant vehicle, but just one. As far as the issue about Tony1's block, I have my own theory about it that has not been expressed by others, but I do not think it appropriate to share here.
 * However, requesting both flags the year after, and bypassing some training time which could help in being a better CU, strikes me as a bit hasty. I am concerned that having both CU/OS at once may be too many responsibilities (and unfortunately, learning about the nasty side of Wikimedia) added at once, which might not be so great. So I would suggest granting only one flag at this time. --Rschen7754 05:48, 21 September 2018 (UTC)
 * I opposed Oshwah last year, and encouraged them to re-apply this year. Last year, Oshwah was a fairly new admin, largely untested, still making some rookie mistakes, still plenty of room for doubt as to whether they'd prove to be a competent admin. In the past year, Oshwah has utterly destroyed that doubt, and has become one of our most prolific, and one of our best, admins. In terms of technical ability, competence, activity level, good judgment, interpersonal skill, help with the backlog, assistance to others, Oshwah has become one of the greatest administrative assets to the project. Oshwah has proven himself to be capable of handling a monumental workload, without the slightest indications that he ever gets stressed out or loses his cool. I find it hard to believe that additional permissions will be too much for him&mdash;on the contrary, he seems like exactly the type of person who could handle it. Oshwah is also one of our most prolific vandal fighters, so it seems unrealistic to think that he would be fazed by the "nasty" side of Wikimedia, and is not already regularly exposed to the types of edits and editors he would be dealing with. ( Swarm ♠  talk ) 05:38, 22 September 2018 (UTC)
 * Support: A helpful, friendly editor and always willing to help. &#8208;&#8208;1997kB (talk) 14:43, 22 September 2018 (UTC)
 * Support as 1997kb said, Oshwah is an extremely helpful and friendly editor/administrator. Through his work with the project, CU would seem to be a natural extension and I see no reason to oppose. -- The SandDoctor Talk 04:27, 23 September 2018 (UTC)
 * Support. An overall positive experience with the nominee's activity. I sincerely appreciate the time they have dedicated to the project. They seem to get things right 99.99% of time. A few mistakes have happened - and have rightly been brought to light here - but I saw nothing that I could in all honesty call a killer to the nomination. — kashmīrī  <sup style="font-family:Candara; color:#80F;">TALK  12:19, 23 September 2018 (UTC)
 * Support Now is a good time for Oshwah to step up. talk to ! dave 13:02, 23 September 2018 (UTC)
 * Support per Swarm. Pawnkingthree (talk) 14:49, 23 September 2018 (UTC)
 * Support - A fine admin. Oshwah is always willing to listen, and to correct themselves on the rare occasion when they do make a mistake such as the Tony1 gung-ho block. Mr rnddude (talk) 23:25, 23 September 2018 (UTC)
 * Support A very polite and experienced admin who is able to solve difficult situations and learn new things. Working with Oshwah is a pleasure. Ktrimi991 (talk) 23:38, 23 September 2018 (UTC)
 * Support, no concerns. <u style="text-decoration:none;font:1.1em/1em Arial Black;letter-spacing:-0.09em"><u style="text-decoration:none;color:#38a">Fish +<u style="text-decoration:none;color:#B44">Karate 13:00, 24 September 2018 (UTC)
 * Support. Great admin, always open to discuss things, super kind and helpful, already involved with SPI, blocking LTAs... don't see why they would abuse the tools, seems like an obvious net positive for me.-- SkyGazer 512 <span style="background: linear-gradient(aqua, #d580ff);">Oh no, what did I do this time? 15:42, 24 September 2018 (UTC)
 * Support I trust Oshwah. Lepricavark (talk) 23:26, 24 September 2018 (UTC)
 * Support: No concerns about the tool being misused in any way; an excellent candidate. K.e.coffman (talk) 05:35, 25 September 2018 (UTC)
 * Support. I know exactly what Tony1 is talking about, but I'm also seeing someone who learns from mistakes and is very, very dedicated, and I believe can be trusted. --Tryptofish (talk) 19:13, 25 September 2018 (UTC)
 * Support: Having worked with Oshwah in many areas of the project, it is clear to me that they are strongly motivated to protect Wikipedia and has the clear technical competence to do it extremely well as a CU. They collaborate extremely well with others, even when in disagreement, and clearly have the demeanor and respect for the community to be deserving of the responsibility. When I was working with Oshwah to get started at ACC, Oshwah taught me how critical it is to respect the responsibility being handed to ACCers with the sensitive information handled there. Waggie (talk) 03:11, 26 September 2018 (UTC)
 * Support. The opposers are unconvincing, Oshwah is probably the only most active admin in the anti-vandalism area and the CU tool may assist him further in dealing with sockpuppets. His SPI traineeship with DoRD is a commendable headstart. <u style="font:1.1em/1em Arial Black"><u style="color:#7f2ed1">Flooded <u style="color:#bfa6d8"> with them <u style="color:#7f2ed1">hundreds 10:02, 26 September 2018 (UTC)
 * Support - All respect to the opposers, but I've always found Oshwah to be, if anything, helpful to a fault, but that's a fault that mostly just takes up his own time and patience. I have no doubt he has the required technical expertise.  G M G  <sup style="color:#000;font-family:Impact">talk  23:08, 26 September 2018 (UTC)
 * Support RH cosm   (talk)  09:45, 27 September 2018 (UTC)
 * Support would make anti vandal work easy for everyone, really. <b style="color:#060">💵Money💵emoji💵</b> 💸 15:25, 27 September 2018 (UTC)
 * Support Oshwah would make a good CU, but he should be a bit careful with his blocks as pointed out by Ritchie333 especially the one involving Tony1 . Kpg  jhp  jm  16:53, 28 September 2018 (UTC)
 * Oppose per Ritchie, Mistakes can and do happen with normal blocking (like the case with Tony and now like the case with the Congress blocking) but I feel with CU there is no room for mistakes and I'm afraid mistakes will happen I guess so regrettably I have to Oppose, We all make mistakes it happens but a lot of care has to be taken with CU, Anyway oppose. – Davey 2010 Talk 21:47, 28 September 2018 (UTC)