Noticeboard notifications are marked as minor edits

edit

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

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)Reply
No, minor edits on your user talk don't trigger alerts. Nardog (talk) 07:56, 23 October 2024 (UTC)Reply
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)Reply
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)Reply

Adding article functionality to Template:Welcome cookie

edit

Hello,

Would it be possible to add article naming functionality to Template:Welcome Cookie in the same way as Template:Welcome? This way, the template would say something to the effect of "I noticed your edits on <x article> and wanted to welcome you! Etc. Let me know if this has already been discussed!

Thanks!

JuxtaposedJacob (talk) | :) | he/him | 09:34, 28 October 2024 (UTC)Reply

Thanks for the idea. This page is mainly for changing the Twinkle gadget. Requests for coders to edit/improve templates might be a better fit for WP:RT or WP:VPT. Hope that helps. –Novem Linguae (talk) 09:50, 28 October 2024 (UTC)Reply
Thank you @Novem Linguae, will follow up there.
Have a great day!
JuxtaposedJacob (talk) | :) | he/him | 06:47, 31 October 2024 (UTC)Reply
  Closing without actionNovem Linguae (talk) 20:40, 31 October 2024 (UTC)Reply

Wikipedia Dark Mode

edit

Could we add support for the new wikipedia dark mode? TheWikipede (talk) 13:16, 31 October 2024 (UTC)Reply

Adding other Welcomeen templates to the default configuration

edit

Hey. As someone who frequently welcomes new users, I sometimes have the occasion to use the many welcomeen templates, which basically says "Hi! Unfortunately, you're not fluent in English. Please edit another language Wikipedia. Thank you." I have had to add several welcomeen templates, and I propose that all be added to the default configuration. Please note that I've used all of them at least once.

Now, I'm vaguely aware that other welcomeen templates exist. On principle, I'm not opposed to having all of them added to the default configuration of Twinkle. I'm just trying to prevent inertia by suggesting only the ones I've had occasion to use. I dream of horses (Hoofprints) (Neigh at me) 22:21, 2 November 2024 (UTC)Reply

CFD/S merging

edit

In Special:Diff/1255067356, I expected it to put a merge tag ({{subst:cfm-speedy}}), but it put a rename tag instead. jlwoodwa (talk) 23:55, 2 November 2024 (UTC)Reply

Misclick? Has it happened anywhere else? Primefac (talk) 12:34, 3 November 2024 (UTC)Reply
I don't see how it could have been a misclick – there's no "rename vs merge" option to incorrectly select, and it did go through as C2F (as shown in Special:Diff/1255067358). I think the issue is that the speedy category criteria are mostly for renaming, and Twinkle doesn't know that C2F is the exception – it's for speedy merging. jlwoodwa (talk) 15:15, 3 November 2024 (UTC)Reply
@Jlwoodwa. Can you confirm the steps you took? Was it TW -> XFD -> CfD/S -> C2D?
When I did that on testwiki just now, it placed {{subst:cfr-speedy|1=Trochilinae}}. But you're saying it should instead place {{subst:cfm-speedy|1=Trochilinae}}? –Novem Linguae (talk) 15:34, 11 November 2024 (UTC)Reply
Almost – it was TW→XfD→CfD/S→C2F. Most of the speedy category criteria are used for renaming, but WP:C2F is for merging, so I think it should place {{subst:cfr-speedy}} in most cases and {{subst:cfm-speedy}} only when C2F is used. jlwoodwa (talk) 16:44, 11 November 2024 (UTC)Reply

Request for a new warning to be added

edit

Every once in a while I have to use the Uw-pronouns series of warnings, and it kind of bugs me that this isn't available for use with twinkle. I'm not quite sure if this is right place to suggest something like this, and if it isn't then I would greatly appreciated being pointed in the right direction. Gaismagorm (talk) 00:44, 4 November 2024 (UTC)Reply

Can we have a warning for renominating pages where the discussion was recently closed?

edit

This would be very ideal as I am not always aware when using Twinkle whether a page has recently been nominated for deletion or not. I just made that same mistake again and I think this problem is avoidable. Something like this:

  • Warning: This page was was recently nominated for deletion and had its discussion closed. Please take caution before renominating again.

or something similar. Awesome Aasim 02:41, 8 November 2024 (UTC)Reply

See also this issue (related, but different), about giving a heads-up when undeleting a page that was previously undeleted. — Frostly (talk) 23:15, 10 November 2024 (UTC)Reply
There's also this thing called "checking the talk page first" as that is the normal location for notifications of previous nominations. Just Step Sideways from this world ..... today 01:13, 11 November 2024 (UTC)Reply
edit

