HelloAnnyong

HelloAnnyong (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Nomination statement (250 words max.)

Hey. I'm HelloAnnyong, and I'm offering my assistance to the project as a checkuser.

I've been active as an editor since early 2007, and have been an administrator since September 2010. I've been a sockpuppet investigations clerk for roughly a year now, and in that time have become one of the most active clerks. I've looked at and made judgments on hundreds of cases using both checkuser data and behavioral evidence. As such, I've got quite a bit of experience in analyzing edit patterns, working with rangeblocks and IP geolocation, and so on. I've worked with the checkusers extensively and understand what sort of information the checkuser tool can provide. Additionally I've been involved with the identification and handling of several of the larger and more prolific sockfarms.

I believe I've served my position of SPI clerk well, and will continue to do so in the future. As a checkuser I would be able to assist even further with cases, as well as help in other situations where sockpuppetry issues arise. In terms of availability, I'm around almost every day and can be contacted by email or on IRC.

Standard questions for all candidates

Please describe any relevant on-Wiki experience you have for this role.

A: I've been an SPI clerk for more than a year now. As one of the most active clerks there, I've handled hundreds of cases spanning all sorts of issues. I've evaluated behavioral evidence, handled checkuser results, and analyzed edit patterns, particularly when it comes to rather prolific sockfarms. I've built and blocked rangeblocks when circumstances have called for them.

Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.

A: I hold a bachelor's degree in computer science, and my day job is in that field. I've built several tools on the Toolserver and have extensive knowledge with IP, browsers and user agent strings, CIDR and IP ranges, and so on.

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?

A: I don't have advanced permissions elsewhere, and I'm not on OTRS.

Questions for this candidate

Being a new checkuser, would you be willing to help with the Checkuser backlog at WP:ACC as there are usually up to 6 requests waiting about 5 days+? -- DQ (t) (e) 19:29, 26 September 2011 (UTC)[reply]

A: Sure! I've never really been involved in that domain, but am absolutely willing to help out.

Would you be proactive in looking at the open cases at SPI to see if they could use a checkuser? -- DQ (t) (e) 19:29, 26 September 2011 (UTC)[reply]

A: Yes. I'm still plan to be as heavily involved with SPI as I am now - part of which is looking at open cases to see if a checkuser is warranted. In many cases, I've added a checkuser request when I feel a checkuser would be beneficial.

As a CheckUser, you will likely, from time to time, coordinate and communicate with the Stewards. What cross-wiki experience can you bring that can help out not only the Stewards, but editors, administrators, and CheckUsers on other wikis? –MuZemike 21:34, 26 September 2011 (UTC)[reply]

A: I've not really had much experience on other Wikis. I've done some editing on the Japanese Wikipedia and have been around on Commons for image uploads (and once dealing with a sockpuppeteer), but that's about it.

In your own words, what are the main differences between the WMF's CheckUser policy and the privacy policy? –MuZemike 21:34, 26 September 2011 (UTC)[reply]

A: The privacy policy explains what data is collected, who has access to that data, and under what circumstances that data can be released. By comparison, the checkuser policy explains under what circumstances the tool should be used, who has access to the tool itself, and what sort of data can be released. The privacy policy is more general in its description; the checkuser policy more clearly defines how the privacy policy applies to the CU tool.

Under what circumstances do the above policies give on the release of CheckUser data? –MuZemike 21:34, 26 September 2011 (UTC)[reply]

A: Checkuser data can be released when it is requested from law enforcement, for abuse complaints (including for reports made to ISPs), or when necessary to protect the Foundation. Other circumstances include when a user specifically states to release it, or for technical issues with bots.

Give some examples on when CheckUser requests of a sensitive nature or discovered CheckUser results of interest that would not be posted on-wiki. –MuZemike 21:34, 26 September 2011 (UTC)[reply]

A: I can recall a few times when Checkuser results were withheld due to surprising or unexpected results. For example, if a longterm editor or administrator comes up as possibly being involved, the results aren't divulged. Similarly, checkuser requests involving issues with administrators would probably not be released openly.

Now that Mr Wales has unblocked me, will you be marking for close any SPIs which come your way? 93.96.236.175 (talk) 10:02, 27 September 2011 (UTC)[reply]

Comments

Comments may also be submitted to the Arbitration Committee privately by emailing arbcom-en-blists.wikimedia.org

• HelloAnnyong has been active and displays consistent good judgment in the current role of SPI clerk. Seems like a fine candidate for CheckUser. --Orlady (talk) 14:07, 26 September 2011 (UTC)[reply]