Archives

Index Archive 1 Archive 2 Archive 3 Archive 4 Archive 5 Archive 6 Archive 7 Archive 8 Archive 9 Archive 10 Archive 11 Archive 12 Archive 13 Archive 14

This page has archives. Sections older than 90 days may be auto-archived by ClueBot III if there are more than 5.

Dear Brandon,

The IP is back making the same unsourced edits and has now made personal attacks against me in the edit summary. I am at 3RR reverting this now.

Please may I ask why the IP address was blocked when I started my request by saying the abuse was coming from a dynamic IP and this wasn't the solution? The user is already on their third IP in this edit war. It's not going to stop without page protection.

Thank you Unknown Temptation (talk) 09:04, 9 October 2025 (UTC)[reply]

Sorry, my mistake, I didn't see the block happened after the last edit. Still, my point stands that this was in your words "disruptive editing" but it's been left up there and I'm 3RR-tied, plus the user can just go down to McDonald's and start this again. Unknown Temptation (talk) 09:07, 9 October 2025 (UTC)[reply]

They're editing from an IPv6 address, the top half (2402:800:61cf:7a5c) is common amongst all of their edits and I blocked the entire 2402:800:61cf:7a5c::/64. From an abuse perspective IPv6 can be challenging but I don't see this any differently than a single IPv4 address vandalizing a page. If they resume editing reply here and I'll sort it out. I also undid their last edit, apologies I wasn't counting edits for 3RR while blocking. Brandon (talk) 09:21, 9 October 2025 (UTC)[reply]

Hello Brandon,

I'm a bot that helps log arbitration enforcement (AE) protection actions on behalf of the Arbitration Committee. As a result of a September 2025 motion by the Arbitration Committee, administrators are no longer required to manually log AE protection actions. Instead, this bot is responsible for logging AE protections to the AE protection log.

While logging AE protections, this bot detected that you recently took the following page protection actions. These action(s) seemed to be AE actions based on the edit summaries, but the bot wasn't able to tell which arbitration case they related to:

• 06:39, 9 October 2025 (UTC) (Atal Bihari Vajpayee)

If these were AE actions, please take a moment to log the appropriate topic code at the AE protection log. If they were not, feel free to remove the actions from the AE protection log, and optionally let the bot operator know about the false positives.

Going forward, in order to help this bot categorize AE actions, please include a link to the contentious topic under which the action was taken in the protection edit summary (for example, [[WP:CT/BLP]] or [[Wikipedia:Contentious topics/Biographies of Living Persons]]).

If you have any questions, please feel free to reach out to the bot operator or to the arbitration clerks at the arbitration clerks' noticeboard.

Thank you! ClerkBot (talk) 14:48, 9 October 2025 (UTC)[reply]

Hey Brandon, please disregard -- IMH just wasn't fully coded up in the bot. Thanks! KevinL (aka L235 · t · c) 14:49, 9 October 2025 (UTC)[reply]

Hello, Brandon,

Just a reminder, when you are deleting articles, please review the talk page and delete them as well. Two articles recently deleted by you had messages on the talk page that were meant to be seen by the admin deleting the article. You can also do what I do and use Twinkle to do page deletions as it will also delete talk pages and all redirects at the same time. Thank you. Liz ^{Read! Talk!} 06:26, 15 October 2025 (UTC)[reply]

I definitely missed the existence of both of those talk pages, thank you for the feedback. Admittedly I haven't processed CSDs in many years and am a bit rusty, I will be more diligent about checking for the existence of talk pages in the future. Brandon (talk) 08:04, 15 October 2025 (UTC)[reply]

Hi there! While reviewing articles nominated for G11, I noticed you recently soft-blocked つぼ市製茶本舗 様 for a promotional username. Looking at their edits, they’ve mainly been creating a promotional page tied to their former username. In this case, a hard block may be more appropriate so they’re required to address the payment disclosure policy before being unblocked. I have updated the block to reflect this, given that the soft block template indicates the editor can simply create a new account rather than request an unblock, and we want to ensure they understand PAID. I understand some of the language around the block notice has changed, so I wanted to bring this to your attention in case you come across a similar situation in the future. Let me know if you have any questions, comments, and/or concerns regarding this. More than happy to hear your perspective! Take care, Significa liberdade (she/her) (talk) 13:50, 15 October 2025 (UTC)[reply]

I've removed the soft block template from つぼ市製茶本舗 様's talk to avoid confusing them.

Choosing {{uw-spamublock}} instead of {{uw-softerblock}} explicitly to elicit a paid-contribution disclosure prior to unblocking honestly hadn't occurred to me, at least in those terms. That is a very intuitive framing of "there is evidence that the user would continue to edit inappropriately" that is easy to apply consistently. Thank you for the advice, it is much appreciated! Brandon (talk) 17:41, 15 October 2025 (UTC)[reply]

Thank you for removing your block notice! I didn't want to remove your statement. Also, glad to give some perspective from a new admin. :) Significa liberdade (she/her) (talk) 19:53, 15 October 2025 (UTC)[reply]

