Wikipedia talk:Twinkle/Archive 48

This is an archive of past discussions on Wikipedia:Twinkle. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 45

Archive 46

Archive 47

Archive 48

Duplicate sockpuppet reports

Tracked in github.com
Issue #1496

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)

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)

+1. I have encountered this as well so I support this enhancement. S0091 (talk) 20:16, 11 January 2024 (UTC)

Warning templates

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)

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)

Thanks! I'll give it a try. Rusty4321 ^{talk contribs} 02:33, 19 October 2023 (UTC)

Thank you MinecraftPlayer321 (talk) 01:47, 17 January 2024 (UTC)

U5 wording

Tracked in github.com
Issue #1930

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)

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)

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)

Merging help/project pages

Tracked in github.com
Issue #1932

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)

Ticket created. –Novem Linguae (talk) 08:55, 19 January 2024 (UTC)

Typo on the Welcome template menu

Tracked in github.com
Issue #1935

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)

Sure. Patch created. –Novem Linguae (talk) 20:52, 22 January 2024 (UTC)

Additional option for CfD

Tracked in github.com
Issue #1939

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)

@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)

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)

@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)

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)

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. — Qwerfjkl talk 19:28, 23 January 2024 (UTC)

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)

Adding a template

Tracked in github.com
Issue #1897

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)

Sure. I created a ticket. –Novem Linguae (talk) 15:26, 25 November 2023 (UTC)

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)

Discussion at Wikipedia:Village Pump (proposals) § Bump XfD heading sizes

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

Link fixed. Primefac (talk) 20:04, 29 January 2024 (UTC)

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

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)

@Largoplazo: You can try using User:Plantaest/TwinkleMobile. Plantaest (talk) 18:52, 9 February 2024 (UTC)

I'll give it a try, thanks! Largoplazo (talk) 22:57, 9 February 2024 (UTC)

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

Tracked in github.com
Issue #1848

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)

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

Tracked in github.com
Issue #1945

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)

Is "es" edit summary? What Twinkle module is "offensive username" in? ARV->UAA? –Novem Linguae (talk) 15:39, 19 February 2024 (UTC)

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)

Errant notifying IP addresses

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)

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)

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)

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)

Changes to Template:Db-draft-deleted

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)

@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)

I only changed parameter prose. Will the change automatically be picked up by Twinkle? Clayoquot (talk | contribs) 23:46, 23 February 2024 (UTC)

I think so. I think Twinkle just does {{subst:Db-draft-deleted}}. –Novem Linguae (talk) 00:10, 24 February 2024 (UTC)

Cool. Looks like it's working, see https://wiki.riteme.site/wiki/User_talk:ZS_Khumalo#Your_draft_article,_Draft:S.J._Ncongwane. Clayoquot (talk | contribs) 01:47, 24 February 2024 (UTC)

Removal of rcat tagging menu for category redirects

Tracked in github.com
Issue #1947

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)

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)

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)

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

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)

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)

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)

Not a bad assumption, just a better case for {{revdel}} than deletion. Primefac (talk) 20:22, 26 February 2024 (UTC)

Notification opt-outs

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)

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)

@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)

Suggestion: Add "suboptimal" Welcome templates

Tracked in github.com
Issue #1950

