Last modified: 2008-08-14 20:31:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 15145 - Two extra types of run, "By user (edits)" and "By page (Accounts/IPs)""
Two extra types of run, "By user (edits)" and "By page (Accounts/IPs)""
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Aaron Schulz
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-12 20:37 UTC by FT2
Modified: 2008-08-14 20:31 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Mock-up showing how the extra actions Checkuser currently can't do, might look. (7.82 KB, image/png)
2008-08-12 20:37 UTC, FT2
Details

Description FT2 2008-08-12 20:37:37 UTC
Created attachment 5172 [details]
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.
Comment 1 Aaron Schulz 2008-08-12 20:44:13 UTC
Well, by page would be interesting, though in would need an index
Comment 2 Aaron Schulz 2008-08-14 16:15:44 UTC
So "get edits from user" would be logged-in edits, right?
Comment 3 FT2 2008-08-14 17:29:55 UTC
Would have to be, yes. "Get edits from user account" would be more accurate but maybe less intuitive.
Comment 4 Aaron Schulz 2008-08-14 18:55:41 UTC
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)
Comment 5 Aaron Schulz 2008-08-14 20:04:04 UTC
(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.
Comment 6 FT2 2008-08-14 20:26:56 UTC
Good point on the logging. An accurate log is possible, along the lines "edits and actions from <timestamp1> to <timestamp2>".
Comment 7 Aaron Schulz 2008-08-14 20:31:19 UTC
(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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links