This will only be an issue when we have more than one wiki where a temporary account can be autocreated by editing. This isn't the case for the testwiki deployment, where we will deploy to testwiki and loginwiki, since it isn't possible to autocreate a temporary account by editing on loginwiki.

Marking the remaining work as a blocker to pilot wiki deployment, instead of testwiki.

Thanks @Amdrel! Sounds like it might be worth removing those help links for temp accounts to avoid confusion.

To improve on this, we could obtain a list of all the accounts that we should fetch IP information for, and batch them in a single request, generating any access logs as necessary.

Doing this will allow us to complete T369930: Update navigation between Special:Contributions and Special:IPContributions.

In T366618#9997801, @Johannnes89 wrote:

Do you also plan to offer a global preference for accepting the IP Info tool agreement? As a steward it's quite annoying having to accept this on hundreds of wikis I visit when dealing with xwiki spam/vandalism.

Can this be closed, now that https://gerrit.wikimedia.org/r/c/mediawiki/core/+/980947 was merged? (It's not the patch in the task description.)

You'd never have data for the target, so I don't know why the buttons are there for those.

@JJMC89 This is true, but we haven't found examples yet of logged actions (actions with a log ID that are saved to the cu_log_event table) where a temporary account can be the performer. (Happy to be corrected!)

Ahead of testwiki deployment, lets do:

• Stop adding the reveal IP buttons on Special:Log

Note that we're awaiting approval from @ppelberg.

As commented in T337089#9989917, a discussion with Product came to the conclusion that ideally we'd build GUC out a bit more so that users could use GUC to look up, globally:

• Temp account edits from the same IP
• Edits from the same temp account
• Edits from the same registered account

...for the last 90 days. This would mean that they wouldn't need to switch between Special:GUC and the GUC tool, at least while checking for recent edits.

@Dreamy_Jazz It should've been in review - moved to QA.

I'm saying that based on understanding the main goal of Temporary accounts to be to not publicly display IP addresses of anonymous contributors.

In T352914#9507676, @Tchanders wrote:

To do next

• Echo

In T352914#9507676, @Tchanders wrote:

Extension	Does it save IP addresses? What for?	What should we do?
CheckUser	Yes. This is the one place where we'll be storing IP addresses, so this is fine.	No action needed.
AbuseFilter	This stores IP addresses in abuse_filter_log.afl_ip if $wgAbuseFilterLogIP is true. This happens in WMF production: we currently store IP addresses in the AbuseFilter tables.	Needs investigation.