Every so often, I'm having to revert a new user's (or IP user's) apparent good faith efforts that have lots of problems, but none of the "problem" Welcome templates that Twinkle provides cover this scenario sufficiently. So, I have to use {{Welcome-suboptimal}} or {{Welcome-anon-suboptimal}} manually outside of Twinkle. Could these be added to the Twinkle selection list? Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 19:54, 5 March 2024 (UTC)

Looks like {{Welcome-suboptimal}} has about 1000 transclusions. Looks good to me. Will create a ticket. –Novem Linguae (talk) 20:33, 5 March 2024 (UTC)

Thanks! Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 20:43, 5 March 2024 (UTC)

Template:Translation request

The instructions said to notify Twinkle if there were "breaking changes" but there weren't so I didn't. But I notice that although direct transclusions of {{Translation request}} (ex-{{Needtrans}}) at WP:PNT are working, most transclusions are not, and I presume those come from Twinkle. The edit in question is rev. 1209066449. Note that there are a couple of edits following that one; they affect solely the presentation of the template page itself, generating the top-of-page example you see there.

P.S., Maybe that wording about "breaking changes" should be modified, because I know what that term means and would have notified Twinkle earlier had the change fit that category, but it does not: new functionality which is fully backward-compatible is not breaking. Unless the problem lies elsewhere, such as in the redirect? Thanks, Mathglot (talk) 03:12, 7 March 2024 (UTC)

@Mathglot. Thanks for the report. Would you be able to link a broken transclusion diff that Twinkle placed, and then also a diff of someone fixing it? That would help me figure out what code changes are needed here. Diffs from WP:PNT preferrably, rather than from Template:Translation request. Thank you very much. –Novem Linguae (talk) 06:14, 7 March 2024 (UTC)

Not broken, in the sense of producing nonsense, just producing the old, valid output that it always used to. Nothing wrong with it, and not harmful in any way, just lacking some useful, new functionality. And since it is (presumably) substed and doesn't leave a hidden text trace of who produced it, I can't be sure that it is even Twinkle at all responsible for it; I just assumed so, since some source continues to produce the old-format output, so what else could it be? (Could even be someone directly typing text onto the page that looks like template output; unlikely, but not impossible.) While looking around for an example for you just now, I realized that the new template version doesn't have proper subst-protection, so let me go fix the Template so you have clean output to compare with. But n the meantime here are a few links that I presume are Twinkle, in case you want to look at these: § Cerveza Cristal (Chile), § Heiligenhoven Castle. I'll get back to you soon when the template is ready. Mathglot (talk) 06:36, 7 March 2024 (UTC)

Hm, won't be quite as quick as I thought. Subst-protection in Template:Translation request actually seems to be okay as is, at least at first glance, so the problem likely lies in one of the newly invoked templates that was not used before. There are two such: {{ISO 639 name}}, which appears to be properly subst-protected , and {{Sitelink}}, which is not. So to get {{Translation request}} to work, I'll have to convert Sitelink to be substable, and it's not one I've worked on before. In principle it should be mechanical and mostly about making sure I don't break anything; but there are a lot options and there is no sandbox or testcases. I may have to ask for help with that one. I'll get back to you on this. Adding Ponor, who is familiar with {{Sitelink}} and may be able to convert it more easily and quickly than I could. Mathglot (talk) 06:58, 7 March 2024 (UTC)

Twinkle edits can be easily identified because it uses an edit tag. So Cerveza Cristal (Chile) was indeed placed by Twinkle (diff). OK, so now we have the first diff. Is there anything wrong with this diff that needs fixing? The code Twinkle is using to place that diff is

'{{subst:duflu|pg=' + Morebits.pageNameNorm + '|Language=' + (lang || 'uncertain') + '|Comments=' + reason.trim() + '}} ~~~~'

The other possible code that Twinkle uses on that page is

'{{subst:needtrans|pg=' + Morebits.pageNameNorm + '|Language=' + (lang || 'uncertain') + '|Comments=' + reason.trim() + '}} ~~~~'

–Novem Linguae (talk) 07:39, 7 March 2024 (UTC)

Ah, that is indeed helpful. Here is the unsubsted output showing the new output for Needtrans (now renamed to {{Translation request}}):

Two examples

1. {{Needtrans |pg=Cerveza Cristal |language=Spanish |comments=Further remarks.}} ⟶

Cerveza Cristal

The original article, Cerveza Cristal (Chile), is in Spanish. Further remarks.

2. {{Needtrans |pg=Heiligenhoven Castle |language=German|comments= }} ⟶

Heiligenhoven Castle

The original article, Schloss Heiligenhoven, is in German.

What I don't quite understand, is why Twinkle doesn't already produce the right output, as it appears to be just generating the code for a call to Needtrans, and since the new output you see above doesn't depend on any new parameters but is derived directly from existing params and Wikidata, I don't quite see why Twinkle would produce different output in that case. (Note that the first article appears to have been renamed to Cerveza Cristal at en-wiki.) This doesn't obviate the need to subst-protect {{Sitelink}}, but it does raise a new question of why Twinkle isn't already picking up the new format. Or perhaps, the subst issue blocks it, somehow? Mathglot (talk) 08:19, 7 March 2024 (UTC)

Hmm. I'm still a bit unclear about what the bug is. A diff of the wrong Twinkle output, and a diff fixing it, would be helpful. –Novem Linguae (talk) 08:35, 7 March 2024 (UTC)

Pasting the below into Wikipedia:Pages needing translation into English

{{subst:needtrans|pg=Cerveza Cristal |language=Spanish |comments=Further remarks.}} ~~~~

{{subst:needtrans|pg=Heiligenhoven Castle |language=German}} ~~~~

Renders this. Is that what you need?

If you need me to do it in Twinkle, I can do it on https://test.wikipedia.org/. But I suspect it will be exactly the same, so starting with this. –Novem Linguae (talk) 09:41, 7 March 2024 (UTC)

Yes, that produced exactly the correct result—although unsubsted, for reasons previously discussed—but note that the rendered-page output is exactly like the collapsed examples above. So the mystery has shifted from the earlier, 'why isn't Twinkle picking up the latest changes?' (answer: it is picking them up), to: 'Why did the two examples cited end up without the new functionality of linked foreign page at WP:PNT when placed earlier by users using {{Needtrans}}?' I don't know the answer to that new mystery, but we don't have to resolve that, because it appears to be working now.

As an aside: I just went back to WP:PNT and noticed that someone just added § Potato production in France using {{Dual fluency request}} (per the hidden comment you added only hours before—great timing; thanks for that!) and is tagged Twinkle in history, that isn't invoking the new functionality, either. That is understandable, as {{Duflu}} is its own template (formerly merged to needtrans then unmerged, for reasons which need not concern us here). {{Duflu}} should have similar functionality added as happened here, and once the subst issue is clarified, I'll add it, or leave a Talk message about it.

I apologize that this got into the weeds a bit and has been confusing and lengthier than I expected. The bottom line is this: we still need to make {{Sitelink}} substable to get {{Needtrans}} up to par (nothing to do with Twinkle) and I doubt you will have to change anything in Twinkle at all for this template, it will just work. Same thing for {{Duflu}} once it is updated to match. I think the right stance now for Twinkle folks regarding these two, is "watchful waiting". It bears monitoring, but I don't expect you'll have to do anything at all to be compatible and in sync. Mathglot (talk) 21:58, 7 March 2024 (UTC)

Sounds good. Glad you liked the hidden comment I added to duflu. I also wrote a Twinkle patch that will make this area of Twinkle code more readable the next time I have to look at it. –Novem Linguae (talk) 01:16, 8 March 2024 (UTC)

Looks like Ponor is not around, so I went ahead and added subst protection to {{Sitelink}}. Now, substing {{Needtrans}} looks okay, via this brief live test in WP:PNT. This should complete this upgrade, and I don't expect any further changes will be required at Twinkle, but please watch with one eye for a little while. Thanks, Mathglot (talk) 02:34, 8 March 2024 (UTC)

Template:Dual fluency request

Courtesy link: Template:Dual fluency request

Non-breaking changes have been made to {{Dual fluency request}} to parallel similar changes to {{Translation request}} as discussed above at § Template:Translation request. I understand "non-breaking" as meaning that nothing will go wrong if you make no changes at the Twinkle end; however, the new version is more powerful, as it retrieves the foreign-language article automatically via Wikidata linkage. Parameter |orig= was formerly required in order to provide a link to the foreign article, but now it is no longer required and its use is discouraged. The |orig= parameter is still available (not deprecated) and if used, will override the Wikidata page link with whatever the user provides as the param value, so it exists solely as an override and to maintain backwards compatibility. If automatic processes generate the transclusion, then probably all you have to do is drop the use of parameter |orig=; everything else can remain the same; however nothing will break if you leave everything as is. If you do make the change, the result will be improved output at WP:PNT. Mathglot (talk) 01:45, 23 March 2024 (UTC)

@Mathglot. Thanks for your work on this. According to the program code, Twinkle posts in the format

{{subst:duflu|pg=' + Morebits.pageNameNorm + '|Language=' + (lang || 'uncertain') + '|Comments=' + reason.trim() + '}} ~~~~

. So I think it only uses the pg, language, and comments parameters of the template, and doesn't ever use orig. So probably no changes needed on Twinkle's end. –Novem Linguae (talk) 02:15, 29 March 2024 (UTC)

That sounds right to me. We should watch as the next few Duflu's from Twinkle come through to WP:PNT. I think the last one was this one, which says, "The initial language of this article was de.". I noticed another one just above it which also uses a lang code instead of a language name; could this be something in the Twinkle doc, or does Twinkle just point to the template doc and users are misreading/not reading it? Another upgrade to Duflu could eliminate this problem by emulating another change at Needtrans, which interprets lang codes if the user uses one by mistake instead of fully spelling out the language. Mathglot (talk) 02:38, 29 March 2024 (UTC)

Another upgrade to Duflu could eliminate this problem by emulating another change at Needtrans, which interprets lang codes if the user uses one by mistake instead of fully spelling out the language. This sounds like the way to go if it isn't too time consuming. In an ideal world, there's no reason these two similar templates should have divergent behavior for the same collected parameters. –Novem Linguae (talk) 04:12, 29 March 2024 (UTC)

Twinkle placement of RFDs when header gets messed up.

@Steel1943. Hey there. Re this ping. Twinkle's current algorithm is to place entries directly below . In the situation on that RFD page, a new user placed their entry above that comment, ignoring the instructions. My recommended fix is to move all entries below that comment. I am disinclined to change Twinkle's algorithm since it's simple and it usually works fine. Hope that makes sense. –Novem Linguae (talk) 02:01, 29 March 2024 (UTC)

@Novem Linguae: Of course (it makes sense). I was, more or less, suggesting that whatever XFDcloser does to determine the top of the page when relisting, somehow incorporate that into Twinkle with posting new RFDs since whatever XFDcloser does is not reliant on that hidden text whereas Twinkle is. Steel1943 (talk) 04:56, 29 March 2024 (UTC)

COI template

Documentation for {{COI}} says (formatting per original):

Like the other neutrality-related tags, if you place this tag, you should promptly start a discussion on the article's talk page to explain what is non-neutral about the article. If you do not start a discussion, any editor will be justified in removing the tag without warning.
[...]
Do not apply this tag simply because you suspect COI editing, or because there is or was a COI editor.

Can Twinkle be made to notify users of these terms, or at least to nudge them to comment on the talk page immediately after applying the template? There may be other templates with similar conditions, so a generic fix might be best. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:41, 15 March 2024 (UTC)

@Pigsonthewing. Looks like Twinkle already does this. Screenshot. –Novem Linguae (talk) 02:08, 29 March 2024 (UTC)

Yes, if "this" is part of my latter, fallback, suggestion. More would be better. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:01, 29 March 2024 (UTC)

Contentious topic alerts

Tracked in github.com
Issue #1806

Can Twinkle be made to work with {{alert}} and its various permutations? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:04, 29 March 2024 (UTC)

I created a ticket for this in June of last year. Would be a lot of work though. Would probably need to create a new module. There's already a user script that does this at User:TheresNoTime/Scripts/CT-Helper.js if you want to try that out. –Novem Linguae (talk) 03:40, 30 March 2024 (UTC)

Add Template:Welcome-anon-unsourced

Tracked in github.com
Issue #1957

Often IP user's will add information that appears good faith, but could be problematic or suspected of lacking a neutral point of view. I would like to welcome these IP user rather than scare them off with a warning template. Could {{Template:Welcome-anon-unsourced}} added to the Twinkle selection list? It is a more friendly and instructive way of welcoming users rather than {{Template:Welcome-anon-unconstructive}}. Apologies if this has been settled before. Classicwiki (talk) If you reply here, please ping me. 19:12, 29 March 2024 (UTC)

Sure. Ticket created. I think you can just add this as a custom welcome template in your Twinkle preferences though. Wikipedia:Twinkle/Preferences#welcome, "Custom welcome templates to display". Might be quicker than waiting for a patch. –Novem Linguae (talk) 03:51, 30 March 2024 (UTC)

Language problems

Tracked in github.com
Issue #1958

I noticed that the Twinkle automated system for non-English welcomes does not support some languages for which we have a template, such as Italian and Hindi. Can this be fixed? Kind regards 14 novembre (talk) 🇮🇹 11:19, 3 April 2024 (UTC)

What are the exact template names please? –Novem Linguae (talk) 11:47, 3 April 2024 (UTC)

@Novem Linguae {{welcomeen-it}} and {{welcomeen-hi}} 14 novembre (talk) 🇮🇹 13:15, 3 April 2024 (UTC)

Sounds good. I created a ticket. Same advice as in the section above though. You can just add these to Twinkle via your Twinkle preferences. –Novem Linguae (talk) 14:40, 3 April 2024 (UTC)

@Novem Linguae Perfect. Thank you so much and kind regards 14 novembre (talk) 🇮🇹 15:58, 3 April 2024 (UTC)

Confused

It is in the speedy deletion procedure. Summaries for administrators are always "speedy deletion of <pagename>" while for all others (including me) it is "speedy deletion nomination of <pagename>" Why are summaries different for admins and others? Toadette ^{(Let's talk together!)} 22:37, 3 April 2024 (UTC)

@ToadetteEdit: Admins have the option of directly deleting the page with Twinkle, rather than simply nominating it for deletion. When this happens, Twinkle will leave a different warning template on the user's talk page that's been rewritten to inform the user that the page had already been deleted. For example, see the difference between {{Db-vandalism-notice}} and {{Db-vandalism-deleted}}. —k6ka 🍁 (Talk · Contributions) 12:32, 4 April 2024 (UTC)

{{Uw-copyright-new}} body text revision and improvements

Good day, this is a courteous message to inform Twinkle’s maintainers and users that:

Implemented: Revision and improvement to the body text in the warning message for {{Uw-copyright-new}}, a 'Single-issue warning' in Twinkle.
Not sure. This should only affect Twinkle, and its users, if the boldtext parameter is used. In such a case, string of text in |boldtext=string of text may no longer function as expected as the body text at {{Uw-copyright-new/body}} has changed. But it seems it would be used more by users who would add the template manually than via Twinkle.
Checked: Checked testcases and tried implementation with Twinkle in many ways as possible. Functioning as expected.

waddie96 ★ (talk) 19:35, 5 April 2024 (UTC)

I only see the word "boldface" in Twinkle's code somewhere else, not in connection with {{Uw-copyright-new}}. I don't think any action is needed. Thank you for checking. –Novem Linguae (talk) 21:54, 5 April 2024 (UTC)

question about notifications

Tracked in github.com
Issue #1848

I have noticed that when users respond to a welcome message that I have left using twinkle, I don't seem to get notified. Is there a way for me to fix this? Gaismagorm (talk) 20:00, 7 April 2024 (UTC)

It's a good idea and has been requested before. More info in this ticket. –Novem Linguae (talk) 21:35, 7 April 2024 (UTC)

ah ok Gaismagorm (talk) 21:48, 7 April 2024 (UTC)

For file maintenance - add these two templates

Tracked in github.com
Issue #1959

For file maintenance, I suggest adding both {{Nominated for deletion on Commons}} and {{Deleted on Commons}} among the Twinkle options, as useful notice tags that the Commons copies of local files were nominated for deletion or deleted.

This is helpful in conducting future undeletion of files, in which the Commons copy should be requested for undeletion instead of transferring the local copy to Commons, as the transfer action effectively overwrites the deleted Cpmmons copy of the same file name. JWilz12345 (Talk|Contrib's.) 03:04, 8 April 2024 (UTC)

Sounds good to me. Ticket created. In the meantime, you can add them in Wikipedia:Twinkle/Preferences#tag -> Custom file maintenance tags to display -> Edit items. –Novem Linguae (talk) 08:53, 9 April 2024 (UTC)

@Novem Linguae thanks for opening the suggestion at GitHub. By the way, I also suggest the tags will be automatically placed above the information fields, like this. If the template is found at the lower part of the description page, some future file movers may not notice it and still conduct transfer of the said file even if there is an identical copy on Commons that can be simply requested for undeletion. JWilz12345 (Talk|Contrib's.) 10:19, 9 April 2024 (UTC)

@JWilz12345. Do you know if this is the "normal" spot to put the template? Is there an MOS:FILEORDER somewhere? Do we need to get consensus for placing these tags in an odd spot? –Novem Linguae (talk) 21:11, 12 April 2024 (UTC)

Custom topic title

Is it possible to customize topics' titles or heading when using Twinkle? —Saqib (talk | contribs) 18:08, 11 April 2024 (UTC)

@Saqib. Is this for placing warnings on user talk pages? Something else? Do you have a diff you could provide of what Twinkle currently does, along with what you'd suggest changing the text to? –Novem Linguae (talk) 21:13, 12 April 2024 (UTC)

@Novem Linguae: I meant is there a way to customize the title when posting a warning message on a user talk page, instead of using the default title based on the current month. --—Saqib (talk | contribs) 17:26, 13 April 2024 (UTC)

I don't see anything like this in Wikipedia:Twinkle/Preferences#warn. There is other software that uses month headers, such as WP:HUGGLE, so changing the header name could result in problems. –Novem Linguae (talk) 02:34, 14 April 2024 (UTC)

Changes to Template:Db-notice-multiple

Hi. Redrose64 reverted my changes, so I'll need to discuss this with you. I made the change for Template:Db-notice-multiple, which added features that can help users clarify if it was a hoax or not, or an unsourced biography of a living person that is entirely negative in tone or not. What do you think about the change? Should we accept the change?
Link to change: https://wiki.riteme.site/w/index.php?title=Template:Db-notice-multiple&oldid=1218647146 71.208.39.196 (talk) 17:13, 13 April 2024 (UTC)

You'll probably want to discuss this at Template talk:Db-notice instead of here. –Novem Linguae (talk) 02:35, 14 April 2024 (UTC)

Uw-ai1 set

Tracked in github.com
Issue #1901

Hi, what's the process of getting the {{Uw-ai1}} through 3 warning templates added? microbiologyMarcus ^{[petri dish·growths]} 16:29, 16 April 2024 (UTC)

Looks like we already have a ticket for it. Next step is a volunteer dev needs to write the patch and submit it to GitHub as a pull request. –Novem Linguae (talk) 21:40, 16 April 2024 (UTC)

Add Template:Uw-talkinarticle Series

Tracked in github.com
Issue #1961

Could we add {{uw-talkinarticle1}}, {{uw-talkinarticle2}}, and {{uw-talkinarticle3}}? It is already found on WP:UV, would be good to have on Twinkle. (I have already added it to my custom preferences, but its not ideal). I would prefer if was standard UW option. Classicwiki (talk) If you reply here, please ping me. 20:28, 17 April 2024 (UTC)

Ticket created. –Novem Linguae (talk) 23:40, 17 April 2024 (UTC)

Patch to change the linter to eslint-config-wikimedia

Tracked in github.com
Issue #1965

Developers might be interested in this: I created a patch tonight to change Twinkle from its custom eslint rules, to use the plugin eslint-config-wikimedia. Eslint-config-wikimedia is the standard wikimedia set of linter rules. I think there's some good advantages to switching to the standard wikimedia linter (discussed in more detail in the ticket). I've turned off controversial rules such as requiring spaces in parentheses, and turned off limiting line lengths to 100 characters. If there's any concerns or objections, please let me know here or in the ticket. I think getting more rules turned on via this plugin is going to be an important step in modernizing the codebase.

Note that this patch also applies all the auto fixes, which includes a conversion from var to let/const. Wikimedia grade A support appears to be firmly at ES6 now, so it should be safe to make ES6 upgrades. This new linter also includes strict rules (stricter than previously) that warn if we try to use features over ES6, which is a nice feature for making sure we align with grade A support.

Thanks. –Novem Linguae (talk) 06:54, 22 April 2024 (UTC)

Talk Page with AIV Issue

Tracked in github.com
Issue #1966

Hi there,

Sorry that the title might not mean what you thought it means. I’ve encountered a problem many times where Twinkle brings me to the talk page of “wiki/User talk:User name/IP” which is annoying. This happens when I do the following:

Revert vandalism from diffs in Recent Changes
Warn user/IP in their talk page
Right after warning, click TW and ARV
Because the page automatically refreshes after a few seconds after warning user through TW menu, it brings me to wiki/User talk:Username/IP (note that Username/IP is the username or IP address of the vandalizing editor).

This issue is really annoying and should be fixed. Could others review that this is not just happening to me? Thank you! Myrealnamm (💬talk · ✏️contribs) at 22:46, 25 April 2024 (UTC)

So the problem is that Twinkle is closing the ARV screen before you're able to hit submit, because of the auto refresh? –Novem Linguae (talk) 05:07, 26 April 2024 (UTC)

Yes, and it brings me to "wiki/User talk:Username or IP address" which is an invalid page.

The ARV screen is useful right after warning a user because it auto fills all the important details about vandalizing, so it would be helpful if it doesn't refresh if you go to the ARV screen in time. Myrealnamm (💬talk · ✏️contribs) at 14:37, 26 April 2024 (UTC)

Sorry, forgot to ping: @Novem Linguae Myrealnamm (💬talk · ✏️contribs) at 14:37, 26 April 2024 (UTC)

This might be a dumb comment, but maybe... wait until the page refreshes before trying to multi-tag with TW in one set? Primefac (talk) 15:10, 26 April 2024 (UTC)

Thanks, but if the page refreshes the auto fill for ARV reporting is gone. I think... Myrealnamm (💬talk · ✏️contribs) at 17:40, 26 April 2024 (UTC)

I have just verified: when I reverted vandalism and warn the user, and go to the ARV menu, Twinkle brings me to /wiki/User talk:Username or IP. Myrealnamm (💬talk · ✏️contribs) at 20:41, 26 April 2024 (UTC)

OK, I was able to reproduce this. I had to click really fast to beat the refresh though, which I think is on a timer for only 3 or 5 seconds. Ticket created. I don't plan on working on this soon, so for now you may just want to get in the habit of hitting F5 (refresh) as soon as Twinkle's status says it has posted the warning. Then do ARV after that. –Novem Linguae (talk) 06:23, 28 April 2024 (UTC)

Or long-press Esc after submitting the warning to prevent the page from refreshing. Nardog (talk) 06:32, 28 April 2024 (UTC)

@Nardog,

I tried to hold esc while hitting ARV, however, once I am in the ARV page and esc is pressed, it will "close" that dialogue and bring back to the warning page (which is already open) and show another "Warning complete. Reloading page in a few seconds" under the previous. After the few seconds, it will bring me to an even more non-sense page @Novem Linguae.

Example: /wiki//wiki/User talk:103.105.145.206

Myrealnamm (💬talk · ✏️contribs) at 00:11, 29 April 2024 (UTC)

I mean long-press Esc right right after "Warning complete, reloading talk page in a few seconds" for a few seconds. Then open ARV. Nardog (talk) 04:41, 29 April 2024 (UTC)

Hello @Novem Linguae,

Thanks for your reply. My point is that after going to a user or IPs talk page after reverting vandalism, Twinkle knows about what happened (from “Grabbing data of earlier revision) and auto fill ARV screen, Warn screen and more. However, I believe that if I refresh the page, the auto fill is removed/cleared. @Nardog I will try that.

Myrealnamm (💬talk · ✏️contribs) at 18:02, 28 April 2024 (UTC)

Update on TwinkleMobile

TwinkleMobile now has the revert feature thanks to a recent update of the Minerva skin, phab:T350181. Please give it a try, everyone. Plantaest (talk) 17:24, 29 April 2024 (UTC)

Toc styles for config page

Tracked in github.com
Issue #1969

Vector 2022 has not (for a long time) provided styles for tables of content. Twinkle-config.js currently constructs a table of contents by hand more-or-less matching what you would have found in old Vector and in the other skins but because Vector 2022 does not send styles, the rendering ends up being more or less "basic" (see Wikipedia:Twinkle/Preferences). I would guess most other skins this displays as a "normal" table of contents.

Not sure if the best solution is to pull in all the styles Twinkle might want here (noting that all the other skins send table of contents styles basically everywhere) or what (the rules could be prefaced with .skin-vector-2022 so that only Vector gets different skinning, etc). Izno (talk) 22:01, 29 April 2024 (UTC)

Template:Db-x3

Tracked in github.com
Issue #1970

Please add Template:Db-x3. Gonnym (talk) 15:16, 2 May 2024 (UTC)

My 2 cents as the closer is that it would be most convenient to place this under the "redirects" header. Mach61 01:13, 3 May 2024 (UTC)

Existing tags showing up twice

The Tag portlet shows existing tags at the top. Sometimes these are listed twice, even though they're only present once in the article. jlwoodwa (talk) 23:14, 24 May 2024 (UTC)

Example? Nardog (talk) 00:35, 25 May 2024 (UTC)

CSD speedy deletion tool notification bug?

Regarding the speedy deletion nomination tool, I WP:G4'd a redirect and NOT an article. Twinkle then left a notification on the creator's page whilst simultaneously welcoming the user. Is this an intended feature for when an article gets CSD nominated if the user's talk page also needs to be created? I'm not sure if this is intended for when a redirect gets speedy delete nominated though. Thanks, Fork99 (talk) 10:52, 3 May 2024 (UTC)

Actually thinking about it, I think the intent to welcome makes sense, just I think that the wording is a bit off with the "problem user welcome template" as it mainly talks about article policy. Fork99 (talk) 11:01, 3 May 2024 (UTC)

@Fork99. You can visit Wikipedia:Twinkle/Preferences#speedy, scroll to "Welcome page creator when notifying with these criteria", and untick G4 if you want. –Novem Linguae (talk) 06:05, 26 May 2024 (UTC)

Unlink and disambiguation pages

I am wondering what the Unlink tool should do on disambiguation pages. Edits like this aren't really helpful: manual removal of the entire entry is the correct action, not just unlinking of the term. Perhaps it would be best to just skip disambiguation pages and tell Twinkle users to deal with disambiguation pages by hand? Ping @Liz whose edits made me notice this issue. —Kusma (talk) 16:36, 9 May 2024 (UTC)

Two things. First, Liz doesn't answer pings, so if you want her to know about this discussion you'll need to drop a talk page note. Second, there's a checklist given when unlinking, so anything with (surname) or (disambiguation) should be unchecked by the user doing the unlinking.

That said, making it uncheck those pages automatically would prevent things like this from happening as often, so I can't say that I'm opposed to the idea. I don't know a ton about the backend of Twinkle so I don't know if it would be able to detect if a page is a dab, though. Primefac (talk) 16:40, 9 May 2024 (UTC)

A third possible option would be to have an option like with WP:XFDC in which the user could specify "delink or remove entirely", but I somehow think the devs are going to throw forks at me for even suggesting it. Primefac (talk) 16:42, 9 May 2024 (UTC)

Removing entirely is often the right action for dabs, even if they don't have (disambiguation) in the title. Theoretically there might be a WP:DABMENTION elsewhere, but I would hope AfDs for such cases replaced the article by a redirect rather than deleting. There may also be rare cases where the deleted link is not the main topic (*[[Joe Redlink]], a singer with [[Deleted Band]]) but we probably want to delete those entries too. (And if the devs throw forks at us, we can use choose either version!) Certes (talk) 17:21, 9 May 2024 (UTC)

Thanks. I have not done any deletions of widely linked pages for a while, so I am not too familiar with the current interface. Unchecking dabs and dab-like pages by default seems a good first step. I will let Liz know of this discussion. —Kusma (talk) 21:26, 9 May 2024 (UTC)

Thanks for letting me know about this discussion. Since many admins tend to "specialize" in different areas, it would help to know where this problem is arising, is it with CSD-tagged articles, PRODS or pages deleted through the XFD processes. If we could specify when the behavior you find problematic is occurring, and there is some kind of consensus that this problem exists, if it's not a change with Twinkle, then it could be a matter of advising a half dozen admins to process deletions differently. For example, I only know of 5 or 6 admins who regularly handle PRODS so this might be a matter of retraining.

My only hesitation when this issue has come up before is we have to find a way of dealing this that can scale. We're not talking about checking links on a dozen articles a day but on hundreds of pages that are deleted daily. The current system is probably too blunt but I deleted an article the other day that had 94 links to other articles. While it's not much effort to scan a list of links, checking each link individually is not feasible with each page deletion. I'm not saying the current system is perfect (it obviously isn't) we are doing what we can with a decreasing number of admins. An admin I work with took a week off and the drafts that needed to be reviewed immediately piled up and we didn't "catch up" for days. I'll check back and see what y'all have to say about this. Liz ^{Read! Talk!} 23:53, 9 May 2024 (UTC)

The example specifically used above was the PROD of Clint Morris. Primefac (talk) 11:35, 10 May 2024 (UTC)

On the technical side, Twinkle uses the API query ?action=query&list=backlinks to generate the list. This does not support filtering out or indicating disambiguation pages. To write a patch that filters out or indicates disambiguation pages, at least one additional API query would be needed.

To write a patch that detects (disambiguation) at the end of a title would be much easier, but would miss a lot of disambiguation pages.

I think XFDCloser is the most common source of backlink removal, since that would handle backlink removal for AFD.

In the case above, Twinkle's backlink remover is being used to help with PROD.

I'm not entirely sure what to patch here or if it's worth it since it is probably used infrequently, but am open to further ideas if someone wants to propose something specific, such as adding an "untick disambiguation pages" link to the backlink list page. –Novem Linguae (talk) 06:26, 26 May 2024 (UTC)

Tags for user-generated and BLP reference issues

Tracked in github.com
Issue #1972

Could {{user-generated}}, {{BLP one source}}, and {{BLP no footnotes}} be added to the Tag portlet? jlwoodwa (talk) 05:02, 26 May 2024 (UTC)

@Jlwoodwa. Ticket created. You can also add it in Wikipedia:Twinkle/Preferences#tag -> Custom article/draft maintenance tags to display -> Edit items. –Novem Linguae (talk) 08:12, 26 May 2024 (UTC)

Uw-multiple-accts

Tracked in github.com
Issue #1971

In my honest opinion {{Uw-multiple-accts}} should also be accessible through Twinkle warning menu, right? I was astonished it wasn't added yet. Best, A09|(talk) 14:21, 23 May 2024 (UTC)

You use it that often? Genuinely curious, given that I didn't even know it existed until just now. Primefac (talk) 11:09, 24 May 2024 (UTC)

@A09. Looks like it's been used 60 times in 15 years. Not very common, but I suppose we can add it. By the way, you can also add it to your Wikipedia:Twinkle/Preferences#warn -> custom warning templates to display -> edit items. –Novem Linguae (talk) 06:35, 26 May 2024 (UTC)

@Novem Linguae: Oh didn't even know this was an option, will set this up. A09|(talk) 08:49, 26 May 2024 (UTC)

Feature suggestion for XfD nominations

Twinkle's XfD nomination toolset should have a feature where it checks if the page creator is blocked from editing, and if so, skip placing an XfD notice on the user's talk page. This is an issue that I've been seeing a lot on many blocked/banned users' talk pages, where other editors have to constantly come and clean up the notices that were placed there, a good majority of them from Twinkle. — AP 499D25 (talk) 00:44, 25 May 2024 (UTC)

Not all blocks are permanent, though. Maybe Category:Wikipedians who opt out of message delivery or similar would be more appropriate? jlwoodwa (talk) 01:31, 25 May 2024 (UTC)

I think this has come up before, and consensus was to err on the side of over-notification. I agree with an over-notification strategy. Blocked users may get unblocked, or may be indeffed and may still want to know what is happening to their articles. –Novem Linguae (talk) 02:10, 25 May 2024 (UTC)

If anything I don't see the reason why other editors have to constantly come and clean up the notices - they do no harm. Primefac (talk) 14:24, 25 May 2024 (UTC)

I'll give the latest example, User talk:BrownHairedGirl, the history is quite messy on that one! — AP 499D25 (talk) 02:37, 26 May 2024 (UTC)

I think it's better to allow user-level optouts by placing a configurable template on the talk page. By default, blocked and and even deceased users want notifications when their articles are being considered for deletion. (Not the deceased user themself, but their talk page watchers.) – SD0001 (talk) 08:54, 26 May 2024 (UTC)

Allow adding deletion sorting categories to all XFD venues

As I've also mentioned in WT:Deletion process#Deletion sorting should be advertised on all XFD venues, deletion sorting is meant to be used with all XfDs, not just AfD. This can be seen in {{Deletionlist}} which explicitly allows linking to any XfD page or even to PRODs from a deletion sorting page. I think this is an underutilised feature of deletion sorting that would become more widely used (and known) if Twinkle supported it. Nickps (talk) 14:50, 26 May 2024 (UTC)

Custom tags can't be put in multiple issues

The Tag portlet will collect compatible tags into {{multiple issues}}, but custom tags (added in user preferences) can't be marked as compatible. jlwoodwa (talk) 20:55, 26 May 2024 (UTC)

"Twinkle Rollback" includes error with articles with "Map" feature

Hello,

On this certain article, Interstate 90 in New York, when I revert multiple vandalism by someone with the "Rollback" button in Twinkle by "comparing selected revisions", it gives me a dialogue to confirm that they have made 3 edits and I would like to revert them all. However, Twinkle keeps a "map" button that is most likely unintended.

Example:

From Wikipedia, the free encyclopedia Notice: Stopping revert. Map

After map shows [3].

Does this occur to every article that has a "map" in it?

Thanks! Myrealnamm (💬talk · ✏️contribs) at 21:53, 29 April 2024 (UTC)

The [1] with the external site logo just represents the logo in the link given. Right after the word "Map" shows the logo. Myrealnamm (💬talk · ✏️contribs) at 21:59, 29 April 2024 (UTC)

@Myrealnamm. I assume this is in regards to this revision. Can you provide a screenshot to help me visualize what is going on? Is Twinkle rollback broken or does Twinkle rollback still revert the edits? –Novem Linguae (talk) 05:57, 26 May 2024 (UTC)

Well, I can't get a screenshot anymore, but when I clicked "Rollback" (the blue button), all the content of the article disappears (which is normal) and shows the progress of the revert. Because there were 3 edits by the same user, Twinkle will ask "This user has made 3 edits in a row. Are you sure you want to revert them all" or something similar. However, in the "progress" of the revert, it shows:

Map (logo)

Replace (logo) with the link provided I said earlier. Myrealnamm (💬talk · ✏️contribs) at 00:20, 27 May 2024 (UTC)

Feedback: add reported users to watchlist

Hi, I am grateful to have Twinkle aid my anti-vandalism and anti-spam efforts. I would like a new feature: I should be able to automatically watchlist the userpages of whoever I report to AIV, UAA, etc. to stay aware of further vandalism developments. Thank you for considering this feature. Air on White (talk) 22:55, 26 May 2024 (UTC)

Doesn't it already do this? I feel like every time I file an SPI they end up on my watchlist. Or is it just for blocking? Primefac (talk) 11:39, 27 May 2024 (UTC)

According to Twinkle settings, SPI is the only user-reporting page for which it adds the userpage to your watchlist. Air on White (talk) 21:54, 27 May 2024 (UTC)

Hah! Figures. Primefac (talk) 11:37, 28 May 2024 (UTC)

Formatting issue when protecting AfDs

I thought I'd mentioned this, but don't see it in the archives. @Novem Linguae and others, is there any way to fix the issue where the protection has a format error with AfD because of the lack of line break. I usually catch it, but sometimes others (courtesy ping of thanks to @Bearcat) have to. With the AfD troll active there's a lot of semi'ing happening. Thanks either way and of course let me know if you need more info. Star Mississippi 13:07, 2 June 2024 (UTC)

Sure, I can look into it. My first thought for a fix is to keep it on the first line and add a line break. Do you think that would work @Bearcat, or does it have to go on the second line? –Novem Linguae (talk) 13:15, 2 June 2024 (UTC)

I thought the problem was that the template was before the page header at all, but I just did a test edit and indeed it was actually the lack of a line break — if I add a line break, the page works properly. So no, it's not that the template has to go on the second line, I just didn't realize that just inserting a line break would have worked the same way to fix the issue. Bearcat (talk) 13:31, 2 June 2024 (UTC)

Thanks both! I don't think it always happened, but seems to happen with every protected AfD now. Star Mississippi 13:36, 2 June 2024 (UTC)

Rollback AGF's description

When using Twinkle's AGF option, the following popup appears: "An optional comment for the edit summary..." If this should not be optional, please change that wording.--☾Loriendrew☽ ☏(ring-ring) 22:43, 5 June 2024 (UTC)

TW doesn't leave Template:Shared IP Advice if warned in Contribution page

Hi there,

I noticed that Twinkle stopped or doesn't leave Shared IP Advices if warnings are made on the contributions page of an IP user. To reproduce:

Go to an IP's contributions page, like this one.
Hit the TW button.
Click on Warn
Give any warning, such as Uw-Vandalism1
There is no {{sharedipadvice}} given.

Thanks! Myrealnamm's Alternate Account (talk) 13:18, 5 June 2024 (UTC)

@Novem Linguae Could you take a look at this? Is this something I can change in Twinkle Preferences? Thx. Myrealnamm's Alternate Account (talk) 15:05, 11 June 2024 (UTC)

TwinkleStarter/enwiki's tag module misidentifying ptwiki tags

Hi! I've been working on TwinkleStarter to localize it to the Portuguese Wikipedia. I've been adapting the enwiki tag module, since it's "already setup", having only changed the tags themselves, nothing else, but I've encountered issues with tags being misidentified when they're already present in the page, more specifically, {{Sem notas|data=março de 2016}} and {{Corrigir}} (pt:Predefinição:Sem notas and pt:Predefinição:Corrigir) have been misidentified as {{Contextualizar}} (pt:Predefinição:Contextualizar), with Twinkle listing it under "Tags already present". I'm running the gadget in a webserver, so all I can give as reference is my repo. Any help would be immensely appreciated. BraunOBruno (talk) 14:20, 13 June 2024 (UTC)

Identification of existing tags is based on the box-{NAME} class that appears on the ambox element in the html, which on ptwiki appears to be controlled by ambox's |nome=. pt:Predefinição:Sem notas and pt:Predefinição:Corrigir both contain |nome=Contextualizar, which is the problem. – SD0001 (talk) 18:16, 13 June 2024 (UTC)

That's a sillier issue than I thought it would be. Thank you so very much, @SD0001! BraunOBruno (talk) 18:27, 13 June 2024 (UTC)

Hey, @SD0001, sorry to bother you, I'm a little in over my head here. The tagging seems to be working quite well, but when there is a (equivalent of) multiple issues tag and then I only leave one tag active (unchecking the others), Twinkle removes even the one that was supposed to stay ([4]), any clues on that? Again sorry and thank you. BraunOBruno (talk) 01:36, 14 June 2024 (UTC)

Not sure. Could potentially be due to a bug in twinkle-core. The intended behaviour is that the one tag should be removed as well as the multiple issues wrapper (assuming groupMinSize is 2), leaving the other tag. Try running the debugger if you're able to see the code which is causing the other tag to be removed. – SD0001 (talk) 17:21, 14 June 2024 (UTC)

PROD - Edit window colors

Hi, I am on Monobook skin, so there is a "Prod" tab that I click on to begin delete proposal. At Reason for proposed deletion the edit window appears as Black. When I type, it's also black, so I am typing blind. Question: any way to change colors? For regular Wikipedia edits, I have colors set like the old IBM green screen, i.e., black background with green text. Regards, JoeNMLC (talk) 18:06, 16 June 2024 (UTC)

Hey there. You appear to be using custom code at User:JoeNMLC/monobook.css. You might be the only person with this problem. It is likely you need to get someone technical to adjust your monobook.css code a bit. –Novem Linguae (talk) 18:19, 16 June 2024 (UTC)

Done - @Novem Linguae, I ran several tests & changed both bg and text colors for the Edit window.Cheers, JoeNMLC (talk) 01:49, 17 June 2024 (UTC)

Recent reverts

Anti-vandalism tools, such as Twinkle, Huggle, and rollback, should not be used to undo changes that are constructive and made in good faith.

@Meters, I agree with @AutisticAndrew and would support removal of the statement. Twinkle has a "revert good faith edits" feature on diff pages called "rollback (AGF)" that makes the above statement seem untrue to me. –Novem Linguae (talk) 19:51, 3 June 2024 (UTC)

It used to say unless a reasonable attempt is made to improve the content rather than revert it (when the contribution has value), and an appropriate edit summary is used but that was lost in the shuffle years back. Maybe just restore that part? Certainly, that's how I've always interpreted it. As I've already said in a similar discussion at WT:ROLLBACK, it makes no difference to the "victim" what tool is used to make a revert. Either the reverter 'splained themselves, or they didn't, and that's what matters. Suffusion of Yellow (talk) 20:12, 3 June 2024 (UTC)

I just feel that the page saying Anti-vandalism tools, such as Twinkle, Huggle, and rollback, should not be used to undo changes that are constructive and made in good faith., conflicts at least with Twinkle, Rollback for example is only for obvious vandalism as I'm fully aware, I just feel that with Twinkle having a revert (AGF) option that it causes conflict by saying Twinkle shouldn't be used for edits made in good faith as it has that option. - AutisticAndrew (talk) 21:18, 3 June 2024 (UTC)

The current wording is misleading, yes. But we don't want to encourage people to click "rollback (AGF)" and leave the summary blank, either. That's still 90% as BITEy as using one of the other buttons. Suffusion of Yellow (talk) 21:51, 3 June 2024 (UTC)

I agree. Any kind of undo/rollback with no edit summary, manual or with any tool, should be reserved for obvious vandalism; and if you use undo/rollback with an explanatory edit summary, it doesn't matter whether you are making the edit with a helper tool or script. -- John of Reading (talk) 06:36, 4 June 2024 (UTC)

Yes, the current state is a bit of a problem. I think the confusion arises with two different features of Twinkle; providing an easy Rollback/Undo option to any user (regardless of confirmed status) and providing canned warning templates. The 2021 diff above (listed by Suffusion of Yellow, edit by user:DKEdwards) separated the qualified "shouldn't be done unless" statement, into a definitive "shouldn't be done" statement, followed by qualifications in separate sentences. That wording still does a pretty good job of covering a difficult situation, and I don't think simply removing the definitive "don't" statement is the solution. AutisticAndrew thinks it is contradictory to have the statement "should not be used to undo changes that are constructive and made in good faith" when Twinkle has an AGF option, but there's an and in that statement that he seems to have missed, and where is this supposed "AGF" option in Twinkle? I'm not aware of any "AGF" option when using Twinkle to undo an edit, and I very frequently use Twinkle to leave that user page messages about edits I have undone that may well have been originally made in good faith, but that were still a problem: POV edits; attempting to link to external images; unsourced claims; promotional additions; etc. There isn't much other than blatant vandalism that isn't possibly a good faith edit.

And why do we mention Huggle and Rollback at all? This is an article about using Twinkle, not a general article about undoing or revertng edits. Meters (talk) 20:19, 4 June 2024 (UTC)

@Novem Linguae:Where does the Twinkle "rollback (AGF)" show up? I don't believe I have ever seen this. Could this be a Huggle prompt instead? Meters (talk) 20:26, 4 June 2024 (UTC)

Huggle is a Windows application so is unable to affect links in the browser. The HTML link class is named tw-rollback-link-agf, with tw- probably meaning Twinkle, so all evidence points to it being Twinkle. Maybe visit your Wikipedia:Twinkle/Preferences and make sure "Show rollback links on these pages" -> "Diff pages" is ticked and saved? –Novem Linguae (talk) 00:47, 5 June 2024 (UTC)

I'm kinda not sure why "constructive" is there. Why would anyone even want to revert an edit that's constructive? Alpha3031 (t • c) 12:56, 4 June 2024 (UTC)

This issue is too minor for all the talking this is generating. Let's just take a stab at fixing it. How's this? –Novem Linguae (talk) 00:53, 5 June 2024 (UTC)

Preferred wording (changes in bold): "Please take particular care with the rollback links provided by Twinkle. Only obvious vandalism qualifies for rollback without an edit summary. If you believe an editor's contribution was made in good faith, you should include an edit summary." DonIago (talk) 01:57, 5 June 2024 (UTC)

Feel free to edit my edit :) –Novem Linguae (talk) 02:59, 5 June 2024 (UTC)

I'm fine with either NL's or DI's version. Both are major improvements over the old language. Firefangledfeathers (talk / contribs) 03:04, 5 June 2024 (UTC)

I've gone ahead with my tweaks. Other editors are welcome to revert if they feel NL's version is preferable; I promise I won't get mad. :) DonIago (talk) 02:41, 6 June 2024 (UTC)

Resolved

–Novem Linguae (talk) 14:05, 17 June 2024 (UTC)

Creating new month section when unneeded

Theres a bug where if a talk page already has a warning section for the current, but the month isn't capitalized, twinkle will create a new month section if you use it to warn somebody (instead of just adding the new warning to the already existing month section). You can view this bug on my user talk page, where I tested it (check the june 2024 and June 2024 sections). Gaismagorm (talk) 13:03, 17 June 2024 (UTC)

Can you provide a diff or two of this bug in the wild? How often does a month warning heading get created that isn't capitalized? This is the first time I've ever heard of it. Anyway, I wonder if a different tool has a bug. –Novem Linguae (talk) 14:08, 17 June 2024 (UTC)

It's not common since most people remember to capitalize, but I could probably find an example, it will take a bit though Gaismagorm (talk) 14:11, 17 June 2024 (UTC)

User talk:71.34.135.166 theres an example of it occurring. There is two sections for September 2023 since I added a section and didn't capitalize september, then somebody else used twinkle to warn and it created a new section Gaismagorm (talk) 14:14, 17 June 2024 (UTC)

also It's not that it creates an uncapitalized month section, it's that it doesn't recognize an already existing section as existing if the existing section isn't capitalized, and it then creates a new one. Gaismagorm (talk) 14:16, 17 June 2024 (UTC)

It's not a bug, the names of months are capitalized even in the middle of a sentence in English. Twinkle has no obligation to account for misspelled section names. Nardog (talk) 14:17, 17 June 2024 (UTC)

ah ok, my bad. sorry bout that! Gaismagorm (talk) 14:18, 17 June 2024 (UTC)

remove template at top of Chicks on Speed page

could you remove the template at the top of the Chicks on Speed wikipedia page please - I am in the band and working on updating the page, adding citations and sources for improvement and accuracy, thanks! Alexmurrayleslie (talk) 10:26, 2 July 2024 (UTC)

while I understand your concerns, the issues are still in the article, so I don't believe removing the template is a good idea just yet. I'd also reccomend not editing the page if you are a member of the band as it would be a conflict of interest. I'd also reccomend bringing this over to the chicks on speed talk page. Gaismagorm (talk) 11:46, 2 July 2024 (UTC)

Blocking notification messages

Is there a way to block Xfd discussion notification messages from being added to a User talk page, such as this Cfd notice posted to the talk page of an indeffed user? These are creating extra work for other editors to remove. What about a category, something similar to this category which blocks mass-mailings, or maybe a {{bots}}-type template? Or any other way for a non-page owner to disable the notification (i.e., not their preferences, or common.js, etc.). Or maybe the script could just check and not post messages on pages of indeffed users, who can't respond to them anyway? Thanks, Mathglot (talk) 08:43, 8 July 2024 (UTC)

This is a frequent request. See Wikipedia talk:Twinkle/Archive 48#Notification opt-outs, Wikipedia talk:Twinkle/Archive 48#Feature suggestion for XfD nominations for example. I'm not sure how comfortable I'd be with reducing auto notifications. Notifying users when their pages are getting deleted is the norm I think, and makes sense to me. These are creating extra work for other editors to remove. Out of curiosity, what is the idea behind removing these? Aren't they harmless if left in place? And removing them likely double notifies since it is a 2nd diff. –Novem Linguae (talk) 09:20, 8 July 2024 (UTC)

Following the links, I like Amorymeltzer's suggestion at Archive 44 of creation of a {{no twinkle}} template with various options. Could something like that be implemented? Also pinging ProcrastinatingReader and SD0001 because of their comments at that thread. Mathglot (talk) 20:04, 8 July 2024 (UTC)

I'm still not sure why people are overly concerned with whether talk page messages are left. As mentioned in previous discussions, a {{no twinkle}} template probably wouldn't be used for deceased editors because people will want to potentially fix articles that have been nominated, and I'm still not sure why people are so bothered by leaving notices (of any type) on the talk page of indefinitely blocked users. Primefac (talk) 23:12, 9 July 2024 (UTC)

Users abusing this tool to add {{One source}} template to stub pages

There are users abusing this tool to add the {{One source}} template to a lot of various stub pages even though the template advises against doing this. Please add documentation to the tool so that users stop doing this. Ergzay (talk) 14:22, 7 June 2024 (UTC)

Similarly for the {{More citations needed}} template which people abuse using twinkle in the same way. Ergzay (talk) 14:32, 7 June 2024 (UTC)

If a user is abusing Twinkle, then that user should be dealt with at the usual locations (usually by talking to them first and then WP:ANI if that doesn't work). We shouldn't be gutting the tool unless everyone is misusing it. Primefac (talk) 19:41, 7 June 2024 (UTC)

@Primefac I didn't propose gutting it. I proposed documenting it. Ergzay (talk) 20:51, 8 June 2024 (UTC)

Isn't it already documented on the /doc pages for the various templates? Twinkle has a disclaimer that the end user is responsible for all edits they make; we do not need to give template-specific warnings in the Twinkle documentation. Users misusing warning or maintenance templates should be notified of such behaviours. Primefac (talk) 22:04, 8 June 2024 (UTC)

indeed 2600:1700:6EE:6890:2D59:1F74:BE97:D6A7 (talk) 17:58, 14 July 2024 (UTC)

Twinkle didn't write filename in FFD listing

See Special:Diff/1234934762, Twinkle didn't write the filename there for some reason. Jonteemil (talk) 22:13, 16 July 2024 (UTC)

Request: Widen name box in the XFD menu for CFD/S and CFD

Tracked in github.com
Issue #1984

I nominate a lot of pages for speedy renaming at WP:CFD/S, almost always using Twinkle to do so. A lot of what I do is fixing capitalizations or making adjustments based on the existing title, but it almost always features pasting to try to avoid making mistakes. When I paste a title into the "new name" box I'll often have to move left and right in the box to make the changes I want, which makes it easier for me to make mistakes or miss things. Given that the new name box takes up less than half of the width of the window, I'd like to ask that it be stretched out farther. An example that I'm just about to nominate is "Ministers of Water Management of the Netherlands", after pasting, gets cut off to show "r Management of the Netherlands". I know this doesn't seem like much, but it would be a HUGE QoL improvement for me. Hey man im josh (talk) 13:34, 25 July 2024 (UTC)

Dark mode feedback from mw:Reading/Web/Accessibility_for_reading/Reporting/wiki.riteme.site

Tracked in github.com
Issue #1979

Posting feedback we received about the new Vector 2022 dark mode: "Twinkle drop down menus unreadable in dark mode When using the Twinkle gadget for tasks such as warning vandals, I have observed that, with dark mode enabled, the text in drop down menus is nearly unreadable as the text colour has changed to white but the background colour of the dropdown has remained the same white colour. " 🐸 Jdlrobson (talk) 20:18, 18 July 2024 (UTC)

Thanks. I wrote a patch to fix the warn module just now. (Not deployed yet.) I may work on other modules as time permits. –Novem Linguae (talk) 01:16, 19 July 2024 (UTC)

Deployed. –Novem Linguae (talk) 00:37, 26 July 2024 (UTC)

Is it not possible to start a requested move with Twinkle?

That is one of the most basic feature not integrated into the tool. Neocorelight (Talk) 03:13, 27 July 2024 (UTC)

It's in TW -> XFD. –Novem Linguae (talk) 04:20, 27 July 2024 (UTC)

Oh, it's hidden there. I didn't think of that. Neocorelight (Talk) 04:28, 27 July 2024 (UTC)

Revision history at top of page no longer updates

I've tried purging the page, deleting my temporary files on my computer, disabling/enabling Twinkle again, does nothing to refresh the revision counter. This has been going on for me since last night. I figured restarting my computer today would fix it but that also did not help. Salmoonlight (talk) 18:56, 4 August 2024 (UTC)

Can you provide a url to an example page? What should I look for to see the bug? –Novem Linguae (talk) 19:42, 4 August 2024 (UTC)

It's for every page. Salmoonlight (talk) 19:43, 4 August 2024 (UTC)

I cant recall ever seeing "Twinkle revision history at top of every page". Can you please provide more details? –Novem Linguae (talk) 19:52, 4 August 2024 (UTC)

Uploaded a screenshot, I'm sorry if this isn't actually a feature of Twinkle and it's actually from some other tool. https://commons.wikimedia.org/wiki/File:Twinkle_stats.png Salmoonlight (talk) 19:57, 4 August 2024 (UTC)

Thanks for the screenshot. Thats the xtools gadget. Is it ticked in Special:Preferences -> gadgets -> xtools? –Novem Linguae (talk) 20:42, 4 August 2024 (UTC)

Adding Redirect Cat Causes Double Redirect

Where do I report an error in trying to add a redirect category to an existing redirect using the Tag button?

I tried to add the {{R with possibilities}} tag to a redirect, and it created a second empty redirect shell. The original redirect had been Special:Permalink/1210632744. When I tried to add the additional category, using the Tag button, it applied this diff: Special:Diff/1237443069. As can be seen, it moved the existing redirects into a new shell, leaving an empty shell. Robert McClenon (talk) 00:30, 30 July 2024 (UTC)

When you say "double redirect", are you referring to the issue described at WP:2R? I haven't heard the phrase used in any other sense before. jlwoodwa (talk) 22:03, 1 August 2024 (UTC)

Those links don't work. Nardog (talk) 01:49, 8 August 2024 (UTC)

Dark mode compatibilty

Tracked in github.com
Issue #1979

I used the AFD functionality of Twinkle today, and with dark mode enabled I was barely able to use the form because of some light-grey-on-white text. There are some official recommendations for fixes at mw:Recommendations for night mode compatibility on Wikimedia wikis. Usually I find either picking mode-sensitive colors from the official palette or using class="skin-invert" does the job. -- Beland (talk) 06:29, 9 August 2024 (UTC)

I converted the warn module a week or two ago. Myself or someone else needs to convert all the other modules now. –Novem Linguae (talk) 07:27, 9 August 2024 (UTC)

Template:Uw-blank1

My Twinkle doesn't have these template, I have not seen any Twinkle users using this template as well, so does Twinkle use this template or not? The notice starting with If you plan to make breaking changes to this template... exists on uw-blank1 and uw-blank2, should it be removed? Myrealnamm (💬pros · ✏️cons) 14:55, 12 August 2024 (UTC)

A potential tweak if within our rules

Tracked in github.com
Issue #1988

When an editor is indeffed and can take no action, Twinkle still notifies them of AfD, CSD, etc. That seems a difficult thing to receive, and is probably pointless. If it is within our rules, please can Twinkle at least have an option not to post the user advisory message when the editor it would notify is indeffed? 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 07:51, 9 August 2024 (UTC)

This has come up a couple times this year, with me and Primefac often opposing, and others supporting, but too low participation to get a good consensus. Might be time to RFC it to get more participation. Taking away an editor's right to be notified of their articles getting deleted feels like a big deal to me so I am hesitant to change the status quo without a consensus. –Novem Linguae (talk) 08:11, 9 August 2024 (UTC)

At the very least it seems it should be rate limited. It feels not great to see a blocked user suddenly get 20 notifications of article deletions, it looks very much like rubbing salt in a wound. CMD (talk) 09:44, 9 August 2024 (UTC)

Just noting that one can turn off the "notify page creator" box when nominating a page (though if the page is PRODded a bot will notify them anyway). Primefac (talk) 10:36, 9 August 2024 (UTC)

@Primefac And I never noticed it previously. Thank you.

A tweak that would be unlikely to need consensus might be a message "The editor who will be notified is blocked indefinitely and can take no action, are you sure you wish to notify them? If not please choose This option ->>>>" to highlight the option. I doubt I am alone in failing to spot it. 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 11:30, 9 August 2024 (UTC)

"User is blocked" would fit better in the space given. Primefac (talk) 12:13, 9 August 2024 (UTC)

I'm not wedded to any particular words 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 14:26, 9 August 2024 (UTC)

@Novem Linguae I agree that such a change would require consensus were it to change the default state. 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 11:27, 9 August 2024 (UTC)

For what it's worth, I also oppose this. Indeffed users get unblocked sometimes and there's no harm in the user getting talk page notifications about it. Hey man im josh (talk) 12:54, 9 August 2024 (UTC)

I somewhat agree to this, for example, some LTAs in proxies that I have been dealing with don't really need those long warnings as they will never read them. However, it does concern me that some users will not use this function appropriately.

I did notice the Speedy template says ": Please consider placing the template: XXXX on the talk page of the author.", in which Twinkle already does. Myrealnamm (💬pros · ✏️cons) 14:53, 12 August 2024 (UTC)

Maybe just letting the twinkle user know someone is blocked could be a good compromise. https://github.com/wikimedia-gadgets/twinkle/issues/1988 –Novem Linguae (talk) 15:46, 12 August 2024 (UTC)

Ok, I see your point. Myrealnamm (💬pros · ✏️cons) 15:49, 12 August 2024 (UTC)

I'd just like to comment that this doesn't always work. I've unchecked it before in cases involving SPAs and obvious public relations article creators, but resulted in a bot intervening and leaving an automated notification on the creator's talk. Courtesy ping to @Timtrent:. Graywalls (talk) 18:14, 12 August 2024 (UTC)

Wikipedia:List of policies should be in Twinkle welcome messages

This is a very useful summary of our policies. I've seen at least one case today where an editor could have avoided problems if whatever welcome they had linked to this. Doug Weller talk 10:53, 14 August 2024 (UTC)

I think this might be something to discuss on the welcome templates talk pages (or a central WikiProject if there is one); Twinkle just places the notifications, it doesn't control or maintain them. Primefac (talk) 10:58, 14 August 2024 (UTC)

I agree 100% (I come from here). JacktheBrown (talk) 11:43, 14 August 2024 (UTC)

CTOP notifications

Tracked in github.com
Issue #1806

Are these not available in Twinkle or are they buried somewhere? Kcmastrpc (talk) 17:54, 17 August 2024 (UTC)

It's not native to Twinkle. But User:TheresNoTime/Scripts/CT-Helper.js is a good workaround. –Novem Linguae (talk) 18:42, 17 August 2024 (UTC)

Uw-AI

Tracked in github.com
Issue #1901

Should you include the AI user warning templates? Ahri Boy (talk) 07:21, 20 August 2024 (UTC)

Sure. We've got a ticket and a patch for that, so it's in progress. In the meantime you can go into Twinkle's preferences and add those warning templates to your custom warning templates. –Novem Linguae (talk) 10:04, 20 August 2024 (UTC)

Thanks. Some warning templates haven't been added into the software. I might mention later. Ahri Boy (talk) 00:22, 21 August 2024 (UTC)

Fringe theories

Tracked in github.com
Issue #1996

Please can you add {{Fringe theories}} to the standard installation for maintenance tags

thanks,

Daisytheduck ^{quack quack} 01:18, 27 August 2024 (UTC)

"One source|Section" tag moved to multiple issues box at top

Tracked in github.com
Issue #1997

When adding a "globalize" tag, I had the "use multiple issues box" checked. To my surprise, some section tags were moved to the top[5]. This seems to be unwanted behaviour. Fram (talk) 12:24, 29 August 2024 (UTC)

CSD C4

Tracked in github.com
Issue #1994

Just noting that our language needs to be changed in the CSD reasons, the text for G8: Categories populated by a deleted or retargeted template needs to be updated to the new WP:C4 language (see e.g. Category:Singapore political party logo templates, which I deleted under the old G8 not remembering that it had been changed to C4). Primefac (talk) 10:16, 30 August 2024 (UTC)

Addition to CSD criteria list

Hello, Twinkle folks,

Could you add "C4. Unused maintenance categories" to your list of CSD criteria (see Wikipedia:Criteria for speedy deletion#C4. Unused maintenance categories)? I've been using "CSD G6 Housekeeping" as a deletion criteria for expired maintenance categories because I didn't see C4 on your list of options and I think this criteria would be more appropriate. Thank you. Liz ^{Read! Talk!} 20:31, 2 September 2024 (UTC)

Merged into previous section, same request. Primefac (talk) 00:16, 4 September 2024 (UTC)

Template:Advert has been nominated for merging with Template:Promotional tone. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:05, 4 September 2024 (UTC)

Creator notification with WP:BLPPROD

Just curious if anyone can direct to me to why the option to not notify a page creator is deactivated when applying a BLPPROD? I'm guessing it is because these are usually very new articles but I just ran across one where the creator is long-term inactive. Just Step Sideways ^{from this world ..... today} 22:44, 4 September 2024 (UTC)

I followed the history of the line containing "has to be notified" in GitHub, and it goes back 14 years to the "initial import from Wikipedia". So it has been this way for at least 14 years. So the "why" is probably lost to history.

Isn't BLPPROD intended to motivate the author to add sources within 1 week to avoid deletion? If I had to guess, that is probably the reason. Kind of hard to motivate the author of an article to act if they are not notified.

This is also related to the discussion of how much to notify blocked users, which has been discussed on this talk page a couple times this year. –Novem Linguae (talk) 23:21, 4 September 2024 (UTC)

Error when navigating away from page very quickly after page load

Tracked in github.com
Issue #1998

I've been noticing this issue for a while now but figured there was no way to fix it, until very recently when I managed to fix it in a script of mine. If you click a link to another page immediately after the page loads, there will often be an error message "Could not load your Twinkle preferences, resorting to default preferences". It seems like the browser (Firefox at least – haven't tested across browsers) makes all pending network requests fail as soon as navigation to a new page starts, but before JS execution stops, so the error handler still has a chance to run and display the message even though there was never actually an error.

The way I (mostly) fixed this was to add a beforeunload listener which sets a flag, and test that flag before displaying the error message. There are a few scenarios where this won't work, because a couple browsers (iOS Safari appearing to be the biggest example) don't fire the event, and it is possible for other scripts to cancel the page unload in their own beforeunload listeners. I figured not firing the event was not an issue (the error will just still show up, which is not a change), and that the chance of both having another script installed listening for beforeunload, and having the user both navigate away and also cancel that navigation in the VERY short time between the request being sent and completed is so low as to be negligible, especially for something as relatively trivial as displaying an error message. Tollens (talk) 21:22, 4 September 2024 (UTC)

I've noticed this nuisance message too. Perhaps the best way to handle it would be to convert it to a console.log() instead. Even if this message is legit, for example a person's Twinkle preferences page became corrupted, it is hard to imagine that the user would want a mw.notify() about this displayed every time they visit a page. –Novem Linguae (talk) 22:45, 4 September 2024 (UTC)

I had figured it was a useful message if it was actually supposed to show up – not sure, though. Reading the code, I don't think someone's preferences being corrupted would cause this particular error to fire (the "Could not load" one), since it should only happen if the network request doesn't complete normally. It would be very surprising, though, for someone to be able to load the Wikipedia page they are viewing but not their Twinkle preferences page, thinking about it further. Maybe changing only the "Could not load" error to a console.log (or .error, probably) and leaving the "Could not parse" error as mw.notify would make sense? Personally I would want to be harassed by an error message if I had screwed up my config file, but I might be an exception. Tollens (talk) 23:04, 4 September 2024 (UTC)

Sure, that's fine. I've updated the ticket to just change the load message to console.log() and not the parse message. –Novem Linguae (talk) 00:15, 5 September 2024 (UTC)

Notability category: organizations

Tracked in github.com
Issue #1999

If you tag an article with {{notability}}, Twinkle lets you select a subcategory, like {{notability|companies}}, which puts the article in Category:Company articles with topics of unclear notability. However, the dropdown menu is missing {{notability|organizations}}, which would populate Category:Organization articles with topics of unclear notability. I didn't notice this for a while, since WP:NCORP and WP:NORG are the same notability guideline, but it means a bunch of non-company organizations have ended up in Category:Company articles with topics of unclear notability. jlwoodwa (talk) 22:37, 4 September 2024 (UTC)

The dropdown already has {{notability|Companies}} which displays the same template and has a description of "notability guideline for companies and organizations". However it wouldn't hurt to add it if it helps people find the correct entry. Ticket created. –Novem Linguae (talk) 22:57, 4 September 2024 (UTC)

It's not just to help people find the correct entry. The issue is that {{notability|companies}} and {{notability|organizations}} aren't just synonyms – they place the article in different categories. jlwoodwa (talk) 23:15, 4 September 2024 (UTC)

I guess the template that is visible to the user is the same because WP:NCORP combines the two. But anyway, sounds good. I've updated the ticket. –Novem Linguae (talk) 00:16, 5 September 2024 (UTC)

db-commons should be dated

Tracked in github.com
Issue #2011

When deleting a file under WP:F8 using Twinkle's dated speedy deletion module, {{db-commons}} is placed on the description page. This is a redirect to {{Now Commons}}, which ideally should be given a date as parameter. (Note that {{Now Commons}} can also be placed directly on a file's description page using Twinkle's file maintenance tagging module, which does pass the date as a parameter.) jlwoodwa (talk) 01:04, 6 September 2024 (UTC)

@Jlwoodwa. Can you please provide an example diff of a correct Db-commons or Now Commons containing the date parameter, so I know how to format it? What date should it take, the date tagged or something else? –Novem Linguae (talk) 22:25, 6 September 2024 (UTC)

Sure, here's one I just did. Any reasonable date format should work, though, since it uses the #time parser function. Template:Now Commons/doc § Detailed gives 2010-07-01 and 20100601023255 as two examples. As for which date to use: yes, it's the date when the file was tagged with this template (Template:Now Commons/doc § TemplateData). jlwoodwa (talk) 22:40, 6 September 2024 (UTC)

Query

Tracked in github.com
Issue #1382

Hello, Twinklers,

I'm hoping Twinkle experts like Novem Linguae can answer this question (and a comment). I see an admin somehow mass-tag pages with CSD notices. Except for Batch Delete/Undelete, I thought Twinkle only worked on one article/User notification at a time. What is this feature that would allow me to tag multiple pages and, at the same time, send out multiple notifications? I've been using Twinkle almost as long as I have been editing but this is news to me.

My comment is one I have raised here several times over the years. While, when I delete a page, Twinkle will delete the Article, the Article talk page, any Redirects but NOT Redirect talk pages. I have to run a special Quarry query to find orphaned talk pages that weren't deleted by Twinkle. This seems like an easy feature to add and, if it was a concern, exempt User talk pages from this operation. But I assume that I'm not the only admin who has brought this up here so you must have some explanation for why Twinkle doesn't do this. Thanks for any answers you can supply. Liz ^{Read! Talk!} 02:37, 20 September 2024 (UTC)

As far as I am aware, you cannot mass-tag articles. You can certainly mass-delete using d-batch, but tagging pages needs to be done on a per-page basis. Since Twinkle is semi-automated, it would be fairly easy to pull up a large list of pages and then tag them sequentially per-page.

As a minor note, you don't need to do a Quarry search to find what links to a page, just use Special:WhatLinksHere. I do agree though that catching the talk page redirects would be useful. Primefac (talk) 10:35, 20 September 2024 (UTC)

I see an admin somehow mass-tag pages with CSD notices. Post a diff and I can take a look at how they did this.

While, when I delete a page, Twinkle will delete the Article, the Article talk page, any Redirects but NOT Redirect talk pages. Yeap, this has had a ticket since 2021. Ticket. I even wrote a patch for this once for batchdelete, but batchdelete is a lot of work to test, so I gave up on it. Maybe one day when I have more time I'll take another stab at it. No time this month though. –Novem Linguae (talk) 18:05, 20 September 2024 (UTC)

Okay, Novem Linguae, look at this page, the CSD C1 taggings for September 19th, September 14th or September 8th. All of them happened at the same minute, it's 7:57 am on my clock for the 19th. I've seen this before but it was seeing this yesterday that prompted my post. Maybe it's just fast fingers from a speedy editor!

As for the Redirect talk pages, it helps to know that, at least, there exists a ticket out there, it's just a low priority. But I'll now stop bringing it up here over and over again. That's something! Liz ^{Read! Talk!} 02:54, 21 September 2024 (UTC)

Those diffs do have the Twinkle tag so they are from Twinkle. Maybe Explicit can answer the question of how he tagged 7 CSD C1's in 1 minute. (We're not saying that's too fast. I think Liz is just curious if there's a mass CSD C1 tag feture in Twinkle.) –Novem Linguae (talk) 03:34, 21 September 2024 (UTC)

We'll see if he responds. I'm their least favorite person on the project. Liz ^{Read! Talk!} 03:42, 21 September 2024 (UTC)

Ah, I didn't know about that. Whoops :) –Novem Linguae (talk) 04:53, 21 September 2024 (UTC)

Doing 7 in a minute is fairly easy to do with a task like this if you open up multiple tabs, maybe triage them, then go back and process with twinkle. Assuming they were just processing Category:Candidates for speedy deletion as empty categories I think they could have done it comfortably without pre-loading all in tabs first. Also I can't see how you could bulk tag as surely you should look at each and check it's valid, even if that check only take 2 seconds. KylieTastic (talk) 09:00, 21 September 2024 (UTC)

Warning typo

Tracked in github.com
Issue #2015

{{uw-longsd}} is missing the "g" in twinklewarn.js (see [6]. Can someone file a pull request? Thanks. C F A 💬 00:16, 23 September 2024 (UTC)

Default behaviour of CSD logging

It took me some fiddling around, looking at other people's CSD logs to figure out that they're not manually added, but typically via Twinkle. That said, CSD logging is disabled by default in Wikipedia:Twinkle/Preferences § Speedy.

It wasn't clear to me if I needed to create User:Shushugah/CSD log manually or if it would be created automatically once setting is enabled. If automatic, are there any defaults, e.g archiving set up? Is there a good reason not to make this a default setting with automatic creation the first time an editor nominates article for speedy deletion? ~ 🦝 Shushugah (he/him • talk) 13:31, 18 September 2024 (UTC)

I would support opt-out rather than the current opt-in for CSD/PROD logging. Primefac (talk) 18:35, 18 September 2024 (UTC)

I concur, default on with opt-out makes more sense to me. KylieTastic (talk) 12:16, 19 September 2024 (UTC)

This is easy to code, but could get some pushback once deployed. Hopefully some more talk page watchers can chime in with their thoughts before we commit to doing this. –Novem Linguae (talk) 21:15, 19 September 2024 (UTC)

We've discussed this before: /Archive 47#csd/prod/xfd: turn on userspace logging by default. Nardog (talk) 21:26, 19 September 2024 (UTC)

I read the older discussion, but I am not persuaded by the reasonable expectation of privacy. Any edits created on Wikipedia is irrevocably released and typically searchable by any other editors. In the current implementation, if a CSD tag is declined, that would be permanently visible in edit history of that page as well as a user's edit. If someone is so concerned about privacy, that their declined CSD tags become visible they should not engage in CSD tagging to begin with. All that said, they still would be able to turn off the logs setting and request WP:U1 deletion. ~ 🦝 Shushugah (he/him • talk) 10:23, 20 September 2024 (UTC)

I don't do CSDs or PRODs very often, so not really affected; i do remember trying to work out why they weren't being recorded automatically many years ago, as Shushugah seems to be referring to. Seems to me that opt-out would be more sensible for both these logs. Happy days, ~ Lindsay^Hello 13:20, 1 October 2024 (UTC)

Per Nardog this is not really a setting intended to be default-on. I think we should instead make the option more discoverable, such as by placing a footer link "Enable CSD logging" leading straight to the option on the pref page, for users who don't already have it enabled. – SD0001 (talk) 00:46, 2 October 2024 (UTC)

Requesting addition of new welcome template

Tracked in github.com
Issue #2020

Hey folks! I'd like to request the addition of Template:Welcome draft to Twinkle's welcome menu. There has been a lot of interest from AfC reviewers for a welcome message tailored toward new users who have already started building drafts. The welcome template was adapted from a custom message I've been using, with refinements provided by other reviewers at Wikipedia talk:WikiProject Articles for creation#AfC-tailored Welcome template. The template supports a parameter for a linked article. Please let me know if there are any questions. Thanks! ~Liance^talk 16:23, 2 October 2024 (UTC)

Missing line break when protecting AFD page

Tracked in github.com
Issue #1870

Reported by @Star Mississippi at User talk:Star Mississippi#Quack!.

There should be a line break at the end of line 1 in this diff.

Posting here to remind myself to investigate more before deciding to make a GitHub ticket. Maybe it's as simple as ticking a box or something. –Novem Linguae (talk) 15:44, 7 October 2024 (UTC)

CSD criteria for categories and another small issue

Tracked in github.com
Issue #1994
Resolved

The CSD criteria for categories should be changed to include the new criteria C4, instead of just showing C1 and two other general criteria. Would help a ton when doing technical CSDs for categories. (I know you can add your own stuff but it always doesn't work for me.) The criteria is also brand new so I don't blame you for not seeing it. I also had a bit of an issue when I was opening up a CFD using Twinkle, it had subst: it but it only pasted in the whole template and not the actual subst: here is the diff but was fixed by Pppery in the next edit. Cowboygilbert - (talk) ♥ 02:01, 16 October 2024 (UTC)

We have a ticket and a patch to add C4 already. Will see if I can expedite it.

Looks like the bad diff was caused by malformed wikicode syntax provided by the user. Changing [[[[ to [[ fixes the subst. Probably no need to fix this on the Twinkle side. –Novem Linguae (talk) 07:38, 16 October 2024 (UTC)

I approved the CSD C4 patch and did a deploy just now. Should be all set. –Novem Linguae (talk) 09:44, 16 October 2024 (UTC)

Question About What Warning to Issue

In an XFD discussion, I entered a Keep !vote, and the nominator struck out the bolded Keep with an explanation. My question is what Twinkle warning can or should I issue. I gave a Level 3 warning for Disruptive Editing, but I would have preferred to give something more specific. Robert McClenon (talk) 18:50, 19 September 2024 (UTC)

More generally, if I would like to propose that a new Twinkle warning be added, is this the place to make the suggestion, or should I make it somewhere else? Robert McClenon (talk) 18:50, 19 September 2024 (UTC)

Twinkle only exposes some of the standard warnings available - see Wikipedia:Template index/User talk namespace for more. Not sure if any more precise warning exists, but I think "Disruptive Editing" is very accurate if they remove an opposing !vote without a clear and valid reason. KylieTastic (talk) 18:54, 19 September 2024 (UTC)

I'd use one of the Uw-tvp* templates. "Refactoring other's talk page comments". Example: {{Uw-tpv3}}. I found it by going to TW -> Warn, then clicking on the dropdown box with all the user warnings. There's a spot to search. I typed "talk", and if that didn't work, I was going to try searching for "tpo". –Novem Linguae (talk) 21:17, 19 September 2024 (UTC)

I saw "Refactoring other's talk page comments" and didn't know if striking the Keep was refactoring. Maybe I will use it next time, but maybe there won't be a next time, because I think that this is the first time I have seen that behavior, and it should be the last time.

They didn't remove an opposing !vote. They struck it. The principle is the same.

The editor deleted my warning, so they saw it and have been warned. Thank you. Robert McClenon (talk) 17:50, 20 September 2024 (UTC)

Closing without action –Novem Linguae (talk) 12:12, 16 October 2024 (UTC)

Where is warn entry?

I don't see the "warn" entry, how to fix? Susbush (talk) 17:43, 23 September 2024 (UTC)

@Susbush. Are you on a user or user talk page? Do you see the TW menu? When you click that open do you see the "Warn" link? –Novem Linguae (talk) 23:27, 23 September 2024 (UTC)

I see the TW menu, but not the "Warn" link. Susbush (talk) 01:20, 24 September 2024 (UTC)

What URL are you at when you're looking at the TW menu? Warn will only show up if you're on a user page or user talk page, and if that page isn't your own. –Novem Linguae (talk) 03:09, 24 September 2024 (UTC)

Oh, so that's why it wasn't showing up. Susbush (talk) 11:30, 24 September 2024 (UTC)

Closing without action –Novem Linguae (talk) 12:12, 16 October 2024 (UTC)

XFDCloser issue?

There's some potential cross-script issues between this and WP:XFDC, if any of the technically-minded back-end programmers could check out this conversation at XFDC's talk page, we would much appreciate it. Primefac (talk) 12:03, 26 September 2024 (UTC)

Replied there. Bug is not caused by Twinkle. – SD0001 (talk) 18:14, 26 September 2024 (UTC)

Closing without action –Novem Linguae (talk) 12:13, 16 October 2024 (UTC)

Warning about citing Wikipedia

Am I right in thinking that Twinkle does not have a warning template for people who cite Wikipedia? If so, could one be added? Does such a template already exist? I have been unable to find one. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:47, 28 September 2024 (UTC)

I've been using Template:Uw-circular. Hope this helps! DonIago (talk) 15:04, 28 September 2024 (UTC)

Thank you. That is for when a user "cited the information you added to another Wikipedia article or an external wiki." - a small subset of the cases I describe. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:23, 28 September 2024 (UTC)

You might have better luck at Wikipedia:Template index/User talk namespace; Twinkle doesn't host (or create) warning templates, it just provides an easier way to post them. Primefac (talk) 13:27, 29 September 2024 (UTC)

I may be being a bit thick here, but I guess I'm not seeing the distinction? Are you talking about citing Wikipedia outside the scope of Wikipedia itself? DonIago (talk) 15:17, 29 September 2024 (UTC)

No, the confusion is mine; I misread the template. Apologies. I have changed the wording slightly to make it clearer. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:57, 29 September 2024 (UTC)

Closing without action –Novem Linguae (talk) 12:13, 16 October 2024 (UTC)

Request: Last protection duration in dialogue box?

Tracked in github.com
Issue #2021

Is it possible, when bringing up the dialogue box to protect a page, to show the duration of the last protection? Like how when you're blocking someone, it shows how long the last block was for. ... discospinster _talk 19:52, 28 September 2024 (UTC)

@Discospinster. When I went to test this, it shows this already. For example, go to WP:ANI, then do TW -> PP. Under Tagging options, I see the red text Current protection level: Move: sysop (indefinite) by ScottishFinnishRadish. Previous protections: protection log • pending changes log (expired 2019-02-24). Got any pages where this isn't showing up that you'd like me to look into? –Novem Linguae (talk) 12:17, 16 October 2024 (UTC)

I'm thinking of articles that are not currently edit protected but have been in the past - for how long was the immediately previous protection? For example Ni Hao, Kai Lan shows that it's currently move protected, but I'm interested in the length of the last edit protection (in this case it was one year but in the Twinkle dialogue box I have to click on "protection log" to see that). ... discospinster _talk 17:31, 16 October 2024 (UTC)

Request: Inline parenthetical referencing

Tracked in github.com
Issue #2022
Resolved

It would be nice if {{Inline parenthetical referencing}} were added. Snowman304|talk 01:14, 6 October 2024 (UTC)

@Snowman304. Are you aware of any other inline templates that Twinkle places? I don't think there are any. I don't think Twinkle has the ability to place anything inline, which would probably require the visual editor. –Novem Linguae (talk) 12:19, 16 October 2024 (UTC)

@Novem Linguae: Template:Inline parenthetical referencing is confusingly named. It's about parenthetical referencing that's inline, not an inline template for parenthetical referencing. It produces the same sort of box that, say, Template:Cleanup lang would. Snowman304|talk 00:10, 17 October 2024 (UTC)

Ah, got it. I've gone ahead and renamed the template to {{Parenthetical referencing}}, since "inline" and "section" both have very specific meaning in maintenance tag template names, and that is not what is going on here. –Novem Linguae (talk) 08:09, 17 October 2024 (UTC)

Wikipedia:Close paraphrasing note in warnings

There is only one level for this, which might be a bit strong for new editors Wikipedia takes copyright violations very seriously and persistent violators will be blocked from editing. Can we get a lighter level, similar to how there are multiple levels for vandalism? Bogazicili (talk) 14:57, 19 October 2024 (UTC)

This isn't really a Twinkle issue because it involves the creation of new user warning (Uw) templates. Wikipedia talk:Template index/User talk namespace might be a better place to suggest this. –Novem Linguae (talk) 19:41, 19 October 2024 (UTC)

Closing without action –Novem Linguae (talk) 05:42, 23 October 2024 (UTC)

Vandalism/Promotion Only Account greyed out

Why is vandalism-only account and promotion-only account greyed out in the ARV menu? TheWikipede^talk 15:47, 12 November 2024 (UTC)

Are you looking at an IP? NightWolf1223 <Howl at me•My hunts> 16:05, 12 November 2024 (UTC)

Yeah TheWikipede^talk 17:45, 12 November 2024 (UTC)

Likely because IPs are editors but are not accounts. Primefac (talk) 20:11, 12 November 2024 (UTC)

Closing without action –Novem Linguae (talk) 22:20, 24 November 2024 (UTC)

Noticeboard notifications are marked as minor edits

Tracked in github.com
Issue #2032
Resolved

When a user is given a noticeboard notification through the Talkback feature (I don't know about the other three), it somehow gets marked as minor (diff). This causes the user to not receive the notification associated with the edit (I know, because ClueBot marks my talk page archivings as minor and I don't get new message alerts on them). Since the point of these notifications is to make sure they are aware of the discussion (especially since ANI requires the user to be notified), these should not be marked as minor. ミラP@Miraclepine 02:17, 23 October 2024 (UTC)

Users will get a notification alright even if the edit is marked as minor. ClueBot doesn't trigger notifications because its edits are additionally marked as bot edits. – SD0001 (talk) 05:29, 23 October 2024 (UTC)

No, minor edits on your user talk don't trigger alerts. Nardog (talk) 07:56, 23 October 2024 (UTC)

From testing it on testwiki, looks like you're right. Is this some recent change? I've always remembered it working that way, and it's what the code says as well – minor edits should suppress notifications only if the editor has nominornewtalk right, which per Special:ListGroupRights is only available to bots. – SD0001 (talk) 11:54, 25 October 2024 (UTC)

It's worked that way for as far back as I can remember. Here's me telling an editor to mark their c/e edits on my talk page as minor in February 2019. Nardog (talk) 05:16, 26 October 2024 (UTC)

Duplicate sockpuppet reports

Warning templates

U5 wording

Merging help/project pages

Typo on the Welcome template menu

Additional option for CfD

Adding a template

Discussion at Wikipedia:Village Pump (proposals) § Bump XfD heading sizes

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

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

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

Errant notifying IP addresses

Changes to Template:Db-draft-deleted

Removal of rcat tagging menu for category redirects

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

Notification opt-outs

Suggestion: Add "suboptimal" Welcome templates

Template:Translation request

Cerveza Cristal

Heiligenhoven Castle

Template:Dual fluency request

Twinkle placement of RFDs when header gets messed up.

COI template

Contentious topic alerts

Add Template:Welcome-anon-unsourced

Language problems

Confused

{{Uw-copyright-new}} body text revision and improvements

question about notifications

For file maintenance - add these two templates

Custom topic title

Changes to Template:Db-notice-multiple

Uw-ai1 set

Add Template:Uw-talkinarticle Series

Patch to change the linter to eslint-config-wikimedia

Talk Page with AIV Issue

Update on TwinkleMobile

Toc styles for config page

Template:Db-x3

Existing tags showing up twice

CSD speedy deletion tool notification bug?

Unlink and disambiguation pages

Tags for user-generated and BLP reference issues

Uw-multiple-accts

Feature suggestion for XfD nominations

Allow adding deletion sorting categories to all XFD venues

Custom tags can't be put in multiple issues

"Twinkle Rollback" includes error with articles with "Map" feature

Feedback: add reported users to watchlist

Formatting issue when protecting AfDs

Rollback AGF's description

TW doesn't leave Template:Shared IP Advice if warned in Contribution page

TwinkleStarter/enwiki's tag module misidentifying ptwiki tags

PROD - Edit window colors

Recent reverts

Creating new month section when unneeded

remove template at top of Chicks on Speed page

Blocking notification messages

Users abusing this tool to add {{One source}} template to stub pages

Twinkle didn't write filename in FFD listing

Request: Widen name box in the XFD menu for CFD/S and CFD

Dark mode feedback from mw:Reading/Web/Accessibility_for_reading/Reporting/wiki.riteme.site

Is it not possible to start a requested move with Twinkle?

Revision history at top of page no longer updates

Adding Redirect Cat Causes Double Redirect

Dark mode compatibilty

Template:Uw-blank1

A potential tweak if within our rules

Wikipedia:List of policies should be in Twinkle welcome messages

CTOP notifications

Uw-AI

Fringe theories

"One source|Section" tag moved to multiple issues box at top

CSD C4

Addition to CSD criteria list

Nomination for merger of Template:Advert

Creator notification with WP:BLPPROD

Error when navigating away from page very quickly after page load

Notability category: organizations

db-commons should be dated