Page MenuHomePhabricator

Global rename of [REDACTED] → Renamed user mou89p43twvqcvm8ut9w3: supervision needed
Closed, ResolvedPublic

Description

I've been asked in private by [REDACTED] to perform this rename of his account. I won't go into any details as to why, but I'm sure that he'll be willing to explain if verification and/or an explanation to a certain degree is needed. His edit count is ~98.3k, but his combined edits and logs total ~110k, requiring the supervision of a sysadmin while the rename is being performed and written to the relevant WMF databases.

May I please work with a sysadmin to reserve a time window so this rename can be performed and simultaneously supervised?

Thank you,
-Oshwah

Event Timeline

Oshwah created this task.Jul 1 2019, 9:53 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 1 2019, 9:53 AM
jbond added a subscriber: jbond.Jul 1 2019, 9:54 AM
Oshwah renamed this task from Need supervision with a global rename of BU_Rob13 → Renamed user mou89p43twvqcvm8ut9w3: supervision needed to Global rename of BU_Rob13 → Renamed user mou89p43twvqcvm8ut9w3: supervision needed.Jul 1 2019, 9:54 AM
jbond added a comment.Jul 1 2019, 9:54 AM

please go ahead

Oshwah renamed this task from Global rename of BU_Rob13 → Renamed user mou89p43twvqcvm8ut9w3: supervision needed to Global rename of [REDACTED] → Renamed user mou89p43twvqcvm8ut9w3: supervision needed.Jul 1 2019, 9:58 AM
Oshwah closed this task as Resolved.
Oshwah claimed this task.
Oshwah triaged this task as Low priority.
Oshwah updated the task description. (Show Details)
DannyS712 added a subscriber: DannyS712.EditedJul 1 2019, 8:32 PM

@Oshwah if the user wants to keep this private, you may want to change the visibility of this task - the name is still visible in the description history.

Oshwah added a comment.Jul 5 2019, 4:46 AM

@DannyS712 - Is this done by clicking on "protect as security issue"? That appears to be only used for security-related vulnerabilities and incidents. If this is not how I change visibility, how do I do this? I don't see an option or way to do so on the interface. Or I'm just an blind idiot... that's always a possibility. :-)

Not sure, but @Aklapper would know how to set a custom visibility policy

The term "security issue" is used in quite broad meaning, basically everything that should be non-public at any given time. You can use it, if you want. However, please keep in mind that given this wasn't security task from the beggining, it was distributed to many users by email notifications, and there is no way how to delete that kind of information.

This is not a Security issue and there is no "broad meaning". "Edit Task" above offers to restrict the task view policy.

This is not a Security issue and there is no "broad meaning". "Edit Task" above offers to restrict the task view policy.

Yes, if you're an admin. Normal user can only escalate tasks to security ones.

Ah, thanks. What should the view policy of this task be exactly then?

NDA only would probably be the easiest

I'm sorry but I don't see a need to restrict this task.

All renames are publicly logged on wiki on several logs. With global rename that means a global rename log entry at Meta and as many local rename log entries as local accounts the renamed user had on those wikis (in their case that's more than one hundred). Using RenameUser as a means to vanish is not really effective given that there's no way you can make a private rename.

This task also doesn't really have any private information. The former username of the renamed username is visible in the contents of this ticket and on logs everywhere, and it is not private data according to the Wikimedia privacy policy either. The reasons because the user requested the rename, in confidence to the global renamer are certainly private and not to be shared, but those ain't posted here.

I can change task's visibilities, and I'm willing as a courtesy to let only registered Phabricator accounts to see this if really needed, though.