Wikipedia:Page Curation/Suggested improvements/Archive 1

For ease of navigation, this archive is for the first 50 suggested improvements numerically, not the first 50 to be archived --DannyS712 (talk) 03:09, 13 September 2019 (UTC)

1. Page curation tool: 'No problems'

Done

Tracked in Phabricator Task T147220 Resolved This request has not been resolved as of 15 June 2017. In the "Page info" section of the toolbar, there is a subheading "Possible issues" which contains the text No problems have been found for this page so far. if there are no maintenance templates currently on the page. This is misleading and has no apparent function. Either list the problems that have already been automatically identified and listed on the New Page Feed, or just remove from the Page Curation flyout entirely. Originally brought up by Kudpung Augist 2012. Some talk, not done.--Kudpung กุดผึ้ง (talk) 00:59, 8 September 2016 (UTC) I've edited the first sentence in your explanation for clarity, to explain where the confusing message is found and what it does. Quiddity (WMF) (talk) 18:36, 3 October 2016 (UTC) @Quiddity (WMF) and Kaldari: still not done although listed at Phab. Perhaps they don't undersand what is required.--Kudpung กุดผึ้ง (talk) 08:40, 26 November 2016 (UTC) The request is easy to understand. Kaldari (talk) 22:41, 28 November 2016 (UTC) This has been completed and will be deployed on June 20 — MusikAnimal talk 03:01, 15 June 2017 (UTC)

3. Feed symbols

Done

Pages tagged for deletion by PROD, BLPPROD, CSD, or AfC, and pages taged for COPYVIO and NOTENGLISH, sgould be shown with the dustbin (AE: trash can) icon, and not the green 'checked' icon. It should be obvious that this would enable admins who are patrolling the quality of the patrollers themselves rather than new pages, can either immediately delete hose pages, or - just as importantly - revert any tags that have been inappropriately or erroneously applied, and then use the 'unreview button' which should then send the 'unreviewed' message automatically to the patroller, using a dropdown list of canned reasons. Kudpung กุดผึ้ง (talk) 04:39, 4 September 2016 (UTC) Support - This is very important. In fact, there should also be an indication of the type of deletion nomination (rather than a generic trash can) and the user name of the patroller who tagged it as such. I will propose this separately.- MrX 13:08, 16 September 2016 (UTC) Comment - I have come to feel that placing an AfD control in the NPP system is counterproductive. If a page is totally inappropriate for Wikipedia, it should be tagged for speedy deletion and kicked straight over to an admin to think about. If it's debatable, we should tell people to message the creator saying that they think the page has problems before they do anything, or draftify it. That could help avoid debacles like some dumb deletion listings I made when I was starting to do NPP, or more recently this one where the page creator just hadn't finished writing the article when it was sent to AfD. (Obviously the flip side to that is that there would probably be more CSD nominations, but they'd get rescinded immediately if inappropriate rather than becoming a deletion discussion that drags out for weeks.) Blythwood (talk) 03:05, 7 October 2016 (UTC) Blythwood, This section is for suggesting icons to be added or improved in order to privide a greatr overview of the content and status with out unduly cluttering the list entry or the feed itself. Our mission is to make Pace Curation sufficiently user friendy in order to attract suitably qualified editors to apply for the user right. Kudpung กุดผึ้ง (talk) 06:28, 9 October 2016 (UTC) Unless I'm misreading it, this has been implemented, right? – Joe (talk) 16:14, 2 February 2017 (UTC)

5. Very short article

Done

Tracked in Phabricator Task T157054 Resolved Any new pages that contain only one body section with less that 100 words or 700 characters (both parameters debatable here) or only contains an infobox and/or an image, should be displayed with a red alert alongside those for 'no citations' etc., as stub. Kudpung กุดผึ้ง (talk) 05:03, 4 September 2016 (UTC) Soon to be resolved. Through the ORES classification being added to SpecialNewPagesFeed. — Insertcleverphrasehere (or here) 21:33, 20 August 2018 (UTC)

7. Recreations

done

Tracked in Phabricator Task T189929 Resolved New pages feed should display if the new page is a recreation of a previously deleted page. First suggested by Carcharoth in 2012, the reasons for this alert should be obvious but previous suggestions for this were not considered by the Foundation to be important. Kudpung กุดผึ้ง (talk) 21:54, 7 September 2016 (UTC) Support I mentioned this below in Additional tools before I noticed the suggestion here. This is high importance. As an interim solution we should suggest all NPP reviewers install User:Writ Keeper/Scripts/deletionFinder.js JbhTalk 14:26, 2 October 2016 (UTC) Support - Many of these pages would need to be speedy deleted - if the original page was speedied, then the same criterion may apply; and if the original was deleted after an AFD discussion, then CSD G4 probably (although not necessarily) applies. עוד מישהו Od Mishehu 05:18, 6 October 2016 (UTC) Strong support--It will help NPP a lot.Winged Blades Godric 10:46, 17 February 2017 (UTC) Strong Support Thanks WBG for letting me know there's already a proposal here. This is one of the most irritating checks one has to do, After the quick fall, It's one of the most common criteria for deleting. Yashovardhan (talk) 09:49, 5 June 2017 (UTC) Support - This is an example of what triage actually means.- MrX 14:32, 15 June 2017 (UTC) UTC) Support - it's a check that would be easily automated that is currently awkward to do manually. Lineslarge (talk) 07:06, 25 September 2017 (UTC) Support Has this been done yet--if not, it is still needed. DGG ( talk ) 00:47, 17 March 2018 (UTC) Support. This should be implemented by searching the archive table using both the prefix (Special:Undelete fuzzy=0) and normal search (Special:Undelete fuzzy=1) instead of just looking for whether the title has deleted revisions or deletion log entries. MER-C 09:54, 15 April 2018 (UTC) Support To better address the triage purpose (well, sort/part of) it would be a great feature. Robertgombos (talk) 19:03, 1 June 2018 (UTC)

8. No Index until patrolled

Done

