Extension talk:CheckUser
Archives
| ||
|---|---|---|
| ||
How do I run queries in the database?
How do I run queries in the database about IP addresses and users by hand. 141.227.140.159 07:08, 30 March 2025 (UTC)
- The CheckUser extension isn't really designed for this, but you can query against Extension:CheckUser/cu changes table, Extension:CheckUser/cu log event table, and Extension:CheckUser/cu private event table database tables. More detail on what columns to use in the WHERE clause can be found at those pages. WBrown (WMF) (talk) 10:30, 7 July 2025 (UTC)
- @WBrown (WMF)without the checkuser extension ~2025-15905-4 (talk) 02:41, 9 July 2025 (UTC)
- If you don't have the CheckUser extension installed, then there isn't a way to get this data (unless you have IP addresses in the
recentchangestable). WBrown (WMF) (talk) 14:56, 9 July 2025 (UTC)
- If you don't have the CheckUser extension installed, then there isn't a way to get this data (unless you have IP addresses in the
- @WBrown (WMF)without the checkuser extension ~2025-15905-4 (talk) 02:41, 9 July 2025 (UTC)
Uncheckable users
A new user right for checkuser may be users that are uncheckable. How this would work is that when a checkuser attempts to run a check on a user with the uncheckable user right, they cannot but the attempt including the reason is still logged like normal. Until someone (usually a higher authority) removes the user from the uncheckable group, then they can check the users IP address. Uncheckable users still have their IP logged when they are editing with that right in checkuser like normal.
Rationale
On wikis where checkuser is not the highest authority, some checkusers may ask a steward for suppression rights and when the stewards say "no" to suppression rights, they checkuser may check the steward's ip address which violates the privacy of the stewards even when they remove the checkuser rights. 185.137.137.154 19:52, 12 May 2025 (UTC)
- Is this an actual problem or are you just fearmongering? Surely on any wiki CheckUser is a highly trusted role and if someone abuses the tool like that their colleagues will detect the abuse and tell them to knock it off or remove rights if necessary. * Pppery * it has begun 21:10, 12 May 2025 (UTC)
- Solution: make checkuser higher than suppressor. ~2025-130987 (talk) 22:46, 4 July 2025 (UTC)
- Or ask them to sign an nda ~2025-130987 (talk) 22:46, 4 July 2025 (UTC)
- I'm not sure this is something the Trust and Safety Product team will work on. If you want to suggest this more formally, I would suggest creating a Phabricator task. WBrown (WMF) (talk) 10:32, 7 July 2025 (UTC)
- Or ask them to sign an nda ~2025-130987 (talk) 22:46, 4 July 2025 (UTC)
- Solution: make checkuser higher than suppressor. ~2025-130987 (talk) 22:46, 4 July 2025 (UTC)