User talk:Cards84664

  1. Home
  2. Wiki


Welcome to Cards84664's talk page!
If I left you a message: please answer on your talk page, as I am watching it.
If you leave me a message: I will answer on my talk page,
then place {{talkback|Cards84664}} on your talk.

Note: Please start a new talk page thread either by clicking the New section link above or using the box below. Thank you.




Archives
Threads are archived manually in groups of 50.
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

October 2025

[edit]

Information icon Hello, I'm Zackmann08. Thank you for your recent contributions to Template:South Shore Line navbox. When you were adding content to the page, you added duplicate arguments to a template which can cause issues with how the template is rendered. In the future, please use the preview button before you save your edit; this helps you find these errors as they will display in yellow at the top of the page. Thanks. Zackmann (Talk to me/What I been doing) 05:51, 25 October 2025 (UTC)[reply]

Why did you remove the adjacent station template Edson and Hinton?

[edit]

Just wondering. Benfwilliamson (talk) 18:58, 30 October 2025 (UTC)[reply]

Standard practice is to use the Adjacent stations module only on station articles. The module and Template:VIA Canadian have been updated to only link between major stations or stations that still have an article. The module can be re-added if an article for Edson station, Hinton station, etc is created with reliable sources based on notability. Cards84664 19:55, 30 October 2025 (UTC)[reply]
Huh? Care to point me at an RFC or something that shows consensus for having the Adjacent station template point at a station that is not adjacent? This doesn't make sense. 162 etc. (talk) 01:29, 31 October 2025 (UTC)[reply]
We don't put station navboxes in non-station articles, the exception with The Canadian and VIA in general has lasted this long because of the sheer number of completely non-notable flag stops all redirecting to the articles of the cities they serve. Between Capreol and Winnipeg, passengers can request a flag stop at any given mile marker along the route, so if you want to include that as well, go ahead. Cards84664 01:53, 31 October 2025 (UTC)[reply]

Guide to temporary accounts

[edit]

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

  • How to use Special:IPContributions
  • How automatic IP reveal works
  • How to use IP Info
  • How to use User Info

Further information and discussion

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

Plan for Template:NYCS header?

[edit]

{{NYCS header}} is currently unused. Do you have plans for it? Unused templates are typically deleted at WP:TFD. – Jonesey95 (talk) 16:16, 7 November 2025 (UTC)[reply]

I think it can be deleted, gonna use this instead for infobox headers:
|custom_header={{Infobox station/Header NYCS|name=33 Street|bullets={{NYCS Lexington local header|time=bullets}}}}
When Infobox NYCS is converted to Infobox station, both ways of writing the template would work: {{NYCS Lexington local header|time=bullets}} and {{NYCS header|Lexington local header}}
So yeah, it can probably be deleted as redundant. Cards84664 19:30, 7 November 2025 (UTC)[reply]
OK, I have nominated it. Thanks for your work on transportation articles! – Jonesey95 (talk) 00:39, 8 November 2025 (UTC)[reply]

Nomination for discussion of Template:NYCS header

[edit]

Template:NYCS header has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. – Jonesey95 (talk) 00:17, 8 November 2025 (UTC)[reply]