Wikipedia talk:Twinkle/Archive 49

From Wikipedia, the free encyclopedia

Archive 45Archive 47Archive 48Archive 49

Can't correctly preview my AfD noms lately

After pressing the preview button, the preview appears, but I need to scroll down to see it. Won't allow me to scroll down (rubberband-like snaps back to top of window view). Different mice, different keyboards. Haven't attempted different browsers yet. This is the only process window I'm having problems with. Is there a preference file I may delete? BusterD (talk) 14:10, 20 April 2025 (UTC)

@BusterD. I'm unable to reproduce by clicking random article (Pen Pumlumon Llygad-bychan), nominating it for XFD, adding it to one delsort category, adding a rationale of "Test", and clicking "Preview". Some other variables that could be involved in this are skin, desktop vs mobile, and article wikicode. Can you provide more details please, such as a link to an article where this always happens, which skin you're using, and if you're on mobile? –Novem Linguae (talk) 10:57, 21 April 2025 (UTC)
I rarely edit on mobile. I'm using the 2010 vector legacy skin. I've just tested running an xfd attempt on something already up for speedy. Exactly the same thing I've been describing; the preview works in the xfd box, but I can't scroll down to see it. Yesterday I published an afd without previewing, then did some minor corrections after publication. Is this going to be one of those "Doctor doctor, it hurts when I go like that. Well don't go like that!" things? BusterD (talk) 11:12, 21 April 2025 (UTC)
I've tried different skins just now. I see the same exact symptoms while using vector, vector legacy and monobook. I DO NOT see this snapback issue while attempting XfD in Timeless, and in MinervaNeue I can't figure out how to get to XfD by the twinkle shortcut. BusterD (talk) 11:24, 21 April 2025 (UTC)
I'll try living in Timeless for a while. BusterD (talk) 11:27, 21 April 2025 (UTC)
Ick. BusterD (talk) 11:29, 21 April 2025 (UTC)
OK, I was able to reproduce on the article Sir Thomas Dyke Acland, 11th Baronet. Will investigate some more. https://github.com/wikimedia-gadgets/twinkle/issues/2177Novem Linguae (talk) 11:47, 21 April 2025 (UTC)
I hoped it was something reproducible. Thanks! BusterD (talk) 12:19, 21 April 2025 (UTC)
If I'm required to move somewhere in the 2020's, I can live with it. The popups are more valuable than in the older vector (which just displays some page stats). Thanks for the help with the interface, Novem Linguae. BusterD (talk) 14:14, 21 April 2025 (UTC)

Nomination for merger of Template:R to disambiguation page

Template:R to disambiguation page has been nominated for merging with Template:R from unnecessary disambiguation. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. HouseBlaster (talk • he/they) 03:11, 27 April 2025 (UTC)

Where can I find Twinkle?

Good day, everyone. I would like to ask where I can specifically find Twinkle in my gadget preferences. I'm new here and I’d like to use it as a tool to help prevent vandalism as part of my initial contributions to Wikipedia. Thank you! Arc Rev (talk) 16:19, 24 April 2025 (UTC)

@Arc Rev: To use Twinkle, your account must be autoconfirmed (at least four days old and have ten edits). I believe the option to enable the gadget is hidden from view until then. -- John of Reading (talk) 16:24, 24 April 2025 (UTC)
@John of Reading: Is Twinkle available on the mobile interface, or do I need to switch to desktop view? Arc Rev (talk) 11:33, 27 April 2025 (UTC)
@Arc Rev: I'm not the person to ask, since I've never tried to edit Wikipedia on a mobile phone! But there's a thread from 2018 which says you should switch to the desktop view. Your account is not four days old yet. -- John of Reading (talk) 13:26, 27 April 2025 (UTC)

Twinkle just showed up on my device after four days, and I’ve turned it on now. I noticed that it's now usable on the mobile interface, with "ROLLBACK" and "RESTORE" options appearing. Can any mobile user confirm if this is really Twinkle running on my device, or if it might be from another script? Thanks! — ArćRèvtalk 12:43, 29 April 2025 (UTC)

When did they come up with the idea to make it available for mobile users? It’s a lot more useful now—if this is really Twinkle running on my device. — ArćRèvtalk 12:40, 29 April 2025 (UTC)

@Arc Rev. According to User:Arc_Rev/common.js, it is probably User:10nm/beta.js, which appears to be an unusual way to load WP:ULTRAVIOLET. I do not think Twinkle works on mobile until you install User:Plantaest/TwinkleMobile. –Novem Linguae (talk) 14:33, 29 April 2025 (UTC)
@Novem Linguae: I’m not sure, but how come I couldn’t do reversion even though I installed the script 5 days ago? I only saw the rollback options after installing Twinkle. Also, when I change preferences in Twinkle, they still apply even on the mobile interface. How is that possible? I’m not totally sure if it was that script, but I turned off Twinkle and noticed the rollback options disappeared too. Then when I turned it back on, they came back. Also, if you check my contributions and see a reverted edit, you'll notice "Twinkle" is tagged there—which means I used Twinkle to revert it. I’m just surprised it actually worked on mobile. Could you please delete that script? I don’t really use it, and I just want to confirm if I’m really using Twinkle. Thanks! — ArćRèvtalk 14:52, 29 April 2025 (UTC)
I deleted User:10nm/beta.js for you. Although you have access to edit that page if you want to change anything there in the future.
On desktop, if you want to confirm if something is Twinkle, you can put your mouse over the rollback hyperlink -> right click -> inspect. If the code says something like "tw-rollback", tw is Twinkle, so that's a pretty sure sign that it's from Twinkle.
Whatever day you achieved WP:AUTOCONFIRMED combined with whatever day you activated the Twinkle gadget in Special:Preferences is probably when it started showing up.
I tested it just now on mobile, and while the Twinkle menu is hidden, it does look like the [restore this version] [rollback (AGF)] || [rollback] || [vandalism] Twinkle links show up on diff pages. Interesting. –Novem Linguae (talk) 15:01, 29 April 2025 (UTC)
Thanks for deleting, and for letting me know Twinkle now works on mobile! I really hope they keep improving it—it’s a big help for us mobile users. — ArćRèvtalk 15:08, 29 April 2025 (UTC)
Honestly it is probably an accident that the Twinkle desktop version now partially works on mobile. It is probably a side effect of phab:T328610. Again, it only partially works on mobile (diff pages only, no TW menu). I would recommend installing User:Plantaest/TwinkleMobile so that you get all of Twinkle's features. –Novem Linguae (talk) 15:47, 29 April 2025 (UTC)
Okay, I do have some trust issues when it comes to installing scripts that aren’t listed in my preferences or gadgets. I’m just wondering why User:Plantaest/TwinkleMobile is only mentioned on the Twinkle page and not included in the mobile interface preferences or gadget section. Still, since it’s a recommended script, I think it’s safe. So for now, even if Twinkle on mobile was added by accident, I’ll keep using it because it’s actually helpful. Thanks! — ArćRèvtalk 15:58, 29 April 2025 (UTC)
All gadgets start as user scripts. There's some pros but also some cons to converting a user script to a gadget, so only certain ones get converted, usually ones with a ton of users. –Novem Linguae (talk) 16:25, 29 April 2025 (UTC)

Nomination for deletion of Template:Uw-editwar1 et al

FYI. The recently created Template:Uw-editwar1 through 4 have been nominated for deletion. Dan Bloch (talk) 04:52, 2 May 2025 (UTC)

Why does changing earlier fields reset latter ones?

It's quite disruptive when it happens, e.g. when I change the rationale for a block and the times, set earlier, are the default again... ~Lofty abyss 12:05, 5 May 2025 (UTC)

Rollback options

I've been using Twinkle for years and recently became a New Pages Patroller which required me to make a few changes to my Twinkle preferences. Ever since then, I've lost my Twinkle rollback functions (AGF rollback / Normal rollback / Vandalism rollback) and cannot for the life of me work out how to get those links back. Does anyone know how these are switched on/off via my Twinkle preferences? Now I'm only seeing the standard "undo" revert option (on the diff page) that everyone sees. Rodney Baggins .talk. 12:44, 14 February 2025 (UTC)

@Rodney Baggins: In your Twinkle settings (TW > Config), search for "Show rollback links on these pages" and tick "Diff" there. -- John of Reading (talk) 13:14, 14 February 2025 (UTC)
@John of Reading: That's brilliant, thank you so much! I guess I'd have found it myself eventually but got a bit blinded by the massive sea of options and didn't have time. No idea how it got unchecked in the first place. Cheers, Rodney Baggins .talk. 16:53, 14 February 2025 (UTC)
@John of Reading The rollback links is kind of confusing of how they are different. pressing any one just gives the same "reverted" tag, whether its vandalism or agf. im not quite sure how they work and pressing them feels inconsistent. sometimes it redirects me to the user page, other times it talks me to the article, sometimes it writes stuff in the source editing, other times it doesn't.it very much confuses me.
sorry for not creating a subject, I just didn't think it was that important to JamesEMonroe (talk) 13:36, 12 May 2025 (UTC)
Also for some reason I cant rollback a rollback with it, it just talks me to the wikipedia :rollback page
it does say :
  1. rollback (AGF) - Performs rollback, then provides an edit summary box, pre-filled with an AGF label. AGF stands for Assume Good Faith, meaning the label is written in a friendly encouraging tone as opposed to a stern warning tone. (preview)
  2. rollback - Performs rollback, then provides an empty edit summary box.
  3. vandalism - Performs rollback and opens vandal's talk page so you can easily add an appropriate warning template (does NOT allow edit summary; edit summary will be automatically filled).
However it always asks for edit summary and it always only adds "reverted tag" if none filled out in any rollback feature then the edits summary will be blank, but with "twinkle" and "revert" tags JamesEMonroe (talk) 13:51, 12 May 2025 (UTC)
@JamesEMonroe: I can't give definitive answers! I mostly use the middle option, filling in the edit summary with my reason for doing it. I try to comment on the edit itself, not on whether I think the edit was made in "good faith". One technical difference in the three buttons is what happens if the editor has made another edit by the time you ask for the revert. The first and second buttons will abort your action, so that you can have a look at the new situation. The third button will continue with your revert, wiping out the new edit as well, since you have told Twinkle that the other editor is vandalising.
I reliably end up on the other editor's talk page. There are some options controlling that in the Twinkle preferences.
Your Twinkle edits all seem to be tagged "Twinkle", and those that are reverts are tagged "Tagged, Undo". This edit was tagged "Twinkle, reverted" because you changed your mind a minute later and undid your edit.
Does that help? I suggest you start a new thread for any new questions. -- John of Reading (talk) 14:15, 12 May 2025 (UTC)

Can't find previous maint tags

See Special:Diff/1291007252 as an example. Twinkle was able to find the "essay-like" tag when assessing which tags were already on the article, but failed to find it when trying to add the previous tags into a "multiple issues" template. -- asilvering (talk) 14:03, 18 May 2025 (UTC)

Bulk nomination logging

The recently added ability to bulk-nominate multiple articles for XfD at once is fantastic and long-awaited, but it is causing problems with automatic XfD logs. Rather than inserting a paragraph break via {{pb}} or <br />, the system instead treats each article as a separate entry before listing the reason under the last article, which messes up the numbering and looks confusing.

  1. Article #1: nominated at RM; New name: Article #1
  2. Article #2: nominated at RM; New name: Article #2
    • Reason: Lorem ipsum

Can this be fixed? InfiniteNexus (talk) 22:16, 23 May 2025 (UTC)

Feature request: add commonly used general sanctions and CTOPs notifications, add General Sanctions to list of block presets

Hello, as a heads up I've opened an issue here requesting the addition of some of the more frequently used user talk page notification templates (alert, alert/first, Gs/alert, Gs/sanction, AE sanction, AE sanction/topicban) to the list of single-issue notices, as well as adding General Sanctions to the list of block presets as a clone of Arbitration Enforcement (but with the appropriate text references and list of sanctions to select from). We use these so frequently and it's annoying that I can use Twinkle to handle all sorts of common "normal" administrative actions like blockings and warnings, but cannot currently use it for warnings in CTOPS or blockings for GS-covered issues like WP:GSRUSUKR, for instance. This seems backwards as those remedies are supposed to make it *easier* for admins to deal with disruption in these areas, but the tools haven't quite caught up so ironically it's slower. SWATJester Shoot Blues, Tell VileRat! 01:35, 26 May 2025 (UTC)

Thanks for doing this! It would also be helpful to add general sanctions to the list of page protection presets. Firefangledfeathers (talk / contribs) 12:51, 26 May 2025 (UTC)
Added to ticket. –Novem Linguae (talk) 04:45, 27 May 2025 (UTC)

Multiple issues wrapper for existing tags

If I find an article with two cleanup tags, and add a third, Twinkle gives me the option to wrap the tags in {{Multiple issues}}.

But if I don't select a new tag, it warns me "you must select at least one option", and will not wrap the two existing tags,

It would be convenient if it would do the latter. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:16, 29 May 2025 (UTC)

Adding a user warning to Twinkle

Hello all,

I recently made the Uw-gaming series of user warnings for gaming the system and would like them to be added to Twinkle. How would I ask for them to be included in the next patch? » Gommeh (he/him) 14:02, 28 May 2025 (UTC)

Same goes for the Uw-civil series. I know we can add these ourselves as custom warnings in the Twinkle config, but I feel it may be better for every Twinkle user to have them. » Gommeh (he/him) 15:19, 28 May 2025 (UTC)
Is there documentation somewhere on how to add custom warnings? SWATJester Shoot Blues, Tell VileRat! 16:25, 28 May 2025 (UTC)
There is I think, I can't find it though. It's towards the bottom of the Twinkle config under "Custom warning templates to display". » Gommeh (he/him) 16:51, 28 May 2025 (UTC)
If you think these user warnings are used often enough to be useful for all Twinkle users, feel free to create a ticket at https://github.com/wikimedia-gadgets/twinkle/issues/newNovem Linguae (talk) 19:29, 29 May 2025 (UTC)

Missing (?) Level 4 warning

I've noticed that there is no level 4 warning gor introducing incorrect pronouns, Uw-pronouns. I've used level 4 vandalism to substitute. I wondered if there was a reason for only level 1,2 and 3? Knitsey (talk) 16:56, 28 May 2025 (UTC)

I think you might have better luck asking this question at Wikipedia talk:Template index/User talk namespace. Cheers. DonIago (talk) 20:03, 28 May 2025 (UTC)
Template:Uw-pronouns4 redirects to Template:Uw-generic4. Doesn't appear to be a Twinkle issue yet. –Novem Linguae (talk) 19:26, 29 May 2025 (UTC)
Thabk you for the reply. The option for Template:Uw-pronouns4 doesn't appear as drop down selection option though, even though it is a redirect? Knitsey (talk) 19:32, 29 May 2025 (UTC)
I believe that's normal for Twinkle. If a template doesn't exist then it doesn't appear. Twinkle won't create "redirects" for templates that don't exist. DonIago (talk) 20:17, 29 May 2025 (UTC)

R2 does not appear in my CSD menu items

My CSD menu items does not include any 'R' options (R1, R2, R3 etc). I cannot see how to fix this via the Twinkle prefs... Am I missing something or perhaps this is a bug? Any help much appreciated. Cabrils (talk) 02:48, 3 June 2025 (UTC)

