Wikipedia talk:Administrator intervention against vandalism

WT:AIV

This is not the page for reporting vandalism.
The page to report persistent vandalism is at Administrator intervention against vandalism.

This is the talk page for discussing Administrator intervention against vandalism and anything related to its purposes and tasks.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16: 14 days

AIV helperbot information

HBC AIV helperbot14 assists with the management of vandalism reports. Edit the following parameters in the page header to control the bot's behavior:

RemoveBlocked: On to enable automatic removal of blocked users from the list. Any other value will disable this functionality (only in cases of bot malfunctions, please).
MergeDuplicates: On to enable automatic merging of multiple reports of the same person. Any other value will disable this functionality.
AutoMark: On to enable automatic marking of users with special IPs or membership in categories as defined at User:HBC AIV helperbot/Special IPs. Any other value will disable this functionality.
FixInstructions: On to enable automatic repair of the reporting instruction HTML comments in the User-reported section of the page, as defined at Wikipedia:Administrator intervention against vandalism/instructions. Any other value will disable this functionality.
AutoBacklog: On to enable the automatic switching on or off of the {{adminbacklog}} message. Any other value will disable this functionality. Associated parameters are:
- AddLimit: The number of vandalism reports at which the {{adminbacklog}} message will be made visible.
- RemoveLimit: The number of vandalism reports at which the backlog message will be disabled ({{noadminbacklog}}).

Question for the volunteers

Does it actually make it easier for blocking admins when I report rapid-fire whack-a-mole instances like 176.7.8.92 (talk · contribs · WHOIS) returning 8 minutes later as 176.7.4.10 (talk · contribs · WHOIS) on the same pages? I'm very eager to nip things in the bud but I'm curious if there are any common reporting behaviors that accidentally create more work for admins rather than expediting the process as much as possible. Remsense ‥ 论 03:33, 12 September 2024 (UTC)[reply]

Any administrator can answer this, not only functionaries – If they're on the same small number of pages you're better off requesting page protection. If they vary their targets but their IPs are on a small range (WP:RANGE), you should post about it with the appropriate evidence at WP:ANI. DatGuy^Talk_Contribs 09:27, 12 September 2024 (UTC)[reply]

Oh, I was using that word for flair, I actually didn't know that was a role, oops! Thanks for letting me know so I can stop confusing people. Remsense ‥ 论 09:29, 12 September 2024 (UTC)[reply]

Probably worth pointing out that this in fact now at ANI (currently here). I don't have a better answer for you. It kinda depends how whac-a-mole things are and how well it can be reported. -- zzuuzz ^(talk) 09:41, 12 September 2024 (UTC)[reply]

Oh, it was entirely just the tangent point—I've been meaning to ask admins on the other side of the AIV process if certain things impede or help them for a bit. Remsense ‥ 论 09:51, 12 September 2024 (UTC)[reply]

I hear that, and it kinda depends (and opinions may differ). When there's something like a board invasion involving hundreds of IPs on a limited set of articles, it's sometimes not worth blocking individuals and going straight for protection. If it's a limited set of IPs, say within a small range like 176.7.* above, there's no harm and some benefit to reporting them individually. The admins will see the range patterns, and the bot will clear them all if range blocked. Some people can actually report ranges, but admins need to see specific examples. For more complicated scenarios, ANI makes sense. -- zzuuzz ^(talk) 09:57, 12 September 2024 (UTC)[reply]