(Translated by https://www.hiragana.jp/)
⚓ T343716 How can we improve the process of requesting account vanishing from the Android and iOS apps?
Page MenuHomePhabricator

How can we improve the process of requesting account vanishing from the Android and iOS apps?
Open, MediumPublicSpike

Description

iOS (and soon Android) apps are required to allow users to delete their account. In Wikimedia projects the closest analogue to ‘deleting’ an account is vanishing it. Currently, users on iOS can request their account be vanished from the app (T300080) through a process which sends an email to the Wikimedia Foundation legal team, who consolidate the requests and send them over to the renamers@ mailing list for processing by renamers . This process has a number of downsides - the Legal team have to vet the requests to ensure that they’re legitimate (i.e. the sending email address matches the user’s account email), and the renamers@ queue is much less convenient for renamers than Special:GlobalRenameQueue. The Legal team has not had sufficient capacity to process the requests in a timely manner. With the Android app also needing this process to be integrated soon, we expect a substantial increase in the number of requests coming through.

We’re exploring some options around account authentication (i.e. demonstrating that the person requesting vanishing is the account holder), but still have open questions around where these requests should be sent and how we might reduce volumes. Additionally we are considering automatically processing requests from accounts with zero logged actions in some way if they are authenticated.

We’re open to your thoughts in general about how to improve this process, but we also have some specific questions:

  • What does the account vanishing process look like for you? Are there any steps in the process that are particularly frustrating?
  • Would you have any concerns if we sent requests to delete/vanish accounts straight to renamers, either through the Queue or to renamers@?
  • Do you have ideas about how we could alleviate any concerns you have?
  • If we were to do this, what information would renamers need to handle these requests?
  • Do you have any concerns about the idea of automatically processing some or all of the vanishing steps for accounts with no logged actions?

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptAug 7 2023, 1:56 PM
JTannerWMF triaged this task as Medium priority.Aug 8 2023, 6:21 PM
JTannerWMF moved this task from Needs Triage to Tracking on the Wikipedia-iOS-App-Backlog board.

Instead of all the manual processes, can this just have them fill in the form that already loads this to the workflow? That will take care of all the workflow, the only programming would be to put in something to generate the newname (perhaps just something like hash(username&&timestamp)

That is, just send them to:

https://meta.wikimedia.org/wiki/Special:GlobalRenameRequest?reason=RTV&newname=Renamed_user_a1b2c3d4e5f6

It should be uncontroversial to allow automatic renames when:

  1. User is logged in
  2. User has no global edits
  3. User has no global actions
  4. User has no active blocks on any project

The only MAYBE issue with that would be log pollution by someone with oldname=TheNameItselfIsVandalism -- where the workflow may instead be hidelock, not rename.

Instead of all the manual processes, can this just have them fill in the form that already loads this to the workflow? That will take care of all the workflow, the only programming would be to put in something to generate the newname (perhaps just something like hash(username&&timestamp)

That is, just send them to:

https://meta.wikimedia.org/wiki/Special:GlobalRenameRequest?reason=RTV&newname=Renamed_user_a1b2c3d4e5f6

Thanks @Xaosflux! Do you have any concerns about the volume of requests coming through this process, were it to increase substantially? Is there anything about it that makes the review particularly frustrating for you already that would get worse, for example?

Instead of all the manual processes, can this just have them fill in the form that already loads this to the workflow? That will take care of all the workflow, the only programming would be to put in something to generate the newname (perhaps just something like hash(username&&timestamp)

That is, just send them to:

https://meta.wikimedia.org/wiki/Special:GlobalRenameRequest?reason=RTV&newname=Renamed_user_a1b2c3d4e5f6

Thanks @Xaosflux! Do you have any concerns about the volume of requests coming through this process, were it to increase substantially? Is there anything about it that makes the review particularly frustrating for you already that would get worse, for example?

In the last week we have gotten hundreds of requests to the renamers email from WMF; several were defective likely due to data encoding/handling errors as it gets moved from system to system. For some fixed set of criteria (example above) - making it actually self-service would certainly reduce the work of volunteers. - Now, this is actually making a self-service "vanish" on the back end type of work that is needed, then the "app side" would just be a call to it.

Perhaps one more screening criteria: can not be on an IP that is currently globally blocked.

I agree with the preference that all requests be submitted to us in the existing system (Special:GlobalRenameQueue). You can add a parameter that will clarify the source form of the request, for example "Special:GlobalRenameRequest", "ios vanishing" or any other future form. It should also be possible to sort + filter according to this parameter, like the other fields currently.