User talk:Xeno
| userpage | talk | dashboard | misc |
|
|
Movement Charter Drafting Committee's monthly newsletter
[edit]Updates:
- Charter Ratification Methodology proposal conversations: The Movement Charter Drafting Committee recently held the first conversations regarding the ratification methodology for the Movement Charter. The MCDC has received valuable feedback from different communities and the Committees during the community input period. The report of the community input will be shared in May, while the updated version of the ratification methodology will be presented between September and November 2023.
- Communication evaluation: The Communications sub-committee of the MCDC together with the support staff conducted an evaluation of the communications. The Communications sub-committee appreciates the time and input of the community members who shared their opinions during the interviews. Several recommendations are going to be implemented in the upcoming period based on the valuable input.
- Learn about the MCDC’s work in April: The MCDC continues to draft additional chapters: The Global Council, Hubs, Decision-making and Roles & Responsibilities. Alongside the drafting work, the MCDC is planning their in-person meeting scheduled for 2-4 June in Utrecht, Netherlands with the aim of advancing the charter's content.
What’s coming up?
- Participants of the WikiNusantara 2023 in Banjarmasin, Indonesia are invited to join a session on the topics around Wikimedia Movement Strategy and community collaboration on May 20. Ramzy Muliawan will provide updates, share about the Movement Charter Ambassadors Program and answer the questions.
Subscribe to this newsletter on Meta wiki

The article Delilah Cotto has been proposed for deletion because of the following concern:
Tagged for BLP sources for 18 years. Tagged for notability concerns for 9 months. Still has only one broken source. Fails the relevant notability guidelines.
While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. Bearian (talk) 00:55, 6 October 2025 (UTC)
Administrators' newsletter – October 2025
[edit]News and updates for administrators from the past month (September 2025).

- 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.
Request for unprotection of Salvation, Texas redirect
[edit]Hello there, Xeno. I hope you are doing well. I am inquiring about the protection of the redirect Salvation, Texas being lifted. You had protected it indefinitely in 2010 per this AfD, and since it has been over 15 years, I was wondering if you could unprotect it so that I may perform categorization template maintenance, akin to the double redirect Salvation, Texas (book). I will note that the student film of the same title brought up in the AfD has not appeared to elicit any further interest in regards to an article, and I intend to keep the redirect target intact. Cheers, — Trailblazer101🔥 (discuss · contribs) 03:00, 11 October 2025 (UTC)
Guide to temporary accounts
[edit]Hello, Xeno. 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?
- 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
- 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) - See Wikipedia:Temporary account IP viewer § What can and can't be said for more detailed guidelines.
Useful tools for patrollers
- It is possible to view if a user has opted-in to view temporary account IPs via the User Info card, available in Preferences → Appearance → Advanced options →
Enable the user info card
- This feature also makes it possible for anyone to see the approximate count of temporary accounts active on the same IP address range.
- Special:IPContributions allows viewing all edits and temporary accounts connected to a specific IP address or IP range.
- Similarly, Special:GlobalContributions supports global search for a given temporary account's activity.
- The auto-reveal feature (see video below) allows users with the right permissions to automatically reveal all IP addresses for a limited time window.
Videos
-
How to use Special:IPContributions
-
How automatic IP reveal works
-
How to use IP Info
-
How to use User Info
Further information and discussion
- For more information and discussion regarding this change, please see the announcement from the Wikimedia Foundation at Wikipedia:Village pump (WMF) § Temporary accounts rollout.
Most of this message was written by Mz7 (source). Thanks, 🎃 SGrabarczuk (WMF) (talk) 02:47, 31 October 2025 (UTC)