Unable to reproduce. My steps to reproduce were 1) copy User:Cabrils/twinkleoptions.js to User:Novem Linguae/twinkleoptions.js, 2) visit the redirect CIA, 3) TW -> CSD -> R2. It is the first radio button. Can you try visiting the CIA redirect linked above and confirm that you still don't see R2? –Novem Linguae (talk) 05:14, 3 June 2025 (UTC)
@Novem Linguae, thanks very much for the help. I visited the CIA redirect as requested and YES I see R2. Perhaps I've misunderstood the problem: when I visit for example my user page] i do NOT see R2, but maybe R2 should not be appearing there and should only occur on pages that have a redirect on them (like CIA)? Cabrils (talk) 22:41, 3 June 2025 (UTC)
Yes. Exactly. The "R" series of CSDs is only for redirects. "G" is for all namespaces. "A" is only for mainspace. "C" is only for categories. etc. –Novem Linguae (talk) 22:42, 3 June 2025 (UTC)
Great, that has resolved the issue. Thanks very much for your help, much appreciated. Cabrils (talk) 22:43, 4 June 2025 (UTC)
You're welcome. Closing without actionNovem Linguae (talk) 23:00, 4 June 2025 (UTC)

Nomination for deletion of Template:Uw-controversial

Template:Uw-controversial has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Mathglot (talk) 09:31, 14 March 2025 (UTC)

Just an update here for anyone watching this page -- the nomination discussion resulted in the template being deleted, and the template should probably be removed from Twinkle. —tonyst (talk) 13:56, 5 June 2025 (UTC)

Add uw-staleuserpageblanked

Can {{uw-staleuserpageblanked}} be added to the warnings included in Twinkle? Legend of 14 (talk) 16:35, 6 June 2025 (UTC)

@Legend of 14: You can always add it to your Twinkle preferences as a custom warning template at Wikipedia:Twinkle/Preferences § warn. 🌳 Balsam Cottonwood (talk) 16:40, 6 June 2025 (UTC)
I didn't know you could do that. Thanks. Legend of 14 (talk) 16:44, 6 June 2025 (UTC)

Twinkle warn menu for Mobile Interface

Now that rollback options are available in the mobile interface, it would be helpful to add the Twinkle warning menu as well. This would allow users to issue warnings without having to switch to desktop view. Currently, if the "warn after rollback" option is enabled in Twinkle preferences, the feature works. However, if that option is disabled, there is no way to warn disruptive users from the mobile interface. - ArćRèvtalk 13:38, 8 June 2025 (UTC)

Twinkle feature request -- look for previous XfDs

It would be nice if Twinkle could, when you click to XfD something, warn you if the previous XfD was within, lets say, 3 months. Here is a quick example made by Claude: User:Polygnotus/Scripts/PreviousAfDs.js Thanks, Polygnotus (talk) 20:05, 8 June 2025 (UTC)

Good idea. If someone codes it up (submits it as a pull request on GitHub) I'd be happy to test and approve the patch. –Novem Linguae (talk) 21:57, 8 June 2025 (UTC)

Batch deletion

Hello, Twinkle repair people,

I'm finding that batch deletion feature is no longer working correctly all of the time. I use it for broken redirects and G13s and when you select it from the drop-down menu, it works as usual with the CSD G13s but not for the broken redirects. The pop-up box appears but it doesn't list the pages to be deleted in the pop-up box. Any ideas why it works with some pages but not with others? I can list the particular pages if that would help. Liz Read! Talk! 21:46, 23 June 2025 (UTC)

Yes, example pages would be great. Please provide when you get a chance. –Novem Linguae (talk) 08:40, 24 June 2025 (UTC)

Template:Db-t5

Please add the new Template:Db-t5. Gonnym (talk) 07:40, 3 December 2024 (UTC)

Just bumping this so it doesn't get lost. Primefac (talk) 21:15, 5 January 2025 (UTC)
@Novem Linguae can the various pull requests (including this) be merged? Gonnym (talk) 09:26, 22 January 2025 (UTC)
I don't have time right now to review all 20 of them, but can try to take a look at the Db-t5 one. The delay with PRs is that they require manual testing, which is laborious. But breaking Twinkle for 50,000 people and then fixing it is even more laborious, so we're stuck with manual testing for each PR :) –Novem Linguae (talk) 11:49, 22 January 2025 (UTC)
I don't know how to test this here (is there a beta version of Twinkle that can be imported?), but looking plainly at the code and the discussion seems correct. There is no need for notifications. Gonnym (talk) 11:55, 22 January 2025 (UTC)
Any updates on this? Gonnym (talk) 11:24, 20 May 2025 (UTC)
@Gonnym, @LaundryPizza03. I'm happy to report I finally got around to this one. Sorry for the delay. Should be all set to start using CSD T5 in Twinkle now. –Novem Linguae (talk) 04:21, 2 July 2025 (UTC)
I ran into a case where I needed db-t5. –LaundryPizza03 (d) 21:51, 16 February 2025 (UTC)

Prod-nn

Could you add Template:Prod-nn to the PROD option for pages? It only has Template:Prod and Template:Prod-blp. 1isall (talk/contribs) 00:13, 2 July 2025 (UTC)

@1isall, just a quick note: you can add it for yourself as a custom template to your Twinkle preferences under the PROD section. This doesn't make it appear for other users, though. 🌳 Balsam Cottonwood (talk) 00:21, 2 July 2025 (UTC)
Oh, I didn't know I could do that. I will do that now. Thanks for telling me! 1isall (talk/contribs) 00:23, 2 July 2025 (UTC)
Wait, I don't know how to add the template to my preferences specifically. Could I have help with that? 1isall (talk/contribs) 00:27, 2 July 2025 (UTC)
@1isall:: Oh, I'm very sorry, I got it mixed up. There are no custom templates for PROD, only for welcoming and warning, I think. Sorry again, I should be more careful next time. In that case, someone else should help with your request. 🌳 Balsam Cottonwood (talk) 00:30, 2 July 2025 (UTC)
It's okay, and thanks anyway. I will wait for a response to this from someone else. 1isall (talk/contribs) 00:33, 2 July 2025 (UTC)
Okay. 🌳 Balsam Cottonwood (talk) 00:40, 2 July 2025 (UTC)
What I wanted is for someone to go into the gadget's code and adjust it so that Prod-nn appears on the PROD option in the TW menu that is on pages. 1isall (talk/contribs) 20:33, 2 July 2025 (UTC)

I see. Well, I think you (or someone else) would have to make a request here for a change at GitHub or something. There's some information in the header at the top of this page. 🌳 Balsam Cottonwood (talk) 01:04, 3 July 2025 (UTC)

Okay, I'll go and look at the top for that info, and then go over to the GitHub page linked. 1isall (talk/contribs) 01:06, 3 July 2025 (UTC)
Wait, the request is supposed to be made here, on the Twinkle talk page. GitHub is where the changes are made, I think. 🌳 Balsam Cottonwood (talk) 01:10, 3 July 2025 (UTC)
Oh, right. I already made the request somewhere in this discussion, didn't I? 1isall (talk/contribs) 01:10, 3 July 2025 (UTC)
Yes, I suppose you did. We'll just wait until someone who knows what they're doing comes along (which shouldn't be too long; this page has over a thousand watchers). 🌳 Balsam Cottonwood (talk) 01:15, 3 July 2025 (UTC)
Should you or I contact one of those watchers? 1isall (talk/contribs) 01:50, 3 July 2025 (UTC)
No, I think someone will see this soon enough. 🌳 Balsam Cottonwood (talk) 01:51, 3 July 2025 (UTC)
Okay, then. I guess we'll just wait. 1isall (talk/contribs) 01:52, 3 July 2025 (UTC)
Howdy. The process is something like create GitHub issue -> volunteer writes a patch (GitHub pull request) -> I test and merge the patch -> I deploy the patch. So feel free to create a GitHub issue, saving me a step since then I don't have to transcribe it from here. –Novem Linguae (talk) 02:06, 3 July 2025 (UTC)
Okay, I'm going to do that. Thanks! 1isall (talk/contribs) 12:12, 3 July 2025 (UTC)
I recently opened the issue at the GitHub page. 1isall (talk/contribs) 14:44, 3 July 2025 (UTC)

Adding topic when tagging article to expanded by translating another wiki

Hello, when tagging an article to be expanded by translating another language version of the article there appears to be no way to select a suitable topic except by manually adding it to the template afterwards. Having a drop down menu to allow us to select a topic would streamline this process and would avoid having a large backlog of uncategorized articles for translation. Giuliotf (talk) 14:48, 14 July 2025 (UTC)

Query

Hello, Twinkle crew,

Did you disable the batch delete feature? Because I just tried it a few times and it didn't work. What shows up is the pop-up box, but it has no pages listed as existing. It's just blank in the lower part of the box as if there were no pages eligible for deletion. I manually deleted the pages instead but it's a handy feature to have when you are deleting a lot of pages so I hope it can be fixed. Liz Read! Talk! 19:06, 21 July 2025 (UTC)

Oh, I see I already posted a message about this last month. So, an example would be User:AnomieBOT III/Broken redirects/Userspace. I don't have a screen shot of the pop-up box. I also use it with the Dreamrimmer Bot II page for expired drafts (User:DreamRimmer bot II/Reports/G13 eligible drafts) but so far, I haven't had this problem there. Liz Read! Talk! 19:09, 21 July 2025 (UTC)
I have this vague recollection that it only works on certain types of pages and/or with certain types of links. Primefac (talk) 17:24, 27 July 2025 (UTC)

WP:CT/SA

The list of possible AE blocks needs updating. It still has the old IPA instead of the new SA. -- asilvering (talk) 00:21, 5 August 2025 (UTC)

@Asilvering The list is stored at Template:Ds/topics.json. You can update it there. – SD0001 (talk) 09:27, 5 August 2025 (UTC)

Template:obituary

I tried to use the tag feature to add the {{obituary}} tag to an article but I don't think it is one of the options. Does anyone know why this is or think it is worth adding. For context, the tag is:

Thanks, JacobTheRox(talk | contributions) 19:14, 7 August 2025 (UTC)

You can add it just for you on the Twinkle config page. If you'd like it added to Twinkle for everyone, please create a ticket on GitHub to get the process started. –Novem Linguae (talk) 05:41, 8 August 2025 (UTC)

Template:Uw-legal has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Interstellarity (talk) 11:23, 8 August 2025 (UTC)

Compatibility with {{Split}}

Is there a reason why {{split}} is not among the tags that can be applied with Twinkle? Ten Pound Hammer(What did I screw up now?) 16:50, 11 August 2025 (UTC)

Nomination for discussion of Template:Uw-colorblock

Template:Uw-colorblock has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Children Will Listen (🐄 talk, 🫘 contribs) 07:47, 12 August 2025 (UTC)

Concurrency bug

I nominated two pages (Aafreen Dabestani and Shivani Sopori) via the TW > XFD tool. Each page was open on a tab of the same browser (Firefox). I switched tabs back and forth while nominating the pages. The timestamps at WP:Redirects for discussion/Log/2025 August 12 also show a minute difference between the additions, but one nomination was over-written by the other. Expected: either one of the XFD actions should have failed with an edit conflict, or both nominations should have gone in. Jay 💬 08:09, 12 August 2025 (UTC)

Template announcement

Announcing new, single-level notice {{uw-citevar}}. I have added a commented out link to Twinkle banner in the template. If you decide to include it in the installation, please uncomment the link, or if you wish, ping me and I'll do it. Mathglot (talk) 06:47, 13 August 2025 (UTC)

Uw-coi-username red text

Twinkle interface showing the red text presented to users using {{uw-coi-username}}

Currently, Twinkle has this red text that appears when trying to use either {{uw-coi-username}} or {{uw-username}}—it tells people that they should skip warning and go straight to WP:UAA for "blatant" username policy violations. For {{uw-coi-username}}, I think we should get rid of this text. The culture on-wiki these days is shifting towards "warn more, block less" for WP:PROMONAME violations—see e.g. Wikipedia:Administrators' noticeboard/Archive373#Unblocks backlog and Wikipedia talk:Username policy#Promotional usernames where the user has not made promotional edits. For PROMONAME in particular, we generally require not only a promotional username, but also promotional editing in order to give a block (see the text of WP:PROMONAME)—if a user has not engaged in promotional editing and just has a username that may represent a company, then warning is an entirely appropriate first step before UAA. Mz7 (talk) 21:20, 17 August 2025 (UTC)

I would also be open to refactoring the text to read something like: If this user has a promotional username and has made promotional edits related to their username, then the account should be reported directly to UAA (via Twinkle's ARV tab). If the user has not made any promotional edits or is otherwise borderline, use {{uw-coi-username}}. Mz7 (talk) 21:23, 17 August 2025 (UTC)

Template:Please see is broken

A template in use in {{Please see}} is currently up for TDF and it has broken the template, FYI. —Locke Coletc 17:29, 21 August 2025 (UTC)

I noticed this yesterday when doing subst:Please see by hand (not in Twinkle). A fix for this would need to happen in template wikicode, I think, not in Twinkle. –Novem Linguae (talk) 18:16, 21 August 2025 (UTC)
Correct, I'm just providing the belated notification that {{Please see}} says is required (and also in the hope that someone here is an admin and can reverse this and close the TFD until we've determined what will break if this is allowed to happen). —Locke Coletc 18:29, 21 August 2025 (UTC)
I have wrapped the TFD notice with noinclude tags. Does that fix the problem? – Jonesey95 (talk) 18:59, 21 August 2025 (UTC)
I dunno, let's test. —Locke Coletc 19:03, 21 August 2025 (UTC)
No, still broke. I honestly think the TFD notice just needs to be removed. —Locke Coletc 19:07, 21 August 2025 (UTC)
Oh, that code is sneaky. It adds an "r" to "Format link" via an #if statement, so {{Format linkr}} is called by default. I have noincluded the TFD notice at both Format link[r] templates. – Jonesey95 (talk) 19:31, 21 August 2025 (UTC)
That got it. =) So now the question (which should be addressed at the TFD) is, is this going to break other templates that rely on these two? —Locke Coletc 19:35, 21 August 2025 (UTC)

G15

New CSD WP:G15 can be added. {{db-g15}}. Thanks, Cremastra (talk · contribs) 20:42, 4 August 2025 (UTC)

I've created a ticket. voorts (talk/contributions) 21:07, 4 August 2025 (UTC)
Bumping this. TarnishedPathtalk 13:46, 18 August 2025 (UTC)
They're working on it per the tickets. voorts (talk/contributions) 16:00, 18 August 2025 (UTC)
I was going to finish https://github.com/wikimedia-gadgets/twinkle/issues/2199 first. But I agree that this and the other new CSD are kind of urgent, so will pause my work on 2199 and refocus on these two new CSDs. –Novem Linguae (talk) 07:39, 21 August 2025 (UTC)
 Done. –Novem Linguae (talk) 05:04, 24 August 2025 (UTC)

Courtesy notice of changes to templates used by Twinkle

They should not cause any breaking changes, however I would appreciate it if you could review the changes in case. waddie96 ★ (talk) 18:25, 29 August 2025 (UTC)

Template-protected edit request on 23 August 2025

{{Shortcut|WP:TWPREFS|WP:TWPREF|WP:TW/PREF|WP:TW/P}}
+
{{Shortcut|WP:TW/P|WP:TWPREFS}}

Per the WP:LINKBOXES guideline, only the most common and easily remembered redirects should be listed. The least used shortcuts should be removed, this page doesn't need more than 2 similar shortcuts.

The ones above are the most common and easily remembered ones for this page. FaviFake (talk) 12:19, 23 August 2025 (UTC)