No indexing for search engines until an article has been successfully patrolled as appropriate for the encyclopedia. This is not the same as not allowing articles to be published such as at AfC. First suggested by WereSpielChequers and discussd in relative depth in 2912 here, it gained serious support, but possibly due the the community believing this to be a fait accompli, it received no further attention. This is possibly a policy issue and may need consensus from the broader community, although as a cross-Wiki critical issue it could be implemented by the Foundation if at least they could be persuaded of the necessity - especially today.Kudpung กุดผึ้ง (talk) 22:19, 7 September 2016 (UTC) There was in fact a RfC on this which gained consensus at [[1]]. As with many WMF promises to do it, they never did. --Kudpung กุดผึ้ง (talk) 10:45, 8 September 2016 (UTC) Support 1000x support! This would decrease the value of spam articles since there would be no SEO benefit. I would say this is one of the top 3 or so most important changes. JbhTalk 14:21, 2 October 2016 (UTC) @Kudpung: There is already consensus for this from the community: Wikipedia:Requests for comment/NOINDEX, and indeed this was implemented back in 2012. I have no idea why this is not working now, but I'll look into it. Kaldari (talk) 00:18, 5 October 2016 (UTC) It looks like this feature was disabled due to some problematic edge cases when articles were deleted and undeleted. I'll file a new task to get this resolved. Kaldari (talk) 00:29, 5 October 2016 (UTC) Thanks, Kaldari. It would be good if you could get this done fairly quickly.Kudpung กุดผึ้ง (talk) 11:38, 5 October 2016 (UTC) @Kudpung: I've submitted a patch to resolve this (and also the other part of Wikipedia:Requests for comment/NOINDEX, which was to noindex articles containing certain templates, such as speedy deletion templates). Once the patch is reviewed, merged, and live, I'll let you know and help set up the on-wiki configuration for the noindexing templates. Kaldari (talk) 06:38, 6 October 2016 (UTC) Great, thanks Ryan.--Ymblanter (talk) 07:06, 6 October 2016 (UTC) I've reviewed and merged Kaldari's patch. It'll be deployed as part of the weekly deployment on Thursday October 13th (in the evening hours UTC). --Roan Kattouw (WMF) (talk) 00:29, 7 October 2016 (UTC) Also: Kaldari mentioned the "noindex template" feature, which his patch also reactivates. The way this works is you'll be able to add a list of template names, separated by | (sorry) to MediaWiki:Noindex templates, and any page that contains any one of those templates will be noindexed. When you first set this up, it won't work retroactively, as pages only become noindexed when they are created, edited or (un)patrolled or purged; so any pages that already had one of these templates when the feature was activated won't immediately be noindexed. For the main use case that it was suggested for (speedy deletion tags) that shouldn't be too much of a problem, because those templates tend to have high turnover. Similarly, the "noindex unreviewed new articles" feature won't immediately apply to unreviewed new articles created before the feature was activated, but only when something happens to the article. --Roan Kattouw (WMF) (talk) 01:18, 7 October 2016 (UTC) MediaWiki:Noindex templates seems like a mistake. Shouldn't noindex templates be handled community-side by just adding __NOINDEX__ to the template itself? BTW this raises a question. What happens when an article has both __INDEX__ and __NOINDEX__? Alsee (talk) 12:01, 8 October 2016 (UTC) Good points, I'll play with putting __NOINDEX__ in a template and see what that does. I'll also investigate the index+noindex conflict situation you mentioned. --Roan Kattouw (WMF) (talk) 20:40, 8 October 2016 (UTC) Looks like __NOINDEX__ does not work when transcluded. We could look into making that work (which I agree would be a better solution than MediaWiki:Noindex templates), but we'd have to make sure that doesn't have unintended side effects for templates whose authors relied on this behavior (i.e. put a __NOINDEX__ directive in the template without bothering to protect it with <noinclude>). --Roan Kattouw (WMF) (talk) @Roan Kattouw (WMF), it is extremely surprising that __NOINDEX__ doesn't work when transcluded. I just did a search[2] for it in EnWiki template namespace. The community clearly believes this does work, with many templates deliberately including NOINDEX onto "problem" pages that we don't want indexed. Several templates have explicit logic to only apply NOINDEX in certain namespaces. We even have a template {{NOINDEX}} for this sole purpose, with nearly 200,000(!) transclusions. I skimmed the 136 search hits in template namespace and I only found one pair of templates that was mistakenly including NOINDEX onto a cluster of 10 articles pages. The template-pair was created as an editor's first attempt at template-editing. I fixed the problem. This definitely should be fixed. BTW, if you know why it doesn't work, or if you find out, I'd love to hear why. I haven't done much with templates, but everything I do know screams to me that this should work.... unless there's code explicitly (and mysteriously) filtering it out for some reason. Alsee (talk) 19:48, 10 October 2016 (UTC) @Alsee: Interesting! Yeah, the existence of Template:NOINDEX is a pretty clear indication that it's expected to work. It clearly doesn't though: I sampled Special:WhatLinksHere/Template:NOINDEX and most of them are noindexed, but that's because they're not in the main namespace (and so are noindexed by default); not one of the main namespace pages on that list is noindexed. I'll see if I can discover why this doesn't work, but I imagine double-underscore directives may not be transcludable in general. --Roan Kattouw (WMF) (talk) 16:36, 11 October 2016 (UTC) Circling back here from WP:VPT: it turns out there is a setting that completely disables __INDEX__/__NOINDEX__ in the main namespace. Mystery solved. We could disable that for the main namespace on English Wikipedia and put __NOINDEX__ in deletion templates, but we'd have to proceed carefully because we could accidentally noindex lots of pages that shouldn't be by lifting that restriction. --Roan Kattouw (WMF) (talk) 17:28, 12 October 2016 (UTC) Roan Kattouw (WMF), I'm not sure what's going on here, but the requireent is clear that new pages are NOT indexed untill they are patrollesd as OK without glaring issues. Pages tagged for any deletion process or for COI or COPYVIO will also remain NO INDEX until they are either deleted or allowed to stay. We volunteer editors are not necessarily interested in the technicalities of how the software is addressed to get these features finally implemented. What is absolutely clear, however, is that these features must be fully automated - we do not have manpower enough to manually Index/NOINDEX pages as well as all the other controls we have to do. Kudpung กุดผึ้ง (talk) 14:09, 8 October 2016 (UTC) @Kudpung: Sorry, let me clarify: once the feature is deployed on Thursday, you won't have to do any manual work to noindex pages that were created or tagged after Thursday, they'll be noindexed automatically. The only thing that won't be automatic is noindexing of pages that were created or tagged before Thursday. I expect the "tagged before Thursday" case is going to be low-impact, because as I understand it, the main use case is speedy deletion templates and those don't stay for long; but if I'm missing something here (e.g. longer-term templates), please explain and I'll see what can be done about it. As for the "created before Thursday" case, that will be annoying at first (although again, something we might be able to work around if it's a problem), but since the feature only works for 90 days that'll eventually be moot in January. (Reviewedness data is lost 90 days after creation, so we can't know if a page was reviewed past that point and have to stop noindexing it.) --Roan Kattouw (WMF) (talk) 20:38, 8 October 2016 (UTC) Roan Kattouw (WMF), thanks for the clarification. Tihs is an extremely important feature because for one thing, it will also act as a strong deterrent to Orangemoody style of attacks on the encyclopedia. There is nothing that can be done about pre-Thursday creations because they are already indexed by search engines and those SE listings can't be reverted, so it's too late for them unless of course a script can be devised to search the site for pages that still have the 'patroll thus page' or 'unpatrolled' on them and thre NOINDEX can be added - not that it would help much, though. What we have to ensure however , for the future, is that NO INDEX really works because a Google bot indexes our new pages within a few milliseconds. The pages to be NOINDEX are: All new mainspace pages except those from WP:Autopatrolled users and admins All new mainspace pages moved from mainspace from other namespaces except those from WP:Autopatrolled users and admins. New Drafts, user pages and sub pages, ~are I believe NOINDEX by defalt, but please check that this is so and is working. Most important: new pages that may be shown as patrolled but whee the patroller has added tags for: CSD all criteria COPYVIO (there are several different templates being used for this ranging from CSD to close-paraphrasing) including the ones applied automatically by the various duplication/copyvio detection bots. Articles not in English (such articles might have already been patrolled by patrollers who see no harm in foreign language articles and will pass them as patrolled. This might need some kind of language detector. The main offending languages are Arabic and Persian which often contain offensive political or religious propaganda, and Chinese, and occasionally articles in Cyrillic. I think if we can get all this done, we'll see a significant reduction in the number of unwanted articles and it will give the patrollers more breathing space, and us more time to investigate ways of recruiting new, more qualified patrollers.Kudpung กุดผึ้ง (talk) 02:37, 9 October 2016 (UTC) @Kudpung: I think we can do almost all of those things with the code that will ship on Thursday. Thanks for pointing out that the ship has already sailed on pre-Thursday creations because they've already been indexed anyway, I hadn't quite thought about it that way. As for your list: New page creations after Thursday should be noindexed automatically until they are reviewed (if created by autopatrollers, they become reviewed immediately). This'll be easy to verify on Friday by inspecting an unpatrolled page (the easiest way is to right click, "view source" and search for "noindex"). Pages moved into the main namespace: from #9. Pages moved to mainspace from other namespaces it sounds like those should work just like page creations. This could also be verified on Friday but someone may have to deliberately create a test case, I don't know if these occur commonly enough that you can just easily find an existing case. User pages and subpages appear to be noindexed (already, right now), but global user pages like mine aren't (probably a bug). Draft pages appear to already be noindexed as well. CSD, copyvio, etc.: please compile a list of templates that should trigger noindexing and add them to MediaWiki:Noindex templates, separated by pipes like so: Db-g1|Db-g2|Copyvio. You can do this at any time, you don't have to wait until after Thursday (although the noindex feature itself won't work until Thursday), and you can also add templates to this list later (but then only pages that are tagged with those templates after you've added them will be noindexed). As for articles in other languages: if patrollers are incorrectly approving those, then I think that's more of a social problem than a technical one. You may be able to get someone to write a bot/script to use a language detector to find such pages and tag them though. --Roan Kattouw (WMF) (talk) 00:55, 10 October 2016 (UTC) That all sounds very good, thank you Roan. Pages moved into the main namespace: from #9 should work just like page creations. These are very common and are fairly high on our list of priorities - we want to preveny the hundreds of Orangemoodyists from slipping their paid spam through. Don't worry too much about the pages with deletion tags - as new pages they will already be NOINDEX. Pages that are 'Not English' are more of a problem because lazy patrollers simply tag them for deletion as gibberish, which is of course completely wrong; hoever, if the are new pages, they will at least be NOINDEX. Kudpung กุดผึ้ง (talk) 21:22, 10 October 2016 (UTC) NOINDEX is disabled in mainspace due to the risk of abuse, as pointed out by User:TheDJ at VPT. A list of templates that noindex would be relatively easy to abuse, it would be easy for a vandal to transclude one of them in a template with a high transclusion count or itself transcluded in high-value target pages, in a way that neither displays the template nor categorizes. It is likely to result in the pages being noindexed for quite some time in the wrong circumstances (even after revert of the vandalism on the causative page). So e.g. Barack Obama and other high profile articles could quite easily be noindexed for some time. We should develop safeguards before going ahead with such a system. IMO, the noindex until patrolled system is enough. Pages older than 3 months appropriately tagged for speedy deletion as attack pages, vandalism or copyright violations are quite rare, and having already being indexed for more than 3 months, the extra minutes it will remain indexed until deletion isn't what we should worry about. Cenarium (talk) 12:10, 14 October 2016 (UTC) I think you're pointing out something that has already been covered. Later tagging for deletion of a page that has already been passed as reviewed can occasionally happewn, but it's too late to get it unindexed in search engines.Kudpung กุดผึ้ง (talk) 12:35, 14 October 2016 (UTC) So we won't be using MediaWiki:Noindex templates then. Cenarium (talk) 13:07, 14 October 2016 (UTC) Good points, and thanks for pointing out that we need to be careful. Kaldari just redid the noindex templates feature and changed it to a config setting instead of an on-wiki list. So if we decide we still want to have certain templates trigger noindex (and it sounds like we might not), then we can configure it there. Apologies for the confusion; this sounded like a good idea until poeple pointed out what it really meant. --Roan Kattouw (WMF) (talk) 21:51, 14 October 2016 (UTC)  Done It looks like this is working now. At the time of this writing List of Petz Club episodes was unpatrolled and noindexed, and 1936 Victorian Sporting Car Club Trophy had just been patrolled and was not noindexed. --Roan Kattouw (WMF) (talk) 21:53, 14 October 2016 (UTC) So here's the current status of this feature: Right now any templates listed at MediaWiki:Noindex templates will trigger noindexing. However, after deploying this I realized that this system isn't very efficient. Every time a page is viewed (unless it is viewed from cache), it has to grab the contents of MediaWiki:Noindex templates, parse out all the template names, and compare them with the templates transcluded in the page. This potentially slows down page render for every page on Wikipedia. If all that is desired is to noindex pages tagged for speedy deletion, there is only one template that needs to be considered: {{db-meta}}. If we're only going to look for 1 or 2 templates (or possibly none per Cenarium), having an on-wiki configuration system is overkill (and an unnecessary performance hit). We should just decide which templates to check, set them in a server-side config variable, and leave it at that. I've already written some new code to do this, so let me know what you think. Kaldari (talk) 22:12, 14 October 2016 (UTC) @Kaldari:, @Roan Kattouw (WMF):, NOINDEX is not working. If all new pages are not indexed until they are oficcialy patrolled, then the bug is that when they are tagged, the tag indexes them, xGoogle indexes them, then an admin deletes the page, leaving Google with an entry to a deleted page. The purpose of NOINDEX is to avoid pages being indexed at all. Kudpung กุดผึ้ง (talk) 11:15, 15 October 2016 (UTC) Maybe we could enable template noindexing but only for pages not older than 90 days, which would solve this issue but prevent abuse. Cenarium (talk) 12:57, 15 October 2016 (UTC) @Kudpung and Cenarium: The feature to noindex based on templates is currently in place. I had originally configured it to noindex any article transcluding the {{db-meta}} template (which means all articles marked for speedy deletion). I removed this, however, based on Cenarium's concerns above. As soon as there is consensus for how to use this feature, I'll be happy to configure it however you want. We can also add a 90 day threshold if that seems like a good idea. Kaldari (talk) 20:38, 15 October 2016 (UTC) @Kaldari, Roan Kattouw (WMF), and Cenarium:, What I pointed out was that while all new pages created in or moved to mainspace should not be indexed (and AFAICS we never discussed fr how long), tagging them for CSD certainly indexes them for a split second, long enough for Google to grab them, leaving the deletion (not the deletED) page in Google. For older pages that were already indexed when later tagged for deletion, it's too late - we will have to live with that. Kudpung กุดผึ้ง (talk) 21:07, 15 October 2016 (UTC) @Kudpung: I think we're all aware of that. Cenarium, however, objected to the use of this feature in the discussion above due to the potential for abuse. (This was also echoed by TheDJ and PrimeHunter in the village pump discussion.) I did some testing and confirmed that the feature could be abused by inserting something like <div style="display:none;">{{db-hoax|nocat=true}}</div> into an article. It sounds though like Cenarium would be willing to accept the potential for abuse if it were limited to articles less than 90 days old. What do you think of this idea? Kaldari (talk) 21:56, 15 October 2016 (UTC) @Kaldari, Roan Kattouw (WMF), and Cenarium:, There's something I don't quite understand here, but that quite possible because it's nearly 6am here and I've been up all night preparing other stuff in anticipation of the consensus of the final RfC on the New Page Reviewer right. As Roan already understood, the ship will have for any articles that have already been passed as 'patrolled OK'. Retro tagging with tags that add NOINDEX doesn't remove the listings by the search engines. In any case it is nowadays impossible to get anything removed from a search engine almost under any conditions other than an expensive legal takedown order. All that needs to be ensured is that from now on all new pages created in, moved to, or otherwise posted to mainspace and draft space are NOINDEX until patrolled by an autorised reviewer (which means removing the 'mark this page as patroled' link from the sight of non approved patrollers) and that no deletion tags or maintenance tags for serious issues automatically mark a new page as 'patrolled'; userspace, AFAIK is by default (and we hope) NOINDEX, because users use their user pages and sub-pages, and even their talk pages for posting artspam and their commercial links. Perhaps Cenarium's concerns about <div style="display:none;">{{db-hoax|nocat=true}}</div> can be addressed by a local filter. How realistic are your concerns, Cenarium, what do you expect to be the frequency? Kudpung กุดผึ้ง (talk) 23:13, 15 October 2016 (UTC) I don't think a filter would be a nice solution, not only it adds to the condition limit (which is a perennial concern of edit filter managers), but it can be evaded. We just had a fixed position vandalism that is supposed to be prevented by Special:AbuseFilter/139. In terms of frequency, if it does happen, I don't think we'd let it happen a second time, but I'm pretty sure it's bound to happen within a few months if enabled. Regarding noindex, it isn't "once indexed, always indexed", because we can modify the html of our pages (and Google respects noindex). Google checks the page html for a noindex tag, so if the page suddenly gets a template that causes it to have a noindex tag, it will no longer be indexed by Google the next time it crawls the page (which happens quickly for wikipedia). The potential for abuse is precisely in some established, high-profile pages getting silently noindexed by a template. Cenarium (talk) 01:05, 16 October 2016 (UTC) @Kudpung: The problem is that there isn't any such distinction as "patrolled OK" or "patrolled not OK". An article is "patrolled" (as far as the software is concerned) as soon as a reviewer is finished reviewing it, regardless of whether the final decision is to keep the article or not. Changing how that works would require rewriting a lot of software and it isn't clear how such an approval-based system would work anyway. (For example, there is no reliable mechanism for the software to detect when an AfD or PROD has been closed other than looking for templates or magic words, which brings us back to the original abuse problem.) Personally, I think we should either abandon the noindex template feature or implement Cenarium's suggestion. Using an abuse filter might help, but the abuse filter system is already under heavy strain (as mentioned by Cenarium) and I doubt it would be 100% effective. Plus, it would require every wiki using PageTriage to write their own abuse filters, and not all wikis have administrators that know how to do this. (Eventually PageTriage is going to be deployed to other wikis, so we have to make sure it's easy to use and hard to abuse.) Kaldari (talk) 01:41, 16 October 2016 (UTC) Sorry, @Kaldari:, it's me confusing you. I just don't think like a software programmer, I think as a linguist ;) I know there is no distinction. A page is either 'patrolled' or it isn't - but it can be made 'unpatrolled' again if a patroller screwed up, thus leaving it open in the list for a more experienced patroller to review. The down side to this s that Google will already have snatched it. We'll have to live with that. An article is "patrolled" (as far as the software is concerned) as soon as a reviewer is finished reviewing it, regardless of whether the final decision is to keep the article or not. - absolutely correct, bearing in mind that adding tags of any kind other than deletion tags does make an article 'patrolled' . If you want to help me understand this more (nd I think I need to), don't hesitate to Skype me now. Kudpung กุดผึ้ง (talk) 02:04, 16 October 2016 (UTC) @Kudpung: Currently, adding a deletion tag via the page curation toolbar does mark an article as patrolled. This is to remove it from the backlog and let other patrollers know that it doesn't need to be reviewed again. I'm still interested to know if you think limiting the noindex template feature to articles created in the past 90 days is a good idea or not. What are your thoughts on that? Kaldari (talk) 20:45, 17 October 2016 (UTC) @Kaldari:, we obviously don't want pages tagged for deletion to be indexexed by Google - that would be counter to the whole concept of control of new content. I'm not sure however, what is even meant by the 90-day suggestion. I hadn't heard of it until you mentioned it recently. Is it supposed to mean that pages not reviewed will automatically become free for Google to index after 90 days? If so, isthere any reason why they can't remain NOINDEX indefinitely? I would be ready to understand an argment that we should perhaps nevertheless instill some form of urgency on reviewers and that this could be one way to do it. We could also move such pages to Draft where the could then be semi-automatically deleted after 6 months if not imporoved. @Kudpung: The main danger of the noindex template feature (as explained by Cenarium) is that someone will use it to noindex a high profile article that they don't like. With the current system, this could be done in a way that is almost completely undetectable. For example, you could create a seemingly innocent template, add it to the Hillary Clinton article, and then the day before the U.S. election add <div style="display:none;">{{db-hoax|nocat=true}}</div> to the template that you embedded weeks before in the Clinton article. Nothing noticeable would change on the Clinton article except that it would suddenly stop being indexed by Google. This is potentially a much worse problem than Wikipedia spam getting indexed by Google. Cenerium's suggestion was to limit the noindex template feature to only affect articles that are less than 90 days old. That would dramatically limit the abuse potential, while still giving new page patrollers and administrators sufficient time to remove the obvious spam and attack pages. And as you mentioned, this might also give NPPers extra incentive to keep the backlog under 90 days old. This seems like a good solution to me, but I would like to know if you support the idea as well. Kaldari (talk) 19:05, 18 October 2016 (UTC) @Kaldari:, Cenarium. Sorry for having been so slow to figure this. Now that I have understood, yes, of course I support it :) Kudpung กุดผึ้ง (talk) 19:24, 18 October 2016 (UTC) This'll create a backlog, probably. Adotchar (talk) 09:35, 26 October 2016 (UTC) It won't, Adotchar, and as you've been asked to refrain from patrolling anyway, you need not worry about it. Kudpung กุดผึ้ง (talk) 14:15, 26 October 2016 (UTC) Good point. Adotchar (talk) 14:32, 26 October 2016 (UTC) In order for this to be of real use the Curation Tool needs to be set to where it does not automark pages as patrolled on every action. For instance if some basic tags (or even CSD, AfD, BLPPROD) are placed the page is marked patrolled and as I understand it, it becomes indexed even if you immediately unpatrol it again. This is also an issue for reviewers who are just tagging low hanging fruit. Right now the practice is to immediately 'unpatrol' the page but this will still end up with the page indexed when it should not be. There is an option in TW to mark pages patrolled when tagged but for deletion tags it should never do so. JbhTalk 15:51, 26 October 2016 (UTC) @Jbhunley and Kudpung: We originally implemented the feature as you describe: You had to explicitly indicate that you wanted to mark the article as reviewed. However, users complained that this was tedious and they wanted it to happen automatically, so we changed it way back in 2012. Also, it is not accurate that an article is immediately indexed between the time that you tag it and "unreview" it. Unless people are massively linking to it from outside Wikipedia (for example, during a news event), it will take Google several hours to find and index an article after it is reviewed. I've tested this myself. And to dispel one of Kudpung's earlier concerns, it is also not accurate that once Google finds an indexable article it will hold on to it forever. As soon as Google revisits an article that is deleted (or unreviewed) it will see the 404 or noindex tag and immediately remove the article from its index. The chances of a CSD-tagged article getting indexed by Google are now extremely low, and even if it does get indexed, it won't stay on Google for more than a day after its deleted. The actual risk of damage here is extremely low, especially compared with how much regular vandalism is indexed by Google every day. Kaldari (talk) 05:49, 27 October 2016 (UTC) @Kaldari and Jbhunley:, I'm relived to hear this, although up until recently, new pages were indexed by Google even quicker than our page reviewers were able to load the New Pages Feed. As these improvements to Page Curation are concomitant with the introduction of the new user right for new page reviewers, which as you know goes into effect at 22:00 UTC tonight (14 hours from now) we need to know that these things will be working because they are partly the reasons why both the right and the wrong people have drifted back to using the old feed and Twinkle. The reasons for the changes are to ensure that no one without the right can tag an unpatrolled page for maintenance or deletion either through twinkle or page Curtion. This is to avoid new users being bitten - and we've lost a few in the last few days. The other eqaually important objective is to ensure that inappropriate new pages do not get patrolled and released into the encyclopedia. The underlying major problem is that we have exhausted all admin capacity for constantly having to monitor the work of the patrollers, and locate the paid spammers who are gaming the system with their sleeper accounts. Kudpung กุดผึ้ง (talk) 06:18, 27 October 2016 (UTC) @Kudpung: Yes, I believe you're correct that somehow Google was aggressively indexing new articles prior to the noindex fix. I'm not sure exactly how they were doing this, but it may have been through monitoring RCStream for new pages. Luckily or unluckily (depending on your point of view) Google is not as good at catching when articles become indexible after being reviewed (at least from my tests), so I think we're actually in pretty good shape now as far as noindexing. If anyone notices issues though, please let me know. Kaldari (talk) 07:01, 27 October 2016 (UTC) @Kaldari: So does 'unpatrolling' reinstate the NOINDEX? My concern is that doing initial tagging will remove the NOINDEX before the review is complete. For instance if, on first read I tag {{orphan}}, {{deadend}}, {{unsourced}} or similar low hanging fruit but I am not familiar enough with the subject complete the review I will 'unreview' so someone who knows the topic can make the final call. In that case would the article be in the state of unpatrolled and __INDEX__ simultamiously? A related question is do {{blpprod}} articles remain NOINDEXed? Now BLPPRODed articles are automarked patrolled but I would think we would want to insure unsourced BLPs are not indexed. Maybe that is a separate issue... JbhTalk 14:38, 27 October 2016 (UTC) Jbhunley, Kaldari, FYI Roan Kattouw (WMF), Cenarium} The effort with the re-implementation if the NOINDEX feature is to ensure that no articles, tagged or otherwise, until finally approved by a reviewer, will be indexed by search engines. The technical issues surrrounding deletion templates must be resolved because: Many creators remove CSD, PROD, and BLPPROD templates contrary to instructions and policy. Allowing such articles to become indexed would defear the entire purpose of patrolling new pages. Many patrollers use the wrong deletion templates (which has to be reverted), or some pages are wrongly templated for deletion but may certainly not be ready for publication (i.e. indexing by search engines. We need some fast updates on this because the new user right goes live on Monday.Kudpung กุดผึ้ง (talk) 22:37, 29 October 2016 (UTC) Kudpung กุดผึ้ง (talk) 22:37, 29 October 2016 (UTC) @Kudpung and Cenarium: I've submitted a new patch for PageTriage that limits the functionality of the noindex template feature to articles less than 90 days old. Right now, there are no active noindex templates, but I think the best course of action will be to designate the existing {{NOINDEX}} template as a noindex template and add a special tracking category (that can't be disabled via a template parameter) that tracks all main namespace articles that transclude the template. The community can then embed the {{NOINDEX}} template in whichever deletion templates they want it to apply to. (It's already embedded in {{Db-g11}} spam template.) To prepare for this, I've already added the tracking category to the template and set up Category:Noindexed articles. Once the new patch is merged and deployed (which may take a week or two), I can add {{NOINDEX}} as an official noindex template and it will start actually noindexing the articles in Category:Noindexed articles that are less than 90 days old. This approach should be fairly resistant to abuse since you won't be able to disable the category inclusion and it will be limited to new articles. Kaldari (talk) 03:20, 31 October 2016 (UTC) @Kaldari: Thanks for writing that patch, I've merged it. Also thanks to Cenarium for reviewing it (twice) and providing good feedback. @Kudpung: This patch would normally be scheduled to be deployed on Thursday November 10th around 20:00-22:00 UTC (merged on a Tuesday + going to enwiki = longest possible wait of 9 days), but if there's a reason why it's needed earlier, tell me (and tell me what the reason is), and I can expedite it to Thursday November 3rd around 23:00-00:00 UTC. (Sorry to have been away from this discussion for a while, and then come back and ask a relatively basic question; I had a busy time followed by a family emergency and today is my first day back.) --Roan Kattouw (WMF) (talk) 02:04, 2 November 2016 (UTC) Thanks Roan - I also know all about family emergencies and I hope all is well, I've just flown back to Thailand from the UK where my father passed away last week. We've been without the required NOINDEX feature for so long that I guess a few more days won't hurt (around 25% of all the 5.5mio articles on the en.Wiki probably shouldn't be there). One of the main objectives for no-indexing is to dissuade the paid SEO spammers from thinking that getting their client on Wikipedia with it associated top-of-the-results at Google will do them any good. In today's climate of Orangemoody it becomes rather critical and we volunteers don't get paid for our work, or for writing the core code. Kudpung กุดผึ้ง (talk) 02:18, 2 November 2016 (UTC) I'm sorry for your loss. Mine was quite similar, I've just returned to California after an unplanned trip to Europe to attend my grandfather's funeral. It sounds like you're happy to wait until the 10th, which saves me the work of expediting this change. I did just realize that we have to explicitly enable the noindex template feature after Kaldari's is deployed (it's currently disabled because of the abuse concerns from this thread), so I wrote that patch too and scheduled it for Friday November 11 00:00-01:00 UTC (i.e. Thursday afternoon US time, a couple hours later than what I said before). --Roan Kattouw (WMF) (talk) 16:45, 2 November 2016 (UTC)  Done The {{NOINDEX}} template change was just deployed, and I verified that it works. --Roan Kattouw (WMF) (talk) 00:19, 11 November 2016 (UTC) @Kudpung: This is working now. Any templates that you want to be noindex templates, just transclude {{NOINDEX}} within them. See for example, {{Db-g11}} (the spam deletion template), which already has this. Now pages like Collibra and Youssif Isa are noindexed, even though they've already been reviewed. Keep in mind this only works for new article though, not old article that have been marked for deletion. Kaldari (talk) 02:25, 11 November 2016 (UTC) Thank you everyone, Roan Kattouw (WMF), Kaldari, Cenarium, et al for your all your hard work on this. The next stages for getting Page Curation and its feed up to date in order to get people using them with their new user right are all documented on this page. I shall shortly be posting the community's short-list wish of priorities which will encourage the holders of the new, New Page Reviewer right, to use it. Thanks again. (FYI: xaosflux). Kudpung กุดผึ้ง (talk) 03:11, 11 November 2016 (UTC)

