This is an archive of past discussions. 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 20

←

Archive 23

Archive 24

Archive 25

Archive 26

Archive 27

→

Archive 30

The template for 'What Wikipedia is not' changed from {{Unencyclopedic}} to {{NOT}} 18 months ago. Could Twinkle be amended accordingly. The reason for the change was about clearing up confusion that the word unencyclopedic incorrectly implied, so would be good if this is changed to be clear in Twinkle also. Regards, SunCreator ^(talk) 23:48, 31 July 2011 (UTC)

If not change the template at least change the wording in Twinkle next to it. It currently says ': article contains unencyclopedic material' change it to something like ': article contain material not appropriate for an encyclopedia'. Regards, SunCreator ^(talk) 23:53, 31 July 2011 (UTC)

I am currently working on an overhaul of the list of tags, so I'll keep this in mind. — This, that, and the other (talk) 01:38, 6 August 2011 (UTC)

This has now been changed. The description for the tag still includes the word "unencyclopedic", though; if you would like this changed, please say so. — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

Today, I came across an annoying problem when I tagged an inappropriate page for speedy deletion that was created by a vandalism-only account. The vandal had created a redirect from his/her user talk page to a certain article. As a result, when Twinkle tried to post the speedy deletion notice on the vandal's user talk page, the warning message ended up on the article page instead of the user talk page. Because of this incident, Twinkle needs to be given the option of ignoring redirects that are present on user talk pages when attempting to post warnings/notices. --SoCalSuperEagle (talk) 17:41, 5 August 2011 (UTC)

That seems like a pretty rare circumstance. There could be legitimate reasons for a user to redirect their talk page, although never to article space of course. Some users have legitimate alternate accounts but keep the talk pages centralized. If it were done it would have to only apply to cross-namespace redirects. Beeblebrox (talk) 20:10, 5 August 2011 (UTC)

Hmm. What I'd like to see would be for it to be set up so that cross-namespace redirects on user talk pages are automatically ignored, and redirects to other user talk pages produce a dialog asking the Twinkle user whether they want to ignore the redirect. This would handle the (admittedly rare) instance of a savvy vandal redirecting their user talk page to that of an established user in an attempt to forward the warnings they would have received to that user. Granted, both of these would probably be very rare (I personally have never seen either one), so this would probably be a low-priority fix, but knowing very little about JS, I wonder how easy or difficult it would be to implement. jcgoble3 (talk) 00:50, 6 August 2011 (UTC)

It wouldn't be super-easy to fix this, but it would be possible. Still, as you say, it would be low-priority, as most User talk redirects are legitimately created by renamed users or users with alternate accounts. — This, that, and the other (talk) 01:38, 6 August 2011 (UTC)

Going along with this, I (through Twinkle) warned a sockpuppeteer for a file without permission on his/her user page, since the user talk page redirected to it. An override feature would be nice when there is a redirect, as I would not have put this template on the user's user page had this been done manually. Logan _Talk ^{Contributions} 22:07, 8 August 2011 (UTC)

Certainly a good idea, but it's easier said than done. Twinkle relies on the server to follow redirects. We would have to implement our own redirect-following logic (not simple!) if we wanted to follow only non-cross-namespace redirects for user talk notifications. — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

I just added {{non-free reduced}} to a file, but Twinkle didn't included a timestamp to the template. I think this needs to fixed. Sir Armbrust ^{Talk to me} _Contribs 20:11, 10 August 2011 (UTC)

Will fix. Thanks for telling us. — This, that, and the other (talk) 08:09, 11 August 2011 (UTC)

Done. — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

In the non-admin (i.e. tagging-only) version of the CSD module, if you tag an image for "F7: Invalid fair-use claim", the resulting tag will always be {{db-badfairuse}} (= {{db-f7}}). However, this tag is appropriate only for a fairly small subset of images handled by WP:CSD#F7, namely those that can be deleted immediately (F7a "clearly invalid tag" and F7b "commercial image agency"). The far greater number of cases of replaceable files and other disputed rationales cannot be handled in this way, since they require delayed speedies. This often leads to technically incorrect taggings, since Twinkle users will of course think the option that says "F7" handles all of the F7 cases.

