Page MenuHomePhabricator

Blocking and tagging from checkuser interface
Closed, ResolvedPublic

Description

Author: mapellegrini

Description:
It's not uncommon to run checkuser on a prolific sockpuppeteer and find lots and lots of sockpuppets of some given user. The process of tagging these users' pages with a sockpuppet tag and blocking them can be very, very time consuming. (For an example of the tag, see http://en.wikipedia.org/wiki/User:Sweatypie) I'd like a way to tag-and-block large numbers of users directly from the checkuser results screen.

Each user listed on a checkuser results page should be listed with a checkbox next to his name, which the checkuser can then check. The person running checkuser would also add a string (a sockpuppet tag to be used to overwrite all checked users' pages) and a block duration/type (should almost always indefinite)

Note that this feature should also work in conjunction with bug 9858 - a feature request for recursive checkuser.


Version: unspecified
Severity: enhancement

Details

Reference
bz12808

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:05 PM
bzimport added a project: CheckUser.
bzimport set Reference to bz12808.
bzimport added a subscriber: Unknown Object (MLST).

mike.lifeguard+bugs wrote:

I don't see how tagging would work beyond a single wiki. That would require a single template to always be used, or a MediaWiki message. I don't think either is practical, but perhaps an output option could be provided like &type=text which would return a .txt file suitable for input into AWB as a workaround.

Blocking from the CU interface is probably doable - already-blocked users are marked, so a link to Special:BlockIP/Whatever could be put there instead. Ideally, there'd be some way to specify block settings, and the url would have the appropriate parameters. Perhaps the holy grail would be a single form for settings, and checkboxes to batch-block with the same settings.

mapellegrini wrote:

It would be nice if tagging and blocking worked across multiple wikis. But most vandals target one project and stick to it, so it's not an urgently needed feature.

Regardless, here's how I envision it. When I run checkuser on an IP address or range, next to each user that pops up, there's a "block and tag" checkbox. The form also contains a blank text field, block duration/type fields, and a 'Commit' button. I enter "{{sockpuppet|BadVandal}}" or something like that in the text field, check all the users I want blocked, set a block duration and type, and click commit. All the users are then blocked indefinitely (and the block summary is the text field), all IPs they have used are blocked (depending on what was specified, either logged-in or anon-only, with or without account creation) for the specified length of type, their user pages get tagged with the text field, and the IP address user pages they've used get tagged with the text field.

So, for example, let's say I checkuser on IP address 1.2.3.4. It shows one entry from user:JoeShmow (perhaps from his account registration). I click the "Block and tag" checkbox next to his username, enter "{{sockpuppet|Badvandal}}" in the text field, set the block duration at one week, the block type as both-anons-and-logged-in-users/no-account-creation and click 'Commit'. What should happen is:

  • [[user:JoeShmow]] is created or replaced with {{sockpuppet|Badvandal}}
  • [[user:1.2.3.4]] is created or replaced with {{sockpuppet|Badvandal}}
  • user:JoeShmow is blocked indefinitely with block summary {{sockpuppet|Badvandal}}
  • IP address 1.2.3.4 is blocked, for both anons and logged in users and no account creation, for one week with block summary {{sockpuppet|Badvandal}}

mapellegrini wrote:

This is something that really needs to be done - the checkuser interface is in dire need of improvement. I'm increasing the priority.

mike.lifeguard+bugs wrote:

With respect to comment 1 (mine) - I just meant there'd have to be a MediaWiki page specifying which template to use (or perhaps specifying an array which you are then given a dropdown to choose from) - not impossible, just something to remember if this gets coded.

Made a simple form with a reason/tag input to block sensibly at my test wiki. Will commit after testing and tweaking.

Done in r39299. May add specific block options later.