Wikipedia:Arbitration Committee/CheckUser and Oversight/2011 CUOS appointments/CU/28bytes

28bytes[edit]

CheckUser candidate pages: 28bytes • AGK • Courcelles • Elockid • HelloAnnyong • Keegan • Kww • Mentifisto • WilliamH

Oversight candidate pages: Courcelles • Fluffernutter • WilliamH

Comment on the candidate below or by email • Community consultation period is now closed.

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

Nomination statement (250 words max.)

Hello, I am 28bytes, and I would like to help out as a CheckUser. I first began editing Wikipedia part-time in 2006 and became a full-time editor in 2010. I have been active on Wikipedia on at least 350 of the past 365 days; I expect to continue to be a highly-available editor, being on-wiki just about every day to respond to CheckUser requests.

My SPI experience has been "read-only" so far: I have not done any clerking there, but I do regularly read the investigations, and have developed a good sense of when and why a CheckUser is likely to accept or decline a request. I am very familiar with, and wholly supportive of, the CheckUser policy, the WMF privacy policy, and am well over 18 years of age and willing to identify to the Foundation.

Standard questions for all candidates[edit]

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

A: I became an administrator earlier this year, and prior to that served as a non-admin edit filter manager. Both roles require a degree of trust and discretion in that they provide the ability to access data (i.e. deleted content and private edit filters) not generally viewable, and I have taken very seriously the requirement to use such access responsibility, not disclosing any sensitive data without an extremely good reason. Similarly, I take very seriously the guidance outlined in the CheckUser and privacy policies as to how to balance the need to maintain an editor's privacy and the need to prevent disruption to the project.

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

A: My full-time job in the information systems industry requires a great deal of data analysis and pattern recognition. In particular, analysis of web server log data is a task I perform regularly that I believe will be helpful background for CheckUser tasks. I hold a bachelor's degree in information management and am currently pursuing a graduate degree.

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 do not.

Questions for this candidate[edit]

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:23, 26 September 2011 (UTC)[reply]

A: Yes, I would be willing to help out there. I have just requested access to the account creation request interface and will start to familiarize myself with it. 28bytes (talk) 21:13, 26 September 2011 (UTC)[reply]

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

A: Yes, I plan to check in on open SPI reports regularly. 28bytes (talk) 21:13, 26 September 2011 (UTC)[reply]

You say you have maintained a watch on SPI cases, can you tell the community something you have learned, and maybe comment on 2 cases before they are processed for CU weather you would endorse or decline? -- DQ (t) (e) 19:23, 26 September 2011 (UTC)[reply]

A: One key thing I've learned from watching SPI cases unfold is the importance of considering multiple explanations for an editor's apparent sockpuppetry. For example, I would decline this currently open SPI request: the request suggests that after the first account was blocked, the editor returned to edit sing the second account. However, since the blocking admin specifically suggested that the editor do that via the uw-softerblock template, there's really no need to investigate further. (At least in regard to sockpuppetry; COI issues may require a closer look.) On the other hand, I would accept this request; looking at the two accounts' contributions, the filer's suspicions are quite plausible, and the alternate explanation (that they are two separate people with an extremely coincidental interest in the same two pages) is not very compelling. 28bytes (talk) 21:13, 26 September 2011 (UTC)[reply]

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:22, 26 September 2011 (UTC)[reply]

A: I have a unified login and a very small number of contributions to other WMF projects, but my editing so far has been almost exclusively to en-wiki. However, I would be happy to assist in any cross-wiki investigations as needed, within the bounds of policy; for example by pointing stewards to relevant SPIs, AN/I threads, etc. on en-wiki. 28bytes (talk) 05:46, 27 September 2011 (UTC)[reply]

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

A: Both policies stress the importance of disseminating personally identifying data only to the degree it is required to prevent disruption to the project. The main difference is in the emphasis: the privacy policy discusses the collection and potential disclosure of personally identifiable user data in a way that gives site users "fair warning" regarding the collection and use of their data; the CheckUser policy gives CheckUsers guidance as to the technical capabilities of the tool, its purpose and its proper uses.

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

A: The privacy policy's "Policy on Release of Data" subsection, also included in the CheckUser policy and manual, specifies the 6 situations in which CheckUser data may be released: (1) in response to a subpoena; (2) with the user's permission; (3) disclosure to the WMF chair as part of an abuse investigation; (4) to aid in resolving certain technical issues; (5) to assist in targeting IP blocks or complaints to an ISP in response to vandalism or other disruption; and (6) "where it is reasonably necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public." The last of these is a bit of a catch-all, and would likely require a more detailed justification in practice. 28bytes (talk) 05:46, 27 September 2011 (UTC)[reply]

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:22, 26 September 2011 (UTC)[reply]

A: If a check turns up a link to an ArbCom-banned editor or a functionary abusing their position (e.g. an administrator or bureaucrat operating an abusive, undisclosed alternate account), it would be wise to pass the data to ArbCom privately rather than posting on-wiki. Another case would be if there is any reason to believe posting a result would cause harm to an editor: for example, if there were threats on-wiki or off-wiki towards the user being investigated, and confirming a link to the user's (multiple) accounts could lead to their personal identity being known; in such a case, it would be best to handle the matter privately. 28bytes (talk) 05:46, 27 September 2011 (UTC)[reply]

Checkuers are often relied on to determine whether someone is using anonymising proxies to perform their sockpuppetry. Please describe your general experience in this area. Please also describe, preferably with an example, how you (would have) suspected, identified, confirmed, and blocked a socking open proxy on Wikipedia. -- zzuuzz ^(talk) 17:14, 28 September 2011 (UTC)[reply]

A: I have not yet had the need to do much regarding proxies, so my experience is very light in that area. I know the basics of proxies, but I have not yet dug into the instructions and documentation that AGK refers to in his response below. I do tend to pick up such things fairly quickly, and would not be hesitant to consult with a more experienced CU to make sure my understanding of a situation was correct. 28bytes (talk) 17:05, 29 September 2011 (UTC)[reply]

Comments[edit]

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

28bytes' blocking log is one of the easier ones to review. While the blocks look generally OK, a couple of questionable block lengths on IP addresses, I can't help but think 41 blocks is not enough experience for an active checkuser. -- zzuuzz ^(talk) 17:14, 28 September 2011 (UTC)[reply]
Not yet. I would like to see more than "read only" participation at SPI. Jehochman ^Talk 07:21, 3 October 2011 (UTC)[reply]
I credit 28bytes with knowledge and understanding of policy, as they clearly demonstrate knowledge of policy, but the experience level shown in areas related to checkuser including the block log are concerning. -- DQ (t) (e) 17:36, 3 October 2011 (UTC)[reply]
I share the concerns expressed by Jehochman and DQ. T. Canens (talk) 04:11, 5 October 2011 (UTC)[reply]