I can see two possible fixes: either split up the option into three (F7ab for immediate deletion, F7c for replaceable, F7d for otherwise disputed), although some of this would duplicate options that also exist in the "twinkleimage" module; or add an explanatory note that this option should only be used for the immediate cases, pointing users to the other module for the replaceable/disputed-rationale ones. Fut.Perf. ☼ 12:46, 11 August 2011 (UTC)

I think the note is a better option, since most applications of F7 involve a seven-day waiting period. SchuminWeb (Talk) 18:46, 11 August 2011 (UTC)

How does this look? These two options would appear in the CSD dialog:

F7: Clearly invalid fair-use tag – tooltip: This is only for files with a clearly invalid fair-use tag, such as a {{Non-free logo}} tag on a photograph of a mascot. For non-obvious cases, use the options on Twinkle\'s DI tab.

F7: Fair-use media from a commercial image agency which is not the subject of sourced commentary – tooltip: Non-free images or media from a commercial source (e.g., Associated Press, Getty), where the file itself is not the subject of sourced commentary, are considered an invalid claim of fair use and fail the strict requirements of WP:NFCC.

The concise descriptions provided for CSD criteria are not meant to be precise and complete. That is what the tooltips, and of course WP:CSD, are for. (There is a link to CSD policy at the bottom of the Twinkle CSD dialog now, too.) — This, that, and the other (talk) 07:22, 12 August 2011 (UTC)

I'd replace "for non-obvious cases" with "for cases that require a waiting period (replaceable images or otherwise disputed rationales)". The "obviousness" isn't the distinguishing criterion here (in fact, "non-obvious" cases go to FFD, not to the DI queues). Otherwise this would work for me. Fut.Perf. ☼ 11:44, 12 August 2011 (UTC)

Should be changed now. Thanks for the feedback. — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

In the tag function for File namespace pages (former FurMe), when adding {{Non-free reduced}} via Twinkle, it does not add the date with the tag. This is what it did when I added the tag via Twinkle. Basically, it placed the tag and nothing else. The template itself recommends using {{subst:furd}} to add this tag. Perhaps this can be worked into the tool to fix the problem? SchuminWeb (Talk) 12:37, 13 August 2011 (UTC)

I've fixed this in the repository, but it's waiting for an admin to sync the script on-wiki. — This, that, and the other (talk) 00:57, 14 August 2011 (UTC)

Done. — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

What happened to the blacklist, and how do I request a user be added to it? —KuyaBriBri^Talk 17:06, 16 August 2011 (UTC)

We did away with it. See Wikipedia:Administrators' noticeboard/Archive221#New Twinkle blacklist proposal and Wikipedia talk:Twinkle/Archive 22#Blacklist. In short, considering that Twinkle (A) does not give the user any new rights but rather automates certain functions that they could already do, and (B) users are fully responsible for all edits that they make using Twinkle, including ones made irresponsibly, it was redundant to the blocking policy. Basically, most admins would rather just reach for the banhammer and block someone's editing access entirely before adding someone's username to a Twinkle blacklist. So we got rid of it. And good riddance to it, too, lest Twinkle become like AWB with the whole stupid game that they play over there with enabling access to the software and revoking said access.

So in short, if someone is causing disruption via Twinkle, we're just going to block them for disruptive editing rather than going about removing their Twinkle access. SchuminWeb (Talk) 19:43, 16 August 2011 (UTC)

Understood. The specific issue I had has already been resolved through ANI, but I'll keep that in mind from here on out. Thanks for the info. —KuyaBriBri^Talk 20:29, 16 August 2011 (UTC)

I'm working on translating the user interface of twinkle for hindi wp and was wondering if it's possible for me to test the translated interface for myself only before proposing and applying it to the gadget?

Hindi wp uses an older version of the gadget. It can be found at hi:Mediawiki:Gadget-Twinkle.js.

I tried copying it to a subpage of my userpage and adding

importScript('User:Siddhartha Ghai/Twinkle.js');