If you look at the data (go to each shortcut and click "What links here" in the toolbox), WP:TW/PREF has 631, WP:TWPREFS has 49, WP:TW/P has 20, and WP:TWPREF has 15. So you're basically proposing to remove the most popular shortcut.  Not done for now.
I may still not support this even if you change your edit request. Tinkering with shortcut boxes can be controversial. –Novem Linguae (talk) 14:41, 23 August 2025 (UTC)
Yes, I did look at the link count. My logic was, following the guideline ("only most common and easily remembered")
  • most common: WP:TWPREF or WP:TW/PREF or WP:TWPREFS, i don't mind which one, but there definitely shouldn't be three of them, differing only by 1 char. I'd prefer if it didn't have a slash, because the one below does, but I don't mind.
  • most easily remembered; it'd say it's WP:TW/P for how short it is.
My point is, there definitely shouldn't be 4 near-identical shortcuts for this page. It even forces the actual preferences down, hindering the usability of the page in favour of... more choiches for shortcuts? as long as you remove one or two I'm happy :) FaviFake (talk) 14:58, 23 August 2025 (UTC)
Must understand that many of the shortcuts that you're changing are part of the Wikipedia gestalt even if not used as a link often.... below can give you a clue to the ones we use the most.
Moxy🍁 15:43, 23 August 2025 (UTC)
Yeah, of course, I didn't mean I wanted to change these shortcuts. I meant removing them from the shortcut box, per the WP:LINKBOXES guideline. FaviFake (talk) 16:19, 23 August 2025 (UTC)
 Not done. This edit request proposes deleting the most popular shortcut, WP:TW/PREF. Also, even if you change the edit request to propose different shortcuts, I may still object. Is this the best use of our wiki time and wiki brainpower? –Novem Linguae (talk) 18:00, 24 August 2025 (UTC)
Concur with the above. Primefac (talk) 21:15, 24 August 2025 (UTC)
What is the point of going through every single shortcut box on Wikipedia and removing the least used ones? Because that's basically what FaviFake is doing. Is there any harm in having less common shortcuts in a shortcut box? Guidelines do not always have to be followed. It ain't broke, so why fix it? SuperPianoMan9167 (talk) 19:15, 25 August 2025 (UTC)
SuperPianoMan9167 That's obviously a misrepresentation of what I'm doing, as I explained elsewhere. I only edit shortcuts boxes, to add or remove shortcuts, when I'm already reading a page and I notice the number seems too large. I never go hunting for long shortcut boxes.

Is there any harm in having less common shortcuts in a shortcut box?

Yes, yes there is. As I have explained many times above.
Can I ask you then: what, in your opinion, is the benefit of keeping the least used shortcut in this specific page, given that it pushes down the actual content of the page that every single visitor is coming to the page to see?
Nobody seems to address this issue directly. Do you need a screenshot of the page? How else can I make it more clear?
I'll try to post a screenshot when I come back from my trip, but you can try viewing the page yourself to see the wasted space. FaviFake (talk) 20:10, 28 August 2025 (UTC)
@FaviFake: At the time I made the above comment, I was unaware that you only edit shortcut boxes on pages that you are already reading. I did not know that detail until you pointed it out on your talk page; your contributions suggested to me that you were specifically editing shortcut boxes due to the number of edits you have made in that topic area. SuperPianoMan9167 (talk) 20:14, 28 August 2025 (UTC)
Right, I've got my timing a bit messed up and I thought you were aware.
I should start to only reply to talk pages comments in chronological order. My bad.
Still, could you address the question? The language came out harsher than I intended, but I'm still interested in the answer. FaviFake (talk) 20:20, 28 August 2025 (UTC)
Removing two shortcuts from a box that has four only seems to save a minimal amount of space. To answer your question, yes, a screenshot of the page with the proposed changes would be helpful. In my opinion, the tiny bit of space lost by including redundant redirects in the box is made up for by the benefits to navigation. I and many other editors usually learn shortcuts from these boxes and not "What links here". Besides, this particular page probably has more than four redirects that aren't listed.
I support what you did at Wikipedia:Be bold, where there were so many shortcuts in the box that not all of them were even visible, but I am inclined to oppose removing shortcuts when the page has less than five for the sake of clarity. Redundancy can be good sometimes. SuperPianoMan9167 (talk) 20:51, 28 August 2025 (UTC)
I changed my proposal to only remove one, not two, but I understand this might be hard to find given the mess that this discussion has become.
I've actually decided I don't about this so much that I should take a screenshot and upload it.
I'll just say: I think it would be odd to intentinally come to the page and learn 4 different shortcuts instead of just one, two, or even three, and that I think we should focus more on the WP:READER, which i realise in this case is also an editor, and on the actual page content.
Would you support my change if it only involved removing 1 shortcut? You said you're inclined to "oppose removing shortcuts", not " a shortcut". FaviFake (talk) 20:07, 29 August 2025 (UTC)
I would support removing WP:TWPREF from the box because it is basically the same as WP:TW/PREF (the most popular shortcut) but without a slash. That shortcut would still redirect here, of course, but I've thought about your proposal a bit more and I tend to agree with you that near-identical shortcuts may not be the best idea. So, TL;DR, yes, I would probably support your change if it involved removing WP:TWPREF only, since it is basically the exact same shortcut as WP:TW/PREF. SuperPianoMan9167 (talk) 20:21, 29 August 2025 (UTC)
Yes! We can do it.
Do you think this consensus is enough to reinstate the modified request? If im not mistaken, the opposing editors only point out that they're worried about removing the most popular, which is not the case. FaviFake (talk) 22:07, 29 August 2025 (UTC)
Well, I did change the request to a different one; I said I don't mind whichever you remove, as long as the layout of the page isn't pushed down due to the high number of shortcuts. That's all I'm asking. This is supported by WP:LINKBOXES.
You said about the link counts that WP:TW/PREF has 631, WP:TWPREFS has 49, WP:TW/P has 20, and WP:TWPREF has 15. Do you mind removing the least popular one then? Again:

My point is, there definitely shouldn't be 4 near-identical shortcuts for this page. It even forces the actual preferences down, hindering the usability of the page in favour of... more choiches for shortcuts? as long as you remove one or two I'm happy :)

I'm not sure what's so controversial about a change that's both supported by a guideline and improves the page layout. FaviFake (talk) 10:20, 25 August 2025 (UTC)
It's controversial because sometimes the most minor changes are the ones people debate the most. SuperPianoMan9167 (talk) 19:41, 25 August 2025 (UTC)
I'm a little confused regarding the claim that having four shortcuts is impacting usability. I just viewed the prefs page and saw minimal impact from having a fourth option provided. Perhaps those who feel this would be a significant benefit could provide more context and/or screenshots so that it's more clear how there's a significant impact to usability? DonIago (talk) 19:38, 26 August 2025 (UTC)
Sure, I'll post screenshots here, if that is what it takes for this minor edit to be implemented. I'll take them once I'm back from my trip, but I really hope this will have been been sorted out by then... FaviFake (talk) 20:15, 28 August 2025 (UTC)
When people tell you to stop, you probably should. WP:CIR applies regardless of the guidelines and policies. This shows how paramount your disruptive editing has been. It doesn't matter if you're right, you're still being disruptive and ignoring feedback. – The Grid (talk) 20:06, 29 August 2025 (UTC)
Could you kindly stop following me wherever i comment on talk pages to point me to policies that aren't even relevant, please?
I don't understand what you're trying to accomplish by inserting yourself into every discussion I'm involved in and adding nothing to the actual discussion other than unrelated links and vague (and often slightly incorrect) comment about my editing.
If you want to talk with me, you know this isn't the way to do it. FaviFake (talk) 20:12, 29 August 2025 (UTC)
There's a history on your talk page that states otherwise and you keep ignoring it. Removing it doesn't make it go away. – The Grid (talk) 20:19, 29 August 2025 (UTC)
There's also a history on my talk where I've explained why I do it, it seems you've missed that one!!! I'm distraught. You should really go look for it and send me the permalink like you always do, it's really going to help with this discussion about the length of shortcuts boxes. FaviFake (talk) 22:04, 29 August 2025 (UTC)

A more "reasonable" request

From the previous discussion, it seems to be that:

  • Novem Liguae responded to my first request saying "[...] you're basically proposing to remove the most popular shortcut" and my second one saying "This edit request proposes deleting the most popular shortcut". In both cases, they said that, even if I changed the edit request to propose different shortcuts, they may still object
    • Primefac concurred with the second.
  • SuperPiano said "I would support removing WP:TWPREF from the box [...] TL;DR, yes, I would probably support your change if it involved removing WP:TWPREF only"
  • Donlago asked for more evidence of the issue and other people didn't !vote against or in favour.

So in short there are 2 people in favour of removing 1 shortcut, and 2 people who objected mainly because I was trying to remove the most popular one. So, does anyone object to this?

WP:TWPREFS|WP:TWPREF|WP:TW/PREF|WP:TW/P
+
WP:TWPREFS|WP:TW/PREF|WP:TW/P

FaviFake (talk) 14:05, 1 September 2025 (UTC)

And here's a screenshot of how it currently looks on my end, for Doniago: FaviFake (talk) 14:06, 1 September 2025 (UTC)
Okay, then I see the same thing, which is why I said that I saw minimal impact. Unless it can be demonstrated that there's more practical adverse effects to having four shortcuts instead of three, I don't see myself supporting this proposal. Is it not possible that deleting one of the shortcuts would ultimately have a greater adverse impact than allowing all four shortcuts to remain intact, which seems to have an extremely minor impact on the usability of the page? Is there something I'm missing here? DonIago (talk) 05:01, 2 September 2025 (UTC)
The only guideline in support of the change would be WP:LINKBOXES. Other than that, you're correct, there's no other benefits. Agree to disagree, I guess. Thanks for explaining your position. FaviFake (talk) 08:48, 2 September 2025 (UTC)
I am not in favor of changing these. And I am disappointed that we've written 1,917 words about this minor issue. Seems inefficient. –Novem Linguae (talk) 17:54, 1 September 2025 (UTC)
Concur. I honestly don't care which way this goes because we are now in BIKESHED territory and should just all walk away. Primefac (talk) 18:16, 1 September 2025 (UTC)
We wouldn't have written so many words if half of the partecipants hadn't kept opposing the change without even providing a reason... FaviFake (talk) 22:35, 1 September 2025 (UTC)

Disabling deletion discussion notification for accounts blocked more than 7 days and locked accounts

One thing I have found very frustrating about Twinkle is how it automatically notifies accounts which are currently blocked by default. I kind of view these notifications as counterproductive since the OP is unlikely to be able to comment on the discussion. The typical XFD discussion is about 7 days, which is why if the block expires more than 7 days from the date of notification I don't see it as productive to send a notification.

We can do the same for speedies where the user is blocked indefinitely or locked because there isn't a good reason to notify a user who is blocked and it can be perceived as gravedancing.

For locked accounts as well if the lock is because the user has passed on it is quite counterproductive to notify, as with accounts banned by the WMF or the Wikimedia community.

