Jump to content

User talk:Callanecc

Page contents not supported in other languages.
This user has administrator privileges on the English Wikipedia.
This user has CheckUser privileges on the English Wikipedia.
This user has oversight privileges on the English Wikipedia.
This user is an edit filter manager on the English Wikipedia.
This user has been editing Wikipedia for at least fifteen years.
From Wikipedia, the free encyclopedia

Administrator Elections | RFC phase

[edit]

The RFC phase of the July 2025 administrator elections has started. There are 10 RFCs for consideration. You can participate in the RFC phase at Wikipedia:Administrator elections/July 2025/RFCs.

Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.

You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.

MediaWiki message delivery (talk) 12:43, 12 September 2025 (UTC)[reply]

Hi, this is a kind notification that I've requested removal of your user page's protection at WP:RPP#User:Callanecc. The protecting admin is you, but I see you last edited 20 July 2025, so I thought it would be futile me leaving a message here as there are also big notices saying you're busy 🙈 and I'd likely forget. I hope you don't mind me taking it to WP:RPP 'first'. waddie96 ★ (talk) 15:33, 12 September 2025 (UTC)[reply]

Why on Earth does it matter if a user page is protected? And if it did, it's hardly such an emergency that it can't be discussed with the user the page belongs to simply because they've been inactive for a few weeks. HJ Mitchell | Penny for your thoughts? 21:42, 12 September 2025 (UTC)[reply]
It's not an emergency I didn't mean to startle you? waddie96 ★ (talk) 22:10, 12 September 2025 (UTC)[reply]
What I mean to say is , I would've forgotten, so just sort it now? It's not like I'm reporting someone to police; it's an admin/maintenance thing. Thanks for your understanding waddie96 ★ (talk) 22:11, 12 September 2025 (UTC)[reply]

NC-2017

[edit]

Hello. Back in 2020, you closed out the SPI for NC-2017 with the summary "I've blocked the sock, but left the master unblocked as there are some good edits."

Since then, your forbearance has been rewarded with them editing exclusively about their company, and now recreating the barely sub-G4 autobio Rowan Winch. What are your thoughts? Thanks, Wikishovel (talk) 09:44, 27 September 2025 (UTC)[reply]

Hi Wikishovel, I've left them a modified welcome template with some information on editing with a COI. I wouldn't say that they're causing any real harm at the moment so my advice would be that it's just about keeping an eye on them and supporting them to understand our requirements around sourcing and COIs. Callanecc (talk • contribs • logs) 13:06, 6 October 2025 (UTC)[reply]

Possible G5

[edit]

Regarding your recent CU block for Fittu123 (talk Â· contribs Â· block log), can you confirm if Template:Uw-lockedorindefinitlyblockedonenglishwikipedia is G5 eligible? I was about to bring it to TfD but it'd make things easier if it can just be nuked right away. Perryprog (talk) 03:40, 11 October 2025 (UTC)[reply]

It is and I've deleted it. Thank you. Callanecc (talk • contribs • logs) 04:28, 11 October 2025 (UTC)[reply]

Feedback request: Wikipedia policies and guidelines request for comment

[edit]

Your feedback is requested at Wikipedia talk:Ignore all rules on a "Wikipedia policies and guidelines" request for comment. Thank you for helping out!
You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name.

(replacing Yapperbot) SodiumBot (botop|talk) 10:31, 25 October 2025 (UTC)[reply]

A question

[edit]

Regarding the logged warning you posted on my tp, I need a bit assistance on what exactly is battleground behaviour. Example, most of my edits were reverting ip´s who were vandalising certain pages. Usually I would report them on official pages. Is that also battleground behaviour? Should I just let go and let that someone else reverts them even though it may pass 2 or 3 weeks? Thank you.Theonewithreason (talk) 08:42, 26 October 2025 (UTC)[reply]

Hi @Theonewithreason, the warning is related to concerns about reverting changes without fully and correctly/completely explaining your reasons, removing sourced material without fully and correctly/completely explaining your reasons and providing NPOV sources, and not productively and positively contributing to consensus building discussions. If it's clear vandalism you're fine to revert and report them, yes. Callanecc (talk • contribs • logs) 09:04, 27 October 2025 (UTC)[reply]
OK thanks.Theonewithreason (talk) 14:26, 27 October 2025 (UTC)[reply]

Guide to temporary accounts

[edit]

Hello, Callanecc. 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]