Page MenuHomePhabricator

Create Utility to collect User information
Closed, ResolvedPublic

Description

As a developer trying to implement an automatic process to vanish account, I would like to have the possibility to fetch important information about an user that will help me make the correct decision.

NOTE: Check the current code to see what information is already collected and ensure that you add to it.

AC:

  • Add ability to fetch user edits
  • Add the ability to check if the user exist (it could already have been renamed)
  • Check if user has any blocks
  • Add ability to fetch user Logs
  • Add the ability to check if user is part of "please ensure that globally action detection is also accounted for " (this was mentioned in an email, I do not have details on what it means at this stage).
NOTE: The information returned should be for ALL wikis the user is part of.
NOTE: at this stage, there is no UI that surface this information, just methods and tests

Event Timeline

Aklapper renamed this task from Crete Utility to collect User information to CreAte Utility to collect User information.Jun 3 2024, 8:47 AM
Aklapper renamed this task from CreAte Utility to collect User information to Create Utility to collect User information.
Amdrel changed the task status from Open to In Progress.Jun 6 2024, 4:23 PM

Add ability to fetch user edits

CentralAuthUser->getGlobalEditCount implements this functionality.

Add the ability to check if the user exist (it could already have been renamed)

CentralAuthUser->getId can be used to check if a global user exists.

Check if user has any blocks

This kind of check was not available as a reusable function. I implemented this as a new method called CentralAuthUser->isBlocked in a patchset I'm currently working on. I'll reference this task in it when it's ready to review.

Add ability to fetch user Logs

These are shown in Special:GlobalRenameQueue currently using existing logging functionality implemented in LogEventsList found in Mediawiki core. I didn't confirm how well this works in a multi-wiki setup, but I can confirm this works fine with a single wiki (as-in rename logs that are stored on the same wiki as the queue page being used by the renamer).