User talk:Jpgordon




Admin statistics
Action Count
Edits 83676
Edits+Deleted 86575
Pages deleted 1862
Revisions deleted 81
Pages restored 24
Pages protected 364
Pages unprotected 27
Protections modified 29
Users blocked 7540
Users reblocked 1739
Users unblocked 734
User rights modified 40

For older history, check [1] as well as the archives.

Unblock

[edit]

Hi, thanks for the help :-) Nyttend (talk) 04:12, 1 September 2025 (UTC)[reply]

Happy First Edit Day!

[edit]

Happy First Edit Day!

[edit]

Edit summary tone(s)

[edit]

Hey! I'm just letting you know I keep noticing a pattern of name calling on some blocked editors in your block notices here: [2], [3], [4]. I know some people can make you upset on here especially in the anti-vandalism scene but I would personally ease off the gas a little? It's not particularly constructive to call other editors or even vandals names regardless of what they've done. 🪷 nahida 23:03, 4 September 2025 (UTC)[reply]

Your concern is noted. It's not "some blocked editors", it's one asshole. --jpgordon𝄢𝄆𝄐𝄇 23:07, 4 September 2025 (UTC)[reply]
Fair, I didn't dig deep to see if it was a sock or if it was different editors, I was patrolling recent changes. I just wouldn't publicly call them names as it can reasonably be construed as a personal attack. 🪷 nahida 23:09, 4 September 2025 (UTC)[reply]

Unblock

[edit]

The problem was that within the past couple of days, somebody created a brand new mainspace redirect from the word unblock to the article block (internet) — which meant that several past invocations of the unblock template on user talk pages were suddenly transcluding that entire article instead of the unblock template, thus putting those pages into all of that article's categories. So I had to edit those talk pages so that they were invoking the template instead of the article, in order to get them out of the categories on WP:USERNOCAT grounds. If that "reactivated" them, then I apologize, but the problem is that they were transcludng a mainspace article with categories instead of the template, and had to be pointed back to where they belonged. If there's an extra code to close them that I should have added, then I can go back and do that — since I don't normally deal with unblock requests, I don't know what that would be, but I can add it if you let me know what it is. Bearcat (talk) 15:57, 6 September 2025 (UTC)[reply]

Certainly no apology necessary -- just a bit of cleanup needed when I see them in unblock land. Thanks for the clarification. --jpgordon𝄢𝄆𝄐𝄇 16:21, 6 September 2025 (UTC)[reply]

Administrators' newsletter – September 2025

[edit]

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

Administrator changes

readded Euryalus
removed

Interface administrator changes

readded Ragesoss

CheckUser changes

readded AmandaNP
removed SQL

Oversight changes

readded AmandaNP

Guideline and policy news

  • An RfC is open on whether use of emojis with no encyclopedic value in mainspace and draftspace (e.g., at the start of paragraphs or in place of bullet points) should be added as a criterion under G15.

Technical news

Arbitration

  • The arbitration case Article titles and capitalisation 2 has been closed.
  • An RfC is in progress to amend the structure, rules, and procedures of the Arbitration Committee election and resolve any issues not covered by existing rules.

alea jacta est?

[edit]

I guess one cannot unmail that which has been mailed. Did anyone refer them to DRV before the threat? When anyone contests one of my G11 deletions, I refer them back to my deletion notice. If they persist, I refer them to DRV. A pity, really. Anyone one that writes such huge volumes could become a great copy editor. -- Deepfriedokra (talk) 09:13, 8 September 2025 (UTC)[reply]

Become? Or require? --jpgordon𝄢𝄆𝄐𝄇 14:42, 8 September 2025 (UTC)[reply]
Hope springs eternal, but don't think they are compatible. -- Deepfriedokra (talk) 14:54, 8 September 2025 (UTC)[reply]

Regulation pigeon

[edit]

Re: WHY?
I know why. Joyous! Noise! 04:09, 10 September 2025 (UTC)[reply]