Wikipedia talk:Twinkle

"WT:TW" redirects here. For other uses, see Wikipedia talk:Transwiki log, or the WikiProject Taiwan talk page.

Go to user talk when reverting pending changes

When a page is reverted with the pending changes "Revert changes" button, Twinkle should give a nice link to go to the user's talk page with the page name pre-filled, like it does when "real" rollback is used. Jackmcbarn (talk) 04:35, 11 January 2014 (UTC)

I'll look into this. I only have reviewer rights on testwiki, so I hope our setup is not too different. — This, that and the other (talk) 02:17, 1 February 2014 (UTC)

@Jackmcbarn: Hm, I'm not quite sure what you are referring to here. When I clicked "Reject changes" I seemed to get sent back to the article itself. — This, that and the other (talk) 06:14, 15 February 2014 (UTC)

A link from the confirmation page, I mean. Jackmcbarn (talk) 23:03, 15 February 2014 (UTC)

Being hopelessly inexperienced with Pending Changes, I will need step-by-step instructions of every click you are making :) — This, that and the other (talk) 02:52, 16 February 2014 (UTC)

Jackmcbarn (talk) 18:31, 16 February 2014 (UTC)

So you want to see a talk page link even before you have made the revert? That seems like a strange order in which to do things. — This, that and the other (talk) 06:41, 18 February 2014 (UTC)

Yes. I know that's kind of strange, but after the revert is made, there's nowhere to put the talk page link. The other alternative is to make the user's talk page pop open in a new window after the revert, the way that it does when you use Twinkle's own rollback to revert someone. Jackmcbarn (talk) 13:27, 18 February 2014 (UTC)

@Jackmcbarn: Sorry Jack, I missed your reply. Yes, a popup wouldn't be a bad idea, although I'm hesitant to add another one. I'll see what is possible here and think about the best way to implement it. — This, that and the other (talk) 07:26, 3 March 2014 (UTC)

Threadcromancy, but I would suggest using popups to direct you quickly to their user talk page. You'll have to copy the page name manually, but it's nonetheless faster than clicking and clicking repeatedly. --k6ka (talk | contribs) 22:09, 28 April 2014 (UTC)

I don't want to see the vandal's talk page, but I would like this bot to automatically create a talk page for the vandal, if necessary, and post a notice on the vandal's talk page that they did something offensive. In my recent use of this bot, no notice was posted on the vandal's talk page; apparently because there was no existing talk page for the vandal. - Ac44ck (talk) 19:11, 3 May 2014 (UTC)

Stuff

...for lack of a better heading.

