31:
220:
Prior to applying, the editor must maintain a log of which blocks they would have made using the role, for 2 weeks or 10 blocks (whichever comes first). Log entries should be made at the time when the block would've been made (that is, not some time afterwards), and should be in userspace. When they
303:
Although it could be argued that ADMINACCT and ADMINBOT would make the adminbots' operators personally accountable for the blocks, if this proposal passes, it is understood that accountability passes entirely to the users requesting blocks, except in instances of bugs and other technical problems
319:
Data will be collected on the the trial. The trial can be evaluated based on whether any bad blocks were made, whether it reduced the amount of vandalism done while AIV reports are open, and whether it saved community time overall. Editors may suggest more metrics to use.
86:), the reported user continues vandalizing while the report waits for an admin. In the fall of 2021, there were 8,020 such edits. On average, there are 12 reports every week where the vandal can make 10+ edits before being blocked. Some examples:
217:. Being nominated by another editor is recommended. The discussion will be open for a minimum of 48 hours. Any editor may comment, but threaded discussion is encouraged instead of bolded !votes. The discussion will be closed by an administrator.
289:. Editors listed there have the ability to place a block as described above while making an AIV report. The adminbot will check that the quantitative criteria for blocking are met and use the API to place the block. Blocks will be
265:
for their actions using the tool. Abuse of this tool, or usage outside of its approved scope, is a serious issue. Any administrator who suspects the tool has been misused may unilaterally revoke it and notify the
315:
Any admin can pause the trial at any time and open a discussion on whether it should continue. Technical changes to how the role works are allowed unilaterally; substantive changes are allowed after discussion.
390:
is needed. Similarly, a lower amount of overall tenure/experience is needed. All passing RfA candidates starting in 2017 have had more than 10k edits, and we're looking for less than that.
202:
Furthermore, this role must not be used when protection or another admin action would be a more effective response, such as when a single page is being disrupted by many different users.
356:
461:
There should be an IRC/Discord channel reporting each responder block in real time. We could have a bot posting when users could (heuristically) be eligible to be blocked, as well.
312:
The trial will last for three months starting when the first user is granted the role. After three months, the role and bot will be disabled and no further blocks will be made.
386:
This role requires much less of a candidate than adminship and would be easier to get. Admittedly, some of the skills overlap (good judgment, policy understanding) but a lower
496:
491:
458:
The precise implementation of how a user requests a block by the bot can be decided later; perhaps AIV reports could include a special template, which the bot would look for.
342:
The single situation where blocks could be made is described very precisely. If they block outside of that situation anyway, this will be noticed and the role can be revoked.
501:
505:
486:
481:
511:
164:
These blocks do not replace blocks made by admins patrolling AIV. Each AIV report will be reviewed by an admin as usual, possibly resulting in a block.
145:
Note that even when the average response time of online admins is at its lowest (i.e. fastest) point during the day, this problem persists. Looking at
464:
User scripts and other tools can be made later to assist any part of this process, but are not in scope initially and aren't required for the trial.
375:
127:
119:
446:
This proposal is only a utility for frequent AIV reporters. Responders have minimal authority, as admins have to review each of their actions.
300:
For further accountability, each week, the bot will post a random sample of blocks (or all, if there weren't many) made with this role to AN.
238:
The editor must have a history of good anti-vandalism work. The editor should make AIV reports that reliably get actioned. They should use
135:
87:
355:
Recent changes patrollers should not revert these edits so that the vandal won't re-revert and the page history looks cleaner. (See also
362:
This strategy is not widely acceptable. It also won't work for blanking and other particularly noticeable vandalism, or for vandals who
111:
374:
This role is unrelated to most admin work, so most RfA candidates will not be expected to have it. So far in 2022, only five out of 14
199:
Generally, there should never be disputes over whether a block was proper; if there's any doubt at all, a block should not be placed.
66:
Proposed: A 3-month trial of a new role to allow users who are reporting a high-speed vandal at AIV to also block them for an hour.
17:
185:
426:
Yes, if that happens, this role will be ineffective. It is unknown how many vandals will do this, which is why this is a trial.
363:
184:; there must be no way it could be good-faith editing. In particular, there must be no credible argument that it could be mere
95:
146:
83:
103:
157:
Users with this role can, when reporting a user to AIV for vandalism, also block that user for an hour (via bot, see
189:
438:
Admins will usually tell users that it's not that important and that they should just report the vandal to AIV.
161:). Blocks cannot be made for any other reason, and this role does not permit any other sort of admin action.
249:
For the trial, and early in the role's lifetime, the goal will be to get editors in this role who will make
139:
131:
123:
115:
107:
99:
91:
262:
336:
239:
234:
The editor should have no behavioral blocks or 3RR violations for a span of 6 months prior to applying.
49:
323:
There may be another RfC after the trial for permanent implementation, depending on community mood.
243:
286:
350:
The responding admin at AIV will take appropriate actions, as they would for a normal AIV report.
406:
An admin should've indeffed/31hr'd them already. If not, action will eventually be taken at AIV.
487:
Knowledge (XXG):Village_pump_(idea_lab)/Archive_32#Staying_ahead_of_the_moles_(as_in_whack-a)
282:
214:
38:
518:
267:
502:
Knowledge (XXG):Village_pump_(proposals)/Archive_120#Proposed_user_right:_Vandal_fighter
273:
The role may also be removed by request or if a user has been inactive for 12 months.
492:
Knowledge (XXG):Administrators'_noticeboard/Archive327#Spitballing_-_autoprotect_bot
482:
Knowledge (XXG):Village_pump_(idea_lab)/Archive_34#Unbundling_for_the_millionth_time
506:
Knowledge (XXG):Village_pump_(idea_lab)/Archive_15#New_"vandal_stopper"_user_group
347:
Responders will block and not take other required admin actions, such as revdel.
171:
Only IP addresses, or registered accounts less than a day old, can be blocked.
335:
Responders will block even when other admin actions would be better choices (
177:
A given IP address or account can only receive one responder block per month.
228:
The editor should be a registered
Knowledge (XXG) user for at least 1 year.
512:
Knowledge (XXG):Requests_for_adminship/2013_RfC/3#Limited_block/unblock
497:
Wikipedia_talk:Requests_for_adminship/Archive_240#Limited_block_button
521:
to split the "block" permission, perhaps into blockip and blockuser.
398:
Anyone blocked using this role should be far from a borderline case.
331:
This list will be posted by the proposer in the bulleted discussion.
149:, in fact, that hour of day has the third worst number of edits.
30:
25:
195:
The vandalism should be rapid (at least one edit per minute).
174:
The blocked user must have vandalized less than an hour ago.
205:
The blocks can be lifted by other responders or by admins.
357:
Knowledge (XXG):Don't edit-war with vandals or sockpuppets
231:
The editor should have made at least 2,000 overall edits.
41:. Please add your thoughts and feedback on the talk page.
253:. The role should be granted and revoked appropriately.
57:
414:
These blocks will include "Prevent account creation" (
221:
apply or are nominated, they should link to the log.
371:This role will become a de facto RfA prerequisite.
431:Users should just ask for help from admins (e.g.
403:The vandal will just come back after an hour.
8:
411:The vandal will just make another account.
285:page listing editors with access, like the
378:mentioned AIV in their Question 1 answers.
7:
18:Knowledge (XXG):Requests for comment
443:This proposal creates mini-admins.
158:
418:) which will make that impossible.
24:
423:The vandal will just switch IPs.
82:In about a third of AIV reports (
79:Update section with 2022 numbers
29:
383:They should just start an RfA.
395:We over-block at AIV already.
364:keep finding new pages to edit
1:
246:, correctly and effectively.
37:This is a draft for a future
327:Responses to some objections
453:Other stuff, details, ideas
268:administrators' noticeboard
535:
330:
47:
477:; here's a small sample.
261:Editors are expected to
251:absolutely zero mistakes
242:or similar tools, like
473:This idea has come up
180:The vandalism must be
337:law of the instrument
213:Editors may apply at
469:Previous discussions
92:2-hour response time
186:tendentious editing
39:request for comment
84:data analysis here
42:
46:
45:
36:
526:
434:
417:
296:
292:
281:There will be a
159:§ Implementation
77:
60:
58:WP:RESPONDER-RFC
33:
26:
534:
533:
529:
528:
527:
525:
524:
523:
471:
455:
432:
415:
332:
329:
310:
294:
290:
283:fully-protected
279:
259:
211:
155:
75:
72:
64:
63:
56:
52:
22:
21:
20:
12:
11:
5:
532:
530:
515:
514:
509:
499:
494:
489:
484:
470:
467:
466:
465:
462:
459:
454:
451:
450:
449:
448:
447:
441:
440:
439:
429:
428:
427:
421:
420:
419:
409:
408:
407:
401:
400:
399:
393:
392:
391:
381:
380:
379:
376:RfA candidates
369:
368:
367:
353:
352:
351:
345:
344:
343:
328:
325:
309:
306:
304:with the bot.
278:
277:Implementation
275:
270:of the issue.
263:be accountable
258:
255:
236:
235:
232:
229:
210:
207:
197:
196:
193:
178:
175:
172:
167:Restrictions:
154:
151:
71:
68:
62:
61:
53:
48:
44:
43:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
531:
522:
520:
513:
510:
507:
504:(preceded by
503:
500:
498:
495:
493:
490:
488:
485:
483:
480:
479:
478:
476:
468:
463:
460:
457:
456:
452:
445:
444:
442:
437:
436:
430:
425:
424:
422:
413:
412:
410:
405:
404:
402:
397:
396:
394:
389:
385:
384:
382:
377:
373:
372:
370:
365:
361:
360:
358:
354:
349:
348:
346:
341:
340:
338:
334:
333:
326:
324:
321:
317:
313:
307:
305:
301:
298:
288:
287:AWB checkpage
284:
276:
274:
271:
269:
264:
256:
254:
252:
247:
245:
241:
233:
230:
227:
226:
225:
222:
218:
216:
208:
206:
203:
200:
194:
191:
187:
183:
179:
176:
173:
170:
169:
168:
165:
162:
160:
152:
150:
148:
143:
141:
137:
133:
129:
125:
121:
117:
113:
109:
105:
101:
97:
93:
89:
85:
80:
78:
69:
67:
59:
55:
54:
51:
40:
35:
32:
28:
27:
19:
516:
474:
472:
387:
322:
318:
314:
311:
302:
299:
280:
272:
260:
250:
248:
237:
224:Guidelines:
223:
219:
212:
204:
201:
198:
190:edit warring
181:
166:
163:
156:
144:
81:
74:
73:
65:
257:Revocation
147:the graphs
70:Background
517:See also
435:on IRC).
295:autoblock
416:nocreate
291:nocreate
240:rollback
209:Granting
153:Proposal
96:79 edits
88:85 edits
50:Shortcut
519:T128328
244:Twinkle
182:blatant
433:!admin
475:a lot
388:level
308:Trial
215:WP:AN
16:<
293:and
76:TODO
359:.)
339:).
188:or
142:).
134:),
132:51m
126:),
118:),
110:),
102:),
100:31m
94:),
297:.
140:2h
136:51
128:55
124:2h
120:63
116:3h
112:69
108:1h
104:71
508:)
366:.
192:.
138:(
130:(
122:(
114:(
106:(
98:(
90:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