9. Pages moved to mainspace from other namespaces

Done

Drafts (a new namespace created later than the Curation tool), and articles moved to mainspace from other namespaces and user space drafted articles. First discussed in 2012, the Foundation promised to look into it and did not follow through. Kudpung กุดผึ้ง (talk) 22:33, 7 September 2016 (UTC) @Kudpung: I'm pretty sure we implemented this way back in 2012. Unless I'm mistaken, I believe this still works. If not, someone should file a new bug report about it. Kaldari (talk) 00:02, 5 October 2016 (UTC) Kaldari, although it was intended, due to other priorities and a couple of WMF scandals at the time that rocked the movement and overshadowed it, I didn't get consensus for the creation of the Draft namespace until later. It has not been done yet. Or if it's in the code, it's not been activated. --Kudpung กุดผึ้ง (talk) 00:25, 5 October 2016 (UTC)  Done @Kudpung: Note that if a page is moved by someone with the autopatrol right this will cause the page to be autopatrolled (same as with an edit). Tested by moving a page from Draft namespace to Main namespace. Kaldari (talk) 19:27, 5 October 2016 (UTC)

12. User filters: Articles tagged for deletion

Done

Offer an additional filter to show a list of articles that are tagged for deletion by PROD, BLPPROD, CSD, and AfD. Particularly useful for cross-checking, checking the performance of patrollers, and for admins who can delete such pages if required. This is in addition to the function that already exists where the feed displays (or should display - this is not always working) a trash can icon. Kudpung กุดผึ้ง (talk) 23:50, 7 September 2016 (UTC)