Hi Brandon,

In the deletion request of my userpage, I set a parameter that had no effect: I tried to say that you should delete all of my userpages, including my subpages. Could you please delete all of my userpages? Thanks!

Best, Faster than Thunder (talk | contributions) _{Tamil speakers: Contribute here} 16:24, 17 October 2025 (UTC)[reply]

 Done Brandon (talk) 21:11, 17 October 2025 (UTC)[reply]

An editor has asked for a deletion review of Jirard. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. –LaundryPizza03 (dc̄) 12:11, 18 October 2025 (UTC)[reply]

Restored. Brandon (talk) 19:52, 18 October 2025 (UTC)[reply]

Hello Brandon,

I'm a bot that helps log arbitration enforcement (AE) protection actions on behalf of the Arbitration Committee. As a result of a September 2025 motion by the Arbitration Committee, administrators are no longer required to manually log AE protection actions. Instead, this bot is responsible for logging AE protections to the AE protection log.

While logging AE protections, this bot detected that you recently took the following page protection actions. These action(s) seemed to be AE actions based on the edit summaries, but the bot wasn't able to tell which arbitration case they related to:

• 05:42, 20 October 2025 (UTC) (Wikipedia:Articles for deletion/2025 Hamas executions)

If these were AE actions, please take a moment to log the appropriate topic code at the AE protection log. If they were not, feel free to remove the actions from the AE protection log, and optionally let the bot operator know about the false positives.

Going forward, in order to help this bot categorize AE actions, please include a link to the contentious topic under which the action was taken in the protection edit summary (for example, [[WP:CT/BLP]] or [[Wikipedia:Contentious topics/Biographies of Living Persons]]).

If you have any questions, please feel free to reach out to the bot operator or to the arbitration clerks at the arbitration clerks' noticeboard.

Thank you! ClerkBot (talk) 23:55, 20 October 2025 (UTC)[reply]

I find this block a bit dubious: the IP edits were properly explained, were falsely labeled as vandalism, and the named account made just as many reverts as the IP. A two-way warning or two-way block would have been more fitting IMO. --JBL (talk) 00:51, 21 October 2025 (UTC)[reply]

Hi. With thanks again for applying the PP change to Avondale House, and while I'm happy to open a new request, before doing so I wanted to follow-up on your kind offer (to 'Drop me a talk page message if pending-changes protected ends up not being sufficient'). In short, I wonder if the current protection level is less-than-sufficient. In encouraging constructive engagement/editing. As a half-dozen pending-changes reviewers have had to review/reject/respond to ongoing noise since the PP tweak. Almost daily. Anyway, happy to (re)open PP thread. If needed. Just wanted to follow-up as suggested first... Guliolopez (talk) 12:01, 22 October 2025 (UTC)[reply]

Hello, Brandon. 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:48, 31 October 2025 (UTC)[reply]

News and updates for administrators from the past month (October 2025).

Administrator changes

Toadspike

• Elahrairah
• Juliancolton
• Magnus Manske

CheckUser changes

asilvering

Guideline and policy news

• The speedy deletion criteria U5 has been repealed, with U6 and U7 replacing it. See the FAQ for more clarifications.
• Community-designated contentious topics may now be enforced and appealed at the arbitration enforcement noticeboard (AE) as a result of an RfC.

Technical news

• You can enable a handy user info card next to usernames, which when clicked displays edit count, blocks, thanks, and other information. To enable this feature, visit Preferences → Appearance → Advanced options → Enable the user info card

Arbitration

• The arbitration case Transgender healthcare and people has been closed
  • Uninvolved administrators may impose an AE participation restriction on any thread at the Arbitration Enforcement noticeboard.

Miscellaneous

• An unreferenced articles backlog drive is happening in November 2025 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!

---

Hi @Brandon! I recently proposed edits to the Splunk article, mainly because it's no longer an independent company since the Cisco purchase. I see you've worked on the article in the past, so I was hoping you would be willing to review my initial proposed edits and provide some feedback. Thanks for your time and any input us welcomed. https://en.wikipedia.org/wiki/Talk:Splunk SBCornelius (talk) 21:15, 25 November 2025 (UTC)[reply]

News and updates for administrators from the past month (November 2025).

Administrator changes

• Chaotic Enby
• Rjjiii

Valereee

• Fathoms Below
• Tamzin

CheckUser changes

Spicy

Technical news

• Starting on November 4, the IP addresses of logged-out editors are no longer being publicly displayed. Instead, they will have a temporary account associated with their edits.
• Administrators will now find that Special:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). T382958

Miscellaneous

• The December 2025 administrator elections are scheduled from Nov 25 – Dec 15.
• An Articles for Creation backlog drive is happening in December 2025, with over 1,000 drafts awaiting review from the past two months. In addition to AfC participants, all administrators and new page patrollers can help review using the Yet Another AFC Helper Script, which can be enabled in the Gadgets settings. Sign up here to participate!

---