Wikipedia talk:Twinkle

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Warning templates[edit]

Sometimes, I have used Twinkle instead of Ultraviolet for anti-vandalism, and have noticed that Twinkle has substantially less built-in templates compared to Ultraviolet/RedWarn, including some important ones like {{uw-coi}}. Can these be added? Rusty4321 talk contribs 22:59, 18 October 2023 (UTC)Reply[reply]

Uw-coi is in there. Try changing Wikipedia:Twinkle/Preferences#warn -> "Default warning level" to "All warning templates". –Novem Linguae (talk) 01:02, 19 October 2023 (UTC)Reply[reply]
Thanks! I'll give it a try. Rusty4321 talk contribs 02:33, 19 October 2023 (UTC)Reply[reply]
Thank you MinecraftPlayer321 (talk) 01:47, 17 January 2024 (UTC)Reply[reply]

Additional option for CfD[edit]

Would it be possible to add another option to the 'Categories for discussion' action dropdown menu? Often, I come across a category that isn't a notable intersection, so I need to indicate both parent categories. The issue is that the current merge option only allows selecting one category. As a workaround, I've been using the split option to propose what are essentially dual merges, enabling me to identify both categories.Mason (talk) 23:42, 14 November 2023 (UTC)Reply[reply]

@Smasongarrison. Can you provide a diff of what you'd like Twinkle to write? Is a second parent category supported by whatever templates are being used here? Is this proposal to add a "Target category 2 (optional)" box to the CFD form in Twinkle? Thanks. –Novem Linguae (talk) 06:55, 15 November 2023 (UTC)Reply[reply]
Sure! The split option supports a 2nd category already. So the proposal is either to add an optional 2nd category to merge, or create a nearly identical copy of split, and call it dual merge. (I don't know which would be easier to implement on the backend). Here's a diff of my workaround: [1]. The only difference would be to change the ":* Propose splitting" to say ":* Propose dual merging". Here's an example of the solution [2]. (I became very lazy about changing the word to split, so I had to dig around for an example.) Mason (talk) 13:03, 15 November 2023 (UTC)Reply[reply]
@Smasongarrison. Do we have a {{Dual merge}} template yet, or support for dual merges in the regular category merge template? Usually Twinkle just writes stuff to existing templates. –Novem Linguae (talk) 04:27, 19 November 2023 (UTC)Reply[reply]
That's a good question. I think that template:cfm-double does this {{cfm-double|ProposedName1|ProposedName2}}. I've never used it (and didn't know that it existed until now). Mason (talk) 05:18, 19 November 2023 (UTC)Reply[reply]
Novem Linguae, Mason is correct that {{cfm-double}} is the template needed here. Adding this would be much appreciated, as a regular closer of CfDs. — Qwerfjkltalk 19:28, 23 January 2024 (UTC)Reply[reply]
Got it. I typed up a ticket. Let me know if I need to change anything. –Novem Linguae (talk) 00:28, 24 January 2024 (UTC)Reply[reply]

Adding a template[edit]

I've just created {{uw-longsd}}, a single-use notice. Would it be possible to add this to Twinkle? /gq Suntooooth, it/he (talk/contribs) 14:06, 25 November 2023 (UTC)Reply[reply]

Sure. I created a ticket. –Novem Linguae (talk) 15:26, 25 November 2023 (UTC)Reply[reply]
Hi Novem Linguae, I saw that the issue was marked as complete last week, but the warning isn't showing up in Twinkle for me. In the file changes at #1938 (where the change was implemented) the template name is misspelt as "uw-lonsd"; perhaps that's causing the issue? Liu1126 (talk) 00:16, 29 January 2024 (UTC)Reply[reply]

Duplicate sockpuppet reports[edit]

Hi! When using Twinkle to report a sockpuppet to WP:SPI, duplicate listings are sometimes created; this has happened to me several times, most recently today. Is there some way that the tool could be set up to check whether the username being reported is already present in the SPI (or the archive thereof), and in that case warn the reporter? – somewhat as it already does when trying to add a user talk-page warning that's already been added. Many thanks, Justlettersandnumbers (talk) 15:55, 11 December 2023 (UTC)Reply[reply]

Looks like we've already got a ticket here. Thanks for reporting though. It's good to see when issues are popular requests. Then hopefully we can prioritize them. –Novem Linguae (talk) 16:19, 11 December 2023 (UTC)Reply[reply]
+1. I have encountered this as well so I support this enhancement. S0091 (talk) 20:16, 11 January 2024 (UTC)Reply[reply]

Why did the morebits documentation disappear?[edit]

All the links taking to the Morebits documentation now take to a blank GitHub page. Why has it been removed? Nacaru 15:16, 29 December 2023 (UTC)Reply[reply]

Can you give some example links? –Novem Linguae (talk) 12:27, 30 December 2023 (UTC)Reply[reply]
Hmm, probably this link: @SD0001, do you know anything about the Morebits documentation? Here's the list of branches in the repo: Linguae (talk) 12:29, 30 December 2023 (UTC)Reply[reply]
@Novem Linguae The morebits docs were setup by Amorymeltzer. The script is in gh-pages branch, which is also the home for the html output files generated by it. That branch has an associated GitHub Pages deployment, which should have been at I believe (since that's the link mentioned in #1668).
This setup currently requires syncing all code changes to the gh-pages and then invoking the docs script. Not an optimal setup – ideally we should automate the whole thing (see #1405). – SD0001 (talk) 13:00, 30 December 2023 (UTC)Reply[reply]
The wiki link is separate from GitHub Pages and isn't a branch in the same repo—I'm not familiar with how any of the Twinkle docs are generated but was alerted to this via Discord and know enough that I was able to pull the old file and restore it on the GitHub wiki page at The GitHub Pages site on the other hand is a separate task as far as I know. Bsoyka (tcg) 21:21, 1 January 2024 (UTC)Reply[reply]

Deletion notice to blocked creator[edit]

I nominated an article for deletion, and the user who created it has been blocked. However, Twinkle went ahead and left a deletion notice on the creator's talk page. I believe Twinkle should check if the creator is blocked. If they are, then it shouldn't send the deletion notice to them. I hope I'm not repeating something that's already been discussed or reported. If this issue has come up before, I apologize. – DreamRimmer (talk) 06:19, 7 January 2024 (UTC)Reply[reply]

Why shouldn't it notify a blocked user? Writ Keeper  06:45, 7 January 2024 (UTC)Reply[reply]
I can recall one or two instances when I left deletion notices on blocked users' talk pages, but I was reverted by the blocking admin, stating that it doesn't make sense to notify an indefinitely blocked user. – DreamRimmer (talk) 06:52, 7 January 2024 (UTC)Reply[reply]
I think the current norm is to notify blocked users. Would probably be a big deal to change it and would need discussion. I am neutral on the matter but this is what I have observed. –Novem Linguae (talk) 08:47, 7 January 2024 (UTC)Reply[reply]
This has been discussed before, though I can't currently pinpoint where or when. I believe some type of extra notification was discussed, informing the Twinkler that the recipient has been blocked. Here's the thing: even users who are blocked indefinitely can be unblocked, sometimes the next day, they can be 'around' and working on getting unblocked, or they might return one day. Leaving a message can be useful so they can see what went wrong with their methodology. They might even have some insight to offer. Even if they're proper banned this can sometimes be a courteous and helpful thing to do in a 'closure' kind of way. Then, it also makes others who are working in similar topics aware of the deletion discussions, and it informs talk page readers of other potential or related issues. After all, talk pages have the functions of broadcasting and logging, in addition to notifying one user. It's not always appropriate to notify a blocked user, and users should be making an informed decision, rather than posting something because that's what a script does. Special:PageHistory/User talk:ClueBot Commons has some good examples of people not considering what they're doing when it comes to deletion notifications, and there are probably parallels to be drawn. Ultimately it's a judgement call. It's not really Twinkle which should be making judgement calls, it's the Twinkler. -- zzuuzz (talk) 10:49, 7 January 2024 (UTC)Reply[reply]
This is a slippery slope Wikipedia:Village pump (policy)/Archive 106#Blocked users - rescinding watchlist and notification access as part of the block. 2A02:C7B:228:3400:5558:2319:26C2:7300 (talk) 11:49, 7 January 2024 (UTC)Reply[reply]

Feature request for CSD[edit]

When filling in the draft name for {{db-afc-move}}, the field should prefill to Draft:Article name Mach61 (talk) 16:40, 9 January 2024 (UTC)Reply[reply]

Sure. Ticket created.Novem Linguae (talk) 10:03, 10 January 2024 (UTC)Reply[reply]

Nomination for deletion of Template:Uw-ublock-nonsense[edit]

Template:Uw-ublock-nonsense has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. — Red-tailed hawk (nest) 06:23, 11 January 2024 (UTC)Reply[reply]

Template is not in Twinkle. Perhaps someone copied a Twinkle template and forgot to remove the template/category from the documentation that triggers this message. –Novem Linguae (talk) 09:52, 11 January 2024 (UTC)Reply[reply]

U5 wording[edit]

Please change “Blatant WP:NOTWEBHOST violations” to “A non contributor violating WP:NOTWEBHOST”.

The hard criteria for U5 is that the user is not a genuine contributor to Wikipedia. If the user is a contributor, it doesn’t matter how blatant the NOTWEBHOST violation, it has to go to MfD. SmokeyJoe (talk) 00:48, 18 January 2024 (UTC)Reply[reply]

WP:U5 calls it U5. A non-contributor's misuse of Wikipedia as a web host, so aligning Twinkle with this wording seems fine. Will make a ticket. –Novem Linguae (talk) 01:04, 18 January 2024 (UTC)Reply[reply]
Thanks. Noting that I did that. It was a frequently recurring problem at MfD, and still occurs. This change has stuck for over a year, and I think it is a good thing. I was heavily involved in implementing U5. SmokeyJoe (talk) 01:19, 18 January 2024 (UTC)Reply[reply]

Merging help/project pages[edit]

It looks like there's currently no way to nominate pages in the Help or Wikipedia namespaces for merging, because the merge function is under the tag menu, which appears only for articles. That's unfortunate, given that there are plenty of projectspace pages that could use merging, so we want to make it easy to suggest doing so. {{u|Sdkb}}talk 01:57, 19 January 2024 (UTC)Reply[reply]

Ticket created.Novem Linguae (talk) 08:55, 19 January 2024 (UTC)Reply[reply]

Typo on the Welcome template menu[edit]

It says "{{WikiProject Women in Red Invite}}: welcome for users with an intrest in writing about women" instead of "{{WikiProject Women in Red Invite}}: welcome for users with an interest in writing about women" when looking at WikiProject welcomes. - The Master of Hedgehogs (always up for a conversation!) 18:27, 22 January 2024 (UTC)Reply[reply]

Sure. Patch created.Novem Linguae (talk) 20:52, 22 January 2024 (UTC)Reply[reply]

 You are invited to join the discussion at Wikipedia:Village Pump (proposals) § Bump XfD heading sizes. NW1223<Howl at meMy hunts> 19:09, 29 January 2024 (UTC)Reply[reply]

Link fixed. Primefac (talk) 20:04, 29 January 2024 (UTC)Reply[reply]

Can't scroll through options in user welcome and tagging dialogs[edit]

I think this is new--I'm pretty sure I've been welcoming users and tagging articles from my phone all along. But today in both dialogs, in Chrome on Android (Samsung Galaxy S10) I was unable to scroll the issue list. Swiping just scrolled the article. I couldn't grab the scrollbar either, though as far as I know that's normal since I don't normally have any reason to do that. Largoplazo (talk) 18:00, 3 February 2024 (UTC)Reply[reply]

@Largoplazo: You can try using User:Plantaest/TwinkleMobile. Plantaest (talk) 18:52, 9 February 2024 (UTC)Reply[reply]
I'll give it a try, thanks! Largoplazo (talk) 22:57, 9 February 2024 (UTC)Reply[reply]

Errant notifying IP addresses[edit]

I recently nominated a category for renaming, and Twinkle dutifully notified the category creator, which was an IP address...that created the category in 2005. The chance of that message reaching the actual creator is somewhere between negligible and negative. Accordingly, I'd propose that Twinkle disable notices to IP addresses when the relevant action was in the distant past. {{u|Sdkb}}talk 17:27, 7 February 2024 (UTC)Reply[reply]

One could argue that any creator that created a page in 2005 is likely to either not care or not be around. Primefac (talk) 08:35, 8 February 2024 (UTC)Reply[reply]
Probably, but for registered users no harm is done such as would justify the effort to modify the code to create this exception. It's different an IP article creator where the next person to arrive with that IP address won't know what it's about. For IPs, it isn't clear to me that a warning is usually worthwhile even a month later, though there are unregistered users with static IPs. Largoplazo (talk) 17:20, 8 February 2024 (UTC)Reply[reply]
I think the current system of always notifying whoever created the first revision of a page, even if they did it decades ago, is acceptable. It's simple code, a simple workflow, maximizes the chances of notifying the creator, and minimizes complaints about not notifying the creator. –Novem Linguae (talk) 19:27, 19 February 2024 (UTC)Reply[reply]

Feature request: subscribe to user warnings instead of watching talk page[edit]

Is there a way to add an option so that warnings added to user talk pages via Twinkle result in subscribing to the particular month level 2 heading that is created, in lieu of adding the talk page to one's watchlist? Thanks, voorts (talk/contributions) 17:22, 15 February 2024 (UTC)Reply[reply]

Feature request: Do not display username in ES if "offensive username" is ticked[edit]

Recommend using a default string like "Adding [Redacted Offensive Username]" verbatim in ES. It just creates something that will need to be revdel'd after since there's no way to uncheck it after, OR give us a checkbox to optionally redact the username from the ES if offensive username is checked. DarmaniLink (talk) 05:25, 19 February 2024 (UTC)Reply[reply]

Is "es" edit summary? What Twinkle module is "offensive username" in? ARV->UAA? –Novem Linguae (talk) 15:39, 19 February 2024 (UTC)Reply[reply]
Yes it's in twinklearv ::aivPage.setEditSummary() and ::uaaPage.setEditSummary(). I'd also like this, along with wider adoption of this practice, however, I should point out that the edit will still probably need to be rev-deleted due to its content. Still, it'll be one less redacted edit summary for the reporting user, and probably one less combination of tickboxes for the admin to deal with. -- zzuuzz (talk) 16:12, 19 February 2024 (UTC)Reply[reply]

Hi, FYI I just made a substantial but non-breaking change to Template:Db-draft-deleted as explained at Template_talk:Db-notice#Rewording_notification_about_G13_deletions. Cheers, Clayoquot (talk | contribs) 19:32, 23 February 2024 (UTC)Reply[reply]

@Clayoquot. Any changes needed to Twinkle? Did you change any template names, parameter names, etc? If you just changed template prose, probably doesn't affect Twinkle :) –Novem Linguae (talk) 21:35, 23 February 2024 (UTC)Reply[reply]
I only changed parameter prose. Will the change automatically be picked up by Twinkle? Clayoquot (talk | contribs) 23:46, 23 February 2024 (UTC)Reply[reply]
I think so. I think Twinkle just does {{subst:Db-draft-deleted}}. –Novem Linguae (talk) 00:10, 24 February 2024 (UTC)Reply[reply]
Cool. Looks like it's working, see,_Draft:S.J._Ncongwane. Clayoquot (talk | contribs) 01:47, 24 February 2024 (UTC)Reply[reply]

Removal of rcat tagging menu for category redirects[edit]

Is it possible for the redirect tagging funtionality in Twinkle to be deactivated for category soft-redirects (e.g. Category:Angus and Julia Stone)? Per WP:RCAT § When to categorize a redirect, soft redirects shouldn't be categorised with rcats - the only exception for categories being {{R category with possibilities}}.

Let me know if there are any queries. All the best, ‍—‍a smart kitten[meow] 02:44, 26 February 2024 (UTC)Reply[reply]

Are all categories soft redirects instead of regular redirects? (I seem to remember that they are, but I could be wrong.) If they are, can we just turn off the tag module completely for categories? –Novem Linguae (talk) 02:55, 26 February 2024 (UTC)Reply[reply]
Yep, that's my understanding also, per WP:CATRED. The tag module already seems to be disabled for normal (non-redirected) categories, so - as far as I can see - I think it would be okay to disable it for category soft redirects as well. All the best, ‍—‍a smart kitten[meow] 03:04, 26 February 2024 (UTC)Reply[reply]

CSD: Do not send notifications of speedy deletions to creators of user talk pages that are not the user in question[edit]

Recently, I CSD'd a talk page and a user who first templated the vandal in question got a template on their talk page. To avoid from needlessly spamming other peoples user pages and have the template blame them for the vandalism of bad actors on their own talk page, do as the title says. DarmaniLink (talk) 08:15, 26 February 2024 (UTC)Reply[reply]

DarmaniLink nominated a user talk page for U5 deletion (which was an invalid action in the first place as it was a just a copyvio situation, but irrelevant to this post), so the creator of that user talk page got a notification. Technically TW is doing exactly what it should be doing, and I question whether it makes sense to change that. First, user talk pages are very rarely CSD candidates, and second if you are nominating a user talk page for deletion (under a valid CSD criteria) chances are good whoever created that page should know about it.
In other words, if User A creates the user talk page of User B with a vandal/copyright post that should be deleted, they should probably get a notice. If User C just happens to make a vandal/copyright post on their own talk page, I do agree the creator of that page shouldn't get a notice, but that page also shouldn't be nominated in the first place. Primefac (talk) 13:02, 26 February 2024 (UTC)Reply[reply]
FWIW, i got a filter hit and saw he uploaded the entire script for the mario movie to his own userpage and assumed he was using it like a pastebin DarmaniLink (talk) 18:33, 26 February 2024 (UTC)Reply[reply]
Not a bad assumption, just a better case for {{revdel}} than deletion. Primefac (talk) 20:22, 26 February 2024 (UTC)Reply[reply]

Notification opt-outs[edit]

I recently came across this thread from 2021, which seemed to have support for the idea of a talk-page category (or similar) that would opt users out of receiving Twinkle notifications (e.g. for XfD discussions); which could be included within the {{Deceased Wikipedian}} & {{Not around}} templates. As the pull request linked from that thread was closed as stale, and I can't find a relevant issue on GitHub, I wondered if anyone had any information on the current status of such a feature.

All the best, ‍—‍a smart kitten[meow] 03:23, 27 February 2024 (UTC)Reply[reply]

One thing to consider is that sometimes people follow a deceased person's talk page to catch these types of notices. They then work to improve the content in that user's memory. I've found this with several different users when I've nominated old drafts for G13 deletion. Hey man im josh (talk) 03:28, 27 February 2024 (UTC)Reply[reply]
@Hey man im josh: Fair point - thanks for mentioning that,/gen it hadn't occurred to me. I'm not so sure now that this would be a good feature. All the best, ‍—‍a smart kitten[meow] 03:44, 27 February 2024 (UTC)Reply[reply]