13. Naked URLs

No consensus. Also see the concepts of information overload and banner blindness. ∯WBGconverse 12:27, 13 September 2019 (UTC)
The following discussion has been closed. Please do not modify it.
Display in the Feed entry, in red alongside the 'no citations' alert, a 'Naked URL' alert. This should enable a patroler to send a canned message to to the creator on the lines of: Thank you for creating X. I notice you left naked URLs in the references section. Please consider returning to the article and addressing this and any other tagged issues. For more information about correctly formatting sources and external links, please see WP:CITE. Kudpung กุดผึ้ง (talk) 00:32, 8 September 2016 (UTC) Oppose - Limited development resources would be better directed to create other features. I would rather see naked URLs counted as citations, which they often are.- MrX 14:36, 15 June 2017 (UTC) This could be done automatically anddoes not involve a lot of HR. Kudpung กุดผึ้ง (talk) 15:42, 15 June 2017 (UTC) Oppose - This is incidental cleanup rather than checking if a new page is suitable for inclusion in the encyclopaedia (naked refs are still refs). Not worth the clutter IMO. Lineslarge (talk) 19:20, 25 September 2017 (UTC)

14. Wikiprojects

Implemented as a user script (User:Kephir/gadgets/rater)

Discussed in 2012, several editors felt that articles get a lot of help if their parent projects know about them. While it might be almost impossible to automate the placing of project templates on article talk pages, it might be an idea to provide patrollers with a drop down of some of the more common projects such as mil hist. BLP, Bio, Math, classical music, rock music, settlements, countries, etc., and let a script do the rest Kudpung กุดผึ้ง (talk) 10:31, 8 September 2016 (UTC) This has in fact been mentioned several times and again recently. However, having done this manually, I beging to get the feeling that a lot of projects are not actually very active and don't take much notice of new articles tags with their project banners. Prhaps the tagging could be done in a similar way that HotCat helps choose categories. --Kudpung กุดผึ้ง (talk) 05:46, 15 September 2016 (UTC) Support - yes, exactly. HotCat's autocomplete interface is what Wikipedia tagging tools should be like in future. We should have this for WikiProject and stub tagging too, as discussed below. Blythwood (talk) 15:33, 1 October 2016 (UTC) Comment - ah, someone on the HotCat talk page points me to the rater module, now in development. So this problem may be going away soon. Blythwood (talk) 04:18, 4 October 2016 (UTC) Comment - There are already a couple of user scripts to handle this: User:Kaldari/assessmentHelper.js and User:Kephir/gadgets/rater.js. I proposed them as gadgets about a year ago, but didn't get any traction. I'm not sure how much this is in the scope of Page Curation, but it's definitely an idea to consider. Kaldari (talk) 23:51, 4 October 2016 (UTC) Comment The AFC Helper script has had this feature for qute a long time already, it works well although some of the more obscure projects are not included in the menu. Roger (Dodger67) (talk) 11:29, 13 October 2016 (UTC) Comment I use the User:Kephir/gadgets/rater.js script on a lot of new articles, and it works quite well, although it seems to have been abandoned by the creator. — InsertCleverPhraseHere 01:29, 21 July 2017 (UTC) Support Or convert some good script into gadget, like Kaldari suggested above. —usernamekiran(talk) 09:35, 18 March 2018 (UTC)

15. Jumpback

Tracked in Phabricator
Task T167475

First raised by DGG in 2012: ability to jump back a specific number or edits or days, as with NPP. I remember when NPP did not have that feature, and it was great getting it. I have been unable to tell if the complete file loads when you open it, it scrolls too slowly. NPP, for comparison, loads a fixed number at a time, which you can adjust to fit your own screen size and connection quality, confirmed by Jorm as doable, promised by O Keyes, never implemented.Kudpung กุดผึ้ง (talk) 10:56, 8 September 2016 (UTC)

• Support - This would be a very valuable feature. It would help eliminate new pages slipping through the cracks during periods where patrolling is low.- MrX 13:03, 16 September 2016 (UTC)

MrX, We don't need to 'support' this, just insist on the WMF or Phabricator that it gets done. Remember, that as there are plenty of missing features that were supposed to have been included in the original build, and as there appears to be a general reluctance of editors to make a teamwork out of pressuring the Foundation to get the job finished, all the features and ideas on this page can be demanded at Phabricator by any individual. Kudpung กุดผึ้ง (talk) 14:12, 16 September 2016 (UTC)

Kudpung, I assume that there has to be some prioritization on what will likely be a long list so my support is intended to reflect that. However, if the WMF should have already done this, then I guess it should already be top priority. I assume that the reason we see only a few records until we scroll down to load a few more is to reduce server/database load. That said, there should be a way to override it.- MrX 14:56, 16 September 2016 (UTC)

I also would like to see this feature added. With more than 14,000 new pages in the feed, I can't help thinking about the thousands of articles in the middle that will have to wait who-knows-how-long to be reviewed. The "Newest" and "Oldest" options let us only whittle away at the extremes of the backlog. Any progress in this regard would be appreciated. Eddie Blick (talk) 16:38, 4 March 2017 (UTC)

(below conversation copied from Wikipedia_talk:New_pages_patrol/Archive_5#New_pages_feed_-_suggestion — Insertcleverphrasehere ^{(or here)} 13:39, 16 October 2018 (UTC))

It would be nice if the new pages feed had a date filter (before after or between). Also, given the number of pages per day, being able to specify am/pm or the hour (1-24 in a dropdown) would be a benefit. It would simplify working through the list IMO if it isn't already available. Regards, Cinderella157 (talk) 04:03, 7 October 2017 (UTC)

Hi Cinderella157, this has been requested in phabricator and is tracked at the task above. TonyBallioni (talk) 04:06, 7 October 2017 (UTC)

@User:TonyBallioni, thankyou for the feedback. I had a look there. I would endorse the idea of a popup calendar per what I read there. What I didn't see there was the idea of adding a time as well. I haven't programmed for years but I would have thought there would be programming tools (templates)that reduced programming a calendar popup to a single line or two, so all up, it would only be a half-dozen lines of code? Rehards, Cinderella157 (talk) 05:15, 7 October 2017 (UTC)

User scripts for NPP

I would like to collect the scripts people currently use to aide in NPP. Some may be worth integrating into Page Curation while others may be useful on their own. As it stands I do not believe there is a central list new or even experienced reviewers can go to find these tools.

1. User:Writ Keeper/Scripts/deletionFinder.js - Gives links to previous AfDs and pervious deletions next to title.
2. WP:HOTCAT
3. WP:DELSORT
4. Page -> Tools -> Copyright vio detector - I do not recall if this is part of the basic interface or an add-on.
5. Page -> Tools -> Expand bare references - I do not recall if this is part of the basic interface or an add-on.

Are ther others? Which, if any, of these should and can be integrated? Jbh^Talk 15:30, 5 October 2016 (UTC)

As I mentioned above, some folks also use User:Kaldari/assessmentHelper.js or User:Kephir/gadgets/rater.js to add WikiProject templates and assessments while new page patrolling. Kaldari (talk) 20:07, 6 October 2016 (UTC)

Asked a while back by Kudpung to post here, I may add a few more suggestions:

1. {{subst:js|User:Writ Keeper/Scripts/googleTitle.js}} - provides a Search Google link to the right of the article title; a fine companion to {{subst:js|User:Writ Keeper/Scripts/deletionFinder.js}} with its prev dels and prev AfDs.
2. WP:STUBSORT: {{subst:js|User:Ais523/stubtagtab2.js}} - at least nine other forks exist (cf. my notes in User:Sam Sailor/common.js), but forget them: this is the mother of them all and was updated in August to include the Architecture stub types that were added to WP:WSS/ST in 2009.
3. {{subst:js|User:The Earwig/copyvios.js}} - adds a "Copyvio check" link to the tools portlet that runs the current page through Earwig's Copyvio Detector.

— Sam Sailor 03:12, 6 December 2016 (UTC)

• See:Wikipedia_talk:New_pages_patrol/Reviewers#Collection_of_independent_scripts_to_bundle_into_a_'NPR_helper_tool' for an up-to-date discussion of this. — Insertcleverphrasehere ^{(or here)} 07:27, 19 October 2018 (UTC)

16. Decline CSD

Discuss at #47

Tracked in Phabricator Task T207435 As per Twinkle, a feature to decline misplaced speedy deletion tags. Suggestion for Curation is to provide a selection of canned rationales.more deais Discussed 2012, never implemented. Kudpung กุดผึ้ง (talk) 11:26, 8 September 2016 (UTC) Also requested below at Wikipedia:Page_Curation/Suggested_improvements#47._Decline_CSD/PROD. Comment there instead of here. — Insertcleverphrasehere (or here) 07:54, 19 October 2018 (UTC)

17. Tag bombing

No Consensus. ∯WBGconverse 12:28, 13 September 2019 (UTC)
The following discussion has been closed. Please do not modify it.
Mentioned in 2012, it was suggested to impose a limit to the number of tags that can by applied to one article by one patroller in one session. 2 or 3 (major) tags should be sufficient to draw attention to any other glaring issues. Empirical experience would appear to suggest that new or inexperienced users place a lot of tags, but are too timid to place one PROD, BLPPROD or CSD tag. Thus the article remains perma-tagged and does not get deleted. Kudpung กุดผึ้ง (talk) 12:11, 8 September 2016 (UTC) Support, with additional comment that we need to change the culture regarding tags. Some of these tags are useful, such as the "advertising" tag, and identify structural problems with the article that cannot easily be fixed. But too many are often just used as a way to bully newbie editors. For example, the "no categories" and "orphan" tags - these are generally problems that can and should be fixed in a valid article within seconds by an experienced editor. (For instance, if a notable woman has a notable husband, a backlink can be added there.) If an article is wrong for Wikipedia, it should be deleted, if it's good, we should fix it where possible explain to the newbie editor why, and ask them to do the fixes next time. Blythwood (talk) 15:33, 1 October 2016 (UTC) Support It's sometimes too easy to be mean/ critical. If you can't cover the basics in 2 major tags, then the article should probably be deleted and you should stand up and have the guts to make a realistic argument as to why. IMO. KDS4444 (talk) 15:07, 28 November 2016 (UTC) Comment I think it's better to tag-bomb and tell the editor what the problem is, as opposed to immediately nominating for deletion, which is much more intimidating and discouraging. — Preceding unsigned comment added by Jjjjjjdddddd (talk • contribs) 15 July 2017 (UTC) Support, new users do indeed tag bomb quite often. — InsertCleverPhraseHere 01:31, 21 July 2017 (UTC) I don't know who made the unsigned 'Comment' above, but it's obviously someone who does not fully understand the cause and effect of patrolling new pages. Kudpung กุดผึ้ง (talk) 02:52, 21 July 2017 (UTC) Support Tagging is better than deletion if the article is salvageable, but you can have too much of a good thing (/more than 3 is probably biting). Lineslarge (talk) 19:50, 25 September 2017 (UTC) Strong oppose-There are rare cases which mandate such tagging and the concept that any article taggable with 3 or more tags equates to deletion-tag-able stuff is nonsensical.Yeah, new reviewers have a tendency to overuse tags and Blythwood is accurate but it will be problematics in case of veteran reviewers, in rare cases.∯WBGconverse 12:43, 21 October 2018 (UTC) I removed the Phab ticket and closed it, as I am no longer convinced that such a change will be an improvement. I also struck my !vote above and am not convinced that we have a current consensus on this. — Insertcleverphrasehere (or here) 08:51, 29 October 2018 (UTC)

18. User right

Done

Perhaps not the 100% appropriate venue to mention this, but a user right was first metioned in August 2012. The 'Foundation' messenger at that time implied that the Curation tutorial would be sufficient to ensure that patrolling would be done correctly. Currently being discussed at RfC. Kudpung กุดผึ้ง (talk) 12:20, 8 September 2016 (UTC)  Done an RfC has reached a consensus for turning NPPer into a formal user right with required minimum experience. --Kudpung กุดผึ้ง (talk) 01:31, 9 October 2016 (UTC) A second RfC is currently debating the entry threshold for this user right. It looks as if the 90/500 is going to be accepted. --Kudpung กุดผึ้ง (talk) 00:29, 13 October 2016 (UTC)  Done. Will be implemented on Thursday 27 October 2016, 22:00 UTC. --Kudpung กุดผึ้ง (talk) 07:37, 27 October 2016 (UTC)

19. Patrolling the patrollers

Done

Tracked in Phabricator Task T204463 Suggested August 2012 by Jorgath: I'd like to add a sorting option to the feed to allow sorting reviewed pages by reviewing editor. Perhaps just filtering it so you only see the reviews of a specified editor would be enough (I mostly want to be able to see a list of articles I've marked as reviewed).. Kudpung กุดผึ้ง (talk) 12:25, 8 September 2016 (UTC) Yes. This. Maintaining quality control after granting the right (if we get there) is important. People learn via feedback and even reviewers who are in general good may have blind spots where feedback would help them be better. JbhTalk 14:07, 2 October 2016 (UTC) Although: I've recently gained autopatrolled and looking through my logs I realise that it massively increases the number of pages you mark as patrolled. Every time I open a user talk page by welcoming someone, or create an article talk page, it's marked as a patrol action. Perhaps it would be nice to be able to separate "actual" patrol actions from this kind of thing. Blythwood (talk) 04:21, 4 October 2016 (UTC) @Blythwood: Thanks to a few patches that User:Cenarium wrote a while ago (see phab:T20954 and phab: T27799), you can now view automatic patrol actions and manual patrol questions separately. These changes added a "Type of patrol" dropdown on Special:Log/patrol. This has been in place since late March / early April. Similar splits were put in for other types of logs (like block, delete, protect, and a few more). --Roan Kattouw (WMF) (talk) 20:32, 11 October 2016 (UTC) 'Support It would remain valuable. DGG ( talk ) 19:30, 17 March 2018 (UTC) Comment This seems largely resolved: We have a page curation log, and a patrol log which can both be specified by user. Links at Wikipedia:Database reports/Top new article reviewers lead to both for pretty much everyone, so it is pretty easy to patrol the patrollers from there. — Insertcleverphrasehere (or here) 13:47, 16 October 2018 (UTC)

