Page MenuHomePhabricator

Two extra types of run, "By user (edits)" and "By page (Accounts/IPs)""
Closed, ResolvedPublic

Description

Author: FT2.wiki

Description:
Mock-up showing how the extra actions Checkuser currently can't do, might look.

At present Checkuser can perform the following mappings:

IP (or IP range) -> List of users on that range
IP (or IP range) -> Individual edits on that range
Username -> List of IPs

A checkuser wishing to get Checkuser data for a specific user's edits (eg to review the IPs or other technical data over time), cannot easily do so. They need to run "User -> IPs", then run Checkuser for each IP in turn, then collate and sort these, then remove all data not pertaining to that user.

An option "get edits from user" would be useful in some cases.

Similar logic might apply to "Edits on a page", giving a list somewhat like the "Get users" output.

A mockup of how this might look is attached. The extra three runs are very similar in output to the existing ones, and hence hopefully most of the code already exists for adapting.


Version: unspecified
Severity: enhancement

Attached:

cu-action.png (220×566 px, 7 KB)

Details

Reference
bz15145

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:19 PM
bzimport added a project: CheckUser.
bzimport set Reference to bz15145.

Well, by page would be interesting, though in would need an index

So "get edits from user" would be logged-in edits, right?

FT2.wiki wrote:

Would have to be, yes. "Get edits from user account" would be more accurate but maybe less intuitive.

Working on the user checking. Don't plan on doing the other since it would log in poor and shadowy manor (eg. not really giving away who was checked)

(In reply to comment #4)

Working on the user checking. Don't plan on doing the other since it would log
in poor and shadowy manor (eg. not really giving away who was checked)

Done in r39364.

FT2.wiki wrote:

Good point on the logging. An accurate log is possible, along the lines "edits and actions from <timestamp1> to <timestamp2>".

(In reply to comment #6)

Good point on the logging. An accurate log is possible, along the lines "edits
and actions from <timestamp1> to <timestamp2>".

Still obscures the users/IPs checked way too much.