TL;DR: it would be helpful to skip automated discussion notification if the user being notified is currently blocked (but then don't turn the help message off). Aasim (話すはなす) 18:57, 2 September 2025 (UTC)

Counter example: there could be people watchlisting the blocked user's page that would like to participate in those discussions / help with cleanup. It's not an oppose from me, but I would want to see support from multiple people before changing this. –Novem Linguae (talk) 06:53, 3 September 2025 (UTC)
I don't have a fixed timeline in mind, but it's a good idea. Blocked editor talk pages being filled up with eg. notifications of speedy category deletion feels a bit rude to the blocked editor. CMD (talk) 07:03, 3 September 2025 (UTC)
For many locked accounts of deceased editors, their talk page stalkers will appreciate the notifications. —Kusma (talk) 08:04, 3 September 2025 (UTC)
Maybe set this feature as on by default with a template to be added to the user talk page to opt out. So if page stalkers want the page to continue to get notifications, they can set it. There is a very minimal amount of pages that actually have stalkers that want to continue to have these notifications. Gonnym (talk) 21:07, 4 September 2025 (UTC)

Announcing new user notice template uw-rfcbefore

Hello. Announcing new, single-level user notice {{uw-rfcbefore}}. If you decide to include it in the Twinkle installation, please lmk so I can add the Twinkle banner to the doc. Or, just feel free to add it yourself. Thanks, Mathglot (talk) 02:17, 7 September 2025 (UTC)

In case the Twinkle community is involved or impacted, here's a heads-up for the following discussion:

Wikipedia talk:Deletion policy#Incubation and the draftify-related standardized language.

Regards CapnZapp (talk) 17:21, 10 September 2025 (UTC)

Compatibility with temp accounts

As I wrote in WP:VPT#Compatibility of gadgets, scripts, bots, and edit filters with temp accounts, I wanted to ask you to check if Twinkle is compatible. Here's our documentation for developers; in particular, see the section How should I update my code?. Thank you! SGrabarczuk (WMF) (talk) 08:53, 1 September 2025 (UTC)

Do any talk page watchers have any ideas about things likely to break that we should take a look at in advance? –Novem Linguae (talk) 12:12, 3 September 2025 (UTC)
I know I'm late here but I imagine everything that is geared towards IP users will need to be deprecated and replaced with (or modified to be) things geared towards temp account users. tony 21:18, 10 September 2025 (UTC)

UTTP and Twinkle (Emergency)

So for some background context the file police man Ganson was created as a parody of the character Officer Short Shrift from The Phantom Tollbooth. I couldn’t help but notice that this image is used by both Twinkle the and UTTP a group of online trolls known for not only being silly and trolling online but promoting sextortion on sites like Discord and SkibidiFarms. I am posting this message on both Twinkle and Police man ganson. Its Lido (talk) 22:14, 19 September 2025 (UTC)

Meh. Primefac (talk) 23:06, 19 September 2025 (UTC)
This doesn't seem like an emergency. Would you like us to do something, or are you just informing us of the history of the icon? –Novem Linguae (talk) 03:31, 20 September 2025 (UTC)
It’s used for sextortion Its Lido (talk) 03:49, 20 September 2025 (UTC)
You're not presenting your case very clearly. You haven't told us what you want us to do (remove it I assume?), and terms like Officer Short Shrift, The Phantom Tollbooth, UTTP, and sextortion are unfamiliar to me. You've provided no wikilinks or external links. But despite that, you may be right. I'm not sure it's good to have a Twinkle icon that basically looks like this guy. His personality and identity doesn't seem like something we would want people to associate Twinkle with. I think whoever made the icon was probably going for "generic police officer" rather than trying to associate Twinkle with this guy.
That icon is used on WP:TWINKLE and also in multiple userboxes. We should probably figure out a replacement square image before swapping. Would someone like to make something and/or look for suitable replacement images on Commons and suggest them here? –Novem Linguae (talk) 04:55, 20 September 2025 (UTC)
Uh... I think we should probably have a discussion before we start panicking about finding a replacement. Honestly, I don't really care what icon we use, but I don't see a compelling reason to change. Primefac (talk) 14:25, 20 September 2025 (UTC)
Ever heard of the UTTp search it up and they use an image called police man game on inspired by officer short shrift and twinkle shares the image:
links
https://m.youtube.com/watch?v=IjPXHdJ4Tls
lhttps://www.reddit.com/r/youtube/comments/1bpjnua/does_anyone_know_where_the_logo_of_the_uttp_comes/
this person right here was extorted into self harm by the uttp and made a video about it later in life https://m.youtube.com/watch?v=ILsftmMkzWo
Anyways for more information search up UTTP, Police man Hanson, officer short shrift a character associated with trolling. Its Lido (talk) 14:34, 20 September 2025 (UTC)
The current Twinkle logo, File:Police man Twinkle Head.svg, appears to have been used since at least 2007. The logo isn't going to be changed just because of a couple of random YouTube videos of questionable legitimacy. 88.97.192.42 (talk) 19:59, 20 September 2025 (UTC)
And this isn't an "emergency" by any definition of the word - misuse of that word tends to undermine the effectiveness of using the word for actual emergencies. 88.97.192.42 (talk) 20:02, 20 September 2025 (UTC)
Well its associated with a group that doxxes people. Its Lido (talk) 20:15, 20 September 2025 (UTC)

@Primefac: I feel like this thread should be closed since it clearly isn't going anywhere productive. 88.97.192.42 (talk) 20:48, 20 September 2025 (UTC)

This discussion doesn't seem finished to me yet. –Novem Linguae (talk) 21:14, 20 September 2025 (UTC)
The OP seems to have the cause and effect, or the timeline, backwards. This "policeman ganson" image appears to have existed on Wikipedia since 2005, when it was uploaded from a PD clipart site. YouTube was created only a couple of months earlier than the image's upload date, so it seems improbable that the image came from a YouTube source. It is much more likely that some YouTubers have adopted the image for their own purposes, which, since it is public domain, they are welcome to do. It should not affect us. The Reddit thread linked above appears to be speculation. As for the resemblance between our image and Officer Short Shrift, all I can say is that there are a lot of male-presenting, overweight police officers who wear blue uniforms and caps with badges on them. It's practically a stereotype. In addition, Officer Short Shrift has a flashing red and yellow light on his cap and has a wheel instead of legs. – Jonesey95 (talk) 22:50, 20 September 2025 (UTC)

Feature request: WP:G5 general sanctions enforcement CSD

Currently, Twinkle offers the normal WP:G5 for banned/blocked users, but not the version for general sanctions enforcement, which is used when a page has been created by a non-extended confirmed editor in violation of WP:ECR. The template in this case is {{db-gs}} and it takes a topic code as the argument. The notice template is {{db-gs-notice}} and it takes an additional named code parameter containing the topic code. Please consider adding this as an option in the CSD menu. Thanks, OutsideNormality (talk) 01:15, 24 September 2025 (UTC)

Double checking feature

There are some popular Twinkle tasks (e.g., XFD) that have specific considerations that are not always clear to taggers. The discussion @Tamzin started about WP:U5 deletions has made me wonder whether Twinkle could be extended to warn taggers when they're likely making a mistake (e.g., trying to add U5 to an experienced editor's User: page, or A1 within the first 10 minutes of the article's creation). What do you think? WhatamIdoing (talk) 22:40, 24 September 2025 (UTC)

I like this idea, specifically for heuristics that will almost always mean the tagging is incorrect. You could probably do both age and length checks for A1 or A3; very few things >100ww will qualify for either. And a recent-creation check for A10 and R3, set at 4 months, which is the point where policy says pages are "almost never" considered recent. An invalid U2 would also be very easy to check for, but maybe not necessary; the only times I can recall seeing that criterion misused have been people overlooking one of the exceptions. -- Tamzin[cetacean needed] (they|xe|🤷) 09:19, 25 September 2025 (UTC)
I proposed adding age-based checks 6 years ago—wow, how time flies!—in 702. Response wasn't very enthusiastic, but probably should be done anyway. – SD0001 (talk) 10:02, 25 September 2025 (UTC)
Seems like a decent idea. But needs a GitHub ticket, an engineering specification ("when exactly X happens, have Twinkle do exactly Y". So for example, "when a user clicks the CSD A1 radio button, do an AJAX API call to figure out the page creation datetime. if that datetime is less than 10 minutes ago, display Z red warning message in the Twinkle CSD interface, and disable the submit button until a different CSD is selected, at which point re-enable the button"), and a volunteer dev to code it up. I was trying to keep up with this kind of stuff for awhile but fell behind. I really need people's help with GitHub tickets and engineering specifications, since it's too much for me to do by myself. –Novem Linguae (talk) 10:25, 25 September 2025 (UTC)
Probably best to engineer it as an "Are you absolutely sure this is what you mean to do?" than a hard disallow, as there might always be some edge case. For instance, if a user makes a bunch of A1able articles and then gets blocked for disruptive editing, there's no need to wait on tagging those, because they're blocked and won't be able to expand the articles. -- Tamzin[cetacean needed] (they|xe|🤷) 10:29, 25 September 2025 (UTC)

Template:Too many photos is not on Twinkle

In the "Article maintenance tagging" popup, there is no mention of Template:Too many photos. I found an article that had too many images, but I couldn't find the template. - Sebbog13 (talk) 11:44, 27 September 2025 (UTC)

You can go to TW -> Config, and there is a spot to customize which templates show up for you. And/or you can file a ticket at https://github.com/wikimedia-gadgets/twinkle/issues/new to get it added for everyone. –Novem Linguae (talk) 14:55, 27 September 2025 (UTC)

Curiosity: How does some of the modules notify administrators?

When looking at User:Sandbox for user warnings, it said:

Please do not use this page to test advance reporting and vetting (ARV), speedy deletion (CSD), nominate for deletion (XFD), or request page protection (RPP), as these notify administrators.

I'm just curious about what this means, and how it notifies administrators. While I have sometimes "tested" the templates in the editor in sandbox pages/user space, I have not actually been publishing the changes; only viewing the preview before abandoning the edit(s). RaptorsFan2019 (talk) 15:51, 30 September 2025 (UTC)

It doesn't mean "notify" as in "ping" or any direct 1-1 notification.
  • ARV lets you automatically file reports to WP:AIV, WP:SPI, WP:AN/3, etc., and does so by directly editing those pages. Some administrators monitor those pages.
  • RPP files a report at WP:RPP, which is monitored by some administrators.
  • CSD adds a few categories to the page which some administrators monitor.
You're "notifying" admins by putting things on pages or in categories which admins check often. --tony 15:58, 30 September 2025 (UTC)
I think "Please do not use this page..." is referring to the fact that some Twinkle reporting functions make edits to both the test page (the sandbox in this case) and a noticeboard. The noticeboard edit is what notifies admins. Hope this helps. –Novem Linguae (talk) 18:02, 30 September 2025 (UTC)

Query

Hello, Novem Linguae and other tech-savvy editors,

I ran into a case today where an admin used the "Nuke" feature to delete dozens of articles but the Nuke feature doesn't delete either Talk pages or redirects of those articles so these had to be deleted separately later which is quite a pain. And I was remembering several times where I came here asking about a similar feature on Twinkle because Twinkle deletes articles/drafts/pages but doesn't delete the talk pages of any redirects that exist. You all were working on this feature and I wanted to follow-up and ask how it was coming along. Is it still a change at somw point in the distant future? You would think that this would be an uncommon situation but it actually comes up every day.

Thanks for any update you can provide. Liz Read! Talk! 21:28, 30 September 2025 (UTC)

Why can't it handle more than two blocks?

As partial blocks are being used more I'm often running into this problem, making me unable to use it... ~Lofty abyss 17:40, 1 October 2025 (UTC)

Coding Twinkle to handle multi-blocks would be complicated and would need additional engineering time. So as a band aid measure, we have it display a link to Special:Block, which can handle multi-blocks. A patch to Twinkle adding support for multi-blocks would be welcome. –Novem Linguae (talk) 22:28, 1 October 2025 (UTC)

Why delay in merging pull requests by maintainers?

We see fairly frequent bug reports and feature requests in this page. There are several issues in the code that need improvement, which volunteers are willing to help. In spite of this several pull requests are pending approval without any comment, many from several months ago. I understand maintainers are volunteers as well, but it is not good to ignore pull requests for so long and discourage those who are willing to contribute code. 2409:40F2:314C:15B9:8000:0:0:0 (talk) 15:03, 10 October 2025 (UTC)

Sorry about that. I'm a volunteer and I have been busy. It's on my todo list to spend like a week and clear out the PR queue as soon as I get some free time. PRs take awhile to approve because I manually test each one, and that's not very fun. And reading code is a high-brainpower activity. However I think the manual testing makes sense and must be done because 1) Twinkle has like 40,000 users or something so any bugs will affect a lot of people, and 2) we have a lot of first time contributors / newer contributors who write patches in this repo and they don't always manually test them on testwiki before submitting their PR.
WikiConference North America is next week. Maybe I can carve out some time there to work on this. Thanks for your patience. –Novem Linguae (talk) 02:34, 11 October 2025 (UTC)
If it matters I'll take whatever you can give, whenever you can give it. You're everywhere helping out with a ton of our vital tools, which is great, but if it's too much then I'd rather wait another week or two. Enjoy WCNA! Primefac (talk) 20:34, 11 October 2025 (UTC)

Nomination for discussion of Template:Image hoax

Template:Image hoax has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Polygnotus (talk) 14:23, 16 October 2025 (UTC)

Template:Uw-controversial

This was deleted and should probably be removed from Twinkle.--Launchballer 03:05, 19 October 2025 (UTC)

@Novem Linguae: See above. Thanks, Polygnotus (talk) 03:10, 19 October 2025 (UTC)

Maintenance tags don't go below Template:Family name hatnote

Nomination for discussion of Template:Uw-hoax

Template:Uw-hoax has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. --pro-anti-air >(talk)< 20:12, 21 October 2025 (UTC)

Nomination for discussion of Template:Db-notwebhost-notice

Template:Db-notwebhost-notice has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Sophisticatedevening(talk) 16:23, 30 October 2025 (UTC)

Nomination for discussion of Template:Db-u5

Template:Db-u5 has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym (talk) 11:34, 31 October 2025 (UTC)

G15 doesn't tag article creator?

Hi, I just used the G15 speedy deletion for the first time, but it seems that it didn't put a notice on the user talk page? Is this intentional? Fram (talk) 15:22, 27 October 2025 (UTC)

Interesting bug. This has to do with the Twinkle config at User:Fram/twinkleoptions.js only writing true values and assuming anything absent is false. But in reality, it should also write the false values, that way it can assume anything absent should use the default value.
This is a hard bug to fix properly. But it has an easy workaround. You can just visit your Twinkle preferences -> "Notify page creator when deleting under these criteria" -> tick G15 -> Save. Hope that helps. –Novem Linguae (talk) 19:04, 27 October 2025 (UTC)
Thanks! Perhaps in the preferences, an option "all" can be added to overrule the individual toggles of when to notify/not to notify? Not mega-important, but I can imagine that others have the same issue and perhaps don't even realise it. Fram (talk) 19:17, 27 October 2025 (UTC)

Other G15 bugs?

I don't know if this adds anything new, but I flagged this at AfC and was sent this-a-way, so am copypasting the salient part here:
Just to be clear, this refers to when I'm actually deleting a page, not just requesting speedy (ie. the 'Tag page only, don't delete' box is unselected).
I do have the 'Notify page creator of page deletion' box selected by default.
And before anyone asks, I also have the page creator notification selected in my Twinkle prefs for G15 (in fact, all bar R2/R4/X3), so Novem's suggested workaround won't help.
Best, -- DoubleGrazing (talk) 10:53, 2 November 2025 (UTC)

"CSD U5 has been repealed."

"CSD U5 has been repealed. It has been replaced with U6 (procedural deletion of some previously U5-eligible pages) and U7 (a much narrower reworking of U5). Please see those criteria to determine if either applies." just appeared on something Ione normally tags as U5 🇵🇸🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦🇵🇸 15:05, 30 October 2025 (UTC)

Wikipedia talk:Speedy deletion#RfC: Replacing U5 with a primarily procedural mechanism ScrabbleTiles (talk) 17:38, 30 October 2025 (UTC)
This does need to follow through to Twinkle, I think. 🇵🇸🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦🇵🇸 18:48, 30 October 2025 (UTC)
Yes, they should remove U5 and add U6 and U7. ScrabbleTiles (talk) 18:56, 30 October 2025 (UTC)
Working on it! Chaotic Enby (talk · contribs) 14:45, 31 October 2025 (UTC)
I'm giving this high priority and carved out some time to work on it today. Will do a round of code review with Chaotic Enby to finish this up, then will merge and deploy it. –Novem Linguae (talk) 23:44, 2 November 2025 (UTC)
Noted, thanks! Chaotic Enby (talk · contribs) 02:32, 3 November 2025 (UTC)
 DoneNovem Linguae (talk) 06:34, 4 November 2025 (UTC)

Nomination for discussion of Template:Uw-ablock

Template:Uw-ablock has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. — AP 499D25 (talk) 12:57, 4 November 2025 (UTC)

Nomination for discussion of Template:Uw-ipevadeblock

Template:Uw-ipevadeblock has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. — AP 499D25 (talk) 13:08, 4 November 2025 (UTC)

Application of IP user welcome templates to temporary accounts

It is obvious that temporary accounts starting with ~2025- are unregistered. It might be best if the Twinkle • Welcome user menu only listed the IP user welcomes for temporary accounts, perhaps renamed to Temporary account welcomes. Peaceray (talk) 16:56, 4 November 2025 (UTC)

FixedNovem Linguae (talk) 18:19, 4 November 2025 (UTC)
Thank you Peaceray (talk) 18:27, 4 November 2025 (UTC)

Future move

At some point within the next few days, someone not me is going to end up moving {{uw-multipleIPs}} to {{uw-multipleTAs}} or similar. Probably not that big a hassle to deal with but thought I'd bring it up just in case. 184.152.65.118 (talk) 19:12, 3 November 2025 (UTC)

Should be fine as long as a redirect is left behind. Although wouldn't hurt to patch it at some point. –Novem Linguae (talk) 19:29, 3 November 2025 (UTC)
Maybe I'll just post it at RM/TR then, given the backlog is currently days old by the time it clears it probably will be the fourth. 184.152.65.118 (talk) 19:42, 3 November 2025 (UTC)
Another important note regarding the uw-multipleTAs template: Twinkle leaves a pre-filled "Vandalism using multiple IPs [on page name]." edit summary when placing the uw-multipleTAs template. That edit summary should be changed to "Disruption using multiple temporary accounts [on page name].". — AP 499D25 (talk) 13:16, 4 November 2025 (UTC)
FixedNovem Linguae (talk) 18:37, 4 November 2025 (UTC)

Template:Disputed-section

Twinkle did not recognize the redirect Template:Disputed-section in the edit Special:Diff/1320472472. Thebiguglyalien (talk) 🛸 22:16, 4 November 2025 (UTC)

@Thebiguglyalien. Weird. I couldn't get {{Disputed}} to show up as ticked when I tested this on testwiki. Diff. I also don't see it in the wikicode. So that's interesting that you were able to get an edit summary that included it.
I think {{Disputed-section}} is for sections, not the entire article. That's probably why Twinkle isn't detecting it on testwiki. If the template had been {{Disputed}}, it probably would have worked. –Novem Linguae (talk) 20:03, 5 November 2025 (UTC)

Another twinkle thing with temp accounts

Can we get the block evasion block reason/template added for accounts as well as IPs? Doesn't really make sense to block temp accounts as socks when it's essentially block evasion as an IP. ScottishFinnishRadish (talk) 13:33, 5 November 2025 (UTC)