20. Build autopatrol nomination into the tool

Denied. Please refer to Wikipedia:Database reports/Editors eligible for Autopatrol privilege

Suggested by hahnchen August 2012. Kudpung กุดผึ้ง (talk) 12:31, 8 September 2016 (UTC) I am still thinking about this, but frankly it would be interesting to know where and how one could find a table of the most prolific article creators who are not autopatrolled. Encouraging those people, if they are doing OK, to apply for autopatrolled status would save us a lot of time. Blythwood (talk) 15:33, 1 October 2016 (UTC) @Blythwood: Check out Wikipedia:Database reports/Editors eligible for Autopatrol privilege, provided by Community Tech bot — MusikAnimal talk 04:38, 4 October 2016 (UTC) MusikAnimal - hi, thanks. I'd seen this somewhere else and I was just about to mention it. Looking through it, it's a bit discouraging. It gives me the impression that there's a lot of high-rate article creators on there who know the notability criteria but can't be bothered to do the grunt work in creating an article like adding a reflist and categories. I am planning to go through it though to see who on there would be good to get autopatrol though (or level up and actually do the work...). Blythwood (talk) 04:43, 4 October 2016 (UTC) Awesome! I believe some admins have been going off of that report and flagging users, but I'm sure there's plenty they overlooked. If you've got some nominations, at WP:PERM/A when you click on "add request" be sure to change the {{subst:REVISIONUSER}} to the user you are nominating. Many thanks! — MusikAnimal talk 04:50, 4 October 2016 (UTC) If we really want it, we can simply add a link to add a request directly at PERM (and auto-fill in the username), but I question if we should include a feature like this at all. One would need to carefully evaluate several articles by the author before nominating them to be autopatrolled. Including a link in the Page Curation interface may result in some hasty nominations — MusikAnimal talk 23:16, 15 October 2016 (UTC) I personally agree, MusikAnimal, that patrolers would make some hasty nominations. Autopatrolled is one of the rights that takes up the most admin time to review (it can't be accorded simply on a numerical basis). The effort at the moment is to reduce the admin workload and I see possible indiscriminate use of such a tool increasing it. Kudpung กุดผึ้ง (talk) 07:50, 27 October 2016 (UTC) Boldly marking this as  Denied for numerous reasons. First, we have Wikipedia:Database reports/Editors eligible for Autopatrol privilege which does a great job of surfacing users eligible for autopatrolled. If you're looking at the New Pages Feed and see someone you think is eligible, chances are they are listed on the report and there will be lots of additional information to help you decide if they are truly fit to be autopatrolled. Another major issues is implementing such a nomination tool is prone to error. I frequent WP:PERM and can tell you that over the years that {{rfplinks}} and other procedures there have changed quite a bit. Each time we'd need to make an update to Page Curation. We also ideally don't want to integrate things that are super duper enwiki-specific. Finally, as described above, there are concerns this could be misused and PERM admins would be overwhelmed with hasty nominations. — MusikAnimal talk 03:27, 15 June 2017 (UTC)

21. More granular CSD A7 criteria as per Twinkle

Done; functionality essentially identical to Twinkle now

