@Jonesey95 the current graph is misleading. I don't think simply adding "maximum" adds enough clarity. We should ideally have a way to display within the graph itself when we hit the 1000 edit cap.
Since we don't have too many editors with more than 1000 edits in 60 days, we decided to hide the graph just for those users. It's not going to impact most use cases. We will come back to this ticket later to implement a more thought through fix (CC @KieranMcCann-WMF).

@mszwarc @Tchanders I wrote this combined task for exposing IP Info and UIC since they seemed similar but we can split it if needed.

@A_smart_kitten no worries! I agree with your assessment. The impact would only be for Russian WP as things stand currently. My understanding is that the Web team are actively talking about deploying Vector 22 with the communities. It is unclear when that might happen in practice though.
In the meantime, we are talking about possibilities for deploying temporary accounts with legacy Vector on ruwiki: T411207. This work will not involve supporting notifications since that is a substantially larger amount of work (per @Jdlrobson). We are optimistic that Vector 22 will be deployed on ruwiki within the next few months, so hopefully this will be a non-issue after some time.

Follow up from the discussion in T410636.
@mszwarc @Tchanders @KieranMcCann-WMF @Dreamy_Jazz I welcome your thoughts on the proposed specs.

@MusikAnimal do you think this task can be closed now?

In T410636#11412424, @Tchanders wrote:

@Niharika What if we made some permanent visual difference between the most recent IPs and IPs associated with the particular action/edit, than also implemented a tooltip to explain what that difference meant?

In the absence of better design, something like (1.2.3.4*)?

I agree that a tooltip can help clarify which IP we are using. I also agree that users won't easily discover the hover affordance. A couple thoughts:

• We should only show this tooltip in the event we are displaying the last used IP and that we know there are multiple IPs associated with the temp account. Can we do this?
• Can we auto-display the tooltip for a few seconds (say 5 seconds) when the IP is made visible and then auto-hide it?

In T340001#11366649, @Neolexx wrote:

As you see I am trying to document something I don't see yet - either at all or its Russian version. From here a few questions below I would like to ask. If there is a more appropriate task for them or a new task must be open - I am ready to follow suggestions.

1. What exactly the Russian labels will be to click on to activate that temporary-account-viewer (TAV) rights? and on what tab in Preferences?
2. Is it correct that non-admins have to agree on rules twice: first in some free form when asking for TAV; second (if granted) by clicking in their preferences? - as opposed to admins, who only need to click in preferences.

In T410636#11400196, @mszwarc wrote:

What IP should be displayed for a given temp user? Should it be simply the last one used or some specific one?

Notably, speaking of a Show IP button next to a signature of a temp. account, it is theoretically possible to connect the user to a specific revision (which is done e.g. for the Thank button in DiscussionTools). It could enable us to show the actual IP that was used when posting the specific message (as opposed to just one of the addresses used by it).

Thank you for that information. I am going to remove our team tag from this task since we don't have the capacity to pick it up at the moment.

@Amire80 okay! Let's do the bulleted list.

I think the spacing appears okay now. Closing out this task. Please reopen if the problem recurs.

I updated T402896: Fix links to user creation log to include the excludetempacct parameter except when specifically accessing temp account log to include this work as well. Closing this as a duplicate.

I encountered it on testwiki but testing there again now does not reproduce it. Maybe something upstream caused it momentarily. Closing this out.

In T407653#11352487, @Niharika wrote:

My proposal is to simplify the message language to avoid the "last" terminology -

Account creation is temporarily restricted because visitors from this IP address have exceeded the number of account creations currently allowed. Please try again later.
Kindly note that there is a limit of one account creation allowed every 10 minutes with a maximum of 6 account creations permitted every 24 hours.

This informs them about the limits but doesn't tell them which of the two limits have been tripped. I think it's OK to do this assuming good faith editors will likely try again later and vandals will just move on.

@Chlod should we close this task now?

I'm inclined to decline this task since the layout shift has not really surfaced as a concern in recent feedback. Also given the engineering effort this task does not seem worth pursuing at the moment. Any objections to declining this task?

We've completed the onboarding dialog work.

I am closing this task since we have not seen any more requests about this recently. We can reopen if the concerns arise again.

@IKhitron Hello! Is this work still pending? Do you know who owns GlobalWatchlist?

In T347209#11388235, @mszwarc wrote:

I'll prepare such implementation, then. (But I'll use T392775: Add link color for temporary usernames in content and discussion pages to track the actual engineering work).

(btw, should we move this task to a differet column than Ready?)

In T410151#11379582, @Tgr wrote:

Chrome in normal mode (not incognito)?

@Tgr I tested in Chrome. I have seen this behavior work before so I was surprised when it didn't. Even after waiting for a few minutes it did not log me in to the temp account.

Related tickets

• T403898: Edge login does not work for temporary accounts (description indicates that login used to eventually work)
• T403899: Top-level autologin does not fully work for temporary accounts

Closing this task since we have finished deployment at nearly all projects now.

Focusing this task on the rewording. We can keep discussing the larger issue in T40417.

I encountered this issue again today. The notice does not disappear after 30 seconds as it should.

In general we should modify There is no active login attempt in your session to be more meaningful. I don't think it's clear what is meant by it.

Let us make the wording change at a minimum. It has come up on the talk page twice in the last week.