Wikipedia talk:Twinkle

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Twinkle not leaving CSD notices on user pages when CSDing redirects for some criteria[edit]

When using Twinkle in my browser, CSD notices are not being given to relevant users on their talkpages when I nominate a redirect for speedy deletion. This occurs even when the "Notify page creator if possible" is checked to notify the creating user. I have the page creation script enabled as well. — Mikehawk10 (talk) 23:54, 19 October 2021 (UTC)

@Mikehawk10: Which criteria, specifically? – SD0001 (talk) 08:23, 20 November 2021 (UTC)
By default, CSD notices are not sent for R2, R3 and R4 criteria. See WP:TWPREFS#speedy where you'll find that those checkboxes are unchecked. These preference options take precedence over the "Notify page creator if possible" option in the CSD screen. – SD0001 (talk) 08:29, 20 November 2021 (UTC)

Why (and how) is Twinkle posting from my bot account?[edit]

I have used twinkle to flag two pages for speedy deletion, and both times the edits came from my bot account. While my bot account had recently accessed the API via a tool running on toolforge, and I had made an edit from my bot account using a private browsing window, that private browsing window had since been closed, and the browser window I was using at the time said I was logged in as "Ahecht" at the top. How is Twinkle able to post as something other than the currently logged in user? --Ahecht (TALK
PAGE
) 17:29, 12 November 2021 (UTC)

Twinkle can only post as the currently logged-in user, but that is not necessarily the one whose username you see at the top. It can change if you log out and log in as the bot in another tab, for instance. Twinkle would never edit under IP addresses, as the API requests use the assert=user check, but currently the assertuser= check is not set, that would ensure that the logged-in user hasn't changed.
DId you see the "edit token expired, fetching new token..." message?
Also, when the page reloaded after action complete, which was the account signed in? – SD0001 (talk) 18:42, 12 November 2021 (UTC)
I did get a "fetching new token" message, but when the page reloaded I was still logged into my Ahecht account. Pages I edited manually after using Twinkle were also using the correct account, but then when I used Twinkle again it posted from the bot account. I think somehow the API was logged in separately from the browser itself. I opened the console and did a new mw.Api().postWithToken( 'csrf', {action: "logout"} ) and logged back in, which seems to have fixed it. --Ahecht (TALK
PAGE
) 22:08, 12 November 2021 (UTC)

Spam blacklist[edit]

I unknowingly included a link to a site on the Spam blacklist in an AfD nomination using Twinkle. As a result, no nomination page was created, but other actions, such as adding the nomination to today's log and notifying the page creator, were performed anyway. In order to redo the nomination, I had to revert those actions first to prevent duplication, and of course type my nomination statement again. Not terrible, but certainly annoying. Could Twinkle not be made to not perform any action at all if one action is not allowed? Lennart97 (talk) 13:37, 15 November 2021 (UTC)

@Lennart97: This could potentially be fixed. But did you have to type the nomination again, or did you get the Your deletion rationale is provided below, which you can copy and paste into a new XFD dialog if you wish to try again message? – SD0001 (talk) 14:30, 15 November 2021 (UTC)
If that's what normally happens, then most likely it happened here too without me noticing, thinking it was part of a long unimportant error message, although I can't be sure... sorry! :) Lennart97 (talk) 14:51, 15 November 2021 (UTC)

Request to remove the SPI notification checkbox[edit]

Notifications are rarely advisable at SPI, and the SPI team has quietly discouraged them for some time. There are rare times when someone's participation is needed, usually if there's strong evidence but a possible AGF explanation, but that should be a carefully studied decision. In practice, when that does happen, it's usually done with a custom message rather than a templated message (example by me, example by a CU). Despite the "use your judgment" tooltip above the notification checkbox, many users (including very experienced ones) still check it by default, presumably on the premise that if it's required for AN, ANI, etc., it's also advisable for SPI. But at SPI, unlike any of these other venues, users should only be filing if good-faith explanations have been exhausted; there is not the notion of working with the subject of the filing to improve, as there is at other venues. Most filings are against repeat offenders who, if notified, often troll the comments and harass the clerks and admins.

Again, there may be some cases where a notification is indicated, but by removing the checkbox we'd force people to put some more thought into that decision to notify. Special:Search/~"An editor has opened an investigation into" shows countless cases of experienced users notifying users who have been blocked or banned for years, suggesting that people tick this box out of habit rather than with due consideration to the circumstances. Both times that I've brought this up with a user, they've told me they thought they were supposed to notify. (Across ~300 filings I've clerked so far, I believe I've notified in three, all with custom notifications, and I think that's about standard for clerks, CUs, and admins who regularly patrol SPI.) -- Tamzin[cetacean needed] (she/they) 17:51, 19 November 2021 (UTC)

Cross-posted to the clerks' noticeboard. -- Tamzin[cetacean needed] (she/they) 17:51, 19 November 2021 (UTC)
  • Yeah, I agree with this assessment. --TheSandDoctor Talk 17:58, 19 November 2021 (UTC)
  • Sounds good to me. I'm all for simplifying user interfaces, especially when it's been shown that an offered option mostly leads to incorrect use. -- RoySmith (talk) 18:07, 19 November 2021 (UTC)
  • Also notified: WT:SPI. – SD0001 (talk) 11:48, 22 November 2021 (UTC)
  • Agreed. I believe the last thing we want to do is to give the offender a heads-up that they're being investigated.   Aloha27  talk  12:21, 22 November 2021 (UTC)
  • Support removal due to mostly incorrect use. If people desire to use it they could always place it manually. Dreamy Jazz talk to me | my contributions 16:13, 22 November 2021 (UTC)
  • I've used it very productively in one case. However, once it's used incorrectly, the notification is the toothpaste that won't go back in the tube. Support removal. Cabayi (talk) 19:43, 22 November 2021 (UTC)
    I wrote a patch for this that was accepted today. Should be all set. This functionality will be removed in the next release of Twinkle. –Novem Linguae (talk) 21:13, 24 November 2021 (UTC)