Partly addressed - needs further checking. Suggested by Writ Keeper October 2012. Acknowledged by the WMF mesenger, but never followed up. Kudpung กุดผึ้ง (talk) 12:54, 8 September 2016 (UTC) Raised again mid January 2013. WMF declined to address it. --Kudpung กุดผึ้ง (talk) 13:20, 8 September 2016 (UTC) Raised again late January 2013. --Kudpung กุดผึ้ง (talk) 13:23, 8 September 2016 (UTC) This is one of the two main reasons why patrollers won't use Page Curation. Complete list of CSD criteria available from the Twinkle CSD panel Articles A1: No context. Articles lacking sufficient context to identify the subject of the article. A2: Foreign language articles that exist on another Wikimedia project A3: No content whatsoever A5: Transwikied articles A7: Unremarkable person A7: Unremarkable musician(s) or band A7: Unremarkable club A7: Unremarkable company or organization A7: Unremarkable website or web content A7: Unremarkable individual animal A7: Unremarkable organized event A9: Unremarkable musical recording where artist's article doesn't exist A10: Recently created article that duplicates an existing topic A11: Obviously made up by creator, and no claim of significance General criteria Custom rationale (custom deletion reason) G1: Patent nonsense. Pages consisting purely of incoherent text or gibberish with no meaningful content or history. G2: Test page G3: Pure vandalism G3: Blatant hoax G4: Recreation of material deleted via a deletion discussion G5: Banned or blocked user G6: History merge G6: Move G6: XfD G6: Unnecessary disambiguation page G6: Copy-and-paste page move G6: Housekeeping G7: Author requests deletion, or author blanked G8: Pages dependent on a non-existent or deleted page G8: Subpages with no parent page G10: Attack page G10: Wholly negative, unsourced BLP G11: Unambiguous advertising G12: Unambiguous copyright infringement G13: Old, abandoned Articles for Creation submissions A couple of things are still missing from this (actually CSD tagging in general_ The ability to tag for multiple reasons using {{db-multi}} This seems to have been  Done. — Insertcleverphrasehere (or here) 22:27, 16 October 2018 (UTC) The ability to add notes to ie user or SPI links to {{db-banned}} This seems to have been  Not done. — Insertcleverphrasehere (or here) 22:27, 16 October 2018 (UTC)  Done by me, months back. ∯WBGconverse 12:22, 13 September 2019 (UTC) I am not seeing the granular A7's like {{db-person}}, {{db-band}} etc. just the generic "elegible subject" tag shows up. This seems to have been  Done. — Insertcleverphrasehere (or here) 22:27, 16 October 2018 (UTC) The ability to tag "promotional article from promotional username" and file the UAA report as in TW. This seems to have been  Not done. — Insertcleverphrasehere (or here) 22:27, 16 October 2018 (UTC) I have also run into problems where a CSD or PROD have been placed and removed where it will not allow an AfD to be opened with the error "deletion tag already present". The work around is to use TW but that action is missed in the curation log. (I would love for TW tagging etc to be recorded in the curation log but I guess that is for a different wishlist :( ) Thank you for all of the great work on this tool! JbhTalk 14:11, 27 October 2016 (UTC) Last edited: 14:22, 27 October 2016 (UTC) MusikAnimal, Kaldari. As the roll out the New Page Reviewer right progresses, we are having difficulty impressing upon reviewers how important it will ultimately be that they start using New Pages Feed and Page Curation insead of Twinkle. The lack of granular A7 calls is given as one of the main reasons for not using Curation, because it also does not adequately inform the creator why his article is being tagged for deletion. This then creates unnecessary additional dialog between patroller, deleting admin, and article creator. Can we address this asap, please? Kudpung กุดผึ้ง (talk) 07:20, 1 November 2016 (UTC) MusikAnimal, Kaldari. This has still not been done. Kudpung กุดผึ้ง (talk) 09:42, 13 November 2016 (UTC) @Kudpung: For the missing A7 reasons, the following code could be added to MediaWiki:PageTriageExternalDeletionTagsOptions.js. These definitions were copied from Twinkle (twinklespeedy.js line 684 onwards). They get added to the end of the list (which may not be what is desired, in which case the whole list needs to be redefined in the wikipage rather than the extension code; that might be good to do anyway, if PageTriage is to be used on other wikis one day). Suggested changes to MediaWiki:PageTriageExternalDeletionTagsOptions.js $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_person = { label: 'Unremarkable person', tag: 'db-person', code: 'A7', desc: 'An article about a real person that does not assert the importance or significance of its subject. If controversial, or if there has been a previous AfD that resulted in the article being kept, the article should be nominated for AfD instead. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_band = { label: 'Unremarkable musician(s) or band', tag: 'db-band', code: 'A7', desc: 'Article about a band, singer, musician, or musical ensemble that does not assert the importance or significance of the subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_club = { label: 'Unremarkable club', tag: 'db-club', code: 'A7', desc: 'Article about a club that does not assert the importance or significance of the subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_corp = { label: 'Unremarkable company or organization', tag: 'db-corp', code: 'A7', desc: 'Article about a company or organization that does not assert the importance or significance of the subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_web = { label: 'Unremarkable website or web content', tag: 'db-web', code: 'A7', desc: 'Article about a web site, blog, online forum, webcomic, podcast, or similar web content that does not assert the importance or significance of its subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_animal = { label: 'Unremarkable individual animal', tag: 'db-animal', code: 'A7', desc: 'Article about an individual animal (e.g. pet) that does not assert the importance or significance of its subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; $.pageTriageDeletionTagsOptions.Main.speedydeletioncommon.tags.dba7_event = { label: 'A7: Unremarkable organized event', tag: 'db-event', code: 'A7', desc: 'Article about an organized event (tour, function, meeting, party, etc.) that does not assert the importance or significance of its subject. (A7)', params: {}, anchor: 'importance', talkpagenotiftpl: 'Db-notability-notice-NPF' }; —Sam Wilson 05:07, 9 December 2016 (UTC) Tracked in Phabricator Task T207230 Some of this is  Done (see above) and some isn't, the remainder is tracked in the Phab task at right. — Insertcleverphrasehere (or here) 22:33, 16 October 2018 (UTC) Insertcleverphrasehere, does the feature of tagging promotional article from promotional username and auto-reporting to UAA exist in any current tool? Do you desire an integration of non-admin version of SUPG into the feed? That will be helpful to know. At any case, this can be implemented from on-wiki customizations or so do I think. Will be looking at the ability to add notes to ie user or SPI links to db-banned -)∯WBGconverse 12:31, 22 October 2018 (UTC) Insertcleverphrasehere, I have already done 1st part (add user to db-banned) of the phab ticket but Twinkle does not offer any "promotional article from promotional username" option, at all. I think that this request can be considered fulfilled. ∯WBGconverse 12:26, 13 September 2019 (UTC)

22. Add a waiting time for CSD A7 templates

No consensus

Already discussed as far back as 2007 and many times since, tagging A1 & A3 with seconds or even minutes of creation is seen by many as too fast. This probably needs a consensus, but experience tends to reveal that most A7 articles are not appropriate for publication and probably never will be. The answer to this lies in the number of pages tagged A7 and the actual percentage that get deleted, and the actual percentage that actually do become recreated and kept even years later. Some work here for someone who knows their way around gathering stats. That said, there are rarely objections for a reasonably fast tagging for A7. The purpose of some of these suggestions is that A1 and/or A3 will become less frequent when creation in manspace is limited to autoconfirmed users and al others are forced through the Article Wizard where there are no times limits for submission for review Kudpung กุดผึ้ง (talk) 06:26, 15 September 2016 (UTC) Semi-support - I believe that one thing that doesn't get done enough during NPP is posting a talk-page message explaining, politely, that this doesn't seem to be what Wikipedia can accept. I think that normally most people who have created a first article (and not always in bad faith) that's non-notable first discover that the article is going to be deleted when they get an actual deletion message, and this is very discouraging for new users. I am developing some new template messages that I hope can be used to explain to people that there is a problem with their article less peremptorily than simply posting over a deletion notification. Blythwood (talk) 15:33, 1 October 2016 (UTC) Oppose - I assume the proposal here is to build delay between the time and article is created to when it can be marked A7, although Kudpung comments have me a bit confused. I don't see the value in this proposal, to the extent I even understand it.- MrX 14:48, 15 June 2017 (UTC) Oppose - while tagging A1 & A3 with seconds or even minutes of creation is seen by many as too fast, there are plenty of A7 candidates that can and should be deletedquickly. Kudpung กุดผึ้ง (talk) 15:52, 15 June 2017 (UTC)

23. Adding stub tags

Not a front-line priority and no consensus.

First mentioned October 2012. Patrollers adding stub tags. There are possibly 1,000s of different stub tags. Perhaps a feature such as Hotcat for subs? PamD suggestions? Kudpung กุดผึ้ง (talk) 13:06, 8 September 2016 (UTC) Raised again in February 2013. --Kudpung กุดผึ้ง (talk) 13:29, 8 September 2016 (UTC) Raised again by Liam987in March 2015. --Kudpung กุดผึ้ง (talk) 14:07, 8 September 2016 (UTC) Raised again 28 April 2016 by PamD. --Kudpung กุดผึ้ง (talk) 14:18, 8 September 2016 (UTC) Yes. I found it very unintuitive when starting to use categorisation that I could add topic tags but not stub tags via HotCat. Blythwood (talk) 15:33, 1 October 2016 (UTC) Also, a better, integrated, categorization tool should be included with this. Unless I am missing something obvious, HotCat pretty much requires that you know, or can guess, appropriate categories. There is no useful keyword search. JbhTalk 20:31, 2 October 2016 (UTC) This is just my personal opinion, but I've always considered stub templates to be a waste of time. I've just never understood the purpose of them. We already have WikiProject assessment templates and assessment categories. What do stub templates actually accomplish? Kaldari (talk) 23:42, 4 October 2016 (UTC) That they add a category and a stub tag in one go. The "you can help Wikipedia by expanding this" message probably is worth it to encourage new contributors (which, let's not forget, we don't have enough of). Blythwood (talk) 02:55, 7 October 2016 (UTC) Oppose - I don't think this is important enough to spend resources on. Kaldari makes a good point about the value of adding stub templates to article.- MrX 14:51, 15 June 2017 (UTC) Neutral - Probably not 100% necessary, but easy to implement and could be useful. Invite comments from PamD. Kudpung กุดผึ้ง (talk) 15:55, 15 June 2017 (UTC) Oppose not necessary, stub sort is a well manned, and it often gets a second set of eyes that make formatting changes that slip by NPP. I tag with an appropriate stub if I can figure it out, but otherwise I let the experts handle it, because I assume they will do it better than I will. TonyBallioni (talk) 15:59, 15 June 2017 (UTC) Oppose: as long as we continue to have the current setup of specific stub tags, I suspect that inviting/forcing Patrollers to add a specific tag rather than {{stub}} would result in a lot of {{bio-stub}} or {{UK-stub}}, taking those articles out of the Category:Stubs where they are more likely to be assigned a detailed tag like {{Widereceiver-1970s-stub}} or {{Lancashire-struct-stub}}. The point I raised on 28 April 2016 was a different one: It would be great if the page curation software would not allow editors to add {{stub}} to an article which already has a specific stub tag .... I'd still like to see that improvement. PamD 17:39, 15 June 2017 (UTC) Support I'd hate to reopen anu discussion, but I'd find this useful. Contrary to what TonyBallioni has said, stub sorting isn't consistently well-manned (resulting in hundreds of articles with a {{stub}} tag at times), nor with the amount of organization that NPP has. If a hotcat-like script for stubs that prompts you to do more specific stub tags can be created and then eventually added to page curation, I'd think that more specific stub categories would be added than PamD believes. Also, adding a stub tag, regardless of how specific it is, will eventually bring a second set of eyes. On the other hand, a primitive script orientated toward experience stub sorters would only make the problem worse, and it's better to have what we have already than to have that (that is, it's better to have nothing). Also, PamDs' idea of restricting the addition of a {{stub}} when a more specific stub tag would be a nice addition regardless.  I dream of horses (My talk page) (My edits) @ 20:33, 15 March 2018 (UTC) (Removed excessive indentation, added sentence at 20:36, 15 March 2018 (UTC)) As I've communicated to you before, I think you are dead wrong on this, and that it's fine to just tag with stub if someone can't figure out the stub tree, and will continue to do it myself, and think wasting developer resources on this would make page curation much more confusing. TonyBallioni (talk) 20:38, 15 March 2018 (UTC) @TonyBallioni: Well, we can't see if it's more confusing until something is released. -- I dream of horses (My talk page) (My edits) @ 23:28, 16 October 2018 (UTC) Comment @I dream of horses: I've put in a script request here for a userspace script to fill this role. A hierarchy based script would make stub tagging really easy, but I also agree with TonyBallioni that this isn't probably something that needs to be integrated with the Page Curation Tools. — Insertcleverphrasehere (or here) 22:36, 16 October 2018 (UTC) @Insertcleverphrasehere: Thanks; it's fine (and in fact, inevitable) if other scripts are given more priority.  I dream of horses (My talk page) (My edits) @ 23:28, 16 October 2018 (UTC) I have to add a note that a new script (User:Danski454/stubsearch) has recently been created, which allows searching by keyword as well as hierarchy style searching to quickly narrow stubs to the bottom of categories. Still not a high priority for this to be added to the PC toolset IMO. — Insertcleverphrasehere (or here) 21:17, 28 October 2018 (UTC)

24. Notability criteria

Done

Tracked in Phabricator Task T147224 Resolved Option to specify which notability guidelines a page fails when adding Notability tag. Suggested March 2013 by Atlantima. Kudpung กุดผึ้ง (talk) 13:35, 8 September 2016 (UTC) Raised again by AnupMehra, and VQuakr mid January 2014. There is an infeence here that editors are not using Page Curation because Twinkle offers better options for tagging. The WMF 'messenger' suggests that adding these features to Page Curation would simply add clutter. --Kudpung กุดผึ้ง (talk) 13:52, 8 September 2016 (UTC)  Done Or at least I think it's resolved. All the notability tags that are in Twinkle should be there now, along with other various tags that were previously absent — MusikAnimal talk 04:31, 4 October 2016 (UTC)

27. Delay

Opposed

I suggest that unpatrolled articles should be listed on the Page Patrol Feed only after a delay of at least 30 minutes. Given the new users could use the time to do (understand) whatever they want to do. I'm suggesting this because I have seen comparatively new users hastily tag bombing articles which are just 2 minutes old. I'm also of the opinion that Special:NewPages should officially be shut down. I understand that it is not the best thing in the world to keep any problematic page hanging around for 30 minutes – it may contain copyright vios or BLP vios, but what difference does it makes? Dozens of copyright vios are found daily on stale user subpages which during creation goes totally unnoticed. Furthermore, since I support the opinion of not indexing before patrolling, I think the delay will not make any major negative effects. Jim Carter 11:42, 2 October 2016 (UTC) Strong disagree - I'm aware of this problem, but attack pages and pure vandalism need to be removed at once to send a message that such content won't be kept and before webcrawlers syndicate the text to other pages. Also, if someone has created a page that is inappropriate but in good, or at least semi-good faith, they should be told why it's wrong before they sign out and do something else, rather than come back the next morning to find it got deleted without them having a chance to contest. We should change the culture on drive-by deletions by telling people off for doing it. Blythwood (talk) 12:16, 2 October 2016 (UTC) You both raise some valid issues and you both miss differnt other ones. Hence my opinion will probably meet opposition from both of you: Yes, Some pages must be deleted as quickly as possible, prticulary the G10 which must be folded and automatically light a red alert on administrators' control panels. Google has a resident bot on Wikipedia that indexes and references new articles the second the creator presses 'save'. BLPPROD and PROD were intended to be placed fast enough to catch the creatorswhie they are still logged in so that they have a chance to address the issues. A very high percentage of new article creators are SPA who skidaddle the moment they have left their dump on the carpet never to return. Page Curation has a feature for contacting the user to advise them that the article has been tagged. I'm currently listing above a request for a feature that does this automatically. Special:NewPages should officially be shut down but for the reason that because it is a real-time live feed, people hover over it with their mouses waiting to pounce, and that's why we can't encourage them to come to New Pages Feed which needs to be manually refreshed. I am asking the devs to make a continuous live feed available for it as an option. We will be asking for new pages to reain non indexed until they are patrolled. We will be asking for ACTRIAL to be implemented. Although we should avoid biting new users, they will in future be forced through the Article Wizard anyway and will be pampered by our cousins at AfC. So there you go, guys.The rest is up to you when you list all the features above in your order of preference on the poll page that you have been informed about. Kudpung กุดผึ้ง (talk) 14:00, 2 October 2016 (UTC) "they will in future be forced through the Article Wizard", that solves my concern, thanks Chris. Jim Carter 14:23, 2 October 2016 (UTC) @Kudpung: I just realized that even if we disable Special:NewPages, people can still see new page creations from Special:RecentChanges and with some small tweakings. Jim Carter 14:34, 2 October 2016 (UTC) Jim, Blythwood, I don't think the average patroller who has applied for and been accorded the Patroler right is going to want to start tinkering with computer technology just to get his own way to patrol new pages. The people who will see new pages at Special:RecentChanges will not have the right to patrol pages - this is one of the teasons why I included Twinkle in my RfC - which turned out not to be such a good suggestion - at least not within the scope of that RfC. The ultimate aim is to have all NPPers qualified and siniging from the sae page, not upset established users who are not patrollers but who come across a bad article lurking somewhere and want to tag it on the fly; tha's what the short-sighted, (and mostly offensive) opposers didn't stop to think about. Kudpung กุดผึ้ง (talk) 00:11, 3 October 2016 (UTC) Explicit community consensus is needed to shut down Special:NewPages.— Godsy (TALKCONT) 17:34, 22 November 2016 (UTC)

28. Tag for hist merge

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Several times I've come across a page during NPP that has been copy-pasted to a new title, rather than moved properly. It would be nice if the page curation toolbar would simplify placing the appropriate templates as described here. ~ ONUnicorn^{(Talk|Contribs)}problem solving 17:20, 3 October 2016 (UTC)

Thank you ONUnicorn, certainly worth considering. There is a bot that already includes an automatic edit summary 'possible cut and paste creation'. This information should be provided in the curation fly-out which up to now permanently displays "no isseus detected with this article'. --Kudpung กุดผึ้ง (talk) 02:45, 9 October 2016 (UTC)

Kudpung, do you think that this is any desirable? This can be easily added:-) ∯WBG^converse 14:39, 22 October 2018 (UTC)

Original request was fulfilled by me, months back but K's request is yet to be. ∯WBG^converse 12:52, 13 September 2019 (UTC)

Useful, see my comment above, but it is probably not one of the most urgent priorities. Kudpung กุดผึ้ง (talk) 04:33, 14 September 2019 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

30. Filter by experienced editor

Done via other efficient means.

It's currently tedious to look through the New Pages Feed in an attempt to find editors currently creating many articles who may be eligible for the autopatrol flag. There's a database report for editors who've created many articles, but many of these editors no longer create articles, so this isn't as useful as knowing who's active and eligible. Ideally, this would filter to only editors who've created 25 new articles, but we could also filter to 1,000 edits or similar if that's easier. ~ Rob13Talk 14:26, 15 October 2016 (UTC) Done by other means? The new version of the Editors eligible for autopatrol report seems to have solved this problem very nicely; it's now a list of editors who have 25 entries and have created at least one in the prior month. Innisfree987 (talk) 03:56, 4 June 2017 (UTC) Also see User:Rentier/NPP for editors with most unreviewed articles. Rentier (talk) 22:18, 30 June 2017 (UTC)

31. ORES integration

Done

ORES is a project that uses machine learning techniques to detect various types of edits. For a start, NewPagesFeed can be set up filter only pages determined to be vandalism by ORES. In the future, maybe a fifth model that detects whether an article will be deleted and even if it will meet individual CSD criteria can be made. Implementing ORES will help patrollers identify detrimental content faster, potentially boosting our currently low reputation for accuracy. Esquivalience (talk) 01:05, 3 November 2016 (UTC) (Copied from duplicate) Filter the content by "likely good faith contributors" or "likely bad faith" via ORES -- so that I could spend time on articles that likely could use some editor-love, for relatively good editors. — Preceding unsigned comment added by Kudpung (talk • contribs) 16:49, 5 June 2017 (UTC) I'd also just like to have the ORESarticle quality assessment (i.e. start/stub/B/C/GA) to be listed in the page curation feed. I have found the ORES assessment to be very good when using the new alpha version of therater tool, which features ORES integration. This would give a good idea about what the article quality is, and it would be awesome to be able to 'sort' by ORES assessed article quality. This would help users review the quality of articles that they want to, and would also help in identifying potential candidates for DYK from the new page feed (which are usually assessed by ORES as B or better, sometimes even assessed as GA). — Insertcleverphrasehere (or here) 21:33, 12 November 2017 (UTC)

32. Additional tools

User:Looie496/Watchlist pinging: Suggested 2011 by Looie496 in a user space essay (probably why it has gone largely unnoticed), this could well be a valuable feature for seriously minded patrollers. This may be possible as a local script of some kind without WMF intervention to the MedaWiki software. Kudpung กุดผึ้ง (talk) 03:49, 19 September 2016 (UTC)

• Support It's like Looie946 was reading my mind--I'm often reluctant to nominate for deletion right away, but have no mechanism to track which entries to circle back to if not improved (as, ironically, if they're not edited, then they don't show up on my watchlist--even though the abandoned ones are the ones that need addressing). Innisfree987 (talk) 04:24, 4 June 2017 (UTC)

User patroll report, one of the most valuable tools for monitoring New Pages Patrol. CReated 2013 by Scottywong,its later versions also included repports on who has recently been patrolling and wo the most active patrolers were. Editors taking the responsibily of porting tools to labs from ToolServer apparently declined to maintain this. Perhaps TParis, or MusikAnimal could look into it. --Kudpung กุดผึ้ง (talk) 02:54, 24 September 2016 (UTC)

• Integration of "Previous AfD/Previous deletion" notices. There is a user script for this but you have to know it is there and install it. Jbh^Talk 14:08, 2 October 2016 (UTC)
• I never got the ping, but improving the User Patrol Report is something I'd be interested in :). I assume Jbhunley is talking about WP:MOREMENU that indicates if a page has previously been at XfD? Indeed the info is not very obvious, but that's not what MoreMenu is for anyway. This would be a fine addition to Page Curation. Kudpung, are these suggested improvements logged on Phabricator? We should try to port them if possible so we can squeeze them into our developer sprints as 10% time (extracurricular) — MusikAnimal ^talk 04:46, 4 October 2016 (UTC)

MusikAnimal, I'm hoping other users will help me share the work on these initiatives so I haven't personally logged any requests at Phabricator - ever. I don't know how to do it and I'm still smarting from my experience with the WMF devs at Bugzilla over ACTRIAL. That said, my global account lets me log in to Phab and I am able to make comments there and offer suggestions. Kudpung กุดผึ้ง (talk) 06:37, 4 October 2016 (UTC)

• Watchlist ping-back may be discussed over a separate CT_Project:- meta:Community Tech/Watchlist item expiration. I don't know what all User-Patrol did but the sole-mentioned job - maintaining a list of active reviewers - has been taken over by User:Community Tech bot. A flag about previous deletion has been now integrated into the NPP. Overall, nothing more to do over here. Archiving. ∯WBG^converse 13:11, 14 September 2019 (UTC)

33. Template:New unreviewed article

Template deleted

Tracked in Phabricator Task T207234 Curator should automatically remove Template:New unreviewed article when the article is reviewed, especially since likely very nearly 100% of the time it is placed automatically by the new article tool. I'm getting the feeling that a lot of people either assume it already does this, or aren't really sure that they should currently be manually removing the template from reviewed pages. TimothyJosephWood 14:45, 4 November 2016 (UTC) Yes please! Innisfree987 (talk) 04:25, 4 June 2017 (UTC) Support complete no brainer. Really surprised this wasn't baked in. Have removed tag that another patroller missed. Lineslarge (talk) 20:52, 25 September 2017 (UTC) Support as an obvious oversight. — InsertCleverPhraseHere (or here) 20:54, 25 September 2017 (UTC) Support agreed. TonyBallioni (talk) 21:02, 25 September 2017 (UTC) Support — An obvious plus that would make the lives of NPRs just that much easier. Regards, SshibumXZ (talk · contribs). 07:34, 19 October 2018 (UTC) Support — Kudpung กุดผึ้ง (talk) 10:22, 22 October 2018 (UTC) Kudpung, umm, suppose that this is executed........ Now Article A was churned out of Article-Wizard by a non-autopatrolled editor, which slaps this template.I, from the NPP feed click the review button which simultaneously removes the tag.But, if I choose to revert my review (by myself), do you wish that the tag be re-slapped back? At any case, I am inclined to think that rather than integrating this into NPP, it might be far better to design a bot that removes such tags, once it is reviewed.And, my guess is that such a bot can be easily constructed rather than persuading the devs to look into this and integrate it to the main suite.I am fairly sure that it can't be executed from NPP through a on-wiki manner. ∯WBGconverse 14:53, 22 October 2018 (UTC) A bot would definitely be easy to create (and useful enough at-least to remove old tags like this one) - although, I've never got the point of the template? Any new pages are listed in the new pages feed so I'm not sure what the point of the template is. Galobtter (pingó mió) 15:01, 22 October 2018 (UTC) Galobtter, my guessis that it was meant to aware a general reader that the content is yet to undergo some sort of special scrutiny and hence, may suffer from certain undocumented faults.So, readers, do not take it to be as perfect, as it looks like, (sans any note-of-concern/tag and all). But, I'm not certain enough.K, ScottyWong et al can provide a far better perspective ∯WBGconverse 15:36, 22 October 2018 (UTC) This is the original discussion on it - doesn't seem to have this purpose.. Galobtter (pingó mió) 15:41, 22 October 2018 (UTC) I don't think a bot is the best solution. Reviewers will still end up doing it manually themselves, and results in time-lost for an obvious oversight that should simply be fixed. — Insertcleverphrasehere (or here) 08:43, 29 October 2018 (UTC) Galobtter and Winged Blades of Godric, Actually, I think that there is a better solution. Get rid of Template:New unreviewed article; take it to TfD. Its a relic of a time long past. It is no longer created by the article wizard (which only creates drafts now), and now that we have the new pages feed, nobody keeps track of Category:Unreviewed_new_articles. It seems to only be added to new pages by users that know that the template exists. Twinkle will have to be notified, as it is one of the basic templates there, but clearly isn't used hardly at all (and if it is, its use is superfluous). All but about 20 of the articles in that category are not in the New Pages Feed, many stretching back to 2016! — Insertcleverphrasehere (or here) 18:31, 29 October 2018 (UTC) @Insertcleverphrasehere and Winged Blades of Godric: Tfded Galobtter (pingó mió) 06:21, 30 October 2018 (UTC)  Done Template:New unreviewed article has been deleted. Pkbwcgs (talk) 16:39, 9 November 2018 (UTC)

34. Removing the 250 character limit

Done

Tracked in Phabricator Task T157056 Resolved Could we remove the 250 character limit when sending messages to page creators? This is extremely easy to exceed when suggesting multiple ways an article could be improved and seems to be an unnecessary inconvenience, as any reviewer could go around it by creating a new user talk page section from scratch. The text in green is what exceeded 250 characters in this suggestion. Forcing brevity might lead to explanations that are more vague and ultimately more confusing for newcomers. Mz7 (talk) 20:00, 4 November 2016 (UTC) Originally posted at Wikipedia talk:Page Curation#250 character limit. Mz7 (talk) 20:00, 4 November 2016 (UTC)

35. Using draft talk pages

Under discussion at AfC

Per this discussion and that discussion, we could start leaving review comments on draft talk pages? (There needs to be another on-wiki measure to make talk pages easier for newcomers to discover; this can be achieved by banners or messages as appropriate and is discussed on wiki elsewhere.) Gryllida (talk) 20:33, 14 November 2016 (UTC) Just as a procedural note, this is a cross-post from here. The discussion should probably happen in only one location (though I have no opinions on which talk page it takes place). Primefac (talk) 23:10, 14 November 2016 (UTC) Thanks. I believe this note is more about bug report for the Page Curation tool; I haven't identified another place where its bug tracker happens, apart from here. (I concur that the link you gave would have been useful for me to include.) --Gryllida (talk) 01:10, 15 November 2016 (UTC) Gryllida, these issues are not New Page Review specific and strictly belong somewhere else, such as the AfC talk page. We are not concerned here with AfC. Kudpung กุดผึ้ง (talk) 18:22, 15 November 2016 (UTC) Sorry, was confused in another discussion; followed up. --Gryllida (talk) 00:29, 16 November 2016 (UTC)

36. Key word search

A user tool has been developed

Is it possible to introduce a keyword search for the New Pages Feed filter. I am happy to work on the backlog but would rather review pages closer to my area of interest.Peter Rehse (talk) 09:22, 26 November 2016 (UTC) PRehse. The feed does have certain optional selections for filtering. New filters are being discussed but they are not a high priority and it will not be possible to filter new pages by content topic. There is nothing to prevent you from simply going through the feed and reviewing articles that interest you. --Kudpung กุดผึ้ง (talk) 09:52, 26 November 2016 (UTC) Doing that - but it is hard to tell sometimes from title and the few lines of text visible. I get the newest pages through other means but ... well it was just a suggestion as I am sure I am not alone in that wish.Peter Rehse (talk) 10:02, 26 November 2016 (UTC) There are indeed other means, Peter, but none that prove such an overview and background detail of both the article and its creator as Special:NewPagesFeed, and we're working on making it even better. --Kudpung กุดผึ้ง (talk) 12:02, 26 November 2016 (UTC) Topics I no longer feel qualified/ have no desire to evaluate: footballers (there are a thousand of these being added per day, all de facto notable, virtually always), movies and actors from India (same thing), and train stations/ intersections/ villages in the Middle East and Asia. If I could lump them all together and turn to someone and say, "What do you think about these?" I would do so. Would rather they didn't appear in a list for me to have to even look at. (Quick example: of the next 40 pages needing patrolling: 7 on footballers/ football, 5 on Asian landmarks, two on Indian actors, and the remainder "other"— that does give "other" an edge, I will admit...). Yes, I am grumpy. That's the magic of being a volunteer!  :-) KDS4444 (talk) 15:14, 28 November 2016 (UTC) We know, we know, KDS4444, and that's why you have volunteered to review new pages. Ironically, if you filter out those articles, there will be nothing left to review... Kudpung กุดผึ้ง (talk) 17:45, 28 November 2016 (UTC) (Smart alec.) KDS4444 (talk) 09:51, 29 November 2016 (UTC) Cute.Peter Rehse (talk) 17:56, 28 November 2016 (UTC)

38. AfD categorization and sorting

Not sufficiently important

The Curation tool does not do either basic AfD categorization or deletion sorting. The former is needed to give it equivelent functionality to Twinkle, which overall is required if the goal of getting people to move from Twinkle to the tool is to be met. The later, while the delsort script is good enough, would streamline the process and also lead to more reviewers doing sorting at the time of nomination which would cut down on the need for others to it. JbhTalk 17:14, 6 December 2016 (UTC) I agree that the curation tool should have some of Twinkle's features, but I wonder how important this really is. In my experience, there are wikignomes who diligently delsort AfDs and they seem to be able to keep up with the volume.- MrX 16:07, 15 June 2017 (UTC) Per MrX I don't think this is very important. Similar to stub tagging, the issue is that the average reviewer won't know all the categories anyway, so it is best left to the experts. — Insertcleverphrasehere (or here) 07:31, 19 October 2018 (UTC) Some of the workload could be tackled by a bot job. Scan uncategorised AfDs, check the article's talk page, if it's tagged with {{WP Biography}} categorise the AfD as a B. Other categories as per the relevant project's classification at Wikipedia:WikiProject Directory... Cabayi (talk) 11:27, 28 October 2018 (UTC)

40. deletion logs

Continue discussion at #55 below

Tracked in Phabricator Task T207237 would be very nice if it supported CSD/PROD logs, similarly to twinkle. -- Aunva6talk - contribs 01:30, 3 May 2017 (UTC) @Aunva6: It does. They are stored in a system log that you can accees by clicking on your logs and then limiting to deletion tag log. it does, @Aunva6 and TonyBallioni:, but only for Reviewers who are using Page Curation, which is the tool that was created specifically for patrolling new pages. Kudpung กุดผึ้ง (talk) 16:46, 5 June 2017 (UTC) Note This same request is duplicated as #40, #55, and #64. — Insertcleverphrasehere (or here) 23:09, 16 October 2018 (UTC)

41. Filters

See #36 Keyword seaching
new filters on the patrol backlog by WikiProject or other way of evaluating the domain of the content (for example, could use the report criteria of User:AlexNewArtBot) -- that way I could know that there is a good chance of a patroller with domain interest to look at the page. (for example, I use Bambot to do this with Category-based backlogs) . Sadads (talk) 22:30, 19 June 2017 (UTC)

43. Date range filter

Tracked in Phabricator
Task T167475

Be able to filter new pages by a date range within Special:NewPages Feed to make pages in the middle of the backlog easier to access and review

@Mduvekot, ONUnicorn, and Kaldari: I've added this to phab since it seems like something that no one would oppose and would have a fair amount of benefit. Kaldari: alerting you so you can follow or alert others if needed/ask for any explanations. TonyBallioni (talk) 22:33, 8 June 2017 (UTC)

Thanks. Sounds pretty straightforward. Kaldari (talk) 22:37, 8 June 2017 (UTC)

Support - yes, probably very useful to be able to select which 'ignored' middle bit of the list to work amongst. Nick Moyes (talk) 22:42, 8 June 2017 (UTC)

Thanks!~ ONUnicorn^{(Talk|Contribs)}problem solving 00:38, 9 June 2017 (UTC)

Thanks from me too, obviously. I really appreciate all the work you're putting into this TonyBallioni Mduvekot (talk) 01:02, 9 June 2017 (UTC)

• Support - This ties into my suggestion below. And please make it easy to use, with a slider or at least a calendar widget. It shouldn't require keyboard input and or multiple mouse actions.- MrX 21:04, 15 June 2017 (UTC)

MrX, if you could make that suggestion in the phab task so those working on it can see it, it'd probably be more likely to be acted on. TonyBallioni (talk) 21:07, 15 June 2017 (UTC)

45. Curation panel size

Done

Tracked in Phabricator Task T207439 Resolved The Curation window should be bigger, and resizable by clicking and dragging its corners. This would bring it more in line with the slightly better clarity and overview in the Twinkle window. It would obviate the necessity to scroll it down to see and click on the 'add this comment' button. Kudpung กุดผึ้ง (talk) 00:49, 9 June 2017 (UTC) I disagree with making it bigger by default. It already intrudes on the article if you don't have your window full screen. However, allowing people to resize it at will by clicking and dragging corners is an acceptable compromise. ~ ONUnicorn(Talk|Contribs)problem solving 03:45, 15 June 2017 (UTC) I agree with ONUnicorn about not making it larger by default, but I do support allowing it to be resized by users.- MrX 15:43, 15 June 2017 (UTC) Currently it hides the button that adds the PROD information. That needs addressing. Kudpung กุดผึ้ง (talk) 16:27, 15 June 2017 (UTC) I'm pleased this issue has already been identified as a need. I am so fed up with trying to type helpful (and admittedly sometimes rather detailed) feedback to article creators and being unable to preview or even see the entire block of text I'm working on. This would be a most welcome addition to the Page Curation tool. Nick Moyes (talk) 22:14, 10 October 2017 (UTC) Accessibility is clearly an issue. Note Nick Moyes that you currently can drag to resize the text box for 'message to creator' as well as the messages that you can leave while tagging, but this drag option isn't available for text windows for the G12 CSD URL window (for example). It would also be good to have a resizable window in general, to improve accessability on different screen sizes and for people that need a bit more zoom. — Insertcleverphrasehere (or here) 07:51, 19 October 2018 (UTC) Well, blow me down, Insertcleverphrasehere! All this time, and I hadn't noticed the inconspicuous'expand' function in the lower right hand corner of the comments box. So every time I used it I was reminded of the joke about the gynaecologist who took a week off work in order to redecorate his hallway through his letterbox. Thank you for pointing it out - I'd always been hoping I could mouse over one of the borders and expand it that way. Doh. Nick Moyes (talk) 08:01, 19 October 2018 (UTC) Barkeep49, apparently this is now done if I have understood ye jargon at Phab. Could someone please verify and collapse this section if appropriate. Kudpung กุดผึ้ง (talk) 04:18, 13 September 2019 (UTC)

46. Page feed: added 'previously deleted'

Duplicate proposal of #7. Recreations
Add 'Previously deleted'. This would highlight recreations. This should not be too difficult to implement. Kudpung กุดผึ้ง (talk) 7:52 am, 9 June 2017,

48. Encourage new patrollers to qualify as New Page Reviewers:

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

When reviewing a page and seeing that it is already tagged, we should be able to send a notification to patrollers who added the tags, point out improper reviewing practices and encouraging them to apply for NPR:

Hi. Thank you for patrolling new pages. You tagged xxxxxx for one or more issues, but you did not check it as patrolled. Also, As you did not inform the author it may remain as a permanently tagged article. If you are not already a New Page Reviewer, and if you already have sufficient experience you may wish to check out this user right and apply for it at WP:PERM.

Kudpung กุดผึ้ง (talk) 01:03, 9 June 2017 (UTC)

@Kudpung: The overall request here (encourage patrollers to request NPR rights) is not possible because you have to have NPR rights to use Page Curation. You might manually add tags or use Twinkle but even if we could detect this, which we can't, there's nowhere to expose this message. Everything is bundled into Page Curation which again requires you have new page reviewer rights. On the other hand if you are a NPR and you use Page Curation to add tags, it will automatically mark the page as patrolled and I think (?) notify the author about it, so correct me if I'm wrong but I don't see how the above scenario could happen — MusikAnimal ^talk 00:21, 15 June 2017 (UTC)

@MusikAnimal:Yes, I think you are wrong. ;) Unless I am very much mistaken, all taggings are shown in the curation toolbar. It's easy to tell from there if the tagger is a qualified New Page Reviewer or not. Text above slightly modified. My motivation is not to find reasons not to update and improve the NPP system software, but to encourage more users to use it :) Kudpung กุดผึ้ง (talk) 00:38, 15 June 2017 (UTC)

@Kudpung: You see that a page has been tagged in the Page Curation toolbar because you are able to use Page Curation. The toolbar is not visible if you are not a new page reviewer, hence there is nowhere to expose this message. The message above also lets the user know if they have not informed the author that they tagged the article, which sounds like a different request than "encourage new patrollers to request NPR". Also if they are not going about standard reviewing procedures, I'm not sure we should be encouraging them to seek NPR rights in the first place — MusikAnimal ^talk 00:46, 15 June 2017 (UTC)

@MusikAnimal:. My motivation is not to find reasons not to update and improve the NPP system software, but to encourage more users to use it :) Kudpung กุดผึ้ง (talk) 00:57, 15 June 2017 (UTC)