to my vector.js but that didn't work(with the gadget either on or off in user preferences). What do I do?--Siddhartha Ghai (talk) 07:24, 19 August 2011 (UTC)

We have been facing similar challenges here on enwiki. See #Custom installation on this page. I wish I could help you here, but I really can't add any more other than what was said in that earlier discussion. — This, that, and the other (talk) 10:40, 19 August 2011 (UTC)

Thanks for the information. Good to know people are working on a solution. Just update the doc when you find one. --Siddhartha Ghai (talk) 15:25, 19 August 2011 (UTC)

When I try to report a page to RPP it says it can find the right section.--Breawycker (talk to me!)

Does this still happen? Or have the RPP admins fixed this? — This, that, and the other (talk) 12:12, 20 August 2011 (UTC)

When any talk page (including File talk, category talk, etc.) is open and CSD is used would it be possible to have G8 for talk page without a subject page appear at the top of the list instead of further down? On File talk in particular, this shows up on the 2nd page when scrolling, requiring a click down on every instance. I would think that when using CSD on any talk, G8 would be the most obvious choice. --After Midnight ⁰⁰⁰¹ 00:35, 19 August 2011 (UTC)

Good point; will fix. — This, that, and the other (talk) 10:40, 19 August 2011 (UTC)

Fixed in repo, pending sync. — This, that, and the other (talk) 12:12, 20 August 2011 (UTC)

Twinkle does not seem to want to use my newer settings, where I have all namespaces selected for enabling unlink. LikeLakers2 (talk) 00:57, 16 August 2011 (UTC)

Did you bypass your cache? Do that and then see if you don't get results. SchuminWeb (Talk) 01:47, 16 August 2011 (UTC)

Yes, I did. Nothing. Yes, I did try emptying my browser's temporary internet files. Still nothing. LikeLakers2 (talk) 01:59, 16 August 2011 (UTC)

Has Twinkle started listening to you yet, or is it still being delinquent? — This, that, and the other (talk) 10:41, 19 August 2011 (UTC)

(moved to bottom of page) Now, it looks for pages from all namespaces. However, I can't seem to get it to actually unlink the pages. I'll upload a picture to my site's ftp, and link it in a moment. LikeLakers2 (talk) 16:41, 19 August 2011 (UTC)

See here. Basically, it shows all of the namespaces, like I set it to, yet when I hit submit query, (whether I inputed a reason or not) it says it finished successfully. But, it seems as though it did not do an actual edit for that. (feel free to remove that link once you have looked) LikeLakers2 (talk) 16:43, 19 August 2011 (UTC)

Ah, I see, you are using Internet Explorer. Unlink has always been a bit flaky in IE. I'll look into it. — This, that, and the other (talk) 01:08, 20 August 2011 (UTC)

If you observe the status dialog, you will see that Twinkle is trying to remove backlinks from the page On, which is normally a fruitless endeavour. I have fixed this problem in the repo; pending sync. — This, that, and the other (talk) 12:12, 20 August 2011 (UTC)

The dialog for notifying a user about a sockpuppet investigation needs some tweaking if possible. It asks for a linked article, but the template {{uw-socksuspect}} expects a user name or SPI subpage. Twinkle then leaves an inaccurate edit summary: Warning: Sockpuppetry on <username> (Wikipedia:TW|TW). The dialog box should ask for the master account name and the edit summary should read something like Warning: You are a suspected WP:SOCK|sockpuppet of User:<username>. See my edit here for an example. Thanks ​—DoRD (talk)​ 22:42, 19 July 2011 (UTC)

I tried to fix this, but it seems there is a coding error. I'll try again soon. — This, that, and the other (talk) 10:13, 24 July 2011 (UTC)

I have fixed the coding error. This should begin to work shortly. — This, that, and the other (talk) 01:38, 6 August 2011 (UTC)

Almost. Twinkle is now erroneously inserting User: before the username when it calls {{uw-socksuspect}}, which expects the username only. See here for an example. Thanks ​—DoRD (talk)​ 00:03, 26 August 2011 (UTC)

