User:Perfect4th/Temporary accounts
From Wikipedia, the free encyclopedia
This guide is a topical recounting I created of the Village Pump discussion which I now find useful mainly for my own personal reference, as the main mechanics of temporary accounts are well covered by User:Giraffer/Guide to temporary accounts.
The WMF rolled out temporary accounts (which I'm lazily abbreviating in places as 'temp accounts') on the English Wikipedia on November 4th, 2025. The temporary accounts feature has a Wikimedia FAQ page, but the WMF post and subsequent discussion on the WMF Village Pump generated several other technical questions, mostly from admins and antivandalism patrollers. This is a September 2025 attempt to centralize some answers to those questions; other information is found in the FAQ page. Answers are largely adapted from comments made by WMF and other experienced accounts, and attributed via diffs.
Basic details of IPs/temp accounts
With thanks to IP 98.97.3.234, User:OutsideNormality, User:Jlwoodwa, User:Elemimele, User:KHarlan (WMF), User:WBrown_(WMF), User:SGrabarczuk (WMF), and User:NKohli (WMF)
- Temporary accounts are associated with individual devices via cookies stored in a browser
- Cookies are only stored for 90 days, so after that time each device will receive a new temp account; this cannot be extended, even if the temp account user extends the cookie ,
- The cookies are not tracking cookies
- Editors can reject cookies via browser configuration, thus creating a new temp account instead with each edit, but this comes with a maximum of six edits/day before requiring full account creation
- Each wiki decides individually whether to keep the talk pages of old temp accounts or delete them; the English Wikipedia has not yet had that discussion
- Temp accounts' expected expiry days are not displayed, but the date is displayed on Special:CentralAuth after expiry
- Temp accounts cannot be directly upgraded to regular accounts
Viewing IPs/temp accounts
With thanks to User:ARandomName123, User:Chipmunkdavis, User:ChildrenWillListen, User:KHarlan (WMF), User:NKohli (WMF), and User:SGrabarczuk (WMF)
- The process for and view of seeing contributions made from accounts and IPs before the rollout will not change
- There is a setting for admins to autoreveal IPs when looking at logs to make those processes smoother
- For a given IP, you can only see the temp accounts of that time; any accounts older than 90 days will not be shown
- Temporary Account Information Viewers (TAIVs)' IP views are logged
- Blocks on previous temp accounts are visible to all TAIVs
- Seeing all temp accounts for an IP will be possible via Special:IPContributions
Talking about IPs/temp accounts
With thanks to User:Fram and User:SGrabarczuk (WMF)
- A temporary account can be publicly linked to another if necessary for anti-abuse, and saying that two temp accounts use the same IP is also allowed if the IP is not specified
- A temporary account cannot be publicly linked to an IP via technical evidence, although linking via behavioral evidence is allowed
- Linking an IP to a temporary account/accounts is not allowed, though saying something like "block the common IP these temp accounts use" is OK
- Linking temp accounts to schools or governments is not OK publicly if based on technical evidence, but OK if based on behavioral evidence
- Linking temp accounts to a location based on technical data does not seem to be allowed
- IPs of temp accounts may be disclosed if "reasonably necessary", such as for LTA pages, but should be revdelled if no longer necessary
Blocking IPs/temp accounts and other admin stuff
With thanks to User:rsjaffe, User:Chipmunkdavis, User:Barkeep49, User:Samwalton9 (WMF), and User:WBrown (WMF)
- If planning to block an anonymous user (a non-signed up account) for a period greater than 90 days, the IP should be blocked rather than the temp account
- If an IP but not a temp account is blocked, all temp accounts on the IP cannot edit
- If a temp account but not IP is blocked, the temp account can't edit; if autoblock is also used, the IP will be autoblocked for a day, and if that temp account tries to edit it will create an autoblock
- IP blocks are "visible on Special:BlockList and other places that show blocks"
- Users cannot tell a temp account is blocked by an IP block unless they have TAIV and find the block for the temp account's IP
- If an IP is blocked and a temp account on that IP switches IPs, they will be able to edit; thus, if the target blockee is a temp account the temp account rather than the IP should be blocked
- IP blocking should instead be used if multiple temp accounts that need blocking are editing on the same IP for some time, or if the temp account has evaded blocks via waiting for autoblocks to expire to edit again
- CUs may not be able to block IPs and immediately block temp accounts as this may publicly connect the two
- Blocking temp accounts for longer than 90 days does not have a technical effect, but User:WBrown (WMF) suggests longer blocks can be used to signal to an admin that a subsequent temp account might need to be blocked for longer
- Blocks are generally for users behind the account, and thus will often be indefinite
- Special:Nuke will apply to all temporary accounts for an IP