@ScottishFinnishRadish. Hey there. Can you help me spec this out? Is this a request to add a template to the "TW -> Block -> Template options -> Choose talk page template" dropdown, or something else? If so, which template exactly should be added? Thanks. –Novem Linguae (talk) 21:24, 5 November 2025 (UTC)
There's a block option in twinkle for IPs for Block evasion that doesn't show up for accounts. I'd like it added to the block drop-down for accounts. ScottishFinnishRadish (talk) 21:25, 5 November 2025 (UTC)

Nomination for discussion of Template:Shared IP advice

Template:Shared IP advice has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Sugar Tax (talk) 10:06, 6 November 2025 (UTC)

Template:Proposed deletion notify

Template:Proposed deletion notify includes some odd language that has been described as hostile and confusing. For example, it implies the article could be speedily deleted after they decline the PROD, which should almost never happen. Multiple editors have suggested changes at Template talk:Proposed deletion notify going back to 2018, but it has never happened. Unless there are objections, I intend to change the text to be clearer and more neutral. Courtesy pings to Mortee and Hinnk. —Rutebega (talk) 20:45, 9 November 2025 (UTC)

The discussion is at Template talk:Proposed deletion notify § Rewording. Primefac (talk) 20:51, 9 November 2025 (UTC)
Is this just changing the template wording? If so, then the changes will probably be invisible to Twinkle and have little chance of breaking it. Should be OK to Closing without actionNovem Linguae (talk) 16:10, 10 November 2025 (UTC)

How can I fix my problem with Twinkle

I created User:Vitorperrut555/Welcome temp, and instead with welcome, shows {{subst:}}. How can I fix this problem? VitorFriboquen :] (Talk) 21:21, 11 November 2025 (UTC)

Context: OP is trying to add User:Vitorperrut555/Welcome temp as a custom welcome using Twinkle preferences. User:Vitorperrut555/twinkleoptions.js. Will take a closer look at this if I get time. –Novem Linguae (talk) 23:20, 11 November 2025 (UTC)

jquery.ui

Since jquery.ui is now deprecated, do we have a plan to migrate Twinkle to use Codex in the future? Or it will still use jquery.ui? Nvdtn19 (talk) 14:53, 9 November 2025 (UTC)

No plan at the current time. It'd be a very large amount of work to redo something that is still working. And my overall impression of Codex is that it is unfinished, i.e. it does not have feature parity with previous mw:MediaWiki front end frameworks such as mw:OOUI. –Novem Linguae (talk) 16:07, 10 November 2025 (UTC)
I think I can help resolve this issue in the future, of course when the Codex library is more stable. Plantaest (talk) 12:40, 16 November 2025 (UTC)

Hi!

I just wanted to say that twinkle is an awesome tool! ‎ ‎ BJayden (talk) 13:18, 17 November 2025 (UTC)

Nomination for discussion of Template:Db-notwebhost-deleted

Template:Db-notwebhost-deleted has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. mwwv converseedits 17:39, 18 November 2025 (UTC)

This may have been covered elsewhere, but I've just left a welcome note on a temp account, and notice that it still recommends creating an account in order to hide the user's IP Address. I guess the text just needs updating?

User talk:~2025-34732-25

You are welcome to edit without logging in; however, creating an account is free and has several benefits (for example, the ability to create pages and upload media). An account also has more protection against revealing your IP address.

Chaheel Riens (talk) 16:40, 21 November 2025 (UTC)

Technically, Wikipedia:Temporary account IP viewers still have access to the IP. Not sure if that's why it remains in the note. —Bagumba (talk) 16:52, 21 November 2025 (UTC)
Probably. I don't see anything in this quote that looks incorrect. I lean towards not changing it, although anyone is free to make changes at Template:Welcome-unregistered. –Novem Linguae (talk) 18:11, 21 November 2025 (UTC)
Closing without actionNovem Linguae (talk) 18:11, 21 November 2025 (UTC)

MediaWiki:Gadget-twinklewarn.js#L-1989

Since the template {{Shared IP advice}} will be deleted in the future, I think the maintainers should delete lines related to that template. Thanks. Plantaest (talk) 18:09, 18 November 2025 (UTC)

It is unclear if templates related to IPs will be mass deleted, marked historical, renamed/repurposed for temporary accounts, etc. There are various discussions about it going on at places such as Wikipedia:Templates for discussion/Log/2025 November 11#Template:Uw-ablock and Wikipedia:Village pump (miscellaneous)#So, what do we do with the WP:BLOCK notice templates for anonymous/IP users?. Personally, I am in favor of keeping these templates. –Novem Linguae (talk) 21:54, 18 November 2025 (UTC)
If you are favor of keeping this template then should have participate in this discussion? It's currently under deletion review. Nvdtn19 (talk) 00:22, 19 November 2025 (UTC)
I can't find the deletion review. Feel free to link to it. –Novem Linguae (talk) 01:20, 19 November 2025 (UTC)
Sorry. Actually there's no DR about it, but there's already a TFD discussion which I already linked. Nvdtn19 (talk) 03:57, 19 November 2025 (UTC)
@Novem Linguae: Hi Novem, I'm not very active here, so I'm not sure about this. I think you will have the best approach for this issue. Regards, Plantaest (talk) 08:19, 19 November 2025 (UTC)
Well, the wiki is moving faster than I'd like to delete every IP related template. I bow to their wisdom. It doesn't make sense to keep {{Shared IP advice}} code in Twinkle if the template doesn't exist. I filed https://github.com/wikimedia-gadgets/twinkle/issues/2247Novem Linguae (talk) 18:18, 21 November 2025 (UTC)

Discussion at Wikipedia:Village pump (proposals) § Have Twinkle stop notifying blocked users of deletion nominations?

 You are invited to join the discussion at Wikipedia:Village pump (proposals) § Have Twinkle stop notifying blocked users of deletion nominations?. –Novem Linguae (talk) 09:38, 25 November 2025 (UTC)

ARV for temporary accounts

I don't know where the best spot is for this but it might be useful to add the ability to include multiple temporary accounts in the ARV wp:AIV feature for users with wp:TAIV rights to be able to report when the same person is vandalizing from multiple temp accounts without revealing the IP address. -- Lenny Marks (talk) 14:53, 26 November 2025 (UTC)

Thanks for creating this tool

A lifesaver! I'm really grateful to whoever contributed to the mammoth process of building such a well-oiled tool! Kajjul (talk) 02:59, 28 November 2025 (UTC)

Add a new default tag

Hey, Novem. Was wondering if you could add a new cleanup template I had created earlier today as a default cleanup template, it's {{Table accessibility cleanup}}. If you don't want to, that is also totally fine. Thanks! Cowboygilbert - (talk) ♥ 22:23, 29 November 2025 (UTC)

If it's OK, let's wait a bit. The tag is brand new, so it could get merged, TFD'd, not catch on, etc. Feel free to circle back to this in 6 months if you still feel like this tag should have equal weight to other tags in the TW -> Tag module. And don't forget you can add it as a custom tag for just your Twinkle by going to TW -> Config -> Tag -> Custom article/draft maintenance tags to display. –Novem Linguae (talk) 00:56, 30 November 2025 (UTC)

GS speedy deletion notification doesn't work?

Hi Twinkle team. I nominated this page for speedy deletion via the "violation of a general sanction" option (thank you for adding that), but the notice here doesn't appear to have worked properly? This also previously happened here on the article 3 Jat. I am on vector 2010. 45dogs (they/them) (talk page) 06:08, 3 December 2025 (UTC)

Delete "Shared IP" module?

There's been a proposal to remove the module "Shared IP", which is used to place templates on IP talk pages. Here's an example talk page if you want to open it and remind yourself what it does: User talk:192.0.2.16.

Anyway, thoughts on deleting the "Shared IP" menu item from Twinkle? –Novem Linguae (talk) 11:30, 5 December 2025 (UTC)

If the reasons for removing it are to reduce technical debt, then that's a no-brainer. —k6ka 🍁 (Talk · Contributions) 15:28, 5 December 2025 (UTC)

Nomination for merger of Template:Uw-aadblock

Information icon Template:Uw-aadblock has been nominated for merging with Template:Uw-adblock. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Sugar Tax (talk) 17:04, 10 December 2025 (UTC)

RM/TR generator failed to find target section

Twinkle could not find the correct section at WP:RMTR to place a new technical request; can you please investigate? –LaundryPizza03 (d) 09:59, 13 December 2025 (UTC)

It's happening because of this edit. Twinkle tries to place the request just above the text ==== Requests to revert undiscussed moves ====, which is no longer present. – SD0001 (talk) 10:15, 13 December 2025 (UTC)
Reverted. –LaundryPizza03 (d) 11:17, 13 December 2025 (UTC)
Because the user cited Template:Anchor/doc#Not_below_the_heading, I'd suggest instead changing both the header and the Twinkle source code. –LaundryPizza03 (d) 11:19, 13 December 2025 (UTC)

Updates to BLP unreferenced

Templates {{BLP unreferenced}} and {{BLP unreferenced section}} now have two new params to manage a more robust 'find-sources' string, similar to what {{unreferenced}} and several other templates already have. Thanks, Mathglot (talk) 02:00, 13 December 2025 (UTC)

Speaking of which, I also noticed that {{Prod blp}} has a "concern" parameter that isn't supported by Twinkle and could be useful. –LaundryPizza03 (d) 11:24, 13 December 2025 (UTC)

speedy: add admin-only "Delete" and "Decline" buttons for quick parsing

Hello friends. A patch has been written to add "Delete" and "Decline" buttons to CSD templates for admins only. If you have any comments on it, feel free to leave them here or at https://github.com/wikimedia-gadgets/twinkle/pull/2248. As the patch is written right now, these will be always-on for admins. –Novem Linguae (talk) 00:59, 23 November 2025 (UTC)

I'm perfectly okay with making them an option that can be activated or deactivated in the Twinkle preferences. Chaotic Enby (talk · contribs) 01:31, 23 November 2025 (UTC)
Let's only do that if people ask for it. Less complexity is good :) –Novem Linguae (talk) 04:49, 23 November 2025 (UTC)
I've cross-posted at WT:CSD. To me, deleting a page is quite fiddly, so I would support this change. You have to click a small TW menu button, then find the CSD in the list, and then go back to the middle of the screen to click delete. Especially with super-easy CSDs like U6, this takes up a substantial part of your time. —Femke 🐦 (talk) 08:57, 12 December 2025 (UTC)
If there is a CSD tag on the page, opening Twinkle's delete option pre-fills the deletion rationale, which means all that is needed is to open TW and click "delete". Primefac (talk) 14:35, 14 December 2025 (UTC)
Strong support. This would make CSD patrolling much easier. Thank you, CE, for writing this, and the others for reviewing it. I disagree with the other editor (I'm guessing that's SD0001?) that this should take two clicks or needs a special label – speedy deletion should be speedy and making it as easy as possible to carry out (once the necessary checks have been done) is important. Toadspike [Talk] 09:09, 12 December 2025 (UTC)
Deleting a page should take at least two clicks, the second to confirm. Otherwise accidental clicks can cause accidents. Without twinkle, the delete button is quite straightforward, as it prefills the page for confirmation. Graeme Bartlett (talk) 11:03, 12 December 2025 (UTC)
I would prefer the implementation with two clicks too, to make it less scary to delete stuff. Still saves one click, and the button is bigger than the TW menu button, so should save 40% of time? —Femke 🐦 (talk) 13:39, 12 December 2025 (UTC)
Deletion should be quick, but not single-button-whoops-I-just-deleted-the-page quick. Agree the (existing) two-click solution (whether by opening Twinkle or using the standard Delete button) is sufficient. Primefac (talk) 14:35, 14 December 2025 (UTC)
The existing solution is three clicks for me. Click twinkle (small button), click CSD (small again), and click delete. Am I missing something? —Femke 🐦 (talk) 14:47, 14 December 2025 (UTC)
Might be a skin thing; I hover over the TW dropdown, click CSD and then click delete. Primefac (talk) 15:59, 14 December 2025 (UTC)
The standard Delete button doesn't deal with talk pages and incoming redirects, meaning it leaves a lot of cleanup to do. The current Twinkle solution is 3 clicks on opposite sides of the page, and takes the bulk of a reviewer's time when going through easy criteria like U6. Chaotic Enby (talk · contribs) 14:52, 14 December 2025 (UTC)
Standard delete does deal with talk pages, but I agree it would be nice if it dealt with redirects. See my reply to Femke directly above your comment about the three- or two-click thing. Primefac (talk) 15:59, 14 December 2025 (UTC)

Added AI-generated tag, reason parameter was dropped

I added the AI-generated tag to Akpanta, Nigeria, and the |reason= parameter was omitted. Can anyone else reproduce this? – Jonesey95 (talk) 13:35, 7 November 2025 (UTC)

@Jonesey95. I don't see a |reason= parameter documented at Template:AI-generated#How to use. Typing into Twinkle's "reason" box in the tag module just puts it in the edit summary. Please let me know if I'm missing something. –Novem Linguae (talk) 08:25, 14 December 2025 (UTC)
There appears to be an undocumented |reason= parameter. Diff. Interesting. So I guess the next steps would be 1) update the template documentation, 2) get this added to Twinkle by having a textbox appear when you click on the AI-generated tag, and 3) rename the "reason" text box at the bottom to "edit summary"? –Novem Linguae (talk) 08:29, 14 December 2025 (UTC)
The |reason= parameter was there the whole time. I clicked on Twinkle and clicked on the AI-generated template. A text box appeared, asking for a reason. I put the reason parameter value in the text box. This was the resulting edit. Twinkle should put the contents of the text box into the template's |reason= parameter. I don't know how to make that happen, hence the original post. – Jonesey95 (talk) 16:05, 14 December 2025 (UTC)
Nothing happens when I tick the check box next to {{AI-generated}} in the Twinkle tag menu. No extra text boxes appear. The "Reason" box at the bottom is always there (for all boxes ticked or no boxes ticked) and is for the edit summary. The typical way Twinkle would handle collecting a custom reason is to add a new text box that appears when clicking the tag. For example, the {{Cleanup}} tag has this.
Also, some possibly relevant discussion: Template talk:AI-generated#Adding rationale parameterNovem Linguae (talk) 07:24, 15 December 2025 (UTC)
If the "Reason" box is for the edit summary, it should say "Edit summary:", not "Reason", which confusingly matches a parameter in this and many other templates. – Jonesey95 (talk) 21:05, 15 December 2025 (UTC)

CSD G15 reason bug

Yeah this happens when adding a reason for the "Communication intended for the user" criteria but not the "Implausible non-existent references" criteria. Unclear about the "Non-sensical citations" criteria because I don't think I've ever nominated under that criteria. @Novem Linguae could you please take a look at this? The issue reliably reproduces for me - see my User:NicheSports/CSD log#November 2025. I always add a reason when I G15 something, but it doesn't work with the "Communication" criteria, and I have to manually add it to the page after Twinkle tags it. But I don't manually add it to my CSD log, so you can see the pattern there. NicheSports (talk) 00:27, 28 November 2025 (UTC)

@NicheSports. OK, I was able to reproduce this. I filed https://github.com/wikimedia-gadgets/twinkle/issues/2276. –Novem Linguae (talk) 08:38, 14 December 2025 (UTC)

Subpages: all

Could you please add to / extend the "Page > Subpages" feature so it lists both talk and non-talk subpages, regardless from which side it gets triggered? Paradoctor (talk) 12:34, 15 December 2025 (UTC)

