Last modified: 2011-12-31 13:07:13 UTC
It should be possible to program a checkuser watchlist feature. People with checkuser access should be able to enter a list of IP ranges, along with a descriptive note (like "IP range used by Grawp" or something like that). When a user->IP check is performed, any IPs that match any ranges listed in the watchlist, the descriptive note is displayed. The watchlists can be user-specific (each person with checkuser access has his own watchlist), or global (all the checkusers share the same watchlist), or both.
I'd strongly suggest these be shared (cross-wiki if possible, but that may have to be done via mailing list if it can't be implemented in software).
This would be HIGHLY useful. Interwiki CU coordination now is via our mailing list which works but oculd be better. I would like to see all 3. A private watchlist just for myself, a watchlist that is shared with every CU on this particular wiki, and a global one across all wikis where Stewards can administer permissions. Let me, as the author of an entry, choose which visibilities are active, requiring at least one to be active at all times, and let entries show who authored them, when, and what wiki they were on at the time. Separate out the watchlist visibility permission from CU itself so it can be assigned to Stewards, allowing them to see per wiki and global watchlists regardless if they turned on the CU permission on a given wiki or not.
Agreed; cross-wiki cu activities can use all the help it can get, and this would be fantastic.
This would greatly improve cross-wiki CheckUser communication. I fully support any efforts toward creating a user-specific and global CU watchlist.
If done, this would likely be global only, but not cross-wiki.
(In reply to comment #5) > If done, this would likely be global only, but not cross-wiki. > Sorry, I'm not sure what the difference between "global" and "cross-wiki" is here. Can you clarify?
There are three levels of watchlist being proposed/discussed right now: * User level - a user's ranges/comments are visible only to that user * Global level - a user's ranges/comments are visible to all checkusers on that wiki * Cross-wiki level - a user's ranges/comments are visible to all checkusers on all wikis
Note - the possibility that this feature could violate the WMF privacy policy was brought up on the checkuser mailing list. Mike Godwin was asked to comment, and he said that such a feature would not violate the policy.
(In reply to comment #7) > * Global level - a user's ranges/comments are visible to all checkusers on that > wiki Using the word "global" to describe this is wrong - it is not global at all (that is why I didn't understand the difference between "global" and "cross-wiki" -- there isn't any such difference). This should more correctly be called "shared" or "shared locally" if there is a need to differentiate between this and cross-wiki sharing. For steward use, cross-wiki sharing is really critical - without that it will be nearly useless for us.
Agree with Mike Suggest instead that the terms be * "personal" - User level - a user's ranges/comments are visible only to that user * "local" - One wiki level - a user's ranges/comments are visible to all checkusers on that wiki * "Global" - Cross-wiki level - a user's ranges/comments are visible to all allowed users on all wikis
I wonder if getCentralDB() like functions could be used, and WMF sites could borrow the centralauth DB if it is to tedious to make another one.
