text:
Wikipedia talk:Twinkle/RFA/Archive 2
|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 1
|Archive 2
- 1 Google Chrome
- 2 CSD I10 and I11
- 3 IfD notifications
- 4 {{Uw-spamublock}}
- 5 {{schoolblock}}
- 6 Notifying top contributer
- 7 Prod2
- 8 schoolblock/anonblock
- 9 Open user talk pages in preview mode
- 10 Notify if possible?
- 11 No evidence of permission
- 12 Expanded AIV options
- 13 Alternate CSD notice for new users?
- 14 Bundle
- 16 Diff link in vandal warnings
- 17 Tagging
- 18 Welcome
- 19 Identify the tool
- 20
User contributions from userpage of user Talk page(resolved - user unaware this is already available)
- 21 Previously deleted versions of pages
- 22 Restore this version
- 23 Notice of reporting
- 24 Talkback
- 25 Additional Single issue notice
- 27 Prod check
- 28 ARV: Usernames
- 29 Don't automatically notify IPs of AfDs
- 30 F8 should ask for filename
- 31 Customise messages for different namespaces
- 32 Deleting copyvios - prompting for URLs
- 33 Automatic "Preview" instead of automatic "Save page"
- 34 Courtesy page blanking when applying db-attack
- 35 Wait for revert completion
- 36 Self-reverting
- 37 Talk page vandalism and SineBot
- 38 Prod, AfD notification and welcome template
- 39 Display last diff after a revert
- 40 Prod-nn?
- 41 (Accidental) misuse of CSD G1
- 43 Add abuse filter block template to list of block templates
- 44 Change G8 template
- 45 Option to not edit protected pages
- 46 Allow reason to be entered for block templates
- 47 Twinkle for IE
- 48 Parsing of SSP boxes for extra User: prefixes
- 49 Image renaming
- 50 BLPunreferenced
- 51 Adding Sofixit
- 52 Simple diffs in AIV reports
- 53 d-batch : option to not delete redirects
- 54 add additional box to CSD G3
- 55 Log articles that I prod
- 56 db-reason
- 57 Patrolling tagged pages
- 58 Function to replace instances of an image being deleted
- 59 CSD notifications
- 60 Add {{citation style}}
- 61 {{uw-fuir}}
- 63 Blatant promotion RfC results
- 64 Auto-add UAA Templates to UAA reports...
- 65 Add the Welcometest message to twinklewarn.js
- 66 Default DELSORT extension
- 67 Template:uw-vgscope
- 68 {{db-attack}} should have the option of adding {{courtesy blanked}} under it.
- 69 Category tag feature
- 70 Support for custom CSD-rationale
- 71 Note for SPI cases
- 72 Watching a user on ARV
- 73 Talkback
- 74 support for template:merge
- 75 AFDM - Hiding Instructions
- 76 Cross-wiki support and customization
- 77 Vector skin support
- 78 An option to instantly report page creator should be provided when tagging a spam page
- 79 Uw-resume
- 80 SPI notification
- 81 Customizing color of rollback links
- 82 Twinkle and rollback
- 83 Reporting to AIV
- 84 Watchlist undo/rollback
- 85 Userification of more blatant autobios
- 86 reqinfobox
- 87 userpages of blocked users as a choice for page protection reason
- 88 Rationale option for all CSDs
- 89 {New unreviewed article} template suggestion
- 90 AfD creation
- 91 Tool for CAT:TEMP
- 92 WP:CONTESTED procedure
- 93 New dropdown menu on Vector?
- 94 Add support for {{db}}
- 95 Prod
- 97 Option to remove deletion captioning on images..
- 98 Marking as patrolled after PRODding
- 99 Another warning template
- 100 Yet another warning template
- 101 db-move with reasoning
- 102 Image Tagging request
- 103 Twinkle should ask for pagename and reason when tagging for {{db-move}}
- 104 Indef
- 105 Template Suggestion
- 106 Unarchived request - Another warning template
- 107 blacklist and copyvios
- 108 Deletion tagging should remove {{mtc}} and related
- 109 Option to tag an image as conflicted-license informing uploader
- 110 De-prodding
- 111 3RR Warning
- 112 Add support for {{db}}
- 113 AfD closing
- 114 Userfication/incubation
- 115 Add another template
- 116 Multiple AfDs
- 117 Propose merge
- 118 Warnings
- 119 Tfd needs updating
- 120 Remove new article tags
- 121 Suggestion
- 122 Additional Template
- 123 Add CSD criteria?
- 124 BLP Prod
- 125 Page blanking
- 126 Restore this version (revisited)
- 127 Template Request
- 128 Sockpuppet reporting thought
- 129 BLP PROD part 2
- 130 Warn code: COI
- 131 Tabs on contributions page
- 132 {{uw-hasty}}
- 133 Global lock checks when attempting to report users
- 134 db-multiple
- 135 G6 - "Local description page for Image on Commons"
- 136 Second prods
- 137 add uw-affiliate warning
- 138 If user is blocked, confirm warning needs to be added
- 139 Clean up tags
- 140 Warn
- 141 Another notice to add
- 142 blp prod removal
- 143 Add {{Uw-spoiler}}
- 144 CSD C1 - Empty Category script should inform category creator about deletion.
- 145 Handle end punctuation in "rollback" edit summary dialogue
- 146 Add optional rationale for db-g6
- 147 Add support for {{Uw-incompleteAFD}}
- 148 Edit War Warning.
- 149 Separate CSD#G10 into two points and detecting redirect/later expansion
- 150 Restate edit summary for pseudo-speedy deletion
- 151 Add support for db-animal
- 152 Warn about permissions
- 153 Ask administrator for clarification on bit-by-bit commons deletions
- 154 Add a legal threat block warning option for IPs
- 155 Semi-protecting a page with pending changes
- 156 Another request on optional rationales
- 157 Remove Template:Uw-sandbox
- 158 add {{Urls}} to Tags option
- 159 Move to commons assistant
- 160 Add a 'Rough translation' tag
- 161 Retain user's Talk page link, on reverting
- 162 Articles for creation
- 163 Add {{WWFinuse}}
- 164 Add Notability:Sports to notability tag options
- 165 On other languages
- 166 Maxlength for rollback prompts
- 167 Wikilink "reverted" to Help:Revert
- 168 Add better Find sources links to AFD/XFD
- 169 Username reports
- 170 Add language popup box for notenglish tag
- 171 Add contrib tags
- 172 Move stuff around
- 173 Addition of {{All plot}} and {{Cleanup-link rot}} (again)
- 174 Add support for db-multiple
- 175 Template:Edit Summary
- 176 Support for more di templates
- 177 Add {{Shared IP gov}}
- 178 Moving files to Commons
- 179 Add new templates
- 180 Uw-mos
- 181 Template:Uw-generic4
- 182 Replace the "don't warn" function for users nominating their own work for deletion/tagging
- 183 Opt out
- 184 {{tense}}
- 185 Add indication that original author has been notified
- 186 New template {{uw-copyright-remove}}
- 187 Minor nit to wording of CSD menu
- 188 Awarding barnstars
- 189 Something to add
- 190 Userfication moves as a default or easier for patrollers than deletion or CSD tagging
- 191 Translation template
- 192 Don't re-create a page that has been deleted under you
- 193 Schoolblock
- 194 Edit-warring warning edit summary
- 195 Linkrot?
- 196 Warn
- 197 Reducing bite
- 198 New welcoming template
- 199 Protection templates
- 200 Belated welcome template?
- 201 Support reason parameter for cleanup template
- 202 Clearer edit summary for "welcome problem user" templates
- 203 Adding suggested merger tags?
- 205 duplicate
- 206 Multiple AfDs
- 207 New template
- 208 Preview Template
- 209 Minor change to menu wording
- 210 language tag for {{tt:notenglish}}
- 211 Multiple CSD reasons
- 212 Barnstars/otherwise positive stuff
- 213 Additional maintenance templates
- 214 Article class candidates
- 215 Adding loging capabilities
- 216 Correctly add links to categories
- 217 Notifying deceased Wikipedians
- 218 Add Template:Cleanup-link rot
- 219 Add Template:bareurls
- 220 Opening talk pages
- 221 Edit summary wording
- 222 Uw-coi-username
Google Chrome
I know it's very early (the download was made public about an hour ago), but I'm wondering about support for the new Google Chrome browser. It's very fast — really speeds up Wikipedia — is built on WebKit, and seems to be really neat. I've tried Twinkle on it already, and the main lack of function seems to be clicking on radio buttons for CSD's and the like. I have a feeling this is a trivial fix. What are the plans? - Realkyhick (Talk to me) 20:08, 2 September 2008 (UTC)
Also, I am having an issue where I have to refresh any wikipedia page to get the twinkle tabs to show up... is this a legacy bug from webkit, or something specific to chrome? --Pennstatephil (talk) 15:12, 3 September 2008 (UTC)
- As far as I know (may be different with other people's computers) but everything works. RockManQ (talk) 03:05, 25 September 2008 (UTC)
CSD I10 and I11
These should/need to be added to the CSD menu for images. SchuminWeb (Talk) 15:32, 14 September 2008 (UTC)
- I10's already on there, but the request still stands for I11. SchuminWeb (Talk) 14:12, 23 September 2008 (UTC)
IfD notifications
Please add article notifications when nominating for WP:IFD. Twinkle's IfD function currently notifies only the uploader but adds no notification to the article(s) affected. Fut.Perf. ☼ 13:51, 16 September 2008 (UTC)
- Update: Looking at User:AzaToth/twinklexfd.js, I now notice the code seems already in place, but it is apparently not working. Is this a bug rather than a (missing) feature? Fut.Perf. ☼ 19:13, 16 September 2008 (UTC)
- Further: twinklexfd.js seems to define a mediawiki api query as:
// adding tag to captions var query = { 'action': 'query', 'list': 'imageusage', 'titles': wgPageName, 'iulimit': userIsInGroup( 'sysop' ) ? 5000 : 500 // 500 is max for normal users, 5000 for bots and sysops };
However, the api [1] seems to expect a parameter called "iutitle", not "titles". If the script does what I think it does, passing a query with "&titles=..." in the url, then it will get returned an error and the script will exit empty-handed where it says:
tagInstancesMain: function( self ) { var xmlDoc = self.responseXML; var nsResolver = xmlDoc.createNSResolver( xmlDoc.ownerDocument == null ? xmlDoc.documentElement : xmlDoc.ownerDocument.documentElement); var snapshot = xmlDoc.evaluate('//imageusage/iu/@title', xmlDoc, nsResolver, XPathResult.UNORDERED_NODE_SNAPSHOT_TYPE, null ); if( snapshot.snapshotLength == 0 ) { return; } }
Fut.Perf. ☼ 19:46, 16 September 2008 (UTC)
Update: This seems to have fixed it, thanks to AzaToth for the quick implementation. Fut.Perf. ☼ 20:17, 16 September 2008 (UTC)
Would it be possible to get this template added to the 'warn > blocking' menu? Thanks. --Kurt Shaped Box (talk) 18:18, 1 October 2008 (UTC)
Anon block is on the list, but not school block. Can this be added? لennavecia 14:45, 13 October 2008 (UTC)
It should be no problem to add, but I would feel better if {{schoolblock}} followed the standard user warning naming convention, like {{uw-ablock}} does. Since the template appears to be, technically, the same as {{uw-ablock}}, I've proposed that {{schoolblock}} be moved to {{uw-edublock}}. Please give your input on the proposal here. If the proposal succeeds, I'll add {{uw-edublock}} to the list of blocking templates in Twinkle right away. If not, I'll have to do some testing to make sure that Twinkle will support a blocking template that doesn't follow user warning template naming conventions. Cheers! Ioeth (talk contribs friendly) 15:22, 13 October 2008 (UTC)
- Actually, turns out that my idea isn't such a good one. Twinkle is only compatible with user warning templates that follow the WP:UW project guidelines. {{anonblock}}, which {{schoolblock}} is based on, does not follow these guidelines, but {{uw-ablock}} does, which is why Twinkle has it. You'll notice that {{anonblock}} and {{uw-ablock}} are quite different. Additionally, {{anonblock}} and {{schoolblock}} are designed to be transcluded, not substituted, so that if the contact information in them ever changes, it won't be out of date on lots of talk pages. They're both kind-of designed to be one-time-use templates placed at the top of talk pages, while {{uw-ablock}} is designed to be more of a notification template used at the bottom of a talk page. It would require a lot of effort to make Twinkle compatible with {{anonblock}} and {{schoolblock}}, so I don't think we should add them. We could propose that the WP:UW create a standard template like {{uw-edublock}} that follows their standards and can be used instead of {{schoolblock}}, though. Ioeth (talk contribs friendly) 15:50, 13 October 2008 (UTC)
Notifying top contributer
when tagging articles for speedy deletion or afd's instead of just notifying the creator of the article, it should notify the top contributor(s) as well. this would be really convenient. - -The Spooky One (talk to me) 21:06, 15 October 2008 (UTC)
I would prefer that if prod is present in an article and I want to prod as well, my reasoning to be added as prod2 instead of prod. -- Magioladitis (talk) 23:48, 19 October 2008 (UTC)
Can {{schoolblock}} and {{anonblock}} please be added to the possible usertalk page messages given when issuing a block? Thanks. Cirt (talk) 18:35, 20 October 2008 (UTC)
- Nope, they don't follow the standards for user warning templates that have been defined by the WP:UW project. Twinkle is only compatible with those templates, such as {{uw-ablock}}, which could be used in place of either of those two. Additionally, these templates are designed to not be substituted, as the contact information in them may change in the future, unlike other user warning templates. Ioeth (talk contribs friendly) 18:54, 20 October 2008 (UTC)
Open user talk pages in preview mode
In its current form, when the user talk page opens for editing, you are looking at an edit window. In order to determine which level of warning is appropriate, you must either click the show preview button or read through the existing code to see what warnings are already present. These steps could be eliminated if the page was opened in preview mode like this. Then you can quickly scroll through the page and either place a warning manually or hit the warn tab. -- Mufka (u) (t) (c) 15:49, 2 November 2008 (UTC)
Notify if possible?
I noticed that when I mark an article for deletion with CSD, twinkle gives me a checkbox with "notify if possible", but for prod and XFD it doesn't have a checkbox and automatically does it. Sometimes I want to prod/AFD article and the user is banned, no longer on wikipedia, ect. and I don't want to notify the person. Is there anyway the checkbox could be added to prod and afd as well so I could decide myself? Thanks in advance. Tavix (talk) 22:01, 20 November 2008 (UTC)
- There is now a checkbox for user notification on the PROD and XFD features. Cheers! Ioeth (talk contribs friendly) 16:13, 21 November 2008 (UTC)
No evidence of permission
Shouldn't be too difficult- could we have the addition of a feature that tags for CSD I11 (no evidence of permission) with a subst'ed {{npd}}, (or a dated {{di-no permission}}, if that is preferable) notifies the uploader with a subst'ed {{di-no permission-notice}} and tags the image captions with the usual {{deletable image-caption}}? We have other image deletion tools, so I don't see why this one would be controversial. Also, I suppose an admin tool to delete under that criteria for balance would be good, but there are other tools for that. J Milburn (talk) 21:59, 12 November 2008 (UTC)
- That functionality already exists in twinklespeedy.js. Go to an image and click on the "csd" tab and see for yourself. :-) Ioeth (talk contribs friendly) 14:27, 13 November 2008 (UTC)
- That deletes the image outright (or does for me, I don't know what the feature is for a non-admin)- I am interested in a tool that would go under the 'di' tab, so that the image could be tagged and deleted 7 days later if the issue was not resolved. J Milburn (talk) 18:01, 13 November 2008 (UTC)
- Is this an extension of my "CSD I11 and I9 issues" and the "Add no-permission to 'di' menu" discussions below? I am doing the inital {{di-no permission}} by hand so it would be nice to have it added to the di menu, or as I first suggested, as an option - sort of "first warning" would tag the di and "final warning" would do the actual CSD i11 tag. Soundvisions1 (talk) 04:04, 15 November 2008 (UTC)
- I've added the {{di-no permission}} option to the di menu. Let me know if there's anything else! Ioeth (talk contribs friendly) 15:21, 18 November 2008 (UTC)
- Cool beans. One issue/request though. It does not ask for a source input. Could a pop up appear that asks for the source and than output "source="? {{di-no permission|date=|source=}}. Thanks! Soundvisions1 (talk) 03:52, 21 November 2008 (UTC)
- Done. I also added the non-free parameter for the {{di-no source}} template. Ioeth (talk contribs friendly) 14:30, 21 November 2008 (UTC)
- Input done, but it does not output the "source=" when placing the tag on the image or in the notice on the users page. Soundvisions1 (talk) 23:40, 22 November 2008 (UTC)
- Done. I also added the non-free parameter for the {{di-no source}} template. Ioeth (talk contribs friendly) 14:30, 21 November 2008 (UTC)
- Cool beans. One issue/request though. It does not ask for a source input. Could a pop up appear that asks for the source and than output "source="? {{di-no permission|date=|source=}}. Thanks! Soundvisions1 (talk) 03:52, 21 November 2008 (UTC)
- I've added the {{di-no permission}} option to the di menu. Let me know if there's anything else! Ioeth (talk contribs friendly) 15:21, 18 November 2008 (UTC)
- Is this an extension of my "CSD I11 and I9 issues" and the "Add no-permission to 'di' menu" discussions below? I am doing the inital {{di-no permission}} by hand so it would be nice to have it added to the di menu, or as I first suggested, as an option - sort of "first warning" would tag the di and "final warning" would do the actual CSD i11 tag. Soundvisions1 (talk) 04:04, 15 November 2008 (UTC)
- That deletes the image outright (or does for me, I don't know what the feature is for a non-admin)- I am interested in a tool that would go under the 'di' tab, so that the image could be tagged and deleted 7 days later if the issue was not resolved. J Milburn (talk) 18:01, 13 November 2008 (UTC)
Thanks very much! J Milburn (talk) 12:22, 23 November 2008 (UTC)
Expanded AIV options
Would it be possible to add another option? 'Personal attacks' would be useful. Or just 'Other', which wouldn't enter a reason automatically on AIV, would require something in the freetext box. Is that doable? //roux 19:38, 23 November 2008 (UTC)
- It is do-able, but the problem is that "personal attacks" and "other" might lead people to believe that those things should be reported to AIV, which they shouldn't. AIV is only for active vandals. If a user is making personal attacks, it should be taken to AN/I, not to AIV. Ioeth (talk contribs friendly) 16:25, 24 November 2008 (UTC)
Alternate CSD notice for new users?
Hello, I used to use Twinkle to mark pages for deletion, but I realized that for new users, the standard CSD notice (automatically used by Twinkle) might be intimidating. I learned of another message, {{firstarticle}}, that is more friendly. Could Twinkle be changed to use that instead, at least as an option? Thank you, LovesMacs (talk) 23:44, 16 November 2008 (UTC)
- {{firstarticle}} won't be made available in Twinkle's warning tab because it's not part of the uw-series of warnings. It is, however, available in Twinkle's sister tool, Friendly, which compliments Twinkle's functionality nicely. Let me know if you need any help installing it. Ioeth (talk contribs friendly) 01:13, 17 November 2008 (UTC)
- Done following this discussion.
{{firstarticle}}will be added if the user talk page doesn't exist when the CSD notice is given. --Amalthea 10:37, 3 December 2008 (UTC)
- Done following this discussion.
Is there anyway there can be a WP:BUNDLE option for TW? Maybe on the XFD page there can be a little box where we can enter in an article name of what we want bundled. Tavix (talk) 03:48, 27 November 2008 (UTC)
It would be helpful if upon marking an article as such, that Twinkle would check to see if the article is set to "not patrolled" and changed it to patrolled. Grika Ⓣ 20:29, 1 December 2008 (UTC)
- Twinkle will now, by default, mark an article that you tag with the "csd" tab as patrolled if applicable. Ioeth (talk contribs friendly) 18:05, 2 December 2008 (UTC)
Diff link in vandal warnings
I think it would be a nice addition to add a link to the offending edit in user warnings, the way Huggle does. Not that it is vitally important, but I think it is more productive to direct users to their edits that were removed, especially if they weren't vandalising. Tealwisp (talk) 21:41, 3 December 2008 (UTC)
- Can you show me some examples of where Huggle does this? Ioeth (talk contribs friendly) 21:47, 3 December 2008 (UTC)
- In any warning, really, e.g. in this one. --Amalthea 22:46, 3 December 2008 (UTC)
- That's a Huggle-specific warning template. The uw series of warning templates doesn't appear to support diff links as a parameter. I could add the feature if they did. Ioeth (talk contribs friendly) 23:54, 3 December 2008 (UTC)
- Eh, I was fooled by the comment in the template claiming that the template was called
{{uw-huggle2}}, which I knew redirected to
{{uw-vandalism2}}. However, the actual template huggle is using is
I wouldn't recommend to simply share the huggle templates, so the WikiProject user warnings should first be contacted to add appropriate parameters (I hear they can be rather protective of the templates, being bold might not be the best approach). --Amalthea 00:35, 4 December 2008 (UTC)
- I encourage you to be bold! Keep in mind, though, that I will probably only add this feature if all of the uw templates support it. I've got your back if you decide to make changes to those templates! Ioeth (talk contribs friendly) 00:40, 4 December 2008 (UTC)
- Just a heads up, I am considering this, but it'll take me some time. There are quite a lot of warning templates. For some of them it doesn't make sense to add a diff link, e.g.
{{Uw-userpage}}. That shouldn't be a problem though, if the template parameter is named then it can just as well be added to those, too, and just won't show when substed. --Amalthea 05:59, 6 December 2008 (UTC)
- Just a heads up, I am considering this, but it'll take me some time. There are quite a lot of warning templates. For some of them it doesn't make sense to add a diff link, e.g.
- I encourage you to be bold! Keep in mind, though, that I will probably only add this feature if all of the uw templates support it. I've got your back if you decide to make changes to those templates! Ioeth (talk contribs friendly) 00:40, 4 December 2008 (UTC)
- Eh, I was fooled by the comment in the template claiming that the template was called
- That's a Huggle-specific warning template. The uw series of warning templates doesn't appear to support diff links as a parameter. I could add the feature if they did. Ioeth (talk contribs friendly) 23:54, 3 December 2008 (UTC)
- In any warning, really, e.g. in this one. --Amalthea 22:46, 3 December 2008 (UTC)
Any thought on adding a "tag" tab for adding things like {{advert}} etc.? Or is it already available and I'm missing something? Grika Ⓣ 17:17, 12 December 2008 (UTC)
- {{advert}}, and indeed the "tag" tab, is already in Friendly (Twinkle's sister tool), which is the tool to which you are referring, not Twinkle. It's the first template listed in the "Problem templates" section, which is the second section of templates. Cheers! Ioeth (talk contribs twinkle friendly) 17:18, 12 December 2008 (UTC)
- Installed it now! Beautiful stuff that. Grika Ⓣ 17:31, 12 December 2008 (UTC)
The new addition of a welcome message to empty talk pages when an article is tagged for CSD is great. Could an option be added to the general warnings dialog to add a welcome if the talk page is blank? Maybe it could be a checkbox so that when you leave a warning on an empty talk page, you could have the option of leaving a welcome above the warning. -- Mufka (u) (t) (c) 14:48, 16 December 2008 (UTC)
- That is a feature that was added to the talk page CSD notification templates themselves, not Twinkle. If you'd like to have a tool to to welcome new users as well, check out Friendly, Twinkle's sister tool. The two are very handy to use together and even interface between each other in some places. Ioeth (talk contribs twinkle friendly) 16:40, 16 December 2008 (UTC)
- Ah, yes. I use both and always forget which one does what. -- Mufka (u) (t) (c) 18:35, 16 December 2008 (UTC)
- Amalthea enhanced the CSD notification templates so that if they are placed on a new talk page, they automatically add {{firstarticle}} before the CSD notice now as well. I may be enhancing Twinkle in the future to do something like this, though. Ioeth (talk contribs twinkle friendly) 19:23, 7 January 2009 (UTC)
- Ah, yes. I use both and always forget which one does what. -- Mufka (u) (t) (c) 18:35, 16 December 2008 (UTC)
Identify the tool
Would it be possible to add "Twinkle" or something to the top of the popup window so that users can know which tool they are using? I always forget which is Twinkle and which is Friendly because they look the same. This only becomes a problem when there is an issue and I need to know which tool the issue is with - but it seems like a harmless addition. -- Mufka (u) (t) (c) 18:48, 7 January 2009 (UTC)
- Eh, just don't sweat it. I developed Friendly myself and while AzaToth developed Twinkle, I do a lot (most?) of the maintenance, enhancements, and updates for it now, so it doesn't really matter if you get the tools confused...the request will likely end up with me anyway! Ioeth (talk contribs twinkle friendly) 19:21, 7 January 2009 (UTC)
User contributions from userpage of user Talk page (resolved - user unaware this is already available) When patrolling and warning, it would be useful to be able to go to a user's contributions directly from their talk page (or, less usefully I think, from a Userpage). This would enable patrollers to see whether the user had a history of vandalism. TrulyBlue (talk) 11:57, 16 January 2009 (UTC) I'm confused. How do you usually find a user's contributions? There's a link to them in the MediaWiki toolbox, both on the user page and on the talk page.
Also, I'd recommend you give WP:NAVPOP a try for an easy way to get to a user's contributions from any link to a page in his userspace. --Amalthea 12:41, 16 January 2009 (UTC)
Previously deleted versions of pages
When patrolling new pages we often see pages being re-created. It would be useful to be able to see whether a page has been previously created and deleted - the deletion log. This could apply only to unpatrolled pages, though there would also be a use also for patrolled versions. This, and the previous suggestion, could clutter the GUI, so maybe they should be part of a Patroller's subset of the functionality? Love the tool, by the way. TrulyBlue (talk) 12:03, 16 January 2009 (UTC)
- I'm not sure that I understand your request. You can access the deletion log for pages that you are patrolling very easily. Are you asking for a way for it to be integrated into the CSD GUI or something? Ioeth (talk contribs twinkle friendly) 14:45, 16 January 2009 (UTC)
- OK, for example, can I go straight from TATS_CRU to [deletion log], seeing that a previous version of the article was deleted? The toolbox has "related changes" which doesn't seem to show this. Am I being thick here? I searched the page source for any mention of a link to deletion logs, with no success, so I can't find an easy way of doing this. Thanks for your patience, TrulyBlue (talk) 23:22, 16 January 2009 (UTC)
- The fastest way would be to go to the page history and click the "View logs for this page" link. That's usually good enough for me, but it wouldn't be hard to write a short script to add that link to the toolbox or to the tabs. I'd imagine that for NPPing, displaying an indicator whether this page has been previously deleted could also be quite useful. --Amalthea 00:20, 17 January 2009 (UTC)
- OK, for example, can I go straight from TATS_CRU to [deletion log], seeing that a previous version of the article was deleted? The toolbox has "related changes" which doesn't seem to show this. Am I being thick here? I searched the page source for any mention of a link to deletion logs, with no success, so I can't find an easy way of doing this. Thanks for your patience, TrulyBlue (talk) 23:22, 16 January 2009 (UTC)
Restore this version
Would it be possible to get the "Restore this version" link above both diffs? Often I'll click to see the previous version just to make sure that I'm reverting to a good version and I then don't have the option to just restore what I think is a good version. It seems like the default for the restore link would be on the newer diff because that's the one you are looking at displayed - although I understand that the purpose is to be looking at the diffs. -- Mufka (u) (t) (c) 14:36, 18 January 2009 (UTC)
Notice of reporting
Is there a way (or a chance) of having the option to post a message on a users talk page that they have been reported to admins during an arv? Grika Ⓣ 20:44, 19 January 2009 (UTC)
- Reporting to WP:SPI does notify the user(s) that you report, but currently reporting to WP:AIV and WP:UAA do not. Are you requesting that we add notification options to the AIV and UAA reporting features? If so, it seems to be a bit pointless...any reports to AIV should come after the user has been sufficiently warned, and it is not likely that a notification in the event of a UAA report would be understood since the user (obviously) isn't aware of or doesn't understand WP:U. For UAA reports, though, you may want to take advantage of the {{uw-username}} template. You can find it in the "warn" tab of Twinkle, under "Single issue warnings". Cheers! Ioeth (talk contribs twinkle friendly) 20:54, 19 January 2009 (UTC)
Any possibility of adding
{{Talkback|Username}} to the single issue notices part of the warn bit?--Jac16888 (talk) 01:27, 9 January 2009 (UTC)
- Using
{{talkback}}would require dedicated programming, since it's quite different than all other single issue notices, e.g.
{{uw-aiv}}. If you'd create something like
{{{icon|[[Image:Information.svg|25px]]}}} I left you a message at {{#if:{{{1|}}}|[[{{{1}}}]]|my talk page}}. {{{2|Thank you!}}}<!--Template:Uw-talkback-->then it would be consistent, and adding it to Twinkle would be trivial. It would however place it in the typical monthly sections, I'm not sure if editors will appreciate that. --Amalthea 13:40, 16 January 2009 (UTC)
- I've actually been considering adding a "tb" tab to Friendly, since it would seem to fit better in that tool than in Twinkle. Amalthea is very right about adding the {{tb}} template to Twinkle's warning tab...it wouldn't fit very well in there and would require some very creative modifications. Ioeth (talk contribs twinkle friendly) 14:43, 16 January 2009 (UTC)
Additional Single issue notice
Should there be an additional notice like uw-date specific to unnecessary changes between BC/AD and BCE/CE? The text could be something like:
- Please don't change between BC/AD and BCE/CE year numbering systems, as you did to {article name}. Both formats are acceptable (See Common Era and WP:ERA).
Grika Ⓣ 18:17, 28 January 2009 (UTC)
Is it possible when nominating an article for deletion, that the editor, not only gets the option to define category but also sort the article correctly by choosing from an appropriate menu with the categories found in WP:DELSORT? Then Tinkle can add the correct message in the AfD page and add the article in the appropriate DELSORT subpage. -- Magioladitis (talk)
- I would also like to request this. Regular DELSORTing is a bit of a pain anyways (two extra steps per XfD), that'd really be helpful. ~ JohnnyMrNinja 19:06, 9 February 2009 (UTC)
Prod check
When someone prods an article, could it be possible for Twinkle to check to see if it has already been prodded? If so, there could be a message recommending to take it to AfD. Doing this would cut back on the number of articles to be prodded, only to be declined by the closing admin due to it already being prodded. Thanks. Tavix (talk) 01:36, 30 January 2009 (UTC)
- That would be difficult to do very well since Twinkle would have to use the Wikipedia API to check every single past revision of the page to see if it had a PROD tag on it. It probably wouldn't be possible just because of the immense overhead (bandwidth and processing-wise) that would be required to perform the check. Sorry :-\ Ioeth (talk contribs twinkle friendly) 15:01, 30 January 2009 (UTC)
- Twinkle could at least add a template to the talk page? Then it could check for these later? Or something... ~ JohnnyMrNinja 11:17, 10 February 2009 (UTC)
ARV: Usernames
- When reporting through ARV for usernames...twinkle should check to see if the person is already blocked.Smallman12q (talk) 13:47, 31 January 2009 (UTC)
- In addition, perhaps people reported for inappropriate usernames could have the {{Uw-username}}template added to their talk page?Smallman12q (talk) 14:14, 31 January 2009 (UTC)
- I don't think it's any big deal that Twinkle doesn't check to see if a user is blocked before reporting to WP:UAA; if a blocked user is reported, one of the AIV helperbots will remove the name from the list almost immediately anyway. The {{uw-username}} template is already available in Twinkle's "warn" tab, but I don't think it's a good idea to add it to the UAA reporting process automatically. Many usernames that get reported there simply need to be blocked outright, so leaving that template would send a confusing message. I think it's probably best left the way it is right now: to let admins and users at WP:UAA decide what to do! Ioeth (talk contribs twinkle friendly) 15:21, 10 February 2009 (UTC)
Don't automatically notify IPs of AfDs
IPs can't create new articles so there is no reason to notify an IP automatically of an AfD [2]. This box should be unchecked by default when it's an IP, with the fact that the creator is an IP mentioned. ~ JohnnyMrNinja 06:55, 10 February 2009 (UTC)
- There aren't going to be many articles around that need deleting and were created by an IP before the restriction. Newer articles that went through WP:AFC are pre-screened, and only a very low part of those will go to AfD. Then there are those static IPs that we want to be notified of the AfD.
Hmm, not sure it's worth the bother for those few remaining cases. --Amalthea 09:49, 10 February 2009 (UTC)
- The only reason I bring it up is because I know that at some point those talk pages get deleted (the above link is to one that was already deleted, that I recreated), but it's definitely not a big deal. ~ JohnnyMrNinja 11:13, 10 February 2009 (UTC)
F8 should ask for filename
[3] - Often files are moved to better names at Commons, or are copied from Commons to WP. Asking for the Commons filename would prevent another edit. ~ JohnnyMrNinja 11:34, 10 February 2009 (UTC)
- Done as requested as part of this change! Ioeth (talk contribs twinkle friendly) 15:12, 10 February 2009 (UTC)
- Great, thanks! ~ JohnnyMrNinja 17:34, 10 February 2009 (UTC)
Customise messages for different namespaces
CSD is offered by Twinkle for User pages under G11, for instance. However the text inserted in the user page refers to an "article", which is somewhat misleading in the context. Example.
The solution might be to substitute "page" for "article" unless the message relates to an article? thanks --Tagishsimon (talk) 04:20, 6 February 2009 (UTC)
- That has bugged me before, too, but I didn't want to have Twinkle changed to pass namespaces to the notices (in particular because Huggle has the same problem). However, that can be solved in the notice templates now since Remember the dot figured out a way to do namespace detection in a template with
{{NAMESPACE}}one week ago (which is such an ugly hack that it prompted someone with MediaWiki commit privileges to implement it as a parser function in rev:46630).
Anyway, handling it in the notices is preferrable since they are used manually as well (at least by me). I can take care of it soonish (next week I think). --Amalthea 10:11, 6 February 2009 (UTC)
- I've changed "article" to "page" now, as you suggested. I'm going to have to think a bit harder how to improve them overall. For example, you'll notice that the talk page link where one should go to support the hangon tag is broken if the target isn't an article, and that still can't be solved with templates or parser functions alone, so Twinkle will need to be changed.
However, I'd like to couple that with a more thorough redesign and unification of all the different CSD notifications, as was previously discussed at the user warning project, so I'll put it off for a short while. It's been like that for longer than I've been active here, so it can wait a little longer I think, quick fixing it wouldn't be trivial since there are a number of parameters involved and I have no idea who might be using them. --Amalthea 16:00, 14 February 2009 (UTC)
- I've changed "article" to "page" now, as you suggested. I'm going to have to think a bit harder how to improve them overall. For example, you'll notice that the talk page link where one should go to support the hangon tag is broken if the target isn't an article, and that still can't be solved with templates or parser functions alone, so Twinkle will need to be changed.
Deleting copyvios - prompting for URLs
When I use Twinkle to tag articles for speedy deletion as copyright violations, it prompts me to enter the URL the article is copied from. I have now deleted a copyvio article using Twinkle, but it didn't prompt me for a URL so the deletion summary isn't particularly informative. Can it please prompt for a URL upon deletion like it does upon tagging? Thanks, Somno (talk) 12:57, 15 February 2009 (UTC)
Automatic "Preview" instead of automatic "Save page"
When Twinkle edits a page, especially when adding a warning notice to a user's talk page, I would like to be able to edit the page myself, or change the edit summary, in addition to the automatic editing. (The first time I used Twinkle, I was astonished that it performed edits without getting my confirmation.) For example, if I go to a user's talk page, click "warn", and answer the questions twinkle asks, then Twinkle will edit the page using whatever information I have filled in. Instead of Twinkle actually submitting the edit (by the programmatic equivalent of the "Save page" button), I'd like it to instead do the equivalent of a "Preview", so that I can make my own extra changes to the page and/or the edit summary before pressing the "Save page" button. This should probably be configurable, so that people can choose to have certain types of edits be fully automatic and other types of edits use "Preview" instead. Perhaps a "Preview this edit: yes/no" option could be added to the set of questions Twinkle asks fo some edits. —AlanBarrett (talk) 17:44, 17 January 2009 (UTC)
- What you're asking for is a complete change in the way that Twinkle works, which most users will be extremely unhappy with. Unfortunately, it will not be done. Ioeth (talk contribs twinkle friendly) 14:29, 18 January 2009 (UTC)
- I thought that it would be a simple matter of parameters to a POST request, and the addition of a configuration option, not a complete change in how Twinkle works. Obviously people who prefer the existing way would choose not to use the new option (if it were implemented). —AlanBarrett (talk) 20:08, 25 January 2009 (UTC)
- I also would find this feature useful. -- OlEnglish (Talk) 21:44, 17 February 2009 (UTC)
Courtesy page blanking when applying db-attack
Under the CSD tab, have a second option right under "G10 - attack page". It could be called "G10 - attack page (blank article as a courtesy)", and all it would do is blank the article and add {{courtesy blanked}} along with adding {{db-attack}}. This would save a couple extra clicks to blank the page when appropriate, depending on the severity and subject of the attack. Thanks for considering this! — LinguistAtLarge • Talk 05:30, 23 February 2009 (UTC)
Wait for revert completion
To illustrate, I will use the names Editor1 (uses TW) and Editor2 (doesn't use TW). When reverting vandalism, TW usually takes longer to revert the vandalism than it does to bring up the talk page and add a warning. Often, Editor1 might not end up actually being the one who successfully reverts the vandalism but Editor1 will often get to the talk page first. In some instances, usually with an inexperienced Editor2, Editor2 will leave a duplicate warning on the vandal's talk page not realizing that someone else has already left a warning for the same vandalism. Is there a way to make TW wait until a successful revert before opening the talk page? In rare cases, when reverting vandalism to a user talk page and you want to leave a warning on the same talk page for the vandalism (rare, I know) TW opens the talk page before the revert so if you don't pay attention, you undo the revert when leaving the warning. -- Mufka (u) (t) (c) 00:53, 13 February 2009 (UTC)
- I'll see what I can do. Good suggestion! Ioeth (talk contribs twinkle friendly) 18:58, 13 February 2009 (UTC)
- Alright, I've changed the logic flow so that the users talk page will only be opened after a successful revert post to the server. Seems to work fine in testing, so let me know if you have any problems with it! Ioeth (talk contribs twinkle friendly) 19:14, 13 February 2009 (UTC)
- So far so good. -- Mufka (u) (t) (c) 22:20, 15 February 2009 (UTC)
- I did have the problem again here. Another editor placed the CSD tag and I ended up leaving the talk page notice. Maybe it's different in this case because it wasn't a revert, but it was a CSD tag. -- Mufka (u) (t) (c) 02:59, 25 February 2009 (UTC)
- So far so good. -- Mufka (u) (t) (c) 22:20, 15 February 2009 (UTC)
- Alright, I've changed the logic flow so that the users talk page will only be opened after a successful revert post to the server. Seems to work fine in testing, so let me know if you have any problems with it! Ioeth (talk contribs twinkle friendly) 19:14, 13 February 2009 (UTC)
← I've now undone that change since it's not working, and it was causing WT:TW/Bugs#TW-B-0259.
Ioeth, as I see it opening the talkpage in the onsuccess handler isn't enough since that handler is called on a successful load of the page, i.e. anything that returns HTTP 200, which is pretty much always except on a server error. I don't think that this RFA can be done without either checking the page history or probably by making the reversion with the API (although I'm not sure it has a return code for that case). --Amalthea 20:15, 25 February 2009 (UTC)
Every now and then, I try to use Twinkle to revert myself, but it bugs out. Huggle already allows you to self-revert (not from personal experience, but from what I've seen), so I wonder if Twinkle could be modified so that you could revert yourself. →Dyl@n620 23:16, 23 February 2009 (UTC)
- Works for me. How does it "bug out"? --Amalthea 00:53, 24 February 2009 (UTC)
Talk page vandalism and SineBot
I have noticed that attempts to revert long series of vandal-edits to Talk pages will often be stymied by the presence of SineBot (talk · contribs) in combination with Twinkle's tendency to treat the bot the same as any other user when figuring out how far it should revert. See this attempt that should have reverted these two extremely silly posts by Skool1 (talk · contribs), but that only zapped the latter one. Since SineBot was kind enough to sign the first of the two edits, my reversion stopped at that signature, and it was only because I was going through the vandal's contribs that I found the rest of the stupidity, for which I had to use an "undo" to revert.
Would it be possible, given a long string of edits by one user but broken up by SineBot signings, for Twinkle to treat the SineBot edits sandwiched between (and immediately following) the major editor's contributions (or "contributions," as the case may be) as part of that major editor's opus for the purposes of reversion? This would eliminate vandals' ability to hide earlier Talk page edits behind SineBot's protective screen, and it would get rid of all signs of the vandalism in one fell swoop, auto-generated signatures and all. --Dynaflow babble 22:47, 24 February 2009 (UTC)
- That's a good idea. From what I understand Twinkle should already think that if you revert SineBot, you actually want to revert the change right before and roll back accordingly. Ignoring interleaving SineBot edits shouldn't be hard. --Amalthea 12:45, 25 February 2009 (UTC)
Prod, AfD notification and welcome template
The welcome template should get automatically added with Prod and AfD notifications (I see it isn't yet [4]), just like it is with the speedy deletion notices[5]. —Magic.Wiki (talk) 18:55, 25 February 2009 (UTC)
- This is not really a Twinkle feature, it's a feature of the speedy deletion notification templates. I added that functionality to them following a discussion at WT:CSD, and I'm happy to add it to the PROD and AfD notification templates as well, but could you seek some consensus for that at WT:PROD and WT:AFD first please? --Amalthea 19:08, 25 February 2009 (UTC)
- Done, for
{{PRODWarning}}. I also change Huggle so that it will use the standard PROD warning from now on instead of its own. Huggle doesn't appear to be configured to allow XFDs currently, so I ignored
{{huggle/xfd}}for now. There are still a number of other notification templates for IFD, CFD, RFD, TFD and MFD that I haven't touched. They can too be extended, but the respective XFD talk pages should be asked first.
Cheers, Amalthea 14:03, 7 March 2009 (UTC)
- Done, for
Display last diff after a revert
After every revert, I always click on "last" for two reasons. It shows who actually completed the revert so I know if I should leave a warning (I see that the Wait for revert completion request above is problematic), and it allows me to see the results, especially when multiple edits are being reverted, sometimes revealing further vandalism which needs to be undone. It would be great if Twinkle had the option to automatically display the last diff after a revert. MANdARAX • XAЯAbИAM 22:25, 26 February 2009 (UTC)
I've actually gone back to using WP:ROLLBACK for reverts of vandalism, then using Twinkle for the warning (manually copying and pasting the article title). This is slightly less convenient than having Twinkle automatically fill in the title for the warning, but the rollback itself is much faster and more convenient for me. I've been using Twinkle for so long that I'd forgotten that the WP rollback does exactly what I wanted: tells me if my rollback was completed or failed, shows the diff, and doesn't waste time displaying the whole page. It would still be nice if Twinkle could do the same. mandarax • xɐɹɐpuɐɯ 10:16, 7 March 2009 (UTC)
- So something like Wikipedia talk:Twinkle/Archive 15#"Warn" as a button similar to Friendly's "welcome" feature would be helpful? --Amalthea 12:40, 7 March 2009 (UTC)
- I installed Friendly and started using SchuminWeb's very useful "welcome" trick. But, since that only works when a user's talk link is red, it would be wonderful if a [Warn] link was always available. For example, when I revert to a previous version, I step through all of the diffs and warn each of the users who contributed to the vandalism, and this would make it much easier. mandarax • xɐɹɐpuɐɯ 20:23, 8 March 2009 (UTC)
Sometimes when I'm prodding articles, I'd like to be able to use {{prod-nn}} instead of {{prod}}. Could Twinkle offer that as an option? Thanks! Dori (Talk • Contribs) 00:13, 5 March 2009 (UTC)
- It sure could. I'm not sure it's used often enough to earn one of the precious tab spots though. --Amalthea 13:04, 9 March 2009 (UTC)
(Accidental) misuse of CSD G1
A lot of Twinkle users are interpreting "Nonsense" as OR etc etc, when it does, in fact, mean "askhdajfsadfkasldgcxuvjn';##sd". Could we have the main heading "G1: Nonsense" reworded to try and prevent the extra burden on admins? - Jarry1250 (t, c) 17:44, 8 March 2009 (UTC)
- Done. I've also changed A1 to be more verbose: per I'm Spartacus!' survey the two appear to be the ones that are most often misapplied. I know I did when I first installed Twinkle – they often seemed to fit articles I was sure should be deleted. Maybe the more precise description will lessen that. --Amalthea 13:01, 9 March 2009 (UTC)
WP:DELSORT - I know this question was just archived, but there was no response. Are there any plans to add deletion sorting to XfDs? Because it's a pain to find the directory, search through until you find the correct one(s), copy & paste the template(s), and transclude the discussion on the page(s). This is a pain for the nominator, but it is really vital to bring discussions to the attention of people who are active in those areas. It usually means some wikignome or elf or banshee or whatever spends tons of time sifting through them all and doing this manually. ▫ JohnnyMrNinja 11:49, 11 March 2009 (UTC)
- Yes. But I can't currently do it, lacking the time.
I noticed that Dinoguy1000 posted some code on Ioeth's talk page a while ago, but I'm not sure how far that went. Dino? --Amalthea 12:59, 11 March 2009 (UTC)
- Aah, sorry for not seeing this before (this particular subpage wasn't on my watchlist). I've done *some* more work on this since then, which can be seen at User:Dinoguy1000/scripts/delsort.js (yeah, I moved it); however, a lack of time and Javascript knowhow have largely stalled my efforts. At some point, I intend to direct the folks at WP:DELSORT towards it and see if anyone there with some scripting know-how may be interested in helping out (and, now that I think about it, at the same time I may open a Twinkle bug report and/or feature request and see if I can't get any assistance that way). I may also spam a few user's talk pages while I'm at it, and see how long it takes to get yelled at. =) In any case, I've always been aiming towards having this implemented as a Twinkle module, hence why I posted about it on Ioeth's talk page. 「ダイノガイ千?!」(Dinoguy1000) 06:58, 17 March 2009 (UTC)
Add abuse filter block template to list of block templates
Template:Uw-afblock. Thanks! - Rjd0060 (talk) 04:15, 19 March 2009 (UTC)
Change G8 template
Using {{db-talk}} is too specific when tagging for G8, it should use the general {{csd-g8}} or prompt for a more specific one. Q T C 17:10, 19 March 2009 (UTC)
Option to not edit protected pages
I would like an option to have twinkle not edit protected pages. As an admin twinkle will just post warnings to talk pages and on images in articles without checking if it is protected. I want don't want to edit protected pages without realizing it. Thanks. Chillum 01:26, 21 March 2009 (UTC)
- Actually, I think the default behavior should be for Twinkle to halt with a warning when an admin tries to use it to edit a protected page (and just display a status message and continue on its merry way if the user isn't an admin). 「ダイノガイ千?!」(Dinoguy1000) 18:25, 21 March 2009 (UTC)
Yes, that would be fine too. Chillum 19:09, 21 March 2009 (UTC)
Allow reason to be entered for block templates
The ability to add the reason parameter to the {{uw-ublock}} message would be useful. -- Mufka (u) (t) (c) 12:26, 30 March 2009 (UTC)
Twinkle for IE
What is the status on creating an IE freindly version of twinkle?--Ipatrol (talk) 21:17, 24 March 2009 (UTC)
- Unchanged I'm afraid, since nobody is working on that. --Amalthea 11:43, 25 March 2009 (UTC)
Why? Why are we ignoring the users who use IE? Why have we not embarked on at least finding out what the problem is?--Ipatrol (talk) 19:18, 26 March 2009 (UTC)
- We? Feel free to embark.
Debugging javascript on IE is a pain, and I think my time is better (and more enjoyably) spent otherwise, so this task has rather low priority for me. I'd be delighted if you or someone else wants to have a look though. --Amalthea 22:51, 26 March 2009 (UTC)
I have been trying to debug TW, but I would like to request the help of someone a little better versed in JS to help. I have made some headway, but I do need someone to help me work on it.--Ipatrol (talk) 01:56, 27 March 2009 (UTC)
- You can post questions or problems both here and at WT:US. I personally have actually only little knowledge of the intricacies of JavaScript, but I can see what I can do. --Amalthea 09:17, 27 March 2009 (UTC)
I will create a page called User:Ipatrol/TwIEdebug to debug twinkle for IE. In the mean time, could an admin edit my monobook so I can see the revert to this revision button, but not the rollback button (I can use twinkle on my iPod touch.--Ipatrol (talk) 19:04, 27 March 2009 (UTC)
- ? It's not protected, you can do that yourself. --Amalthea 22:05, 27 March 2009 (UTC)
Yes, but I don't know anything about js. I also want a feature to add a tag at the top of an XFD to add the closure tages to a page's top and bottom, and the closing rationale.--Ipatrol (talk) 21:57, 1 April 2009 (UTC)
- There is the fact that Firefox works on every major OS and IE works only on Windows. It is only natural that the option everyone can use is given the most attention. Plus, writing JS for IE is a pain in the neck. Chillum 23:26, 1 April 2009 (UTC)
- I don't suppose anyone who hangs around here has, or knows of, a general-purpose XFD-detection script? (if not, we should bully one of the JS gurus into writing one for us *evul grin* ) 「ダイノガイ千?!」(Dinoguy1000) 18:31, 2 April 2009 (UTC)
- What would that do? --Amalthea 18:37, 2 April 2009 (UTC)
- Allow scripts which deal with XFD discussions in some way to call it and simply die if it doesn't return true (i.e. is a discussion page). Obviously, some customization would be necessary (if you only care about one type of discussion page, for example), but even the basic functionality would save lots of time and effort (and duplicated code between different scripts). 「ダイノガイ千?!」(Dinoguy1000) 20:46, 2 April 2009 (UTC)
- Err ... OK, but what does it do? --Amalthea 21:10, 2 April 2009 (UTC)
- Heh, should've known it still wouldn't be clear... =D Basically, the script would look at the current page, and return true if the page is an XFD discussion page, and false otherwise. A good version would also allow you to specify specific XFD areas (CFD, AFD, etc.) to check specifically for, ignoring others. 「ダイノガイ千?!」(Dinoguy1000) 21:28, 2 April 2009 (UTC)
- Err ... OK, but what does it do? --Amalthea 21:10, 2 April 2009 (UTC)
- Allow scripts which deal with XFD discussions in some way to call it and simply die if it doesn't return true (i.e. is a discussion page). Obviously, some customization would be necessary (if you only care about one type of discussion page, for example), but even the basic functionality would save lots of time and effort (and duplicated code between different scripts). 「ダイノガイ千?!」(Dinoguy1000) 20:46, 2 April 2009 (UTC)
- What would that do? --Amalthea 18:37, 2 April 2009 (UTC)
- I don't suppose anyone who hangs around here has, or knows of, a general-purpose XFD-detection script? (if not, we should bully one of the JS gurus into writing one for us *evul grin* ) 「ダイノガイ千?!」(Dinoguy1000) 18:31, 2 April 2009 (UTC)
- Ipatrol, I believe there are already a number of XfD closing scripts around. --Amalthea 21:12, 2 April 2009 (UTC)
I think that an idea to work on is a script to make adding morebits tabs and windows easier to those who don't know js. So for example, with that utility this could be inserted into my monobook:
<custtab>AddTab:Close; InNamespace:Wikipedia; OnPage:Articles for deletion +subpages; WindowOptions:()Close AFD=Actions? Add-{{s/ubst:a/t}}_[TextboxContents1]*#top*& Add-{{su/bst:a/b}}*#footer*;TextboxContensts:1=large&header?Closing rationale<nocode>:</nocode>; </custtab>
I admit is is somewhat verbouse, but it is simpiler than JavaScript, so it's like making a very high level programming language out of JavaScript.--Ipatrol (talk) 21:31, 2 April 2009 (UTC)
Parsing of SSP boxes for extra User: prefixes
It's happened to me a couple of times where I have spaced and/or copy and pasted User:xxxx into one of the suspected sockpuppet entry boxes and not noticed that you were supposed to omit the User: prefix. Of course then the action creates non existent user page User:User:xxxx to place the SSP tag on and notifies the correspondingly non existent User_talk:User:xxxx. It would be great if the dialog could parse for the User: prefix and either auto remove it or refuse to let you OK until they are removed to save having to go and manually move all the tags and messages, especially to prevent it creating user and talk pages for non existent users. Mfield (Oi!) 00:50, 4 April 2009 (UTC)
Image renaming
One thing that has made it difficult for me when moving free images to Wikimedia Commons is that it takes quite awhile to change names of images while moving them, since then every page which they are used on needs to be manually updated. I was wondering if another function could be added to Twinkle that would, when you are on an image description page, provide a "new name" link. Although this won't actually change the image's name, it would edit each page that the image is used on and change the link to the file to link to a new filename. This way, renaming an image while moving it to Commons will take virtually no additional time than just keeping the current name does. –Drilnoth (T • C) 23:21, 10 April 2009 (UTC)
- Is this still an issue with image redirects? They should work now, shouldn't they?
In Article Maintenance Tagging, there's a drop menu for notability to specify bios, among other things. Would be helpful if such a drop box or separate option were added for {{BLPunreferenced}}. لennavecia 16:53, 11 April 2009 (UTC)
- I've been wanting this myself... it shouldn't be hard to do. Actually, I could make the changes in my userspace and then someone with editprotected access could actually update it, if nobody else would like to spend the time. –Drilnoth (T • C) 17:16, 11 April 2009 (UTC)
Adding Sofixit
What about adding {{Sofixit}} under Single Issue Notices? --The New Mikemoral ♪♫ 07:46, 12 April 2009 (UTC)
- I guess it's up to an admin who see this, for now. --The New Mikemoral ♪♫ 04:05, 13 April 2009 (UTC)
- Well, give it a few hours and I'll probably be an admin who sees this. :) –Drilnoth (T • C) 12:32, 13 April 2009 (UTC)
- I guess it's up to an admin who see this, for now. --The New Mikemoral ♪♫ 04:05, 13 April 2009 (UTC)
(<--) Okay, that sound good. --The New Mikemoral ♪♫ 22:42, 17 April 2009 (UTC)
- I'd like to stick with uw-* notices in that dialog. From what I see it seems to mostly follow uw conventions already, but before adding it it should be renamed, and it should have a comment in the message pointing at the template ().
Otherwise Twinkle won't recognize whether that notice has been added before (lest it starts doing insane checks).
If you do that then I can add it. --Amalthea 09:10, 22 April 2009 (UTC)
- Done Template:Uw-sofixit, is the link to the the new template (I created a new template). Thanks for offering to add the template to Twinkle. --The New Mikemoral ♪♫ 22:58, 22 April 2009 (UTC)
- ... and I moved the original template over it. Things should really only live in one place, to keep changes focused, and if you do duplicate anything, you always have to make sure from where you're splitting it, for GFDL reasons. Otherwise the original contributors' content isn't attributed as required.
I've added {{Uw-sofixit}} to the single issue notices.
Amalthea 14:13, 23 April 2009 (UTC)
- ... and I moved the original template over it. Things should really only live in one place, to keep changes focused, and if you do duplicate anything, you always have to make sure from where you're splitting it, for GFDL reasons. Otherwise the original contributors' content isn't attributed as required.
Simple diffs in AIV reports
When clicking the "arv" tab and choosing the Vandalism option, one must type in, amongst other things, the title of the vandalised page, the
oldid of the vandalised version and of the last good version. This then produces "Page name (diff)" on WP:AIV. The problem is that most people using this feature will be finding vandalism through a watchlist or feed, most likely by clicking a diff to see the vandalism. Having to open the vandalised and good versions of the page and retrieve the
oldids seems like a waste of everyone's time (for the reporter, 3 pages opened, two copies and pastes; for the bot, having to assemble a diff out of two
oldids), when they could just copy the diff of the vandalism into Twinkle (for the reporter: one page opened, one copy/paste; for the bot, no diff assembly needed). So, I request that in addition to the "two page versions" option, there be added a "type the diff of the vandalism here" option. Skomorokh 15:56, 18 April 2009 (UTC)
- You're right, I always hated that too, and often built my own reports in the comments field. FWIW, you don't have to open all those pages though, if you take the vandalised revision ID from the diff link you already openened, and the previous revision was good, you can simply dump hat ID in the input field and leave the "last good revision" empty.
I agree that just having some text boxes where you can paste diff links is easier. If you're on the contributions page you can then very simply preview a diff with NAVPOP, and if you want to add it to the report you just drag&drop them into the text boxes. Amalthea 09:47, 22 April 2009 (UTC)
d-batch : option to not delete redirects
I just ran into a situation where I wanted to temporarily delete a bunch of things then restore them all (history merging busywork)... I didn't want it to delete all the redirects, but there doesn't seem to be an option to prevent this. –xeno talk 19:51, 24 April 2009 (UTC)
add additional box to CSD G3
I'd like it if there was an additional box for G3, specifically for hoaxes, using the {{db-hoax}} template. Sometimes it isn't clear exactly what you are trying to get at, since vandalism is such a wide spectrum, a little more specificity would be nice.--Terrillja talk 19:16, 6 May 2009 (UTC)
- Done. Amalthea 11:03, 7 May 2009 (UTC)
Log articles that I prod
The "watchProdPages" config option is nice, but I have way too many articles on my watchlist for that to be very useful. I would love a config option that would log all pages I prod to a sub-page of my userspace. For example,
TwinkleConfig.logProdPages = 'Prod'; // Name of your userspace page to log prodded articles to
which would log all pages I prod to User:LinguistAtLarge/Prod. It could be a simple chronological list of the articles I have prodded, along with the date perhaps. I would then be responsible for cleaning out old items from the list.
Sample list:
- Prodded article one — 04:05, 13 April 2009 (UTC)
- Prodded article two — 09:14, 14 April 2009 (UTC)
- Prodded article three — 20:27, 15 April 2009 (UTC)
This would be very helpful to keep track of prodded pages and follow up on them (if the prod is removed w/o good reason etc.). There could be additional safeguards, such as Twinkle would only write to the user's userspace, nowhere else, and you could ask the user to include an HTML comment on the page, such as , and if that comment is not there then don't write to the page. — LinguistAtLarge • Talk 18:31, 17 April 2009 (UTC)
- In case this doesn't get implemented, you might want to look at WP:WIKIMARK. It works pretty well. –xeno talk 18:34, 17 April 2009 (UTC)
- Thanks xeno, that looks useful as well. I'd still love for this to be implemented, since it would be quite convenient for me (and I suspect for others). — LinguistAtLarge • Talk 18:46, 17 April 2009 (UTC)
I threw a script together that extends Twinkle to implement this functionality. You can see it at User:LinguistAtLarge/twinkleprodlog.js Anyone can try it out if they want, just import that script and set the config variables in your monobook.js file.
@Amalthea -- I would love it if you would take a look at the script and include it in the official Twinkle release. It's basically just 3 additional config variables and a modification to the twinkleprod.callbacks.tagPage function. — LinguistAtLarge • Talk 23:01, 17 April 2009 (UTC)
Configuration vars (defaults shown below)
To enable logging of all the pages you propose for deletion, set this variable to the name of a sub-page in your user space where you want the pages to be logged to (REQUIRED)
TwinkleConfig.logProdPage = '';
If you want to change the format for each line of the log, you can to it here (for example if you want to format it as a list, table etc.) (OPTIONAL) (defaults to a list)
TwinkleConfig.logProdLineTemplate = "\*\[\[%PAGENAME%\]\] — %REASON% (%PRODTYPE%) — \~\~\~\~\~";
Set this to true to add new lines at the bottom of your log file, or false to add new lines to the top (OPTIONAL)
TwinkleConfig.logProdAddBottom = true;
- Nice! Haven't gotten around to do anything here yet, but I like it! Judging from the config options alone it's pretty similar to how I would have done it, cause it invites extending twinklespeedy and twinklexfd the same way. I'll try to add it till next week.
Cheers, Amalthea 09:17, 22 April 2009 (UTC)
- That's great news, thanks. If you implement it for Speedy and XfD as well (each with a separate log target), that would be wonderful. Thanks again! — LinguistAtLarge • Talk 04:06, 26 April 2009 (UTC)
- Actually, if you also implement such logging for speedy and XfD, it should allow logging to the same page (I do such tagging infrequently enough that a single page would suffice my needs). Therefore, you could probably get away with a
TwinkleConfig.logSpeedyProdXfdPagevariable which would replace individual
logSpeedyPage, and
logXfdPagevars. 「ダイノガイ千?!」(Dinoguy1000) 18:40, 28 April 2009 (UTC)
- Actually, if you also implement such logging for speedy and XfD, it should allow logging to the same page (I do such tagging infrequently enough that a single page would suffice my needs). Therefore, you could probably get away with a
- I think one log target variable per tagging method is easier. If they all point to the same page, then they all get logged at the same page. And yes, I haven't forgotten this, I'm just so darn slow.Amalthea 11:01, 8 May 2009 (UTC)
I see this was requested before, but I guess I'll ask again: would it be possible to enable support for {{db-reason}} in Twinkle? AnturiaethwrTalk 15:23, 6 May 2009 (UTC)
- It would. And I think I like it. It needs setting up an additional notification template first. Amalthea 11:01, 8 May 2009 (UTC)
Patrolling tagged pages
I don't use Twinkle, but I do tag new pages for deletion if it is eligible to do so, and it has struck me that nearly all the pages db-tagged by twinkle users remain unpatrolled, I normally just patrol them myself, and move on, but I don't think this would be to hard to fix? I am thoroughly naïve as far as scripts go, could some one very kindly put a little thought into this? Thanks, all the best, SpitfireTally-ho! 21:30, 10 April 2009 (UTC)
- I think that it does patrol pages, but if you are already at Special:NewPages when the article is tagged for speedy deletion, you'll still see the "mark this page as patrolled" tag. –Drilnoth (T • C) 23:16, 10 April 2009 (UTC)
- Exactly. There is a feature request at mediazilla that would allow Twinkle to always mark a page as patrolled in those cases, but until then it very simply can't. Amalthea 11:01, 8 May 2009 (UTC)
- I notice this section is marked as Resolved - however, I have observed that it does seem to mark as patrolled if the page has been accessed directly from Special:NewPages but if accessed from elsewhere or refreshed in any way it does not mark it. --ClubOranjeT 11:02, 29 May 2009 (UTC)
- Exactly. There is a feature request at mediazilla that would allow Twinkle to always mark a page as patrolled in those cases, but until then it very simply can't. Amalthea 11:01, 8 May 2009 (UTC)
Actually, I've changed my mind, it seems that, according to Amalthea, this cannot be changed until the next mediawiki upgrade? SpitfireTally-ho! 11:13, 29 May 2009 (UTC)
- I'm afraid so. And not only the next upgrade, but bugzilla:15936 needs to be fixed first. Amalthea 11:45, 29 May 2009 (UTC)
Function to replace instances of an image being deleted
Yeah, I really couldn't think of a decent title. Anyway, I was wondering if it would be possible to have an option when I'm deleting an image under WP:F8 to replace all the instances of the image under the old name to the new name/name at commons. Example: File:Foo.jpg on enwp is a duplicate of File:Bar.jpg on commons. Foo is used in a bunch of articles including Foobar. I'd like to be able to replace Foo.jpg with Bar.jpg in [[Foobar]] (as well as everywhere else) when I delete Foo. Possible? --Closedmouth (talk) 17:05, 2 May 2009 (UTC)
- That's similar to something Drilnoth asked above. Image redirects shoould work these days, isn't it easier to set one up instead? Amalthea 11:01, 8 May 2009 (UTC)
- I'm not sure, but I don't think they work to Commons files because technically the file on this end has been deleted. I'll have to test that, though. (Oh, and sorry about the dup request, I do that all the damn time :-/) --Closedmouth (talk) 06:06, 9 May 2009 (UTC)
- Well, I'll be damned, it does work. They're still being detected as broken redirects, though, and they act like them by not physically redirecting you to the target when you click on them, so I'll have to ping someone about that. Otherwise, problem solved. Huh. --Closedmouth (talk) 06:17, 9 May 2009 (UTC)
- Ugh, maybe not. --Closedmouth (talk) 07:24, 9 May 2009 (UTC)
- Pity. Of course, one could set one up at Commons, but it probably was renamed for a reason. Amalthea 12:12, 29 May 2009 (UTC)
CSD notifications
If TW is used to directly speedy delete articles shouldn't it inform users by default like it does normally when tagging? -- Mentifisto 08:52, 9 May 2009 (UTC)
- Yep, see discussion at User talk:SoWhy/Archive 14#Speedy deletion which you started. :) Amalthea 11:50, 29 May 2009 (UTC)
Add {{citation style}}
I'd like to see {{citation style}} added to twinkle. It covers a number of referencing issues in one handy tag and includes good links for more information and help.--RadioFan (talk) 16:51, 21 May 2009 (UTC)
- That would probably be WP:FRIENDLY, though, wouldn't it? DW, same people, I think. - Jarry1250 (t, c) 17:06, 21 May 2009 (UTC)
Can we have this as a single-issue notice, please? — This, that, and the other [talk] 07:50, 22 May 2009 (UTC)
- DoneAmalthea 11:49, 29 May 2009 (UTC)
This template is used to close requests for page protection at WP:RFPP. It has many confusing options and I often find myself referring to the template to get the syntax I want. Could someone add an "RFPP closer" to TWINKLE? Many thanks! --causa sui talk 02:39, 31 May 2009 (UTC)
Blatant promotion RfC results
The following changes were approved as consensus at the RfC:
- Update twinkle to include under the ARV (user reporting) function for Vandalism (AIV), a preloaded template for "Account is a promotion-only account", which expands into an AIV report of "This account is being used for only promotional purposes. ".
- This would be a check box, similar to the vandalism-only-account checkbox. Pretty easy one.
- Update twinkle to include under ARV a new category of "Select report type -> Conflict of Interest", which generates a report on WP:COI/N, functionality similar to current twinkle ARV tools. Instructions within twinkle should indicate that COI reports should be for more complex cases of COI.
- This is a slightly larger request. Let me know if you need some templates made for this or need help with the verbiage.
Gigs (talk) 01:04, 17 June 2009 (UTC)
- First part Done, see this edit for an example.
For the second part, it would be very useful if you could post the layout of such a COIN report here, and which options go into creating one. Amalthea 22:35, 4 July 2009 (UTC)
- Sure, something like
== [[User:badusername]] == {{userlinks|badusername}} Page that demonstrates the conflict of interest: [[<user input page>]]. <user input from comments box> ~~~~
So the UI for this would be one text entry field for the "page" that demonstrates the COI, which will be linked to in the report. This page could be an article or in User: space. Making this a separate, required field will reduce insufficient reports that lack detail about where the COI problem is going on. I can't think of any time where a page name couldn't be provided, but if one comes up, people can always make a COIN report the way they have been up until now.
The alternative would be to only have the "comments" box and rely on that alone, but like I said, I think we'd wind up seeing a lot of reports with not enough info on them.
Note that COIN wants new reports on the bottom of the page, so add new sections at the bottom. Gigs (talk) 02:55, 6 July 2009 (UTC)
Auto-add UAA Templates to UAA reports...
Sometimes I see a new username that may obviously be a role account (promotional), but the user hasn't made any edits yet. I'd like some way to add the UAA report, automatically appending the {{UAA|wt}} template as a comment to the report.
I attempted to manually add the template to a UAA report I'd made and got an edit conflict from an editor who agreed with me.
"Wait" might not be the only desired UAA template, though it's the only one I'd see meriting an automatic add. See Template:UAA for examples of what might be useful. Hopefully other Twinkle UAA reporters might comment here. --Tckma (talk) 16:15, 30 June 2009 (UTC)
- Why would you want to add a report and then reject the report yourself? It sounds like you want some way to add a name to HBC NameWatcherBot's "wait list" manually, rather than to UAA. The bot already has a feature for waiting and watching suspicious names, so a manual tag function for that would probably be possible, and would automate the waiting and watching part. Gigs (talk) 21:56, 6 July 2009 (UTC)
Add the Welcometest message to twinklewarn.js
Request to add the {{Welcometest}} message to twinklewarn.js.
To act as a more encouraging & informative alternative to {{uw-test1}}.
Ideally to be placed under "General note (1)" for ease of access and to promote its use. If not, or in addition, putting it under "Single issue notices" would be ok, too. -- Quiddity (talk) 01:02, 17 July 2009 (UTC) Perhaps a few more could be added from this short list, if anyone felt the urge.
Default DELSORT extension
Recently (last week), I discovered the Deletion sorting tool extension of twinkle. I've had Twinkle for about a year now, and just now discovering it was a disappointment because I could've used that tool for a while before then. So, could there be anyway to make that tool standard for anyone who uses Twinkle, and not just for people who add it separately. I think it would be a big help and useful for people. Thanks in advance. Tavix | Talk 19:01, 1 July 2009 (UTC)
- I've done a certain amount of work on my own version of the delsort script, because it doesn't seem like there are any other actively maintained scripts (including the one you pointed out). My ultimate goal was to get a reasonably flexible, robust script which could then be modified for inclusion directly with Twinkle, as you would like. Unfortunately, a lack of technical knowledge has largely stalled my efforts (even though there are a couple of improvements I could make to it right now, just by copying and modifying code from other scripts). 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 20:51, 1 July 2009 (UTC)
- Can this be made into a bug? I wouldn't want to irritate people, but how many times has DELSORT been brought up? At least it would give a central focus point that wouldn't be archived. I don't think there's any question as to whether Twinkle needs a proper built-in DELSORT tool. ▫ JohnnyMrNinja 05:25, 17 July 2009 (UTC)
- I've considered filing a bug report, but never done it. Probably because that means I'd have to run around and compile a list of links to relevant discussions and existing tools. =) 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 17:55, 17 July 2009 (UTC)
- Can this be made into a bug? I wouldn't want to irritate people, but how many times has DELSORT been brought up? At least it would give a central focus point that wouldn't be archived. I don't think there's any question as to whether Twinkle needs a proper built-in DELSORT tool. ▫ JohnnyMrNinja 05:25, 17 July 2009 (UTC)
More a heads-up than a full request, but since we've just created Template:uw-vgscope, I wondered if the devs would be interested in adding it as a single level notice on the warn tab. Enjoy. Greg Tyler (t • c) 18:47, 25 July 2009 (UTC)
{{db-attack}} should have the option of adding {{courtesy blanked}} under it.
Title says it all. ηoian ‡orever ηew ‡rontiers 05:01, 16 June 2009 (UTC)
- Just point out that blanking attack pages isn't a courtesy - it's essentially required. :) Ale_Jrbtalk 22:18, 27 June 2009 (UTC)
- The blanking is happening already. I'd think we should either always add {{courtesy blanked}}, or never. I don't really see the added value in offering the tagger a choice here. Amalthea 22:36, 4 July 2009 (UTC)
- I merely stated choice because I seem to remember TW having {{courtesy blanked}} before auto-added, and then removed (or maybe it was just a edit-conflict....) and I think having the template would be informative for those who view the page first without checking history on why {{db-attack}} was used instead of {{db-empty}}. ηoian ‡orever ηew ‡rontiers 21:37, 8 July 2009 (UTC)
- It now displays a "courtesy blanked" notice. Amalthea 14:46, 27 July 2009 (UTC)
- I merely stated choice because I seem to remember TW having {{courtesy blanked}} before auto-added, and then removed (or maybe it was just a edit-conflict....) and I think having the template would be informative for those who view the page first without checking history on why {{db-attack}} was used instead of {{db-empty}}. ηoian ‡orever ηew ‡rontiers 21:37, 8 July 2009 (UTC)
- The blanking is happening already. I'd think we should either always add {{courtesy blanked}}, or never. I don't really see the added value in offering the tagger a choice here. Amalthea 22:36, 4 July 2009 (UTC)
Category tag feature
Don't know if this would be technically realistic to implement, but it would be awesome if there was a capability to search for and add category tags through twinkle. - 2 ... says you, says me 17:07, 28 July 2009 (UTC)
Support for custom CSD-rationale
It would be nice if Twinkle could have support for {{db-reason}} and/or {{db-g6}} with the
|rationale= option.
Also, it would be helpful if a unpatrolled page could be marked as patrolled automatically when placing a prod. --MrStalker (talk) 12:30, 2 August 2009 (UTC)
- See also WP:TW/BUGS#312. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 21:43, 3 August 2009 (UTC)
Note for SPI cases
It would be really nice if the ARV dialogue for SPI could include a note asking people to report simple, non-extensive instances of vandalism to AIV. Sometimes SPI gets reports of very simple vandalism only involving two or three accounts, and that is really not what it is for. — Jake Wartenberg 04:52, 6 August 2009 (UTC)
Watching a user on ARV
I think there should be an option to watch someone's userpage when using ARV. This would allow the user to see what action was taken on the user via their watchlist. Triplestop x3 21:57, 12 August 2009 (UTC)
This would be a rather minor feature but why not add the ability to leave a talkback message in way similar to the way user warnings can be left? Kotiwalo (talk) 10:10, 16 August 2009 (UTC)
- WP:FRIENDLY does that already. AnturiaethwrTalk 16:16, 16 August 2009 (UTC)
support for template:merge
It would be nice to have the merge tag supported. It should prompt for the article the user is proposing redirection to (similar to how speedy deletion for copyvio works) and include a date parameter.--RadioFan (talk) 16:29, 16 July 2009 (UTC)
- I kind of feel that {{merge}} is too important to include in something like Twinkle. It's not just something you slap on an article, like you would with, say, {{orphan}}. You need to consider it strongly, start discussion about it on the relevant talk page. The fact that it takes such effort slows you down, which could be considered essential with merging. Greg Tyler (t • c) 23:21, 31 July 2009 (UTC)
- Merge is more important than XfD, or requires less discussion? Automating complicated processes isn't usually undesirable, and it increases the chances that such things will be discussed beforehand. Currently is is much easier to just merge without discussion. ▫ JohnnyMrNinja 19:19, 17 August 2009 (UTC)
- I echo JohnnyMrNinja's thoughts on the matter: Twinkle already automates the process of listing pages at XfD, as well as helping with a number of other hot-button areas (making ANI reports, requesting page protection, etc.). I think the addition of a merge-tagging module would be good. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 22:00, 17 August 2009 (UTC)
- Merge is more important than XfD, or requires less discussion? Automating complicated processes isn't usually undesirable, and it increases the chances that such things will be discussed beforehand. Currently is is much easier to just merge without discussion. ▫ JohnnyMrNinja 19:19, 17 August 2009 (UTC)
- On the other hand, I see too many incorrectly created merge templates applied to page. One way templating (with no link back), the talk page sections not created, etc. I totally get what you are saying about slowing people down, but sure would be nice if there was a way to semi-automate the various steps when someone is sure they want to merge stuff. —Willscrlt ( "Talk" ) 22:30, 8 August 2009 (UTC)
AFDM - Hiding Instructions
The folks over at the AFD template aisle have added a paramater to the AFDM template that Twinkle uses to suppress the help / instructions which show up in the AFD template by default. Can I politely suggest that twinkle implement this in the code to reduce the noise on the article page. Should be {{AFDM|help=off|whatever else...}} since Twinkle is automatically following those directions for us. Would be great if twinkle knew whether or not the posts to the AFD summary page and article specific pages had worked before it turned the help off. Thanks. 7 talk | Δ | 07:50, 21 July 2009 (UTC)
- Done, in parts. It required changing {{Afd}} and {{Afdx}} since those are used by Twinkle to prepare the {{AfDM}}, but now all AfD noms are passing through
That's really only a workaround though, the link will still be shown as a redlink since the MediaWiki caching issue can only be overcome by adding a rather arbitrary delay to Twinkle.
I also didn't add any logic to test whether the nomination was successful; that's really a seperate issue in that it should never happen in the first place, I'd rather invest the time (once I find it) to fix the underlying problem. Amalthea 10:19, 21 July 2009 (UTC)
- Great - thanks as always for the quick work! 7 talk | Δ | 10:29, 21 July 2009 (UTC)
- One issue which can cause it (I've only experienced it with TfDs, but it should affect other XfDs as well, I'd imagine) is if the system clock is off - Twinkle attempte to post to the list for the day according to the local computer clock, so there's potential for discussions to be posted to pages which have been finished for months, or to attempt to post to pages which haven't been created yet (in the latter case, though, Twinkle *does* report a problem). 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 21:00, 21 July 2009 (UTC)
- The required modification of {{afd}} has been undone, so this doesn't work anymore. See Template talk:Afd. Amalthea 23:00, 31 July 2009 (UTC)
- Works again. Amalthea 09:37, 18 August 2009 (UTC)
- The required modification of {{afd}} has been undone, so this doesn't work anymore. See Template talk:Afd. Amalthea 23:00, 31 July 2009 (UTC)
Cross-wiki support and customization
This may not be the most appropriate forum to discuss this, and it may already be answered somewhere else. I have searched through the archives here, and I never found anything very similar to this discussed here. So, forgive me if I am bringing up an old or sore subject.
I am setting up a new installation of MW 1.15, and I have installed the Gadgets extension. So far, I have been able to install Friendly as a gadget there, but it's rather en.wiki-centric (as is to be expected, naturally). I was setting out to install Twinkle in the same way, and I noticed that there is a lot more en.wiki-specific details hardcoded into its code.
Here are my thought/questions... Wouldn't it make more sense, be more maintainable, and easier to troubleshoot (and admittedly a big pain to initially implement!) if the en.wiki-specific details were modularized and moved out of the main codebase.
Here's a concrete example. Looking through the morebits.js file (the backbone of both Twinkle and friendly), there are only four problematic areas that I saw. The globals variables 'namespaces' and 'Namespace' are set to en.wiki's specific set of namespaces. In order to use this on any other wiki or language of Wikipedia, those namespaces have to be set to different values. While namespaces -2 through 99 are defined or reserved by the MW software, ns 100+ are potentially different on every site. At the very least, you could define ns -2 through 99 in the main code, but ns 100+ should be defined in a site-specific module. Additionally, 'Namespace' contains several English-specific and site-specific DEFINEd values, which are likely to be different on different sites, and are certainly different on several other language sites. Again, all of the MW-standard values could remain hard-coded within the main body of code, but the site-specific ones should be moved to a different module.
Another problem in morebits.js is with 'function ln'. I've not totally traced through the entire set of scripts to see how it is used, but the array index names seem to be site-specific (and rather cryptic at first glance, though understandable after a little study). As with the global variables already mentioned, it would seem that this should be modified somehow to make it more portable.
Here is a Twinkle-specific example (though Friendly is guilty of this, too). In twinklespeedy.js, there are many lines similar to this:
form.append( { type:'header', label:'General criteria' } ); form.append( { type: 'radio', name: 'csd', list: [ { label: 'G1: Patent nonsense. Pages consisting purely of incoherent text or gibberish with no meaningful content or history.', value: 'nonsense', tooltip: 'This does not include poor writing, partisan screeds, obscene remarks, vandalism, fictional material, material not in English, poorly translated material, implausible theories, or hoaxes' }, { label: 'G2: Test page', value: 'test', tooltip: 'e.g., "Can I really create a page here?"' }, { label: 'G3: Pure vandalism', value: 'vandalism', tooltip: 'Plain pure vandalism' },
As far as I can tell, this adds new options to the form for the various genera Speedy Deletion criteria on en.wiki. That's great. But it doesn't help when you are on a different site. For example, over at Commons or on fr.news, the criteria are likely different. On the new MW installation I am building, the criteria are much simpler (basically only two: off-topic, vandalism). With 20/20 hindsight, it is obvious now that these should never have been embedded within the main code of the module. The application logic (how to tag something for deletion regardless of the particular reason) should remain in the module, and all of the presentation layer (the labels, templates, etc. used on the site) should be moved into a different file.
How does this help on en.wiki? Well, just as we do with templates and documentation here, it separates the stuff that really impacts functionality (the template, on in Twinkle's case, the core application code) from the stuff that is not quite as critical (the documentation, or in Twinkles case, the site-specific presentation portion). If a great new template comes out, the presentation layer could be updated quickly and without impacting other sites using the core code. If the MW software is updated in a way that alters the user interface, one update to the core code would fix the problem for all wikis (though it might make the core MW-version-dependent at that point, but that's still fairly easy to accomplish).
Looking beyond en.wiki, the benefits of such reorganization of the code are even more impressive. Commons, Meta, de.wiki, ar.news, and Wikiversity would all benefit from the ease of use that Twinkle (and Friendly) provide for doing basic administrative tasks. It's why I want it on my own MW installation, too. So, here is how other sites could implement Twinkle.
- Create a MediaWiki:Gadgets-TwinkleLoader.js page
- That page include a line similar to this:
- That page include a line similar to this:
- Create a MediaWiki:Gadgets-TwinkleLocal.js page
- That page contains the site-specific presentation layer information.
- There should be a copy-paste generic example available that the local site admins can customize to match their unique settings.
- These are not overrides of default values, but the first time they are defined (saves bandwidth, improves page rendering speed, greatly reduces potential for global variable scope conflicts and problems if scripts load out of sequence [a problem I am having now trying to override Twinkle defaults]).
- Create an optional MediaWiki:Gadgets-TwinkleConfig.js page
- This holds the standard configuration settings described in the Twinkle docs.
To further improve the user experience, ease the burden on the Foundation's servers, and reduce bandwidth consumption, the User:AzaToth/twinklecore-min.js file should be in minified form. The editable, non-minified version could be stored at User:AzaToth/twinklecore.js.
'twinklecore.js', naturally, would be just the application core. It should include all the modules in a single file (better for cacheability and fewer HTTP requests). The modules could then be enabled or disabled by a configuration flag. This should also result in a slight performance improvement based on YUI's site optimization tips (see here).
Right now Twinkle and Friendly (and any other related tools) are legacy tools that are extremely difficult to port to other sites. That's not good coding practices, nor is it in the spirit of the MediaWiki software. Don't get me wrong—the tools are awesome and I love them! I'm just trying to figure out how we can roll them out to a much larger group of users that would also love to use them.
One final thought... Once the presentation is split out from the core application code, it might even be possible to craft an extension that handles much of the presentation portion for local site admins. All of the namespaces, thinking back to my first example, are defined in LocalSettngs.php. Why should the sysops have to figure those settings out and remember to update them every time they make changes in their LocalSettngs.php (it's a very rare occurrence here, but happens quite a lot when setting up a new wiki!). Perhaps the extension could analyze the namespaces and a parser hook could output the JavaScript code for the namespaces. Likewise, it might be possible to have all the templates within a given category automatically populate the form fields (like a hidden category called 'Cat:Twinkle XfD templates' that is specified by the local site admin). I don't know. These are just some random ideas about how the thing could possibly be extended and customized even more. But first, we would have to break the core app from its presentation layer.
I am not particularly strong in JavaScript programming (enough to tweak things without getting into too much trouble), and I am a decent PHP coder. If my skills would be of help, I'll do my best. I am annoyed when people come up with ideas, but don't offer to help (though many times offering a great idea without helping is better than not offering it at all). So let me know what you think and how I can help, if at all.
Since a redesign of the code could be very disruptive to en.wiki and the current user base, the code should probably be forked. I'd be willing to offer my wiki installation for testing and development purposes. We could probably also use test.wikipedia.org, too.
—Willscrlt ( "Talk" ) 22:27, 8 August 2009 (UTC)
- You're requesting several different things here: separation of platform/application from action/presentation, optimization of code, and auto-generation of configuration code.
The first one is something that should be looked at quite seriously, but it would require, I think, a complete rewrite of Twinkle and Friendly. Such a rewrite should then use the API and jQuery as a starting point, rather than upgrading to them from the current method of screen-scraping, since using the API from the beginning would let you do things you wouldn't be able to do via an upgrade without a huge amount of work (primarily, it would let you optimize the code in various ways that wouldn't be obvious through an upgrade). This one would definitely require a fork and extensive testing, but I think the end product would likely be more stable, robust, extensible, and portable than the current Twinkle and Friendly are.
Second, code optimization is something every programmer should have in the back of their minds while writing code. However, certain forms of minification should probably be avoided, such as packing everything into one file. This is because Twinkle and Friendly are developed and maintained by multiple people, and not everyone is going to know how to properly minify the files - or is going to know that such minification is even necessary.
Lastly, the configuration auto-generation is a very interesting idea, but I have no idea what its technical feasibility would be. If it is possible, though, it should be pursued separately from Twinkle and Friendly, so that it can be applied to other tools as well. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 21:55, 10 August 2009 (UTC)
- I'm going to read all this once I have a little more time. For now: Twinkle could certainly be rewritten to cope better with interprojectionalization (I22N?), but some parts of the logic will always have to be customized for the project at hand. For some random examples, ARV and XfD are pretty strongly intertwined with the layout of those areas here on en-wiki. Even the different XfD areas here on enwiki aren't standardized enough to use the same code for all, and it's much worse if one tries to have other projects in mind as well. Trying to extract those setups into metadata is going to be pretty difficult.
I for one would prefer an easier ways to break down the scripts and modularize the steps so that one could more easily rearrange them as required for other tasks or other projects.
Amalthea 21:48, 13 August 2009 (UTC)
- Of course, modularization is (probably) always a Good Thing™; it would seem to me that (further) modularization would be another aspect of a Twinkle/Friendly rewrite. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 22:06, 13 August 2009 (UTC)
- Since all codes are licensed under CC-BY-SA & GFDL, it's very simple for you to copy the whole repo (maybe some better words?) to your site and then localize them. For example, we've got Friendly on zhwiki and localized. It works really fine. And some functions of Twinkle (such as speedy and fluff) has been merged into Friendly on zhwiki (since I'm lazy to maintenance two document), these functions (including speedy, as you mentioned) work fine too. So just be bold to copy those code and localize them. You don't need to change the framework, just localize some array values will simply do. For example, speedy (Twinkle devs, forgive my renaming...). Best regards.--Jimmy Xu (talk) 07:43, 23 August 2009 (UTC)
- Of course, modularization is (probably) always a Good Thing™; it would seem to me that (further) modularization would be another aspect of a Twinkle/Friendly rewrite. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 22:06, 13 August 2009 (UTC)
Vector skin support
Currently, adding the script line to vector.js does absolutely nothing - it looks like Twinkle refuses to work with anything but Monobook. Please add support for the new Vector skin. --NetRolller 3D 23:31, 18 August 2009 (UTC)
- I suggest bypassing your browser cache, and having a look at WP:TW/DOC#Trouble if that doesn't work. FWIW, Twinkle works using the vector skin. You'll find the Twinkle links in the drop down menu. Amalthea 23:45, 18 August 2009 (UTC)
An option to instantly report page creator should be provided when tagging a spam page
Basically, if Twinkle is used to tag a new spam page for speedy deletion, it would be really convenient if Twinkle were to display a dialog box containing the page creator's username and ask if Twinkle should automatically report the page creator to UAA immediately after tagging the spam page. Such an improvement could save a good amount of time (and mouse clicks). SoCalSuperEagle (talk) 20:23, 20 August 2009 (UTC)
And just to add to the above, if a Twinkle user were to answer "yes" to the prompt (because the username in question is clearly a promotional username that matches whatever the page creator was trying to promote), the automatically-generated report at UAA should read something like "violation of username policy because it is a promotional username; user created the spam page (insert name of spam page)." SoCalSuperEagle (talk) 20:35, 20 August 2009 (UTC)
- AIV could also be added for attack pages/other vandalism. Triplestop x3 20:08, 26 August 2009 (UTC)
I'd like to propose an option on the "warn" tab to subst the warning template {{uw-resume}} to a user's talk page.
When I come across a resume or CV during new page patrolling, I typically mark it for CSD under A7, unremarkable person. Would it be possible to add this as an option instead of the standard warning when so marking an article? Tckma (talk) 13:42, 26 August 2009 (UTC)
SPI notification
Over at WP:SPI#Evidence and SPI case guidelines, it states: Notification is not mandatory, and may, in some instances, lead to further disruption or provide a sockpuppeteer with guidance on how to avoid detection. Considering this, wouldn't it be desirable to add some sort of check box to have the option to avoid notifying suspected sockpuppeters? — Σxplicit 05:54, 3 September 2009 (UTC)
Customizing color of rollback links
I recently started using some parts of Twinkle and think it is a great tool, but I really don't like the colors of revert links. I noticed that these colors are in inline CSS. My request is to add either
classes or
ids to these elements (e.g.
<span style="color: SaddleBrown;">restore this version</span>), so that me and other users can change their appearance in user CSS. Thanks. Svick (talk) 15:09, 18 September 2009 (UTC)
Twinkle and rollback
Hello, can Twinkle be linked to rollback so that users who have rollback permission can revert vandalism faster and still be able to leave warnings semi-automatically? Thanks. LovesMacs (talk) 21:15, 22 September 2009 (UTC)
- Isn't that what the red "vandalism" link is for? ;) 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 22:26, 22 September 2009 (UTC)
- Yes, but it's not integrated in to the Wikipedia rollback feature yet. Ioeth (talk contribs twinkle friendly) 22:29, 22 September 2009 (UTC)
- Oh... yeah, that makes sense. ^_^;; *misread first comment* 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 17:37, 23 September 2009 (UTC)
- Yes, but it's not integrated in to the Wikipedia rollback feature yet. Ioeth (talk contribs twinkle friendly) 22:29, 22 September 2009 (UTC)
Reporting to AIV
The option "Evidently a vandalism-only account" (in the AIV reporting form) is disabled on IP talk pages. I think an option such as "Long term vandal" should be there to report obvious IP vandals such as H.A.G.G.E.R/Grawp to AIV without warning them at all. —SpaceFlight89 07:50, 26 September 2009 (UTC)
Watchlist undo/rollback
It would be nice to have the same [[rollback]] [[vandalisim]] links on Special:Watchlist that are currently on Special:Contributions. Is this only enabled for users with rollback privileges? I use popups/undo currently, but it can be really slow to load the page editing window. The TW direct interface is much faster. UncleDouggie (talk) 04:55, 27 September 2009 (UTC)
Userification of more blatant autobios
Something that might be nice would be a script to: check that a page has just one author, move the page to their userpage if blank, request speedy deletion (R2) of the subsequent redirect, and leave a message on the user's talk page explaining what's been done. If the userpage exists, could either append the details in the page, do nothing, or fall back to nominating for CSD. Might mean more of these get done, as at the moment it's much faster to request CSD A7 - justified but more bitey for newbies who just don't quite get it. Many thanks Pseudomonas(talk) 10:33, 28 September 2009 (UTC)
Please add {{reqinfobox}} to the tag tab of Twinkle. Thank you. Btilm 02:22, 5 October 2009 (UTC)
- Twinkle doesn't add the Tag tab, Friendly does. ;) 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 19:55, 5 October 2009 (UTC)
userpages of blocked users as a choice for page protection reason
There is no appropriate choice for page protection of a blocked user's user page. Can the user talk selection be modified to include both user talk and user pages?--Doug.(talk • contribs) 08:23, 12 October 2009 (UTC)
- OK, there's no reason for that, I wasn't paying attention to the fact that that's a custom protection template to show why a usertalk page is protected. Never mind.--Doug.(talk • contribs) 13:48, 12 October 2009 (UTC)
Rationale option for all CSDs
I've noticed that for certain CSD tags there's a popup requesting rationale. Could there be the option to enter rationale for all the CSD tags? Perhaps a checkbox in the window where you choose your criteria, that would cause a popup? I usually find myself wanting to add rationale, and having to edit that in manually after Twinkle is done. Lemme know what you think. Thanks! Equazcion (talk) 02:28, 20 October 2009 (UTC)
{New unreviewed article} template suggestion
Can twinkle remove {{New unreviewed article}} templates when adding speedy deletion tags to articles? --Pontificalibus (talk) 11:24, 20 October 2009 (UTC)
AfD creation
Having ignored Twinkle for years, I have just discovered how good it is at AfD nominations. One tiny suggestion: when it updates Wikipedia:Articles for deletion/Log/<date> instead of an edit summary of "Adding Wikipedia:Articles for deletion/<article name>" can we just have "Adding [[<article name>]].". The "Wikipedia:Articles for deletion/" is implicit! The advantage is, that when I review my contributions a week later, I can see from the colour of the link what the result has been - like this. — RHaworth (talk · contribs) 16:55, 23 October 2009 (UTC)
Tool for CAT:TEMP
Similar to the Traverse image category tool, it could show the talk page of the user in question (To verify a block notice was added), the block log for that user (To ensure that the user is actually blocked), and the page history (To check for any appeals and for when the last edit was) and then it would have an option to delete or ignore, it would then move onto the next page, etc. CAT:TEMP currently has over 27000 pages in it sense the bot that used to clean it out stopped running and this could make cleaning out the Category much easier. Thanks and All the Best, Mifter (talk) 22:27, 8 November 2009 (UTC)
- Any such tool needs to be very carefully designed to ensure sock pages are not deleted, they are often (I'd say most of the 27000) mis-categorized into CAT:TEMP. They are subject to WP:SOCK policy and are not deleted. I think there was a bot that was clearing the cat and it was stopped when this issue was realized by enough people. It's why the cat should generally be cleared by slow manual examination.--Doug.(talk • contribs) 13:45, 11 November 2009 (UTC)
- I can tell you through personal experience that about 1% of the pages in that cat shouldn't be, it's really not as bad as people think. I've deleted several thousand and had two complaints, both easily rectified mistakes on my part. A tool designed specifically for the job would be very handy, as AWB is designed for editing, not deleting. --Closedmouth (talk) 21:54, 11 November 2009 (UTC)
WP:CONTESTED procedure
Hi. As it is useful to add PRODs, often it is also useful to contest them -something I happen to do on a regular basis. It would be extremly nice if the WP:CONTESTED procedure -which I admit I don't follow 100% now because it is very time consuming now if contesting several PRODs one after another (I usually add an empty oldprodfull tag, without date etc.)- could be automated. Thanks! --Cyclopiatalk 14:59, 10 November 2009 (UTC)
- Comment Wikipedia:Dazzle! currently has this feature, and it works fine side by side with Twinkle, Friendly, etc. And I personally fine Dazzle useful for the features that TW doen't have. Best, Mifter (talk) 00:21, 11 November 2009 (UTC)
Could an option for Twinkle's (and Friendly's) tabs to be listed in a separate dropdown menu be added? This is spurred by Wikipedia:Dazzle!/News#2009-10-22: New vector tab functionality, in case you're wondering. 「ダイノガイ千?!」? · Talk⇒Dinoguy1000 18:39, 23 October 2009 (UTC)
- Following up on this, could Twinkle please appear as a drop down in the Monobook skin? Gary King (talk) 22:57, 18 November 2009 (UTC)
Add support for {{db}}
The barebones {{db}} template is not supported by Twinkle's csd functionality. Any chance of this being added? — This, that, and the other (talk) 10:16, 19 November 2009 (UTC)
I would like to be able to define in my monobook.js a default PROD reason. I tend to use "no evidence of notability" a lot and it would be nice if it could pop up automatically. — RHaworth (talk · contribs) 17:02, 23 October 2009 (UTC)
- OK, added that functionality. I'm not sure if you're still watching so I've gone ahead and made the change to your vector.js right away, hope you don't mind. Goes without saying to not become lazy with this feature and still think about your PROD reasons before submitting. Cheers, Amalthea 00:15, 30 November 2009 (UTC)
Hey, I sent you a message on IRC, but I'm just letting you know that a new CSD criteria, WP:A10, has been implemented, and hence
{{db-a10}} may need to be incorporated into Twinkle. Thanks in advance, \ Backslash Forwardslash / (talk) 06:09, 29 November 2009 (UTC)
- Who is "you"? I was waiting to see if the "Where do we stand?" goes anywhere. Seems stable enough though. Amalthea 12:31, 29 November 2009 (UTC)
- I sent AzaToth a message, perhaps I should've said who. :) \ Backslash Forwardslash / (talk) 12:41, 29 November 2009 (UTC)
I'd like an option that will remove {{deleteable image-caption}} from linked pages/articles where a specfic image is used.
This is so that when the issues that caused an image to be tagged are resolved, I don't have to manually find and remove all the {{deleteable image-caption}} s manually.
Thanks Sfan00 IMG (talk) 15:12, 28 November 2009 (UTC)
- There used to be a bot for that, but the bot op is MIA. I can see whether I can get it going again. Amalthea 12:32, 29 November 2009 (UTC)
- Any update on what happened to the bot? Sfan00 IMG (talk) 23:42, 12 December 2009 (UTC)
- Afraid not. I've asked at WP:BOTREQ whether someone would be willing to take over the task. Amalthea 16:47, 17 December 2009 (UTC)
- Any update on what happened to the bot? Sfan00 IMG (talk) 23:42, 12 December 2009 (UTC)
Marking as patrolled after PRODding
I just noticed this, but pages marked for speedy deletion get marked as patrolled by default, but the same does not happen when an article is PRODded. Can that be added in there, please? MuZemike 02:37, 18 December 2009 (UTC)
Another warning template
Would it be possible to add {{uw-coi-username}} to the single issue
notices warnings for warning users? It would be helpful with my new page patrolling when I come across a borderline promotional username. Thanks, Ks0stm (T•C•G) 13:20, 23 December 2009 (UTC)
Yet another warning template
I recently created the {{uw-consensus1}} warning series after an issue raised in #wikipedia-en-help. I thought you might want to know about the template in case you want to add it in to Twinkle's set of templates. It's not directly targeted at vandalism, however, like some of the other templates Twinkle uses, it can be quite useful for new users making edits that are going to be reverted due to disputes. --Shirik (talk) 20:44, 28 December 2009 (UTC)
db-move with reasoning
{{db-move}} does not work (i.e., not in CAT:CSD) unless both the move from page and the reasoning are provided. Please provide in the UI. And for that matter, any other templates that require it (I'm not aware of them). Magog the Ogre (talk) 23:38, 29 December 2009 (UTC)
Image Tagging request
Hi there! First, let me thank you for maintaining such a great tool. Secondly, I would like to request that the no source AND no license image tagging template be added to the di tab on images, along with its user talk notice. It's a convenient tag for images that are lacking both. Thanks, Nick—Contact/Contribs 08:36, 4 January 2010 (UTC)
Twinkle should ask for pagename and reason when tagging for {{db-move}}
The {{db-move}} template now requires two parameters:
- the pagename from where a page should be moved
- the reason for the move
- However, Twinkle doesn't want to know that and then adds an empty template with errors (example). It would be good if Twinkle asks for both, possibly as an alert box like with CSD F8, where it asks for the filename on Commons. Thank you, --The Evil IP address (talk) 17:22, 11 January 2010 (UTC)
- He he I just submitted this one above. Magog the Ogre (talk) 03:39, 12 January 2010 (UTC)
Looking for a one-click button to clear all content and place {{indef}} tag when in User: or User Talk: namespaces in line with WP:DENY. Users tend to go away once the template is placed on their user and talk page in my experience and stop screwing with comments left there. Something akin to the new blanking for attack pages, just instead add the indef template, the code should pretty much already be there.--Terrillja talk 04:37, 17 January 2010 (UTC)
Template Suggestion
Hello. Skier Dude and I have created a set of standard multi-level warning templates for warning users about repeatedly uploading files missing copyright information:
Would it be possible to implement them into Twinkle? Thanks in advance, FASTILY (TALK) 03:35, 22 January 2010 (UTC)
Unarchived request - Another warning template
Would it be possible to add {{uw-coi-username}} to the single issue
notices warnings for warning users? It would be helpful with my new page patrolling when I come across a borderline promotional username. Thanks, Ks0stm (T•C•G) 13:20, 23 December 2009 (UTC)
blacklist and copyvios
A user pasted a page copied verbatim from stores.lulu.com. I tried to CSD-tag it as a copyvio using Twinkle but it failed silently, repeatedly; only after trying to do it manually did I realise that the spam blacklist was preventing submission. Would it be possible for this sort of thing to generate an obvious error message? Pseudomonas(talk) 13:06, 4 February 2010 (UTC)
- This is a known problem with Twinkle. Please see TW-B-36. Ioeth (talk contribs twinkle friendly) 14:45, 4 February 2010 (UTC)
I've been finding images that have been tagged for commons but have issues.
Thus if an image is tagged for any of the di type things like no licence etc, any tag saying it should be moved to commons should be removed.
Sfan00 IMG (talk) 20:53, 7 February 2010 (UTC)
Option to tag an image as conflicted-license informing uploader
Images on wikipedia can't have both a 'free' and 'un-free' license, barring a few well known and understood exceptions.
Therefore an option to tag an image as 'conflicted' and inform the uploader would be appreciated. (There are templates for both the File namespace page and uploaders talk page available).
Sfan00 IMG (talk) 20:53, 7 February 2010 (UTC)
Hi: Is there any chance support for De-prodding could be made available? Currently, the de-prodding process consists of: removing the prod (and leaving an edit summary explaining why), putting an appropriate {{oldprodfull}} on the talk page, and putting an appropriate template (such as {{Deprod}} or one of its near relations) on the page of the prodding editor. Doing all this manually is getting to be a bit of a pain. Thanks, RayTalk 15:35, 24 January 2010 (UTC)
- on the subject of prodding and prod related activities I would like to see a {{prod-2}} feature, it would be really helpful for prod patrollers. andyzweb (talk) 01:03, 31 January 2010 (UTC)
- The PROD function performs a PROD2 if a PROD is already present.--Pontificalibus (talk) 13:56, 18 February 2010 (UTC)
3RR Warning
Unless I missed it, why is there no warning for edit waring? Even just Template:Uw-3rr would be sufficient. CTJF83 chat 20:51, 9 February 2010 (UTC)
{{uw-3rr}}is under "Single-issue notices." AnturiaethwrTalk 20:58, 9 February 2010 (UTC)
- Well, I'll be damned, thanks. CTJF83 chat 21:57, 9 February 2010 (UTC)
- No problem. AnturiaethwrTalk 02:11, 10 February 2010 (UTC)
- Well, I'll be damned, thanks. CTJF83 chat 21:57, 9 February 2010 (UTC)
Add support for {{db}}
The barebones {{db}} template is not supported by Twinkle's csd functionality. Any chance of this being added? — This, that, and the other (talk) 10:16, 19 November 2009 (UTC)
- De-archiving. — This, that, and the other (talk) 06:52, 13 January 2010 (UTC)
- If you're using that template, are you doing so because none of the criteria match, or because you want to pass in additional information? Amalthea 10:16, 13 January 2010 (UTC)
- It is often very useful for when you know at least one CSD criterion matches, but you're not sure precisely which one; or if two or more criteria match; or if an explanation is warranted. Whatever the case, it should still be made available. — This, that, and the other (talk) 07:08, 29 January 2010 (UTC)
- Yes, I was just going to ask for this. Often a page is pasted from a company's web page, making it a copyvio AND blatant advertising AND db-corp, for instance (tagging just copyvio leads to it being rewritten in the editor's own words, only to be re-deleted under one of the other criteria). Another common case is the indecisive border between incoherent and hoax; yet another is something that is certainly a non-notable person and possibly negative enough to count as an attack page (say, something that's positive but obviously sarcastic) Pseudomonas(talk) 12:37, 4 February 2010 (UTC)
- It is often very useful for when you know at least one CSD criterion matches, but you're not sure precisely which one; or if two or more criteria match; or if an explanation is warranted. Whatever the case, it should still be made available. — This, that, and the other (talk) 07:08, 29 January 2010 (UTC)
- If you're using that template, are you doing so because none of the criteria match, or because you want to pass in additional information? Amalthea 10:16, 13 January 2010 (UTC)
AfD closing
Is it possible to make it so closing AfDs is faster and quicker like nominating them? Such as posting {{subst:at}} '''RESULT''' ~~~~, removing the AfD notice from the article page, and noting the results on the article talk page...also deleting the page for admins. CTJF83 GoUSA 22:31, 23 February 2010 (UTC)
- There are already scripts that do that. User:Mr.Z-man/closeAFD for example. Amalthea 22:51, 23 February 2010 (UTC)
The outcome of Wikipedia:Requests for comment/userfication, a while back now, was (I think) to go ahead with adding userfication of articles to Twinkle (admin access only) and incubation (all editors). How difficult is it to do that? Whatever the answer, can someone volunteer? Rd232 talk 18:37, 2 March 2010 (UTC)
Add another template
Can we have {{subst:uw-talkinarticle}} added? This would be useful in cases where it's obvious the editor isn't familiar with using talk pages and isn't really vandalizing. Thanks! ···日本穣? · 投稿 · Talk to Nihonjoe 08:29, 4 March 2010 (UTC)
Multiple AfDs
Can you make it so it is possible to nominate more than one related article for AfD at a time? CTJF83 chat 06:20, 6 March 2010 (UTC)
Propose merge
A script that facilitate propsing article merge. Sole Soul (talk) 05:49, 9 March 2010 (UTC)
Is there a way to make Twinkle automatically not warn for XFDs in certain situations? I would say the following situations would be applicable:
- The article creator has a {{retired}} on his/her user and/or user talk page;
- The article creator has not edited in x months (9? 12?);
- The article creator is an IP address (IP addresses haven't been allowed to create articles in ages);
- The article creator has been indefinitely blocked.
All the time, I find myself warning a blocked, vanished or retired user with Twinkle. Is there any way to stop that? Ten Pound Hammer, his otters and a clue-bat • (Many otters • One bat • One hammer) 14:56, 25 February 2010 (UTC)
- Indeed, hammer has a point. --JokerXtreme (talk) 17:31, 4 March 2010 (UTC)
- I want to add, don't warn creator if the creator is the nominator. Don't warn yourself that is. --JokerXtreme (talk) 10:30, 23 March 2010 (UTC)
Tfd needs updating
Hi there! There have been some changes in the Tfd template. Tfd-inline functionality has been incorporated to Tdf and other features were included too. You can see the changes at the documentation:Template:Tfd
If you need something, just make a topic at Tfd:talk or contact me. --JokerXtreme (talk) 17:30, 4 March 2010 (UTC)
- Done. But I didn't check any new features. Amalthea 10:12, 23 March 2010 (UTC)
- Ok, thanx. Check the other types too when you can. It would be nice to have a drop down menu to select a notification type from. --JokerXtreme (talk) 10:25, 23 March 2010 (UTC)
Hi, it would be very helpful if Twinkle would automatically remove {{new unreviewed article}} (or {{userspace draft}} when used in mainspace, which then displays the same thing) when appropriate actions are performed. The new article tag is supposed to be removed when someone other than the creator reviews it and if necessary tags for cleanup - but often the new article tag is left in place. Actions that should remove the tag: any Article Issues tag (notability etc); PROD; AFD, CSD. Rd232 talk 15:50, 14 March 2010 (UTC)
- Done: The scripts remove {{New unreviewed article}} and {{Userspace draft}} when prodding, SDing, and issue-tagging an article, and AfDing will in addition remove {{dated prod}} and {{prod2}} and ask whether to remove (db-\w*|delete|hangon) as well. Amalthea 16:21, 26 March 2010 (UTC)
Could you add some form of standardise templates for "Hello X, thanks for your contribution to Wikipedia! Please remember that articles must be referenced. Thanks, [username]"? Ironholds (talk) 14:53, 4 April 2010 (UTC)
- Shouldn't we add them as part of the uw- project first? WT:UW Gigs (talk) 16:09, 5 April 2010 (UTC)
Additional Template
Please add {{uw-badlistentry}} to the list of available single issue notice templates. I seem to run across these issues a lot. Thanks! Cptmurdok (talk) 19:10, 5 April 2010 (UTC)
Add CSD criteria?
Hi there. Thanks in advance for taking the time to review my request :). Is there any way that we could get {{db-animal}} added as one of the specialized A7 criteria? I've yet to use it, but it seems rather useful! Cheers, Nick—Contact/Contribs 04:22, 13 March 2010 (UTC)
- So, I went to the template page after leaving this request and see that its tagged as a template that Twinkle uses...but since mine doesn't seem to have it, I'm not sure what to make of that. I'm pretty sure I have the most recent version and all, since I have it enabled via preferences. Perhaps the tag on the template page is wrong, or I'm missing it somehow... --Nick—Contact/Contribs 04:23, 13 March 2010 (UTC)
- I've noticed this myself. I don't know what the problem is, but I have an idea. First, I think it needs to be hard-coded in for Twinkle to recognize it. Second, it needs a warning that's compatible with Twinkle - if I'm not incorrect, this is the {{Db-csd-notice-custom}} series. No sub-template exists for A7.5, which would refer to animals. I'm halfway through creating it myself, using the same framework as the other ones. —LedgendGamer 19:32, 20 March 2010 (UTC)
- Okay, I've created {{db-animal-notice}} and Template:Db-A7.5-notice. I think all we need now is for it to be hard-coded into Twinkle's set of tags and notices. I really hope I didn't break anything. —LedgendGamer 19:49, 20 March 2010 (UTC)
- Is that getting enough use to warrant the additional entry? Seems a bit obscure. Amalthea 12:53, 13 April 2010 (UTC)
- Okay, I've created {{db-animal-notice}} and Template:Db-A7.5-notice. I think all we need now is for it to be hard-coded into Twinkle's set of tags and notices. I really hope I didn't break anything. —LedgendGamer 19:49, 20 March 2010 (UTC)
- I've noticed this myself. I don't know what the problem is, but I have an idea. First, I think it needs to be hard-coded in for Twinkle to recognize it. Second, it needs a warning that's compatible with Twinkle - if I'm not incorrect, this is the {{Db-csd-notice-custom}} series. No sub-template exists for A7.5, which would refer to animals. I'm halfway through creating it myself, using the same framework as the other ones. —LedgendGamer 19:32, 20 March 2010 (UTC)
BLP Prod
As NW noted below, the BLP prod is pretty much ready to go. Getting this in twinkle is going to be critical to its wide-spread acceptance. Considering that this is a high profile issue, this should be considered a high priority request.
- Under the PROD tab dialog, a drop down should be given to select "BLP Prod", retaining normal prod as the default.
- The "reason" field should disappear, since the reason is always the same, it's an unsourced BLP created after March 18, 2010.
- Upon submission, Twinkle should check to ensure that the article was indeed created after March 18,2010. If it wasn't, then abort everything.
- Subst
{{Prod blp}}on the article at the top
- Subst
{{ProdwarningBLP}}on the article creator's talk page at the bottom
(If anyone has a different idea about how it should work, feel free to edit this) Gigs (talk) 13:18, 31 March 2010 (UTC)
- Well, Twinkle is prepared to use it, seeing that it's highly likely to come sooner or later. Currently only shows a teaser (you might need to bypass your browser cache), unless you use the secret config option – don't use it yet though, as far as I can tell this hes yet to be introduced into WP:DELPOL. It'll probably be hard to miss when this changes, but feel free to leave me a short notice once it does so that I can enable it for all.
Amalthea 19:18, 1 April 2010 (UTC)
- Oh, and Twinkle won't prevent you from sticking this on an article that existed before March 18, because you might actually want to do that if a redirect was turned into an unsourced BLP, and the redirected existed before that date. It will display a notice instead. Could be turned into a more aggressive dialog that needs to be confirmed before it goes through with it. Amalthea 20:25, 1 April 2010 (UTC)
- I think we will probably want the confirmation dialog, if you don't want to refuse it entirely. The March 18th date is kind of a surprising restriction. As time goes on, less and less BLPs will hit that restriction just from natural turnover, so slapping them in the face with it until it's widely known wouldn't be a bad thing. Gigs (talk) 16:59, 2 April 2010 (UTC)
- Just noting here that it's not ready to go, and is still being discussed. Input welcome at Wikipedia talk:Proposed deletion of biographies of living people. SlimVirgin talk contribs 22:23, 2 April 2010 (UTC)
- Yeah I know, I'm waiting for it to become somewhat stable before I turn it on. By the way, I believe you are needlessly concerned, as far as I always understood the proposal it's an additional criterion for deletion, and does not touch on anything we have, pretty much as WereSpielChequers said. :)
Cheers, Amalthea 23:36, 2 April 2010 (UTC)
- Amalthea, I don't know how much you've been watching the debate, but I think things have calmed down enough that we can turn this on in Twinkle. A couple more people expressed concerns about enforcing the cutoff date, so I think we'll want that confirmation dialog instead of a passing note. Let me know if I can be of assistance. Gigs (talk) 16:07, 5 April 2010 (UTC)
The test is actually a bit too lazy, and will produce a false positive if an article was last undeleted past March 18 (since it gets a new article id then). I'm thinking this will happen rarely enough (moves are OK), otherwise it'd require an additional server request to get the timestamp of the first revision (which isn't necessarily the oldest either once Special:Import comes into play, I think). Amalthea 14:38, 6 April 2010 (UTC)
OK, turned it on for all, including the additional confirmation box for articles found to be created before March 18.
- OK, turned it on for all, including the additional confirmation box for articles found to be created before March 18.
- Amalthea, I don't know how much you've been watching the debate, but I think things have calmed down enough that we can turn this on in Twinkle. A couple more people expressed concerns about enforcing the cutoff date, so I think we'll want that confirmation dialog instead of a passing note. Let me know if I can be of assistance. Gigs (talk) 16:07, 5 April 2010 (UTC)
- Yeah I know, I'm waiting for it to become somewhat stable before I turn it on. By the way, I believe you are needlessly concerned, as far as I always understood the proposal it's an additional criterion for deletion, and does not touch on anything we have, pretty much as WereSpielChequers said. :)
- Just noting here that it's not ready to go, and is still being discussed. Input welcome at Wikipedia talk:Proposed deletion of biographies of living people. SlimVirgin talk contribs 22:23, 2 April 2010 (UTC)
Page blanking
Hey, Twinkle is a very useful tool and you should be proud.
Is it possible to implement a way for Twinkle to be able to detect if the author of a page has blanked it but not tagged the page after you loaded it but before you put the appropriate tag on the page so that I don't realise that the author has blanked a page but Twinkle can give a warning telling me that the author has blanked the page so that I will know and I won't go tagging the article as vandalism etc.
Many thanks :) ShockMetric 19:53, 20 April 2010 (UTC)
- You're quite right, it actually should pick up on any changes since you've opened the page, and inform the user, not only with page blanking. Amalthea 21:00, 22 April 2010 (UTC)
Restore this version (revisited)
I had requested this feature a year ago and it didn't get any responses. Still seems like a good idea, just wondering if there is a reason it isn't. Basically I'm wondering why the "restore this version" link only appears above the diff on the left and not the one on the right (when you're actually looking at the version on the right). -- Mufka (u) (t) (c) 19:23, 22 April 2010 (UTC)
- Done. You might need to WP:BYPASS your cache to see the change, and you'll only get it if you aren't looking at the diff to the current revision, of course. Amalthea 20:57, 22 April 2010 (UTC)
Template Request
Hello. Skier Dude and I have created a set of standard multi-level warning templates for warning users about repeatedly uploading files missing copyright information:
Would it be possible to implement them into Twinkle? Thanks in advance, FASTILYsock(TALK) 07:06, 7 April 2010 (UTC)
- Just as a pointer for this and the above section, I'm normally waiting for other opinions before adding templates, so as not to overload Twinkle and Friendly.
Friendly offers customized templates being defined in each user's skin script – useful for Twinkle, too? Amalthea 23:54, 27 April 2010 (UTC)
Sockpuppet reporting thought
Unfortunately, I've found myself reporting a number of sockpuppets lately. I've normally done so manually at WP:SPI, but then I saw that Twinkle could do it. Well, I ran across a new sockpuppet of a banned user, so I filed the report using Twinkle; however, it posted the report as if the user was the master puppeteer instead of the sock of an already-banned puppeteer. Has any thought been given to adding an option that enables the user to tag the account as a suspected master puppeteer or as a sockpuppet to another account that already has a "rap sheet", of sorts? Thanks for giving users the chance to improve the performance of this impressive set of tools. --McDoobAU93 (talk) 15:27, 30 April 2010 (UTC)
- Hmm, yeah, the sockpuppet reporting was rewritten with the new SPI process a while back, and a number of markers Twinkle used have been changed in the meantime. I'll have a look. Amalthea 20:57, 2 May 2010 (UTC)
BLP PROD part 2
This is more a request for an additional warning rather than a feature. If you look at Wikipedia talk:Proposed deletion of biographies of living people#Does scope need to be clarified? there has been a bit of confusion by at least two editors as to what the PROD actually covers. Right now it warns if the article was created before 18 March 2010 but it might be a good idea to have a warning that always comes up explaining that the PROD is only for biographies and no other article types. The highly esteemed CBW presents the Talk Page! 19:33, 2 May 2010 (UTC)
- Alright, since my previous note used the somewhat wider definition "article focused on biographic material of living persons" I added a line pointing that out. Will probably remove it down the line though once this process is more established.
Cheers, Amalthea 20:54, 2 May 2010 (UTC)
Warn code: COI
{{uw-coi}} should be included as a choice for warning a user. — Timneu22 · talk 22:06, 17 May 2010 (UTC)
- Already in there, with the single notice templates. Amalthea 23:32, 17 May 2010 (UTC)
Tabs on contributions page
In addition to "arv", please add the following tabs on each user contributions page (for instance mine here): "tb"; "wel"; "warn"; "last"; "rpp"; and "unlink". Thanks! — Jeff G. ツ 03:20, 23 May 2010 (UTC)
- The latter three need to refer to a specific page, they can't be added on a contributions page. Amalthea 10:43, 23 May 2010 (UTC)
Hi and, first of all, thanks for Twinkle: it makes patrolling extremely easy!
Anyway, a new template was recently created, {{uw-hasty}}, stemming from this discussion; would it be possible to include it in the list of warning avalaible, using Twinkle? Thanks! Salvio ( Let's talk 'bout it!) 16:38, 28 May 2010 (UTC)
Global lock checks when attempting to report users
When reporting a user to AIV or UAA, Twinkle should check whether the user in question is using a SUL account, and if so, whether the account has already been globally-locked by a Steward. If the account to be reported is globally-locked, Twinkle should display an appropriate alert message and ask whether it should still try to report the user anyway. --SoCalSuperEagle (talk) 18:45, 29 May 2010 (UTC)
- I agree, but would add that if the offender is using an IP Address, check instead whether it has been subjected to Global blocking. — Jeff G. ツ 22:09, 31 May 2010 (UTC)
Can support for db-multiple be added to the CSD dialogue ? Codf1977 (talk) 11:40, 2 June 2010 (UTC)
- See WT:TW#Multiple db tags. Amalthea 16:42, 2 June 2010 (UTC)
G6 - "Local description page for Image on Commons"
Could an option for this be added to the CSD's?
Sfan00 IMG (talk) 12:58, 2 June 2010 (UTC)
- I've been told that F2's wording doesn't actually say that this is covered.Sfan00 IMG (talk) 16:05, 2 June 2010 (UTC)
- Ah, I see, there was WP:Administrators' noticeboard/Archive213#WP:CSD#F2. It's been added back, and at the moment explicitly covers it ("This also includes empty (i.e., no content) image description pages for Commons images."). WP:CSD#G8 does too, though. There's no discussion on WT:CSD about it, I would say that it should be cleared up there first. Amalthea 16:41, 2 June 2010 (UTC)
- I've been told that F2's wording doesn't actually say that this is covered.Sfan00 IMG (talk) 16:05, 2 June 2010 (UTC)
Second prods
There should be a way to "prod-2" articles with twinkle. Marcus Qwertius (talk) 15:53, 5 June 2010 (UTC)
- ah. I see now that you can prod-2 with the prod button. Maybe make a note of that feature in the description? Marcus Qwertius (talk) 15:56, 5 June 2010 (UTC)
add uw-affiliate warning
Add {{uw-affiliate}} as a selectable warning, please. -- Rick Van Tassel user|talk|contribs 20:49, 9 June 2010 (UTC)
If user is blocked, confirm warning needs to be added
Further to some comments at Wikipedia talk:User pages#WP:REMOVED - should current blocks be in the list?. Probably a useful feature, to prevent unnecessary warnings after vandals have already been blocked. –xenotalk 18:21, 14 June 2010 (UTC)
- Not all of them will never be unblocked if you mean any warning. Sole Soul (talk) 18:35, 14 June 2010 (UTC)
Can a feature be added to easily add cleanup templates to a page? CTJF83 pride 08:14, 22 June 2010 (UTC)
- WP:FRIENDLY does that. Amalthea 09:48, 22 June 2010 (UTC)
The warn feature on a talk page doesn't seem to have edit war as a reason.--Iankap99 (talk) 23:44, 2 July 2010 (UTC)
Another notice to add
Template:Firstredirect would be a good candidate to add to the "Single issue notices" group, however it takes two parameters so I'm unsure if the Twinkle dialog box can support that (if it's too much of a pain in the ass, don't worry about it). Also, I can create a redirect in the standard uw-xxx format if necessary. -- Ϫ 19:28, 5 July 2010 (UTC)
blp prod removal
I started a Uw-blpprod series of user warning templates. -- Marcus Qwertyus (talk) 23:26, 23 June 2010 (UTC)
Done Marcus Qwertyus (signs his posts) 04:37, 10 July 2010 (UTC)
Add {{Uw-spoiler}}
Please add {{Uw-spoiler}}, this would be extremely helpful to anyone working on television related articles, as it is one of those issues that keeps coming up with decent frequency. Thanks. Xeworlebi (talk) 00:30, 10 July 2010 (UTC)
- Will implement tonight. Marcus Qwertyus (signs his posts) 02:35, 10 July 2010 (UTC)
CSD C1 - Empty Category script should inform category creator about deletion.
I had a concern raised on my talk page (User_talk:Sfan00_IMG#informing_category_creators) that I should be informing category creators about C1 CSD's.
I can do this manually, but it would be much appreciated if this could be automated inside TWINKLE.
Sfan00 IMG (talk) 10:47, 15 July 2010 (UTC)
Handle end punctuation in "rollback" edit summary dialogue
I very commonly add end punctuation to my edit summaries when I roll back others' edits. The result is usually a doubled full-stop, which looks like some kind of strange hybrid of full stop and ellipsis. Here are two example diffs: 1 2
This double-punctuation would also occur with question marks and exclamation points, I believe.
If possible, the user's edit summary should be checked for end punctuation, and if any exists, TW should not add an extra full-stop to the end. Thank you. —Bill Price(notyourbroom) 15:53, 26 July 2010 (UTC)
Add optional rationale for db-g6
Would it be possible to prompt for an optional rationale when selecting the "G6: Housekeeping" option? In its current state, selecting this option populates the template with text to the effect of "this template should not be used in its default state; please insert a rationale" and I have to manually edit the article to add my rationale. Thanks! —KuyaBriBriTalk 15:23, 11 August 2010 (UTC)
- Done! You're now prompted for an (optional) rationale when selecting the g6 housekeeping option. Ioeth (talk contribs twinkle friendly) 19:50, 27 August 2010 (UTC)
Add support for {{Uw-incompleteAFD}}
Blanchardb just helped me create a new user warning template, {{Uw-incompleteAFD}}. Could support for this be added in the "single issue notices" section? Ten Pound Hammer, his otters and a clue-bat • (Many otters • One bat • One hammer) 15:56, 13 August 2010 (UTC)
Edit War Warning.
I think this should be added to user warnings: uw-3rr
I could really find that useful to warn people for edit wars. Thanks! Endofskull (talk) 17:22, 14 August 2010 (UTC)
- That's under "Single-issue warnings." AnturiaethwrTalk 17:44, 14 August 2010 (UTC)
- Oh, okay. Thanks! Endofskull (talk) 21:22, 14 August 2010 (UTC)
- No problem. AnturiaethwrTalk 21:56, 14 August 2010 (UTC)
- Oh, okay. Thanks! Endofskull (talk) 21:22, 14 August 2010 (UTC)
Separate CSD#G10 into two points and detecting redirect/later expansion
Last night I nominated an article for deletion under CSD#G10, but under the "biographical material about a living person that is entirely negative in tone and unsourced" provision, rather than the "attack page" rule. Understandably, the article creator was a bit upset to then be accused of writting an attack page by the std user notification template used by Twinkle. Rather than making the tagger go in and edit the user notification each time, can G10 be split into two options - attack page or negative unreffed BLP.
This article was also more complicated as the article was created as a redirect and then expanded by someone else. Is it possible for Twinkle to detect this and notify both editors? The-Pope (talk) 00:10, 25 August 2010 (UTC)
- If you can point me to a template that should be used in the case you described above instead of {{db-G10-notice}}, I'll happily make the change. Ioeth (talk contribs twinkle friendly) 19:55, 27 August 2010 (UTC)
- I do this occasionally, including today but I find it rare enough that a bespoke message works. ϢereSpielChequers 18:35, 6 September 2010 (UTC)
Restate edit summary for pseudo-speedy deletion
The di deletion tags on Wikipedia are strictly speaking speedy deletion, but in reality it's more of a pseudo-speedy deletion. This has caused confusion and panic for at least one user, and probably confuses several other people, because the edit summary under Twinkle says "This file is up for deletion per WP:CSD." Perhaps we can restate that as
- "This file is up for pseudo-speedy deletion per WP:CSD#F[type]" or
- "This file is up for deletion within [X] days per WP:CSD#F[type]",
- where [X] = 2 or 7 (i.e., the days until the pseudo-speedy deletion becomes active) and
- where [type] = F4-F7 or F11 (the proper CSD category)
Also, sorry for typing in pseudocode (no pun intended). Magog the Ogre (talk) 08:54, 7 September 2010 (UTC)
Add support for db-animal
I know it's not all that common, but can we add support for {{db-animal}}? It's already supported in the template that Twinkle uses to warn users about speedy deletions. — Train2104 (talk • contribs • count) 19:42, 10 September 2010 (UTC)
Warn about permissions
Twinkle should notify the user and soft-quit (i.e. not require the user to close the floating window) when the user does not have permission to edit the page. Currently, if a non-admin tries to edit a protected page, it gets stuck on "...data loaded". Same applies for editnotices and those who can't edit them. — Train2104 (talk • contribs • count) 19:45, 10 September 2010 (UTC)
Ask administrator for clarification on bit-by-bit commons deletions
When deleting under F8, if the commons file has a different file name, it becomes difficult to track down the new name on commons. IMHO, Twinkle really ought to ask an administrator for clarification (e.g., "Please type the name of the file on commons here, or leave blank if it is the same (omit File: prefix)"). Additionally, if you're feeling particularly clever, you could have the field pre-populate by having the Twinkle script automatically pick up the new name as it will be listed on the page and at Special:FileDuplicateSearch. Magog the Ogre (talk) 08:56, 11 September 2010 (UTC)
Add a legal threat block warning option for IPs
So it doesn't say "blocked indefinitely" when you can't block them indefinitely. Grandmasterka 21:26, 11 September 2010 (UTC)
Semi-protecting a page with pending changes
When I protect a page, TW usually performs the action and adds the appropriate template, but this isn't the case when TW has to remove PC as well as protect the page (exmaple). Could the auto-adding of the semi-protection template be implemented for this function as well? Airplaneman ✈ 21:24, 19 September 2010 (UTC)
Another request on optional rationales
Thanks for fulfilling my request to add an optional rationale for db-g6 "Housekeeping"! I have another request on all optional rationale prompts such as on "rollback" and "rollback (AGF)". As it stands, the rationale window has an "OK" and "Cancel" button. To me, selecting "Cancel" intuitively means to abort the process; however, in this case selecting "Cancel" goes ahead with the process without adding a rationale. Would it be possible to do one of the following:
- Make three buttons: "OK" to insert the rationale given, "Skip" to give no rationale, and "Cancel" or "Abort" to completely abort the process
- Relabel "Cancel" as "Skip" or "No rationale"
While I realize the second option is probably easier to code, I would prefer the first option, as it makes it possible to switch to one of my other browser tabs if I need to copy and paste something like a copyvio URL. —KuyaBriBriTalk 14:43, 21 September 2010 (UTC)
- Actually, pressing "Cancel" should really cancel the rollback request since April 2009. Are you sure that still happens? You can already "Skip" by leaving the input field empty and pressing OK. Amalthea 15:10, 21 September 2010 (UTC)
- I really need to work on this whole "fire, ready, aim" trend I've been on lately. Looks like you're right as far as rollback, rollback AGF, and db-g12 are concerned, but my concern is still valid for the new db-g6 rationale prompt. Regardless, could you add a one-liner to the effect of "Leave blank and click OK to skip"? —KuyaBriBriTalk 16:36, 21 September 2010 (UTC)
- I've made G6 consistent in that it will now abort if you press cancel. Bypass your browser cache once to get the new version. Amalthea 17:36, 21 September 2010 (UTC)
- I really need to work on this whole "fire, ready, aim" trend I've been on lately. Looks like you're right as far as rollback, rollback AGF, and db-g12 are concerned, but my concern is still valid for the new db-g6 rationale prompt. Regardless, could you add a one-liner to the effect of "Leave blank and click OK to skip"? —KuyaBriBriTalk 16:36, 21 September 2010 (UTC)
Remove Template:Uw-sandbox
I respectfully ask that Template:Uw-sandbox be removed from Twinkle.
The warning is bitey to new users, and entirely unnecessary, as a bot replaces the sandbox header within minutes of its removal. It gets users off to a poor start with a warning message, and discourages otherwise healthy experimentation that is in the right place, ie not disrupting the project.
In the case of actual problematic edits to sandbox, the other warnings cover things just fine.
Recently, this was discussed in TfD. Whilst a few keep votes saved deletion, please note that they suggested a total rewrite and rename. Quite simply, it does not require a warning. Its existence in the Twinkle choices makes it all too easy for over-eager folks to slap a warning on a new users page, for surely the most trivial of all digressions.
For full reasoning, do see the TFD page. Thank you for your consideration, Chzz ► 16:38, 12 September 2010 (UTC)
- Support - This template really should not be used on new users. --Alpha Quadrant talk 14:43, 24 September 2010 (UTC)
add {{Urls}} to Tags option
It'd be nice to have the {{Urls}} template in the tags option because I see a lot of article that have bare URLs as references and they could easily be fixed with citation templates. Devourer09 14:32, 7 October 2010 (UTC)
Move to commons assistant
The Wikipedia files with duplicates on commons backlog is literally several months behind and around 10 thousand images. It's not hard to see why, given the tedium involved. However, a Twinkle tool built upon the traverse function would be incredibly helpful _ I estimate it would safe time on a magnitude of 10. It would involve the following:
- On one side it would display the en.wp page, and on the other the commons page. (For comparing license equivalence, attribution, etc.). Ideally, the tool could also note if the uploader's name on en.wp is present on commons.
- The tool would verify if the images are bit-by-bit copies of each other (if not, the commons image might just be a higher res version, which is still OK).
- The tool would verify the two images are of the same type (e.g., jpg vs. png)
- If the two images are of a different name, and approved by the clicking administrator, then it would change the transclusions to the commons file name.
- The tool would verify that a different image of the same name as the commons image doesn't exist on wp. E.g., File:Image1.jpg is different than Commons:File:Image1.jpg. To clarify, if image (1) exists as B.jpg on en.wp, and image (1) exists as A.jpg on commons, but image (2) exists as A.jpg on en.wp, then image (1) will be inaccessible to en.wp until image (2) is removed.
This tool would be very helpful for those of us that work in this backlog. I looked into creating an AWB plugin, but I was lost. Then I looked into writing the Twinkle plugin myself, but the programming style is lost on me. Nevertheless, I could easily write and maintain much of the code with some assistance in pointing to where to start (I was a computer science major, but I've been out of the profession for a few years). Magog the Ogre (talk) 21:19, 21 September 2010 (UTC)
Bumping to avoid bot archival. Magog the Ogre (talk) 07:44, 9 October 2010 (UTC)
Add a 'Rough translation' tag
Suggest adding a Twinkle item for the {{RoughTranslation|Foo}} tag.--Kudpung (talk) 10:32, 19 October 2010 (UTC)
Retain user's Talk page link, on reverting
When Twinkle is used to revert an edit, Twinkle's Edit Summary (ES) shows the account name of the user whose edit is being reverted. Unfortunately, though, it doesn't retain the user's (talk) page link (examples here). I suggest it's better to show the (talk) link, because:
- if the user's talk page is in red (talk), the user may well still need an appropriately guarded 'welcome' &/or a possible warning.
- if the user's talk page is in blue (talk), the above step(s) have ideally already been undertaken by the reverter.
Retaining (talk) adds a mere 6 characters to the ES, and of course an ES can be up to 200 characters. I'm guessing this would be an easy change. Trafford09 (talk) 08:10, 20 October 2010 (UTC)
- I agree, it should generally try and emulate MediaWiki:Revertpage:
- The reverted editor should be listed with contributions and talk link
- The editor reverted to should not be linked
- Done, you may need to bypass your browser cache to get the changed script. Amalthea 10:02, 21 October 2010 (UTC)
- Oh, and it's seven characters if you count the space, and the edit summary can actually contain up to around 255 characters. :) Amalthea 10:04, 21 October 2010 (UTC)
- Thanks, Amalthea - you're a star - and quick service to boot.
- Seven characters, yes, you're right :)
- ~255? If so and we're sure (please indicate where it says so), I'd be happy to change Help:Edit_summary#Properties. Trafford09 (talk) 10:43, 21 October 2010 (UTC)
- It says so in the database. :) The web interface does indeed limit to 200, to be somewhat safe since UTF8 multibyte characters take up more than one byte. There's a gadget that calculates how many characters you may actually use depending on the content (i.e. you can use 250 'a', but only 125 'ä'). Amalthea 10:50, 21 October 2010 (UTC)
- 'Ask an expert' works again. Thanks. I'll leave the above 200 alone, then, as it seems a fair yardstick for users to have in mind. Cheers, Trafford09 (talk) 10:57, 21 October 2010 (UTC)
- Oh, and it's seven characters if you count the space, and the edit summary can actually contain up to around 255 characters. :) Amalthea 10:04, 21 October 2010 (UTC)
Articles for creation
Hello, I was wondering if Twinkle could be modified so that it can help with the AFC Process as pasting the templates can become tedious. Thank you, Bobby122 Contact Me (C) 00:24, 26 October 2010 (UTC)
- Never mind, I see there is already a script for it. Bobby122 Contact Me (C) 02:05, 26 October 2010 (UTC)
Add {{WWFinuse}}
Could we add {{WWFinuse}} to the tagging section? WikiCopter (radio • sorties • images • lost • defense • attack) 05:01, 3 November 2010 (UTC)
Add Notability:Sports to notability tag options
Now that Wikipedia:Notability (sports) is an accepted guideline, could that please be added as a sub-option to the notability list in the same way as Wikipedia:Notability (academics) is? Cheers.--ClubOranjeT 10:50, 5 November 2010 (UTC)
On other languages
I think Twinkle should be on other some Wikipedias. Such as the French Wikipedia. Is this possible? Endofskull (talk) 19:01, 27 October 2010 (UTC)
- Support. Hmm, yes, I'd use that. Trafford09 (talk) 10:13, 10 November 2010 (UTC)
Maxlength for rollback prompts
As of now there is no way to know if the edit summary is too long when prompted after using TW's non-vandalism rollback feature. This will often cut of long edit summaries in the middle of a word unless you count the characters and add them to the ones TW is producing. Some lines of code for a maxlength would solve this. Sorry if this request already has been dismissed, I couldn't find anything in the archives. jonkerz♠ 19:46, 8 November 2010 (UTC)
- Can't limit the input field in a native prompt dialog, HTML's maxlength doesn't work there. Would need to be reworked to use a DOM-type modular input dialog, which only makes sense as part of a complete port to use jquery or something. Amalthea 23:52, 8 November 2010 (UTC)
(outdent) You are right that there no way to do it natively with the promt() function, but I was thinking of something like this:
var max_length = 200;
var summary = "Reverted [[WP:AGF|good faith]] edits: ";
var extra_summary ="";
while (extra_summary = prompt("An optional comment for the edit summary:", extra_summary), extra_summary.length > max_length - summary.length) {
var r = confirm("Edit summary too long, chop comment?");
if (r == true)
break; //Not actually chopped, but passed along as usual
It works, but I don't know if the code is ugly. Too long comments are not a huge problem, so this request is not top priority anyways. By the way, thanks for the quick reply, jonkerz♠ 02:28, 9 November 2010 (UTC)
Wikilink "reverted" to Help:Revert
I used Twinkle this morning for a reversion [6] and it suddenly struck me that it would be helpful for newbies if the word "reverted", which is part of the Twinkle edit summary, were wikilinked to Help:Revert. Rollback does this. Rd232 talk 09:43, 10 November 2010 (UTC)
- Support Nice idea - helpful and consistent - fingers crossed :) Trafford09 (talk) 10:06, 10 November 2010 (UTC)
Add better Find sources links to AFD/XFD
In this AFD created by Twinkle I noticed the {{Find sources}} link includes the disambiguating parentheses within the search links. This restricts the search results such that genuine sources are not found. Could this be improved? Suggestions are: only include the article name up to the open parentheses (with the disadvantage that results might then contain too many irrelevant sources); output both links, first a set without parentheses followed by a set with parentheses. -84user (talk) 11:34, 19 November 2010 (UTC)
- Twinkle uses the {{Afd2}} template to create the AfD page. If you want the text passed to the find-sources template manipulated it needs to be done there.
Hint: {{Italic title}} already recognizes disambiguators, should be easy to whip up one that cuts them off. Amalthea 13:46, 19 November 2010 (UTC)
Username reports
How about a special checkbox for WP:CORPNAME violations that produces report reason on WP:UAA of "Company/organization username"? This would help for these usernames to stand out from "promotional username" reports (which could then be restricted to truly promotional usernames like "Buy iPods now!", etc). Ks0stm (T•C•G) 21:54, 22 December 2010 (UTC)
Add language popup box for notenglish tag
I would love to have a popup box to enter the language when using the "notenglish" tag. Currently, you must manually edit after adding the tag to add the language. Thanks!!! jsfouche ☽☾Talk 00:16, 28 December 2010 (UTC)
- I did manage to add them individually (the most common) to my custom tags, but it would still be helpful. jsfouche ☽☾Talk 01:17, 28 December 2010 (UTC)
I would like to be able to add a contrib tag to user talk pages when they are writing in languages other than English. Thanks!!!jsfouche ☽☾Talk 00:35, 28 December 2010 (UTC)
Move stuff around
I'm not sure how much support this will get, but I think it may be necessary to move the radio buttons to a more prioritized order. This could either be a hard-coded order or (preferred) a user preference. For example, the screen shows:
Essentially, this means that I have to scroll down to the bottom of the page to get to the G10-G12 stuff. Not only is this slightly slower, but it leads me to accidentally click a radio button and apply the incorrect CSD. For the patrolling I do, these make up close to 100% of my nominations: A1, A3, A7, A9, G10, G11, G12, and somewhat G3, G1, A9, and A10. It would be ideal for me to just have those available immediately. I have never used G5, and rarely use G4 or G6, yet those things are right in my face because we're sorting numerically. I dunno, just a thought. — Timneu22 · talk 16:01, 22 December 2010 (UTC)
- Support I like this idea; I've experienced similar issues myself. This would make it that much easier to use Twinkle. The Blade of the Northern Lights (話して下さい) 20:53, 22 December 2010 (UTC)
- Support Makes sense to me. Trafford09 (talk) 09:50, 26 December 2010 (UTC)
- Comment Perhaps a better idea would be to allow users to specify a preference for the size of each Twinkle window that pops up. That way, if you have a large monitor, you can size the window so that all of the options appear, and no scrolling is required. SnottyWong spout 21:44, 28 December 2010 (UTC)
Addition of {{All plot}} and {{Cleanup-link rot}} (again)
I requested these tags to be added a couple of months ago, so far two people supported the addition, but the request was archived and the tags never added. So I'll request them again, please add {{All plot}} and {{Cleanup-link rot}}. Thanks. Xeworlebi (talk) 13:41, 26 December 2010 (UTC)
- Strong Support - In particular, {{Cleanup-link rot}} is a must-have for me. I think it would make sense to have the checkbox for {{Cleanup}} expand when you click on it (like it does for {{Notability}}) and give you access to the specific cleanup templates, like {{Cleanup-rewrite}}, {{Cleanup-reorganize}}, {{Cleanup-images}}, {{Cleanup-gallery}}, {{Cleanup-tense}}, {{Cleanup-jargon}}, {{Cleanup-link rot}}, {{Cleanup-HTML}}, {{Cleanup-articletitle}}, and many others. There are literally tons of these, some of which would be appropriate to include, some of which would not. Perhaps it would be appropriate to start a quick discussion on which should be included, and then add them to the script. I'd be happy to write the code and have an admin insert it, if no one else has the time. SnottyWong verbalize 21:32, 28 December 2010 (UTC)
- For what it's worth, I copied the current version of the script into my userspace and added the functionality for {{cleanup-link rot}}. Adding the extended cleanup functionality as I described above would be more complicated, and would not work correctly in some situations (per a bug report I recently submitted here). You can find (and use, if you like) the modified version at User:Snottywong/friendlytagmod.js. Of course, this version will not benefit from future upgrades, so hopefully this can be rolled into the permanent version of the script, as it was extraordinarily trivial to add this functionality. SnottyWong chat 23:11, 28 December 2010 (UTC)
Add support for db-multiple
I noticed that on a number of new articles that I look at on NPP, speedy deletion criteria A7 (Unremarkable company or organization) and G11 (Blatant promotion) go together a lot. Is there a way to get Twinkle to support the Template:db-multiple tag? —Preceding unsigned comment added by Bk314159 (talk • contribs) 02:42, 6 August 2010 (UTC)
- Strong support. I tend to go manual when db-multiple is required, and putting it into Twinkle would make it easier. — Train2104 (talk • contribs • count) 19:40, 10 September 2010 (UTC)
- Please, please, please add this on if possible. There are many instances where I could use that, and manual tagging is far more tedious. The Blade of the Northern Lights (話して下さい) 00:37, 30 September 2010 (UTC)
- Big-time support! I could really use this, too. - Realkyhick (Talk to me) 03:45, 30 September 2010 (UTC)
- Strong support! it takes ages to fish around and do this manually.--Kudpung (talk) 10:29, 19 October 2010 (UTC)
- Absolutely Yes! Anyone who has spent time in Special:NewPages knows how helpful this would be --Fiftytwo thirty (talk) 02:12, 21 October 2010 (UTC)
- Support. Well - if I didn't, this section would be archived (after 28 days, it says above). Trafford09 (talk) 10:09, 10 November 2010 (UTC)
- Support a lot. It seems this could be very useful since lots of people use it. Speeds things up a bit I would think. Alex³ (talk) 15:38, 17 November 2010 (UTC)
- Support, since Twinkle currently does not allow for the addition of more than one speedy deletion criteria. Guoguo12--Talk-- 00:23, 23 November 2010 (UTC)
- Support - per above. Eagles 24/7 (C) 01:23, 23 November 2010 (UTC)
- ASAP, please and thank you. Marcus Qwertyus 01:32, 23 November 2010 (UTC)
- Strong Support Would make things way easier. →GƒoleyFour (GSV) 02:35, 23 November 2010 (UTC)
- Strong Support per above: would make things far easier, and it would not be too hard of an addition to add so far as I can tell. dmz 23:38, 5 December 2010 (UTC)
- Yes, need this!— Timneu22 · talk 15:56, 22 December 2010 (UTC)
- Support Would be very useful. Acather96 (talk) 18:23, 7 January 2011 (UTC)
- Support Very good idea. Armbrust Talk Contribs 19:53, 7 January 2011 (UTC)
Template:Edit Summary
I think it would be useful if Template:Uw-editsummary was added to the standard version of Twinkle. --Confession0791 talk 05:01, 29 December 2010 (UTC)
- It's already there, under 'single issue notices' Pol430 talk to me 09:30, 29 December 2010 (UTC)
- To Confession0791 and others, consider also:
- Wikipedia relies on wp:consensus, and our all adhering to its guidelines.
- One such is wp:ES#Always provide an edit summary. Please adhere to it, or state why the consensus doesn't apply in your case.
- and if that template fails, you may find the following helpful:
Edit summaries
|Tip of the day...
Please summarize your work using the Edit summary box
If you make anything other than a minor edit to an article, it helps others if you fill in the edit summary. Edit summaries are visible in the page history, watchlists, and on Recent changes, so they help other users keep track of what is happening to a page.
If you use section editing, the summary box is filled in with the section heading by default (in gray text), which you can follow with more detail. You also can put links to articles in the edit summary. Just put double brackets around [[the article title]] like you would normally. The summary is limited to 255 characters, so many people use common abbreviations, such as sp for correcting spelling mistakes, rm for remove, ce for copy-edit, etc.
Edit summaries (ad)
|A Wikipedia ad has been created for this project page
Trafford09 (talk) 14:58, 29 December 2010 (UTC)
Support for more di templates
Currently we don't have those supported on Twinkle. They're listed at Template:File deletion template notice. The ones I'd be interested in are:
- Dw-nld
- Dw-nsd
- Dw-nsdnld
- Orfurrev
- Furd
And lastly one I don't care about but you might want to add anyway:
- Nchd
I could surely just add it myself, but I don't want to touch your code without your permission. Magog the Ogre (talk) 16:49, 7 December 2010 (UTC)
Bump. Magog the Ogre (talk) 02:31, 28 December 2010 (UTC)
- Would enable me to be lazier, which is fantastic, so Strong Support. Acather96 (talk) 08:34, 8 January 2011 (UTC)
Self-explanatory. Logan Talk Contributions 21:51, 10 January 2011 (UTC)
Moving files to Commons
Not sure how possible this is, or how much support this is going to get but... Currently, when I need to move a file to Commons
- I tag it with {{MTC}}
- Click "Show Preview"
- Middle-click (open in new tab) "Copy to Commons via CommonsHelper"
- Complete the form
- Then replace the {{MTC}} (in the unsaved preview page) with {{Db-f8}}
- Click "Save Page"
Would it be possible to simply click a "MTC" via Twinkle, which directly goes to a pre-filled CommonsHelper (or CommonsHelper2 once that's up again)? And maybe even tag it with {{NowCommons}} or {{Db-f8}} once the transfer is complete? That would make things much faster and simpler wouldn't it? Rehman 04:12, 8 January 2011 (UTC)
- Take a look at User:Legoktm/com2.js. Logan Talk Contributions 21:51, 10 January 2011 (UTC)
Add new templates
I have created a series of 3 UW templates aimed at disruptive editing that is not vandalism, there appeared to be rough consensus for this at the project talk page. Could you integrate them into twinkle please. I have added the documentation template on to the first template (considering they are not yet included) you can find the first template at Template:Uw-disruptive1 with links to 2 and 3. Pol430 talk to me 20:23, 13 January 2011 (UTC)
Uw-mos1,2,3,4 now just a single issue notice. Marcus Qwertyus 06:02, 26 December 2010 (UTC)
- Scratch that. 1, 2, and 3 were restored. Just remove 4. Marcus Qwertyus 00:56, 17 January 2011 (UTC)
This template states (on the template page), that it is included in the standard installation of Twinkle, but I can't find it anywhere in the menus? I can't read scripts so looking at the scripts pages revealed nothing to me. Is this warning used in TW? If so where can I find it? And if not, can it be inserted for relevant warnings per the table at Wikipedia:Template messages/User talk namespace? Pol430 talk to me 10:54, 26 December 2010 (UTC)
- Comment - I did a bit of test editing in my user talk sandbox and found that this template exists for some L4 warnings (assuming as a redirect). For example, if you issue an L4 warning for edit tests using TW you get Uw-generic4. It appears to be missing from some areas though, for example there is no option in TW to issue an L4 warning for adding unsourced content... It stops at level 3. Whilst I could issue a L4 manually the whole purpose of using TW is to make is quicker. If I were to issue an L4 warning for adding unsourced content by just selecting L4 edit tests in TW knowing the template would ultimately be correct, the edit summary would be wrong. Pol430 talk to me 11:23, 26 December 2010 (UTC)
- I concur. Can Template:Uw-generic4 be added please for issuing L4 on unsourced content? I keep having the dilemma of doing it manually which defeats the purpose of TW, or having an incorrect edit summary. Thanks. --Muhandes (talk) 10:10, 19 January 2011 (UTC)
Replace the "don't warn" function for users nominating their own work for deletion/tagging
Hi. I've just been speaking to AzaToth over IRC, who informed me that a feature which used to be present in Twinkle has been removed, and not by him. I edited some of my work earlier today, nominating an image I'd uploaded, and to which only I had contributed, for deletion. I subsequently discovered that I'd received a warning on my talk page about the CSD request. What is the point of telling me something I already know??? I know I've nominated the page for deletion, I don't need warning that I've done it, since I have a memory longer than a goldfish :)
Is there any chance that this feature could be replaced please? If ever I go through and clean out all my old images and work, I'm gonna be flooded with warnings, and I don't fancy wasting time cleaning out my work, and then having to remove a load of warnings about stuff I don't need to know from my talk page too!!! Thank you! BarkingFish 02:42, 6 January 2011 (UTC)
- I've had a similar experience. After userfying an autobiographical page, I tried tagged the redirect that was left behind (WP:CSD#R2) and received a warning on my talk page that a page I had created was nominated for speedy deletion. -- Bk314159 (Talk to me and find out what I've done) 16:27, 18 January 2011 (UTC)
- I don't think there ever was a check in the CSD tool, actually (some scripts have or had such sanity checks, the ARV tool for example).
Wouldn't be hard to add a prompt asking the user whether he really wants to notify himself (which some people sometimes want to do). And I note that there's always been the [ ] Notify checkbox that you can can use to prevent the notification.
Amalthea 14:52, 20 January 2011 (UTC)
Opt out
Would it be possible to add an opt-out so that people don't need to receive notifications via Twinkle? I've recently had 3 notices about deletion of articles I did not create. In each case I had made a minor edit many years ago. Angela. 02:42, 16 January 2011 (UTC)
- Only the last one of those notifications was made via Twinkle, the first two were placed on your talk page manually. You technically did create the first revision of that last article: a redirect as part of a page move, and it is very hard to automatically decide whether you want to be notified in such a case or not.
Anyway, it's of course technically possible to add an opt-out mechanism, and something like that is already on my long-term to-do list. Can't give you a time frame though, I'm afraid.
Cheers, Amalthea 12:34, 16 January 2011 (UTC)
- Template:Nobots gives a very simple Javascript regular expression to accomplish it. And I might point out that this is a real pain in the rear on User:Antidote, where admin notices are plugging up the page despite it being protected, so we regularly have to revert. Magog the Ogre (talk) 15:02, 19 January 2011 (UTC)
Would someone add {{tense}} to the "Tag" menu of Twinkle? Thanks! --- c y m r u . l a s s (talk me, stalk me) 16:14, 26 January 2011 (UTC)
It would be nice if Twinkle, when doing a CSD tagging, added a third step to the current two:
- Add CSD template to article
- Notify original editor of the article
- Update the article CSD template to indicate that the editor has been notified (e.g "user:foo received a notification".)
When I review a CSD, I almost always check to see that the original editor has been notified. Most of the time this is the case, but I wouldn't have to spend the time on that step if I could see, on the article CSD template, that notification has occurred.
Then I could skip checking the 90% or so that do notify, concentrate on determining whether the CSD is warranted, and only track down notification issues in those cases where it hasn't happened.--SPhilbrickT 16:00, 30 January 2011 (UTC)
- Some method of suppressing the recommendation to notify the initial contributor, as you suggest in step 3, needs to be implemented in the {{db-meta}} template, and the entire family of speedy deletion templates, before it could be implemented in Twinkle. If it were to be implemented in Twinkle, I don't think the method you suggest is quite right, in terms of bandwidth, unnecessary edits, etc. Better off to notify the user, then tag the page (at which point we will know whether the notification succeeded or not). — This, that, and the other (talk) 11:13, 5 February 2011 (UTC)
- I don't see any major problems with changing the order if it makes it easier:
- Notify user
- Add CSD template to article, with a paragraph indicating that the user:foo has been notified.
- I agree it would be easier to implement.--SPhilbrickT 15:50, 13 February 2011 (UTC)
- I don't see any major problems with changing the order if it makes it easier:
New template {{uw-copyright-remove}}
Could someone add the new single-level warning {{uw-copyright-remove}}? Thanks! -- King of ♥ ♦ ♣ ♠ 18:13, 7 February 2011 (UTC)
I have a minor nit I'd like to see done to the CSD menu. I'd like to see "Unremarkable band" reworded to "Unremarkable musician(s) or band", and "Unremarkable website" reworded to "Unremarkable website or web content". Both of these proposed wordings better sum up what the CSD templates state without getting too wordy. —KuyaBriBriTalk 22:20, 2 December 2010 (UTC)
- Support Sounds good to me (but - and I hesitate to ask this - what's a nit in this context?). Trafford09 (talk) 23:09, 22 December 2010 (UTC)
- Support Good idea. Armbrust public Talk Contribs 13:47, 3 February 2011 (UTC)
- I implemented this as part of my improvement to Twinkle's speedy functionality. All that remains to be done is for the appropriate code to be added to the main version. — This, that, and the other (talk) 10:42, 15 February 2011 (UTC)
Awarding barnstars
I've always wished that I could use Twinkle to award barnstars to good users the same way that I use it issue warnings to bad users. The fact that it is so much easier to issue warnings than barnstars means that I tend to issue lots of warnings and very few barnstars. Thus Wikipedia tends towards being a more hostile and less friendly place to be :( Kaldari (talk) 22:22, 15 February 2011 (UTC)
- I think awarding barnstars with Twinkle would be open to abuse. Barnstars are already misused enough. The award of a barnstar should be rare enough and sufficiently meritable that anyone who wants to award a one can find the time to do it manually. Kudpung (talk) 02:04, 17 February 2011 (UTC)
- How does someone abuse awarding barnstars?? Surely the potential for abusing warning templates is much higher than that for abusing barnstars! Just because awarding barnstars is rare doesn't mean it should be difficult. And if we want to make sure that barnstars are only used in the most meritous circumstances, we could also throw in an option to award a WikiCookie for lesser achievements. Kaldari (talk) 23:23, 21 February 2011 (UTC)
- Really? Nothing says barnstars should be used rarely. In fact, barnstars only encourage participation by rewarding contributions, major or minor. Adding a barnstar functionality to TW is, in my opinion, a great idea. Swarm X 05:29, 28 February 2011 (UTC)
- Agree with Kaldari and Swarm. I give out barnstars (somewhat frequently) just as a token of thanks for hard work, and more importantly, as a boost of encouragement. I think this is a good idea. Rehman 08:50, 28 February 2011 (UTC)
- I went ahead and wrote my own barnstar award tool in the meantime: User:Kaldari/wikilove.js. Feel free to install this in your vector.js. Kaldari (talk) 02:56, 1 March 2011 (UTC)
- Agree with Kaldari and Swarm. I give out barnstars (somewhat frequently) just as a token of thanks for hard work, and more importantly, as a boost of encouragement. I think this is a good idea. Rehman 08:50, 28 February 2011 (UTC)
Something to add
On the menu when you request for page protection can pending changes be added to the list of protections? Baseball Watcher 22:00, 28 February 2011 (UTC)
- This should probably wait until the future status of pending changes is more certain. Kaldari (talk) 02:57, 1 March 2011 (UTC)
Userfication moves as a default or easier for patrollers than deletion or CSD tagging
Last week's IRC Office Hours with Sue Gardner and their write up in this week's Signpost suggest that making userfication moves easier than deletion tagging for Twinkle users would make patrollers a lot more friendly to newbies. How hard is that? 188.8.131.52 (talk) 07:39, 1 March 2011 (UTC)
- What a good idea. A new Twinkle tab/menu item "Userfy" would be great. At the moment, we are currently trying to fix Twinkle to accommodate the rollout of MW 1.17. Once I'm done there, this might (just maybe) become a reality... — This, that, and the other (talk) 10:46, 1 March 2011 (UTC)
Translation template
When using the {{notenglish}} tag, one should receive a prompt for the language field. Feezo (Talk) 07:16, 2 March 2011 (UTC)
Don't re-create a page that has been deleted under you
In the fast and furious world of NPP Twinkle is a godsend, however I've experienced a peculiar oddity. I'm in the middle of tagging a page and the page is deleted from underneath me before I submit. I would like to request that if you are tagging or nominating for CSD, that Twinkle checks to see if the page has been deleted before attempting to apply the items. Hasteur (talk) 18:37, 13 January 2011 (UTC)
- It does do this, I believe, before it starts. However, if the deletion occurs in the moment after it checks for the page's existence, but before it actually tags the page, then it will probably fail. Twinkle's error-handling is notoriously poor, unfortunately, and it would be difficult to improve it. — This, that, and the other (talk) 11:00, 5 February 2011 (UTC)
- I guess it's just a by-product of working in the sub-second world of New Page Patrol. Hasteur (talk) 21:16, 5 February 2011 (UTC)
- Actually, this can be fixed by using the API. No doubt this will be fixed in the coming days; see WT:TW#2011-02-24. — This, that, and the other (talk) 11:17, 25 February 2011 (UTC)
- This is already in the core of the new version, but we still need to update the modules to use it. —UncleDouggie (talk) 20:06, 8 March 2011 (UTC)
- Actually, this can be fixed by using the API. No doubt this will be fixed in the coming days; see WT:TW#2011-02-24. — This, that, and the other (talk) 11:17, 25 February 2011 (UTC)
- I guess it's just a by-product of working in the sub-second world of New Page Patrol. Hasteur (talk) 21:16, 5 February 2011 (UTC)
First, thanks to the dev(s) for this great tool - I've been using Twinkle for nigh on four years now and have found it really useful. Second, can I request that {{schoolblock}} be added to the drop-down list of templated block reasons? It's one I use quite frequently and it would be very handy to have it at the click of a mouse :) Best regards, EyeSerenetalk 17:34, 16 March 2011 (UTC)
- Hi,
schoolblock and anonblock were removed a while ago since they aren't really compatible with the other uw-* templates and required a number of special cases in the code (they aren't substituted, for one). If necessary they can certainly be re-added or made compatible, one way or another. However, I note that User:Animum/easyblock.js also supports schoolblock/anonblock, with the added benefit that it takes care of the blocking as well. Have you ever tried using that?
Cheers, Amalthea 17:58, 16 March 2011 (UTC)
- Thanks for the explanation. I appreciate the difficultly with schoolblock and anonblock; I wonder if creating an alternative version of schoolblock (a la uw-ablock/anonblock) might be a viable alternative? However, I wasn't aware of easyblock.js so in the meantime I'll certainly take a look at that. Thanks again, EyeSerenetalk 11:54, 17 March 2011 (UTC)
Edit-warring warning edit summary
The edit summary for edit-warring warning currently reads "Warning: Potentially violating the three revert rule on ...". This puts too much emphasis on 3rr, when it's really just plain edit-warring that I'm warning of. How's about simply this: "Warning: Edit warring on/at ...". Rami R 11:37, 18 March 2011 (UTC)
As an experienced editor and frequent stub-sorter who's only just installed Twinkle, I'm surprised that it doesn't seem to offer {{linkrot}}. Is it hidden somewhere that I haven't found? If not, please could it be added? PamD (talk) 09:40, 19 March 2011 (UTC)
Can you make it so we have the "warn" drop down menu from the contributions page? Instead of just user/talk pages. CTJF83 01:42, 13 March 2011 (UTC)
- Thoughts??? CTJF83 04:28, 24 March 2011 (UTC)
- How would you know how to select the proper warning level without first viewing the user's talk page? —UncleDouggie (talk) 06:22, 24 March 2011 (UTC)
- I guess I'm mostly thinking if I view their edits and it is the first edit they have ever made...guess it wouldn't be as beneficial as I thought, touché CTJF83 15:21, 25 March 2011 (UTC)
- How would you know how to select the proper warning level without first viewing the user's talk page? —UncleDouggie (talk) 06:22, 24 March 2011 (UTC)
Reducing bite
So, I've been doing a bit of random beard-stroking and musing for the WMF on the interactions new users get at Special:NewPages, where Twinkle is widely used. One of the things I encountered was that the Twinkle CSD/Delete interface doesn't allow an admin to warn a user and delete the page; the options are "delete it and tell the user nothing" and "tag it for deletion and warn the user, while letting the article remain". This is a pretty clear problem, particularly since the former option is the default (and people are very, very lazy). Articles can be deleted without anything being said to the contributor, who comes back to find their work gone up in smoke with no obvious grounds or means of appeal, and no rationale given. Could we please enable "delete-and-warn" as an option, specifically the default option for administrators using Twinkle? Ironholds (talk) 20:49, 17 March 2011 (UTC)
- Or not? Ironholds (talk) 21:22, 24 March 2011 (UTC)
- Well, very few pages are actually deleted via Twinkle, for various reasons.
I would approve of automatic notification since it would make Twinkle delete a bit more useful, and it wouldn't be hard to implement. However, the first task would be to create notification templates that make sense when used during deletion, as opposed to the SD notification templates that mostly talk about SD templates and hangon and talk page rationales.
I can't tell whether this would make Twinkle delete attractive enough so that it's actually used though (See User talk:Amalthea/Archive 5#twinklespeedy.js again for some other issues I have with it). Amalthea 16:03, 25 March 2011 (UTC)
- Well, very few pages are actually deleted via Twinkle, for various reasons.
New welcoming template
I noticed there is no "potential problem user" welcoming template for someone who has created an unreferenced BLP. I have created one for Twinkle, {{Welcome unref blp}}. If it's deemed adequate, should it be added to Twinkle's menu of welcoming templates? — Preceding signed comment added by Cymru.lass (talk • contribs) 01:37, 28 March 2011 (UTC)
- The main thing I'd change is move the User:Cymru.lass/Advice/External links and references page to Help space. Amalthea 12:40, 28 March 2011 (UTC)
- Okie doke. I've never done much editing in the Help namespace, so I'm not entirely sure what the guidelines for inclusion are... Should I just move this to something like Help:External links and references? — Preceding signed comment added by Cymru.lass (talk • contribs) 00:22, 29 March 2011 (UTC)
- Sounds good; I'm not aware of guidelines describing what goes into Help space. Technical wikicode information should always be OK I'd say. Amalthea 10:23, 4 April 2011 (UTC)
- Okie doke. I've never done much editing in the Help namespace, so I'm not entirely sure what the guidelines for inclusion are... Should I just move this to something like Help:External links and references? — Preceding signed comment added by Cymru.lass (talk • contribs) 00:22, 29 March 2011 (UTC)
Protection templates
Has the possibility of adding the protection templates (
{{pp-semi}}, etc.) to the tag dialog been considered? -- Mufka (u) (t) (c) 01:35, 20 April 2011 (UTC)
- They are added when admins use the PP tab to protect pages. But thanks for the feedback; that module needs a serious overhaul (it allows you to insert a few templates that were deleted in 2009, for example), and I might add protection template tagging into it. — This, that, and the other (talk) 06:55, 21 April 2011 (UTC)
Belated welcome template?
I use this a lot, but it's not offered in Twinkle's list: {{Welcome-belated}}. Otherwise, I love using the Welcome feature in Twinkle! Cheers, Aristophanes68 (talk) 04:25, 24 March 2011 (UTC)
- Yes? No? Aristophanes68 (talk) 01:54, 29 March 2011 (UTC)
- We're a little busy on the rewrite at the moment. —UncleDouggie (talk) 02:17, 29 March 2011 (UTC)
- This is done, and Pending. — This, that, and the other (talk) 10:14, 23 April 2011 (UTC)
- We're a little busy on the rewrite at the moment. —UncleDouggie (talk) 02:17, 29 March 2011 (UTC)
Support reason parameter for cleanup template
When using Twinkle to tag pages using the Template:Cleanup, Twinkle currently does not support the reason parameter, use of which is now strongly encouraged as result of the consensus of a discussion last January. Twinkle should be modified to support that parameter. --Nat682 (talk) 06:05, 10 April 2011 (UTC)
- Pending. — This, that, and the other (talk) 07:33, 24 April 2011 (UTC)
Clearer edit summary for "welcome problem user" templates
Currently the edit summary for all the welcome templates is the same: "Added welcome template to user talk page using TW". Anyone glancing at the talk page history, perhaps using the navigation popup, won't see the implication of vandalism/spam/whatever and will get the impression that the user hasn't been warned. Could the "problem user" templates include the template name in the edit summary, perhaps? -- John of Reading (talk) 07:46, 25 March 2011 (UTC)
- The template names are omitted intentionally from the edit summary. Here's an example of why: if you were an anon IP who happened to be looking through your talk page history, and you saw "Added {{welcome-anon-vandal}} template...", you would likely feel offended and puzzled. Even the user doing the vandalizing might find it offensive. Anyway, the whole point of this is to reduce bite by hiding the template names.
- If you really want your welcomes to break from this, there is a preference you can set (see Wikipedia:Twinkle/doc#maskTemplateInSummary). But I advise against it. — This, that, and the other (talk) 07:38, 24 April 2011 (UTC)
- OK, not the template names then. But {{welcome-anon-vandal}} is roughly equivalent to {{welcome}} plus {{uw-vandal1}}; and Twinkle already knows to use the words "nonconstructive editing" for the latter. So perhaps "Added welcome template (nonconstructive editing) ...". -- John of Reading (talk) 07:51, 24 April 2011 (UTC)
Could the set of {{merge}} tags be added to Twinkle's list of tags? It would involve creating a dialogue box or two (to get the name of the article to merge to/from) and would also involve an edit to the article named in the dialogue box adding the corresponding merge tag. (I suppose also a functionality to cover merging multiple articles) I can see three situations that the new feature would have to cover:
- Using Twinkle, an editor adds
{{merge|B}}to article A suggesting that A be merged with (not to) B. Twinkle then adds
{{merge|A}}to article B
- Using Twinkle, an editor adds
{{merge to|B}}to article A suggesting that A be merged into B. Twinkle then adds
{{merge from|B}}to article B
- (Rare, but I suppose it could happen) Using Twinkle, an editor adds
{{merge from|B}}to article A, indicating that article B should be merged into article A. Twinkle then adds
{{merge to|A}}to article B
This has the potential to be superuseful. Thanks! — Preceding signed comment added by Cymru.lass (talk • contribs) 17:47, 23 April 2011 (UTC)
- Simple enough to add the tags: but I can't promise you that I'll get the tagging of the other page happening. — This, that, and the other (talk) 02:27, 24 April 2011 (UTC)
- Thanks! That sounds good :) By the way, thanks for all the work you do on Twinkle. It's an awesome tool! — Preceding signed comment added by Cymru.lass (talk • contribs) 21:13, 24 April 2011 (UTC)
{{db-animal}} be added to the list of criterion on the CSD menu? Baseball Watcher 23:30, 26 April 2011 (UTC)
- I thought about it. Seriously, though, how often do you need it? Besides, non-notable animal articles are usually obviously non-notable enough to be tagged with the general A7 tag, and the deleting admin will get it. — This, that, and the other (talk) 00:45, 30 April 2011 (UTC)
Twinkle probably needs new options in automatic warning notices. For example "Addition of duplicate material" would be helpful. Pass a Method talk 10:13, 27 April 2011 (UTC)
Multiple AfDs
It would be nice to list multiple similar articles for AfD at the same time. CTJF83 12:39, 26 April 2011 (UTC)
- It would be nice, wouldn't it? — This, that, and the other (talk) 11:47, 8 May 2011 (UTC)
- LOL, well is this something you can create? CTJF83 12:13, 9 May 2011 (UTC)
- It can be added to the to-do list. — This, that, and the other (talk) 10:45, 25 May 2011 (UTC)
- LOL, well is this something you can create? CTJF83 12:13, 9 May 2011 (UTC)
New template
Template:Uw-agf-sock is a new single level notification/warning for new users who are likely to have violated WP:SOCK out of ignorance, not malice. Could it be added to Twinkle's template list? Zakhalesh (talk) 17:06, 28 April 2011 (UTC)
- Pending — This, that, and the other (talk) 11:49, 25 May 2011 (UTC)
Preview Template
Would it be possible to preview the template that will be added to the page before clicking submit? Often I'm not sure exactly which template is correct, but if I could see what it says before sumitting, it would avoid having to either pull up the template in another tab or revert the edit if turns out to be wrong. MrKIA11 (talk) 04:17, 30 April 2011 (UTC)
- What a good idea. I have written the code, and this is Pending the roll-out of the updated Twinkle version, which hopefully shouldn't be too far away... — This, that, and the other (talk) 12:16, 30 April 2011 (UTC)
In the "Warn/Notify User" window, "Single issue warnings" category, the template that inserts Template:Uw-attack reads "[attack]: Personal attacks". First off, today was the first time I noticed this option, and if it is new I thank the developers for adding it. However, I would like to request a minor change to its wording, so that it reads "[uw-attack]: Creating attack pages". The addition of the "uw-" is to make it more consistent with the other choices in that menu, while changing the description to "Creating attack pages" brings it more in line with the actual text of the warning that it adds. Plus, to me, the term "personal attacks" is more generic in nature and is covered under the {{uw-npa#}} series of warnings. —KuyaBriBriTalk 18:30, 2 May 2011 (UTC)
- Quite right; this template is mislabelled. Pending the roll-out of the updated version of Twinkle. — This, that, and the other (talk) 08:33, 5 May 2011 (UTC)
language tag for {{tt:notenglish}}
Can you add support for tagging the article's language to the application of the {{tt:notenglish}}? Thanks! :) - UtherSRG (talk) 16:09, 7 May 2011 (UTC)
Multiple CSD reasons
Can we have support for the db-multiple tag added? No reason to have the tool limited to only one CSD reason. - UtherSRG (talk) 15:07, 9 May 2011 (UTC)
- There already is, at least on my version. On the top of the CSD dialog there's a box "Notify if possible" and right underneath it the multiple criteria box. Zakhalesh (talk) 16:31, 9 May 2011 (UTC)
- Same for me. It's labelled "Tag with multiple criteria." — Preceding signed comment added by Cymru.lass (talk • contribs) 16:33, 9 May 2011 (UTC)
- Hrm... I must be using an older version of TW... didn't think that was possible... I'll have to see what I need to change on my installation... (Help on my talk page would be appreciated!) - UtherSRG (talk) 16:42, 9 May 2011 (UTC)
- Nope, I don't have that at all. I have Twinkle and TW Friendly installed via my user preferences. Somehow I didn't get an update? - UtherSRG (talk) 16:51, 9 May 2011 (UTC)
- I posted a message on your talk page before I saw this message, but have you tried taking the script out of your .js and then purging the cache of your browser? Maybe the Special:Preferences version is clashing with your .js version somehow...? (I have no idea.) — Preceding signed comment added by Cymru.lass (talk • contribs) 16:56, 9 May 2011 (UTC)
- Same for me. It's labelled "Tag with multiple criteria." — Preceding signed comment added by Cymru.lass (talk • contribs) 16:33, 9 May 2011 (UTC)
- For some reason the feature is not visible for sysops ... :) Amalthea 16:59, 9 May 2011 (UTC)
- LOL! I guess this is under the assumptions that admins wouldn't tag but would simply do the deletion themselves? I think this needs to be changed. Sometimes I delete, and sometimes I tag.... - UtherSRG (talk) 17:05, 9 May 2011 (UTC)
- You know I've always wondered if sysops tagged or simply went ahead and deleted... Question answered, I guess! :P — Preceding signed comment added by Cymru.lass (talk • contribs) 17:14, 9 May 2011 (UTC)
- LOL! I guess this is under the assumptions that admins wouldn't tag but would simply do the deletion themselves? I think this needs to be changed. Sometimes I delete, and sometimes I tag.... - UtherSRG (talk) 17:05, 9 May 2011 (UTC)
- This has been fixed in the development version. AzaToth and I are (slowly) working on a roll-out at the moment. — This, that, and the other (talk) 22:36, 12 May 2011 (UTC)
Barnstars/otherwise positive stuff
Given Twinkle currently does warnings on user talk pages very well, and seeing today's Signpost coverage on the increase of negative talk page messages (partially driven by Twinkle, perhaps), would it be a good idea to add a tab allowing editors to leave barnstars or otherwise friendly messages? Effectively, what User:Ancient Apparition/WikiLove2 does, just incorporated into Twinkle? Strange Passerby (talk • cont) 01:15, 10 May 2011 (UTC)
- Note: this was discussed in February. MANdARAX • XAЯAbИAM 01:31, 10 May 2011 (UTC)
- I don't think it's a good idea to add anything that's strictly Wikipedia-culture and not directly related to the building of an encyclopedia to Twinkle. If people want to build a separate tool based on Morebits for awarding barnstars and such, then great, but I don't think we really want to open that can of beans with Twinkle, because my fear is, where would it end? Adding the former Friendly modules to Twinkle was a good idea because it harmonized with Twinkle's anti-vandalism and speedy deletion tools. This seems superfluous, plus Barnstars awarded manually are more personal and more meaningful than ones given via script, especially if one goofs in setting up the script and has to then re-edit. SchuminWeb (Talk) 03:04, 11 May 2011 (UTC)
Additional maintenance templates
Can the following templates be added to the tagging system?
{{All plot}}, I've requested this several times before
{{Cleanup-link rot}}, also requested this one on previous occasions
{{Over detailed}}, first time requesting this one
There appears a serious lack of response for template additions; they seem to be just ignored, even the ones were other users support the addition; and then they're archived of the page. Xeworlebi (talk) 17:08, 10 May 2011 (UTC)
- I believe it may be because Twinkle is undergoing a bit of a rewrite as we speak, and more energy may be going on programming the new Twinkle, vs. maintaining the existing Twinkle. At this point, I think the best advice is to please be patient, because once we get the new Twinkle running well and cut over to it, then we can talk about adding new templates to it. SchuminWeb (Talk) 02:59, 11 May 2011 (UTC)
- Except the first time I made these requests was more than 4 months ago, which was long before the rewrite started. I've seen many request go ignored long before the rewrite/merge with Friendly was going on. I know I'll have to wait a bit, but I tag quite a number of articles with these tags, and it's quite cumbersome to tag some with Twinkle, en then the others manually. Xeworlebi (talk) 12:01, 11 May 2011 (UTC)
- Well, I think if we're going to look at the tags box, let's really look at it. Biggest thing I have is that the current categorization of that box, which places things into "maintenance" and "problem", is somewhat arbitrary, and needs to get dropped, plus a few other fixtures. SchuminWeb (Talk) 12:41, 11 May 2011 (UTC)
- I, for one, am now checking RFA more regularly, so hopefully these requests should not get lost in the future. I can tell you that, in the development version (edging ever closer to an on-wiki rollout!), {{cleanup-link rot}} was already added, under the name {{link rot}}; I have added the other two now. Thanks for letting us know. — This, that, and the other (talk) 07:56, 15 May 2011 (UTC)
Article class candidates
How about putting a capability to start a FAC, FPC, FPOC, FLC, FTC, FSC, and GTC with twinkle. It would be useful. ~~EBE123~~ talkContribs 22:56, 14 May 2011 (UTC)
- So, a tool for featured article, picture, portal, list, topic, sound, and good topic nominations. Would it get that much use, though? Someone who has prepared an article for FA will be prepared to nominate it manually - I would think that having a tool to do this would promote lots of WP:SNOW nominations from misguided newbies, etc. In other words, I just can't see that a tool for this would be worth it. — This, that, and the other (talk) 08:03, 15 May 2011 (UTC)
- Seconded. FA nominations aren't routine maintenance work, and thus seem to warrant extra attention when being made. SchuminWeb (Talk) 13:06, 15 May 2011 (UTC)
Adding loging capabilities
How about updating twinkle to be able to log all of the proposed PRODs and CSDs. There is 2 codes (User:Timotheus Canens/twinklespeedy.js, User:Timotheus Canens/twinkleprod.js) that can do that but now, I would want a merge so that le same buttons will not appear 2 times, and it should be useful for evreyone. ~~EBE123~~ talkContribs 18:37, 14 April 2011 (UTC)
- It's on my to-do list. — This, that, and the other (talk) 04:24, 17 April 2011 (UTC)
Moved to here by ~~EBE123~~ talkContribs. 22:56, 14 May 2011 (UTC).
- It's now on my "done" list, and will appear on-wiki soon. Note that the logging feature is opt-in only for the moment; I believe part of the original proposal was to have it enabled by default, but I think this would require greater consensus (as it amounts to letting the general public into some of your deleted contributions, which some users may object to). — This, that, and the other (talk) 07:58, 15 May 2011 (UTC)
- It wasn't meant to be default. But how to opt-in? ~~EBE123~~ talkContribs 18:59, 18 May 2011 (UTC)
- All will be revealed shortly, upon roll-out. — This, that, and the other (talk) 01:54, 21 May 2011 (UTC)
- It wasn't meant to be default. But how to opt-in? ~~EBE123~~ talkContribs 18:59, 18 May 2011 (UTC)
- It's now on my "done" list, and will appear on-wiki soon. Note that the logging feature is opt-in only for the moment; I believe part of the original proposal was to have it enabled by default, but I think this would require greater consensus (as it amounts to letting the general public into some of your deleted contributions, which some users may object to). — This, that, and the other (talk) 07:58, 15 May 2011 (UTC)
Actually, could it be also for Advance Reporting and Vetting, RPP, and XfD too. Could it? ~~EBE123~~ talkContribs 18:31, 23 May 2011 (UTC)
- But you can use your contributions for those, as they are never deleted, like CSDs and PROds are. — This, that, and the other (talk) 00:28, 26 May 2011 (UTC)
Correctly add links to categories
When adding a warning or such with a link to a category, Twinkle adds a colon in front of the link to stop the page being added to the category; however, it always adds a colon before a link so when the link is to a category, it adds two colons, making one of those colons visible. For example, User talk:220.127.116.11. McLerristarr | Mclay1 14:03, 15 May 2011 (UTC)
- Hm - that is interesting. While the IP user you cited is now a moot point for 60 hours, the problem is intriguing. I would hazard a guess and say that a colon is hardcoded into the template as well as in Twinkle, and the two interact. If we can ensure that the colon is always hardcoded into the templates in every instance, I believe we could probably remove it on Twinkle, solving the problem (as long as my theory is actually the case). SchuminWeb (Talk) 02:16, 16 May 2011 (UTC)
- Looking at Template:Uw-vandalism1, it does add a colon before the link. I'm assuming the other templates all do the same and if they don't, it could easily be added. The colon-adding feature of Twinkle could probably be removed then. McLerristarr | Mclay1 12:58, 25 May 2011 (UTC)
Notifying deceased Wikipedians
Twinkle was used to send a message to User talk:Rydel. Unfortunately User:Rydel passed away. He is listed on Wikipedia:Deceased Wikipedians. Sending a message about a PROD or about anything to a deceased user's talk page is pointless, to say the least.
This message has to be sent somewhere, however, and this is relevant not only to deceased users, but also to those who resigned or disappeared for other reasons. A clever solution would be to send such messages to someone who would designate himself as a "caretaker" for the departed user. --Amir E. Aharoni (talk) 08:24, 18 May 2011 (UTC)
- I believe that this is a policy issue that goes well beyond Twinkle. Get us some good, solid policy on the matter, and then it should be a pretty straightforward issue of programming Twinkle to follow it. SchuminWeb (Talk) 13:49, 18 May 2011 (UTC)
- In such cases as these, the user talk page in question is normally fully protected. Non-admins cannot edit fully protected pages, not even using Twinkle, and (after the shortly forthcoming Twinkle rollout) admins will be warned before Twinkle edits a protected page for them. As SchuminWeb says, there needs to be policy on this matter, but the status quo as I see it is that protection is the solution. — This, that, and the other (talk) 07:38, 19 May 2011 (UTC)
- Generally though, several editors have asked for some kind of opt-out mechanism before. I previously thought about allowing the recipient of a Twinkle message to define some options.
Besides an opt-out (for selected messages or for all), a user may e.g. want to define how talkback messages are left for them (by a specific template, or only by a dummy edit with all information in edit summary). The idea to allow forwarding some twinkle notification messages to another user is also interesting (although the 'caretaker' will probably watch the relevant talk page anyway, so it makes little difference in practise).
Amalthea 09:08, 19 May 2011 (UTC)
- Generally though, several editors have asked for some kind of opt-out mechanism before. I previously thought about allowing the recipient of a Twinkle message to define some options.
Add Template:Cleanup-link rot
Can we get {{Cleanup-link rot}} added? -- Alan Liefting (talk) - 21:09, 19 May 2011 (UTC)
- See #Additional maintenance templates above. — This, that, and the other (talk) 07:09, 20 May 2011 (UTC)
Add Template:bareurls
Can we add tagging articles with {{bareurls}}. At the moment I don't see this template in twinkle. mabdul 15:28, 23 May 2011 (UTC)
- See above. It is the same request. ~~EBE123~~ talkContribs 18:41, 23 May 2011 (UTC)
- Oh thanks. Didn't know that link rot is the same template. (I always can't remember the correct title ;p) mabdul 08:25, 24 May 2011 (UTC)
Opening talk pages
When reverting edits, Twinkle displays text saying something along the lines of "Opening talk page of user", yet it never actually does this. Is the text a left-over from an old feature or a precursor to a new feature? Or perhaps the talk page not opening is a bug or a bug specific to my browser, Safari? McLerristarr | Mclay1 07:41, 25 May 2011 (UTC)
- It ought to happen. Perhaps you might need to turn off Safari's popup blocker - it appears that Safari lacks a way to add exceptions for its popup blocking functionality. — This, that, and the other (talk) 10:44, 25 May 2011 (UTC)
- Thank you. Yes, it works when I turn the pop-up blocker off. Quite irritating that. McLerristarr | Mclay1 12:54, 25 May 2011 (UTC)
Edit summary wording
When selecting "G6: History merge" from the CSD menu, the edit summary is populated with "Requesting speedy deletion (CSD G6)" (example). The {{db-histmerge}} template was recently modified so that the word "delete" no longer appears anywhere in the tag ([7]), so I was wondering if the edit summary could be changed to "Requesting history merge (CSD G6)". I think the "speedy deletion" text in the edit summary might be misinterpreted by good-faith editors who are not aware of the necessity of using the move function versus cut/paste moving. —KuyaBriBriTalk 19:17, 26 May 2011 (UTC)
Template:Uw-coi-username would be useful to have available through Twinkle. I like the template and need it for some of what I do, but I have to do it by hand. Having it in TW would be better (it would be a single issue notice). Raymie (t • c) 19:55, 26 May 2011 (UTC)
- It's already listed under "single issue warnings" -- John of Reading (talk) 20:00, 26 May 2011 (UTC)