And, come to think of it, the edit summary should probably be Warning: You are suspected of WP:SOCK|sockpuppetry to be appropriate for both socks and masters. ​—DoRD (talk)​ 00:09, 26 August 2011 (UTC)

Please see this correction which I had to apply to a TW generated-message - space added before (2nd. — RHaworth (talk · contribs) 10:50, 23 August 2011 (UTC)

This isn't a Twinkle problem as much as it is a template problem. Do we even know what this template is? We can go in and fix the problem, but I couldn't find what template this even was. Thus I can't fix what I can't identify. SchuminWeb (Talk) 05:07, 24 August 2011 (UTC)

The {{AfD-notice}} template has an undocumented "order" parameter which Twinkle uses. I can see no reason why the space would have been omitted, as Twinkle inserts this by way of a " " character entity. In other words, I'm just as puzzled as you are. — This, that, and the other (talk) 07:57, 24 August 2011 (UTC)

Even when tagging something as G10, if there's something inferior like a7, it will not replace it. I think if someone tags something as G10, it should ignore the fact that there's an A7 or something lower-priority, as I've had to revert someone else's tag so I could tag it as an attack page, multiple times. --Σ _{^talkcontribs} 05:01, 26 August 2011 (UTC)

I agree that this is a hassle. I think that twinkle should either just add the second tag or combine the existing tag with the new tag. Is this technically possible? Ryan Vesey Review me! 05:13, 26 August 2011 (UTC)

At least for G10 this is certainly important, as they need to be deleted more quickly. I might add a feature that replaces CSD tags with {{db-attack}} when that option is selected. — This, that, and the other (talk) 05:27, 26 August 2011 (UTC)

I think there should be an option to allow the user to force him/herself to generate a preview of a user warning before submitting it. If this option were checked, the "submit" button would be disabled (greyed out) unless the "preview" command had been clicked at least once. An even better option would be to require a preview after any change to the level or type of the warning being created. I always do a preview, and I'd like to use an option like this to make me remember to preview, but I realize others might not want this to be mandatory. Richwales (talk · contribs) 19:38, 27 August 2011 (UTC)

This could get quite annoying after a while, and would increase server load (the API isn't cached, as far as I know, and it isn't very fast either). Also, I don't see the benefit in adding such a sugary feature when only one user is likely to use it. — This, that, and the other (talk) 07:56, 28 August 2011 (UTC)

Currently, if Twinkle tries to place a CSD, PROD, or XFD tag on a page that already has a CSD tag, it will simply abort the procedure with an error message. I think this response should be changed so that if a user tries to place a CSD tag that doesn't match the one already on the page, Twinkle would prompt whether it should overwrite the existing CSD tag with the new one. Or if a user tries to PROD or XFD a page that already has a CSD tag but clearly doesn't meet any of the speedy deletion criteria, Twinkle should prompt whether it should downgrade the CSD to a PROD or XFD. If the user answers yes, Twinkle would then prompt for both the CSD decline reason and the PROD or XFD nomination rationale. --SoCalSuperEagle (talk) 21:49, 27 August 2011 (UTC)

I agree, just as I did for the G10 attack proposal earlier. I think another option should be that it combines both tags into multiple issues. Ryan Vesey Review me! 23:44, 27 August 2011 (UTC)

The best solution is to educate those who patrol new pages into paying more attention to accuracy. If they would read WP:NPP first to see exactly what page patrolling entails, they would be less likely to cause the errors that need the remedy suggested above. --Kudpung กุดผึ้ง (talk) 00:58, 28 August 2011 (UTC)

Right, but changes to Twinkle can't educate the people who patrol new pages. Changes to the tool can only be made in reaction to the way things are currently done. Ryan Vesey Review me! 01:00, 28 August 2011 (UTC)

Personally I think the easiest way to replace a CSD tag is to edit the page manually and change the template. The benefits of this are that the creator won't be notified again, and it requires less coding in Twinkle If you haven't memorised the CSD criteria, you can refer to the Twinkle list, then close it and change the CSD template on the page to {{db-g6}} or whatever criterion you want. — This, that, and the other (talk) 07:52, 28 August 2011 (UTC)

That's what I do, and it's the logical solution. I understand Ryan's comment, but tools are supposed to be an aid for the people who already possess the knowledge of policy to use them. Tools are not suppose to plug that knwledge gap. Everyone has time do carry out such manual corrections - we need to put out a clear message that 'speedy deletion' is not a synonym for 'speedy tagging'. Kudpung กุดผึ้ง (talk) 08:39, 28 August 2011 (UTC)

I have a quick question. Is there a single-issued notice for offensive or promotional usernames? -- Luke (Talk) 01:02, 28 August 2011 (UTC)

You're looking for {{uw-username}} and {{uw-coi-username}}, both of which can be found near the bottom of the "Single issue warnings" category in Twinkle. jcgoble3 (talk) 03:07, 28 August 2011 (UTC)

Any chance the dropdown list for non-indefinite blocking could include "disruptive editing" like the warning tags do? Quite often I find myself blocking editors for short periods of time for transgressions that aren't strictly vandalism, and aren't strictly 3RR violations, and at the moment I have to edit the template after I've placed it. Black Kite (t) (c) 14:40, 13 August 2011 (UTC)

Likewise, while we're tinkering, could we harmonize the Twinkle list's order with the block dialog's order of reasons as much as possible? Would make it much easier to find the template I'm looking for. SchuminWeb (Talk) 21:13, 13 August 2011 (UTC)

Re Black Kite, I'm afraid I don't understand your request at all. It might have something to do with me not being an admin! Is there a template you want added to the list of block templates?

Ah, I see the problem now. Very surprisingly, no disruption block template actually existed (there were level 1-4 templates, but no block). I have created one instead - Template:Uw-disruptblock. Can this be added? Thanks. Black Kite (t) (c) 11:25, 14 August 2011 (UTC)

Re SchuminWeb, I would look into this, but I can't find the list of block reasons for some reason. It ought to be somewhere in the MediaWiki namespace. Do you know where? — This, that, and the other (talk) 10:15, 14 August 2011 (UTC)

It's here - MediaWiki:Ipbreason-dropdown. Black Kite (t) (c) 11:28, 14 August 2011 (UTC)

It's on my to-do list. — This, that, and the other (talk) 12:12, 20 August 2011 (UTC)

Almost done. Also included in the package is a feature allowing admins to preview block templates!! Exciting. (I wrote this just to remind myself to get this done.) — This, that, and the other (talk) 10:27, 31 August 2011 (UTC)

Can we add the {{Autobiography}} template to Twinkle, please? I'm fairly certain it used to be in there. Some believe it's covered by {{COI}} because both are defined as someone who is pushing goals that are contrary to WP's but where a COI is someone with a close connection to the subject, AB are the actual subject. I'm hung over. I hope that made sense. OlYeller^Talktome 17:26, 20 August 2011 (UTC)

I removed it, because I thought it was little-used. But, looking more closely, it appears to have almost a thousand transclusions. So perhaps my removal of it was unjustified... I've added it back in the repo, so it should re-appear soon. — This, that, and the other (talk) 04:16, 21 August 2011 (UTC)

Thank you. Keep up the great work! OlYeller^Talktome 00:18, 27 August 2011 (UTC)

I'm not seeing it in there still. Do I need to clear my cache or something? I'm not terribly knowledgeable about how scripts like this work. OlYeller^Talktome 14:24, 29 August 2011 (UTC)

The change was made in our offsite repository, but the gadget file on this wiki has not been updated yet. User:Amalthea usually does this, but he seems to be away at the moment, so updates are not getting done. User:AzaToth can also do it. I'll poke him when I've pushed a couple of other changes. — This, that, and the other (talk) 10:27, 31 August 2011 (UTC)

Zdroj:https://en.wikipedia.org?pojem=Wikipedia_talk:Twinkle/Archive_25
Text je dostupný za podmienok Creative Commons Attribution/Share-Alike License 3.0 Unported; prípadne za ďalších podmienok. Podrobnejšie informácie nájdete na stránke Podmienky použitia.

---