User talk:Andrewa

G'day! This is Andrew Alder's user talk page, you knew that. Welcome!

If you're tempted to go below the top three levels, you might like to read User:Andrewa/How not to rant first


Psalm 150 (paraphrased)

WikiProject Article Rescue Squadron Newsletter

[edit]

Article Rescue Squadron Newsletter

Volume I, Issue III
February 2012

To contribute to the next newsletter, please visit the Newsletter draft page.
ARS Members automatically receive this newsletter. To opt out, please remove your name from the recipients list.


You've got mail

[edit]
Hello, Andrewa. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

ArbCom Elections 2016: Voting now open!

[edit]

Hello, Andrewa. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page.

Guide to temporary accounts

[edit]

Hello, Andrewa. 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

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 → Tick 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

Further information and discussion

Most of this message was written by Mz7 (source). Thanks, 🎃 SGrabarczuk (WMF) (talk) 02:48, 31 October 2025 (UTC)[reply]

UNT Health rename

[edit]

Per WP:NAMECHANGES we need reliable secondary sources published since the rename that use the new name. To avoid cluttering the RM discussion Talk:University of North Texas Health Science Center#Requested move 29 October 2025 I invite suggestions below. I'm happy to discuss here whether or not these are helpful sources. No pressure to do this, just an idea that might help the eventual closer. Andrewa (talk) 21:38, 12 November 2025 (UTC)[reply]

Sources now provided. Andrewa (talk) 05:42, 13 November 2025 (UTC)[reply]
And RM closed as move by consensus [1]. Andrewa (talk) 01:12, 16 November 2025 (UTC)[reply]

ArbCom 2025 Elections voter message

[edit]

Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2025 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:17, 18 November 2025 (UTC)[reply]

James Angleton (or just in general) renaming protocol

[edit]

Hello,

I'm a newbie editor, and noticed that you chimed in on my requested renaming of James Jesus Angleton. Obviously, I feel pretty strongly about where I want the renaming to go, but it's definitely without consensus. Should I just close the renaming request because of the lack of consensus per wp:rmci, or do something else? Forgive me for my confusion, just don't want to do anything wrong. Best, Theodore Christopher (talk) 20:34, 18 November 2025 (UTC)[reply]

Thanks Theodore Christopher for the question.
Closure should normally be done by an uninvolved editor. The only time it's proper for the requestor (called the "nominator" of "nom" for short) to close a requested move themselves is if they decide to withdraw the request and obviously that's not the case here. You can request closure but you do not need to do so, it will happen in any case. Watch Wikipedia:Requested moves/Current discussions#Elapsed listings and the following backlog section and you will see the requests progressively closed as editors who take on this role get around to processing the requests.
Much of this is automated by various scripts and bots which take care of some of the drudgery, but that's the underlying process. Andrewa (talk) 21:48, 18 November 2025 (UTC)[reply]