Last modified: 2007-12-31 21:02:53 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 12447 - Checkuser results omit information?
Checkuser results omit information?
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-29 20:34 UTC by FT2
Modified: 2007-12-31 21:02 UTC (History)
2 users (show)

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


Attachments

Description FT2 2007-12-29 20:34:39 UTC
As a new checkuser I've been playing with CU. The agent string etc could be usefully reported where it isn't at the moment. Would be exceptionally useful and surprised it's not. Examples:

(1)
"Get edits from IP" using my IP, lists my last many edits, and the IP they're from (as I entered) but not the agent string etc for each. Would be /very/ helpful for editing patterns, as the IP is (obviously) known by being input. For example if the agent changes at specific points, or its changes match changes noted already elsewhere.

(2)
"Get users" using my IP, reports the last agent used.

Present report:

1. <user or IP #1>
<last agent string>

2. <user or IP #2>
<last agent string>

Desired report:

1. <user or IP #1>
<agent string #1> [number of edits] [view]
<agent string #2> [number of edits] [view]

2. <user or IP #2>
<agent string #1> [number of edits] [view]
<agent string #2> [number of edits] [view]
Comment 1 Aaron Schulz 2007-12-29 21:13:21 UTC
#1 done in r29007.

Not sure what #2 is asking...
Comment 2 FT2 2007-12-29 22:07:31 UTC
I was testing it on my own contribs. I use 2 browsers (opera and IE). I noticed though that when I entered my IP and used "get users" as the function, it didn't give the expected response.

But the output only reported that edits were made with opera. That surprised me so I made an edit via IE, and rechecked. This time it reported only that edits were made via IE. Clearly if an IP made edits with multiple browsers or useragents, it's merely reporting the one agent string related to the most recent edit, not others.

That's a problem. Suppose a sock is being checked and agent is part of the evidence, you can ckeckuser an IP and the fact it made 1000 edits with useragent #1 will not show up, provided the most recent edit was via a browser (eg work) with useragent #2.

What I'd like therefore is that a "get users" report of an IP, lists not just each account (plus the IP) and beneath each the most recent agentstring applicable, but each account (plus the IP) and _all_ agentstrings applicable.

Graphically, changed like this:

Suppose I create an account User:X, and make 50 edits with opera (at home) then go to work and make 3 edits with IE, what seems to show up is this:

1. User:X
<useragent string for IE only, as the most recent agent>

What I _want_ to show up is this:

1. User:X <and click to view CheckUser details of all edits made via this account>
<useragent string for IE> "3 edits" <and click to view CheckUser details of these 3 edits>
<useragent string for Opera> "50 edits" <and click to view CheckUser details of these 50 edits>

Comment 3 Aaron Schulz 2007-12-30 01:55:12 UTC
I've done #2 in 29019, but without the counter for performance reasons.
Comment 4 Aaron Schulz 2007-12-31 21:02:53 UTC
Marking this closed, unless the counter is a must have.

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


Navigation
Links