KrakatoaKatie is suffering from health issues. This may affect her ability to work on Wikipedia. Consequently, she may not be able to respond to talk-page messages or e-mails in a timely manner. Your patience is greatly appreciated.
This page has archives. Sections older than 21 days may be auto-archived by Lowercase sigmabot III if there are more than 2.
This user talk page might be watched by friendly talk page stalkers, which means that someone other than me might reply to your query. Their input is welcome and their help with messages that I cannot reply to quickly is appreciated.
B
This user is currently busy but should return shortly.
After a motion, arbitration enforcement page protections no longer need to be logged in the AELOG. A bot now automatically posts protections at WP:AELOG/P. To facilitate this bot, protection summaries must include a link to the relevant CT page (e.g. [[WP:CT/BLP]]), and you will receive talk page reminders if you forget to specify the contentious topic but otherwise indicate it is an AE action.
Verifiability is increasingly important as AI evolves. You should ensure that every statement made is adequately sourced. There should be no less than three independent reliable sources for each biography, including at least one source for each paragraph.
Progress ("moving the needle"):
Statistics available via various tools: previously, Humaniki tool; currently, QLever. Thank you if you contributed one or more of the 20,473 articles created in the past year.
21 Oct 2024, 19.963% of biographies on EN-WP were about women (2,030,245 biographies; 405,305 women)
28 Oct 2025: 20.23% of biographies on EN-WP were about women (2,094,677 biographies; 423,778 women)
Help wanted! Want to apply your skills or learn new ones? Help us plan monthly events, design event logos, come up with a tip-of-the-month, and/or provide any general ideas on developing the project.
Hello, KrakatoaKatie. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.
Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.
How do temporary accounts work?
Editing from a temporary account
When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern: ~2025-12345-67 (a tilde, year of creation, a number split into units of 5).
All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
As a measure against vandalism, there are two limitations on the creation of temporary accounts:
There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.
Temporary account IP viewer user right
How to enable IP Reveal
Administrators may grant the temporary account IP viewer (TAIV) user right to non-administrators who meet the criteria for granting. Importantly, an editor must make an explicit request for the permission (e.g. at WP:PERM/TAIV)—administrators are not permitted to assign the right without a request.
Administrators will automatically be able to see temporary account IP information once they have accepted the Access to Temporary Account IP Addresses Policy via Special:Preferences or via the onboarding dialog which comes up after temporary accounts are deployed.
Impact for administrators
It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
It will still be possible to block an IP address or IP range.
Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).
Rules about IP information disclosure
Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g. ~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67)
