@Peachey88 We have a large number of unconfirmed emails on accounts. We already send periodic Echo notifications to users about this T58074: Echo: Generate periodic web notification to nudge users to confirm an unverified email address which has made some impact - P87975. We think we can make a bigger impact by adding a more persistent reminder. The goal here is to minimize unconfirmed emails. The users will be able to update or remove their email address if that's what they prefer instead.

Thanks for looking into this. I tried to get a hold of the totals on superset but realized they scrub gu_email(makes sense) so I can only get count and timestamp of confirmed emails but not the unconfirmed ones.

What I think would be easy to track in Logstash and could be helpful:

• How many email confirmation emails are sent (I think we'll also need this for T415886)
• How many emails get confirmed (although the ratio between this metric and the previous one might be misleading, if there's a delay)
• How much time elapses between us sending a (user-initiated) confirmation email and the user confirming their email. (This is something we should be able to compute and log to logstash at the time the user confirms their email.)

@Madalina I'm adding this to Next since this feels important in light of the threads Johannes shared above.

Thanks for that @Johannnes89. I will mark this as higher priority.

@WikiBayer this information is available on the top of Special:Contribs now. Does that help?

@neriah Hello. Is this still a problem? Have you managed to reproduce it?

This request has not come up in a while even after reaching out to concerned editors. Declining this task until we hear otherwise.

In T412221#11454207, @mszwarc wrote:

@Niharika Linking to Special:IPContributions will reveal the IP behind the temporary account. Should we log that reveal?

If we log it, also cases where the user's intent wasn't to see the IP (but rather general and public data) would be logged. (And since the IP would be only in the link URL, they wouldn't even necessarily see the IP).

We discussed internally and have decided that it makes sense to make the limits global, because the account creation happens globally. We will monitor the impact nonetheless and re-evaluate these limits after a period of time.

@sgrabarczuk should we close this task now? Anything left to do on ruwiki?

@Tchanders is it possible to include the number of temp accounts on the IP/range too?

I agree with your suggestions @mszwarc. Can you please share a screenshot of the end result? Thanks.

In T404984#11211894, @Dreamy_Jazz wrote:

I've got some proposed rough designs, but these have some necessary and other possible changes to what is specified in the specs to consider.

We cannot add links to the text inside the notification. This is because the "primary link" is accessed by clicking anywhere in the notification (except for the secondary link buttons). and the thank you notifications have the primary link going to the edit that was at the specified milestone. Therefore, I think we have to use a secondary link for the account creation page.

Here are some variations on the design to consider that should work for real:

Place it is visible	With no space between the text	With a space between the text
Notification dropdown
Special:Notifications page

Can we also accomplish T410511: Support cross-wiki IP reveals from the global AbuseLog while we work on this? Or is that a very different set of work?

We discussed keeping this out of the sprint for now while we gather feedback about the importance of this work.