557:
above) that all of them were borderline at the outset. So my position (if even called upon in such a case, which I doubt I would be as an AUSC member) would be to examine closely before digging in. Another similar example is the equally absurd cases where an editor is accused and simply laughs it off; I saw that recently as well. But the key is: many of them are laughed off initially - even though some turn out to actually be socks. So, wrapping up this section: borderline is along the lines of RfAs that are near the perceived discretionary range, or editors who show up in a debate that has the
641:) but rather a recognition that things do change around here; I note that at least two of my co-candidates have held or do hold these permissions already. Incidentally, I think much of the perception of inappropriate use of permission bits around here could be eliminated if we were to have defined terms for positions (not necessarily
705:
necessary, then normal channels should be followed. While one hopes that those with CU and OS privileges will already have displayed sufficient judgment that these situations do not occur, we do know that expectation is not always met. Having said all that, I believe there is community consensus that certain individuals
155:
real-world experience to handle both the technical aspects and the perceived stress, and I have the on-wiki experience to know what to do and when to do it. Thank you in advance for your consideration; questions and comments are welcome and will be given my sincere attention, as I do with all my efforts around here.
740:
I think an investigation would probably be warranted, and without being able to know specifics, I generally would lean toward holding CU/OS users to a higher standard. (In my own case, I'd rather have the bits removed pending the outcome of an investigation than continue under a cloud.) If there's no
549:
good candidates for CU, but I don't assume they automatically are just because several people are on the opposite side of a debate. This is similar to AIV; people sometimes report users at AIV without warning (or sufficient warning) just because they are upset about one edit; sometimes it's a content
533:
Credible evidence of socking, as in any number of discussions/debates such as AfD or RfA. "Credible" would include sudden appearance of opinions from infrequently-used accounts, or accounts that don't ordinarily frequent the particular venue. Often these are first tagged as single-purpose accounts or
522:
directly reference any existing cases. The reason for this is that I don't want to dig through earlier cases and second-guess someone, and there's no need to pick on individuals or previously decided cases. If there is a desire for me to comment on a specific case, please point to it and I can decide
366:
Generally, the purpose of a subcommittee is to serve a committee. I am standing for election to this subcommittee on the basis that its purpose is to be a check on the committee itself. "Active duty" use of these bits would defeat the purpose of the subcommittee, so I don't feel active duty use would
729:
Suppose a checkuser or oversighter is found to posses an undisclosed alternative account (not previously known of ArbCom), used recently, what do you think should be done w.r.t. their CU/OS accessĀ ? Do you think this deserves a AUSC investigation and would you support as auditor to open oneĀ ? If not
717:
As to your specific request to consider the dispute scenario, you are describing a specific situation of abuse which I think is highly inappropriate. If the evidence were incontrovertible, I'd likely support and/or recommend removal of the bits. I have a hard time imagining a situation in which it's
624:
Since the appointment is specifically for one year, I don't see any reason the mandate to retain the tools could extend beyond that. Further, if there were a credible, sufficient reason to have me removed prior, I like to think I'd have the good sense to request removal myself rather than go through
573:
Personal information provided by a user, especially one who is or appears to be a child, is completely appropriate to oversight. The argument can be made that since only admins can view deleted pages, that a deletion by itself is sufficient. However, there's a reason OS exists, and we unfortunately
455:
OK, so A1 is a bit humorous but maybe not feasible. The real answer is, of course, "it depends." I don't think the answer to such a situation necessarily rests on the shoulders of a single person, so my own personal response would likely be the same as it is for other things around here: do what is
592:
report, they might make OS requests to remove information. This might be medical or other personal information (lovers, sexual orientation, place of residence, prior legal troubles supposedly "sealed"). We can't remove everything that is (or might be) negative just because someone "knows" it isn't
499:
Would you give one example each of 1) appropriate use of CheckUser; 2) inappropriate use of CheckUser; 3) borderline use of CheckUser - and how you would view such borderline use; 4) appropriate use of
Oversight; 5) inappropriate use of Oversight; 6) borderline use of Oversight - and how you would
697:
Suppose a checkuser or oversighter performs an edit which needs to be oversighted, for having added nonpublic information, what do you think should be done w.r.t. their CU/OS accessĀ ? Do you think this deserves a AUSC investigation and would you support as auditor to open oneĀ ? If not in general,
599:
I'm pretty sure this is far less likely to occur. I personally feel like no harm is done by removing information that others might deem borderline. There's nothing that would stop it from being replaced if it were deemed appropriate after all. I don't know what harm is done by exercising a little
313:
software in a (non-public) system which requires me not only to have editing capability (and explain it to others), but also to be the administrator of the system. I won't pretend it is nearly as large or complex as
Knowledge (XXG), of course, but I do have some insight into how the system itself
556:
Obviously this is the toughest to determine in advance. I guess one example is the accusation that a well-respected user (possibly an admin) is either a sock or a sock-master. Yes, there have been some well-publicized cases these last few months - and I think (without getting specific as I said
154:
I believe I have shown the judgment, experience, and maturity necessary for these very sensitive tasks. Those who know my work will, I think, generally agree I'm a low-key, drama-free guy, although I suspect I've been around here long enough that there may be some who will disagree. I have the
704:
Same general answer applies; I don't think this position is going to make policy but rather perform duties requested of AUSC by ArbCom or WMF. I think any editor that makes this particular error in judgment should be alerted to it and an explanation requested. If some sanction were to become
538:
sufficient, but they're a start. Other clues that would lend further credibility would be if the accounts started showing up mid-way through a debate, if they all seemed to reference the same opinion ("...per XXXXX"), or if they showed a high correlation of page editing with the suspected
456:
appropriate, possibly after consultation with fellow subcommittee members, ArbCom itself, or AN/I. I don't think this subcommittee will set policy; nor do I think that being a member of this subcommittee would mean that all the other policies we follow are somehow thrown out the window.
224:
shows they are overwhelmingly still red. The ones that are no longer red links generally either now meet criteria for inclusion or are redirects elsewhere. In both areas, I think I've been able to very accurately enact community policies, and I hope to be able to do that in additional
459:
Anticipating any number of potential follow-up questions along the lines of "would that be enough?", I would say that I will certainly do my best to make sure that a response is early enough to avoid harm. I don't have any illusions that anyone around here can assure we
62:
220:- a new article). Regarding deletion, it is a "necessary evil" around here; in order to be considered a serious resource, we must have standards and they must be kept up. After more than 3500 deletions, I think I have a pretty good track record; a glance at my
709:
held to a higher standard, and therefore the leash, so to speak, should be shorter. Whether administrators fall into this category or not is a constant subject of debate; I don't think there is any question that bureaucrats, checkusers, or oversighters
56:
68:
44:
359:
Do you feel that members of the audit subcommittee should also be permitted to use the CU or OS bit for for "active duty" as would a regularly elected/appointed checkuserer or oversighter would in their regular course of duties? Why or why not?
74:
25:
380:
Do you agree to only use the checkuser/oversight bit as directly related to your duties as an audit subcommittee member or emergency situations where no other CU/OS is available (similar to Tznkai's 'personal policy' described
411:
cases for oversighting an edit rather than waiting for another oversighter to take action. I have run across only one edit that qualified, and the oversighter I contacted took the action I would have taken. This IAR note does
296:, log files, and tools for examining log files. I'm aware of the items that are generally logged with http requests and why they are important. I'm also aware that use of both Checkuser and Oversight permissions is
753:, and I guess I'd have to say my response would really depend on the specific situation. Still and all, I remain mindful that the purpose of the AUSC is to monitor and investigate, not necessarily to take action.
297:
690:. I view the committee as having a limited scope: when ArbCom calls, the committee answers. If ArbCom assigns one or more of those tasks as a regular part of its requests, then that's fine with me.
479:
As for my own actions specifically, when I get involved in disputes, I don't wield the admin bit as a blunt instrument, and I fully understand that for access to CU/OS, the community (and, indeed,
574:
are aware that admins can behave inappropriately just like anyone else, so the case where people post inappropriate information is an easy one. This can be about themselves or others, such as in
333:
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?
141:
615:
611:
628:
As far as I can tell, you will retain the tools once your term expires unless you request that they be removed. Will you request that they be removed once you are no longer on the AUSC? ā
395:
I agree that if appointed to the AUSC, I will only use the checkuser and oversight tools as directly related to duties as a member of the subcommittee or emergency situations. I expect
399:
to be defined by the
Arbitration Committee and/or the Wikimedia Foundation, in advance of any such action I take, and not by any single individual. I furthermore reserve the right to
21:
550:
dispute and sometimes the "vandal" is truly a new editor and the "vandalism" isn't obviously so. We have to have proper judgment as to what is appropriate; CU is the same way.
268:. I'm certainly "geeky" and experienced enough to understand the technology behind HTTP requests and how people might try to avoid detection. I'm very familiar with IP
232:
track closely to privacy issues of (and, alas, abuses by) both editors and functionaries, and I think that understanding and implementing CSD criteria (particularly
698:
then in which situationsĀ ? Please consider in particular a situation where the functionary was in dispute with the user concerned by the nonpublic information.
407:
directed by ArbCom if I feel such use contravenes existing policy, process, or common sense. Finally, it is not unreasonable to think that there may be
632:
513:
177:
545:
Any type of fishing expedition. These often show up as a user feeling like s/he is being "attacked" or tag-teamed. I'm not saying that such cases
567:
template at the top. Just because something unusual happens doesn't automatically mean it's the result of socking; more judgment must be applied.
665:
Do you think the following are part or should be part of the Audit
Subcommittee's written or unwritten responsibilities and would you do thoseĀ ?
327:
of others' actions regarding this technical information more so than be expected to generate it directly, but I'm not intimidated either way.
610:
Will you promise to resign your CU/OS rights once you are no longer on the AUSC? You would still be free to seek CU/OS permissions through
432:
in the
Checkuser/Suppression policies in a manner that go against the spirit of privacy and community well-being, and then use it to
17:
523:
at that point if it's appropriate (because, let's face it: there is the possibility of drama being created in re-hashing old stuff).
244:
real people, and that as a result, the way it is managed can have effects on all of those people: its editors, users, and subjects.
250:
Please outline, without breaching your personal privacy, what off-Wiki experience or technical expertise you have for this role.
600:
caution here. Having said that, I doubt my participation as an AUSC member would be likely to venture near any borderline cases.
673:
advise (through email) checkusers and oversighters on best practices, point out possible improvements in their use of the tools
428:
Thank you for stepping forward to volunteer for the role. Just one question. How would you deal with editors who attempt to
173:
105:
387:"While serving on the Audit Subcommittee, I will not use the CheckUser and Oversight tools with certain exceptions"
81:
117:
135:
123:
180:. The two areas I've spent the most time in are biographical articles and deletion of articles, particularly
637:
Yes, if they haven't been otherwise granted through some other means. That caveat isn't a sign of ambition (
111:
730:
in general, then in which situationsĀ ? Please distinguish in particular between situations where breach of
446:
433:
129:
676:
verify that CU, OS and privacy related matters are properly handled in the functionaries-en mailing list
534:"this account has made few or no other edits outside this discussion". I'm not saying that these are
480:
233:
670:
oversee the use of the oversight and checkuser tools by monitoring the checkuser and oversight logs
510:
289:
277:
265:
682:
I'm not big on creating policy on the fly. In general, I think all three of the things you list
442:
561:
484:
217:
742:
731:
429:
464:
harm, and I don't assert that such a guarantee is a reasonable thing to even attempt. But I
575:
408:
237:
229:
185:
181:
629:
588:
When a person claims that something is "wrong" because they know it differently than what
293:
281:
205:
99:
589:
209:
264:
guru of sorts for years, and I've also at times been a web-hosting provider using the
503:
213:
193:
285:
273:
201:
197:
189:
257:
269:
94:
323:
Having said all that, I expect that a member of the AUSC will be expected to
310:
240:) are also related. We need to be mindful that Knowledge (XXG) is literally
261:
166:
Please describe any relevant on-Wiki experience you have for this role.
618:
about this, although the proposal there goes beyond what I'm asking.)
579:
339:
I hold no permissions beyond those of an administrator on this wiki.
745:
found to have occurred, the answer is less clear; I think that the
375:
since the permission is granted with appointment to the committee.)
468:
think we can do our best as a community to establish, uphold, and
256:
I have long experience with data analysis in general. I've been a
228:
How do these relate to AUSC? I think the issues associated with
367:
be appropriate. (I want to be careful with the use of the word
625:
some ugly online drama. (I'm not expecting that, mind you.)
86:ā¢ Poll open 00:01 (UTC) 30 October to 23:59 8 November (UTC)
578:
another editor (which needn't specifically have to do with
309:
On a related note, in my professional life, I am using the
734:
clearly occurred, clearly did not occur, or is uncertain.
350:
Please put any questions you might have in this section.
638:
382:
221:
174:
active editor since early 2008 (registered since 2006)
722:without fairly immediate and serious consequences.
472:our policies and procedures such that they don't
749:of impropriety is sometimes just as bad as the
686:be within the purview of the AUSC, but are not
292:regarding web applications, public shared IPs,
184:. Some of the biographical articles fall under
518:I'm choosing to be generic in this answer and
8:
385:in the section prefixed with the statement
371:here, though; I'd rather think of it as
162:Standard questions for all candidates
149:Nomination statement (250 words max.)
18:Knowledge (XXG):Arbitration Committee
7:
714:fall into the short-leash category.
649:terms, or a combination of the two.
483:) expectation is the same, only on
300:, which strikes me as a good thing.
32:
645:but end points), enforced breaks
284:, Remote Desktop, multi-tasking,
208:, for example) and some do not (
1:
430:find or/and exploit loopholes
178:administrator since July 2008
633:08:26, 4 November 2009 (UTC)
514:12:03, 2 November 2009 (UTC)
346:Questions for this candidate
242:by, for, and (largely) about
423:Question from Mailer Diablo
775:
500:view such borderline use.
314:works from the inside out.
288:, the concept of "sticky"
605:Question from Emufarmers
487:. I take that seriously.
718:appropriate to violate
660:Questions from Cenarium
494:Question from SilkTork
403:to use the tools even
216:, and, just recently,
720:several core policies
639:far from it, actually
298:logged and documented
26:October 2009 election
481:Wikimedia Foundation
41:AUSC candidate pages
416:apply to checkuser.
354:Questions from Xeno
325:analyze the results
278:text-based browsing
612:the normal process
222:last 500 deletions
22:Audit Subcommittee
586:Inappropriate OS:
543:Inappropriate CU:
266:Apache web server
218:Allie Beth Martin
766:
590:reliable sources
566:
560:
512:
506:
397:directly related
145:
774:
773:
769:
768:
767:
765:
764:
763:
762:
571:Appropriate OS:
564:
558:
531:Appropriate CU:
504:
501:
348:
206:Richard Ravitch
164:
97:
89:
88:
80:To vote, click
64:KillerChihuahua
37:
30:
29:
28:
12:
11:
5:
772:
770:
761:
758:
757:
756:
755:
754:
726:
725:
724:
723:
715:
694:
693:
692:
691:
674:
671:
667:
666:
662:
661:
657:
656:
655:
654:
653:
652:
651:
650:
607:
606:
602:
601:
597:Borderline OS:
594:
583:
568:
554:Borderline CU:
551:
540:
527:
526:
525:
524:
496:
495:
491:
490:
489:
488:
477:
457:
450:
425:
424:
420:
419:
418:
417:
378:
377:
376:
356:
355:
347:
344:
343:
342:
341:
340:
331:
330:
329:
328:
318:
317:
316:
315:
304:
303:
302:
301:
248:
247:
246:
245:
226:
210:Farrah Fawcett
163:
160:
159:
158:
157:
156:
150:
91:
39:
38:
36:
33:
31:
15:
14:
13:
10:
9:
6:
4:
3:
2:
771:
759:
752:
748:
744:
739:
736:
735:
733:
728:
727:
721:
716:
713:
708:
703:
700:
699:
696:
695:
689:
685:
681:
678:
677:
675:
672:
669:
668:
664:
663:
659:
658:
648:
644:
640:
636:
635:
634:
631:
627:
626:
623:
620:
619:
617:
613:
609:
608:
604:
603:
598:
595:
591:
587:
584:
581:
577:
572:
569:
563:
555:
552:
548:
544:
541:
537:
536:automatically
532:
529:
528:
521:
517:
516:
515:
511:
508:
507:
498:
497:
493:
492:
486:
482:
478:
475:
471:
467:
463:
458:
454:
451:
448:
447:WP:DISRUPTION
444:
441:
438:
437:
435:
431:
427:
426:
422:
421:
415:
410:
406:
402:
398:
394:
391:
390:
388:
384:
379:
374:
370:
365:
362:
361:
358:
357:
353:
352:
351:
345:
338:
337:
336:
335:
334:
326:
322:
321:
320:
319:
312:
308:
307:
306:
305:
299:
295:
291:
287:
286:proxy servers
283:
279:
275:
271:
267:
263:
259:
255:
254:
253:
252:
251:
243:
239:
235:
231:
227:
223:
219:
215:
214:Leroy Grumman
211:
207:
203:
199:
195:
194:Frank Lorenzo
191:
187:
183:
179:
175:
172:I've been an
171:
170:
169:
168:
167:
161:
153:
152:
151:
148:
147:
146:
143:
140:
137:
134:
131:
128:
125:
122:
119:
116:
113:
110:
107:
104:
101:
96:
92:
87:
85:
84:
78:
77:
72:
71:
66:
65:
60:
59:
54:
53:
48:
47:
42:
34:
27:
23:
19:
750:
746:
737:
719:
711:
706:
701:
687:
683:
679:
646:
642:
621:
614:. (There is
596:
585:
570:
553:
546:
542:
535:
530:
519:
502:
473:
469:
465:
461:
452:
439:
413:
404:
400:
396:
392:
386:
372:
368:
363:
349:
332:
324:
249:
241:
202:Marcia Fudge
198:Delano Lewis
190:Bill Bradley
165:
138:
132:
126:
120:
114:
108:
102:
93:
90:
82:
79:
75:
69:
63:
57:
51:
50:
45:
40:
688:necessarily
539:account(s).
258:spreadsheet
118:protections
747:appearance
741:breach of
630:Emufarmers
270:subnetting
234:WP:COPYVIO
188:policies (
130:pageĀ moves
751:actuality
707:should be
576:WP:OUTing
445:them for
369:permitted
311:Mediawiki
280:, remote
124:deletions
760:Comments
616:a thread
593:correct.
562:notavote
505:SilkTork
485:steroids
443:WP:BLOCK
434:cry wolf
373:expected
294:spoofing
290:sessions
262:database
106:contribs
58:Jredmond
24: |
20: |
743:WP:SOCK
732:WP:SOCK
647:between
462:prevent
401:decline
176:and an
70:MBisanz
46:Dominic
643:limits
580:outing
547:aren't
476:abuse.
474:invite
470:update
409:WP:IAR
230:WP:BLP
204:, and
186:WP:BLP
136:rights
112:blocks
76:Tznkai
684:could
225:ways.
95:Frank
52:Frank
35:Frank
16:<
383:here
260:and
236:and
100:talk
83:here
520:not
453:A2:
440:A1:
414:not
389:)?
274:ssh
238:G10
182:CSD
142:RfA
738:A:
712:do
702:A:
680:A:
622:A:
582:).
565:}}
559:{{
466:do
436:?
405:if
393:A:
364:A:
276:,
272:,
212:,
200:,
196:,
192:,
73:ā¢
67:ā¢
61:ā¢
55:ā¢
49:ā¢
43::
509:*
449:?
282:X
144:)
139:Ā·
133:Ā·
127:Ā·
121:Ā·
115:Ā·
109:Ā·
103:Ā·
98:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.