Page MenuHomePhabricator

Do not show link between named account and temporary account in RecentChanges and Special:Log
Closed, ResolvedPublic1 Estimated Story Points

Description

Context

We create temporary accounts to protect user privacy. Temp account users can create permanent accounts. We inform temp account users that their edit history is not carried over to the named account. My expectation then is that temp account users would expect to not see a public link between the temporary account and their named account.

But in RecentChanges and in Special:Log, anyone can see that the new named account was created by a specific temp account.

image.png (276×1 px, 43 KB)

Proposal

  • Don't show the "created by" part in Special:Log, RecentChanges, etc

Consequences

  • It is harder for someone to guess at which permanent, named account is associated with a particular temporary account

See also:
T357498: Temp account creations do not appear in Special:Log
T335508: Connect temporary and permanent account during signup

Event Timeline

kostajh renamed this task from Do not show link between named account and temporary account in RecentChanges to Do not show link between named account and temporary account in RecentChanges and Special:Log.May 13 2024, 9:03 AM

@kostajh I wanted to confirm if TSP intended on working on this task? We were discussing it today but wanted to clarify before we considered investigating this.

@kostajh I wanted to confirm if TSP intended on working on this task? We were discussing it today but wanted to clarify before we considered investigating this.

If Growth has capacity to work on this, that would be great.

We're currently focused getting through a couple of issues that are critical to us deploying Community Configuration to our first pilot wiki. I suspect that we may have some bandwidth after we deploy Community Configuration to a pilot wiki(~ 1.5 sprints from today which is in 3 weeks) to launch an initial investigation into this.

Can the task wait until then since it's been tagged as a high priority?

We're currently focused getting through a couple of issues that are critical to us deploying Community Configuration to our first pilot wiki. I suspect that we may have some bandwidth after we deploy Community Configuration to a pilot wiki(~ 1.5 sprints from today which is in 3 weeks) to launch an initial investigation into this.

Can the task wait until then since it's been tagged as a high priority?

That sounds OK to me (cc @Tchanders)

We're currently focused getting through a couple of issues that are critical to us deploying Community Configuration to our first pilot wiki. I suspect that we may have some bandwidth after we deploy Community Configuration to a pilot wiki(~ 1.5 sprints from today which is in 3 weeks) to launch an initial investigation into this.

Can the task wait until then since it's been tagged as a high priority?

That sounds OK to me (cc @Tchanders)

Sounds reasonable, thanks @DMburugu. Note that I think this would be a blocker to testwiki deployment though, since it could make IP addresses of registered accounts more discoverable.

Tagging @TAdeleye_WMF who is keeping track of different teams' work schedules.

Sgs set the point value for this task to 1.May 28 2024, 4:26 PM

Change #1047952 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/core@master] Don't link temporary account and named account in newusers log

https://gerrit.wikimedia.org/r/1047952

Testing notes

  1. Enable temp users
  2. As a logged out user, make an edit, creating a temp user
  3. As that temp user, visit Special:CreateAccount
  4. Create a new account
  5. Visit Special:Log?type=newusers

Before this task, the log entry for the new account says it was created by the temp user.

Now, it should just say the the account was created, without mentioning who created it.

Change #1047952 merged by jenkins-bot:

[mediawiki/core@master] Don't link temporary account and named account in newusers log

https://gerrit.wikimedia.org/r/1047952

Djackson-ctr subscribed.

I have verified the new code has been implemented and is functioning and displaying as expected.

image.png (569×1 px, 213 KB)

image.png (863×1 px, 227 KB)

image.png (891×735 px, 111 KB)

image.png (471×910 px, 145 KB)

image.png (896×454 px, 212 KB)

Dreamy_Jazz claimed this task.