What module? What steps do I need to follow to see what you're seeing? –Novem Linguae (talk) 06:20, 16 December 2025 (UTC)
Screenshot of Twinkle menu showing Subpages feature, taken 2025-12-16, Vector Legacy (2010) skin
That do it for you? Paradoctor (talk) 12:01, 16 December 2025 (UTC)
That's not a Twinkle menu. You're looking at m:MoreMenu. – SD0001 (talk) 13:36, 16 December 2025 (UTC)
I would be embarassed now if I wasn't so busy pulling my hair. Paradoctor (talk) 13:42, 16 December 2025 (UTC)

Feature request: Rcat tags

For {{R from other language}} and for {{R avoided double redirect}}, when selected Twinkle will provide a box to fill in the parameter (or parameters, for alt lang). Could we get the same option for {{R from sort name}}, which is supposed to pass two parameters? {{{1}}} being the first letter of the redirect, and {{{2}}} being the first letter of the target. Happy Editing -- IAmChaos 21:06, 15 December 2025 (UTC)

This is enough information for a GitHub ticket if someone wants to file it and then add a {{Tracked in}} template to this section. –Novem Linguae (talk) 06:21, 16 December 2025 (UTC)
I've not used github before, but I can try if you want me to file the request there directly. Happy Editing -- IAmChaos 06:31, 16 December 2025 (UTC)
Yes, that'd be great if you're willing. Here's a link: https://github.com/wikimedia-gadgets/twinkle/issues/newNovem Linguae (talk) 07:07, 16 December 2025 (UTC)
Added to github, and the template here. Happy Editing -- IAmChaos 22:07, 16 December 2025 (UTC)

Nomination for discussion of Template:Reduce to stub

Template:Reduce to stub has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Gonnym (talk) 10:04, 17 December 2025 (UTC)

New welcome template 'Welcome mentee'

New template {{Welcome mentee}} is now available for widespread use by Mentors in the Growth Team's Mentorship program. Twinkle users signed up as mentors may wish to use it to welcome their mentees; please add it to the installation. Template {{Mentor welcome}} has been available through Twinkle for some time now; {{Welcome mentee}} is an alternative with more links and different features. There are dozens of welcome templates available at the Welcoming committee for non-mentors, but up until now, there was only one for mentors to place, and now there are two. Hopefully, more will be forthcoming. And a plug for the program: More mentors are needed, and signing up is easy; see WP:GT/ML#How do I sign up?. Thanks! Mathglot (talk) 08:23, 8 December 2025 (UTC)

To this request, please also add {{Welcome mentee brief}}. Thanks, Mathglot (talk) 23:06, 17 December 2025 (UTC)

Twinkle closes merge discussions?

I came across Special:Diff/1328515844 and noticed that a) there was an excessively long edit summary, likely caused by b) a Twinkle tag. Does TW have the ability to close merge discussions and make the associated edits with removal etc? I've never seen that before. If that is the case, can I request that we remove the full edit from the edit summary? Primefac (talk) 11:58, 20 December 2025 (UTC)

I think that editor might have just used the TW -> Tag feature, unticked {{Merge from}}, then typed or copy pasted a long reason in the "reason" box (which then shows up as the edit summary). –Novem Linguae (talk) 12:30, 20 December 2025 (UTC)
Ah, that would make sense. Seems like just editing the page would be easier, but... shrugs... you do you I guess. Primefac (talk) 12:36, 20 December 2025 (UTC)

Module page TfD incorrectly done

Twinkle messed up this nomination. It was supposed to look like this. This is the first time this happened. Gonnym (talk) 14:18, 21 December 2025 (UTC)

I was able to reproduce by visiting Module:Bar box/doc, then going to TW -> XFD, then clicking preview. Anyone should feel free to file this on GitHub as the next step. –Novem Linguae (talk) 15:46, 21 December 2025 (UTC)

Warning for MOS (naming)

Hi, I created these warnings to be used for WP:COMMONNAME. Addition of these would be quite useful for patrollers. Thanks! codelivid 15:43, 30 December 2025 (UTC)

Nomination for discussion of Template:Uw-name1

Template:Uw-name1 has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Mathglot (talk) 23:08, 3 January 2026 (UTC)

Warning needed for using Twinkle on pages under sanctions

I recently reverted edits on a page using Twinkle. Only afterward did I see that there was CTOP 1RR restriction on the page. The notice appears in the normal editing window, but not when doing edits with Twinkle. There should be some alert if using Twinkle to revert edits on pages (or for other edits to which it may apply) if any such sanctions are present to avoid accidental violations of 1RR restrictions. TornadoLGS (talk) 23:23, 3 January 2026 (UTC)

WP:X3 has been deprecated

WP:X3 has been deprecated. Please remove it from the WP:CSD options. Thanks. Steel1943 (talk) 20:57, 26 December 2025 (UTC)

 DoneNovem Linguae (talk) 19:25, 4 January 2026 (UTC)

Subscribed to deletion sorting lists

Twinkle has recently started subscribing me to deletion sorting lists when I take something to AfD. I'm not sure why this is, and I don't know whether it's reproducible. For example, Special:Diff/1328961685 subscribed me to Wikipedia:WikiProject Deletion sorting/United Kingdom. lp0 on fire () 14:00, 23 December 2025 (UTC)

Possibly related: phab:T412462Novem Linguae (talk) 15:01, 23 December 2025 (UTC)
came here looking for something else and found this answer. Was driving me bonkers but never thought to blame my beloved Twinkle. Thanks @Lp0 on fire @Novem Linguae @SD0001 Star Mississippi 01:17, 31 January 2026 (UTC)
This has been fixed (#2302). – SD0001 (talk) 11:43, 28 January 2026 (UTC)
Thanks! lp0 on fire () 11:46, 28 January 2026 (UTC)

Batch RFD nomination

"Help:FRIENDLY" listed at Redirects for discussion

The redirect Help:FRIENDLY has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 3 § Help:FRIENDLY until a consensus is reached. Primefac (talk) 20:47, 3 January 2026 (UTC)

"Wikipedia:Friendly" listed at Redirects for discussion

The redirect Wikipedia:Friendly has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:Friendly until a consensus is reached. CycloneYoris talk! 22:48, 10 January 2026 (UTC)

"Wikipedia:FRIENDLY" listed at Redirects for discussion

The redirect Wikipedia:FRIENDLY has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:FRIENDLY until a consensus is reached. CycloneYoris talk! 22:49, 10 January 2026 (UTC)

"Wikipedia:FRIEND" listed at Redirects for discussion

The redirect Wikipedia:FRIEND has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:FRIEND until a consensus is reached. CycloneYoris talk! 22:49, 10 January 2026 (UTC)

"Wikipedia:FREINDLY" listed at Redirects for discussion

The redirect Wikipedia:FREINDLY has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:FREINDLY until a consensus is reached. CycloneYoris talk! 22:50, 10 January 2026 (UTC)

"Wikipedia:Fdly" listed at Redirects for discussion

The redirect Wikipedia:Fdly has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:Fdly until a consensus is reached. CycloneYoris talk! 22:50, 10 January 2026 (UTC)

"Wikipedia:FDLY" listed at Redirects for discussion

The redirect Wikipedia:FDLY has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 January 10 § Wikipedia:FDLY until a consensus is reached. CycloneYoris talk! 22:51, 10 January 2026 (UTC)

X3 notification templates

Recently, the following two templates for the WP:X3 deletion criterion were nominated for speedy deletion under WP:G8:

  • Template:Db-x3-deleted
  • Template:Db-x3-notice

The X3 criterion was rescinded in November, so these initially seemed to qualify. However, on further review, the documentation of these pages says: Any breaking changes to this template, including moving it or nominating it for deletion, must be communicated in advance to Twinkle's users and maintainers at Wikipedia talk:Twinkle.

I see that the Twinkle options still allow a page to be tagged for speedy deletion via X3. Can this be sorted out so the above two templates can be deleted? Epicgenius (talk) 18:36, 4 January 2026 (UTC)

Also pinging @ExcitedA who nominated the two above templates for deletion. Epicgenius (talk) 18:37, 4 January 2026 (UTC)
@Epicgenius. I've made the appropriate code changes to Twinkle. These are OK to be deleted now. Thanks for checking first. –Novem Linguae (talk) 19:24, 4 January 2026 (UTC)
Sounds good. I've deleted the pages and their corresponding documentation subpages now. Epicgenius (talk) 19:55, 4 January 2026 (UTC)

Nomination for merger of Template:Uw-spamblacklistblock

Information icon Template:Uw-spamblacklistblock has been nominated for merging with Template:Uw-sblock. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Janhrach (talk) 18:47, 8 January 2026 (UTC)

Userspace logs

Where are the logs for CSD or AfD stored in my userspace when I have the option enabled? —Opecuted (talk) 14:31, 9 January 2026 (UTC)

Should be User:Opecuted/CSD log and User:Opecuted/AfD log. You can configure that in Twinkle though. You can also find all your user subpages at Special:PrefixIndex/User:Opecuted Toadspike [Talk] 14:41, 9 January 2026 (UTC)

G5 in db-multiple bug

If {{db-gs}} is selected as a rationale for a {{db-multiple}} CSD nomination, Twinkle instead places the {{db-banned}} rationale (e.g. Special:Diff/1332331953). The intended is correctly recorded in the user's CSD log.

Also, {{db-hoax}} is supported in {{db-multiple}} separate from {{db-g3}}, and should be listed as an option. –LaundryPizza03 (d) 06:50, 11 January 2026 (UTC)

CT-Helper topic list

This comment:

Is the list editable somewhere? It's currently rather confused, and confusing, and could do with being copy-edited. For example, one entry begins "Wikipedia:" but the others do not; and several begin "The".

I'm happy to do the grunt work, if you can tell me where.

was archived unanswered. Since then, the most recent additions are "Can", "Ee" and "Ps".

Can anyone here advise or assist? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:13, 15 January 2026 (UTC)

@Pigsonthewing. Hey there. The user script's source code is at User:TheresNoTime/Scripts/CT-Helper.js. Looking very quickly at the code, it looks like it might grab its list from Template:Contentious topics/list (click "edit source" to see the codes). Is that the list you're looking for? –Novem Linguae (talk) 14:08, 15 January 2026 (UTC)
The current Twinkle logo

I don't normally concern myself these days with graphical changes to internal Wikipedia pages (some combination of "it's a lost cause" and "we have bigger fish to try"), but I'm going to make an exception here, since the current Twinkle logo (File:Police man Twinkle Head.svg) is uniquely bad. Laying out the specific reasons so that this isn't just WP:IDLI:

  • It doesn't fit the tool's name: There's nothing twinkling in it.
  • It doesn't fit the tool's contemporary purpose: It was created back in 2007, and my understanding of the history is that Twinkle then was primarily an anti-vandalism tool, for which a policeman arguably has some fit. But these days it's used for a much broader array of tasks.
  • It carries aggressive, exclusionary connotations: The logo is of a light-skinned male, which isn't optimal when we're trying to diversify our editorship. And not to get too political, but police officers in many countries (especially those with grumpy expressions like in the logo) carry connotations of aggression, authority, and other attributes that don't align well with the behavior we'd like to encourage among Twinkle users.
  • It's poorly designed: I didn't have to go to the file page to tell that it was made c.2007 — the design has several qualities that make it feel dated. It scales poorly to small sizes (important for userboxen).

Together (even if you disagree with one or two of my reasons), these add up to an unsuitable logo, so I'd like to propose that we consider changing it to something new. Perhaps it could be related to twinkling (e.g. ✨) or perhaps someone could design something totally new (courtesy ping Triton, who I see made flat versions of the current logo in 2022). Perhaps if it's good enough we'd actually want to use it in the Twinkle tool's interface or on the Github repository page. Thoughts/suggestions? Sdkbtalk 23:25, 13 December 2025 (UTC)

Hi, feel free to check in the various icons or let me know if you need something new. Cheers. Triton (talk) 23:28, 13 December 2025 (UTC)
I think we probably want to move away from a person-based logo entirely. I suggested something to do with sparkling above, but beyond that I'll leave the design up to whoever wants to make something — I tend to find that design by committee works poorly, so it's better to go with whatever you think looks best. Sdkbtalk 23:31, 13 December 2025 (UTC)
Sort of related discussion: Wikipedia_talk:Twinkle/Archive_49#UTTP_and_Twinkle_(Emergency). Schazjmd (talk) 23:35, 13 December 2025 (UTC)
Yeah, I came across that; I'd have to dig into it further to determine whether there's anything there. But there are plenty of other reasons, even setting that aside, to change it. Sdkbtalk 23:52, 13 December 2025 (UTC)
Just a random thought but how about a paint roller? ~ Argenti Aertheri(Chat?) 00:48, 14 December 2025 (UTC)
Not sure I get it; what prompted that as an idea? Sdkbtalk 01:45, 14 December 2025 (UTC)
Perhaps Huggle's broom logo? ~ Rusty meow ~ 01:47, 14 December 2025 (UTC)
How about the sparkles (✨) at the end of a wand to imply that it is a tool? cmɢʟee τaʟκ (please add {{ping|cmglee}} to your reply) 02:14, 14 December 2025 (UTC)
The "sparkles" icon is now associated with AI/LLM generation, so please no! qcne (talk) 16:12, 15 December 2025 (UTC)
Good point! I don't want to be associated with LLM. Happy Editing -- IAmChaos 18:36, 15 December 2025 (UTC)
Twinkle makes it easy to make big changes in one sweep, like a paint roller. Don't ask me where my brain gets its ideas from. ~ Argenti Aertheri(Chat?) 04:40, 14 December 2025 (UTC)
A large cross-shaped star suggesting the letter "t" surrounded by smaller cross-shaped stars? The middle-left figure on https://www.shutterstock.com/image-vector/set-original-vector-stars-sparkle-260nw-1405814981.jpg seems an aesthetic arrangement. cmɢʟee τaʟκ (please add {{ping|cmglee}} to your reply) 02:21, 14 December 2025 (UTC)
I took inspiration from this, with the smaller stars going at the top to suggest the upper bar of the T! Chaotic Enby (talk · contribs) 13:54, 14 December 2025 (UTC)
I am fully in support of a logo change. Once that's out of the way, we just need to bartender our way to a new one... thus far, both the paint-roller idea and the T-shaped star idea sound good. Toadspike [Talk] 11:21, 14 December 2025 (UTC)
Gonna ping @Chaotic Enby, who is both active in building Twinkle and has graphic design skills. Toadspike [Talk] 11:22, 14 December 2025 (UTC)
Well, that's definitely something I had in the back of my mind for a long time! Happy to see there's support for a change. I really don't like it being a police officer, or the very cop-like nature of many of Wikipedia's metaphor (the Wikipedia:Counter-Vandalism Unit also comes to my mind). Twinkle is more of a tool for helping with technical stuff, or at most housekeeping, than one for policing, and the logo should reflect that.
Regarding the specific ideas that have been proposed, I like the idea of twinkling stars, although the ✨ symbol is (to my greatest regret) associated with AI and might be a bit misleading. We've got many other star arrangements that could work well, especially if we elongate the diffraction spikes in a T shape. Chaotic Enby (talk · contribs) 11:28, 14 December 2025 (UTC)

Cmglee proposal

t-shaped asterism
Thanks. How about this? cmɢʟee τaʟκ (please add {{ping|cmglee}} to your reply) 13:12, 14 December 2025 (UTC)
I'm currently working on a proposal of my own. I don't like how this one still looks like a small variation on the ✨symbol with slightly elongated spikes, especially on smaller screens. Chaotic Enby (talk · contribs) 13:14, 14 December 2025 (UTC)

Chaotic Enby proposal 1

Proposal by Chaotic Enby
This is my current logo proposal: Chaotic Enby (talk · contribs) 13:52, 14 December 2025 (UTC)
Looks very celestial. Like angels flying around in heaven. Not sure if that is good or bad. –Novem Linguae (talk) 15:03, 14 December 2025 (UTC)
No. The current logo is fine, and has been associated with Twinkle for virtually it's entire lifespan. I see no reason whatsoever why the current logo should be changed. Sugar Tax (talk) 13:16, 14 December 2025 (UTC)
I'm always glad when we move away from gendered symbolism on Wikipedia. I like the star designs, but perhaps the T should be more clear. You see some software use the stars for AI magic, so that might become confusing. If the big star in CE's proposal is more like a T, that might work? —Femke 🐦 (talk) 14:52, 14 December 2025 (UTC)
I wanted to make the smaller stars form the top bar of the T, as raising the middle bar of the big star might make it look like a Christian cross. Especially with stars, it's a bit easy to accidentally sprinkle in some religious symbolism, and I'm trying to also stay neutral in that regards. I'll try to see if I can get a design to make the T a bit clearer! Chaotic Enby (talk · contribs) 15:33, 14 December 2025 (UTC)

Chaotic Enby proposal 2

Second proposal by Chaotic Enby
Here's a new version! Chaotic Enby (talk · contribs) 16:06, 14 December 2025 (UTC)
That does look a lot more T-shaped. The question is whether it's T-shaped enough. The top gives fairly triangular vibes. I really like the colors though. Toadspike [Talk] 12:41, 15 December 2025 (UTC)
The idea of the top is that the stars would also form a W shape, for TW! Chaotic Enby (talk · contribs) 15:59, 15 December 2025 (UTC)
Ah okay, that makes more sense. If it isn't too much trouble, could you please try making a version with the "W" at the bottom as well? I think the order ("T" --> "W") might be clearer that way. Toadspike [Talk] 21:01, 15 December 2025 (UTC)
I'd like to, but I'm afraid that the T might look upside-down if the W cuts it off from the bottom instead. Chaotic Enby (talk · contribs) 21:22, 15 December 2025 (UTC)
Consider replacing the blue cross with a T. I think right now the TW is too subtle to notice for most people. –Novem Linguae (talk) 06:19, 16 December 2025 (UTC)
  • Courtesy pinging Serhio Magpie, who I believe did the excellent redesign of the MediaWiki logo in 2020, in case you have any thoughts/suggestions. Sdkbtalk 16:40, 15 December 2025 (UTC)
    Thanks, I appreciate the notice! I completely agree with all of your arguments in the main post, and I support changing the logo to some meaningful abstraction, as I love functional simplicity in design. Right now I don't have any bright ideas that I can bring to this topic that haven't already been brought up. But I can highlight some internal processes and requirements that I brought to designing the logo for my own tool - Instant Diffs.
    Instant Diffs logo in light theme
    Instant Diffs logo in dark theme
  • The logo should contain some abstract metaphors for what the tool represents. In my logo I use two filled blocks drawn side-by-side in the same color that's used to highlight removed or added content in diffs. I left the top and bottom boxes outlined so they resemble a well-balanced weighing scale.
  • The logo should be readable in both color themes and at various sizes. To achieve readability in extreme cases, for example inline text emoji-like size, I resorted to the next point.
  • (optionally) It would be good if a simplified icon could be represented by some UTF-8 symbol that isn't used often in other contexts. I chose ❖ (Black Diamond Minus White X) as it represents windows or panes, which fits nicely with Instant Diffs' nature as a dialog window with content.
Serhio Magpie (talk) 20:23, 17 December 2025 (UTC)
That looks amazing, and I really like your design process! I was wary about making the lettering too blatant, and having a very abstract logo can indeed work well, especially in your case where the colors also help convey the concept. I'll look at some Unicode symbols that can work well as inspiration for Twinkle (correct me if I'm wrong, but all Unicode symbols can be encoded in UTF-8, right?) Chaotic Enby (talk · contribs) 20:43, 17 December 2025 (UTC)
Oh sorry, I meant Unicode symbol. I'm pretty sure all Unicode characters can be encoded in UTF-8. Have a great creative session! Serhio Magpie (talk) 21:25, 17 December 2025 (UTC)