I'm with you there, but all due respect, I don't believe this request as currently laid out is possible or perhaps even desirable — MusikAnimal ^talk 01:02, 15 June 2017 (UTC)

MusikAnimal I think you have completely misunderstood me there. Perhaps I expressed my self badly. Now if we were in a proper working environment, or at least a collaborative one of the kind where people were ready to talk over video links, this would be resolved in seconds. Kudpung กุดผึ้ง (talk) 10:36, 15 June 2017 (UTC)

Sorry! I get it now. You meant you as the user of Page Curation should be able to notify the previous patrollers of a page who added the tags, not let the software automatically do it. This was ambiguous to me so I have reworded your request a bit. I still however think there are two requests here "notify new and/or unqualified patrollers who are not getting it right" and "Encourage new patrollers to qualify as New Page Reviewers". Do we really want to do this with the same message? — MusikAnimal ^talk 17:43, 15 June 2017 (UTC)

• Oppose-This plan need to get a lot-detailed and will add a lot of unnecessary bloat.Some manual touches to the workflow are desirable.∯WBG^converse 15:57, 22 October 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

49. Notifying creators of tags

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Tracked in Phabricator
Task T204464

All tags maintenance tags of any kind other than AfD, PROD, BLPPROD, NotEnglish, (which all do this anyway), should leave this message on the creator's talk page:

A new page patroller has reviewed an article you created at xxxxx and has found some inconsistencies with our guidelines. Please return to the article and address the flagged issues. In some cases the tags may eventually lead to deletion of the article. For more information please read WP:My first article or ask a question at The Teahouse

Kudpung กุดผึ้ง (talk) 01:09, 9 June 2017 (UTC)

• Support, provided that this only applies to new users.- MrX 15:12, 15 June 2017 (UTC)
• Support Personally although I've created thousands of articles, I would appreciate a message when an article I created is tagged, because I would definitely go there to try to solve the problem, as many editors would, so I would support something with different wording for that. The wording here is well-suited to those who aren't autopatrolled. Boleyn (talk) 05:35, 14 July 2017 (UTC)
• This could be partially addressed by Phab T204464 (configurable messages). Though it would be nice to have a different message for autopatrolled users. — Insertcleverphrasehere ^{(or here)} 07:59, 19 October 2018 (UTC)

  Insertcleverphrasehere, This ought to happen and there even exists a template, created by the devs. But, for some unknown reason, it has been never integrated into the code or has been kicked out, at some point of time. ∯WBG^converse 08:32, 28 October 2018 (UTC)

  Template:Taggednonote-NPF is the template. Need to dig .... ∯WBG^converse 06:51, 14 September 2019 (UTC)

  Noting this. ∯WBG^converse 12:26, 14 September 2019 (UTC)

• Support -- support very strongly, but when it's done we should have control of the messages, not have them hard-coded, and they should be subst'd to allow people placing the tags to change them as needed for particular cases. DGG ( talk ) 04:42, 14 September 2019 (UTC)

Closed at Phab a year ago as 'resolved' by Galobtter . I realise that making the message templates is now locally configurable (or is at least a work in progress), but could someone please check that this is so. Kudpung กุดผึ้ง (talk) 04:42, 14 September 2019 (UTC)

No, I checked just now. ∯WBG^converse 05:06, 14 September 2019 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

50. Proposing Autopatrolled for user creating new articles of a very high quality

Not a priority, out of scope for NPR

Tracked in Phabricator Task T207441 When reviewing a page and seeing it is of great quality, we should be able to send a notification to the page author encouraging them to apply for autopatrolled: If you have created 25 or more articles to this excellent standard, please apply at WP:PERM for your account to be autopatrolled so that your new articles no longer need to be reviewed. Kudpung กุดผึ้ง (talk) 01:09, 9 June 2017 (UTC) Same as with #47 above, if the user is not a new page reviewer the Page Curation toolbar is not usable, so there's nowhere to expose this message. Even if you are a NPR, the toolbar is not shown on articles you yourself have created. Also I would be hesitant to use the language "...this excellent standard" as we can only automatically detect basic issues with an article. Only humans can truly ascertain an article as high-quality or even acceptable. This particular request I don't think we need to worry too much about anymore, though. Wikipedia:Database reports/Editors eligible for Autopatrol privilege has been revamped, is now updated daily and only reports active page creators. We have a group of users who regularly go through this report and nominate users at WP:PERM/A — MusikAnimal talk 00:55, 15 June 2017 (UTC) MusikAnimal , Again, I think you have completely misunderstood me here. Perhaps I expressed my self badly. Now if we were in a proper working environment, or at least a collaborative one of the kind where people were ready to talk over video links, this would be resolved in seconds. Kudpung กุดผึ้ง (talk) 11:02, 15 June 2017 (UTC) Yes I did. It's clicking now, I am truly sorry. You meant the Page Curation user should have a way to send this notification to the author of the page. I have reworded the request, hope this is OK! Please copy edit if I've got it wrong. I have some reservations about this request but I can share them later. For now let's just make sure it's clear what we want — MusikAnimal talk 18:22, 15 June 2017 (UTC) Together with [[3]], I have put these through as a request to be added to the 'Wikilove' section as templated options for High Quality Submissions. — Insertcleverphrasehere (or here) 08:11, 19 October 2018 (UTC) Oppose-The database is excellent (and we don't need to ask them, as to if you have created 25 articles or so, go apply for a hat) and is well-monitored.Overall, a largely-redundant feature. I support the DYK-case, though:-)∯WBGconverse 16:00, 22 October 2018 (UTC)