TwinkleMobile[edit]

Hello everyone, I'm from viwiki. Yesterday, I made a script which enables Twinkle on mobile view (Minerva skin). If you want to use this script, please see how to install it on this page: User:P.T.Đ/TwinkleMobile. I don't know English, so I can only write basic sentences. Thanks. P.T.Đ (talk) 19:57, 28 November 2021 (UTC)

Thanks for the note @P.T.Đ. This looks excellent. Ideally, we should integrate minerva support into the gadget. I'll open a github issue for that. Sidenote: you should probably use the Toolforge CDN instead of cdnjs for loading an external library to comply with the wikimedia privacy policy. – SD0001 (talk) 15:58, 1 December 2021 (UTC)
Thanks @SD0001. I used Toolforge CDN for external library. I made this because some viwiki users want to use Twinkle on mobile. If Twinkle is updated for using on mobile (and the gadget supports mobile view, loads scripts with ResourceLoader), I will disable this script. P.T.Đ (talk) 22:44, 2 December 2021 (UTC)
Opened #1483 on the issue tracker. – SD0001 (talk) 17:09, 5 December 2021 (UTC)

redirect which may not be needed in uw-joke1[edit]

in the uw-joke1 template, the "certain degree of freedom" section links to a redirect, I'm not sure if that's particularly needed. Example on a user talk page. It links to this redirect, which is an alternative capitalisation of the actual title of the page it's linking to, and I'm not sure if its necessary. Not really a big issue, just something I noticed.

DirkJandeGeer (щи) 12:24, 30 November 2021 (UTC)

@DirkJandeGeer: Since you've mentioned it, I've edited {{uw-joke1}} to bypass two redirects. This isn't really a Twinkle issue; Twinkle just places the template on a user talk page, and doesn't care what the template actually says. -- John of Reading (talk) 12:43, 30 November 2021 (UTC)
Many thanks, I was trying to figure out how to edit it but I saw a notification saying I should post something on this talk page first, now I know for next time.
Thanks for the help, DirkJandeGeer (щи) 13:38, 30 November 2021 (UTC)

Retooling the Vandalism revert button[edit]

Hi, I have a suggetion for changing the "Vandalism" revert button to something else. At present, the "Vandalism" button reverts a series of edits, has no option for adding an edit summary, does not automatically give an explanation in the summary, but does open the user talk page for adding warnings. (The automatic summary "Vandalism" was removed several years ago.)

I'd like to suggest that this be changed to add a edit summary, but not open the user's talk page. This would basically be a straight rollback, and could be called "Rollback No Warning" or something else. This would be useful in cases where a rollback is desired, but warning the offending user is unnecessary for whatever reason. Thanks. BilCat (talk) 20:43, 30 November 2021 (UTC)

@BilCat Adding an edit summary but not opening the user's talk page is what the "Undo" button is for. --Ahecht (TALK
PAGE
) 21:28, 30 November 2021 (UTC)
Not if there's more than one edit. That's my point. BilCat (talk) 21:31, 30 November 2021 (UTC)
@BilCat Undo works just fine for more than one edit. For example, try the undo button at http://en.wikipedia.org/w/index.php?title=Wikipedia%3ASandbox&type=revision&diff=1058001342&oldid=1058001285 (assuming no one else has written to the sandbox in the meantime). --Ahecht (TALK
PAGE
) 22:04, 30 November 2021 (UTC)
They have. BilCat (talk) 22:08, 30 November 2021 (UTC)
Isn't there already a 'Rollback' button for this purpose? When I use it, I get a warning first, then a prompt to enter an edit summary. I am then taken to the user's talk page, but this is a setting that can be changed in Twinkle prefs. Firefangledfeathers 22:13, 30 November 2021 (UTC)
Yes, there is, but I am taken to the user's talk page. In most cases that's what I want to happen, but not in all cases. BilCat (talk) 22:19, 30 November 2021 (UTC)
Looks like that's something that you could change in Twinkle preferences. I appreciate the Vandalism button. When I use it, I know my edit will be marked minor with no additional edit summary, which I know communicates a reversion of vandalism. And I like to add an appropriate template warning to the user talk. Firefangledfeathers 22:24, 30 November 2021 (UTC)
It's an either/or option, so I'd like a separate button for each. I'd also prefer that it add "Vandalism" automatically, but I'm in the minority on that one. (I don't use it incorrectly, but apparently other users did, and so Vandalism was removed from the summary.) BilCat (talk) 22:31, 30 November 2021 (UTC)

Discussion at Wikipedia talk:Template index/User talk namespace § Customizing warning headers for Twinkle[edit]

 You are invited to join the discussion at Wikipedia talk:Template index/User talk namespace § Customizing warning headers for Twinkle. {{u|Sdkb}}talk 20:57, 30 November 2021 (UTC)

G10 notice should link to the page, no?[edit]

See Special:Diff/1058050271. I'm taking this here because both the template and Twinkle would need to be changed, I imagine. Enterprisey (talk!) 06:34, 1 December 2021 (UTC)

I always assumed that was intentional, since the name of the article is often an attack itself. Meters (talk) 06:49, 1 December 2021 (UTC)
Yes, it's intentional as attack page titles are often libellous. In fact, the code has a lot of hacky special cases like this just to prevent G10 page names from leaking anywhere – even in the edit summary and the CSD log. – SD0001 (talk) 12:01, 1 December 2021 (UTC)