Skin it?

Why not make the logo user-customizable? Tech FTW Paradoctor (talk) 12:37, 15 December 2025 (UTC)

The thing is, most of the uses of the logo are outside of the script (like topicons, userboxes, information pages, ...), so they can't be customized on the reader side, and having the person adding each logo choose which one to use would make it confusing for the reader. Chaotic Enby (talk · contribs) 16:03, 15 December 2025 (UTC)

Chaotic Enby proposal 3

Third proposal by Chaotic Enby
After working on it for a few days, here's another design! This one is inspired by the character U+2748 HEAVY SPARKLE, with the sides being shaped like lightbulbs pointing in all directions. Twinkle is very much a multi-purpose tool, and it would've been hard to point to a single main "task" it does like Instant Diffs, so this abstract metaphor works well!
One issue I've run into is that Twinkle doesn't have much of a color palette. While I'm thinking of working on bringing it more in line with Codex, I had to take a few artistic liberties for now. I really liked the idea of a blue sparkle (O-type, or Wolf-Rayet stars), although I didn't want to go with the obvious choice of yellow lightbulbs to not look too much like Instant Diffs. I went for a purple gradient (inspired by plasma lamps and novae such as GK Persei), which adds a modern touch to it. Chaotic Enby (talk · contribs) 11:09, 23 December 2025 (UTC)
This one looks good to me. – SD0001 (talk) 13:25, 23 December 2025 (UTC)
I like this one. Colours, not really bothered - but the design is much improved. qcne (talk) 13:35, 23 December 2025 (UTC)
Looks good, my idea was half baked anyway. ~ Argenti Aertheri(Chat?) 14:31, 23 December 2025 (UTC)
I like it! Easily a major improvement over the status quo. Sdkbtalk 16:55, 23 December 2025 (UTC)
Love how everything comes together in one piece, super cool! The cosmic metaphors really got me, that's totally my vibe! Serhio Magpie (talk) 21:05, 23 December 2025 (UTC)
I like this one. I thought the previous (T-shaped) design was a bit too busy. ClaudineChionh (she/her · talk · email · global) 00:25, 24 December 2025 (UTC)
Looks like a clear consensus. Feel free to start swapping at WP:TW and in user boxes. –Novem Linguae (talk) 03:18, 24 December 2025 (UTC)
There's some objections below, so let's pause additional swapping for a couple days. –Novem Linguae (talk) 06:17, 24 December 2025 (UTC)
I think I'd like it better, as I state below, if it had a bit of an homage to the current logo - perhaps yellow light bulbs and a red center, or vice versa. Somehow incorporating the color scheme from the policeman. ~Darth StabroTalk  Contribs 16:31, 24 December 2025 (UTC)
This is my favorite proposal thus far; I'd fully support switching to it. Toadspike [Talk] 17:22, 24 December 2025 (UTC)
  • Am I the only one, thinking that this one looks a little weird? It looks to me like if there's a star blade with boxing gloves shooting out. It's not representing the unicode spark character, it's inspired from. While I don't actually have any issues with this(I only said what I thought when I first looked at it.), I'd opt for a wordmark like icon as used for Ultraviolet. The sparkle icon can be used in it(for the 🔴 on top), with another icon for tool (eg:-🔧)(for the vertical bar). (Don't take my words too seriously!!)codelivid 17:16, 29 December 2025 (UTC)

Chaotic Enby proposal 4

Red against yellow, merry fellow...

Here's a red and yellow version following suggestions by @Darth Stabro and @Argenti Aertheri! Chaotic Enby (talk · contribs) 23:44, 24 December 2025 (UTC)

Hi. I haven't been editing long enough to have nostalgic feelings for the cop, but I sympathize with editors who do. With logo changes to internal tools, it really does just come down to personal preference in the end, so I don't really see the logic in weighing one !vote over another. That being said, I don't feel very strongly that the logo should be changed, but if it is to be changed, it makes sense to pay homage to the original. In short: I'm neutral towards changing the logo, but I support version 4 if it happens. Chess enjoyer (talk) 04:45, 25 December 2025 (UTC)
I change my mind: the new logo has grown on me, and I support it over the original. I still prefer version 4, but I don't mind if version 3 becomes the official logo. Chess enjoyer (talk) 03:01, 4 January 2026 (UTC)
Seems fine to me; I easily support it over the status quo, and have no strong preference for it vs. the purple/blue version. Sdkbtalk 06:59, 25 December 2025 (UTC)
Here's a side by side comparison: imgur. I prefer version 3. –Novem Linguae (talk) 10:56, 25 December 2025 (UTC)
Same. Version 4 feels like better fit to be RedWarn's logo. – SD0001 (talk) 13:38, 25 December 2025 (UTC)
Same, V3 is nice. qcne (talk) 13:53, 25 December 2025 (UTC)
Same, V3 is in more neutral colors. Serhio Magpie (talk) 23:09, 25 December 2025 (UTC)
Hi Chaotic Enby, version 4 seems very appealing than V3. I easily support it because red means endurance, engagement, decisiveness and courage. Ahri Boy (talk) 11:45, 29 December 2025 (UTC)
I like the color scheme a lot, but I think that it could use a mascot of some sort. To avoid dealing with the human sociopolitical scenario, I propose that the new mascot should be a well-regarded animal. My first thoughts would be:
  • A dolphin, because dolphins are usually considered fun and intelligent
  • A crow, because crows are known for basic tool usage, and Twinkle is a tool
  • A golden retriever, because they act as excellent companions and double as hunting dogs (just like how Twinkle can hunt vandals)
I'd need to see some mockups to be convinced of anything, but I think that one of those could be a good start. GrinningIodize (talk) 16:13, 29 December 2025 (UTC)

Was consensus sought fully?

Here to register an objection to the new logo. I like the policeman. And, furthermore, is a few people on a discussion the vast majority of Twinkle users don't know about really consensus? And is consensus decided in less than a day? ~Darth StabroTalk  Contribs 04:50, 24 December 2025 (UTC)
The 17 editors in this thread have been discussing for more than a week, at the centralized forum for Twinkle discussions with more than 1,000 watchers. And WP:IJDLI is not an objection. Sdkbtalk 04:54, 24 December 2025 (UTC)
The new logo was posted 15 hours ago, not one week. I'm indifferent to "liking it", but to say more than a week when changes have already started is disingenuous. Happy Editing -- IAmChaos 05:30, 24 December 2025 (UTC)
Fair enough; I might have waited a little longer. But the logo was the iterative result of the workshopping that began more than a week ago, not a tabula rasa design. And 8-0 is enough of a prevailing consensus that I think it's rather hard to fault Chaotic Enby for acting. Sdkbtalk 05:45, 24 December 2025 (UTC)
I think "I just don't like it" is an acceptable argument when it comes to visual changes, such as logos and skins. I think the spirit behind WP:IJDLI is more for making folks make policy-based arguments in deletion discussions. –Novem Linguae (talk) 06:25, 24 December 2025 (UTC)
I started off this discussion with specific reasons that made the old logo unsuitable, so I would expect specific rebuttals to those points from anyone defending it. Talking about specifics of design requires building up a bit of a new vocabulary, so I'm sympathetic when people don't arrive with that off the bat. But requiring it to give !votes weight is the only way to even try to distinguish between those that come only from a place of "this is new and I don't like change" (see my comment below) and those that come from a more legitimate place. Sdkbtalk 15:17, 24 December 2025 (UTC)
So far it's only been changed at WP:TW. We can wait on the other changes (userboxes) a couple days if you want. –Novem Linguae (talk) 06:16, 24 December 2025 (UTC)
the topicon was changed as well. Happy Editing -- IAmChaos 06:18, 24 December 2025 (UTC)
Reverted for now. Template:Twinkle topicon. –Novem Linguae (talk) 06:23, 24 December 2025 (UTC)
@Darth Stabro I fear that your objection is going to mean this process grinds to a halt and the logo will never change. One of the reasons I hate Wikipedia consensus making, when a single person can derail a discussion that users have put work into. I like the new logo suggestion, and I feel that should have equal weighting. What could we do to flip your objection to a support, or at the minimum a "I don't care"? qcne (talk) 12:08, 24 December 2025 (UTC)
@Qcne, Sdkb, and Novem Linguae: I think the main reason I don't like the new logo aesthetically is nostalgia, to be sure - like many people here, I've been using Twinkle for a long time. If some sort of update was done, I'd like something that did some homage to the old logo, even if just by a matching color scheme, incorporation of the policeman's star or smile, etc. That said, if a greater consensus was found for the already-proposed new logo, I'd live with that. But I don't think eight people out of the thousands who use Twinkle is enough consensus for a change, especially on such short discussion. Some way of notifying regular users, who might not necessarily have WT:TWINKLE on their watchlist, would be good. I only saw the discussion when the template I created, {{Twinkle topicon}}, was modified. ~Darth StabroTalk  Contribs 14:52, 24 December 2025 (UTC)
This page has 1,194 watchers, so that's good. This page is a pretty good megaphone. But yeah, point taken about keeping this open longer. Let's see where consensus is in a few days. –Novem Linguae (talk) 14:59, 24 December 2025 (UTC)
I appreciate your candor in acknowledging the role of nostalgia. To add on to qcne's point, though, design discussions are particularly hard to achieve in a consensus system because most people naturally like what they're used to, and that causes some level of built-in opposition. The same thing happened with Vector 2022. I wish that we could have some sort of rule with something like, before !voting in a design discussion, try out the new design for a week and see if it grows on you. Sdkbtalk 15:09, 24 December 2025 (UTC)
Nostalgia is powerful, I'll give you that. Also, it seems like the policeman had meaning (at least at one point). One of the things I hate in the world right now is the growing sense of everything having to fit minimalism. The newest proposal is just a unicode character? I can't tell what a tool is like with just 4 blobs. UV isn't exactly descriptive as a logo, but it matches the name. The policeman is very fitting for antivandalism. I'm looking at my topicons right now; the WP:RE logo is very clear, a broom for cleaning and #R for redirect syntax; the mentor logo has a question and response. Changing from a recognizable logo to a random blob with less than a day's warning feels abrupt. at least the second proposal has a T and a W. If this is a !vote, which I know it's not, that's what I'm voting for. Happy Editing -- IAmChaos 17:14, 24 December 2025 (UTC)
The policeman is very fitting for antivandalism. It is, but there's a lot more to twinkle than that. The policeman never made sense to me since I use it for WP:PROD // deletions, which is more janitor than cop. I have no desire for authority lol. I like the idea to keep the colors though, the red/yellow has good contrast and ties whatever comes out of this back to the officer. ~ Argenti Aertheri(Chat?) 23:22, 24 December 2025 (UTC)
The policeman icon feels not appropriate for everyone, especially holding views against cops, hence ACAB stands for. Ahri Boy (talk) 11:47, 29 December 2025 (UTC)
FWIW, I'm an oldie, I understand nostalgia, and I still use Twinkle for anti-vandalism among other tasks; but I also sympathise with the growing trend towards anti-police sentiment. I'd like to see a logo that minimises or completely removes the cop association while bringing back the "twinkle" element. To me, using Twinkle feels more like applying "magic pixie dust" (a bit of cleanup here, a bit of tagging there) than policing. ClaudineChionh (she/her · talk · email · global) 00:59, 25 December 2025 (UTC)
As someone who just arrived, I support the new logo for all the reasons Sdkb points out. I personally like v3 but am happy with v4 (or really most things which are not white male cops). HouseBlaster (talk • he/they) 21:42, 30 December 2025 (UTC)
V3, per globalization and other issues raised above. --SarekOfVulcan (talk) 21:48, 30 December 2025 (UTC)
i really don't like v3 or v4. i much prefer v1. ltbdl (scan) 06:14, 31 December 2025 (UTC)
I always thought the policeman mascot was literally called “Twinkle” because it’s a funny ironically cutesy name for a big burly dude. Dronebogus (talk) 09:55, 1 January 2026 (UTC)
Indeed, wikt:twinkle toes came to mind. Arlo James Barnes 06:55, 24 January 2026 (UTC)
  • Also, I support CE V3 aka the current one. The colors are nice, the shape is distinctive (even if it’s more “flower” than “sparkle” to me), it’s timeless (unlike the early 2000s vector clipart vibes of the classic logo) and the neutral software logo vibe is better for a general maintenance tool than “I’m an angry cop who’s gonna kick your ass, vandal” which I guess was the message behind the first logo. --Dronebogus (talk) 10:05, 1 January 2026 (UTC)
    I oppose any changes, the logo carried history and was just fine. No convincing arguments here. Claiming a white police officer conveys racism is just disgusting as well and it's just a fact that most WP editors, alike policemen, are white males. This should've been decided with an RfC. ~2026-97303 (talk) 16:52, 5 January 2026 (UTC)
    Start an RFC once we've got an alternative to present then? No one is going to vote to keep something that was clearly designed 20 years ago though, so if you want to keep him you should probably try making a version that isn't littered with gradients. ~ Argenti Aertheri(Chat?) 20:14, 5 January 2026 (UTC)
    The gradients add character to the logo, and I like it that way. GrinningIodize (talk) 21:43, 5 January 2026 (UTC)
    most WP editors, alike policemen, are white males
    [citation needed] ltbdl (activate) 14:52, 7 January 2026 (UTC)
    @Ltbdl, the IP makes a terrible argument for us not being inclusive. But they are broadly correct about the demographic situation, and we need to be honest with ourselves about that. Sdkbtalk 18:36, 7 January 2026 (UTC)
  • People are quite passionate about logos, aren't they! Audacity is getting a new logo with v4 and people are up in arms about it too! And does anyone remember MediaWiki's old sunflower logo that we used for 18 years? People have strong attachments to logos, even if they can't really explain why. I have no strong opinion about the old and new Twinkle logos myself (even though the policeman does bring back memories of my high school self); the old logo is more akin to Twinkle's history as a tool for patrollers while the new logo is more of a literal "twinkle". WP:IJDLI is an argument you're going to hear a lot with any logo change, simply because people are so passionately and emotionally attached to logos (it's a human thing; we like symbols we can fly over our heads), but one that you'll start to hear less and less as everyone gets used to (or begrudgingly accepts) the new logo, and more practical matters take hold. While I'm here, from a cursory glance, it looks like the logo has only been discussed twice on this talk page: once in 2015 over whether Twinkle was strictly an anti-vandalism tool or a "Swiss army knife", and more recently in September over the Twinkle policeman icon being used by trolls on other sites. "Meh" at the second, but I do agree that Twinkle has long evolved from its early days as a patroller's companion and more towards a general "Swiss army knife" that does a whole bunch of useful things. —k6ka 🍁 (Talk · Contributions) 13:50, 6 January 2026 (UTC)

