Summary
When a temporary account is shown in the UserInfoCard, also provide a visual cue to indicate if other active (registered in last 90 days) temporary accounts exist on the same IP address / IP address range.
Background
- Temporary accounts paradigm means that users without IP reveal access cannot see that a bad actor has created multiple temporary accounts from the same IP address
- Providing an indicator that there are other temporary accounts from the same IP or IPv6 /64 range can help:
- users without IP reveal access can scrutinize those contributions more closely
- users with IP reveal access would know that revealing the IP may be necessary for further investigation
- Note that multiple temporary accounts from a single IP is *not* a sole predictor of a bad actor, given that schools, universities, and larger communities in countries with fewer IP addresses can share a single IP address
- The visual cue is an icon and text: "Temporary accounts from this IP: [count]". We'll need a link to documentation to explain further what the implications are.
- We should *not* provide any details about which specific temporary account names are active on the same IP / IPv6 /64 range. We should just note the fact that other temp accounts exist.
User story
- As a user without IP reveal rights, I want to understand if a temporary account is possibly associated with a bad actor who is creating multiple temporary accounts from the same IP
- As a user with IP reveal rights, I want a visual indicator to understand if IP reveal is more likely to be productive when investigating an account
Design
T389448: UserInfoCard: Design Temporary User Card
- Icon: UserTemporary
- Copy: Temporary accounts from this IP: [count]
- Numbers are bucketed to protect privacy: 0, 1-2, 3-5, 6-10, 11+
Technical notes
(needs more detail)
- Use the same code involved in Special:IPContributions
- Need to consider that when we say "other temporary accounts are active on the same IP / IPv6 range" that we take into account the initial edit that created the temporary account, and any subsequent IPs used in further editing
- Would be nice to package this code such that it could potentially be reused elsewhere, e.g. an AbuseFilter variable that could provide stricter rate limiting if we see that multiple temporary accounts are active from a single IP in a short period of time
Acceptance criteria
- When viewing temporary accounts in the UserInfoCard, we see a visual cue that other active temporary accounts exist on the IP / IPv6 /64 range
- Documentation exists to explain to the user what the implications are (e.g. not necessarily a bad actor)
