Page MenuHomePhabricator

CU 2.0: Blocking - add new Special:InvestigateBlock
Closed, ResolvedPublic4 Estimated Story PointsJun 30 2020

Description

Goal

Based on our conversation in the planning meeting, we are going to have a new special page that follows from Special:Block to allow blocking in Checkuser.

Acceptance criteria

Event Timeline

Niharika triaged this task as Medium priority.Mar 25 2020, 11:04 PM
Niharika created this task.

Good point, @JJMC89. Thanks for bringing that task to our attention. Will raise it in team meeting.

@Tchanders I updated this to say we should implement the limited form solution. Feel free to add more detail as you see fit!

Do we like the name Speical:InvestigateBlock ? It feels like this this page isn't really related to Special:Investigate?

Do we like the name Speical:InvestigateBlock ? It feels like this this page isn't really related to Special:Investigate?

Hmm, that's a good point. It's for CheckUsers only that's why we linked it to Special:Investigate. @Prtksxna thoughts?

Hmm, that's a good point. It's for CheckUsers only that's why we linked it to Special:Investigate. @Prtksxna thoughts?

I guess another question is... should we create a new right for this page or should we use an existing one? Should we use the investigate right or the block right?

Hmm, that's a good point. It's for CheckUsers only that's why we linked it to Special:Investigate. @Prtksxna thoughts?

I guess another question is... should we create a new right for this page or should we use an existing one? Should we use the investigate right or the block right?

The investigate right. Remember that this page has special options that are only meant for checkusers to use - T248533: CU 2.0: Update Special:InvestigateBlock to add new options. Also this page allows blocking multiple users which is only meant for checkusers.

Do we like the name Speical:InvestigateBlock ? It feels like this this page isn't really related to Special:Investigate?

Per above, I think we should go with Special:InvestigateBlock for now. It might be that a year down the line we need to change that but it's hard to say right now.

Do we like the name Speical:InvestigateBlock ? It feels like this this page isn't really related to Special:Investigate?

Per above, I think we should go with Special:InvestigateBlock for now. It might be that a year down the line we need to change that but it's hard to say right now.

Agreed Special:InvestigateBlock is good.

ARamirez_WMF changed the subtype of this task from "Task" to "Deadline".
ARamirez_WMF changed Due Date from Jun 17 2020, 4:00 AM to Jun 16 2020, 4:00 AM.Jun 9 2020, 8:26 PM

Change 604403 had a related patch set uploaded (by Tchanders; owner: Tchanders):
[mediawiki/extensions/CheckUser@master] Add Special:InvestigateBlock page for blocking multiple users

https://gerrit.wikimedia.org/r/604403

@Prtksxna @Niharika The reason field on Special:CheckUser is just a text input, whereas on Special:Block it allows selecting from pre-defined options. Which should we use here?

@Prtksxna @Niharika The reason field on Special:CheckUser is just a text input, whereas on Special:Block it allows selecting from pre-defined options. Which should we use here?

We should go with what Checkuser offers. We can iterate from there if needed.

ARamirez_WMF changed Due Date from Jun 16 2020, 4:00 AM to Jun 30 2020, 4:00 AM.Jun 17 2020, 5:06 PM

We should go with what Checkuser offers. We can iterate from there if needed.

Thanks @Niharika.

Some questions we could ask the users, for future iterations:

  • Should we make the length of time the block is active for configurable?
  • Should we increase the reason character limit from 150 to CommentStore::COMMENT_CHARACTER_LIMIT?

Change 604403 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Add Special:InvestigateBlock page for blocking multiple users

https://gerrit.wikimedia.org/r/604403

dom_walden added a subscriber: dom_walden.

There is now a Special:InvestigateBlock form (I don't believe anywhere links to this yet).

This looks identical to the blocking form on Special:CheckUser, except without the "Replace user pages with:" and "Replace user pages with:" options.

You can submit multiple users and IP addresses at a time.

If you submit with "Override existing blocks" unchecked, blocks are only created for users/IPs which are not already blocked. Already blocked users/IPs are ignored.

A message is shown to the user on successful submission. Only successfully blocked users/IPs are shown. For example, The users 192.168.121.1, 192.168.121.2, Drwpb and Drwpr are now blocked.

If all users/IPs are already blocked, submit fails and you see a message: No users were blocked. To override existing blocks, check the 'reblock' box. A block will not be overridden if the new block is identical to the existing block.

If you submit with "Override existing blocks" checked, all blocks are created and preexisting blocks are overwritten.

I tested Special:InvestigateBlock alongside the current Special:CheckUser block form to compare behaviour with respect to reblocking and block parameters.

Special:InvestigateBlock and Special:CheckUser produce blocks with the same parameters (e.g. users are blocked indefinitely, IPs for 1 week. User blocks are autoblocks. IP blocks are anonymous.)

You cannot access Special:InvestigateBlock if you are blocked, you see the regular block message. Nor can you submit the form if you happen to already be on the page when someone blocks you.

Users also need the 'investigate' right to access Special:InvestigateBlock.

Testing done on https://test.wikipedia.org (MediaWiki 1.35.0-wmf.38 (rMW923deb81c133) 02:06, 23 June 2020).