Use subst:requested move instead of transcluding requested move/dated

Twinkle transcludes requested move/dated directly, but the template documentation says to subsitute it. Speedrunz (talk) 15:57, 26 January 2026 (UTC)

TM:Uw-archive

Why isn't this included? HKLionel TALK 09:49, 31 January 2026 (UTC)

Because no one has asked yet, I suppose. If you want it (in a "right now" sort of way) see Wikipedia:Twinkle/doc § Warn (user talk warnings) for information about adding your preferred templates to the tool. Primefac (talk) 10:25, 31 January 2026 (UTC)
I don't mind, but I'd like to see this added to the default set as it definitely addresses an existing issue. HKLionel TALK 10:30, 31 January 2026 (UTC)
I'm not a big fan of this one. If you manage to get a problematically long user talk page you are likely an established user and is unlikely to be happy about a templated warning that assumes you are a newbie. Trialpears (talk) 11:05, 31 January 2026 (UTC)
Just because someone's an "established user" doesn't mean they can't be reminded about issues that affect others, regardless of their standing. It's also entirely possible that the issue has never been brought up before, or that they aren't aware it's an issue. TM:Please archive exists as a short reminder, consider that instead if you will. HKLionel TALK 11:19, 31 January 2026 (UTC)
To give my opinion on the merits of this request, I would say that templates in the Twinkle system should be commonly-used. I am currently seeing ~230 uses in the user talk space (and less than 50 of the shorter variant). Even counting stuff that might have been deleted, I'm not sure it's going to be used enough to merit making it a default template in Twinkle. Primefac (talk) 12:19, 31 January 2026 (UTC)
Makes sense. Thanks, HKLionel TALK 12:30, 31 January 2026 (UTC)
I like {{please archive}} significantly more since it is a lot less confrontational. I also find the concern raised by Primefac convincing although I believe it would be used significantly more often if in twinkle. Adding it in your own install should be sufficient imo. Trialpears (talk) 12:29, 31 January 2026 (UTC)
I'm not sure if this is an implication of your post, TP, but the template has been nominate for deletion twiceTemplate talk:Uw-archive and kept both times. Primefac (talk) 12:19, 31 January 2026 (UTC)
Can't say the thought didn't strike me but I guess the second time is too recent for any consolidation at the moment. Trialpears (talk) 12:30, 31 January 2026 (UTC)

"Wikipedia:FREINDLY" listed at Redirects for discussion

The redirect Wikipedia:FREINDLY has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 February 6 § Wikipedia:FREINDLY until a consensus is reached. - ExcitedA. It may be a good idea to look at this. 19:49, 6 February 2026 (UTC)

G5 WP:CT/IMH talk page messages

See permanent link for User talk:BrightNova1001. The WP:CT/IMH codes were clearly not formatted properly in the messages, despite being correctly formatted in the deletion templates itself (see e.g. Draft:Capture of Rohtas). ~~ AirshipJungleman29 (talk) 18:15, 30 January 2026 (UTC)

Adding to this that WP:CT/KURD also isn't adding correctly (see ). I've been curious why I've seen multiple talk pages with notices like this, where they state, "No contentious topic code has been specified", and thought it may be user error. Doesn't seem like it, though. Significa liberdade (she/her) (talk) 23:09, 5 February 2026 (UTC)
Looks like this applies to all CT SDs I've seen. Significa liberdade (she/her) (talk) 06:03, 8 February 2026 (UTC)

Shared IP tagging module removed

The "Shared IP" option in Twinkle has been removed per #Delete "Shared IP" module? and #2260. This module was only used 4 times over the last 30 days, by 2 distinct users – which isn't the expected level of usage for a Twinkle component.

If by any chance you continue to find the option useful, the same functionality has been made available as a user script: User:SD0001/SharedIPTagger. – SD0001 (talk) 08:27, 8 February 2026 (UTC)

Nominating multiple items to XFD

I struggle with this. I know it's a rare thing to need to do. I find it a right royal pain. Have I just not found the part of Twinkle that lets me do this with ease? 🇵🇸🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦🇵🇸 12:46, 12 February 2026 (UTC)

I don't know that Twinkle supports that. I use this. DonIago (talk) 14:35, 12 February 2026 (UTC)
@Doniago Thank you. 🇵🇸🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦🇵🇸 18:36, 12 February 2026 (UTC)

Deletion sorting

When starting an AfD, I have to scroll through a long list in a narrow window to choose deletion sorting categories. WP:WikiProject Deletion sorting/Compact is much more helpful in choosing categories, and it should be linked to in the Twinkle menu. If not, then a link to the WikiProject at least please. Thanks, HKLionel TALK 19:24, 16 February 2026 (UTC)

The interface allows entering a search term to filter the listing. – SD0001 (talk) 20:12, 16 February 2026 (UTC)
Having a list helps make connections to DELSORT lists that wouldn't have been made otherwise. Not every search term turns up results, and synonyms can complicate things. It'd also be more user-friendly for newcomers and people who are inexperienced regarding AfD. HKLionel TALK 21:11, 16 February 2026 (UTC)

SPI reports lacking a checkuser tickbox

It used to be the case that reporting a sockpuppet through Twinkle would include a tickbox for requesting a checkuser, but I'm not seeing that box any more. Was it removed deliberately? Belbury (talk) 14:04, 18 February 2026 (UTC)

@Belbury Yes, the SPI template no longer has an option for the filer to request CU. New cases are now set to "New". Clerks/admins can request CU on a case if needed, while cases that don't need CU are set to "Open". Toadspike [Talk] 14:36, 19 February 2026 (UTC)
Got it. Thanks. Belbury (talk) 14:38, 19 February 2026 (UTC)

Twinkle no longer uses jQuery UI

Twinkle's UI has been migrated to no longer rely on jQuery UI, which is deprecated. This is largely an internal change and doesn't have visible effects. The only notable difference is that dialogs can be resized only from the bottom-right corner (earlier they could be resized from any corner or edge).

The update is live. Let me know if you notice any unexpected changes in behaviour of the dialog windows or tooltips. – SD0001 (talk) 08:43, 14 February 2026 (UTC)

Hi @SD0001: I don't know if this is connected (or whether it's a Twinkle issue at all, for that matter) but the submit button on the Twinkle dialog box used to be focused on load (ie. it had the 'focus ring' around it), which meant that when eg. welcoming a user you could just select that option from the menu and hit return. For the past couple of days this is no longer the case, and you now need to explicitly click on the submit button. I realise this is a tiny thing in the bigger scheme of things, but if it's a very easy fix, it would save an old dog like yours truly having to learn new tricks. -- DoubleGrazing (talk) 09:43, 16 February 2026 (UTC)
It's actually the first input in the form that was focused on load. Now, the dialog as a whole is getting focused. I restored the earlier behaviour (should be live in a few minutes). As long as any form element is in focus, hitting return will submit the form. – SD0001 (talk) 18:52, 16 February 2026 (UTC)
Excellent, many thanks! -- DoubleGrazing (talk) 14:59, 19 February 2026 (UTC)

Mobile

It would be very beneficial if mobile got the same features as desktop. This would save time and effort. Thank you for your time. Dafootballguy (talk) 05:01, 18 February 2026 (UTC)

@Dafootballguy: Have you looked at Plantaest/TwinkleMobile? Alternatively, if you're already using it, consider reporting the issue to that talkpage instead. ~ rusty meow ~ 14:40, 20 February 2026 (UTC)

Auto-subscribing to AIV

Is there a setting that I'm missing to disable automatically subscribing to WP:AIV when I report a user via ARV? I know that this was a known issue on Wikimedia's end, but to my (not terribly tech-savvy) understanding, that issue was resolved quite a while ago, and the flood of notifications that comes in when I forget to manually unsubscribe is quite obnoxious. ᴸᵃᶠᶠʸTaffer💬(they/she) 17:59, 27 February 2026 (UTC)

I've raised 2332. The issue was previously reported for XFDs, but not for ARV module. – SD0001 (talk) 19:32, 27 February 2026 (UTC)
@LaffyTaffer If you turn off "Automatically subscribe to topics" in your settings, it will fix this problem. You will, however, no longer be automatically subscribed to talk page topics you comment on. I found the tradeoff to be worth it, though, and have turned this feature off. Toadspike [Talk] 23:27, 27 February 2026 (UTC)
I was aware of that, yeah. I personally did not find the tradeoff to be worth it, I already forget to subscribe to topics enough with things like Wikilove messages. Thank you for the reminder all the same, and thanks to @SD0001 for opening a ticket(?) ᴸᵃᶠᶠʸTaffer💬(they/she) 23:38, 27 February 2026 (UTC)
Fixed. Auto-subscribe is now disabled for AIV, SPI, and AN3. It was already disabled for XFD listings. Let me know if there are other places where it's a problem. – SD0001 (talk) 06:02, 28 February 2026 (UTC)

Minimum number of uses to add a template to the Twinkle default list

I'd like to make an objective criteria for adding a template to Twinkle. The criteria should be if a template has at least X number of uses, because this signals popularity/usefulness in an objective way. This would apply to user warnings, maintenance tags, and maybe to some other stuff that I am forgetting. I was thinking 25, but in the section above folks were saying even 230 wasn't enough. What are our thoughts on the exact number? Thanks. –Novem Linguae (talk) 15:45, 31 January 2026 (UTC)

No comment on the specific number, but I'd just like to point out that most templates of this nature probably get their usage from Twinkle itself, so if it's added and Twinkle users find them useful/there are enough use cases that they can be applied to, usage would naturally rise. Some Twinkle users, including myself, sometimes scroll through the menu to see what templates can address the issues at hand, so we aren't really aware of templates not listed there, nor would we really go out of our way to search for one, unless—like me in the above section—we are aware of the specific issue. HKLionel TALK 17:41, 31 January 2026 (UTC)
Maybe like 5 per month on average? Doesn't seem overly onerous for an actually widely useful template even if it isn't in twinkle default and makes it easier for new templates to be added to twinkle. Given how easy it is to add your own templates I don't feel like it's necessary to be more permissive than this. Trialpears (talk) 18:13, 31 January 2026 (UTC)
Measuring per month seems a little difficult. I think total uses would be easier to check. –Novem Linguae (talk) 19:11, 31 January 2026 (UTC)
Uses divided by age of template isn't hard to do. Usage might have changed significantly so that's a flaw with that methodology but a template racking up a hundred uses over a decade or two does not mean it's highly used either. Ultimately I think we will have to be a bit subjective here. Trialpears (talk) 11:26, 1 February 2026 (UTC)
I think it should be based on user request. If a single person thinks a template should be added, they can do it themselves. If multiple people (maybe... 5?) agree that it's an overlooked template, we can add it. That avoids the "it's not used" issue and demonstrates that it will actually be used by folk. Primefac (talk) 20:09, 31 January 2026 (UTC)
I'd do it myself, if there were something on the doc page explaining how. I made a request § above, but I'm not even aware how to determine whether it has already been added or not. Could something be added to the project page about it? Mathglot (talk) 00:35, 6 March 2026 (UTC)

What happened to the logo?

The logo used to be a police head. What did they do to my man? Soviet Pepega (talk) 07:35, 6 May 2026 (UTC)

oh nvm found out the reason, had to check the archives. Soviet Pepega (talk) 07:41, 6 May 2026 (UTC)
Noted. CapnZapp (talk) 19:24, 9 May 2026 (UTC)
Closing without actionNovem Linguae (talk) 11:53, 12 May 2026 (UTC)

D-batch fail?

So, trying to batch-delete a mixed group (draft/template/file) pages in Category:Candidates for speedy deletion by user, Twinkle just hangs with the message "Grabbing list of pages: loading..." – something I've never seen before. Tried purging, opening the category in a new page and so on, no joy. Any cmt or suggestion? Justlettersandnumbers (talk) 09:59, 11 March 2026 (UTC)

I can reproduce. Seems to be due to a change in API response formats. Will look into it when I get home. – SD0001 (talk) 11:06, 11 March 2026 (UTC)

Related Articles

Wikiwand AI