• The preferences panel at Wikipedia:Twinkle/Preferences nowhere states that twinkle preferences are actually stored on a wiki page, and are hence public (unlike the mediawiki preferences). A js-savvy user could easily understand what they mean (and even a not-so-savvy user could copy-paste someone else's preferences and then go to the twinkle preferences panel). Also, the page doesn't mention that the prefs will be released under the default wikipedia license. (Not sure if there's a copyright/privacy violation in there anywhere, but you might want to look into this.)
• Someone might want to take a look at this commit I did downstream back in 2012. It includes a function to softcode namespace names in regex creation for the unlink tool in morebits.js. Devs may want to properly implement that upstream. The benefit would be that the regex would work on any wikipedia without problem.
• There's a script at hi:User:Siddhartha Ghai/twinkle.js which loads for me a personal version of twinkle from various user subpages. The only difference from the gadget version is that the header and footer have been kept separate. Devs might want to consider separating them again since using this script, changes in one module can be tested easily with the other live modules (i.e copy one module to your userspace, make some changes, use hi:User:Siddhartha Ghai/twinkle.js to load the default gadget, only replacing the changed module with the userspace subpage instead of the mediawiki page) and you can test the changes live!
• Over the past 1.5 months I've done a lot of updates to the gadget at hi.wp (stuff dating from May 2012 to October 2013). I'm just giving a heads up since I may have to take a long wikibreak and if the gadget breaks there, someone might complain here. Anything that was implemented after mid-October hasn't been implemented there (including the mediawiki js deprecations removal)
• Oh, and it seems that Jimbo uses Twinkle too, in case any of the devs ever want to do an April Fool's prank for users in the founder group ;) --Siddhartha Ghai (talk) 16:14, 27 April 2014 (UTC)

Wow, even Jimbo Wales uses Twinkle? Man, this is just reason enough to get all autoconfirmed users in good standing to get Twinkle, even if they're not planning on using it often. It's just an awesome tool. --k6ka (talk | contribs) 21:51, 28 April 2014 (UTC)

I'm considering adding a line to the top of the preferences panel saying "Note that your preferences will be released publicly as JavaScript code in a subpage of your user page." Thoughts? Eman235/talk 06:01, 1 September 2014 (UTC)

If you really want to do it, perhaps something less technical would be better: "Note that your preferences are stored in (a subpage of your user page). Only you (and Wikipedia administrators) can modify your preferences, but the settings you choose are visible to everyone." — This, that and the other (talk) 12:10, 1 September 2014 (UTC)

And now the {{-}} is boggling me. If this note is going to be put in I don't think I can do it. Eman235/talk 00:38, 3 September 2014 (UTC)

*slaps self* never mind, figured it out. I made a slight change to the wording mention that it is JavaScript, not blatant text -- dunno what you think of that -- but yes, item one in this list is amended, kind of. Eman235/talk 00:48, 3 September 2014 (UTC)

Custom tags for non-article namespace

Is there a way to make custom tags (such as I use on User:Jo-Jo Eumerus/twinkleoptions.js) appear in the Twinkle menu even in non-Main namespaces? Such as File.Jo-Jo Eumerus (talk, contributions) 16:16, 4 April 2016 (UTC)

• Pinging @MusikAnimal: so that this doesn't get lost.Jo-Jo Eumerus (talk, contributions) 14:54, 12 April 2016 (UTC)

  Sorry, I'll look into this when I can, got a backlog of other work to take care of first. I've instructed the bot not to archive this thread. Best — MusikAnimal ^talk 15:36, 12 April 2016 (UTC)

Children's personal info

The emerging consensus of this discussion at Wikipedia talk:Criteria for speedy deletion is that kids' personal information needs to be oversighted. I'm sure I'm not the only editor who has viewed this material in terms of deletion (U5, A7, G11, G10) in the past. Could we have another option on Twinkle's CSD menu to handle this properly by initiating an oversight request, Special:EmailUser/Oversight, pre-populated along the lines of "Child's personal info at articlename"? Thanks, Cabayi (talk) 10:46, 16 August 2017 (UTC)

Please, please, please! Legacypac (talk) 12:43, 16 August 2017 (UTC)

+1. Lowering the action threshold for this is a big win in terms of ensuring that issues like this get dealt with not by shining a huge spotlight on it (as there are several known cases of nominating for CSD immediately triggering bots to scrape the data and store it on one of numerous SpeedyDeletion wikis) but to make it easier to privately request oversight is a big win. Hasteur (talk) 12:59, 16 August 2017 (UTC)

• +1 but not limited to child personal data. Twinkle should offer an "email oversight" tab that contains common reasons for oversight or allows entering a custom reason. Regards SoWhy 12:30, 17 August 2017 (UTC)

• Support offering Twinkle-users a clear and simple way to report stuff which needs to be oversighted. If Oversighters find they are getting sent too many reports for non-oversight-worthy content, then the documentation at Twinkle can be fine-tuned to clarify what does and doesn't need to be reported. PamD 13:07, 17 August 2017 (UTC)
• There should be language to specify content needs to be removed before oversight is contacted. I'll save everyone my rant about how much content that should be rev del'd or oversight gets through NPP, but the goal should be to hide the content from the general public as quickly as possible, which requires the editor remove it before waiting what can be hours before an oversighter responds. TonyBallioni (talk) 13:28, 17 August 2017 (UTC)

Just blank the personal details on sight, that should remove them from view and hide them from most of the general public and scrappers, who don't know enough to look in the page history, up until the Oversighter fully blocks them. Diego (talk) 14:04, 17 August 2017 (UTC)

Yes. I know: I'm saying Twinkle should make that clear. A lot of people don't know that, though, so education is key here. TonyBallioni (talk) 14:21, 17 August 2017 (UTC)

• Support, streamlining the processing of content that needs to be removed for BLP reasons is a good thing. Diego (talk) 14:04, 17 August 2017 (UTC)
• Support per above, but the Oversight team should be made aware of this discussion as this will probably lead to a significant increase in requests and associated decrease in response time, perhaps to unacceptable levels. We may need more oversighters. – Train2104 (t • c) 14:18, 17 August 2017 (UTC)
• Support. This seems like a very valuable use of the developers' time, for the reasons above. Matt's talk 19:05, 17 August 2017 (UTC)
• Support - Including Primefac's RevDel option below. - FlightTime (open channel) 01:42, 18 August 2017 (UTC)
• Support Good idea. Chris Troutman (talk) 03:36, 18 August 2017 (UTC)
• Support apap04 ^{talk | contributions} 22:18, 30 September 2018 (UTC)

Revdel?

Can we add in revdel support as well? I completely understand the importance of a subtle oversight, but revdel is just as important and Twinkle could make such a task much easier. I hate to piggyback on a somewhat-separate topic, but it's been proposed three times now with zero comments from others. Primefac (talk) 01:29, 18 August 2017 (UTC)

• Yes. Yes. 1000x Yes. For all the reasons I noted above. TonyBallioni (talk) 03:02, 18 August 2017 (UTC)
• Support Chris Troutman (talk) 03:36, 18 August 2017 (UTC)
• Strong support for both - the average editor doesn't need to concern himself with the differences between oversight and revdel. I've been at this near 6 years and I'm not sure which is appropriate when, mainly because I don't need to be. Editing school articles primarily as I do, I come across "Tammy Foo is a slut" or "Bill Foo has a huge cock" almost daily. Making a revdel request easier would be a blessing. John from Idegon (talk) 15:36, 18 August 2017 (UTC)
• Support both - I've had to mosey over to IRC I believe four times in the past two days over these types of things. TimothyJosephWood 10:46, 25 August 2017 (UTC)
• Support both - I've had to google "copyvio revdel template" far too many times now. Gone shall be those days. 100% support from my side. Jiten Dhandha • talk • contributions • 11:21, 5 September 2017 (UTC)
  • @Timothyjosephwood and Jiten Dhandha: it's not perfect, but until the above gets implemented I've written up User:Primefac/revdel.js. Just add importScript('User:Primefac/revdel.js'); // Linkback: [[User:Primefac/revdel.js]] to your common/vector/etc. Should help with that pesky "what's the code" issue. Let me know if there are any major issues, or other ways I could improve it further. Primefac (talk) 16:21, 8 September 2017 (UTC)

There is absolutely no way I'm going to figure out how to do that without accidentally deleting my entire account. TimothyJosephWood 16:37, 8 September 2017 (UTC)

@Timothyjosephwood: Click this link: Special:Mypage/common.js > (Create the page if not already existent) > Edit page > Copy code exactly the way Primefac mentioned in the comment above > Hit "Save changes" and voila! :P Jiten Dhandha • talk • contributions • 16:51, 8 September 2017 (UTC)

Jiten Dhandha, TJW doesn't have a common.js ;) Primefac (talk) 17:16, 8 September 2017 (UTC)

@Primefac: I havent tested it yet, but I did add the code to my common.js. The prompts look simple and neat so there's no issue there (I see that only 4 ranges are allowed at max, which isnt an issue since I've never come across an article needed more than that). Now to see if it actually works when I come across an article with copyvio issues. Also, thanks for taking the time out to write the script! Jiten Dhandha • talk • contributions • 16:43, 8 September 2017 (UTC)

• Support Sam Sailor 23:30, 13 September 2018 (UTC)

Feature request for easier warnings

Many years ago, I extracted a chunk of Twinkle code and modified it. It added a link next to the user on both sides of every diff. Clicking on it took me to the user's talk page, where I could then warn them, with the relevant article title automatically supplied.

A recent MediaWiki change broke this. Rather than figure out how to fix it, I thought I would put in a feature request for it to be implemented for everybody. For all those years, I've always found it to be extremely useful, and I'm sure many other users will appreciate it, too.

A slightly less convenient alternative would be an option to always display a "welcome" link in diffs, whether or not the user's talk page exists. Then you could click on it, but issue a warning instead of a welcome. MANdARAX • XAЯAbИAM 21:26, 27 September 2018 (UTC)

It is tremendously helpful to be able to warn a user from a diff, with the page title filled in automatically. For example, you restore to a previous version and want to warn each of the participating vandals. Or you see that someone else reverted vandalism and you want to issue a warning that they neglected to do. Without this feature, you have to copy and paste, or type in, the page's title, which is inconvenient, and sometimes leads to errors. Or, worse, people issue a warning without bothering to take the extra time to fill in the relevant page name. MANdARAX • XAЯAbИAM 09:48, 3 November 2018 (UTC)

Edit warring

Hi, When I file an edit warring report - I fill out everything as normal .. but when I click "submit query" it just blanks out - Nothing happens and repeating it still does nothing,
Thanks, –Davey2010^Talk 18:48, 19 October 2018 (UTC)

Not sure what the issue was but it now seems to have been fixed as edit warring reports go through no probs - Thanks to whoever had fixed it, Thanks, –Davey2010^Talk 20:20, 22 October 2018 (UTC)

This is most likely because of phab:T197486, which is beyond our control. Basically the API query the edit warring report module uses will sometimes time out. It will work for some users, other users it will not. The current belief is an upgrade of the database servers will fix it but there's no indication of when this will happen. Sorry! — MusikAnimal ^talk 18:51, 8 November 2018 (UTC)

RPP function bug

When I request PP for a page with twinkle, it adds to WP:RFPP "=== [[:Example]] === * {{pagelinks|Example}} " and then the reason and the sig. This should be changed to add |1=Example instead of |Example, because when RPPing a page with an equal sign ("="), it breaks the template. See this diff for the problem when requesting page protection of 2 + 2 = 5. L293D (☎ • ✎) 13:49, 24 October 2018 (UTC)

Fixed. ~ Amory (u • t • c) 22:17, 5 November 2018 (UTC)

Nomination of Template:New unreviewed article

I have nominated Template:New unreviewed article (which is used in twinkle) for deletion; see discussion. Galobtter (pingó mió) 06:24, 30 October 2018 (UTC)

The template discussion has now been closed as "delete" so please make changes to Twinkle as necessary as I am going to start to orphan the template. Pkbwcgs (talk) 06:51, 7 November 2018 (UTC)

Template:New unreviewed article has still not been removed from Twinkle's "tag" tab. Pkbwcgs (talk) 17:07, 8 November 2018 (UTC)

It should be deployed soon, I've pushed the commit to the repo. --QEDK (後 ☕ 桜) 17:19, 8 November 2018 (UTC)

 Done Deployed. --QEDK (後 ☕ 桜) 14:00, 11 November 2018 (UTC)

Batch mode?...

Currently TWINKLE works on a per page mode, However in some instances (Such as image review) this means that a contributor ends up with a "wall of notifications", which has been described as annoying and can be counter productive. (Some templates like Bsr already support multiple images in a single notifcation.)

At WP:VPT there is currently a request to port Visual File Changes from Commons back to English Wikipedia. This is something that should be combined with a rewrite and extension of TWINKLE so that it can be used in a "batch mode" and thus a contributor need only get one (albiet a large) notification about pages or media with a specific issue.

Ideally, a fully developed batch mode would enable a contributor to patrol through an entire list of pages or media ( such as those in a category), and as well as batch tagging the pages media with the appropriate issue templates, TWINKLE would group up any required notifcations that are needed into appropriate batched notifications (i.e one notification per user on a specfic issue) or better one composite summary notification with sections (ideallyu comprising collapsed lists or tables of pages or media affected) for the relevant issues. This would let contributors and patrollers that do 'sweep' style efforts to generate ONE notifcation to a contributor or uploader instead of several, and thus avoid "wall of enforcement" notifcations that aren't necessarily going to be read. ShakespeareFan00 (talk) 22:07, 2 November 2018 (UTC)

This would require a lot of rework and would work better in a different tool, and we would need someone who wants to make such a mode. Twinkle is meant as a jack-of-all-trades and less as a specialized tool. --QEDK (後 ☕ 桜) 17:44, 5 November 2018 (UTC)

Such a mode is needed to reduce the incidence of 'tag-bombs' where an admin or patroller needs to make a LOT of notifications. Rather than leaving a LOT of virtually identical and lengthy notifications, wouldn't it be better to consolidate the notifcations into a single list, and send ONE notification instead? (Which is what Visual File Changes on commons achieves)ShakespeareFan00 (talk) 09:44, 7 November 2018 (UTC)

The problem is you're equating Commons need with Wikipedia's. On Commons, a person can uploads 100 copyrighted images and then the need to delete them all arises. Then a tool to notify the editor once and also do the other work is needed. That doesn't happen on Wikipedia often, if any. You cannot create 100 pages that are all eligible for speedy at the same time, the reason is obvious and hence lack of need of such tool.–Ammarpad (talk) 12:04, 7 November 2018 (UTC)

Tray notifcations vs Talk Page messages

In follow up to the above, is there a reason why Twinkle uses Talk page notifcations, rather than tray notifications for some issues related to media files?

I've sometimes been more quick to respond to tray or bell notifications, than I am to changes I only notice due to watchlisting some media file.ShakespeareFan00 (talk) 22:10, 2 November 2018 (UTC)

Also Some users don't want to be bothered by boiler plate messages on a talk page, but would like to be aware of when pages they've edited have changed, or media they've upload has been tagged in specific ways. using tray or bell notifications would in these instances be more appropriate. Rather than a talk page message for say a file being tagged for CSD F4. You'd get a "tray notifcation" giving a link to the media file, and the CSD criteria that needed resolving. ShakespeareFan00 (talk) 22:16, 2 November 2018 (UTC)

Template:checkuserblock-account

Hi, I've sandboxed a change to this template so that it supports a duration parameter. It is sometimes used when blocks aren't indefinite! So this note is twofold - firstly, consensus for the change, and secondly, the new parameter might want building into Twinkle at some point. ∰Bellezzasolo✡ Discuss 21:34, 3 November 2018 (UTC)

Most CSDs not being added to log

I've noticed that when tagging a file for dated speedy deletion, that the process box gets stuck on "Adding entry to userspace log: Retrieving page..." and never adds to the CSD log or even closes. All OK for a normal CSD. Is this a bug or my setup gone awry? Ronhjones  ^(Talk) 00:53, 4 November 2018 (UTC)

I bet your log is too long. Go to User:Ronhjones/CSD_log and move it to User:Ronhjones/CSD_log 1 then go back to User:Ronhjones/CSD_log and replace the #REDIRECT with See also: so people can follow the link to the older log but you will not send the script there. Everything will greatly speed up. Repeat every thousand or so CSDs. Legacypac (talk) 00:58, 4 November 2018 (UTC)

Only 3 items in log User:Ronhjones/CSD log. I thought of that already. Ronhjones  ^(Talk) 00:35, 5 November 2018 (UTC)

Have you cleared the cache? Is logging enabled for the criteria you're nominating under? --QEDK (後 ☕ 桜) 18:31, 6 November 2018 (UTC)

As one can see in User:Ronhjones/CSD_log, it's quite happy logging F9 CSD, I just tried another F11, and it gets as far as "Adding entry to userspace log: Retrieving page..." and then nothing happens, window never closes. Settings are to log all CSD except U1. Ronhjones  ^(Talk) 19:12, 8 November 2018 (UTC)

This bug crept in in September as part of an effort to improve CSD logging. Let's see. SD0001 (talk) 19:46, 12 November 2018 (UTC)

 Fixed The fix should be deployed soon. SD0001 (talk) 21:40, 12 November 2018 (UTC)

Do not mark as 'patrolled' when adding CSD tag.

Per this discussion, we are going to stop marking CSDs and PRODs as 'reviewed' in the new pages feed at New Page Patrol, to stop things falling through the cracks if the CSD tags are inappropriately removed or the PROD removal is missed.

Twinkle currently does not mark PRODs as 'patrolled' but does mark CSDs as 'patrolled'. We need this to change so that CSD's are no longer marked as 'patrolled'. — Insertcleverphrasehere ^{(or here)} 16:58, 4 November 2018 (UTC)

Insertcleverphrasehere, it's already an option (like I already told you). Cabayi (talk) 17:16, 4 November 2018 (UTC)

Yes, but not marking as reviewed should be the default. — Insertcleverphrasehere ^{(or here)} 17:28, 4 November 2018 (UTC)

 Done This has been deployed. — MusikAnimal ^talk 16:16, 5 November 2018 (UTC)

Feature request

Is there any way to add warnings via Twinke to folk who repeatedly jump the ACPERM queue. In this instance where the article has been moved from Draft to article space, moved back to Draft as it has a canker, then moved back to article space. I would like to warn the editor. I don't even know if this is policy. But it needs to be stopped, as it is a waste, unproductive, and pushes terrible article into article space, that shouldn't be here. If this is not the place to post, please tell me. Thanks. scope_creep (talk) 12:28, 7 November 2018 (UTC)

Problem when clicking on "vandalism" link while examining user contributions

I am seeing a problem when clicking on the "[vandalism]" rollback link while examining user contributions. The link does not perform a rollback – instead, it tries to create a new article called with the old article name plus "&twinklerevert=vand" tacked on the end. Binksternet (talk) 21:41, 10 November 2018 (UTC)

I'm having the same issue. - FlightTime Phone (open channel) 21:50, 10 November 2018 (UTC)

Consider making an issue on the GitHub repository. --QEDK (後 ☕ 桜) 14:00, 11 November 2018 (UTC)

This also occurs for the normal rollback feature on Twinkle, both on PC and mobile. aNode (discuss) 16:30, 11 November 2018 (UTC)

Sorry, I cannot make heads or tails the git cite. - FlightTime Phone (open channel) 16:48, 11 November 2018 (UTC)

I have just used the Vandalism feature, and also the normal rollback and Good faith rollback on TW, and it all seems to be working fine for me. Orphan Wiki 21:00, 11 November 2018 (UTC)

@Orphan Wiki: This issue only affects the "rollback" and "vandalism" links on a user's contributions page. The ones seen when viewing a diff are working fine. —k6ka 🍁 (Talk · Contributions) 23:49, 11 November 2018 (UTC)

@Binksternet, K6ka, and FlightTime Phone: what browser and version are you using? — MusikAnimal ^talk 02:10, 12 November 2018 (UTC)

Never mind, it's not your browser (broken on modern browsers too). We're looking into it. — MusikAnimal ^talk 02:15, 12 November 2018 (UTC)

Thanks in advance. Binksternet (talk) 04:11, 12 November 2018 (UTC)

Subtle Vandalism Template

Hi there! I think Twinkle should have a subtle vandalism template. The message it gives is different than the regular vandalism template. Should Twinkle add this template? INeedSupport^{(Care free to give me support?)} 18:10, 12 November 2018 (UTC)

Remove links to everywhere

I've never used the "remove links from everywhere" yet I think I have a case for it, so I'm getting some feedback before hitting a button that will cause hundreds or possibly thousands of edits (just about 1200).

WP:Articles for deletion/GameZone resulted in a delete for notability reasons (and I think that deletion was correct). It is currently linked in several hundred or thousand pages for its use as a cited work. What is the edit rate at which this occurs (possibly add to WP:Twinkle/doc)? From the image, it does not look like the edits are tagged with a bot tag. Given the number of links, would it be more reasonable to remove the redlinks with a bot (or at least, a bot account)? I guess it also does not distinguish between links in main and outside mainspace (I get to choose which pages are executed against). --Izno (talk) 16:49, 14 November 2018 (UTC)

Vaguely related discussion back when it was actually deleted; Username Needed did around half a thousand at the time, possibly through XFDC. AFAIK the edits will happen as quickly as possible ~ Amory (u • t • c) 18:54, 14 November 2018 (UTC)

Twinkle dropdown in Vector

My section of the same name was archived with no response. Should I post this issue somewhere else? ♫ekips39 (talk)❀ 05:59, 17 November 2018 (UTC)

Feature request - Peer review

I am wondering if it's possible to add a feature to Twinkle to close peer reviews. This would need to do two things, and ideally would have an additional option to leave a message. Process planned would be:

1. Reviewer goes to a peer review page, then selects "Twinkle - close review"
   • Ideally, an option will be given for the reviewer to input a message or select from a dropdown menu of options for why the review is closed, with a message added to the peer review page: closed for inactivity (autoselected), closed as direct nomination (in which case this shouled be included at the end of the peer review page: {{Wikipedia:Peer review/Direct nomination| --~~~~}}, or can leave an individualised message
2. Twinkle will:
   • On the peer review page, replace {{Peer review page|topic = X}} with {{subst:PR/archive}}
   • On the article's talk page, replace the {{Peer review}} tag on the article's talk page with {{Old peer review|archive = N}}, where N is the number of the peer review discussion page above (e.g. 1 for /archive1).
3. An optional feature to include would be to insert this peer review in the article {{Article history}} template on the talk page if there is one.

Such a feature would be MOST appreciated by peer reviewers and save us a lot of time :). --Tom (LT) (talk) 08:01, 18 November 2018 (UTC)

Wishlist proposal on one-click inline cleanup tags

It would be easier to do this with Twinkle

The current Wishlist Survey has a proposal to make it as easy to tag (with "citation needed" etc.) as it is to rvv. This should be faster than writing custom comments in a good-faith revert, and there is evidence[1] that it will cause more new editors to fix their own edits, learning editing skills in the process. Please consider voting on the wish. HLHJ (talk) 19:12, 18 November 2018 (UTC)