Following a TfD, {{Advert}} and {{Promotional tone}} have been merged and moved to {{Promotional}}. Please update Twinkle accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:11, 8 November 2024 (UTC)Reply

mw.loader.load('ext.gadget.TwinkleAr');

edit
 
the options that i never get in arwiki

Hi Every one,

I'm Ayoub from arwiki, sorry if i ask for help in the wrong place nd sorry for my english, As you may know arwiki use

mw.loader.load('ext.gadget.TwinkleAr');

as here to load Twinkle, and it works very well, but in File namespace when i choiceTw>Tag its gives me nothing, but in articles pages it works, so I need help to fix that probleme,   Thank you — أيوب (Talk 📧) 21:41, 8 November 2024 (UTC)Reply

It might be better to get a technical person from your own wiki to look into this. Have you tried posting somewhere like ar:ويكيبيديا:الميدان/تقنية or ar:نقاش_ويكيبيديا:لمح_البصر? –Novem Linguae (talk) 17:20, 11 November 2024 (UTC)Reply
@Novem Linguae Thank you for replay, I tried to share this issus with Interface administrators in Wikipedia:Interface administrators' noticeboard there, but i don't get any information exept that Twinkle in arwiki is load from enwiki, that's why i open this topic here hoping find any help. — أيوب (Talk 📧) 19:49, 11 November 2024 (UTC)Reply
@Novem Linguae thank you again, the issus is fixed. — أيوب (Talk 📧) 21:16, 11 November 2024 (UTC)Reply
You're welcome.   Closing without actionNovem Linguae (talk) 03:27, 12 November 2024 (UTC)Reply

Vandalism/Promotion Only Account greyed out

edit

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

Are you looking at an IP? NightWolf1223 <Howl at meMy hunts> 16:05, 12 November 2024 (UTC)Reply
Yeah TheWikipedetalk 17:45, 12 November 2024 (UTC)Reply
Likely because IPs are editors but are not accounts. Primefac (talk) 20:11, 12 November 2024 (UTC)Reply

Twinkle does not update selections when copy-pasting via right click

edit

Virtually what the title says. I discovered this as I got lazy when adding tags via twinkle.
Steps:
1. Open the Twinkle gadget for tagging
2. Use the copy paste feature when right clicking to paste in a valid option (in my case, unreferenced)
Expected result: Twinkle should update to show the unreferenced option.
Actual result: Nothing updates and it stays on the screen from when it was opened.
Cheers! Klinetalkcontribs 18:32, 16 November 2024 (UTC)Reply

Request for an RfPP preset that addresses specific pattern of disruptive editing

edit

It would be nice to be able to select a page-protection preset designed to address MAB-style IP sockpuppetry on noticeboards where we want to avoid restricting new editors' access. Currently I've been applying 1-hour or 2-hour autoconfirmed or pending changes restrictions; I don't have strong opinions about what exact number is best but I can propose 2 hours pending changes as the preset in order to have a concrete suggestion to start with. The current sockpuppetry log statement is essentially fine, could be made more precise as Persistent sockpuppetry of a high-traffic forum. signed, Rosguill talk 22:31, 19 November 2024 (UTC)Reply

Twinkle shows Teahouse is protected when it expired two minutes ago

edit

At 23:45 November 19, 2024, I was going to remove the protection template from the teahouse when Twinkle says that it is protected. It actually expired two minutes ago (23:43 November 19). I think this is because my local time is "earlier" than UTC time (for example, if UTC is at 13:00, my local time is still before that), and Twinkle assumes my time zone is the same as UTC.

 
I captured a screenshot of the error.

Myrealnamm (💬Let's talk · 📜My work) 23:58, 19 November 2024 (UTC)Reply

Renaming fluff to rollback

edit

Hello talk page watchers. I have a patch in the queue that, once merged, will rename "fluff" to "rollback". Fluff is the bespoke name for Twinkle's rollback module which provides [rollback] links on diff pages. Anyway, this also involves renaming the preference variables confirmOnFluff and confirmOnMobileFluff. Changing these preference names will make Twinkle forget those two particular preferences for 937 users that are not using the default setting. If this patch is merged as is, those folks will have to go to their Twinkle preferences and turn those preferences back on manually.

Anyway, just wanted to check with the group first. Is this kind of collateral damage acceptable here? (A bunch of the 937 are probably inactive.) Or does it need to be mitigated somehow, with backwards compatibility code, an WP:AWB run to change them all, etc? I'm leaning towards it being acceptable, but happy to hear other thoughts. Thanks. –Novem Linguae (talk) 09:15, 21 November 2024 (UTC)Reply

  DoneNovem Linguae (talk) 10:47, 22 November 2024 (UTC)Reply