Misplaced Pages

talk:Did you know: Difference between revisions - Misplaced Pages

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 18:43, 23 July 2011 editQrsdogg (talk | contribs)Autopatrolled, Pending changes reviewers6,586 edits →Multiple RFCs confusing, simply remove DYK from the mainpage: o← Previous edit Latest revision as of 20:59, 22 January 2025 edit undoSL93 (talk | contribs)Autopatrolled, Extended confirmed users, New page reviewers, Pending changes reviewers, Template editors79,406 edits →long-legged lovebird 
Line 1: Line 1:
]<!--
-->
{{ombox {{ombox
|style=color:black; background-color:#fff; padding:1em; margin-bottom:1.5em; border: 2px solid #a00; text-align: center; clear:all; |style=color:black; background-color:#fff; padding:1em; margin-bottom:1.5em; border: 2px solid #a00; text-align: center; clear:all;
|text=<div style="font-size:150%;">'''Error reports'''</div>Please '''do not''' post error reports for the current Main Page template version here. Instead, post them to ]. If you post an error report on one of the ] here, please include a '''link''' to the queue in question. Thank you. |text=<div style="font-size:150%;">'''Error reports'''</div>Please '''do not''' post error reports for the current Main Page template version here. Instead, post them to ]. Error reports relating to the next two queues to be promoted can also be posted to ERRORS. If you post an error report on one of the ] here, please include a '''link''' to the queue in question. Thank you.
}} }}
{{DYK-Refresh}}
{{DYKbox|style=font-size:88%; width:23em; table-layout:fixed;}} {{DYKbox|style=font-size:88%; width:23em; table-layout:fixed;}}
{{shortcut|WT:DYK}} {{shortcut|WT:DYK}}
{{archives|• ]<br/>• ]<br/>• ]<br/>• Removed hooks: ]
{{archives
|style = font-size:88%; width:23em; |style = font-size:88%; width:23em;
|auto = yes |auto = yes
|editbox= no |editbox= no
|search = yes |search = yes
|prefix = Wikipedia_talk:Did you know/Archive |searchprefix = Wikipedia_talk:Did you know/Archive
|index = /Archive index |index = /Archive index
|bot=lowercase sigmabot III

|age=5
|bot=MiszaBot
|collapsible=yes
|age=7

<!-- |1=<p style="text-align:center;">]</p> --> <!-- |1=<p style="text-align:center;">]</p> -->
}} }}
{{todo
|small=yes
|style=font-size:88%; width:23em; table-layout:fixed;
|9
}}
{{User:MiszaBot/config {{User:MiszaBot/config
|archiveheader = {{aan}} |archiveheader = {{aan}}
|maxarchivesize = 250K |maxarchivesize = 600K
|counter = 68 |counter = 204
|minthreadsleft = 5 |minthreadsleft = 5
|algo = old(7d) |algo = old(5d)
|archive = Misplaced Pages talk:Did you know/Archive %(counter)d |archive = Misplaced Pages talk:Did you know/Archive %(counter)d
}}{{User:HBC Archive Indexerbot/OptIn
}}
{{User:HBC Archive Indexerbot/OptIn
|target=/Archive index |target=/Archive index
|mask=/Archive <#> |mask=/Archive <#>
|leading_zeros=0 |leading_zeros=0 |indexhere=yes
|indexhere=yes
}} }}


This is where the ''']''' section on the main page, its policies, and its processes can be discussed.<!-- for nominations: see ... -->
{{DYK-Refresh}}

This is where the ''']''' section on the main page, its policies and the featured items can be discussed.<br><br>

== Main page features ==

A ] is underway to discuss what features the community desires to see on the main page. Please participate! Thanks. ] 19:22, 13 July 2011 (UTC)
*Still looking for participants. ] (]) 01:12, 21 July 2011 (UTC)

== All the queues are empty. All the preps are full. ==

Also, please try to have France-themed articles show up on the front page during a part of July 14 when France is awake, not asleep. Thanks! <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 01:09, 14 July 2011 (UTC)

:I have filled out one and a bit prep areas. If someone could continue loading prep areas, that'd be great. I can upload to queue later. ] (] '''·''' ]) 02:48, 15 July 2011 (UTC)

::I've done four more, and Crisco 1492 has done another. The biggest problem I see is that most of the many nominations from before 9 July had not been reviewed ''at all''. I've spent several hours today wading through a lot of these, and have posted initial evaluations. Most of those that checked out have already been moved to a prep area. As for the others, I've marked some as having unusable hooks, or as needing copy editing of the article itself. However, there are still ''many'' nominations in need of checking, even if it's just a preliminary check. Most of these are biographies or buildings.

::Prep areas 1, 3, and 4 currently contain nominations I've selected, so someone else should double-check and set those into a queue (when space allows). A few of those nominations were older, unreviewed noms that I reviewed and moved in ], so a double check of my work is in order. --] (]) 21:00, 15 July 2011 (UTC)

== Up or out: "From Misplaced Pages's newest content" ==

When I was making up Prep last night, I wanted to clear some of the backlog of older articles but most of them didn't have the magic checkmark. Three items created July 2 do not have even one review. I suggest we review articles from the backlog, NOT articles recently added, until the backlog is cleared. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 11:39, 15 July 2011 (UTC)
:As I say above, I noticed this problem as well. I've reviewed and moved quite a few of these, and have noted problems with a few more.

:Current statistic: about '''25''' nominations in 2-6 July, but only '''3''' of those cleared for use.

:However, I've now been at DYK for nearly <s>four</s> five hours straight and will need a break to do other things now :P --] (]) 21:07, 15 July 2011 (UTC)
::Thanks, EncycloPetey, your work is appreciated! <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 23:50, 16 July 2011 (UTC)
:::A good few more have been reviewed. Hopefully the backlog is more manageable. ] (]) 02:29, 23 July 2011 (UTC)

== Verifying science articles ==

I've seen a fair number of science articles get posted to DYK lately that have absurd claims or outright misinformation in them. I'm not talking about scientific controversies, just basic facts that are wrong or extremely outdated. Can reviewers PLEASE post requests to review scientific or technical articles to the relevant WikiProjects BEFORE the DYK goes live? Otherwise our DYK section is going to erode Misplaced Pages's reputation for accuracy. ] (]) 21:39, 16 July 2011 (UTC)
:There is already a ''lot'' of work going on just to keep up with DYK without requiring the ''volunteeers'' to post an additional set of notices. If the relevant projects wish to check in and review nominated articles, they can always do that, and it will help the overtaxed DYK project when they do. Any nominated article can be checked, often a week or more before selected for the Main Page. --] (]) 21:49, 16 July 2011 (UTC)
:: You mention "a fair number" of articles "lately" with "absurd claims"; please do give a few recent examples so we can see where we went wrong. We haven't had many chemistry or physics articles, but we do have a lot of articles about animal and plant species. As a member of WikiProject Life, I posted an invitation over there, more eyes are always welcome. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 21:59, 16 July 2011 (UTC)
:::We could try including the specific source, page, link, etc. in the comments for all science articles? The main problem with them is that their 'facts' are often not as clear cut and easy to find as normal news, website, or book-cited articles By providing source info, we save the reviewer the hassle of searching for them inside journals.--&nbsp;'''<span style="font-family:century gothic">]&nbsp;]</span>''' 22:13, 16 July 2011 (UTC)
::::Kaldari, these should be raised at the time and on an individual basis. Even retrospectively is helpful so we can review process. ] (] '''·''' ]) 23:48, 16 July 2011 (UTC)
:::::The problem is that no matter how well DYK volunteers review the articles and check the sources, if the article is on an obscure topic, only people from the respective WikiProjects are going to be able to tell if the articles are actually accurate or not. In the case of science articles especially, we have a problem with people using outdated sources, since those are generally the ones most likely to be accessible online (ironically). Then there is also the problem of people simply not understanding the subject they are writing about. I think if no one is available to review a technical or scientific article for accuracy, it shouldn't be approved for DYK, no matter how many citations it has. Otherwise, we are just spreading misinformation. ] (]) 07:26, 17 July 2011 (UTC)
* The rule change you propose would be a substantial one. Could you give examples of a few recent science DYKs showing a problem with "spreading misinformation" and/or "absurd claims"? <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 12:28, 17 July 2011 (UTC)
** I'd rather not embarrass the authors as I'm sure they were written with the best of intentions. Perhaps I should amend my proposal to say articles on ''obscure'' topics, as this doesn't seem to be much of a problem with run-of-the-mill science articles (where the reviewer would probably have a basic knowledge). And I'm sure the same problem could happen with an article on 17th century Russian literature or any other obscure topic. Basically, I would suggest that if the reviewer has no knowledge of an article's subject whatsoever, they request the nominator to get someone from a relevant WikiProject to vouch for the article. And they don't have to vouch for every detail, just vouch for the fact that the article wouldn't sound absurd to someone familiar with the field. ] (]) 19:18, 17 July 2011 (UTC)
***Well, there's not much the project can do for you if you want to come here insisting on horrible problems that are occuring but refuse to point out any of them specifically. <b class="IPA">]</b>&nbsp;(]) 02:56, 18 July 2011 (UTC)
Kaldari, I don't know if you're referring to any of the DYKs I have written, but if you are, please tell me, so I can fix them and avoid similar problems in the future. ] 12:00, 20 July 2011 (UTC)

== Good articles redux ==

Given this trial at ] which ended 22/18 after one month of voting - is it worth relooking at as a trial? There is some discussion at ]. I'd normally not do anything but I doubt there will be clear consensus or plan of action on that page for a couple of months. So how about the following, which is modest and doesn't disrupt the existing process much. ] (] '''·''' ]) 23:58, 16 July 2011 (UTC)

To whit - I am proposing a modest trial outlined below, that doesn't impact greatly on the current process but give us a flavour of possible how it'd work?

*Recently Listed Good Articles eligible - i.e. within five days of Listing.

*A limit of 1 (or 2) GAs per set of hooks '''''(please specify number below)'''''.

*Change mainpage from "newest articles" (which 5x expansions aren't anyway) to "newest and newly-improved articles"

*Review after a month and see how folks feel about it.

===Support===
# '''Support''' It has to be acknowledged that Misplaced Pages is ten years old and needs to slightly shift focus from quantity to quality. Since DYK includes quantitative improvements (i.e. 5x size) it should also allow major qualitative improvements (i.e. reaching GA status). I think a short trial as proposed is a good idea with no major risks involved and it would be fair to test the assumptions of both supporters and opposers of the proposal. GA's which already featured as DYK should be excluded IMO. I think one GA per set of hooks would suffice for the trial, but I would like to see it at the top of the group. --] (]) 01:43, 17 July 2011 (UTC)
#I don't see any harm in a trial, but care must be taken so that we aren't biased towards a certain topic area. The arts and sports articles have a higher GA rate than other areas. —] (] · ]) 03:33, 17 July 2011 (UTC)
#'''Support''', with a caveat, which is probably obvious anyway, that newly made GAs that had previously been on DYK are not eligible and don't get to be featured twice. For the most part this is of no practical significance, but I have seen some articles go from new->DYK->GA very quickly (one of mine travelled this path in less than two weeks). The inclusion of GAs in DYK should be a reward for genuine old-article improvement, which is the essence of this proposal as I understand it.] (]) 05:47, 17 July 2011 (UTC)
#Great idea, let's at least try it and see how it goes. ] ] 07:13, 17 July 2011 (UTC)
#I'm a bit wary, but let's see how a trial goes. There's no harm in that. ]&nbsp;<sup>]] ]]</sup> 07:21, 17 July 2011 (UTC)
# I'd like to see a trial of this. It seems like a way to get some more high-quality content on the main page, encourage GA writers and reviewers, and foster a bit of crossover between DYK reviewing and GA reviewing. ] ] 17:20, 17 July 2011 (UTC)
# '''Strong Support'''. ] hit the nail on the head - we need to shift our focus from quantity to quality. As mentioned in the section above this one, some of the articles that appear on DYK are really quite embarrassing as they haven't been checked for sanity by anyone familiar with the topic. More importantly, since DYK articles have to consist of a substantial quantity of new content, this excludes anyone who takes a slow collaborative approach to building articles - i.e. the wiki way. Instead it rewards authors who write their articles offline and then post the finished product. These articles are then rushed through DYK before anyone familiar with the topic has had a chance to look at them. Good articles have none of these problems and are much more deserving a spot on the main page. At the very least, we shouldn't be completely excluding them. ] (]) 19:34, 17 July 2011 (UTC)
#: Rushed? nominations typically sit for a week or two before being used. Can you provide ''examples'' of articles that haven't been checked for sanity? This isn't a DYK problem in any case, as I've seen embarassing GA approvals as well. Why haven't editors in the various projects stopped in to help with that? I typically check articles against their sources, and evaluate sources when I approve hooks. You could do the same, and so can others. With a week or more before the nominations are used, that gives you plenty of time to help. --] (]) 22:37, 17 July 2011 (UTC)
#::I agree we sometimes have embarrassing GA approvals as well, but if the article has been around for a while it's far more likely that someone knowledgeable on the topic will have stumbled across it and fixed the glaring errors. Now that I've noticed the problem, I'm definitely going to try to be more active at looking at DYK nominations before they go live (rather than after), but regardless, I don't think adding in some GA articles will hurt anything. ] (]) 00:49, 18 July 2011 (UTC)
# '''Support''' There are a fair number of GAs which don't have much FA potential. The proposal both allows for more of our better articles to be brought to public attention and for users who improve Misplaced Pages to get their work seen more by the public. I don't see it as greatly increasing the workload here as the articles will already have been vetted to some extent.--] (]) 21:08, 17 July 2011 (UTC)
# '''Support''' per ]. Regards, ] <sup>(])</sup> 21:58, 17 July 2011 (UTC)
# '''Strong Support''' Sounds like a great idea, I think it will probably lead to increased interest in improving articles. Perhaps we should give the top slot with a picture to a GA. ] (]) 22:10, 17 July 2011 (UTC)
#: I would expect to see the ''opposite'' result. On Wiktionary, we feature a "Word of the Day", and this is ''never'' a fully-polished entry. When the word goes up, we get lots of activity adding trandslations and quotations, and other sorts of improvements. When an article is already at GA, I expect there to be ''less'' involvement in improvement, since there will be less opportunity for a general reader to participate if the article has alreay gone through a review process. Putting the GA first is also a bad idea, as it overemphasizes that article, limits the GA choice to a suitably-illustrated one, and prevents the new articles from having their photos featured. --] (]) 22:31, 17 July 2011 (UTC)
#::My comment about "increased interest in improving articles" was in regards to people being more interested in bringing articles to GA if they knew they could get main page territory. I don't see why we shouldn't give the slot that gets the most hits to the best written article. I also don't see the problem with drawing illustrations from GAs, from a reader's perspective at least. (Of course people writing new DYK articles with good pictures or GAs without good illustrations wouldn't like it, but you can't please everybody.) ] (]) 23:21, 17 July 2011 (UTC)
#If DYK were limited to new articles, this would be radical. But it isn't - it already includes articles that have substantially improved in quantity (5x expansion) - so on what basis are we excluding articles that have substantially improved in quality as measured by peer review (Good Articles)? Frankly, a lot of the opposition to this would seem ]ery if exhibited on an article. ] <sup>]</sup> 21:14, 19 July 2011 (UTC)
#I think it's good to give GAs some exposure; a trial won't hurt. ] 12:16, 20 July 2011 (UTC)
# It would be good to gives articles a chance to be featured if someone revamps a fairly large article (impossible to make eligible under DYK rules) and gets it to GA status. The only caveat is making sure the article is thoroughly examined because of the potential for substandard GAs. –&nbsp;'''] «]»''' 12:26, 20 July 2011 (UTC)
#'''Support''' DYK is a good idea, but ''not'' for new articles. I'd much prefer GAs to be put in their place. At the moment, we award an article GA status, but nothing comes of it. This would be the ideal place to feature articles that are good but not as good as featured ones. We have long since passed the time of needing an incentive to create new articles. ] 11:03, 21 July 2011 (UTC)
#'''Support''' I've thought this for a long time now.♦ ] 17:35, 22 July 2011 (UTC)
#I'm not so sure about the idea, but we rather ought to run a trial and I don't see any harm in that. &mdash;] 19:33, 22 July 2011 (UTC)
#'''Support''', DYK isn't working at all, and there is no longer a need to encourage new article creation on Misplaced Pages; there is a much greater need to encourage article improvements to Misplaced Pages standards than there is to put up new content that does not often meet standards and requires cleanup by experienced editors, of which we no longer have enough. Replace DYK entirely with daily GAs, perhaps two can fill the space currently occupied by DYK, and they need not be recent-- they need to be vetted by a directorate, which DYK does not have (I suggest GA-experienced editors, so the DYK crowd doesn't just move over to GA to put up inferior content on the mainpage under a different name). ] (]) 22:31, 22 July 2011 (UTC)
#'''Support'''. One GA hook per set. This is a modest proposal which would help to put more quality content on the front page, while still allowing traditional DYK hooks to appear there as well. No plausible arguments have been presented as to why it could possibly be a bad thing. This is not an attempt to destroy DYK, it is not the thin end of the wedge of some conspiracy against DYK, it is just a minor and much-needed improvement. --] (]) 22:50, 22 July 2011 (UTC)

===Oppose===
# The way GA has been running lately, there is little difference between GA and FA for many reviewers. Articles up for GA are often pushed to FA standards, so those articles should soon have a chance for the Main Page anyway. I also prefer a uniform set of criteria, not a this-or-that blend in DYK. It makes the entire process much easier to manage. --] (]) 02:33, 17 July 2011 (UTC)
#: Please consider that in the last ten years there were 3,335 FAs produced while 12,336 GAs which means there are four times more GAs than FAs. Most FAs have been promoted without being GAs before. Those editors who wish to bring the article from GA further to FA most likely will not bother to nominate for DYK. So doubling wouldn't be frequent, probably not more than between DYKs and FAs anyway. Your other argument is about the difficulty to manage an extra rule. Well, why not be friendly towards those who think that this is a good idea and allow for a ''trial''. Than the results could be evaluated and your concerns proven to be justified. --] (]) 02:56, 17 July 2011 (UTC)
#:: Your argument supports my point, in that if so many articles are making FA without ever going through GA, then the function of those two processes has become largely the same. We don't need to double-dip the highly improved articles. Featuring the new articles will do much more to encourage newbies that will featuring GAs. --] (]) 22:22, 17 July 2011 (UTC)
# In just the past couple of weeks I have seen proposals from Tony1 to reduce the number of DYKs per day to 8 and to replace an unspecified fraction of DYK with a large image promoting one article. SandyGeorgia now proposes getting rid of DYK entirely, to make more room for more featured content. DYK is a wonderful feature of the Main Page and it is there to promote creation of new content. There are many other wonderful goals in the world, but it would be better to do a very good job on DYK's own good goals than to start pursuing radically different good goals. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 03:46, 17 July 2011 (UTC)
#: I thought DYK and GA have the same goal, which is to improve Misplaced Pages. This is a proposal to ''trial'' a possible ''improvement'' of DYK. If this minor proposal cannot be tested, I'm afraid the number of those calling for truly radical change will increase. --] (]) 06:08, 17 July 2011 (UTC)
#::The goal of DYK is giving "publicity to newly created or expanded Misplaced Pages articles. This serves as a way to thank editors who create new content, encourages editors to contribute to and improve articles and the encyclopedia, and brings new and expanded articles to the attention of readers who view the Main Page." That is the way we "improve Misplaced Pages" here. Of course the goal of every feature on the Main Page is to improve Misplaced Pages," but reviewing and selecting GAs for exposure is much closer to the mission and expertise of the FA section than to DYK's. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 11:54, 17 July 2011 (UTC)
#::: I'm afraid you're misguided, GA is not about reviewing and selecting, it is about qualitative improvement. I don't think the concept of having a DYK which stands only for quantity is tenable. --] (]) 14:07, 17 July 2011 (UTC)
#:::: DYK is about reviewing and selecting new content of quality. But I don't want to ] this discussion, and perhaps you don't either? <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 14:24, 17 July 2011 (UTC)
#If there is a ''need'' to feature recently promoted GAs on the main page, why not propose just that as its '''own section'''? DYK's purpose is to feature new content, encouraging both new editors and frequent content creators. Diverting 25-33% of the slots to freshly-minted GAs would divert DYK from its mission, create a slippery slope towards the ''de facto'' destruction of DYK as the same tiny group of editors propose these changes over and over until something sticks, and only add to the workload of DYK reviewers with no benefit to DTK's mission. - ] (]) 10:19, 17 July 2011 (UTC)
#: There are about more new articles than GAs. That's 1% not 25-33%. No reason to be scared. --] (]) 14:07, 17 July 2011 (UTC)
#For the same reasons I have given in all the previous repetitions of this ] (e.g. ], ], ]). GA status means nothing to our readers, most of them don't even know what a GA is; this proposal has always seemed to me to be more about editors wanting to scratch their own backs then about improving the experience for readers. Is there anything new in this proposal that hasn't already been gone over in the numerous previous discussions? <b class="IPA">]</b>&nbsp;(]) 11:41, 17 July 2011 (UTC)
#:Why do you think that including Good Articles would not improve the experience for readers? Considering how abysmal some of our DYK articles are, I think we could only stand to improve from this change. ] (]) 19:38, 17 July 2011 (UTC)
#::This is already discussed at length in the numerous links I posted above; please take the time to read them. And, as Sharktopus pointed out above, take care not to ]. There is no need for you guys to respond to every single opposing comment; your opinions are already known. <b class="IPA">]</b>&nbsp;(]) 02:50, 18 July 2011 (UTC)
#I agree with Dravecky that this would be better done in a separate section (and I'd support it there), as mixing these two in one section would confuse and dilute the important mission of DYK in encouraging new content creation. -- ] (]) 14:19, 17 July 2011 (UTC)
#:Isn't writing good articles part of new content creation? More importantly, isn't it about adding high quality new content, which is the one thing that Misplaced Pages really needs to support more of? Last time I checked, we weren't suffering from a lack of articles. ] (]) 19:43, 17 July 2011 (UTC)
#::First, what's with the badgering of each oppose vote here? Second, I think you're missing the point a bit. I agree that encouraging the refinement of articles is important, which is why I'd be fine with a section of the front page that recognizes GAs as we do FAs. But I also think that quality first-stage content creation is ''equally'' important to recognize.<br>Because the truth is, Misplaced Pages '''is''' suffering from a lack of articles, at least on ]. Check out the DYK section of my ], if you like; all of those appeared on DYK since May of this year, and I'd estimate that 49-50 of the 53 were wholly new. You can argue that ] (Egypt's most famous playwright), ] (a well-known Burmese hiphop artist, now a political prisoner), ] (an internationally-recognized Thai journalist who heads the country's largest TV network), or ] (leader of the monks in Burma's 2007 "Saffron Revolution") don't belong in Misplaced Pages, I guess, and that we should stop encouraging people to create articles like those. But IMHO, you'd be wrong; to keep the encyclopedia growing, we need to continue to expand our coverage in both breadth (quantity) ''and'' depth (quality), and our awards and front page should reflect that. I get a bit tired of those interested only in the latter dropping by to deride even the ''idea'' of working on the former. -- ] (]) 04:02, 18 July 2011 (UTC)
#:::First, it is not badgering, is a good faith attempt for dialogue. Second, the proposal is not to stop encouraging new articles or expanding articles. It is about a sensible shift after ten years of creating new content towards encouraging quality improvement. There are still 100 times more new articles created than GAs and there are 1,813,206 stubs waiting for expansion. --] (]) 07:17, 23 July 2011 (UTC)
#Per the other opposes, in particular rʨanaɢ and Khazar. This suggestion is step towards disbanding DYK as it is today - by reducing the newness and the variety. ] (]) 13:43, 18 July 2011 (UTC)
#Per the other opposes, for a broad international and cultural representation, --] (]) 15:42, 18 July 2011 (UTC)
# For many of the reasons above. DYK encourages new content, and that remains an important element in the continuing development of Misplaced Pages. Placing featured articles on the main page promotes those who work to elevate articles to top quality level. Both elements are important. Already, FA is more prominently featured than DYK, but the current balance is appropriate in my mind. By watering down DYK with inclusion of GAs, it shifts the focus further toward the top quality element at the further expense of new content. ] (]) 21:13, 18 July 2011 (UTC)
# Per Rjanag and Khazar. ] (]) 14:34, 19 July 2011 (UTC)
#I agree with just about all of the ''oppose'' reasons given above. ]&nbsp;<font color="blue">•</font>&nbsp;] 18:06, 19 July 2011 (UTC)
#The point of DYK is to foster new content and feature users' work on the main page, if only for a moment. I think it works fabulously as an incentive to create new articles, and I have to oppose any proposal to modify it with GA material. ] (]) 20:03, 19 July 2011 (UTC)
#DYK should encourage new content. Personally, I would like to see new GA's replace the stagnant "On this day".--] (]) 22:57, 22 July 2011 (UTC)

===Discussion===
* I think if GAs are going on the front page, they should be highlighted ''as'' good articles. That is, I don't want them mixed in the same box with new articles. I think a better idea would be to highlight GAs some days and new articles other days (like every other day), or have a separate box for GAs entirely. —] (]) 03:43, 17 July 2011 (UTC)
*: DYKs ''are'' a mix of new articles and old articles improved through quantitative expansion (5x). Adding qualitatively improved articles does not really change the current new-old mix. The difference between new, 5x-expanded and GA articles might be important for editors, but readers just want to see quality content. --] (]) 04:13, 17 July 2011 (UTC)
*::The 5x expanded articles are at least 80%-new prose and usually more than that so they genuinely are 'new' content. I do support the idea of a separate box for newly promoted GAs, perhaps in a screen-wide box under the featured picture. - ] (]) 10:25, 17 July 2011 (UTC)
*:::I don't think GA has the strength to support a section on its own on the main page. I think the proposal would benefit ''both'' GA and DYK. --] (]) 06:53, 23 July 2011 (UTC)
*::* Some folks (like me) are in favor of eliminating the "featured picture", as this is something Commons already does. I would think it could be replaced with a GA section. --] (]) 23:28, 20 July 2011 (UTC)
*:::FPs often get more views than DYKs, so there is clearly interest for them. Also the ] shows that editors appreciate FPs and rather consider the main page should have ], not less images. --] (]) 06:53, 23 July 2011 (UTC)
*::If people cared about providing readers with quality content, then they would be arguing for the inclusion of new FAs, which are of higher quality than GAs. Ever since this was first proposed nearly 3 years ago (and there may be earlier proposals I'm not aware of), people have been wanting this as a way to reward editors who write GAs, ''not'' as a way to improve the experience for readers. <b class="IPA">]</b>&nbsp;(]) 12:15, 17 July 2011 (UTC)

*I argued with Tony1 about this over beers on Friday night. I am thinking we do this ''instead'' of reducing, and was thinking of 1 (or 2) initially so the reduction would be minor only and we could see how it goes and how folks enjoyed it. I also think that as many GAs are only reviewed by one reviewer, it might be a good way of a fair number of them just getting a second pair of eyes on them before (hopefully) going to FAC. ] (] '''·''' ]) 07:06, 17 July 2011 (UTC)
** How about suggesting to Tony1 next time you get together for beers that your joint project be hosted by FA for a month instead of by DYK? They have more pixels than DYK, the mission and editor expertise there are more similar, plus this would give FA an inside track to overseeing GA. Furthermore, since writing the actual FA blurb seems to be a last-minute job with little oversight, it might be good to make FA blurbs shorter. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 20:40, 20 July 2011 (UTC)
*Should we set a designated 'end' date to possibly blunt some of the opposers' wariness? ]&nbsp;<sup>]] ]]</sup> 07:21, 17 July 2011 (UTC)
**It's part of the proposal, it says clearly that is for ''one month''. --] (]) 14:07, 17 July 2011 (UTC)
*** But the proposal says nothing about how we will gauge the success/failure of all this. Is the proposal simply saying that we'll do it for a month, and then go through the same set of arguments again, or is there some objective way we can gauge whether all this wrangling has resulted in something positive? --] (]) 23:30, 20 July 2011 (UTC)
**** Surely being a bit more ] could help... I would have thought. --] (]) 13:47, 21 July 2011 (UTC)
***** Every empirical scientist first establishes a ''plan'' for the experiment, so that he or she will be prepared to watch for and interpret the data, and will have set up the equipment necessary to collect the data generated by the experiment. Will the data be temperture changes, and thus reuire a thermometer, or will the data be in the form of spectrum absorbancy, in which case a spectrophotometer is needed. Not being prepared means that data will likely be missed, and almost certainly misinterpreted. Setting out raw meat which then produced maggots spontaneously was long thought to support the concept of ], principally because the empirical approach was uncontrolled and so the results were grossly misinterpreted. The proposal has no plan for interpreting data, nor even a statement about what kind of data we expect to get. Good experimental design is a fundamental part of collecteing and interpreting any data. --] (]) 21:19, 21 July 2011 (UTC)
****** Oh wow, really confusing. What have natural sciences in common with this? Are you really expecting a comprehensive social research to be set up before any modest change is tested for DYK? --] (]) 06:35, 23 July 2011 (UTC)

I think some people are missing the point here: some opposers state that DYK is for new/expanded articles, and they seem to be unable to budge on this opinion. The fact is, DYK can be for ''anything'', if there is agreement to change it. We don't have to stick with new articles just because it's always been that way. As I noted in my support we are long past the time where we need an incentive to create new articles. Why should new articles get exposure on the main page, over someone who slaved away making a good article who will get no such time? ] 11:10, 21 July 2011 (UTC)
:In part because we are ''not'' long past the time where we need an incentive to create new articles. There are many, many thousands of topics not yet covered on Misplaced Pages, or that are covered only as a short stub in need of vast expansion. Thus, an incentive to find and start/expand articles on those topics should not be eliminated. Also, featuring new artiicles on the Main Page will draw attention to what may be articles in their infancy, and infants need more help and care than the adult articles that already have their diploma. Opposers are not ''missing'' the point; we're disagreeing with the premise behind it. --] (]) 21:12, 21 July 2011 (UTC)
::But the proposal does not replace any of these. It is a modest shift. I fully agree that there is huge scope to expand stubs (55% of articles are stubs!), but the need to provide incentive for new articles has massively decreased, and is time to provide a bit more incentive for quality improvement. I can't see any ] missing. --] (]) 06:35, 23 July 2011 (UTC)
:::I remember the beer with Cas, and putting the point that the focus should move from ''quantity'' (achieving a set number of DYKs per day come what may), to ''quality'' (properly reviewing each nom and exposing it only if it meets the policies and quality benchmarks); in other words, the main-page exposure time for DYKs should be a movable valve to match the number of DYKs that have passed review at any particular time, and no more stress-outs for the queuing admins. I'm not sure Cas agreed entirely with my view.<p>On another matter he contended—that GAs are themselves newly expanded and/or newly improved articles—I was skeptical, but went away thinking about it and was won over. To have even ''one'' GA as a DYK each day seems like a win–win, for these reasons:<p>(1) DYK is the natural start-point for the trajectory towards GA, both in terms of individual articles and as a training ground for editors;<p>(2) DYK articles via the existing rules would benefit by association with one GA per day on the main page;<p>(3) DYK, let's be frank, loses reviewers at least as fast as it gains them, and can't nearly manage the flow—a good way of dealing with this would be to get DYK and GA to work ''with'' each other, not against each other;<p>(4) GA really really needs more official recognition: it is second to FAC as a model for article quality, and creating a five-day window for one newly promoted GA per day to be DYKed would lift GA's presence in the project and motivate more editors to participate at both forums; and (5) ] is moribund, isn't it? We need to coordinate and strengthen the fabric of article improvement, not maintain such separate islands. ] ] 07:10, 23 July 2011 (UTC)

=== Somewhat separate but not really thought ===
Regardless of the vote above, I think the wording on the Main Page should be changed to some form of "newest and newly-improved articles", as 5x expansions are never "new" articles. Am I alone in thinking this? ]&nbsp;<sup>]] ]]</sup> 07:21, 17 July 2011 (UTC)
:It says "From Misplaced Pages's newest content:", which is not the same as "new articles". The content is new, in the form of at least 4/5 new prose. —] (] · ]) 07:31, 17 July 2011 (UTC)
::What Adabow said. Furthermore, adding "newly-improved" is not a good idea, as it opens the door to precisely the kind of nominations DYK has been rejecting for years (e.g., articles that have been copyedited or otherwise improved without any substantial expansion). <b class="IPA">]</b>&nbsp;(]) 12:17, 17 July 2011 (UTC)
:::If the proposal above is successful, I think we should just axe the text completely. Readers don't care if the articles are new or not, they just want to read interesting, well-written articles. ] (]) 00:52, 18 July 2011 (UTC)
::::How do you know what readers want?
::::If ''all'' readers want is to read well-written content, then why not just have four TFAs? DYK is meant to serve a different purpose than what you are insisting on (as are ITN and OTD, which also are not necessarily showing interesting or well-written articles). <b class="IPA">]</b>&nbsp;(]) 02:53, 18 July 2011 (UTC)

To Rjanag I will outline my idea of how the article treadmill has worked at[REDACTED] - essentially getting a bite of the mainpage cherry has been great at pushing editors that little bit, from stub or nonexistent article to DYK, and then finally at the last hurdle, FAC. Over the past few years, FAC has become more and more exacting. I personally don't see this as a bad thing but as a natural development as[REDACTED] looks more and more like a professional encyclopedia. In this production line, GA has become more and more important as a waypoint for review on the road to FA status. I was thinking that as GA status can be achieved with only one reviewer, that sending a few through DYK might be a good carrots-rather-than-sticks approach at getting more eyes on them and giving them more of a shove to FAC. I have always been happy having good content which has some incompleteness accessible from the mainpage so that the reader sees WP as a work in progress. Anyway, help in bridging the step between GA and FA is what I see as more of a development in the past 18-24 months as opposed to previously. ] (] '''·''' ]) 03:20, 18 July 2011 (UTC)

===Related RfC which has been announced to people at FA but not here at DYK===
People including many commenting here are !Voting on . The RfC asks what features of the Main Page should be eliminated, including DYK. It seems to me a bit off to be !voting here to change DYK and !voting there to eliminate DYK entirely. I also notice that when the RfC listed the goals of the Main Page, somehow the goal of DYK, to motivate creation of new content, was left out, but I just put that in there. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 19:17, 19 July 2011 (UTC)
:Realistically, I was thinking it'd be a couple of months before anything really happened to the mainpage. That is one RfC that really needs to run its course, have results analysed and figure out where to go from there, which I suspect would be more proposals. I figured this would be a trial to try in the meantime. My initial idea (when arguing with Tony) was that cycling 4 queues a day containing average 5.5 DYK and 1 GA meant 22 DYK and 4 GA cycling through vs 3 x 6.5 DYK which leaves us 19.5 DYK hooks going through. This is based on an off-the-cuff calculation of between 6 and 7 hooks per set. I thought this'd be a net gain for everybody.] (] '''·''' ]) 20:25, 20 July 2011 (UTC)
::I should bloody well hope the Wikimedia Foundation has more sense than to let its front page be redesigned by a random walk through !voters with COI. Of course the FA people think we should have more featured content, and of course getting rid of DYK, ITN, and OTD would create more room for featured content. Of course I like DYK because I like creating new content and I often notice that Misplaced Pages needs something it doesn't have. If you offered me twice as many "ribbons" for critiquing other people's metric conversions, I'd drown in boredom. That's my COI. Of course new articles do not have the same smooth proof-read-ness of articles that have been vetted for months, but I follow Main Page/Errors, and we rarely have more errors picked up in 3 or 4 runs of 7 hooks each per day than FA has in their one blurb per day. People don't come to Misplaced Pages because they want to read polished prose about arbitrary topics, they come here because they are curious and lively and hope to learn something. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 21:00, 20 July 2011 (UTC)
:::I don't think the voting in and of itself there is going to dictate the changes. There has been talk on wikimedia pages before so some foundation input might take place as well. Hence why I think it'll be a few months yet. ] (] '''·''' ]) 21:22, 20 July 2011 (UTC)

::The other "!voters with COI" have no more conflict of interest that you do, with your support for putting DYK above FA. The community needs comments from everyone, because the whole page belongs to all of us, not just to DYKers—or FA folks, or ITN stringers, or any other group you care to name. You should feel free to share whatever opinions you have about the Main Page, even if it's not about "your" area.
::This is the first unified discussion, and it is basically a brainstorming session. The majority of ideas will be rejected. Those (if any) that seem to have some significant support will be discussed separately, and probably for months on end, before any actual decisions are made. I would realistically not expect to see any changes as a result of this discussion until 2012. ] (]) 22:18, 20 July 2011 (UTC)

== Disagreement that I would like others to look at ==

One of our waiting-a-while hooks connects 4 articles -- a nonfiction book and three people who were the subject of the book. To my regret, I think the articles overlap so much that a reader clicking through from this hook on the main page would not discover 4 articles "worth" of new content. The creator disagrees. Could others check out the issues described in this thread? Thanks for taking a look. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 03:11, 17 July 2011 (UTC)

:Needs new text, not re-use of text that's already in other articles. That's already in the DYK rules. Simple as that. Re-use of text is not eligible. --] (]) 03:29, 17 July 2011 (UTC)
::I a citation for your "simple as that" claim already. You didn't provide it there, do you care to do so here? The four articles were created in main space more or less simultaneously; it seems obvious that since the four are connected there would be re-used text...simple as that, to borrow a phrase. If the rules really state that "re-use of text is not eligible", I'll withdraw the nomination. I've gone back (again) and read both ] and ], and I just don't see it. The fact that these four articles were added simultaneously precludes use of ], since none of these articles is being nominated on the basis of expansion but rather as newly-created articles. Invoke ], call ], or something else...but without a citation for "not eligible", you'll have to send this to ] without my approval. <small><span style="padding:2px;border:1px solid #000000">]&nbsp;&#124;&nbsp;]</span></small> 03:51, 17 July 2011 (UTC)
:::General reply. Reuse of ''one's own new content'' is well allowed, unless it is misused (willingly or not) for reaching the 1500 char (or 5x expansion) limit in the individual articles, or is simply unreasonable. Whether or not this is the case depends on a personal view on what information should be in what article. My personal view is that the current overlap is such that Zoya Fyodorova, Victoria Fyodorova and The Admiral's Daughter articles could well be merged into one article. They could also stand on their own, provided they are expanded individually and the overlap is reduced. ] (]) 04:56, 17 July 2011 (UTC)
::::Practically speaking this seems to be just a disagreement over semantics. There is at least one DYK article in there, right? So pick one article, feature it, with that particular article's title bolded, de-emphasize the rest in the hook (though of course retain the wlinks) and we're good to go. The only way I can see this mattering is if somebody's bean-counting their DYKs and wants to have "credit" (whatever that really is) for 4 DYKs rather than 1. But I'm not sure that should really be a consideration.] (]) 05:51, 17 July 2011 (UTC)
::::::Thanks everybody for very helpful replies, and to Volunteer Marek for a practical suggestion on resolving the disagreement. I have suggested a couple of alt hooks that would point to two out of these four articles. I feel that having a DYK hook pointing from our Main Page to 4 articles that all tell essentially the same story is not appropriate. If somebody else could review the nomination so we can move it up to Prep, that would be good. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 14:01, 17 July 2011 (UTC)

== ] ==

I would like to complain how ] reviewed the article ]. I have withdrawn it because he distrusts a Wikipedian like me. Misplaced Pages belongs to everyone. What he did is against the Misplaced Pages way of openness and collaboration. He must be removed as an administrator because of this. - ] (]) 01:05, 20 July 2011 (UTC)
:He won't be. The diff is . The nom dates back to July 4, so it's a pity the issues weren't addressed earlier. Including the name of the main character in a plagiarism comparison is a bit, er, harsh, but otherwise his removal seems reasonable. ] (]) 01:20, 20 July 2011 (UTC)
::Is it a striking feature of the plot or public perception of the novel, that the main character ''worships Hindu gods at an altar in the United Nations building''? If so, how else would one word a quick summary of that fact? --] (]) 01:33, 20 July 2011 (UTC)

:AnakngAraw, having articles featured on DYK is a privilege, not a right, and the project doesn't need people calling for desysopping/banning every DYK editor who doesn't agree with them. If you can't work with DYK reviewers civilly, then maybe your privilege of nominating DYK articles should be removed. <b class="IPA">]</b>&nbsp;(]) 01:55, 21 July 2011 (UTC)
::I wasn't aware that there was a "privilege of nominating DYK articles" that could be removed, other than by a block etc. Where does this strange idea come from? ] (]) 02:12, 21 July 2011 (UTC)
:::People can be ] from any project. Likewise, DYK reviewers can simply refuse to review anything edited by that editor. If someone is going to make threats against every DYK editor who criticizes their nomination, that person clearly is not ready to be a constructive member of the project, and the people who volunteer their time to run DYK shouldn't have to worry about getting this kind of crap for their reviews. <b class="IPA">]</b>&nbsp;(]) 12:31, 21 July 2011 (UTC)
::::That doesn't amount to what you said. Frankly here your language here is inappropriate. ] (]) 12:56, 21 July 2011 (UTC)
:::::Topic banning is removing an editing privilege. How is that different? AnakngAraw's complaint above was the only inappropriate thing in this thread and I will not apologize for calling it inappropriate. Do you have something to contribute to this discussion (which seems to be stale anyway, as the OP hasn't commented in days), or are you just looking for a fight? <b class="IPA">]</b>&nbsp;(]) 23:28, 21 July 2011 (UTC)
::::::Misplaced Pages is "the encyclopedia anyone can edit" (until blocked or banned). Talking about "privileges" is bullshit and fundamentally wrong, re DYK or any other normal editing function. I've made my point. ] (]) 23:52, 21 July 2011 (UTC)
:::::::So you don't disagree with the point I was making in any way, you just felt like going off on a tangent to complain about my word choice. I'm glad that is cleared up. <b class="IPA">]</b>&nbsp;(]) 14:05, 22 July 2011 (UTC)
:::::::(And by the way, longstanding consensus is that ]. <b class="IPA">]</b>&nbsp;(]) 14:49, 22 July 2011 (UTC))

== Do quotes count as main prose for fivefold expansion? ==

Hi all. I've been working on expanding ]. It's gone from to in total... My question is: given that the article constituted of a full third of quotes beforehand, is that counted when ascertaining the prose length to determine fivefold expansion? Also, is there an easy way to see the prose-only byte count? Thanks =) ''']]]''' 18:58, 20 July 2011 (UTC)
:Bytes are not what you count, see the rules, but re quotes this is a good borderline example. I would say that quotes that ''ought'' to have been taken out of running prose per MOS principles should be excluded from before & after counts, but that leaves a fair amount of room for personal taste. I noticed recently that the rules re expansions do not specifically mention quotes. Full declaration: when I did the nom for ] (July 18) my "before" count excluded a huge 868 char quote that was then in running prose but in the "after" version was separated as a quote, as it clearly should be. I think this was right - at that point it made a difference to the 5x but now it doesn't as the article has grown. It would be silly to include it before and exclude it after. ] (]) 22:57, 20 July 2011 (UTC)
::Expansion is counted based on the size of the previous article, no matter what shape it was in; this is stated clearly in the rules. A character of prose in the pre-existing version is counted as a character of prose, even if it happens to be in quotes. So your article is not 5x expanded.
::If an article was already 10,000+ characters before you started expanding it, you should consider ] rather than ]. <b class="IPA">]</b>&nbsp;(]) 01:57, 21 July 2011 (UTC)
:::No ''bytes'' dude. The previous version contained little prose, but lists, refs, templates etc etc. ] (]) 02:10, 21 July 2011 (UTC)
::As for your second question, you can calculate prose size using ], ], or ]. <b class="IPA">]</b>&nbsp;(]) 01:59, 21 July 2011 (UTC)

* is 2854 characters, is 7568. Less than 3x expansion. <b class="IPA">]</b>&nbsp;(]) 02:13, 21 July 2011 (UTC)
:Indeed you are correct - though given that block-quotes are discounted by the script and the former has 2 massive inline quotes, should only be 1982 chars and as such the goal is far more attainable! Either way, thanks for all your help =) ''']]]''' 07:44, 21 July 2011 (UTC)

== Daily DYK scandal ==

There's always one, whether faulty sources, plagiarism, or sensationalism, but y'all have exceeded even your own low standards with:
{{dyktalk|21 July|2011|entry=... that ] ''']''' obtained passage of an amendment in 2009 that allowed him to rebuild his own beachfront property damaged by ]?}}
reporting one negative fact based on one source which places the subject of a BLP in a negative light. Have you all no shame, or simply no processes for assuring you don't trash the main page? All one has to do is take a daily glance at DYK to realize it's gotten worse and worse. By the way, who verified the hook this time, because the source says he "may" be able to, not that he did. ] (]) 02:41, 21 July 2011 (UTC)
:For reference: this hook was moved to the prep area {{diff2|440135616|here}}. ] 02:47, 21 July 2011 (UTC)
:: Thanks, Ucucha: am I reading that correctly? It appears to me that TK verified the *first* hook, and yet DYK *ran* the second (alternate) hook. If correct, amazing. How did that happen? Get it off the main page, folks-- it's a debacle. ] (]) 02:52, 21 July 2011 (UTC)
::: by Dom. --] (]) 03:00, 21 July 2011 (UTC)
::::Yup, Dominic got to it before me (or MZM, apparently!). Nice catch Sandy. ]&nbsp;<sup>]] ]]</sup> 03:02, 21 July 2011 (UTC)
:::: (But you both got here in time to edit conflict me!) Yes, I removed it. I intended to replace it with the other hook, but it seems that it wasn't chosen because there was an issue with self-published sources being used. I'd rather leave it for more experienced DYKers to decide what to replace the spot with, whether it's another one from that article or something new. ]·] 03:03, 21 July 2011 (UTC)

::::: Thanks, all, but can y'all go back and figure out how that happened? Am I correct that the first hook was the one verified by TK, yet for some reason the second hook was chosen even though it wasn't checked? Y'all have got to find a way to plug these holes. ] (]) 03:05, 21 July 2011 (UTC)

::::::No, TK didn't specify which hook he verified; so in effect, he verified both. --] (]) 03:15, 21 July 2011 (UTC)
::::::::As far as I remember there was a hook about a water board. How can you see from that there were two hooks there? Once these are processed they're gone. At any rate, if there was an alt hook, which looking back at the page, I see there was, I wouldn't have expected it to run unless I suggested it, which I didn't. In my mind alt = something wrong with first, and I never commented on the hook, I was focusing on the content. But at any rate, am prepared to admit I screwed up here. ] (]) 04:18, 21 July 2011 (UTC)
::::::: From reading the discussion, it does not appear that TK was looking at the alt hook, and no where in this mess of a process can I understand WHY Crisco chose to run the second hook. Another user (OCNative) ce'd it in the prep area 1, and then moved it to queue. None of those people saw the problem? There is a systemic breakdown here. You've got one person proposing a hook, another reviewing, another moving to prep (Crisco somebody), another copyediting the hook (OCNative), another moving to queue (Materialscientist), and no one saw the problem, or noticed that apparently TK verified the first hook, not the alt? How is Crisco empowered to choose the alt, based on that discussion? Are you all simply pushing through too much volume to pick up things like this? ] (]) 03:20, 21 July 2011 (UTC)

::::::::No, TK's first review of the DYK submission , at which point there were already two hooks there; he put his comments (which discussed various aspects of the article, not just hooks) underneath the second hook. There was nothing to suggest he wasn't looking at the second hook. --] (]) 03:25, 21 July 2011 (UTC)
::::::::::*Absolutely correct. TK did not specify which he checked, or which he agreed with, so I chose the hookiest hook. ] (]) 00:46, 22 July 2011 (UTC)
:::::::::::* DYK can be as obtuse as you all want for as long as you want, but it doesn't take any amount of effort to read the discussion there and realize that TK (a new reviewer) did not verify the alt hook. But, at least Crisco has now told us why he chose the alt hook in spite of that-- he prefers the sensationalist hooks, which is another big problem driving the DYK daily scandal. One editor can put a debacle on the main page, that three other editors up the DYK line don't catch. No accountability, no transparency, no archives, no institutional memory, no decency wrt human beings. And you're still putting BLP vios from the same editor who wrote this one on the main page. Tsk, tsk. ] (]) 16:36, 22 July 2011 (UTC)
:::::::::::::*I said hooky / ], not ]. Please do not twist my words around. Naturally, if one hook reads "... that ''']''' was born in ]?" and the other reads "... that President of the United States ''']''' has won two Emmys?", the Emmy hook is hookier. As for the reviewing process, please feel ]. ] (]) 00:46, 23 July 2011 (UTC)
::::::::::::::Or, for an example of a somewhat negative hook, "... that President of the United States ''']''' smoked ] as a teenager?" Still hookier than "was born in Hawaii" ] (]) 02:35, 23 July 2011 (UTC)
*Perhaps there was an error in the review here, which is certainly worth checking, but I believe the DYK hook used is well-verified and the subject of many news reports in Texas. Its not even that shocking really. Too many DYK hooks are totally boring bollocks, at least this allows readers to check into the controversy and understand it.--''']''' • <small><sup style="position:relative">]<span style="position:relative;bottom:-2.0ex;left:-3.2ex;*left:-5.5ex;">]</span></sup></small> 03:26, 21 July 2011 (UTC)
::Agreed - in fact, the first hook here was indeed extremely dull (and yes, maybe even close to "boring bollocks"), which may be what encouraged choice of the second hook. --] (]) 03:29, 21 July 2011 (UTC)
::: Would it be possible to have one, just once in a while, just one discussion about the obvious problems at DYK that focuses on solutions? A BIG part of the DYK problem is the desire for sensationalism which leads to junk like his being run on the mainpage. Choosing one negative sensational fact from a BLP, based (in the article) on one source isn't the way we should be doing things. Again, are you all trying to push through too much volume, with too many hands in the pot, no accountability, no archives, no means of checking, that things like this can too easily get through? Boring is better than the sensationalist crap that often makes it into DYK-- and that article for darn sure did not allow any readers to check into the controversy and understand it-- the entire controversy is reported from *one* source in the article. Please stop the drive for sensationalist hooks, and institute a process where there is some accountability for what goes on the main page, instead of too many cooks in the broth, no archives, complex processes, and no one in charge. ] (]) 03:38, 21 July 2011 (UTC)
:::There is almost never a good reason to put even true and cited negative facts about living people on the main page of Misplaced Pages, and certainly not recent controversies for local politicians still in office. Putting a negative claim about a living person on the main page, which gets millions of hits, without the context of the rest of the article gives an incredible amount of undue weight to that aspect of the biography. ]·] 03:41, 21 July 2011 (UTC)
::::The DYK rule is that hooks must not focus "'''unduly'''" on negative statements about a living person: "Articles and hooks that focus unduly on negative aspects of living individuals or promote one side of an ongoing dispute should be avoided." Let's get a grip on what actually happened here. Somebody approved a hook the described an amendment Christian verifiably supported, one that was verifiably limited to beach property in the exact area of his own beach property. There is nothing in BLP that says you can't mention a verifiable fact about somebody that others might perceive in a negative way. The bar is set higher for a DYK hook because it is short, and you can't typically balance something negative once it is mentioned. This was a mild infraction at DYK of one of DYK's own rules. It was not a "scandal." <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 03:48, 21 July 2011 (UTC)
::::SandyGeorgia, to answer just one of your questions, yes I think you all ''are'' trying to push through too much volume. There's a proposal above, at ] that would reduce that volume by a small amount - what should in my opinion be an uncontroversial amount. But it doesn't seem to get much support. Some more thoughtful input there would be useful. --] (]) 03:51, 21 July 2011 (UTC)

::::: The basic problem is the number of submissions we get, fiddling with the means of dealing with them will not alter the workload, because someone still has to vet every submission and make decisions about it. Tightening the criteria for DYK would be the only way to reduce submissions, but no-one seems to want to do that and there is no guarantee it would change anything, since many of the people who do most of the work now would probably just see it as a means of reducing their own workload.

::::: In any case, this is not such a big deal, DYK only has occasional slip-ups but they occur in every part of the project, and there seems to be some disagreement over whether this hook should have been pulled anyway. Debate is healthy, but let's not blow things out of proportion. ] (]) 04:24, 21 July 2011 (UTC)

::::::It ''is'' a big deal, and should be taken more seriously as it's a BLP. Yes people make mistakes, but then again, people should learn from them and not make them again and again. ] 11:05, 21 July 2011 (UTC)
:::::::What Aiken drum just said. This is not a minor glitch that should be swept under the carpet. A negative fact about a living person was put onto the most viewed page on the fourth largest website on the internet. There was no need for that and it should be taken seriously. ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 11:37, 21 July 2011 (UTC)

::::::: Except that there's a steady turnover of people so that mistakes are made by those less experienced. And while I agree that the hook probably breached our rules, it was on the main page for less than three hours. ] (]) 11:34, 21 July 2011 (UTC)::
::::::::So let's look at solutions that deal with these mistakes so they don't hit the main page? Don't just accept it as a problem. I see this as a very good reason to reduce the number hooks on the front page, so only the best get on (something I wasn't really for before). NB In 3 hours, the page is seen by ~600k people. Don't underestimate that power. ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 11:41, 21 July 2011 (UTC)
::::::::: As I just said, reducing the number of hooks will not reduce the number of submissions, so it won't reduce anyone's workload and won't make the end result more reliable. This kind of thing happens once in a blue moon, occasional mistakes are always going to occur, they occur even with FA from time to time, and they are not a reason for proposing radical changes. ] (]) 12:03, 21 July 2011 (UTC)
::::::::::Fair enough, TCO mentioned to me that he was after some data on DYK, I'll do my best to get that together before commenting further. I've done a fair amount of DYK work myself, I'd almost consider myself a reg and I've seen enough that I think that some sort of change is needed. ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 12:14, 21 July 2011 (UTC)

Catching up on multiple: Dominic has it ''just right'', and anyone who doesn't get that shouldn't be working on anything that goes on the mainpage. Gatoclass has a very valid point about the high turnover of people working here-- there's a new crowd of people in here about every three months, so the old mistakes keep repeating, even though MANY of us have been harping on the same things for years now. Perhaps good and experienced editors eventually leave this area because the turnover is too high, the workload is too high, the process is too complex, or they become embarrassed when they realize the poorly sourced sensationalism and plagiarism they often put on the mainpage? It is NOT an occassional mistake-- any time one chances to look at DYK (as I did yesterday), one can find something egregious-- whether plagiarism, copyvio, non-reliable sources, inaccurate representation of sources, and now gross BLP situations. You all need to figure out how to fix this-- editors are NOT entitled to have time on the mainpage, and the volume of turnover needs to be reduced. You also need, IMO, a directorate made up of experienced editors-- a place where the buck stops and someone is responsible when this happens. I think it's pisspoor to blame this on TK, even if she accepts responsibility, when it's quite clear from the discussion that she vetted the first hook, yet the second ran. Will someone PLEASE tell us what possessed that Crisco person to run the alternate hook? What is your process? Who is in charge? Nothing has changed even though many of us have been harping on this for years, and Gatoclass points out why (there's a new crowd in here every three months claiming there's no problem when the problems go back years, the Shark character is the latest DYK apologist in a long stream of same)-- you all know best how to fix it-- others from outside can't pretend to tell you how, but you do need to fix it. You need lower turnaround and accountability. ] (]) 13:13, 21 July 2011 (UTC)
:If I may, Sandy, I would suggest it's not helpful to use this as another stick with which to beat DYK over the head or to blame a specific editor. Everybody here has acted in good faith, but mistakes have been made—I think we all agree on that much. So instead of insulting DYK (regardless of whether it deserves to be insulted or not), why don't we have a collegial discussion about how (or even whether) DYK can be improved. Without that discussion, we'll all waste a lot of space discussing these issues every time they come up. ] &#124; ] 13:25, 21 July 2011 (UTC)
:: I thought that's what we were trying to do, and who is trying to blame any specific editor? Or better stated, who is trying to brush this under the rug? This cannot be blamed on TK-- it took multiple (systemic) process failures to cause this. Until some regular denialists here start looking at the process problems, and considering for how long this has been happening, it may be time to take up a stick rather than drop it. As soon as the regulars here start discussing much needed change, rather than resisting it, I'll be glad to unwatch for the gazillionth time after finding egregious DYK issues on the main page. And until DYK begins to seriously discuss how to change the problems, rather than deny them and claim they are occassional, it may be time to start assigning blame. ] (]) 13:35, 21 July 2011 (UTC)
:::Have started reading this whole discussion, starting from this section and working down to the recent RfC at the bottom, and I'm trying to concentrate on the issues at play here, but the tone of the discourse is varying wildly from person to person, so it is difficult to avoid getting distracted by comments like ''"that Crisco person"'' and ''"the Shark character"''. Can we use people's usernames rather than dismissive terms, as failing to follow the basic courtesy of using someone's username properly only distracts from the systemic issues you are trying to get people to see? I agree there ''are'' systemic issues, but it seems to me to be people having different standards and not agreeing on what is a reliable source, or having the time to explain to users how to write properly from sources and what needs rewriting or not. Just pointing something out is sometimes not enough. Sometimes you have to demonstrate by editing the article what should be done instead. ] (]) 09:52, 23 July 2011 (UTC)

===Break===
* One feature that all Main Page programs rely on is ], where people swiftly report problems to get swift correction. I encourage everyone to look at the history of that page to search for past "scandals", let alone daily scandals, at DYK. Errors occur in all the Main Page features. This page is commonly used to suggest changes in DYK process, many of which have been or are being implemented. This particular article was reviewed by a novice reviewer. I had proposed a while ago that some more experienced reviewers make a practice of reviewing Prep instead of reviewing individual articles; I would be happy to see ] reconsidered. Another recent proposal to help novice reviewers resulted in cmadler's very kindly posting a ] to help new reviewers. I just a more prominent link to that guide and a strong suggestion to new reviewers that they read it before proceeding. The rule about "unduly negative" BLP hooks is in there. It is regrettable that mistake was missed by the more experienced people who made up Prep and Queue, but I am betting they don't make that mistake again.<font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 12:04, 21 July 2011 (UTC)
:* I'd advise you not to put money on that-- every mistake made at DYK recurs quite regularly, and has for years, because there's a new crowd of editors in here every few months. ERRORS should be for errors-- not systemic, long-standing, well-documented, ongoing process failures. Please stop glossing this over and pushing it under the rug. ] (]) 13:16, 21 July 2011 (UTC)
:First of all, I apologize for this, and take full blame. Whoever said I was a novice reviewer is partially correct; I don't review often at DYK. This particular situation arose from where Demiurge1000 to review a DYK. Honestly I was only looking at the content and made two very serious mistakes. One is that I assumed the article creator would scrub all the problems after a spotcheck, and two I assumed the first hook would be used, as it seemed fine and no reason to go to the alt hook, about which I didn't comment. We all know what happens when a person assumes, and for that I'm completely culpable. Not much more to say, otherwise. Oh, except to thank Sandy for being on the ball, to thank whomever pulled the submission from the frontpage. ] (]) 12:28, 21 July 2011 (UTC)
:: No, you're not completely culpable-- it is QUITE clear from the discussion that you reviewed the first hook, yet for some reason, that Crisco editor chose the second hook. The problem here is too many queue turnovers and no one in charge-- after you reviewed the first hook, three different experienced DYK editors worked to put the alternate hook on the mainpage-- it took multiple cooks in the broth to cause this to happen, and therein lies the problem-- no accountability even as an obviously bad hook moves up the chain. Further, that this could have happened with an experienced editor (TK, who did NOT review the alternate hook, yet it ran anyway) only highlights the problem-- that is, DYK requires nominators to review regardless of their editing experience, so you get inexperienced reviewers, who are even MORE likely to make a mistake than an experienced editor like TK. Bad, bad process here. I hope you all will decide how to fix it, and stop relying on faulty RFCs-- you need to DO something. ] (]) 13:23, 21 July 2011 (UTC)
:::After so many edit conflicts (and a cuppa tea :D) - TK, you're a link in a chain. The nominator, the reviewer, the "prepper" and the admin who moved it to the queue all failed. ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 13:49, 21 July 2011 (UTC)

**Well I'm afraid it's not working—at least for DYK it's not. And as far as I'm concerned, Sandy is right: daily is no exaggeration. Do we need to start a public DYK bloopers page to convince people that the current system makes the safe, secure, functional reviewing of DYKs virtually impossible? Apart from the dangers to the main page, there can be no proper role of mentoring less experienced editors and inducting them into the process of improving articles from scratch. It's painfully obvious that the system needs to be reformed in several ways to ensure that DYK fulfills its own objectives and those of the whole project. The number of hooks per day needs to be reduced, and the system of nominator reviews needs to be a little more demanding than tick tick tick, count the characters. The time has come to drop the inflexible coloured ticks and crosses that assume lightening quick reviewing, and to create a proper checklist of the urgents that need to be OKed before exposure. ] ] 12:32, 21 July 2011 (UTC)

::: Sorry, but we're not GAN, and there's never been a requirement that DYK articles have to be perfect or anywhere near it. The basic idea of DYK is that it's a process that is accessible both to new users and to prospective users who might read one of our new articles and think "I could do that!" DYK articles are not ''supposed'' to be perfect.

::: As Sharktopus pointed out, there is a page here specifically designed to catch and rectify mainpage errors, which occur routinely in EVERY mainpage project. Why DYK gets singled out for this negative attention I don't know, but I suspect it's because some users just don't like the format and philosophy behind it. We've had many attempts to change the working of DYK in the past and they have all failed, most people like it the way it is. ] (]) 13:33, 21 July 2011 (UTC)

:::: No one is asking for perfect, but we don't need apologists for plagiarism, sensationalism, and BLP issues. It is NOT acceptable to put this level of debacle on the mainpage. As an experienced DYK editor, I hold you and other experienced DYKers responsible for fixing them, not denying it or apologizing for it. Your process stinks; fix it. DYK deserves this negative attention-- it is NOT an error, it is a sytemic process failure that has been going on for years. You're on old-timer here-- work on it, or take your lumps. ] (]) 13:38, 21 July 2011 (UTC)
:::::As someone who contributed to DYK in the past - but only extremely rarely now - it seems to me that the problems have worsened significantly since the decision was made to require self-nominators to also be reviewers. What that meant is that some nominators found an easy hook to skim-review, with little concern for the article's accuracy or for finding the best or most appropriate hook. So long as they could tick the "reviewed another article" box, their own hook was likely to be promoted. But there has never been any reason to assume that new article contributors would have any expertise or interest ''at all'' in reviewing other people's articles or hooks. The system worked better when reviews were in the hands of experienced and dedicated (albeit, I'm sure, overworked) reviewers who took the responsibility seriously. But, of course, it's also true that ''far, far'' too many articles are promoted through DYK. ] (]) 13:48, 21 July 2011 (UTC)

::::: (edit conflict) I'm afraid I've been largely inactive at DYK for quite some time. The main reason is that I got tired of the almost total lack of support for combating POV pushing in the I-P topic area. Many users either don't see the problems (presumably due to systemic bias), or else run a mile when they see a dispute in contentious areas come up - some admins won't touch politically sensitive submissions as a matter of policy. I guess at some point I came to the conclusion that it just wasn't worth the hassle.

::::: So I can't pretend to have my finger on the pulse of the project as it currently exists - possibly standards have slipped somewhat due to the implementation of QPQ, as admins have come to rely on it too much instead of verifying hooks themselves. DYK is a constant grind and it's usually left up to just a handful of admins to run it. Sometimes I think WP should have some sort of roster system where admins were encouraged to take part in one part of the project or another for a set period - there are lots of areas that are short of manpower. ] (]) 14:07, 21 July 2011 (UTC)

:::::: But if those are, in fact, the identifiable issues (quid pro quo and too much volume), why can't both of them be solved? Eliminate the QPQ reviewing, get a directorate, and reduce the turnover volume to one queue per day. I don't mean to propose solutions-- you all should know best-- but who is the "you all" at DYK, if knowledgeable editors move along and denialists and apologists move in? Who will fix this? ] (]) 14:18, 21 July 2011 (UTC)
:::::::Not being an old hand at DYK, I dont understand this statement "Eliminate the QPQ reviewing, get a directorate". Could you please elucidate, SandyGeorgia? ] (]) 14:25, 21 July 2011 (UTC)
:::::::: I too was a bit lost in the shorthand introduced in Gatoclass's post, but I assume that when he used QPQ he meant Quid Pro Quo reviewing. DYK instituted in the last year a process that requires nominators to review another editors' hook (QPQ)-- I believe that to be a big step in the wrong direction, and it is something we have studiously avoided at FAC, for a number of reasons that I would think are obvious, but I will elaborate if necessary. By directorate, I mean that FAC, FLC and others have directors and delegates in charge, so that some real person is responsible if repeat issues aren't corrected. We had one bad, and well publicized instance, of copyvio at FAC, and we took responsibility and got on it and corrected the problem. By directorate here, I mean a core group of experienced knowlegdeable editors who are where the buck stops before a DYK is put on the main page-- in this case, it took at least five editors to contribute to the mistake, but there is no one "in charge", no one "responsible", no bottom line of accountability. ] (]) 14:53, 21 July 2011 (UTC)

::::::: As I've said, reducing the number of hooks which appear on the main page does nothing to reduce the workload, because the number of ''submissions'' remains the same. We could increase the DYK requirements but such proposals have always been shot down in the past.

::::::: I guess one thing that could be done is to have greater accountability at the update level, where admins have to actually sign off on some sort of boilerplate statement saying they have checked all the hooks thoroughly for compliance with DYK rules before loading them. ATM admins have the option of signing off on the update, but they are not obliged to vouch for its quality. Just a simple change like that might go a long way toward improving the output. It would discourage admins from treating the update process as nothing more than a series of mechanical actions. ] (]) 14:37, 21 July 2011 (UTC)
:::::::: Gato, whatever you all decide to do, another thing to consider is the kind of thing we had to do at FAC to address the backlog from repeat offenders: if a FAC is archived, the nominator can't bring another for two weeks. If you make some kind of change, perhaps whenever you find a problem, that person then either can't review or can't submit for several weeks-- that may help slow down the high level of submissions, and encourage folks to get it right the first time. Just an idea, that may or may not be applicable here as it is at FAC. ] (]) 14:58, 21 July 2011 (UTC)

::::::::: Hmmm, that could also work at T:TDYK level too - if users verify hooks that turn out to be problematic, they could be banned from submitting any more DYKs for a set period of time. That would be one way to increase the quality of reviews, especially QPQ reviews. ] (]) 15:47, 21 July 2011 (UTC)

:::::::::: But take care not to phrase it as "banning" or "sanctions", as that can be off-putting. Allow them to save face-- frame it as a means to reduce the backlog and assure adequate review and give nominators and reviewers time to address previous mistakes, rather than as some kind of penalty, ban or sanction. Honestly, we had to put a FAC rule change in place to deal with one nominator's abuses, but it isn't helpful to call attention to individuals and their mistakes-- it's more helpful to simply put processes in place that improve quality and encourage better submissions without blame. If nominators know that an archival means that can't come back for two weeks, they will hopefully bring increasingly better prepared articles to FAC. ] (]) 15:51, 21 July 2011 (UTC)

::::::::::: What's an "archival"? I'm inclined to agree that wording is important - I was shocked at the amount of resistance just to QPQ, which was seen as an unreasonable imposition by some contributors. We wouldn't have to be confrontational about it, but the point would need to be made clear. ] (]) 15:58, 21 July 2011 (UTC)

:::::::::::: A FAC is either "promoted" or "archived" (we used to call it failed, but that's hard on nominator ego :) The problem we had was that some nominators were serial offenders, bringing repeatedly ill-prepared articles to FAC that sapped a lot of reviewer time. As soon as one was archived they put up another, equally deficient FAC that just took reviewer time and increased the backlog. So, we added the two-week wait after archival. See my suggestion in the section below for implementing something similar at DYK. FAC has also seriously rejected-- and will always reject AFAIK-- QPQ reviewing. Nominators are not necessarily good or experienced reviewers, and personal motivations may become an issue. I think doing that at DYK has directly resulted in lower quality: only experienced editors should be vetting mainpage content. ] (]) 16:05, 21 July 2011 (UTC)

::::::::::::: Okay, thanks for the explanation. FYI, QPQ is not a requirement for ''every'' nominator - only those who have at least 5 DYKs to their credit already. The assumption is that anyone who has accumulated five DYKs knows enough about the process to review other noms - but whether they are all bothering to do so adequately is obviously another question. I'm thinking that auto-rejection of their next nomination would be an effective method of improving reviewers' concentration, although I have little doubt after the QPQ experience that there would be howls of outrage from some quarters over such a proposal. ] (]) 16:18, 21 July 2011 (UTC)

{{od}} Glossary for those who are confused by the ]s (my interpretation) -
*QPQ Reviewing = Quid pro quo reviewing, as part of your nomination you are required to review another nomination, certain editors believe this causes sloppy reviewing. <-- Current situation
*Directorate = A group of editors "in charge" of reviewing, who have the experience to do so and the accountability if something gets through. Certain editors believe this will cause a backlog.
Hope that helps AshLin ;) ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 14:45, 21 July 2011 (UTC)
*: Oops, sorry for the repeat above :) ] (]) 14:59, 21 July 2011 (UTC)
*::Thanks SandyGeorgia and Worm That Turned for the explanations! Whenever I have reviewed a DYK I was conscious to try to follow the rules & additional rules to letter and spirit. I was not aware there was a QPQ involved - I thought that unless the other person reviewed my DYK in return for my reviewing his, no QPQ was involved. ] (]) 15:53, 21 July 2011 (UTC)
*::: Correct-- I would not have labeled it QPQ, but QPQ is a potential side effect of requiring nominators to review, which is one of many reasons we have always rejected that proposal at FAC. ] (]) 16:08, 21 July 2011 (UTC)
*Seeing as my choice of the ALT for this DYK is causing more problems than a volcano in downtown Los Angeles, I will try and explain why I chose the ALT. As DYK regulars have probably noted, I prefer the more sensational (a.k.a. hooky) hooks. In this case, the original hook was something that could apply to any old politician. Meanwhile, the ALT was something quite unique (and which I honestly did not see as too negative). As TK did not state which hook he preferred, I went with my gut. Preppers are not required to double check the referencing of hooks, so I assumed it was okay. Sorry for any misunderstandings. ] (]) 00:52, 22 July 2011 (UTC)

=== Instructions/rules additions needed ===
One part of the problem here, is that the reviewer approved the nomination apparently without checking (or even looking at) the alternative hook. Their assumption was that the alternative hook wouldn't be used unless there was some sort of problem followed by a further review, and that therefore they only needed to look at the first hook. This might seem obviously wrong to someone experienced with DYK, but not to a novice reviewer. More to the point, alternative hooks, despite being a well established and widely used practice, aren't mentioned ''at all'' (that I can find) in ] or in ]. They are mentioned in ] under "Proofreading Template talk:Did you know" ("you need to check ALT's, some of which occur in the middle of a paragraph full of comments. Just because an ALT isn't formalized as an ALT, doesn't mean someone can't copy it to a preparation area") and under "Glossary" ("Often an ALT is selected instead of the original version"). Really, there should be some mention of this in the other DYK instruction pages; it might have prevented the problem in this instance. --] (]) 14:49, 21 July 2011 (UTC)

:You're quite right. I looked at the plagiarism, and as it happens didn't even catch all the plagiarism on the page. I also looked at the hook which seemed appropriate and no need for an alt hook, so let it be at that. I've apologized. There's nothing wrong with the instructions; you challenged me to review a page, I did, and screwed up. Happy? All this after your quite frankly comments that continue above. I did look at the hook - am not that stupid. ] (]) 15:17, 21 July 2011 (UTC)
: With respect, I don't think more instruction creep is the solution-- this process is already so obtuse and hard-to-follow, that it's unlikely that adding to it will address the recurring issues. A complete revamp of the process is needed-- this whole business of nominate, prep, queue, move to mainpage, no archives just makes for no accountability or transparency, and this is something we've been discussing for at least a year. Someone needs to take the bull by the horns and revamp the technicalities of how DYK works-- it's impossible for an outsider to follow. And my opinion is that that task would be much eaiser if you reduced it to one queue per day. Everyone who writes a DYK is NOT entitled to mainpage exposure if we don't have enough peoplepower to assure mainpage quality-- tighten the requirements, reduce the submissions, go for one change a day, get a directorate, and if you can avoid these kinds of issues under an improved system, then move back to four queues a day. ] (]) 15:04, 21 July 2011 (UTC)

:I find it astounding that no one seemed to notice this problem. I suggest a simple new rule: Each did you know needs two "good/assume good faith" reviews. Thoughts? ]&nbsp;<sup>]&nbsp;]</sup> 15:08, 21 July 2011 (UTC)

:: That would just destroy the whole point of QPQ, which was to ''reduce'' the reviewing burden on the regulars.

:: IMO, if a double-check system was to be implemented, it would make more sense, as Sharktopus suggested above, to implement it at the Prep level rather than at T:TDYK. But I've already suggested a less onerous alternative to this, which I think should be tried first. ] (]) 15:20, 21 July 2011 (UTC)

=== Continuing ===
Um, POV on the mainpage is also something we should watch for. The same editor who put up the nasty BLP that led to this has another DYK today, which raises eyebrows at least. ]. Looks like a pattern of editing with an agenda to me: YMMV. And can someone tell me why we use a primary source to discuss his $250 contribution to the Republican party? Have reliable sources mentioned it? Houston, don't look now, but you've got big problems. Also, I can't locate any info about perhaps I'm missing it, but I've reviewed their entire "About" page and don't find anything qualifying them as a reliable source. Who reviewed this time? Does DYK really want to continue in the business of allowing such clearly biased content to be put on the mainpage, because someone claims to have checked one sentence? We have another purely negative, unbalanced article on a politician on the mainpage-- now a pattern. Please someone consider whether it should be removed. ] (]) 16:37, 21 July 2011 (UTC)

: Sorry, but I'm not seeing any great problem with that hook or article. There is nothing wrong with primary sources, AFAIK there is nothing sinister about the ], and I don't see how supporting an "anti-bullying bill" represents an attack on a politician. ] (]) 16:40, 21 July 2011 (UTC)

:: Interesting-- the problem is more systemic than I thought. Well, it must be a good time to go the ballgame and unwatch DYK, which is rather clearly beyond help. See y'all next time round. ] (]) 16:42, 21 July 2011 (UTC)

::: Oh come on, that's a total copout, apart from being a slight on my own capabilities. Please explain the nature of your objections so that I at least have the opportunity to defend myself. ] (]) 16:45, 21 July 2011 (UTC)

:::: Perhaps Dominic will come along, and perhaps some CUs will come along. I'm afraid it looks like DYK is part of a much larger systemic problem than even I thought. Honestly, clean up your act. If you don't know the problem with using primary sources and non-reliable sources in political bios, I can't help you. What's going on here is alarming in how long it's been happening, but plainly disgusting in the levels to which it has reached. I'd much rather go to the ballgame now, bye. ] (]) 16:53, 21 July 2011 (UTC)

::::: I concede that I've missed the public figure/primary source issue up to now, it's the kind of nuance that as a regular FAC contributor you would be well aware of but you shouldn't assume everyone has the same level of familiarity that you and your fellow FAC contributors have accumulated. As for unreliable sources, of course we don't accept them. Had I reviewed this article myself, I would certainly have raised questions about it, however, many articles get promoted that I myself would not promote, and one cannot get too far out of step with one's colleagues. It seems you are trying to bring FAC standards to a process that is radically different - we simply can't give articles that kind of scrutiny. I can't possibly go through ''every'' source in ''every'' article in ''every'' update to ensure that ''every'' fact is verified - one has to rely on the wider process to some extent. ] (]) 17:19, 21 July 2011 (UTC)

::::: And BTW, referring to the contributions of other good faith editors as "plainly disgusting" is uncivil in the extreme - I must say I am deeply disappointed with your attitude and your comments in this thread. ] (]) 17:22, 21 July 2011 (UTC)

:::::: Without disparaging the legitimate concerns that Sandy's raising--I agree that <s>this hook's</s> the ] hook's appearance on the main page was a problem and we should discuss how to better prevent its recurrence--the ] tone strikes me, too, as both off-putting and likely to generate more heat than light. -- ] (]) 18:03, 21 July 2011 (UTC)
:::::::::<small>Sorry for any confusion created by my comment above; I lost track of where I was posting. It's the Christian hook that seems objectionable to me, not the Downs. -- ] (]) 18:45, 21 July 2011 (UTC)</small>

::::::: Looking at the particular ] in this thread, I'm having trouble following Sandy's description of it as "purely negative", "clearly biased", "plainly disgusting", etc. The language describing Downs' history and legislation seems to me neutral and (for the latter) to give due weight to both sides of arguments, and while I agree that the mention of the donation to the RNC was silly and rightly deleted as irrelevant, I have trouble seeing how it was an attack. The guy's a Republican state representative; why would anyone be surprised by this? If anything, I think this article makes Downs sounds rather good. I see no reason to remove it from the main page. -- ] (]) 18:45, 21 July 2011 (UTC)
*'''Question''': Do you mean the creator or the prepper? If you mean the prepper, I will let you know that I have no opinion on US politics, especially on the state level. ] (]) 01:42, 22 July 2011 (UTC)

:: The author of this article has something like 800 DYKs to his credit, and though his contributions have been serially problematic in one way or another, I've never heard anyone accuse him of "having an agenda" against Republicans - AFAIK his political bios are almost exclusively on Republicans, and I've always made the assumption the writer is a Republican himself. So I think Sandy is just plain wrong on that score. I agree that the bio is a little rough, but so are lots of DYKs, perfection is not the goal here, these are Misplaced Pages's ''newest'' articles and it's expected that there will be room for improvement. Judging by Sandy's dummy spit in this thread, what our most trenchant critics are expecting to see at DYK is FAC- or at least GA-level rigour, if that's what they want then we should just hand DYK over to the GA process and scrap this process altogether, because we don't remotely have the resources for that level of reviewing and never will. ] (]) 02:11, 22 July 2011 (UTC)

:::Gato, that's alarmingly like what Rlevse said to me when I first questioned his approving of nominations where almost all of the article was basically copy and pasted from a single scouting website of unknown provenance. "These articles can be tricky to source", and "this isn't GA you know" ... and onto the main page they went. No-one else saw a problem with it, and I was too new to put up a fight. Are we sleep-walking to a new disaster? --] (]) 07:00, 22 July 2011 (UTC)

:::: Not at all. I wouldn't for a moment endorse putting plagiarism or copyvio on the mainpage, and in the past I've argued for the strongest possible sanctions for those who submit such articles, proposing that any such articles be automatically disqualified and that repeat offenders be banned. As usual, I got little support for my views. As for Rlevse, I had ongoing serious misgivings with the quality of his reviews, but made few comments since (a) he was at the time a sitting arbitrator who ought to have known what he was doing, and (b) he was a prolific contributor whom I didn't want to alienate. In retrospect, it's clear we all should have been more vigilant, but let's not forget that Rlevse's plagiarism also got a free pass for an extended period at FAC, where there really ''is'' no excuse. ] (]) 09:23, 22 July 2011 (UTC)

:Despite making a mistake on the hook, I didn't make a mistake on the close paraphrasing issues with ]. The Downs page has the same problems, fwiw. I'd think this would be case where an editor should have a greater level of scrutiny, or something. ] (]) 01:54, 22 July 2011 (UTC)
::Am I crazy or did we not have a discussion awhile back about the author of this article ({{User|Billy Hathorn}}) <s>and plagiarizing</s>? Or was it sourcing? Either way, this is a really ''really'' bad thing to find in someone who has written so many pages. ]&nbsp;<sup>]] ]]</sup> 07:59, 22 July 2011 (UTC)

::: Billy has an ongoing problem with the use of substandard sources for his articles, it's not that ''all'' the sources he employs are substandard but he doesn't exercise much discrimination. He also used to have a problem with writing articles on people who failed ], although he has improved in that regard.

::: I'm not aware of any plagiarism issues in his articles, if this is a recent concern I've missed it. He appears to have good language skills and is able to put things into his own words and usually does in my experience. If he's starting to take shortcuts, obviously that's something that will need to be addressed but I'd have to see some evidence of that. ] (]) 09:40, 22 July 2011 (UTC)
::::No, this would have been awhile ago. It was probably over sourcing. Anyway, TK above says that she found close paraphrasing in two of his articles &ndash; that's what I was going off of. Could you (TK) provide some examples? ]&nbsp;<sup>]] ]]</sup> 18:18, 22 July 2011 (UTC)

=== Next scandal of the day, keep 'em coming===
{{od}} The sourcing problems, BLP problems, and plagiarism are easily found, including in today's DYK-- that no one here is aware of them in someone with this many DYKs is not surprising, considering the history of serial plagiarizers who have gotten away with it for years at DYK with no regulars here detecting the problems. But, again, plagiarism and copyvio are not the only problems DYK is showcasing on the mainpage-- poor sourcing is an equal concern.

Have some easily found examples (we can go on for pages and pages, but perhaps one of the good folk here will get off their duffs and open the copyright investiation on the work enabled by this process):

] nominated for DYK on July 12.

:Article:
*Young Dove's vehicle '''careened across the highway, crashed into the right guardrail,''' and overturned '''several times'''. His seat belt was not fastened. '''Partially thrown out the back window and pinned beneath the''' SUV, '''he died at the scene'''.
:Source:
*The SUV '''careened''' back '''across the highway, crashed into the right guardrail''' and flipped '''several times'''. Dove, who police said was not wearing a seat belt, was '''partially thrown out the back window and pinned beneath the''' vehicle. '''He died at the scene'''.
:Article:
*Dove is chairman of the House Natural Resources Committee and works to '''raise awareness of the importance of coastal passes and barrier islands'''. He supports the '''north-south corridor for hurricane evacuation''' and the funding of the hurricane protection system from Morganza to the Gulf of Mexico. Dove also supports the state charity hospital system by removing the '''Medicare and Medicaid caps placed on the hospitals'''
:Source:
*As chairman of the House Natural Resources Committee, Dove will be a coastal floor leader for some years to come. In particular, he is interested in '''raising awareness of the importance of coastal passes and barrier islands'''. ... On health care, he supports funding the state’s charity hospital system by lifting existing '''Medicare and Medicaid caps placed on the hospitals'''. On coastal protections, the planned '''north-south corridor for hurricane evacuation''' and the funding of the Morganza-to-the-Gulf hurricane protection system are top objectives.

Deny away. DYK has got more than one prolific editor who doesn't know reliable sourcing, doesn't know BLP, and doesn't know how to paraphrase content in their own words, and you have no mechanism for preventing this systemic issue from being displayed on the mainpage. Why, again, is it that we MUST display new content, rather than vetted content, on the mainpage? And why is it that DYK has no directorate, no one responsible for these messes? ] (]) 23:05, 22 July 2011 (UTC)

] (]) 23:05, 22 July 2011 (UTC)


:I didn't see this as a scandal but a controvery in which Mr. Christian prevailed. ] (]) 19:09, 22 July 2011 (UTC)
::I did do some rewording to minimise some of this - looks like some more would be prudent. ] (] '''·''' ]) 04:34, 23 July 2011 (UTC)

I can't think of a way to equate "careen" with something else, nor "north-south corridor", "raise awareness of the importance" should be doable. ] (] '''·''' ]) 04:57, 23 July 2011 (UTC)

=== Next ===
* ]. After removing all the text in a BLP not cited to reliable sources, does it still meet the size needed for DYK? How can you all be passing DYKs on size needed without checking that sources are reliable, and why are you putting BLPs on the mainpage with non-RS? More importantly, why are you still passing DYKs from this particular writer, given the number of issues already identified? ] (]) 02:32, 23 July 2011 (UTC)

=== Nexxxxxt ===
* ]; I'll let some other genius spot the close paraphrasing, plagiarism, or whatever you want to call it, but the article is built almost entirely from non-reliable sources, so how does it meet the expansion criteria? ] (]) 02:42, 23 July 2011 (UTC)

:: Sandy, your hyperbole on this page is becoming increasingly irritating. More than once now you have described articles with minor flaws as "egregiously bad". The supposed "BLP violations" you are finding are at best technical, and at times questionable (what is wrong with votesmart.org?). There's a difference between constructive criticism and mudslinging, the latter only causes resentment so please try to exercise some restraint. We are already discussing ways to improve the process so this ongoing documentation of alleged errors is just becoming a distraction. ] (]) 06:20, 23 July 2011 (UTC)
::*I agree with Gato. What's next? Something like this? <blockquote>"]"</blockquote>
:::You have raised valid points, which has ignited a longer discussion than most threads in the history of DYK. I think that participating in said discussion, rather than adding trivial or questionable mistakes to the "list" here, would be a better way to improve Misplaced Pages. As Gatoclass said, there is a difference between constructive criticism and mudslinging. ] (]) 11:52, 23 July 2011 (UTC)
:::: Hyperbole might apply if you all weren't continuing to put serial plagiarism, BLP vios and faulty sourcing on the mainpage YEARS after this discussion has been going on, and if you weren't continuing to do exactly the same in every single DYK queue since this first came to light, thanks to TK's unfortunate dip into the mess here. It '''might'' be hyperbole if you all were doing a single thing to stop it. You're not: you're enabling it and continuing it and several DYK regulars have evidenced that they have no clue or concern for Misplaced Pages policies. ] (]) 14:28, 23 July 2011 (UTC)

::::The problem is that the copyvio really needs to be addressed. From the source : ''''''in which contestants would have to guess the identity of a celebrity based on a few given clues.'''''' From the article: "''and a section called "What's My Name?", '''in which contestants sought to guess the identity of a celebrity based on a few clues'''''. This from the first sentence I've checked. ] (]) 11:59, 23 July 2011 (UTC)
:::::That is a somewhat close paraphrase, but information cannot be copyrighted. I don't think it would qualify as a copyvio, as there ''is'' paraphrasing. ] (]) 12:25, 23 July 2011 (UTC)

:::::::No, you are wrong. Simply changing a few words most certainly can constitute copyvio. I don't know what you mean by your statement that information cannot be copyrighted. ] (]) 13:33, 23 July 2011 (UTC)

:::::::: I'm not trying to deny the seriousness of problems like copyvio and close paraphrasing, and the examples raised are valid and will require action, but many of the other supposedly "egregiously bad" examples are relatively minor and in some cases, nonexistent. This particular article, for example, hasn't even been reviewed - and yet it's being used as an example of DYK's supposedly broken processes. Threads like this are just becoming a distraction when we are already discussing methods of improving the system. ] (]) 13:35, 23 July 2011 (UTC)
::::::::In one sentence (5 words out of a total of 15 or so)? No. A few words in a whole article? Most definitely. As for information, perhaps facts would have been a better term. ] (]) 13:35, 23 July 2011 (UTC)
::::::::@Crisco - I looked at one sentence from one source in one article. We don't count words - we look at similarity. This is a fundamental misunderstanding of how to rewrite source material that I find worrying. ] (]) 13:48, 23 July 2011 (UTC)
:::::::::I understand that, but using one example that is only one sentence long is not the best way to show a possible violation. Numerous structural and lexical similarities would be best. Naturally, if we are worried about it we could rewrite the article, with more paraphrasing and whatnot. ] (]) 13:52, 23 July 2011 (UTC)

:::::::::: Pretty big problem here when two DYK regulars don't understand the seriousness even when it's black and white. No, people who don't get this should not be working at DYK in *any* capacity-- we cannot be putting this kind of thing regularly on the mainpage, and the reason it hasn't been fixed in more than a couple of years of awareness is the the DYK regulars either don't get it or don't care. I don't know if this is incompetence or indifference, but it's quite alarming. By now, someone should have started a copyvio investigation on the Billy editor doing this (and no, Carcharoth, I can't keep all the players straight here, nor do I presume to remember in the midst of a discussion that Crisco is 1942-- there's something to be said for choosing a username others can remember). ] (]) 13:55, 23 July 2011 (UTC)
:::::::::::::An investigation of the nominator would be acceptable, although I take offence at the suggestion that I do not understand basic copyright law. As I have noted above, facts cannot be copyrighted; it would be ridiculous to try and copyright the fact that Misplaced Pages was founded in 2001, for example. The wording of the facts themselves may be copyrighted, but a single sentence is not always indicative of a violation, especially when efforts were made to paraphrase it. As for the user name, I have had it for nearly 5 years now and the meaning is explained explicitly on my userpage. You are the first to complain that it is too hard to remember, and if you feel so please call me Crisco. ] (]) 14:03, 23 July 2011 (UTC)
::::::::::::Using a single sentence is called spotchecking. It's how it's done. If I were a teacher or a professor, spotchecked and found that, I'd know all I needed. This is pretty much best practice for finding copyvio. We have 3 million or more articles - the best that can be done is spotcheck a few at a time. That's how it works, and the example is quite clearly copyvio. ] (]) 14:10, 23 July 2011 (UTC)
::::::::::::::I am quite clear on what spotchecking is; I've done it myself with my students. However, spotchecking and demonstrating copyright violations are two completely different balls of wax; a spotcheck helps to find the copyvio, but numerous similarities prove it. You seem to have submitted the above as proof of a copyright violation. Perhaps a link to the tool's readings would help? I forget its name. ] (]) 14:16, 23 July 2011 (UTC)
:::::::::::::::The tool is my eyes. ] (]) 14:30, 23 July 2011 (UTC)
:::::::::::::::: would help show possible copyvios much more thoroughly. ] (]) 14:39, 23 July 2011 (UTC)
::::::::::::::::It gives , which doesn't convince me of anything but a close paraphrasing. ] (]) 14:41, 23 July 2011 (UTC)
Oh for gosh sakes, stop the obfuscating: DYK puts serial plagiarizers on the mainpage, all the time, and even when they know it, they continue to do it. That's a bigger point than the fact that many regulars here don't consider it their job to stop enabling writers to violate Misplaced Pages BLP, sourcing and copyvio policies. Focus. ] (]) 14:24, 23 July 2011 (UTC)
:I'm highly tempted to hat most of this discussion so that we can focus; we have 7 (and counting) sub sections to this thread. Yes, you are showing good indicators that we have a problem of close paraphrasing, which as mentioned somewhere on this talk page is a guideline and not a policy. As to whether or not it is close enough to be called a copyvio, we have numerous editors who could be called in to weigh in on it. However, the I doubt the actions of a single editor should be used to waterboard the entire DYK community. Perhaps you would like to check some of the other articles featured today and then let us know if it is DYK that is at fault or the one editor. ] (]) 14:30, 23 July 2011 (UTC)
::Hatting it shoves the problem under the rug. ] (]) 14:34, 23 July 2011 (UTC)
:::Very well then, could someone please choose which subsection we should continue this discussion in? ] (]) 14:36, 23 July 2011 (UTC)
::::Discussion is done. Sandy brought up the article; I spotchecked and found problems. You seem to believe this kind of writing is acceptable for main page content. There's nothing more to discuss, but the section should stay as documentation. ] (]) 14:39, 23 July 2011 (UTC)

:::: Crisco, might I inquire if you were involved over the years the '''numerous''' times we've had this same discussion, and '''nothing''' has been done about it-- in fact, it's gotten worse? Last time it was other editors, the same denialists and enablers denied the problem, hence the problem is still here. Next week it will be another editor, because <s>your</s> the DYK process is deficient, <s>you've</s> DYK has done nothing to correct it, and it only got worse after last year's Halloween debacle. No, you won't hat it-- as long as every queue has blatant policy violations, and you all do nothing about it, and five (at least) RFCs are running, I will continue to highlight that <s>you've</s> DYK has done zilch, for many years, except shoot the messenger and complain that I'm highlighting <s>your</s>the faulty process. ] (]) 14:39, 23 July 2011 (UTC)
::::I would appreciate using a less ambiguous term than ''you'', because if you are referring to me (the editor) then I am beginning to consider this a borderline ]. I have '''not''' done zilch for years, as I have been active at DYK for only a few months; I have '''not''' become an enabler (I have tried to review thoroughly); I have tried to correct it, which is why I am here discussing this at 9pm on a Saturday night; I have '''not''' "shot the messenger" (I have offered that you try reviewing a couple current noms at least twice, to catch problems ''before'' they become problems). As for the copyright issue, I have already noted numerous times; a close paraphrase cannot be considered a blatant copyvio. I have offered a link to the tool to help TK prove his/her statement, although the results seem ambiguous to me. I have also tried to forgive your twisting of my comments. Please, can we discuss this in a neutral and less standoffish manner? None of us right now are stellar examples of ]. ] (]) 14:51, 23 July 2011 (UTC)
::::: Good point about my generic vs specific use of "you"-- I have corrected above, it's a frequent fault of mine (as is not knowing full editor names and shortening them, even on TK, an editor I know well). Anyway, once again, you may consider my tone harsh if you think this is a stand-alone incident: it's not, it's a repeat month after month, year after year, that DYK does not address. THe only thing that changes is a new crop of serial offenders and a new crop of enablers/denialists every few months. ] (]) 15:08, 23 July 2011 (UTC)
:::::::Thank you for the quick reply and fix. I've noticed a general distrust of DYK held by numerous editors (especially those active in ]), but this is the first truly contentious debate I have participated in. Right now Billy's hooks are in the process of being double checked. As for the further changes... I do not know. ] (]) 15:15, 23 July 2011 (UTC)
:::::::::: Also, the essay on close paraphrasing may be an essay, but it is not so much a stand-alone essay, as a practical interpretation of a very firm and pretty universal policy on copyvios and plagiarism. I agree we need to do something here. I think the first thing is to check if it is more generalised or not. Agree we should all work together and maybe all take a breather. Ha, it's 1 am where I am. ] (] '''·''' ]) 14:55, 23 July 2011 (UTC)
::::::::::PS: I guess it also highlights the tightrope walking of content contribution, too close to sources and we veer close to copyvio, too far and it's into OR or synthesis. ] (] '''·''' ]) 14:56, 23 July 2011 (UTC)
:::::::::::<small>It's actually 10... I must have lost track of time</small> Indeed it does, and it is something we need to worry about. However, I don't see a firm definition of when paraphrasing becomes too close. My interpretation is that the article or section would have to be based mostly on one source to be closely paraphrased; if it uses numerous reliable sources, with paraphrasing, to paint a complete picture of the subject, it would be a new creation. Methinks, at least. A cup of tea would be nice... ] (]) 15:00, 23 July 2011 (UTC)

=== The show goes on, next again ===
Today's DYK: ]. First, does anyone here care to explain why several of those sources are reliable, or how you can qualify as having expanded an article based on non-reliable sources? More importantly, why, in the midst of this discussion, is DYK STILL doing same ???

*Source: Carmody first made a name for himself in the community in 2003 by '''pushing for an independent review of the police-related shooting death of Marquise Hudspeth''', which '''made national headlines at the time.'''

*Article: In 2003, councilman Carmody '''pushed for an independent review of the police-related shooting death of Marquise Hudspeth''', which '''at the time acquired national headlines.'''

This is BLATANT. I didn't even check the rest of the article-- that one was only the first I saw. Who approved the hook? And Cas, I'd like to know why you put it on the mainpage. ] (]) 14:21, 23 July 2011 (UTC)

:My name came up as the DYK giver as I moved the batch from the prep area to the queue. I wasn't aware of the issues at that point. ] (] '''·''' ]) 14:31, 23 July 2011 (UTC)

:: Thanks, Cas-- I appreciate the explanation, because the system and lack of archives here is MUCH too complex for an outsider to understand. So, the next question is, what is DYK doing '''now''' to shut down this editor, and who will bring in the copyvio people? He's got hundreds of DYKs that need looking at by people who know copyvio. Must I do everything? ] (])
:::He still has numerous noms at ], which could be double checked. ] (]) 14:54, 23 July 2011 (UTC)
::::I think that is a good place to start, and a friendly word. ] (] '''·''' ]) 14:57, 23 July 2011 (UTC)
::::In my opinion, all of those should be put on hold until someone explicitly takes responsibility for checking them for close paraphrasing problems. Are there any in prep and the queues? --] (]) 14:59, 23 July 2011 (UTC)
:::::At least one: ] in Queue 5. I'll add more if I see them. ] (]) 15:02, 23 July 2011 (UTC)
:::::] in Prep 3 ] (]) 15:04, 23 July 2011 (UTC)
: I queried MRG, and now I must get on with my day. ] (]) 15:10, 23 July 2011 (UTC)

== Disagreement over a hook ==

Would be great if this receives some third opinion. ]] 08:06, 21 July 2011 (UTC)

: I commented in the thread, although I was pre-empted by another comment from Binksternet. ] (]) 08:53, 21 July 2011 (UTC)

== Suggestion/question ==

Reading the commentary above I very much agree with Gatoclass that there is a need to reduce the number of DYK submissions and in order for us to do that DYK nomination standards have to be raised (basically we need to make it harder to write DYK-worthy article - I'd start with a simple no brainer of raising min character count to 2500 characters). But the other side of the problem is potentially sloppy reviewing. I was wondering then if it would be possible to somehow change how reviewers mark articles they've checked.

Right now, if I go to review an article I'm told where to put my comment and given the list of 'ticks': ] · ] · ] · ] · ]. But there's nothing on the page which will tell or remind me what the actual rules for DYK are. Back in the day when doing reviews I often had to go back and look up the (particularly since I kept thinking articles had to be 2500 characters) each time just to make sure.

What I think would better is if there was a built in template that pops up new nominations when you open the edit window to give your review of the article. It shouldn't be a all or nothing one either (though to get it passed all aspect would have to be approved) but should specifically list the things that need to be checked, as a reminder to reviewers. I would include in the template something like

<nowiki>{{hook length=|hook source=|adequate sourcing=|article length=|vintage=|close paraphrasing=|sources accessible=|comment=}}</nowiki>

which would be very much like the template for DYK nominations themselves (and you can stick the cute little 'ticks' in there). Of source these sections of the review template can be named whatever but basically such a template should remind reviewers that they need to check all of these things (the last one "sources accessible" would just indicate whether they sources are available easily (which basically means online and in English), with "agf" an option).

While this would probably not deter any kind of unscrupulous reviewers, it would make it immediately explicit to everyone what is expected of them in the review process.] (]) 13:05, 21 July 2011 (UTC)
:That's a very clever and interesting idea, VM. Right now, a potential reviewer who clicks "Edit" on an article entry at T:TDYK sees a designed to help people nominating articles, not people reviewing them. Reviewers don't need that information but they could use different information, and a different template. Does one of our resident ninjas know how to implement this? <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 13:42, 21 July 2011 (UTC)

: (edit conflict) That's one possibility I guess, although it would make for a more cluttered page. I think the main problem is that DYK admins tend to get a little slack from time to time. Perhaps we just need to more strongly emphasize the need for admins to check hooks thoroughly for problems before loading them into the queue. It's what is supposed to happen, but overworked admins sometimes resort to cutting corners. ] (]) 13:45, 21 July 2011 (UTC)
::Yes but this is exactly part of "more strongly emphasize". How else would you do it? Tsk tsk people after the fact?] (]) 14:26, 21 July 2011 (UTC)
:::I really like this proposal to improve the supporting structure. It is simple, it is targeted, and it is quantized (easy to tell whether it has been implemented or not). <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 15:13, 21 July 2011 (UTC)

:::: It could work provided it doesn't take up too much space. I guess it could be implemented something like article rating templates - you have a series of questions to which you respond "y" or "n", and based on your input, the template outputs the appropriate icon. ] (]) 15:26, 21 July 2011 (UTC)

::::: I agree that some version of this seems worth trying. -- ] (]) 18:04, 21 July 2011 (UTC)

::::::''you have a series of questions to which you respond "y" or "n", and based on your input, the template outputs the appropriate icon'' - yes, that's exactly the idea I had in mind. The only wrinkle would be that the "checked sources" entry would have an "AGF" option for sources that are not available online or are not in English.] (]) 04:43, 22 July 2011 (UTC)

== DYK is almost overdue ==

<!-- 2011-07-22T00:00:00Z -->
In less than two hours ] will need to be updated, however the ''']''' either has no hooks or has not been approved by an administrator. It would be much appreciated if an administrator would take the time to ensure that DYK is updated on time by following these instructions:
# Check the ''']'''; if there are between 6-10 hooks on the page then it is probably good to go. If not move approved hooks from the ''']''' and add them and the credits as required.
# Once completed edit ''']''' and replace the page with the entire content from the next update
# Add <nowiki>{{</nowiki>]<nowiki>|~~~}}</nowiki> to the top of the queue and save the page
Then, when the time is right I will be able to update the template.
Thanks and have a good day, ] (]) 14:06, 21 July 2011 (UTC)

: I've dropped a couple of new updates into the queue. ] (]) 15:11, 21 July 2011 (UTC)
::...and I've now moved 2 more preps into the queue, and have populated 3 prep areas for double checking by someone else. --] (]) 02:47, 22 July 2011 (UTC)

== Proposal - minimum character requirement increase from 1500 to 2500 ==

It is regularly pointed out, correctly, that reducing the number of hooks that rotate through the main page, will not solve the problems, because it will not reduce the number of submissions that need to be evaluated. Therefore, a proposal is to increase the readable prose minimum requirement from 1500 characters to 2500 characters. This should not be very difficult to achieve for the vast majority of articles (I just checked one of my own rather start-class DYKs and it came to 2275 chars, so certainly possible to improve it a bit), and it should act to reduce, slightly, the number of incoming submissions. This would give reviewers and administrators more time to deal with reviewing and checking, and also in turn support a reduction of the number of hooks rotating through the main page, to focus more on quality (and less on plagiarism, sensationalism, boring hooks).

*'''Support''' as proposer. --] (]) 15:07, 21 July 2011 (UTC)
*'''Support''' for a start. ]&nbsp;<span style="font-weight:bold;">&middot;</span>&#32;(]) 15:11, 21 July 2011 (UTC)

*'''Comment''' - I think this !vote is premature. !Votes should never be proposed before thorough discussion, and this notion has barely been discussed at all. ] (]) 15:23, 21 July 2011 (UTC)

* I agree with Gatoclass. There are already a bunch of proposals and discussions, and "voting" on any one is premature. I think that's how the QPQ problem came about-- the desire for a quick fix without a serious analysis of how to get a long-term fix. I for one would want to know how you're going to check even more content if smaller articles aren't being checked now? It is not OK that, even if the hook is checked, we're putting some really faulty articles on the mainpage-- why would this not mean we're putting even more faulty content linked from the mainpage? Perhaps this is the only way to slow down submissions; isn't there another way? Editors who don't understand how to correctly represent sources in their own words can do 2,500 words just as fast as they can do 1,500-- the original editor whose plagiarism brought this problem to my attention was one of DYK's most prolific editors. He turned out plagiarized bios from obits that set records, and no one caught it here. ] (]) 15:35, 21 July 2011 (UTC)

:* Quite frankly, I don't want to slow down submissions, I like the fact that lots of different hooks get featured and that less talented editors can get some encouragement through this process. And I think we would have to slow down submissions a ''lot'' before it started having an impact on quality of reviews. IMO we would be better to stick to trying to improve the reviewing at Prep level for the present, we don't want to start making radical changes when they may not be necessary. ] (]) 15:44, 21 July 2011 (UTC)
::* Good points. My gut feeling is that having a panel of directors where the buck stops might be a better way to address all of the issues, but you really really really need a clearer, easier, more transparent process with archives, as well. ] (]) 15:47, 21 July 2011 (UTC)

::: Actually, we are doing the archives thing, it was recently decided to have a separate page for each submission, it's just that the coder is unavailable right now. I think your notion of sanctions for sloppy reviewing may also have merit BTW. ] (]) 15:53, 21 July 2011 (UTC)
::::: I didn't know that-- that's good news, glad to hear of the improvement. We don't need to point fingers, but you can't solve problems unless you know who is committing them and why (and that's why I keep asking why Crisco ran the alt hook instead of the one TK reviewed-- why did s/he do that? You can't solve the problem without knowing what went into making the problem.) ] (]) 15:56, 21 July 2011 (UTC)
::::Well the discussion here is endless, so many pages of it that every time a major concern is raised (which, let's face it, could be done on a daily basis given the quality of some of the material going through) then the process gets backlogged because the people who keep the system running are busy replying to yet another round of discussion. (As just happened). You all need to work out how your proposed directorate is going to keep up with maintaining quality for that level of submissions, if there's never going to be any willingness to increase the standards for submissions or tell anyone they don't have an absolute right to put their article on the main page if they can get it to meet a very basic list of requirements. --] (]) 15:55, 21 July 2011 (UTC)

::::: Well, I don't like to further my proposal when you all know better, but my idea is something like this. Admins move the queue to the main page. That is the point at which problems should be identified-- the critical point that matters. Ditch the "any admin" can move it, set up a panel, a directorate at that level, only that panel can place the content on the main page, and they are responsible for EVERYTHING about that hook-- not only that plagiarism and copyvio are avoided, but that other policies are upheld as well. At that level, if an already approved hook has to be rejected, then that nominator can't put up another DYK for a month, and that reviewer can't approve a hook for another month. Just an idea-- you all can make it better. IF a "director" makes repeat mistakes, resulting in mainpage debacles, that director will find him/herself out of business soon, in a vote of no-confidence. ] (]) 16:01, 21 July 2011 (UTC)

:::::: That would be an ideal system, but I doubt we would ever have the manpower for it. However, I think it might be possible to start doing a few things to tighten up quality control until an appropriate standard is reached, some of which have already been suggested in the various threads above. ] (]) 16:09, 21 July 2011 (UTC)
::::::But what would that achieve beyond a blame game? ] &#124; ] 16:11, 21 July 2011 (UTC)
::::::: It's not about "blame game"-- putting some brakes on like this encourages nominators and reviewers alike to get it right the first time, hence lowers wasted reviewer time. OK, Gato, how about a middle of the road compromise? You're at four queues per day now, right? Lower it to only three-- you're not losing that much, the directorate will have more time to review, and quality will improve and those that submit faulty articles will be ..... ummmmmm ... exposed and less likely to continue submissions, so submissions will decline slightly while improving in quality, so that you can hopefully move back to four queues daily once the new system is working. ] (]) 16:14, 21 July 2011 (UTC)

:Too many people have come to see it as their right to have their article on DYK if it's 1500 characters—even if it's crap, and even if the hook is boring. I don't think that will stop if we up the character limit, and I think folks here are unwilling to say no to nominators, especially prolific ones who throw their weight around to get their article on DYK. Most importantly, though, meeting an arbitrary character count is not an indicator of the quality of the article. It would be difficult to write a decent article in less than 1500 characters, but it's relatively easy to write a long, crappy article. ] &#124; ] 16:11, 21 July 2011 (UTC)

*'''No'''. This has been brought up numerous times before; it would be nice of the proposer to provide links to past iterations of this proposal. The reasons it has been opposed include: 1) quantity != quality; 2) increasing the length limit won't decrease the number of noms (if someone wants to nom, they'll write as much as they need to to do it); 3) increasing the length limit will just increase the fluff. <b class="IPA">]</b>&nbsp;(]) 23:26, 21 July 2011 (UTC)
*'''Oppose''' I have found numerous articles that are quite tricky to get from 1500 to 2500 chars, but more importantly recently-promoted GAs I think provide a better ground of recently-improved-vetted articles. Their introduction will slow the rate down a little. ] (] '''·''' ]) 04:28, 22 July 2011 (UTC)
*'''Support''' as I've suggested this before. To address some of the comments made above:
**Sandy, this of course isn't meant as a fix-it-all approach, in fact, I don't see why it wouldn't be complementary to some of the suggestions you're making. Second, I don't see that this proposal would increase the amount of content that needs to be checked. By eliminating shorter noms it would decrease it.
**Gatoclass, your contention that this hasn't been discussed before contradicts Rjanag's contention that this has been discussed before. Basically, it has been discussed before but I've never seen a good argument not to implement it and the discussion usually gets derailed by "it won't solve all the problems", or in other words, people making the perfect the enemy of the good.
**HJ Mitchell, of course character count isn't a '''perfect''' indicator of quality but let's face it, a 1500 character article is barely more than a stub (honestly, it is a stub). As long as sourcing is required - which it is - then in fact '''it is''' harder to write 2500 character article than a 1500 one. And one way or another we're gonna have a character minimum and it's always going to be somewhat arbitrary. Obviously we don't want 500 character articles. Or 5 character articles. So some line has to be drawn. And I think the current line is too lax/low.
**Rjanag, 1) yes, quantity does not '''necessarily''' imply better quality but I think in this case it does. A 1500 character article is better than a 15 character article, no? And a 2500 character article is likely to be better than a 1500 character article? Now, if you're talking, I dunno, 5k vs. 10k then maybe you'd have a point. But that's not what is being discussed here. 2) '' increasing the length limit won't decrease the number of noms'' - how do you know? Seriously. You got data or something? Evidence? At least a logical argument for why that would be so? By upping the character count you're increasing the cost on the writer which means the laziest people won't submit noms. And that's the whole point. 3) '' increasing the length limit will just increase the fluff'' - how in the world do you get that? You just pulled that out of thin air. Completely unsupported assertion that doesn't even make sense. It might be true if sourcing isn't required, but it is.
**Casliber, ''I have found numerous articles that are quite tricky to get from 1500 to 2500 chars'' - yes and that's exactly the point! If a topic doesn't have 2500 chars in it, it shouldn't be featured. Maybe as a list or something but not a DYK at least. '' recently-promoted GAs I think provide a better ground of recently-improved-vetted articles'' - sure and I supported that idea above. But why does it have to be either/or? Why can't it be both? I've never seen a GA that is less than 2500 characters (and if there are such out there somebody needs to review them again) so this proposal is not going to affect that proposal in anyway.

::Basically it's hard to escape the feeling that the opposition comes from the "it's not perfect, hence it's not good" attitude or something like "I didn't think of it first, so it can't be good". I'll stop there.] (]) 05:04, 22 July 2011 (UTC)
:::In response to your comments addressed to me: more in-depth discussion of all these issues is included in the previous discussions of this perennial proposal. The person proposing it this time neglected his responsibility to share links to the past discussions, but if you look up those discussions you can find answers to these questions. <b class="IPA">]</b>&nbsp;(]) 13:59, 22 July 2011 (UTC)

* '''Oppose''' - I don't agree with the rationale for this proposal. The idea seems to be that a longer prose requirement will reduce the number of submissions. Well, maybe. But will it "give reviewers and administrators more time to deal with reviewing and checking"? No. The problem isn't that we don't have time to review nominations. Rather, the problem is that there aren't people reviewing half of the noms until they're two weeks old, and by that time it's difficult to get an editor/nominator to make changes within the expected timeframe. If DYK participants just spent more time reviewing newly nominated articles, instead of bickering, there wouldn't ''be'' a problem for us to have to fix. --] (]) 05:46, 22 July 2011 (UTC)
* '''Oppose'''. I think it's silly that we're !voting on this at all without a more comprehensive discussion as a preamble, but if other editors insist we are, I guess I might as well cast my !ballot. My first instinct is that this is likely to do as much harm (more cluttery submissions, potentially suppressing quality submissions) as good (reducing workload, encouraging longer new articles). While I'm interested in looking at ideas to improve DYK quality control, this seems to me to be one of the less promising of the ideas proposed today, and I'm reluctant to introduce too many of these at the same time; attacking the issue nine different ways at the same time seems likely to create confusion, and be potentially less effective than if we applied solutions one at a time. And finally, I'd to show V. Marek that not everybody opposing this is doing it because only because they "didn't think of it first", since I've agreed with one of his excellent proposals elsewhere on this page, which I didn't think of first either. =) -- ] (]) 06:29, 22 July 2011 (UTC)
*'''Oppose''' Sorry, I think the quality is hardly correlating with the quantity in a simple linear relation. The more concise the better, encouraging "fluff" is not the way to improve article quality, imo. --] (]) 06:31, 22 July 2011 (UTC)
*'''Oppose''' Quantity does not always mean quality, as shown by numerous POV rants found in the histories of controversial articles. Someone could write 50k of readable text that is a POV rant and it would be less worthy than 1,500 bytes of well researched information on a difficult to research subject. ] (]) 09:22, 22 July 2011 (UTC)
*'''Oppose''' Length does not equal quality.♦ ] 13:49, 22 July 2011 (UTC)
'''Oppose''' I do not think that's a good idea as it is hard to get some new articles up to 1500 let alone 2500 based on certain sources that avaliable at the time. And in support of Blofeld's comment, quality not quantity. ] (]) 13:56, 22 July 2011 (UTC)
*'''Oppose'''. We've considered this many times before; read what I wrote then. ] (]) 19:50, 22 July 2011 (UTC)

*'''Support''' as someone said above 1500 is little more than a stub. ] (]) 15:50, 23 July 2011 (UTC)

=== blame game (or some nicer name for it) ===
Picking out one of SandyGeorgia's ideas, "if an already approved hook has to be rejected, then that nominator can't put up another DYK for a month, and that reviewer can't approve a hook for another month" - what is wrong with this suggestion, even separately to any other change? (I would change it to the reviewer being prevented from approving hooks ''or'' nominating them, since the current QPQ system means that one reason for doing a rushed review might be that they want to get their own nomination on the main page fast.) --] (]) 16:39, 21 July 2011 (UTC)

:Demiurge by your own admission, the current fiasco was created by a "novice". Don't worry I won't come around here again. You don't need to add more instruction creep to ensure that. ] (]) 17:31, 21 July 2011 (UTC)

::A variation of what Demiurge proposes seems reasonable to me, though I'd suggest adding more room for discretion to account for new users making mistakes. In my first weeks on DYK, I approved two hooks that were later changed to requested revisions for minor causes, and also rejected one hook that an admin overturned as okay; I was doing my best, but just missed some of the less-emphasized criteria. Since DYK is a more likely starting point for new editors than other projects, I don't want to slap them down too hard or make them feel unwelcome.<br>Still, I could name 2 or 3 regular DYK contributors who appear to give incomplete reviews that I've seen repeatedly overturned by other editors, sometimes just putting the check icon without even a word. DYK doesn't seem to have a system to deal with that yet, but I think it's reasonable to ask these reviewers to be more thorough, and if necessary, to ask them to take a break for a bit. -- ] (]) 18:27, 21 July 2011 (UTC)

:::(ec)I think some version of Demiurge's accountability idea would be good, though I personally think a week would be better. A penalty too stiff will just spawn meatpuppet nominations. Hey, TK, you probably did us a favor by coming in as a relative novice and making an innocent error that somebody else should have picked up and set right. It was generous and helpful, the way you stepped up and explained your process, so that we could look for ways to improve. And apparently your skills in other areas picked up a couple of copyvio problems somebody else might have missed. What happened was a mistake in adhering to DYK's own rule, not a violation of BLP policy and certainly not a scandal or a fiasco. It resulted in an Error on the Main Page, and we are trying to figure out more and better ways to prevent such. Driving away a conscientious, intelligent reviewer like TK is '''not''' something anyone wants. <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 18:35, 21 July 2011 (UTC)

::::Indeed not - I certainly don't. And this proposal wouldn't be retrospective anyway. The implementation of this challenge has helped fix some copyvio issues and also resulted in . That's not instruction creep, that's (a bit of) progress in the right direction.

::::A week sounds a bit short to me... some problematic nominators/reviewers might only do one article a week or less anyway. How about two weeks? --] (]) 18:49, 21 July 2011 (UTC)
:::::I've not yet thought about this proposal enough to support or oppose it, but if such a proposal is to be enacted, I'd suggest that a month is probably the right length. I'll agree that it's probably reasonable to (somehow) penalize a "reviewer" who fails to give a thorough review. It might be reasonable to penalize a nominator who nominates an unusable (rejected -- whether initially or after a erroneous approval) article/hook, though I think ] should be made in the case of a suitable article with an unsuitable hook nomination (as in the recent case that sparked the discussion) and particularly in the case of new-to-DYK nominators. On the other hand, experienced DYK nominators (not going to name names here, but I'm sure most regulars can think of a few) who ''regularly'' submit unsuitable articles, especially when it's the same problem repeatedly, should be given very little slack. ] (]) 19:23, 21 July 2011 (UTC)
:*This is quite a storm I seem to have inadvertently caused. I '''do not support''' an extended limit. However, if possible we should add another rule for somewhat negative hooks, roughly reading "any hook fact that can be construed as a negative should be cited in at least two ]. Hopefully that can avoid most problems of a similar nature. ] (]) 01:01, 22 July 2011 (UTC)

Imposing timeouts for reviewers will be quite ineffective since they will leave their articles in their sandbox and then just submit them at the end of the timout. I guess what we could do, if a QPQ review gets pulled from the queue for some reason, is to scrap the reviewer's accompanying submission. It would be harsh, but would I think be a very effective way of ensuring that QPQ reviews were thorough. We might need to outline the precise conditions under which a submission is scrapped however, which could be a little tricky. ] (]) 02:33, 22 July 2011 (UTC)
:That would be interesting, but perhaps difficult to implement. It is a rare event that a hook gets pulled back from the queues, AFAIK. Even being pulled back from Prep isn't that common an occurrence. I have a question though: what should we do if the hook is pulled back from the queue or prep due to a problem that could not reasonably be foreseen, such as the lizard hook currently scheduled for August 9? ] (]) 03:41, 22 July 2011 (UTC)

:: Yes, I know, that's why I said it would be difficult to come up with a clear criteria. I'm not sure it would actually be practical, it's just something to think about. ] (]) 07:00, 22 July 2011 (UTC)

::dunno, I think this proposal comes over as quite heavy :( no easy answers though. ] (] '''·''' ]) 04:29, 22 July 2011 (UTC)

== Some thoughts from a semi-regular ==

#The somewhat enforceable request for an interesting hook encourages sensationalism.
#A raise in the character limit will lead to more padding and chattiness---not to better, or <s>even less</s> fewer, submissions. {{Done}} <small>This is an argument in favor of the status quo. ] (]) 14:29, 22 July 2011 (UTC)</small>
#The request for reviews ("QPQ" reviewing) was a bad idea. We tried it, it did not work, we should scrap it again.
#To "ban" editors or reviewers for a period of time will not work: Who's going to check this with 40-odd submissions per day? {{Done}} <small>This is an argument in favor of the status quo. ] (]) 14:29, 22 July 2011 (UTC)</small>
#The mose basic of all rules is missing: That the hook ref must be a reliable, independent source. {{done}} Issue #5 is solved. --] (]) 13:56, 22 July 2011 (UTC)

Suggestion: Implement a subset of ] without a minimal length and with a drastically reduced request for comprehensiveness. Then run one hook set per day. --] (]) 19:49, 21 July 2011 (UTC)

*According to the guideline ], ''Articles should be based on reliable, third-party, published sources with a reputation for fact-checking and accuracy.'' This applies to ''everything'' on Misplaced Pages, so I figured that it would go without repeating, but since you mention it, I've added that in appropriate places to the DYK rules, with a piped link to that guideline. ] (]) 20:15, 21 July 2011 (UTC)
::Pgallert's words are some of the most eminently sensible I've seen on this site for some time. Support. ] (]) 20:24, 21 July 2011 (UTC)
:::Thank you for the kind words, Ghmyrtle. --] (]) 20:59, 21 July 2011 (UTC)
::cmadler, the ''articles'' must indeed be based on reliable sources, but the ''hook fact'' need not, according to current standards of reviewing. In fact, for the DYK hook often the shadiest of all article sources is employed because that one allows the most surprising hook. --] (]) 20:59, 21 July 2011 (UTC)
:::The hook citation ''must'' be in the article, and therefore it is subject to the same strictures as articles. It may be that this has not been regularly enforced or investigated before a nomination made it to the Main Page, but that does not mean the stricture does not apply. It does. --] (]) 21:05, 21 July 2011 (UTC)
::::Sorry to disagree. Articles may contain unreliable (for instance self-published) sources, as long as notability is not derived from them. Articles must be ''based'' on reliable sources, not ''exclusively employ'' them. The problem is that nothing in the DYK rules forbids editors to pick this very reference to build a hook. --] (]) 21:17, 21 July 2011 (UTC)
:::::You need to read the rest of the opening sentence of that policy: ..."and, all majority and significant minority views that appear in these sources should be covered by these articles". Since a sensational DYK hook is either a majority opinion or significant as a minority opinion, its citation is covered by this policy. --] (]) 21:54, 21 July 2011 (UTC)
::::::... or at least, we can infer that. So Pgallert is right, we need to add more rulecreep to make that explicit. --] (]) 22:09, 21 July 2011 (UTC)
:::::::Either way, this is something many (most?) of us have been enforcing already, such as in cases where a place-article's hook comes only from a travel website. So, I would see an emendation to "Da Rules" more as a codification of existing practice, in order to make the point explicit (and easier to justify to nominators), than as rulecreep (which carries a pejorative connotation). --] (]) 22:22, 21 July 2011 (UTC)

:::::::: We don't need to change the rules in this regard. Of course hooks must be reliably sourced - reviewers shouldn't need to be reminded of such basic principles, if they do, they shouldn't be reviewing. AFAIK this has not been raised as a problem in any case. ] (]) 01:58, 22 July 2011 (UTC)
:::::::::The fact that they shouldn't ''need to be'' reminded doesn't mean that they ''shouldn't'' be reminded. Better to be safe than sorry, particularly with "over-enthusiastic" reviewers. ] (]) 08:52, 22 July 2011 (UTC)

:::::::::: It's instruction creep - in this case, completely redundant instruction creep since it's just a reiteration of a core[REDACTED] policy. And I don't believe it will have the slightest effect on the quality of reviews. ] (]) 09:15, 22 July 2011 (UTC)
::::::Almost whenever you see a hook in the form "A said X", someone has violated that principle. Currently for instance {{T:TDYK|Sam Johnson (New Zealand)}} where all hooks are sourced with (1) a commentary and (2) a University press release. None of the hooks received a tick so far but the discussion is not about reliable sources. Already okayed is {{T:TDYK|Hunter Greene}}, the independence of the reference is not apparent to me. See also {{T:TDYK|George McGavin}} where a reviewer just argues in the direction that hook refs need not be reliable and independent. This is what I found in 15 minutes on a very slow Internet connection; I bet 1000 major edits that there are more in the current set of submissions, and I remember a variety of cases from the past. This is not an isolated incident. --] (]) 10:03, 22 July 2011 (UTC)

::::::::Greene and McGavin look problematic to me too; ] ] (]) 13:28, 22 July 2011 (UTC)
:::::::::I wanted to explain that DYK in general operates like this, to an extent that editors specifically argue that a reliable source is not necessary for a DYK hook. Your addition to the rules solved the problem, see a few posts below. --] (]) 13:41, 22 July 2011 (UTC)
::::::::::I'm concerned that when you read the comments that raised the problem of reliability of citations for {{T:TDYK|George McGavin}}, you re-interpreted those comments as meaning "that hook refs need not be reliable". That's the ''opposite'' of what the comments are saying. --] (]) 14:05, 22 July 2011 (UTC)
:::::::::::Well-intentioned editors often disagree about what constitutes a suitably reliable source in a given situation (as in the case above, where it's a question of whether a self-published source is acceptable -- and remember that sometimes it is), but I don't recall anyone ever suggesting that a reliable source is unneeded. ] (]) 14:42, 22 July 2011 (UTC)
::::::: Quite frankly, I'm struggling to understand what it is exactly that you are proposing. Our current rules state (I quote):

::::::: ''The hook fact <u>must be cited</u> in the article with an ''']''' to a ], since inline citations are used to support specific statements in an article. The hook fact must have an inline citation right after it, since the fact is an extraordinary claim; citing the hook fact at the end of the paragraph is not acceptable.''

::::::: That seems to me to explain the requirement quite clearly. What do you think is missing? ] (]) 10:56, 22 July 2011 (UTC)
::::::::<small>FYI, I just added "to a reliable source" to that rule yesterday afternoon. ] (]) 12:54, 22 July 2011 (UTC)</small>
:::::::::After that addition my point 5 is solved, thank you. I just wasn't sure that this change of rules would stick but judging from the discussion elsewhere on this page I guess it has consensus. Somehow I feel this is a fundamental change that should be published somehow. --] (]) 13:42, 22 July 2011 (UTC)

::::::::: That's odd, I'm sure I checked the history to see when that clause had been added and didn't see any recent changes - possibly it was one of those occasions when the history page lags behind the actual edit. Anyway, I thoroughly approve of your change cmadler :) ] (]) 14:14, 22 July 2011 (UTC)

It's more than a wee bit appalling that anyone working at an area that puts content on the main page doesn't know that all Misplaced Pages content needs to be cited to reliable sources, much less what a reliable source is, but I'm more troubled that Gatoclass claims this discussion has not been about reliable sources, when in fact I pointed out early on that a failure to use reliable sources, and misrepresentation of sources, was as prevalent in hooks as plagiarism and BLP bios are, and I have in fact indicated one in this very discussion that uses a non-reliable source. Is there no sense of decency here? I suppose my alarm is just continuing to fall on tone deaf ears. ] (]) 16:40, 22 July 2011 (UTC)

: You have misinterpreted my comments - I didn't mean reliable sources are not an issue, I meant no-one had suggested merely rewording our instructions as a solution. As for the fact that some unreliable sources might be used - as long as the bulk of the article is reliably sourced, and the questionably sourced content is not controversial, I am not necessarily going to make an issue of that. Again, this is not GA, it's DYK, we don't have a week to spend on every article, we aim at ensuring there are no major defects, we don't have the time or resources to address every minor detail. ] (]) 17:41, 22 July 2011 (UTC)

:: Thank you for the clarification-- that helps. I do find it astounding that we have to mention anywhere at any time that *all* Misplaced Pages content should be cited to reliable sources. But the bigger problem that is emerging at DYK is that you are putting BLPs sourced to non-reliable sources on the main page, and you continue to do that today, with editors who are known not to understand sourcing. If you don't have the time and resources to assure that you aren't putting egregiously bad articles on the mainpage, you should not be putting anything on the mainpage. GA has better quality control, and we no longer need to encourage article creation, particularly when so many of those articles created are just messes someone else needs to clean up, and we no longer have enough editors to clean up these messes. Let's encourage quality content improvements, not the kind of stuff DYK runs on the mainpage, hoping someone else will bring them to Misplaced Pages standards, not to mention standards of human decency. ] (]) 22:15, 22 July 2011 (UTC)


== Back to 24 hours? ==
::: So, will you be actually helping here, or merely criticizing the volunteers who do the actual work? Have you ''ever'' looked at the Queue for problems ''before'' they went up on the Main Page, or do you wait for them to appear on the Main Page ''first'' and then come here to complain? There is a Queue where hooks are placed in advance of appearing on the Main Page, and you can help spot problems ''before'' they appear on the Main Page (which would be helpful), or you can sit back and just complain (which is ''un''helpful). Instead of telling the volunteers what to do, why not actually pitch in and ''show'' us how to do it? --] (]) 02:48, 23 July 2011 (UTC)


{{DYK admins}} As of this moment, we've got five filled queues. If we can fill another two queues before midnight UTC (eight hours from now), we'll keep running 12 hour updates for another three days. Otherwise we're back to 24. ] ] 16:06, 2 January 2025 (UTC)
:::: That you have to ask those questions shows that you aren't paying attention. Perhaps you weren't around DYK last Halloween, or perhaps you aren't familiar with how often I tried to help and how often the denialists scream when I do? Please do your homework before making statements about me-- the delightful thing about Misplaced Pages is that it's all there in history. Including the fact that no matter how many times I looked *before* articles ran, you still ran them, just exactly as you are still running articles from a serial offender. No accountability, and yet, what, you want me to do your work for you? Fix your process-- it's broken. Soooo ... in addition to rampant plagiarism and close paraphrasing, and BLP vios, we have numerous DYKs built extensively on non-reliable sources. So, if you must have a minimum expansion and size, how can you verify that criteria are met without looking at whether articles are reliably sourced? So, anyone can put any ole crap on a page and get a DYK, and then you expect *real* editors to come along later and clean up the mess? How is this helping Misplaced Pages? You still have Quid Pro Quo reviewing-- nominators who may know little to nothing of Misplaced Pages policies reviewing nominations from other nominators who may know even less. What are you all doing about the systemic problems here, other than complaining that I'm complaining about it? ] (]) 02:58, 23 July 2011 (UTC)


:I've promoted one more, but don't think I'll have time for the last one. &spades;]&spades; ] 21:50, 2 January 2025 (UTC)
::::: I did in fact look at your recent edit history. I'm sorry that I didn't realize I'd have to go all the way to last October (9 months ago) to find your participation. Such an absence strongly suggests abandonment. You do seem to have a lot of time in recent days to point out flaws and to spot mistakes ''after'' they happen, but in the recent weeks and months have not worked to prevent the problems you're pointing out. This creates a self-fulfilling phophecy. You haven't worked to prevent the problems, because if you do, then you won't be able to complain about them afterwords. The biggest problem right now with DYK (and always) is that there aren't enough people taking the initiative to review nominations. If people actually did that, in a timely fashion, we wouldn't need to wrangle about all the other issues.
::Thanks. I'm working on ] right now, so we're good to keep going until 0000 6 Jan UTC. ] ] 22:03, 2 January 2025 (UTC)
:::And somebody needs to back-fill the holes that got left in ] after various yankings. ] ] 22:04, 2 January 2025 (UTC)
::::{{dykadmins}} just to make sure everybody is aware, we're going to extend 12-hour mode (at least) another 3 days now that we have 7 full queues. We do have quite a backlog to dig out of. By my count, we've got 165 approved hooks, and there's another GAN review drive that just started so I expect another big influx of nominations. I expect it'll take us several more 3-day sprints to get back to normal and it'll be less disruptive to keep them going back-to-back vs flitting back and forth between modes. ] ] 22:28, 2 January 2025 (UTC)
:::::So long as queue 3 is filled by midnight and the two date requests in queues 4 and 5 are suitably kicked back, I have no valid objections.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 22:38, 2 January 2025 (UTC)
::::::I filled one of the holes in queue 3. ] ] 23:11, 2 January 2025 (UTC)
::::::I'm getting confused as to where the SOHA hooks need to go; anyone able to get their head around it? ] (]) 13:11, 3 January 2025 (UTC)
:::::::5 and 6 January, but they're already there. Brain fog is brain fogging, clearly.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 13:31, 3 January 2025 (UTC)
::::::::As a reminder, ] says {{tq|The reviewer must approve the special occasion request, but prep builders and admins are not bound by the reviewer's approval}}. The relevance to this discussion is that keeping the queues running smoothly is a higher priority than satisfying special date requests. I'm all for people putting in the extra effort shuffling hooks around to satisfy SOHA requests, but we can't let "perfect" get in the way of "good enough". It would have been a mistake to force a change to the update schedule because of SOHA. ] ] 14:32, 3 January 2025 (UTC)
===5 January===
We need one more queue to get filled in the next 8 hours to keep going with 12 hour mode ] ] 16:20, 5 January 2025 (UTC)
:I can take the next one if no-one else does in the next five hours. I'd need more eyes on the Tyler hook though.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 16:36, 5 January 2025 (UTC)
::Doing, although Glucoboy in prep 6 looks interesting and I might swap it and Tyler to avoid outsourcing. I'll make that decision after in nine articles' time.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 21:43, 5 January 2025 (UTC)
:::Another six sets of 12 hour mode it is.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 00:03, 6 January 2025 (UTC)


===8 January===
::::: And what have I been doing? I've been reviewing articles, pointing out uncited hooks, encouraging explicit citations, and contributing to the project. The DYK is a developmental effort that points new editors towards the standards of Misplaced Pages through interactive education. GA and FA processes only deal with elitist advanced editors. --] (]) 09:16, 23 July 2011 (UTC)
{{dykadmins}} We've got about 10 hours left in the current sprint. There's only 4 queues filled right now; unless we get 3 more filled today, we'll go back to 24 hour sets at 0000Z. By my count, we've currently got 156 approved hooks, and there's still that GA backlog drive going on, so I would expect another influx of nominations from that. ] ] 14:47, 8 January 2025 (UTC)
:I see you and {{yo|Hilst}} have queues 1 and 2 in hand. If no-one else does prep 3 in the next four hours, I'll take it.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 17:40, 8 January 2025 (UTC)
::I took it. Next decision to be made on 11 January. ] (]) 18:00, 8 January 2025 (UTC)


===11 January===
:I have avoided this conversation for the past few days but I do have to throw in that I agree with Sandy and others about QPQ reviewing being a problem. Granted, it was implemented to solve another problem (and I feel partially responsible for it, because last year during the DYK plagiarism ruckus I remember complaining about editors who nominate tons of articles and never review, although I didn't personally propose QPQ), but it hasn't solved that problem (the backlog is still as long as always) and it has created new problems (crappy reviews). We should just get rid of QPQ and go back to the way things were before: an understanding, similar to at ], that if you nominate it would be nice to offset your nomination by also reviewing, but that it's not required. Forced reviews from people who don't want to be doing them are not worth the trouble they cause. <b class="IPA">]</b>&nbsp;(]) 03:05, 23 July 2011 (UTC)
{{dykadmins}} we're down to 127 approved hooks, which is great progress, but still above the threshold for another sprint if we can get 4 queues filled in the next 8 hours. ] ] 15:51, 11 January 2025 (UTC)
:: Eliminating the QPQ would be a good start, but wouldn't solve all of the problems here. Some seem to think that mainpage exposure is a right, and that it's up to others to solve DYK's problems. An experienced Wikipedian came over here because she was challenged to help here, reviewed a hook, found numerous problems, got them corrected, and then some DYK regular came along and ran a *different* hook because it was splashier, and then three DYK regulars up the line missed that it violated UNDUE. So, these challenges to just get in here and help make no sense-- the process is broken, has been for as long as I've been editing, and the *process* needs adjustment, since there will be another new crop of regulars in here three months from now who don't know the history of DYK. It is not up to others to solve DYK's problems-- if DYK won't solve them, they should not be on the mainpage. ] (]) 03:20, 23 July 2011 (UTC)
:I'll take the next one.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 15:59, 11 January 2025 (UTC)
:::Well Sandy, that's not right, as I already explained above. I'm not quite sure why you keep repeating that inaccuracy, when TK has certainly made no attempt at any such pretence. There were two hooks for that nomination when TK came to do the review, and TK put their review underneath the second hook. TK did not specify which hook they were approving. The principal responsibility lies with the admin picking the hook and putting it in a queue (that's why only admins can do it...), but repeating yourself over and over in an attempt to re-write the facts of the incident according to your taste, makes your case weaker, not stronger. --] (]) 03:33, 23 July 2011 (UTC)
::{{yo|RoySmith}} I've queued prep 6 and can probably do prep 1 this evening.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 17:39, 11 January 2025 (UTC)
:::: I keep repeating it because it is right. TK did not review the alt hook becuase she didn't know she was supposed to (the process here is too complex), and the discussion at the thread makes it abundantly clear even to an idiot like me that she did not review the second hook. ] (]) 13:48, 23 July 2011 (UTC)
:::I did 7 (which, by the way, was totally clean, which made it easy). ] ] 18:22, 11 January 2025 (UTC)
::::::Demiurge, you've been trying mighty hard to blame this on me. You know and I know that you challenged me to review a DYK for copyvio or plagiarism (which you seem to believe doesn't exist). I accepted your challenge and found problems. I did not comment on the hook. Although I don't have them displayed on my page, I've had plenty of DYKs and reviewed plenty of them. Usually the alt hook is exactly that: an ''alternative''. I didn't comment because it didn't seem necessary; the ''primary'' hook was fine, except I didn't actually check the wording of the hook and if I had I would have found it too was plagiarized. In the future if you want to throw stones please come to my page to do so. Thanks. 13:59, 23 July 2011 (UTC)
::::I'll take 1 once I've cooked.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:00, 11 January 2025 (UTC)
:::::::Wait, what? So now you're saying that the reason you messed up the review was that you were focused on trying to prove wrong a belief that I don't hold but you'd decided to ascribe to me? Wow.
:::::Doing now.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 20:06, 11 January 2025 (UTC)
::::::And the last one's all yours.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 21:42, 11 January 2025 (UTC)
:::::::I'm assuming somebody else will step up. This is a team effort. ] ] 22:04, 11 January 2025 (UTC)
::::::::Sorry, would do but am annoyingly indisposed. ] (]) 23:51, 11 January 2025 (UTC)
:::::::::Someone needs to update ] as it's protected.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 00:11, 12 January 2025 (UTC)
::::::::::OK, I've put us back to 24 hour mode. I think this was the first time we've tried the "3 day sprint" thing and from what I can see, it worked well. We ran for 12 days, knocked the backlog down from (I think) 165 to 128, and always knew where we were. No more panic when the queues ran down to empty. So, good job everybody. I haven't been keeping careful track, but I think Launchballer probably gets the prize for most sets promoted to queue during this.
::::::::::My guess is we'll need to run some more sprints in the near future as the GA review drive throws more work our way. But for now, we get to stand down and get some more rest. ] ] 00:53, 12 January 2025 (UTC)
We are now back to a significant backlog. ] (]) 02:07, 17 January 2025 (UTC)
:@] We need more {{dykadmins}} to keep the queues filled, and then we could go back to 12 hour sets. If you're willing to help out in that department, I'd be happy to nominate you for ]. Or, if you prefer, I could just give you ]. ] ] 02:37, 17 January 2025 (UTC)
::{{u|RoySmith}} I thought that I needed to meet "The editor should have made at least 150 total edits to the Template and Module namespaces." for TPE. We also don't have that many prep builders so I wouldn't want to stop helping fill preps just so that I could promote them to queues. ] (]) 02:41, 17 January 2025 (UTC)
::I see now that template namespace also refers to DYK nominations. I should have figured. ] (]) 02:59, 17 January 2025 (UTC)
:::Just for the record, I've granted ] to {{u|SL93}}. It'll be good to have more hands working the queues! ] ] 15:40, 17 January 2025 (UTC)
::::I hit something of a wall last week after attempting two in a day, but I plan on resuming in the next couple of days.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 17:24, 17 January 2025 (UTC)
::::Thank you. I do have one question about moving a prep to queue. For example, I promoted two hooks that are in prep 2. Could I still promote those two hooks to a queue and leave a note on the DYK talk page for someone else to check over it? I wouldn't want to promote prep 7 or prep 1 because I filled those preps by myself, but I'm curious about if only a small amount of the hooks were promoted by me. ] (]) 17:45, 17 January 2025 (UTC)
:::::I used to do both preps and queues, and often found myself in this kind of dilemma, so I decided to mostly work one side of the street. But, yeah, when I promote a set to a queue where I've had hands on one or two of the hooks, I'll post a request here for somebody else to look at those. ] (]) 18:08, 17 January 2025 (UTC)
::::::{{u|RoySmith}} I listed ] under the section Prep 2 to have someone look over the article because I promoted it to prep. I wonder if using the @DYK admins template would be acceptable in such a case. ] (]) 02:16, 18 January 2025 (UTC)
:::::::I don't usually bother with the {{t|dykadmins}}, but it can't hurt. ] ] 02:50, 18 January 2025 (UTC)
::::{{like}}. Welcome aboard! —] (]) 08:42, 18 January 2025 (UTC)
===18 January===
If someone can queue Prep 2, we can go to 12-hour backlog mode tomorrow. ] (]) 13:32, 18 January 2025 (UTC)


:::::::How many other DYK reviews have you done? What was the focus of those? Something similar? --] (]) 16:31, 23 July 2011 (UTC) :Queued, currently finishing checks. —] (]) 16:53, 18 January 2025 (UTC)
::12-hour mode should be activated between midnight and 12:00 noon UTC tomorrow. If nobody has done it by then, I'll flip the switch after I wake up tomorrow. —] (]) 17:25, 18 January 2025 (UTC)
:::(ec, re Sandy) I wonder if it would help if the project regularly appointed a "director", something along the lines of what Raul is for TFA, who is expected to personally review all hooks before they go up? Right now the project has several experienced editors like Gatoclass, but they're not necessarily able to be involved all the time (or, like me, have more or less lost interest), and thus much of the grunt work is done by inexperienced editors, since DYK has a high turnover (it gets boring quickly). It might be better if there were someone who agreed to check every queue before it went up, for a year or something like that, and who knew that that was his/her responsibility. I think it would not actually be a huge job (assuming people get the queues prepared beforehand, the "director" could check all the queues once per day and just reject hooks that are inappropriate, without necessarily having to spend a whole lot of his/her own time trying to figure out how to fix them). Such a "director" should probably not be able to reject hooks based on boringness in this capacity (although he/she could still comment on boringness at T:TDYK like any other reviewer), since it's too subjective, but any experienced editor in this position would be able to keep hooks with, e.g., BLP problems from making it to the main page. (Catching plagiarism is a much bigger task, though, since it requires much more reading, and would be too much or one person to do on a daily basis like this.) <b class="IPA">]</b>&nbsp;(]) 03:36, 23 July 2011 (UTC)
:::The instructions say {{tq|For a variety of technical reasons, you should only make a change shortly after midnight UTC}}. I've always assumed that means "sometime before noon", but I'be never been quite sure if there's not more to it than that. ] ] 17:30, 18 January 2025 (UTC)
:::: I have always advocated that DYK (and GA as well) should have some sort of directorate or clearing panel-- someone responsible when a debacle occurs. FAC put plagiarism on the mainpage once: I (we) did something about it. I would expect to be "fired" if we didn't. But I would strongly oppose putting Gatoclass in any position of DYK responsibility-- he doesn't see the issues, and didn't even a year or so ago. The notion that those of us who think DYK does a huge disservice to the main page are supposed to dig in and review, in a faulty process, is absurd. If I disagree with any corrupt, inept political system, does that mean I should join their party to change them from within? How silly. Those of you who participate here and know you are putting plagiarism, BLP vios, incorrectly sourced articles, and plagiarism on the mainpage are responsible to stop it. The problem seems to be that so many of the regulars here don't know verbatim copying and poor sourcing even when it's put right under their noses, hence have no business writing anywhere on Wikpedia, much less putting content on the mainpage. I haven't looked at the new proposals added here-- there are 144 posts since I last read here-- will go there next. ] (]) 13:48, 23 July 2011 (UTC)
::::I am not sure when the bot does its runs to update ], whether that depends on update frequency and how long it takes for the bot to notice a change in updates per day, but I don't really think anything will break if we change the time between updates in the late UTC morning. I wouldn't flip the switch at 11:55, but 8:30 should be pretty safe. —] (]) 17:49, 18 January 2025 (UTC)
:::::The ] was a few minutes after midnight. I must have caught it in mid-update and confused something because as soon as I saved it, I got the "Oh no, all queues are empty!" warning box (which tankfully turned into something more encouraging shortly after). ] ] 18:21, 18 January 2025 (UTC)


A friendly reminder that the lead hook of ] is a special occasion hook that is supposed to run on 26 January. It will have to moved soon: if we don't continue twice a day on 22 January, then it will have to go into ]. If we do continue, then it would need to end up in ] if we don't again continue on 25 January, or ] if we continue twice a day on 25 January as well. The key, of course, is to get it out of Queue 3. Thanks. ] (]) 21:39, 20 January 2025 (UTC)
:: (Edit conflict): QPQ wasn't introduced to help with the backlog but to relieve the workload on the handful of users who were doing all the reviewing. And on that score, it's actually made a huge difference, there are currently 205 articles at T:TDYK and almost half of them are verified. Before QPQ, it was not unusual to have less than a dozen hooks verified - sometimes not even enough to create an update.
:{{u|BlueMoonset}} I took care of it. However, the new first hook in Queue 3 will need to be reviewed by someone else because I promoted it to prep. {{Template:DYK admins}} ] (]) 18:07, 21 January 2025 (UTC)
::{{done}}. The ] hook and article look OK to me. &nbsp;&mdash;&nbsp;] (]) 18:20, 21 January 2025 (UTC)


== 10 hook sets? ==
:: If a problem has arisen it is that those people who used to make the effort to do the reviewing have not used the extra time available to do other things at DYK - they've just cut the time they spend at DYK instead. Which means less oversight on the project overall. So I think it's premature to start talking about dumping QPQ. If we are going to make changes, IMO we should start by looking to improve the oversight at the Prep level. I suggested a method of doing so earlier, by making admins involved in moving updates from Prep to the Queue more accountable. Right now, the move is often treated as nothing more than a mechanical process instead of being also an editorial one. So if there's a perception that standards at DYK have slipped, I think that would be the place to start. ] (]) 04:00, 23 July 2011 (UTC)


We switched to 9 hooks per set a while ago. That has certainly kept us closer to keeping up with nominations, but we're still falling behind and having to run in 12-hour mode once in a while to keep up. I suggest we try 10 hooks per set and see how that goes. ] ] 01:12, 12 January 2025 (UTC)
:::I agree that a combination of what Gato proposes here and what Tony proposes below would create a better sense of accountability. -- ] (]) 04:12, 23 July 2011 (UTC)
:Not worth it. The current rate will even out over time. ] (]) 01:27, 12 January 2025 (UTC)
:I'm not sure if one extra hook per set will help much if at all. I do think that more prep builders would help. ] (]) 01:29, 12 January 2025 (UTC)
:I do not mind going to 10 hooks a set. If we start running out, we can always return to 9-a-set at a later date. ] (]) 03:14, 13 January 2025 (UTC)
: Nine is already more than enough IMO. Apart from the extra work required in verifying a 10-hook set, it becomes much harder not to repeat topics with longer sets, and longer sets just tend to look cluttered. 12-hour mode has long been a staple of DYK anyhow and one extra hook per set is not going to change that. ] (]) 12:32, 15 January 2025 (UTC)
:I think we're getting to the point where DYK is at risk of getting so long that hooks won't get the attention they deserve. I'd rather not move to 10 unless the overall backlog situation gets worse. —] (]) 12:42, 15 January 2025 (UTC)


== ] ==
== Two fold expansion ==


===] (])===
Would I get a two-fold expansion DYK credit if a 650-character article has one ref in the text but no refs needed BLP tags?--] <small>(]/]/]/]/]) </small> 14:10, 22 July 2011 (UTC)
{{ping|Locust member|Phibeatrice|SL93}} the hook says that the breakup was the only inspiration for the album, but both the lead and body say that it was also inspired by friendships and family. Surely the hook will need rewriting to match the article? ] (]) 11:28, 17 January 2025 (UTC)
:The two-fold expansion rule is for ''unreferenced BLPs''. If it has one reference already, it does not quality. ] (]) 14:20, 22 July 2011 (UTC)


:The hook doesn’t use the word “only” or “inspired”. The hook is “… that Gracie Abrams wrote Good Riddance about her breakup from her former collaborator and boyfriend, Blake Slatkin” and that is what the song is about. ] (]) 12:04, 17 January 2025 (UTC)
== Prep areas need filling ==
:I did not include the word "only" in the hook; I used Slatkin for the hook since it is much more interesting to know an album was written about her ex boyfriend and former collaborator (a notable person) than just friendships and family. ] (]) 12:37, 17 January 2025 (UTC)
:As others have stated, the hooks don’t use the word “only”—and if we’re talking about the insinuation of “only” given that the hooks omit mention of other inspirations, I don’t feel compelled by that either. I believe the hooks are fine as they are in this regard. ] (]) 15:39, 17 January 2025 (UTC)


===] (])===
I have nearly finished prep area 4 but really need to do stuff elsewhere. So folks, fill away...] (] '''·''' ]) 14:33, 22 July 2011 (UTC)
{{ping|Spiderpig662}} I wonder if it's worth including the factoid that she only stopped because she couldn't get her foot over the back of her neck. I can't do that and I'm around 20% as old as she was! ] (]) 11:28, 17 January 2025 (UTC)
:Thanks folks. Now to get an admin on commons to protect the prep images. Will ask posthaste. ] (] '''·''' ]) 23:01, 22 July 2011 (UTC)
: {{replyto|AirshipJungleman29}} That might be a good idea. Would a consensus be needed before that was added to the hook? ] (]) 17:21, 18 January 2025 (UTC)
:Just now. ] (] '''·''' ]) 23:08, 22 July 2011 (UTC)


===] (])===
== Nom deleted without discussion? ==
{{ping|AlphaBetaGamma|Viriditas|Lajmmoore|SL93}} I can't read Japanese, so are we ''really'' sure this meets ]? ] (]) 11:28, 17 January 2025 (UTC)


:I would hope so after the long discussion. ] (]) 11:59, 17 January 2025 (UTC)
I assume this was an accident, but my nom, ] under July 19 was deleted today (see ) without any discussion. The edit summary says "need source" and although the edit summary says "Wittorf affair, the comment is made for the nom following it, ] and Wittorf affair is simply deleted, section header and all. It being DYK, I would rather not just restore it myself and am not sure if that would be appropriate anyway. I would appreciate someone restoring the nom. Thanks in advance. ] (]) 21:02, 22 July 2011 (UTC)
::Looking the title up in Japanese brings up of hits.
:I guess that was an accident and tried to restore it, please check, --] (]) 21:15, 22 July 2011 (UTC)
::Following sources use the subject in its title:
::] <small> (]) </small> 23:30, 17 January 2025 (UTC)
:::AirshipJungleman29 asks a good and needed question. ABG, I think your sourcing is pretty poor, but the search results you provide show that the term has currency in Japan, particularly in the car industry and related niche sites, so much so, so that it appears that many of your cited sources are in part, a response from the car industry to the trend. So with that said, I think it's clear the term has currency in Japan. There's also the related and associated legal case(s) and general phenomenon of elderly drivers and unintended acceleration (usually involving a Prius) that appears in many related articles, scholarly journals, and news articles. The problem AirshipJungleman29 poses then becomes a bit narrower in terms of Misplaced Pages. In other words, while the phenomenon and term can be said to exist and are in use, do the sources meet the criteria for inclusion (in other words NEOLOGISM)? The article by Yoshitaka Kimura that you cite, which appears to be an article in an auto industry news site known as "Mediavague" (which I think might be funded by the auto industry to promote their products), argues that the term has been in use since at least early 2019, which establishes that it was a problem for Toyota, and was very real and threatened their business. I think this meets the RS criteria, and it reads as a kind of industry hybrid between ] and ]. Your second link also mentions the Prius Missile but is more of a used car site run by Nextage. I'm not convinced this is a great RS, but we have a lot of others to choose from based on your search results. From there, I see a link to an article by MOTA, which is a car industry trade group, again, likely trying to dispel the internet slang which could harm Toyota's brand. Moving on, I see an interesting blog post about the phenomenon with some detail over "Creative Trends", but I don't think this meets RS. On the other hand, I see an article about the Prius Missile by jidounten lab, which appears to be a respected, reliable auto and tech journalism site. I also see a BuzzFeed Japan article about the term in your results. I think the problem here is that the sources in the current Misplaced Pages article, while accurate, might need to have better sources added, which I can clearly see in your google search results. ] (]) 00:24, 18 January 2025 (UTC)
::::<small>My horrible attention span may have caused me to misunderstand some parts.</small> I got lost on the last part, were you referring to links in the article or the previous message I sent here? I know it's an annoying question... ] <small> (]) </small> 10:57, 18 January 2025 (UTC)
:::::It’s really simple. Use the best sources you can find. ] (]) 11:41, 18 January 2025 (UTC)
::::::I think what Viriditas is saying @] is that you should add some of the other sources (that are reliable) from the google search you linked, into the article since they are missing. ] (]) 18:24, 19 January 2025 (UTC)
:::::::I replaced two sources that seem weird. I don't remember citing blogs in this article so I'm confused. ] <small> (]) </small> 05:05, 20 January 2025 (UTC)


== ] ==
== Freddie Mitchell in queue 4 ==


==='']''===
I'd like a second opinion on the Freddie Mitchell hook in queue 4. It asserts that Mitchell "received racially threatening hate mail in 2003, apparently due to his appearance on a reality television show, A Dating Story?" This doesn't sound correct linguistically. While the hate mail appears to have been "racially motivated," I don't think it's correct to call it "racially threatening." I think the word "racially" should be stricken, or changed to "racially motivated hate mail." ] (]) 00:10, 23 July 2011 (UTC)
Pinging {{u|Prince of Erebor}} The fifth reference on ''Last Song for You'' seems unreliable. Google Translate reveals that it is a WordPress blog. I'm planning on promoting prep 2 when it is ready, and I'm just doing some early checking. ] (]) 22:43, 17 January 2025 (UTC)
: How about just "hate mail"? I don't really like these tabloid headline hooks, I have to say. There was another one at T:TDYK about some recent guy getting enslaved and beheaded. DYK is to motivate people to create new content for '''encyclopedia articles''', and I'm not sure we achieve that by front-paging ugly trivia. Just off the top of my head here, but what do others think? <font style="font-family:sans-serif;color:black;"> <span style="text-shadow:#0099cc 0.12em 0.12em 0.12em; class=texhtml"> ''''']'''''</span> ] 00:43, 23 July 2011 (UTC)
:Hey ], I believe you are referring to ''Film Pilgrimage'', which should be considered a reliable source because Gary Wong Kwun-ho (王冠豪) is an established film historian and writer with a long career researching on film location scouting and his books are widely cited in this field. (He is also a notable figure that warrants an article, and I have had him on my to-write list for a long time.) So I believe he qualifies as a ] according to ]. (Film articles on zhwiki have also cited ''Film Pilgrimage'' for the same rationale.) Also, the article is an exclusive interview with the director and lead actress, discussing the filming locations (which falls within Wong's expertise and does not contain exceptional claims). So I see no issue with citing Wong's piece in this case. —''']<small>（]）</small>''' 04:38, 18 January 2025 (UTC)
:I'd use a different hook altogether. It's a minor point in the article, and using it as a hook is not very sensitive to potential BLP concerns. --'''<font color="#0000FF">]</font><font color=" #FFBF00">]</font><font color="#0000FF">]</font>''' 04:38, 23 July 2011 (UTC)
::That’s great. Thank you. ] (]) 12:16, 18 January 2025 (UTC)


===]===
== RfC: DYK quality assurance and archiving ==
Pinging {{u|4meter4}} The Unruh, Delbert (2018). Forgotten Designers Costume Designers of American Broadway Revues and Musicals From 1900–1930 reference was published by Page Publishing. It is a self-publishing company. The source can work if Delbert Unruh received significant coverage over his work. ] (]) 22:54, 17 January 2025 (UTC)
::@{{u|SL93}} You have not actually looked at the article and what sources are physically cited in the article for the hook. Unruh isn't cited in the article for the source. Hischak is for the quote which is from ]. But Hischak oddly excluded Swanstrom from the lyrics credits. That's why I provided two different sources verifying Swanstrom as a co-lyricist of this work when I proposed the hook. One was Unruh, but the same content is also found in Bloom which is the source actually cited for the hook content in the article. Bloom is published by ]. There isn't a verifiability issue here.] (]) 00:43, 18 January 2025 (UTC)
:::{{u|4meter4}} I never said that the Unruh source was used for the hook. I brought it up just in case because no unreliable sources should be used in articles. If the self-published source doesn't help anything, I fail to see why you want it there. Checking preps is not just about checking hooks. ] (]) 00:47, 18 January 2025 (UTC)
:::::{{u|SL93}} Here is Delbert Unruh's obituary . He was a full professor of theatre at the University of Kansas where he taught for forty years. He was a ] and was honored by the United States Institute of Theatre Technology and by the ] for his work as a theatre scholar and educator. He's clearly a subject matter expert. Given the source is only used to support a single non-controversial sentence in the article I don't think this should be issue. The ] has the same content, but I think Unruh is a better source to cite given who he is over a database without an attributed author. Best.] (]) 00:58, 18 January 2025 (UTC)
::::::{{u|4meter4}} That is all that I needed, and you did not need to assume bad faith on my part. You should also know better. Well, it certainly isn't an issue now. ] (]) 00:59, 18 January 2025 (UTC)
:::::::I'm sorry, I misinterpreted your objection because I had mention Unruh as a supporting source of the hook in my nomination. I didn't realize initially that you were objecting to its inclusion in the article overall. I didn't mean to make you feel attacked or slighted in my comments. Best.] (]) 01:01, 18 January 2025 (UTC)
::::::::It's fine. I guess I will be clearer next time. ] (]) 01:02, 18 January 2025 (UTC)
:This has been resolved. ] (]) 01:46, 18 January 2025 (UTC)


===]===
{{rfc|policy|rfcid=81AA6B7}}
I promoted this to prep. Can someone check over it? ] (]) 02:02, 18 January 2025 (UTC)
:Are NZ Short Walks and The End is Naenae reliable? Pinging {{u|Petersmeter}} and {{u|Schwede66}}. ] (]) 02:32, 18 January 2025 (UTC)
::I've had a look, {{u|SL93}}, and are happy to share my thoughts:
::* NZ Short Walks – that's obviously a blog and I couldn't figure out who the blogger is. Seems a well-informed person but without knowing more about who is doing the blogging, the default position has to be that this isn't a reliable source.
::* The End is Naenae – this is a blog by Dr {{Cite Q|Q131787008}} (I've made a Wikidata entry for her). She's a reasonably senior civil servant, and the area she's blogging about falls squarely within her professional expertise. I suggest that ] is appropriate guidance and this content, if presented as McMartin's opinion, is acceptable to be used. And I've just spotted that by ]; that's a rather well regarded magazine and gives the whole affair a lot of credence. The full story is behind a paywall and if anyone has access to it, that would obviously be preferable to use as a source.
::That's at least my 2c. ''']]''' 05:04, 18 January 2025 (UTC)
:::NZ Short Walks is by Joanne Rolston. She is the author of The Kingdom (]) but appreciate that is fiction. I believe she is working on a book on NZ history - but not yet published. I can't find much about her background/qualification etc. So accept that we have to default to not a reliable source. ] (]) 11:01, 20 January 2025 (UTC)
:I have removed NZ Short Walks from the article. ] (]) 22:23, 18 January 2025 (UTC)


== ] (23 January) ==


===]===
Extensive discussion above shows that there are serious quality and policy-compliance problems in the current DYK process, and that many editors are concerned that ], ], ], ], and wrong facts are regularly going through under the radar. This RfC is to determine whether there is consensus for two changes to the process as partial steps towards fixing these problems.
{{ping|SL93|It is a wonderful world| Narutolovehinata5}} there is substantial ] which needs to be resolved before this can run. ] ] 00:18, 18 January 2025 (UTC)
:I wrongly assumed that there was something that I was missing when I checked for CLOP because two substantial editors participated in the DYK. I swear to not do that again, and to follow my gut instinct. I will see about fixing it. ] (]) 00:24, 18 January 2025 (UTC)
:{{u|RoySmith}} I believe that I have taken care of it. ] (]) 01:08, 18 January 2025 (UTC)
::I am admittedly a less experienced editor, but are most of these changes needed? Does stating that someone was "sentenced to life imprisonment without the possibility of parole" actually violate CLOP? '']''] 01:30, 18 January 2025 (UTC)
:::I would say yes if there is a way to reword it. ] (]) 01:37, 18 January 2025 (UTC)
::::What caught my eye was {{text and translation|Records show that he had at least three different stepfathers and three half-siblings by the time he was 15 years old. Meza began using drugs at age eight and was first arrested in 1973 on shoplifting and burglary charges; the following year, he was accused of arson|County and state marriage records show Meza had at least three different stepfathers and three half-siblings before he was 15 years old ... Meza began using drugs at the age of 8 and was first arrested in 1973 on shoplifting and burglary charges ... The following year, the report stated, Meza was accused of arson }} That's classic close paraphrasing, which is defined as "superficial modification of material from another source". Once I saw that, I kept looking and found other examples. Yeah, most of the changes were needed. ] ] 01:46, 18 January 2025 (UTC)
:::::I see. I will be more careful about this from now on. Thanks. '']''] 01:50, 18 January 2025 (UTC)
::::::Thanks. I didn't intend to single you out. ] is one of our most commonly misunderstood policies. ] ] 02:10, 18 January 2025 (UTC)


===]===
The RfC does <u>''not''</u> cover issues that might need to be resolved if one or both of the current proposals gains consensus. These include whether:
{{ping|SL93|UndercoverClassicist|Thriley}} The hook is, at best, deceptive. He may have spent six weeks at Flynn's School, but he spent four years at Trinity College. ] ] 00:26, 18 January 2025 (UTC)
*there should be a directorate;
:{{u|RoySmith}} Maybe this as a rewording - "...that ''']''', a professor of ], spent six weeks at a private school?" or maybe "... that ''']''', a professor of ], was mostly home-schooled as a child?" ] (]) 01:18, 18 January 2025 (UTC)
*nominators (after their fourth successful DYK) should still be required to review another editor's nomination when they nominate a DYK;
::{{ping|RoySmith}} this is probably a British-ism, where "school" and "university" are separate: "at school" excludes "at university". We could add "was accepted to university and became a professor of classics" to clarify that distinction? Alternatively, there are two ALTs:
*a template should be created to provide for the explicit checking off of the explicit requirements listed in the first proposal, below; and
::* '''ALT1''': ... that ''']''' successfully recommended that ] be made a professor, and unsuccessfully recommended that ] be released from jail? <small>Source: {{cite book| last=Beard| first=Mary| author-link=Mary Beard (classicist)| year=2002| chapter=Ciceronian Correspondences: Making a Book out of Letters| editor-last=Wiseman| editor-first=Timothy Peter| editor-link=T. P. Wiseman| title=Classics in Progress: Essays on Ancient Greece and Rome| publisher=Oxford University Press| isbn=0-19-726323-2| page=107| ref=none}} (Housman); {{cite journal| author-last=Stanford| author-first=William Bedell| url=https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| title=Robert Yelverton Tyrrell| journal=Hermathena| volume=125| date=Winter 1978| issue=| page=17| url-status=dead| jstor=23040586| archive-url=https://web.archive.org/web/20211020071850/https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| archive-date=2021-10-20| ref=none}}} (Wilde)</small>
*the system of pasting in coloured ticks and crosses should be binned or modified.
::* '''ALT2''': ... that ''']''' started a "minor civil war" over an edition of the Greek historian ]? <small>Source: {{cite journal| author-last=Stanford| author-first=William Bedell| url=https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| title=Robert Yelverton Tyrrell| journal=Hermathena| volume=125| date=Winter 1978| issue=| pages=5–6| url-status=dead| jstor=23040586| archive-url=https://web.archive.org/web/20211020071850/https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| archive-date=2021-10-20| ref=none}}}</small>
::I might add an abbreviated version of ALT1: "... that the classics professor ''']''' tried to get ] released from jail?" <small>Source: {{cite book| last=Beard| first=Mary| author-link=Mary Beard (classicist)| year=2002| chapter=Ciceronian Correspondences: Making a Book out of Letters| editor-last=Wiseman| editor-first=Timothy Peter| editor-link=T. P. Wiseman| title=Classics in Progress: Essays on Ancient Greece and Rome| publisher=Oxford University Press| isbn=0-19-726323-2| page=107| ref=none}} (Housman); {{cite journal| author-last=Stanford| author-first=William Bedell| url=https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| title=Robert Yelverton Tyrrell| journal=Hermathena| volume=125| date=Winter 1978| issue=| page=17| url-status=dead| jstor=23040586| archive-url=https://web.archive.org/web/20211020071850/https://www.tcd.ie/Secretary/FellowsScholars/discourses/discourses/1978_%20W.B.%20Stanford%20on%20R.Y.%20Tyrrell.pdf| archive-date=2021-10-20| ref=none}}} (Wilde)</small> '']'' <sup>]·]</sup> 08:30, 18 January 2025 (UTC)
Implicit in the proposals is the likelihood that the maximum four six-hour shifts per day of five to eight hooks (≥ 32 DYKs) will more often than now be altered by the queing admins to longer exposures and fewer shifts per day, and be treated as normal practice. This would not be necessary if there is a sudden influx of reviewers and more nominators who can manage the time to respond to the issues they raise. However, please note that the primary consideration of the two proposals is effective quality assurance and compliance with site-wide policies, not reduced flow.
:::I was not aware of that British usage, thanks for that. I'm not opposed to any of those, but maybe the simplest fix would be to say "... six weeks at secondary school". ] ] 15:28, 18 January 2025 (UTC)
::::That would work too! '']'' <sup>]·]</sup> 16:18, 18 January 2025 (UTC)
Please respond under the proposals below with brief "support", "oppose", or "neutral" entries; longer comments may be made in the "Discussion" section underneath each proposal. Long comments in the !voting sections may be relocated to the related "Discussion" section.
:::::Done ] ] 17:25, 18 January 2025 (UTC)


== ] ==
===RfC proposal: a proper reviewing checklist===
'''Proposal:''' "No DYK article should receive main-page exposure unless the article has been checked and <u>''explicitly''</u> passed for:
#adequate sourcing, including ], ] and ];
#];
#plagiarism and ];
#other ], in files and text; and
#obvious faults in prose, structure, and formatting."


===] (])===
These checks are in addition to the existing requirements concerning hook length, hook source, article length, and time since article creation/expansion.
{{ping|TheDoctorWho|Sammi Brie}} the way this article mentions the incident ({{green|captioned the poster with "Joy to the Worlds", mirroring the title "Joy to the World"}}) is not entirely clear, especially the word "mirroring". Would it not be better to simply state that the title was misspelled? ] (]) 13:46, 18 January 2025 (UTC)


:@] Responded with a reword. Hope you don't mind the tweak, TheDoctorWho. ] (she/her • ] • ]) 17:19, 18 January 2025 (UTC)
*'''Support''' as proposer. ] ] 03:32, 23 July 2011 (UTC)
::Don't mind at all, was just about to take care of it myself but you beat me to it, thanks! {{smiley}} ] ] 17:30, 18 January 2025 (UTC)
*'''Support''' as yet another proposal that I can't possibly see any sensible objection to. Long overdue. --] (]) 03:37, 23 July 2011 (UTC)
*'''Support'''. These are all things a reviewer should be checking anyway, although they aren't yet required to "explicitly" say they did. <b class="IPA">]</b>&nbsp;(]) 03:39, 23 July 2011 (UTC)
*'''Support''' I remember a checklist was brought up last year but not implemented. Copyvios are most common of problems to slip below the radar.--] <small>]</small> 04:00, 23 July 2011 (UTC)
*'''Qualified support''' - on reflection, I think I will support this, but only on the basis that QPQ is retained. We don't remotely have the manpower to check and fix absolutely every problem in every submission without QPQ. But I do think a requirement like this would help guide and remind reviewers of the issues they need to be checking. ] (]) 04:04, 23 July 2011 (UTC)
*'''Support''' Any obvious errors should already be sounding warning bells in reviewers' heads. —<font face="IrishJig">''']'''<sub>]''']'''</sub></font> 04:12, 23 July 2011 (UTC)
*'''Support''' per Rjanag. -- ] (]) 04:05, 23 July 2011 (UTC)
*'''Support'''. per Rjanag - not sure of the reason for explicitly stating this unless it is to ensure that folks tick it off explicitly when reviewing. ] (] '''·''' ]) 04:14, 23 July 2011 (UTC)
*'''Support'''. --'''<font color="#0000FF">]</font><font color=" #FFBF00">]</font><font color="#0000FF">]</font>''' 04:16, 23 July 2011 (UTC)
*'''Support''', but with more specific minimum guidelines ], specific to the problems critics see most often slipping through DYK. ] (]) 04:26, 23 July 2011 (UTC)
*'''Support'''. DYK needs to be done more professionally, and this will help (so will reduced throughput, but that's another issue...) ] (]) 04:35, 23 July 2011 (UTC)
*'''Support'''. DYK articles needn't be FA or even GA, but they should comply with minimum standards. Everything that appears on the main page should be work of which we can be proud. &nbsp; <b>]&nbsp; ]&nbsp; </b> 04:40, 23 July 2011 (UTC)
*'''Qualified support'''. Seems pretty motherhood and I agree. Seems like we should slim down and simplify the instructions. Points 1, 3, and 4 seem like same concept ("plagiarism" loosely defined.) Maybe just say "close paraphrasing". Mechanics will be tricky for offline content. Also, I think we need to be reasonable (even at FA it is a spotcheck, not a complete text search). (2) neutrality...sure...and maybe important given the Cirt kerfuffle. I think they try to do it, but put it in the checklist. (5) I think they already say that it needs to be half decent. Would be good to understand somehow what standard we are really looking for "halfway to GA"? GA quality? (even if not length?) I don't want to get legalistic, just want some better instruction as this could be no change or could be FA-lite. Also, I LOVE the idea of a checklist, but would want to add all the stuff they do now (the hook ref and one ref per para and allthat).] (]) 04:59, 23 July 2011 (UTC)
* '''Oppose'''. In general, the proposal requires a GA-level review. Is that what is meant? Remember that a 5x expansion may be quite large. A straight answer, please. --] (]) 06:01, 23 July 2011 (UTC)
*#{{nay}} "adequate sourcing, including ], ] and ]" for the whole article, every word? --] (]) 06:01, 23 July 2011 (UTC)
*#{{ok}}]; --] (]) 06:01, 23 July 2011 (UTC)
*#{{nay}}plagiarism and ]; OK re plagiarism. NO re ], which at present is a ''proposal'', and needs refinement and ''wide'' ], e.g. a widely advertised RfC of its own. --] (]) 06:01, 23 July 2011 (UTC)
*#(?) other ], in files and text; Please explain. --] (]) 06:01, 23 July 2011 (UTC)
*#{{nay}}obvious faults in prose, structure, and formatting." That is subjective, and WP history suggests that prose issues are contentious and that "prose experts" try to impose their own standards. --] (]) 06:01, 23 July 2011 (UTC)
:::: I share your "GA-Lite" concerns to some extent, but on reflection I think it does no harm to remind reviewers of the kinds of issues they should be looking out for. As Rjanag said, most of these points are things reviewers are supposed to be checking for in any case, so it shouldn't add an undue burden. And it will act as a guide to reviewers as well as promoting a greater sense of responsibility and accountability. ] (]) 06:38, 23 July 2011 (UTC)
*'''Oppose'''. The theory is okay, but to 100% verify all this stuff is a massive task. Combined with the automatic 7 day rule below this will just result in masses of DYK noms being deleted for no good reason other than they're out of time and no one has the time or inclination to fully check them out. We wait long enough for other editors to comment as it is. Far too bureacratic. --] (]) 06:23, 23 July 2011 (UTC)
*'''Support''' I very much support this, but how will this be handled unless the number of noms is decreased or number of reviewers increased? Or, I guess more precisely, how will this be enforced? Why aren't people doing this already?] (]) 07:10, 23 July 2011 (UTC)
*I support the principle, but '''oppose''' in this form. This amounts to a ] review, which is excessive for short new articles. I am not aware of recurring problems with DYK articles that would require this. Verifiability and neutrality are often controversial and cannot be properly determined except through a formal consensus-based discussion in the style of ], which is not suited to the high volume of DYK articles. Our disclaimer states that we make no guarantee of validity or correctness, so readers will occasionally encounter suboptimal articles linked to on the main page, just like they will occasionally encounter deficient articles via Google. Moreover, "close paraphrasing" is an essay, so compliance with it cannnot be made mandatory. It is sufficient to check that the article does not contain clear copyright and BLP violations or clear formal faults, and does not ''obviously and indisputably'' violate important content policies such as V, NPOV and NOR. <small><span style="border:1px solid black;padding:1px;">]</span></small> 10:22, 23 July 2011 (UTC)
*'''Support''' I don't know why DYK produces frequent errors but I do know the main page isn't the place for repeat error. ] (]) 11:19, 23 July 2011 (UTC)
*'''Qualified oppose''': I do not think that this would be most effective at review time, but when moving hooks from Prep to Queues. If the proposal were for that, I would vote support. ] (]) 12:03, 23 July 2011 (UTC)
*'''Support''' per Rjanag, Cas, Sasata, and Will Beback. ] (]) 13:45, 23 July 2011 (UTC)
* '''weak support''' wholesale radical change is necessary instead of tinkering; does not go far enough, but is better than nothing. --] (]) (aka Ohconfucius) 14:59, 23 July 2011 (UTC)
*'''Support''' Hopefully this will promote consistency in the quality of DYKs. ] (]) 15:14, 23 July 2011 (UTC)
*'''Support''' – I too often get the feeling that DYKs are just getting rubber-stamped. This will ensure some minimal standards for what appears on the main page. And it's not as demanding for reviewers as it sounds; some source spot-checks and a quick look through the article and reference list, and you're done. Only suggestion is to merge points 3 and 4, since they cover similar territory. ''']''' (]) 15:48, 23 July 2011 (UTC)
*'''Support'''. Misplaced Pages is about being a useful encyclopedia, not an easy way for editors to rack up DYKs. This proposal simply asks that things be done, that should ''always'' be done as a matter of common sense. I appreciate that it may make it harder to move nominations through the pipeline. So be it. I would have no objection to extending the amount of time a nomination can wait for review if need be, and extending the amount of time after page expansion. Newness of the content really isn't that important. I would also have no objection to simply having fewer DYKs on the main page, so long as those that do appear are well vetted, if it comes to that. --] (]) 16:34, 23 July 2011 (UTC)
*'''Qualified support''' for a very lightweight process. See the discussion section for more detail.
*'''Support''' - It is risky to be putting material from brand new articles up on the front page. I think it would be wiser to shift the DYK emphasis from new articles, to more mature articles that are GA quality. Here's an idea: why not make DYK a follow-on process to achieving GA status? Thus, focus would shift to the GA process, and DYKs would be a natural by-product of that. --] (]) 17:45, 23 July 2011 (UTC)
::I just noticed that another editor had a similar proposal (great minds think alike :-) down below in this Talk page ]. --] (]) 17:51, 23 July 2011 (UTC)
====Discussion about "proper checklist" proposal====
''Long posts in the !voting section above may be relocated here.''


== ] ==
*'''Comment''' - <s>I think this RFC should be pulled, it's a fishing expedition that is proposing outcomes rather than solutions. We need to stay focussed on improving the project, all this RFC is likely to do is give DYK critics a venue for sounding off without addressing any of the actual problems.</s> ] (]) 03:55, 23 July 2011 (UTC) Changed my mind about this, and submitted a !vote with comment above. ] (]) 04:06, 23 July 2011 (UTC)


=== ] (]) ===
*@Tony1 - I guess what you're getting at here is that the reviewer should explicitly ''state'' that they've reviewed these issues, in which case it should be in a proposal. ] (] '''·''' ]) 04:17, 23 July 2011 (UTC)
Needs end of sentence citation. @], @], @]. —] (]) 16:57, 18 January 2025 (UTC)
**<p>''Response to Cas'': Indeed, but I should point out that it wasn't my intention to propose that every reviewer should have to tick off on every aspect. Specialist reviewers should be encouraged, IMO. ] ] 04:21, 23 July 2011 (UTC)
***KISS. Better to just have one person run through the whole thing. We don't want to duplicate FA and/or have all kinds of moving parts (shared checklist pages and the like). Sure. some people will be better at one task than the other, but it will drive learning anyway. We ALL need to learn more about looking for close paraphrasing. Mottenen is only one person. Making everyone do it, will raise the level of community knowledge and over time the standards of the project as a whole.] (]) 05:24, 23 July 2011 (UTC)
****I don't know diddley-squat about which pop-music or sporting sites are reliable and which aren't; nor do I know much about image copyright and checking for plagiarism and close paraphrasing (some people do; maybe we need a pointer to the how-to-do-it pages); and many reviewers won't feel they are equipped to review prose, formatting and structure. That's why we should all be grateful if an editor is willing to zap through a tranche of DYK noms using their specialist knowledge of these matters. What distinguishes DYK noms from FACs is their size and, usually, lack of comprehensiveness; and I suppose there's more acceptance of less-than-perfect prose and a few other areas (but not obvious glitches, please). ] ] 06:01, 23 July 2011 (UTC)
*****As long as I'm not doing much subject matter expertise and just looking for common sense inconsistencies, than I can review a new article on anything. (I would expect more for FA, we don't do enough subject matter and coverage consideration there. but here? Nah. I can review anything.) We don't have infinite resources, Tony. How much time and manpower do you think will do a review. Then moving parts and coordination? And now you have a 7 day limit on it? KISS, baby. You can learn the basics of image copyright just by writing a few articles and having some deletions come up of your own. All you do is go to the file page and check the source and look for obvious inconsistencies. Or just do a few reviews and figure it out. Or read what someone else says. It won't be CLindburg/Dcoetze quality, but we only have a few of them and need to do some work ourselves. It doesn't need to be a nuclear assurance. Just a second screen and then move the thing along the path. We don't have infinite experts on call. Rather move along with something workmanlike than develop intricate dependencies.] (]) 12:43, 23 July 2011 (UTC)
*'''Comment''' What does "obvious faults in prose, structure, and formatting" mean, exactly? I am concerned about the potential for standards creep here, in part because I see DYK as having an article incubation/improvement role. Because any article featured on DYK pulls in so many eyeballs, there are certain things like unsourced/ill-sourced BLP and copyvio and plagiarism that should never appear in such an article. On the other hand, I think an article that lacks completeness, for instance, should remain a DYK candidate, in part because the exposure at DYK might pull in the right person to complete it. The checklist should forbid such things as a policy-conscious editor would ''never'' put in mainspace, but should permit usages that might be left for later development. ] (]) 05:55, 23 July 2011 (UTC)


:@] Done. ] (she/her • ] • ]) 17:18, 18 January 2025 (UTC)
:: I think the interpretation could probably be left up to the individual reviewer, not everybody has the same notion of what constitutes an unacceptable flaw but if some reviewers want to take a harder line over such matters, it's not such a big deal. ] (]) 06:54, 23 July 2011 (UTC)
::@], forgive me if I'm being dense, but don't we need this to be one sentence earlier? —] (]) 17:21, 18 January 2025 (UTC)
:::@] Combined the two sentences instead for DYK purposes. ] (she/her • ] • ]) 19:38, 18 January 2025 (UTC)
::::That works! Apologies for the pedantry. —] (]) 19:41, 18 January 2025 (UTC)


== 2/day ==
::I'm uncomfortable with this one as well. Out of the whole list it's the least important and arbitrary. The key word in there is obviously "obvious" but I'm guessing most reviewers won't pay attention to that. I'd hate to see a good DYK nom turned down because, for example, someone didn't use citation templates or something.] (]) 07:13, 23 July 2011 (UTC)


::: When noms are turned down, they are usually turned down by consensus not by a single user, so I see little prospect of this occurring in practice. ] (]) 08:37, 23 July 2011 (UTC) I have just activated 2/day, 12-hour set backlog mode. Hope a few people can pitch in and help promote hooks to prep and preps to queue so we can do this without burning out anyone. —] (]) 07:20, 19 January 2025 (UTC)
:There are only five queues filled after the midnight promotion was made, so it's time to go back to 1/day, 24-hour set backlog mode. Pinging {{DYK admins}} so that this can be done in the next few hours. Many thanks. ] (]) 01:14, 22 January 2025 (UTC)
::I'm sorry, is the current rule that we only do 12-hour sets for three days at a time? I must have missed that change, but I'll trust BlueMoonset to be on top of it. {{Done}} :) ] (] • she/her) 08:18, 22 January 2025 (UTC)
:::It doesn’t seem like a good idea with 135 approved nominations. It also looks like we will have to go back to two sets a day again soon. ] (]) 08:28, 22 January 2025 (UTC)
::::IIRC the three day cut off was put in place to ensure the rate was reduced before admins (and now template editors?) burnt out. Being able to trigger it a second time quickly is I believe part of the intended design, dependent on there being filled preps and queues that show that volunteers have not yet burnt out. ] (]) 08:34, 22 January 2025 (UTC)
:::::That makes sense. Thanks for the information. ] (]) 16:50, 22 January 2025 (UTC)
::::::I pushed for the 3-day rule exactly to prevent burnout. Previously, our only criteria for mode change was how many noms were stacked up in the approved pile. So we'd start doing 12-hour sets and quickly run the queues empty with nobody willing to put in the work to keep it going. Now at least we find out if we've got the work capacity to handle it without getting to the crisis stage of zero queues filled.
::::::Informally, I think flitting back and forth between modes is a bad idea because it complicates the job of people trying to schedule special occasion hooks. I'd rather see us stay in 12-hour mode for a bunch of consecutive cycles, but not at the cost of running the queues down to zero. ] ] 17:11, 22 January 2025 (UTC)
::::::I've done one, though I notice that PSHAW hung when I clicked the button - pinging {{yo|Theleekycauldron}}. The next one has one of mine in it; will do the other eight if no-one else does in the next three hours.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:27, 22 January 2025 (UTC)


== ] ==
*One of the problems with greater scrutiny like this is that to fix some of the issues will require an extensive rewrite of the article. What happens to articles that get rejected, but the nominator doesn't fix? Does the reviewer then have to find the time to rewrite and fix the article? Articles with this level of problems should be picked up earlier by another process, or get sent somewhere else for fixing. The few times I've reviewed articles for DYK, I've found myself thinking "this article is poor", and the temptation was great to go find another article to review that was of a better quality. It would be very liberating to be able to say "this article is not good enough", to give a list of reasons, and then reject it, ''and list it somewhere where it would get fixed''. But it would be very depressing to see no follow-up to that and no fixes made to the article. What might help is some examples of articles at different stages of development, with indications of where minimum standards have been met, maybe even with specific diffs that show the correction of particular problems. ] (]) 10:44, 23 July 2011 (UTC)


=== ] (]) ===
*Checking for plagiarism and copyvios should be easier using the . ] 13:27, 23 July 2011 (UTC)
@]: The hook fact lacks an end-of sentence citation. —] (]) 07:33, 19 January 2025 (UTC)


:@], do you mean in the article? '']''<sup>]</sup> 10:05, 19 January 2025 (UTC)
*One thing we can be sure of is that there will be no "sudden influx of reviewers and more nominators who can manage the time to respond to the issues they raise". Did You Know has always had more than enough people to demand error correction, and not enough to do it. Every added procedure, subprocedure and exception (especially the unwritten ones) will detract from time to actually fix anything, not add to it.] (]) 14:19, 23 July 2011 (UTC)
::@], yes. Thank you for adding it. —] (]) 10:07, 19 January 2025 (UTC)
:::@] no worries. I didn't worry about it when I was promoting the hook because it was at the end of the paragraph anyway. Can't hurt to have it at the end of each sentence though. '']''<sup>]</sup> 10:17, 19 January 2025 (UTC)
::::@], it is actually a requirement per ]. —] (]) 11:29, 19 January 2025 (UTC)


=== ] (]) ===
*'''Comment''' I support only a very lightweight process - the check should only be for obvious cases and not a "GA-light". "Prose issues" should be limited to checking that it is of at least "adequate clarity" (to use the feedback tool's terminology); similarly the NPOV should just check that there is "no obvious bias", and the sourcing should just require that the portion being used is supported by "adequate reliable sources" and the rest of the article has at least some reliable sources. Any reviewer should be able to determine whether the criteria are met in about 2-5 minutes for most short and medium length articles. Plagiarism and close paraphrasing checks should only search for the obvious cases unless there are explicitly raised concerns or the initial check warrants further investigation. ] (]) 17:20, 23 July 2011 (UTC)
@{{U|Le Loy}}/{{U|Ле Лой}}, @{{U|Geni}}: The lead should be expanded a bit to make the article properly ]. —] (]) 08:03, 19 January 2025 (UTC)
*] '''Question''' Will nominators have a chance to fix any of the above issues should they appear in the article, or will the DYK nomination be promptly removed basically saying "fix it and submit again?" ]] <small>(note: not a ]!)</small> 17:58, 23 July 2011 (UTC)
:@], done, please take a look. I got so sick of this institution it took me a while to return to the article. ] (]) 11:46, 19 January 2025 (UTC)
:*Nevermind, just read the below discussion. ]] <small>(note: not a ]!)</small> 18:00, 23 July 2011 (UTC)
::@]: much better, thanks! —] (]) 11:49, 19 January 2025 (UTC)


== ] ==
===RfC proposal: archive unsuccessful nominations after seven days===
'''Proposal:''' "A nomination that has not met the requirements seven days after it is first edited by a reviewer<sup>1</sup> should be declined and archived, unless an administrator involved in DYK queuing grants an application for an extension of a specified number of days. Time limits include time spent in a preparation area."


===]===
<sup>1</sup><small>Or a similar arrangement decided on by editors at DYK, such as a template expiry date.</small>
{{u|Olmagon}} {{u|AmateurHi$torian}} {{u|AirshipJungleman29}} - How does anyone know that only two people are known to have seen the frog alive? The article even says this about the first discoverer - "He collected three individuals, which would later be studied and recognized as a new species by British biologist Arthur Loveridge in 1935." That would be two people already if those specimens were alive, and that is without mentioning the next discoverer of live specimens named Ronalda Keith. ] (]) 12:21, 19 January 2025 (UTC)
:{{ping|Olmagon}} I guess the collected species are presumed to be dead, but is there a source which says that? If there is none, maybe ALT1 can be used instead. -] (]) 12:41, 19 January 2025 (UTC)
:{{u|SL93}}, collected specimens are dead. The source clearly says that they were preserved in ] after their collection in the field. ] (]) 12:58, 19 January 2025 (UTC)
::{{u|AirshipJungleman29}} Collected specimens are not always dead. As for the source, I only have access to an abstract that didn't answer my question. ] (]) 13:06, 19 January 2025 (UTC)
:::See ]. If they are not dead and preserved, they are not yet considered specimens. ] (]) 13:09, 19 January 2025 (UTC)
::::Not true. Searching "living specimen" and "living specimen meaning" shows otherwise. along with and are just three of many examples. Although it doesn't matter now. ] (]) 13:28, 19 January 2025 (UTC)
::::The source right after mentioning Arthur Loveridge makes it clear that they were preserved. The View Article link originally didn't show up on my screen. I just had to refresh. I'm sorry. ] (]) 13:59, 19 January 2025 (UTC)
:::::I suppose it's always possible that someone saw this frog alive but never reported it or didn't realize it was this species, that's why I specified "known", but I suppose you seem to have solved the issue already without me anyways. ] (]) 21:18, 20 January 2025 (UTC)


===]===
There has never been a clear process for removing from the "suggestions" page nominations that have not reached acceptable standards. This is essential if compliance with site policies and other standards are to be upheld in DYKs on the main page. Expecting the queuing admins to tip-toe around removing the odd bum nomination is hardly a professional procedure. A professional DYK process involves rejection as well as passing, and the nominations page needs to be kept under control by the admins.
{{u|AmateurHi$torian}} {{u|MartinPoulter}} {{u|AirshipJungleman29}} - A direct citation is needed after the hook fact. ] (]) 12:21, 19 January 2025 (UTC)
:{{re|SL93}} Added -] (]) 12:36, 19 January 2025 (UTC)


===]===
*'''Support''' as proposer. ] ] 03:32, 23 July 2011 (UTC)
{{u|Mccunicano}} A citation is needed after "Southbound exit." ] (]) 12:21, 19 January 2025 (UTC)
*'''Support''' tentatively. I have also flirted with this idea (although in response to a different problem--hook boringness) at '']'' and '']''. I have a lot of concerns about the details of how it would work (see those links and the discussion below) but in spirit I think it's the right move. <b class="IPA">]</b>&nbsp;(]) 03:50, 23 July 2011 (UTC)
{{reply to|SL93}} That's what the Google Maps reference is for at the top of the junction list, but the information also exists within the page linked to the junctions that are to be closed, it's redundant to attach it for a junction that is not impacted by the closures. ''']]''' 23:44, 19 January 2025 (UTC)
*'''Support''' this would probably help to move along some of the nominations that develop lengthy and largely unproductive discussions. --] (]) 04:01, 23 July 2011 (UTC)
:{{u|Mccunicano}} I wrongly assumed that everything in the notes was meant to be sourced to the 6th reference, and I didn't think Google Maps was the best option when another source is available. I came to that conclusion after searching recent discussions about if Google Maps was completely reliable, and I came across ] a few minutes ago which revealed to me that it can be used to such a purpose as this. You can remove the citation. ] (]) 00:12, 20 January 2025 (UTC)
*'''Support'''. Excellent idea. -- ] (]) 04:04, 23 July 2011 (UTC)
*'''Support'''. yes, long tails on the suggestion queue are somewhat distracting. ] (] '''·''' ]) 04:15, 23 July 2011 (UTC)
*'''Weak support''' There will be articles that are sent to AfD and kept ''after'' the seven day period has ended, but I suppose a few casualties isn't a huge issue. —<font face="IrishJig">''']'''<sub>]''']'''</sub></font> 04:20, 23 July 2011 (UTC)
*'''Support'''. Hooks should be well-prepared, interesting, and inviting to reviewers from the start. ] (]) 04:26, 23 July 2011 (UTC)
*'''Support'''. Increases efficiency. ] (]) 04:31, 23 July 2011 (UTC)
*'''Support'''. If standards for DYK articles are increased then some streamlining will be necessary. While some last minute fixes for new articles may be needed, DYK is not an article nursery. &nbsp; <b>]&nbsp; ]&nbsp; </b> 04:44, 23 July 2011 (UTC)
*'''Sure'''. This will ease the stress for the whole infrastructure and give a bit of a kick in the ass to weaker submitters.] (]) 05:02, 23 July 2011 (UTC)
*'''Support''' with Tony's last change (otherwise, no). I'm thinking there will need to be a special page made with instructions for reviewers.] (]) 07:16, 23 July 2011 (UTC)
*'''Qualified support''' It needs to be changed to a week that a reviewer's comment has remained unanswered - a point raised by Gatoclass below, support if that is actually the proposal. ] (]) 10:25, 23 July 2011 (UTC)
*'''Support'''. Agree with this. ] (]) 11:04, 23 July 2011 (UTC)
*'''Support''' Due process requires criteria to be enforced. ] (]) 11:21, 23 July 2011 (UTC)
*'''Qualified Support''': Not 7 days since the first review, but 7 days since the last comment. Some require major discussion, like the Children of the Stork hook at ] right now. ] (]) 12:07, 23 July 2011 (UTC)
* '''Support''' incorporating Tony's change of 03:51, 23 July 2011 --] (]) (aka Ohconfucius) 15:03, 23 July 2011 (UTC)
*'''Support''' with the changes. ] (]) 15:16, 23 July 2011 (UTC)
*'''Support''' – Wouldn't support removing noms that are completely unreviewed, but if there are important comments that go unaddressed for a week, a nomination should be failed. I wonder why this isn't in the rules now. ''']''' (]) 15:48, 23 July 2011 (UTC)
*'''Support''' 7 days after reviewer edit. I would expect the DYK admins to check that concerns have been addressed, if the nominator has responded to say that they are fixed. ] (]) 17:52, 23 July 2011 (UTC)
*'''Support''' I just saw the backlog for the first time a little while ago, and I couldn't believe it. This sounds like a fair solution. ]] <small>(note: not a ]!)</small> 18:02, 23 July 2011 (UTC)
*I can '''support''' this as written, but I would also suggest that nominations that have not yet been reviewed should in fact be given ''more'' time. --] (]) 18:39, 23 July 2011 (UTC)


== ] ==
====Discussion about "archiving unsuccessful nominations" proposal====
''Long posts in the !voting section above may be relocated here.''


===]===
Does this mean that if a nominator nominates their article on 1st August, and no-one has gotten round to reviewing it by 8th August, then the nomination fails? I'm assuming not, but this needs to be clearer...? --] (]) 03:39, 23 July 2011 (UTC)
{{u|Jolielover}} {{u|Pbritti}} {{u|Hilst}} Caffey family murders has ] issues per Earwig such as "to be tried as an adult" and "All four defendants were initially charged with three counts of capital murder". ] (]) 14:41, 20 January 2025 (UTC)
:I think it does mean that; that is how I'm understanding it. <b class="IPA">]</b>&nbsp;(]) 03:42, 23 July 2011 (UTC)
:{{u|Jolielover}} Will you be taking care of this? ] (]) 22:19, 21 January 2025 (UTC)
::Hi there, some false positives due to quotations & things such as names of shows the case was featured on. I have paraphrased the rest, hope it works, thanks. ]] 02:22, 22 January 2025 (UTC)
:::Thank you. ] (]) 02:27, 22 January 2025 (UTC)


===]===
*This may be hard to keep track of, given that for example an article may be nominated on August 5 but placed under the August 1 header (if that was the date it was actually created). The way the proposal is currently written, this nom would expire on August 12 (7 days after nomination), not August 8 (7 days after the header under which it's included). I'm not necessarily saying that's wrong, just that it might be a pain to keep track of (although I suppose people could just remove old noms whenever they happen to notice one, without necessarily needing a system to remove all new old noms at once). <b class="IPA">]</b>&nbsp;(]) 03:42, 23 July 2011 (UTC)
This is my nomination so someone else needs to look over it. {{Template:DYK admins}} ] (]) 14:41, 20 January 2025 (UTC)
**Thanks for these points: I've boldly changed "seven days after nomination" to "seven days after it is first edited by a reviewer". Does this resolve the problem? ] ] 03:51, 23 July 2011 (UTC)
:Will take shortly.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 15:01, 20 January 2025 (UTC)
**(ec) Actually, it would probably be easy to work in something in the template that says "this nomination expires on DATE", similar to image speedy deletion templates. After that, we could just have an understanding that any editor is free to archive any nomination with an expired date. <b class="IPA">]</b>&nbsp;(]) 03:52, 23 July 2011 (UTC)
:{{done}} {{ec}} Hi {{ping|SL93}} I've taken a look at this and looks good to me. The only thing is, I thought the Career section seemed to be missing coverage from between 1987 and 2012, but then I noticed that was contained in the Filmography section. I've taken the liberty of folding those two into one as that seems to offer a better chronology. It's still a bit on the short side and could do with expansion on more of his career, but fine for a DYK IMHO. Cheers &nbsp;&mdash;&nbsp;] (]) 15:06, 20 January 2025 (UTC)
***Thanks: I've added a footnote above to this effect. This kind of flexibility in the mechanics is good: the principle of time limitation is the main concern of this second RfC proposal. ] ] 04:00, 23 July 2011 (UTC)
**** The problem is that on some occasions, I have placed science-oriented DYK nominations with few/no problems of the kind mentioned above which took longer than 7 days to find a reviewer. Yet when they were finally checked by a reviewer at archive time, they were good to go and made it without remark to the main page. Certain classes of articles which people may shy away from are likely to be discriminated. ] (]) 04:07, 23 July 2011 (UTC)
***** I've had your problem before also, so this concerned me, too. But if I understand right, Tony's just modified it to now count off seven days after ''review'' rather than ''nomination'' (which sounds fair to me). -- ] (]) 04:18, 23 July 2011 (UTC)


== ] ==
The more I think about this, the more impractical it sounds. What happens if someone reviews a hook, the nominator responds and then no-one gets around to having another look for a week? Is that the nominator's fault? Of course not. But under this system, his nom will be deleted unless an admin gives it a reprieve. But do we really want to have nominators running around pestering admins for extra time? IMO it would make more sense for a nom to be deleted if the nominator hasn't responded to a concern within a set period. ] (]) 08:47, 23 July 2011 (UTC)
:In practice, I would hope that those archiving/closing/promoting older nominations would look at the discussions and make a judgment on whether more discussion is needed, or whether archiving/closing/promotion is needed. Effectively, the proposal is asking for a ''decision'' to be taken within 7 days of the review starting (though the decision could be to extend the discussion period). This sounds reasonable to me, and is a lot like how AfD works. ] (]) 11:01, 23 July 2011 (UTC)
:As far as I know, we already do remove noms if a nominator hasn't responded to a concern in a while, although there is no official time period. <b class="IPA">]</b>&nbsp;(]) 11:57, 23 July 2011 (UTC)


=== ] ===
:: Yes we do, but as you say there is no set time period, I think if we made it five days, or even three days, it would help get rid of those lingering noms. Other than that, I can see this proposal creating more problems than it solves, because there are going to be disputes about whether or not a nom should have been given more time, and there is also the possibility of factions gaming the system to delay a nom until it gets deleted. A system that relies on the continued attention of the nominator, on the other hand, places the responsibility on the shoulders of the person most involved, and if he fails to stay abreast of the discussion, he has no-one to blame but himself when the nom is deleted. ] (]) 14:04, 23 July 2011 (UTC)
{{yo|Epicgenius}} The newspaper.com link for the restored organ clipping is incorrect. It links to a . The ProQuest link is fine, though. – 🌻 ] (] &#124; ])
:::Five days would be best, methinks. Three would be cutting it too close, especially since some Wikipedians take the weekends off. ] (]) 14:08, 23 July 2011 (UTC)
::::And some Wikipedians work in the week and edit at the weekends... ] (]) 15:35, 23 July 2011 (UTC) :@], thanks for pointing it out. I found and fixed it. &ndash; ] (]) 15:37, 20 January 2025 (UTC)


=== ] ===
*Can someone clarify what "Time limits include time spent in a preparation area." means? Does that mean if I ask for some improvements on 00:00 5 August which are finished by 12:00 11 August, the article is ineligible to go up because it will take longer than 12 hours to move through ]? '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 18:24, 23 July 2011 (UTC)
{{yo|Viriditas|Jonathan Deamer|AirshipJungleman29}} Do we need to include the fact that it "features model Suzanne Valadon and the stylistic influence of Vincent van Gogh"? I don't see what those tidbits add to the hook. – 🌻 ] (] &#124; ]) 15:24, 20 January 2025 (UTC)
:The model can be cut; I find it interesting that a painting inspired by van Gogh could be found suitable for a nightclub. ] (]) 15:33, 20 January 2025 (UTC)
::The suggestion of @] sounds good! ] (]) 17:31, 20 January 2025 (UTC)
:::Works for me. ] (]) 19:06, 20 January 2025 (UTC)
::::{{Done}} – 🌻 ] (] &#124; ]) 20:55, 20 January 2025 (UTC)


== Older nominations needing DYK reviewers ==
===RfC question: has the obligation to review been a net positive or negative?===
This is a question for DYK regulars - has the introduction of the obligation to review (i.e. QPQ) been a net positive or negative? I'm not sure myself. ] (] '''·''' ]) 04:20, 23 July 2011 (UTC)


The previous list was archived yesterday, so I've created a new list of 31 nominations that need reviewing in the Older nominations section of the Nominations page, covering everything through January 8. We have a total of 271 nominations, of which 156 have been approved, a gap of 115 nominations that has decreased by 8 over the past 8 days. Thanks to everyone who reviews these and any other nominations!
====net positive====
# I think it's a major net positive but I think it's becoming clear it needs some refinement. Specifying the issues that reviewers need to be checking as in the first proposal above is a step in the right direction, but we may need to add some further checks. I would strongly oppose any attempt to scrap QPQ ATM, there are plenty of other things we can try first and going back to the old system of relying on a handful of reviewers would be a last resort in my view. ] (]) 05:27, 23 July 2011 (UTC)
# I think it's been good to have so many more people doing it, even if some of us do it imperfectly on occasion. I don't mind having "experts" double-check reviews (especially if we someday reduce the number of articles reaching the main page), but I want to keep the diversity of reviewers. ] (]) 05:32, 23 July 2011 (UTC)
# Pros: encouragement of collaboration, learning DYK and WP policies and reviewing process, provision of some review. Cons: sloppy reviews. Solution: cover up, check the reviews and provide additional ones. Hook promoter is the key person in the current DYK scheme, and most proposals should be focused here, for example: (i) formally disallow promoting hooks to any editor who hasn't reviewed xx noms in their lifetime (unfortunately, we don't count reviews; but with the QPQ system, reviewed=submitted, and this we do count at stats pages, thus 50 or 100 successful DYKs may do). (ii) keep the whole review thread in the prep so that the promoting admin could check the promotion. ] (]) 05:42, 23 July 2011 (UTC)
# Net positive. Reviewing DYKs made me familiar with rules especially in those areas where I normally dont edit such as BLP. It made me a better and more confident DYK nominator. ] (]) 09:13, 23 July 2011 (UTC)
# What if we required two editors to green-light a hook before it is sent to prep? That would still be faster than having a handful of editors doing all the (tedious) work. —<font face="IrishJig">''']'''<sub>]''']'''</sub></font> 10:40, 23 July 2011 (UTC)
# Positive, but with room for improvements. I like Tony's comment done in the discussion section that an extra aspect of the article could be checked. ] (]) 12:14, 23 July 2011 (UTC)


'''More than one month old'''
====net negative====
*November 19: ]
#While I do not think that everything about the QPQ turned out bad, I believe "net negative" is the right description. Those are my main concerns:
*December 1: ]
#*First in line of course is the entirely subjective observation that there are more unsatisfying reviews than before. And as it is not visible who is new and who is experienced, you just cannot trust the DYK tick symbols anymore.
'''Other nominations'''
#*Less obvious but maybe even more important is the situation that the average reviewer is not as bold as before. Every once in a while a review should start with ] or ] if the problems are many, or if they cover the entire article---not just for purely numerical concerns about length.
*December 24: ]
#*Thirdly, particularly due to DYK's quality problems I believe it is the wrong place to learn Misplaced Pages rules, or how to review. I think ] is a much better place to do that, but one might also think of specific adoptions or a particular lesson in ].
*December 31: ]
#*From a pure project management point of view, I think there is little doubt that reviews are at least not better than before. But the process has become more difficult. To me, this is added complexity without benefit.
*January 2: ]
#*Finally, I never liked the idea to force anyone to do voluntary work. I know of at least one very prolific DYK writer whose creations often get GA status before DYK, and who does not edit T:TDYK anymore. In this respect, DYK currently is stricter than GA and FAC, and that is not a healthy thing. --] (]) 11:37, 23 July 2011 (UTC)
*<s>January 2: ]</s>
#Gatoclass raises good points at ] and the section above this one. Overall, though, I still think requiring reviews from new editors who aren't interested in reviewing is a net negative. <b class="IPA">]</b>&nbsp;(]) 11:54, 23 July 2011 (UTC)
*January 2: ]
# I think that the inherent conflict of interest may be too strong. Since I started reviewing in May, I have come across quite a few with serious prose or other issues. While many serious reviewers at work, there also seems to me to be a certain 'going through the motions' with reviewing and commenting on the bare minimum criteria. I suspect some reviewers may be afraid of ruffling feathers when their own articles are under review for fear of 'retaliatory' fails, and I suspect that the conflict of interest may be a contributing factor to mediocrity of reviewing. --] (]) (aka Ohconfucius) 15:18, 23 July 2011 (UTC)
*January 2: ]
#Someone asked below if this view could be articulated. Let me try. Even when this was being proposed, I knew it would be a problem in the long run, but anyone who said that risked being seen as just trying to avoid doing the work. So I mistakenly held my tongue. The problem was and is obvious: requiring everybody to review means that there are many weaker reviewers who need to look at something so their articles can be approved. They either haven't yet acquired the skills to review something properly, or just rubber-stamp something to get it over with. Hence why so many crappy articles have been making it through lately. For someone like me, a regular reviewer elsewhere, I can handle such a requirement comfortably. But this isn't necessarily true for everyone. I think there was an assumption that DYK writers would grow into strong reviewers over time, but it just isn't happening. The best thing that could happen to DYK is to remove this requirement and leave reviewing to those who are interested and experienced. It may take longer to get articles through, but it will be worth it. ''']''' (]) 15:48, 23 July 2011 (UTC)
*January 3: ]
*January 3: ]
*January 3: ]
*January 4: ]
*January 4: ]
*January 5: ]
*January 5: ]
*January 5: ]
*January 6: ] (two articles)
*January 6: ]
*January 6: ]
*January 6: ]
*January 6: ]
*January 6: ]
*January 7: ]
*January 7: ] (three articles)
*January 8: ]
*<s>January 8: ]</s>
*January 8: ]
*January 8: ]
*January 8: ]
*January 8: ]
*January 8: ]


Please remember to cross off entries, including the date, as you finish reviewing them (unless you're asking for further review), even if the review was not an approval. Please do not remove them entirely. Many thanks! ] (]) 21:31, 20 January 2025 (UTC)
====mixed====
#


== Edit top section ==
====discussion====
*I have no objection to requiring nominators to do a bit of character-counting and examining of page histories as clerical verification of eligibility. But in the interests of making DYK a bit more of a training ground, I'd be inclined to add a requirement that in addition, they review at least one other point, of their choice, listed in the first RfC proposal. ] ] 04:28, 23 July 2011 (UTC)


I tried to correct a grammatical error but this page doesn't seem to edit like others: "go to article's talk page" should be "go to the article's talk page". ] (]) 15:29, 21 January 2025 (UTC)
*I can't answer as I'm not a DYK regular. But I really like the idea and have debated this with Sandy before and been pretty unsatisfied with the responses. Working scientists who write papers, review them also (not tit for tat, but regularly). I think if someone can write a capable article, he can review one. And I sure get sick of the "build it and it will come" hope that reviewers will descend out of the sky or the begging for more reviewers on FAC talk (or articles not progressing because no one reviewed it). Plus it's fair giveback for people burdening the sytsem. Plus reviewing teaches you things that help with writing! And I think the concerns over poor reviewers are over-rated. We need to use what we have. This is not nuclear code security carefulness...this is content creation...let's get on with it. ] (]) 05:05, 23 July 2011 (UTC)
:I corrected it at ].--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 21:45, 21 January 2025 (UTC)


== DYK's use of the T: pseudo-namespace ==
:: I endorse the above comments by TCO. ] (]) 05:31, 23 July 2011 (UTC)


There is currently a proposal (]) to fully deprecate the T: pseudo-namespace. A significant chunk of the remaining T: pages (]) are related to DYK, including the main ] redirect and redirects to all the preps and queues. Some of these are directly referred to in our ], and in places such as the ]. I've !voted to exclude DYK from the proposed sunsetting, but perhaps we should also think of switching to using TM: shortcuts as standard. ] (]) 16:03, 21 January 2025 (UTC)
:::The other thing is it makes even MORE sense that required reviews make sense at FAC since anyone who can write one of those mofos can more than review one. And one could do an analysis...there are some areas where we are close to tit for tat anyway just in terms of the smallness of the group. Perhaps requiring more reviews would broaden things up. Some times I think people here get entrenched positions from years ago and don't really have an open mind. Like...look GA has done fine with a little plus sign...and that was a big kerfuffle where FA didn't want to allow it. Or like the way the FA reviews are all on one gigantic megapage (no academic journal runs that way) which makes it painful for everuyone other than the scanning director (and prevents getting substantive discussions, like in an academic review.) (No drama/teasing, honest...just my newbie perspective.)] (]) 17:17, 23 July 2011 (UTC)


== What I can't promote ==
*I would like to see someone articulate the "net negative" position. I see some folks in other discussions above say "this has been a failure" but I'm not quite clear on why this is so. And pointing out that during the time that this has been in effect a couple of bad noms slipped through is not sufficient - DYK has come under more and more scrutiny over time so we really don't know how many bad noms slipped through before the implementation of this feature.] (]) 07:19, 23 July 2011 (UTC)
**I'm sure someone will; the big negative to me is that it has enabled the system to deceive itself that proper reviewing is occurring, beyond the merely clerical minima. We should want to ''augment'' it, not remove it, I believe. ] ] 07:36, 23 July 2011 (UTC)
***One of the problems with reviewing in general (not QPQ) is that reviewing can be silent. If people actually put a tick on a checklist, it tells others what got checked. Though you do want some thing double-checked as well, as some aspects need more than one person for a proper check. ] (]) 11:08, 23 July 2011 (UTC)


The nominations that I have participated in and that are not being promoted is getting longer. Here is a list of the oldest ones needing promotion.
:::: It also increases accountability, people can't say "I forgot to check that" or "I didn't know I was expected to do that". They will have to take responsibility for their errors. ] (]) 14:12, 23 July 2011 (UTC)
:]
:::::So are we going to implement the checklist, as suggested ?] (]) 14:37, 23 July 2011 (UTC)
:]
:]
:] ] (]) 02:33, 22 January 2025 (UTC)


== Eye-rolling hook in Q5 ==
:::::: Well, assuming this proposal achieves consensus, yes, that would be the sort of system I would envisage. ] (]) 14:48, 23 July 2011 (UTC)


"''* ... that the discontinuation of ''']''' in the summer of 1939 was unrelated to the ]?''"
==Proposal to replace DYK with new Good article DYKs and demote the current system to a sub page==
My feeling on this is that we should replace did you know of new articles on the main page with did you knows of recently passed good articles. Then I would have a link underneath like in the featured article section, ''more DYKs of recently created/expanded articles'' and then I'd demote the DYK for newly expanded article as it currently appears on the main page to a sub page. This way it gives credit to those who've recently had a good article promotion, general quality on the main page would be much improved without obvious blunders and the often embarrassing did you knows would appear on a sub page and be hidden from appearing on the main page. Given that we just don't have the numbers to ensure the quality hitting the main page is universal the only solution to deal with this problem in my view is to simply stop it from doing so. The problem is we can't paint all DYKs with the same brush. There are some very good DYKs which are new GAs anyway which I've seen today, but to keep that sort of level for every entry would be great in my view. Maybe I'm biased I don't know but the deal with DYKs for me has never been an excitement about it appearing on the main page so I could accept that the current system could be demoted to a sub page and replaced with GA DYKs. The problem is how to accommodate those editors who enjoy creating start class articles and having their articles appear on the front page and to retain the system that motivates them to expand content. I myself would be perfectly happy to see my did you know hooks appearing on a sub page of the main page as page views illustrate a small percentage actually view them anyway.


If you read the article, you learn that the journal folded due to financial shortcomings and published its last issue on ''June 30'' of that year ... about ''two months'' before the Germans invaded. At a time when no one was expecting that to occur, at least not imminently. Hell, if you read the hook and know basic history, your first thought would not be "Well, I'd like to read the article and find out why" but "Who''ever'' would have thought it ''was''?" Just because the war in Europe started on September 1 of that year does not mean ''every event in Poland'' that year, especially those prior to that date (save, of course, the ]) must automatically have ''something'' to do with it.<p>Put it this way: it would be like a hook saying that the cancellation of an American TV show that happened to occur in spring 2001 was "unrelated to 9/11".<p>I could understand, perhaps, if the sources showed that it was a common perception that the journal ''had'' been shut down due to the invasion. But they do not appear to. We do appear to have one source offhandedly saying this, but purely on its own. That's the sort of thing that really shouldn't have made it into the article because of ]-y ness like this.
'''What I propose''' is a nicely designed sub page for new hook DYKs rather like ]'s user page (but tidier in format) linked from the main page and for every hook if possible to have an image by the side and to include more hooks in the list. It would alleviate the pressure and some of the negative comments associated with the main page. Every hook created on a certain day would be listed on this sub page for 24 hours maybe with a 5 day approval period leading up to it. So any proposed and authorised article created today would appear on this list on 28 July and be listed for 24 hours with all others created/expanded on that day. Any which have not been approved within that time period because of issues will be scrapped. This would easy the pressure on those who have to regularly update the main page with new hooks, editors would see their new DYKs featured for much longer than the measly few hours at present and many of the beautiful images which would not appear on the front page because they are not the top entry there would be room to list them all. We could also give it a major revamp and organize DYKs on a page by topic like geography, sport, history, wildlife etc with many colorful images and themes, have thematic days and collaborative drives on certain topic to produce a combined input on any given topic as well as the usual mix and mash we have to make it more enjoyable and challenging. ♦ ] 11:17, 23 July 2011 (UTC)


Pinging {{ping|AirshipJungleman29}} (reviewer) and {{ping|Generalissima}} (creator, who in fairness ''did'' say during ] that they were open to alternate hook ideas. ] (]) 05:27, 22 January 2025 (UTC)
*'''Support'''. DYK is heavily biased towards promoting the mass creation of content in obscure areas, with minimal quality control. Promote ''good'' editing, not ''fast'' editing. --] (]) 11:26, 23 July 2011 (UTC)
*'''Support'''—nice one, Dr. Blofeld, and Mkativerata sums it up well. I'd also support drawing on GAs, FAs, and FLs. DYKs must be from content that contains an interesting, catchy, punchy hook in the first place, and as SandyGeorgia has pointed out, it can easily become forced if you're not selective (the cheap hook). A good proportion of articles at whatever stage or status are just not DYKable, something that has plagued the current DYK model. So changing the scope so it's classier and broader makes a lot of sense—solves a bunch of problems in one go. Everyone knows I'm not a Jimbo groupie, but he has just , having moved from earlier today. ] ] 12:02, 23 July 2011 (UTC)
*'''Strong Oppose''' to this perennial proposal, for all of the same reasons every time this is brought up. Since it's the same small group proposing this over and over, hoping it will eventually stick or wear down the regulars, I feel no obligation to repeat myself for the umpteenth time. If there is a burning need to display not-good-enough-to-be-FA content on the Main Page, propose a new section for GAs ''without'' targeting a useful extant project like DYK for destruction. - ] (]) 12:14, 23 July 2011 (UTC)


:I'm pretty sure there was a much higher volume of Yiddish literature curtailed in Poland after the Nazi invasion than there were American TV shows cancelled after 9/11 <small> also, the invasion happened in the summer, so your comparison doesn't even make sense </small> <small> ] (]) (it/she) </small> 06:57, 22 January 2025 (UTC)
::I didn't say DYK would be destroyed. To accommodate those who enjoy contributing new articles for DYK and being credited I think that it should be kept but demoted to a sub page, if anything it could be a big page of hooks just like the DYK nom page is right for those who are interested in viewing new articles. But I believe that articles which have been shown to be poorly reviewed and many containing a plethora of problems are not front page worthy even if for just a few hours. I believe the front page should be reserved solely for the cream of wikipedia. We need to clean up our act and deal with this.♦ ] 12:21, 23 July 2011 (UTC)
:::Instead of speling the death-knell of DYK, this proposal could be the beginning of a brilliant future of DYK, in the form of a DYK portal linked to from the main page and other portals and templates; it will be a portal where content can be displayed in full glory, instead of one-line hooks, images and other embellishments will be permitted. I see repeated mentions that DYK isn't broken and doesn't need fixing, but this seems to be ] of the problems that Sandy and many others have clearly identified and elaborated on; supporters have not come up with satisfactory answers nor ways of dealing with the issues, which continue to recur on a regular basis; they therefor feel like they are being bludgeoned by repeated retabling of similar proposals. ''That'' is the real reason that this proposal is perennial; it's not the fault of the proposers. ] (]) (aka Ohconfucius) 16:15, 23 July 2011 (UTC)
*'''Support''' This proposal would see a measurable improvement in the content of the main page, and show readers (and potential contributors) what writers should be aiming for. ] (]) 12:19, 23 July 2011 (UTC)
*'''Strong oppose'''. Most of what is used in DYK could never reach GA simply because the sources aren't there. If we were to limit DYK to GAs, systemic bias would rear its ugly head immediately; if FAs, FLs, and GAs, we'd be invading on TFA and TFL's turf, which could theoretically cause major conflict. This is not the way to improve DYK. Quality control may need to be improved, but not to GA-level standards; GA length alone would preclude many otherwise sound DYKs from reaching the main page. ] (]) 12:20, 23 July 2011 (UTC)
::Did you not read the proposal? I have not proposed to scrap new article/expanded DYK. Rather to keep them off the main age when they are often poorly reviewed and reserve the main page purely for reviewed material. As I've said there could be a direct link from the main page for new DYK articles on a smart looking sub page.♦ ] 12:23, 23 July 2011 (UTC)
:::I did read the proposal, but a sub-page is not the main page itself. We'd be expecting interested readers to click on one link to open the subpage, then another to choose the article they want to read. Effectively, we'd lose around 50 to 80% of our readership. ] (]) 12:28, 23 July 2011 (UTC)
*'''Oppose''': I like the multicultural flavour of DYK, written by many for whom English is a second language, covering a broad range of interests. I don't envision that quality for GAs. The opposite might work: have a subpage on GAs. --] (]) 12:22, 23 July 2011 (UTC)
::I like it too, but is it really a good idea to have poorly reviewed material with problems hitting the main page in the eyes of millions on a daily basis?♦ ] 12:25, 23 July 2011 (UTC)
:::The "millions" would only see the hook. Less than 100k would actually have any exposure to the sub-par articles themselves. As for Gerda's idea, I'd support such a motion. A mix of new DYKs and recently promoted GAs may be acceptable too. ] (]) 12:30, 23 July 2011 (UTC)
::::For some reason I fail to see the multitude of poorly reviewed poorly written DYK. I reviewed more than 80 this year, only 4 had to be rejected. I hope they were reviewed well, smile. I keep a collection of ], didn't see a single bad one there. I also collect ], same thing. --] (]) 12:40, 23 July 2011 (UTC)
:::::Respected editors such as Sandy Georgia claim to have never seen a DYK set without multiple issues. I think she knows what she is talking about. I regularly see articles hit the main page with suspect sources, POV and needing a jolly good copyedit even if many of them are absolutely fine. The problem is there is an inconsistency and I think the main page should not be inconsistent.♦ ] 12:56, 23 July 2011 (UTC)
::::::How about accepting the fact that man is inconsistent? --] (]) 13:02, 23 July 2011 (UTC)
:::::::Accepting that should not be used as an excuse not to progress and improve. Improving the quality of the content that appears on the main page certainly sounds like a good idea to me. ] (]) 13:12, 23 July 2011 (UTC)
*'''Oppose''' I'd prefer other options of solving the problem raised by Dr. Blofeld. Extending the scope of DYK to also include new GA's and FA's ect but not removing new content altogether. Extending the timeframe from 5 days to about a month to allow for more scrutiny. ] (]) 12:34, 23 July 2011 (UTC)
:New content would be featured on a sub page linked from the main page and would allow more room for multiple photographs and some additional features which at present cannot be presented on the main page because of its restrictions. This proposal is not to entirely scrap new DYKs, just keep poorly reviewed articles off the main page.♦ ] 12:38, 23 July 2011 (UTC)
::Baby with bathwater ... Out of sight out of mind. New articles do benefit from mainpage exposure. Therefore I do dislike the subpage idea. ] (]) 12:44, 23 July 2011 (UTC)
:::Actually if you compare DYK page views and main page views an extremely small percentage actually visit the articles.♦ ] 12:46, 23 July 2011 (UTC)
::::True. But from my experience with ] there is a spinoff and that would be severely reduced by having an extra page inbetween. ] (]) 12:56, 23 July 2011 (UTC)
====Arbitary break ====
*'''Oppose''' for all the reasons stated above.] (]) 12:40, 23 July 2011 (UTC)
*'''Torn'''. I think something like 3 GAs per day in the same space as DYK would make sense. "Today's Good Articles". I would want a director(s) like person(s) to pick them and would draw from the whole bank, not from new ones only. Think the implicit named difference (and lower down and 3 versus 1) makes it clear to reader that articles are not as polishd as TFA. but good to show some (still strong) difference of article quality on Wiki. We could have some proposal thing on the side like TFAR, but that is just mechanics. (KISS though.) The only bad part of this is it basically blows up DYK and takes their main page space away from them. And hurts the individuals who like DYK. And I really don't mind if we just leave DYK in place for avoiding hurt feelings from blowing it up.] (]) 12:55, 23 July 2011 (UTC)


== ] ==
*'''Oppose''' The current DYK process works well enough and so doesn't need fixing. If GAs feel the need for some love too then maybe we could add achievement of GA status as a qualification to appear in the DYK queue. ] (]) 13:13, 23 July 2011 (UTC)
::Sorry but I don't think it is working well enough, even many of the most active DYK contributors and operators including myself claim it is not like it used to be or has problems and I think if we created a DYK Hall of Shame it would expose that there is a problem which exists. I personally have felt under pressure recently from DYK operators like MaterialScientist in regards to sourcing and standards and quite rightly and I'm not the only one. Do you realize how many complaints there have been in the last month alone about certain articles hitting the main page? Of course there are many regular DYK contributors who work incredibly hard at producing quality and interesting new content but its got to be said that to some it has almost become a sort of game and that the notch on the board is more important than the article itself.♦ ] 13:36, 23 July 2011 (UTC)


===]===
*'''Support'''. The current system is broken and doesn't deserve to be on the main page. A radical change has to be made. ] (]) 13:18, 23 July 2011 (UTC)
{{yo|Yue|Jeromi Mikhael|Hilst}} Article and hook attribute, source doesn't.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:17, 22 January 2025 (UTC)
*'''Support''' At what point will people realize that incentivising new content might not be our ''top'' priority anymore? When we have 10 million articles, 20 million, 50 million? Articles on previously not covered content are always a good thing, but ''quality'' content on any subject we cover should be a priority, especially now that have over 3.6 million articles. I don't think this proposal will destroy the incentive for new content. What it does is create incentives for people to improve current content, and/or to create new content with the goal of making it top quality instead of simply making it passable enough to get another notch on the old DYK belt.] (]) 13:36, 23 July 2011 (UTC)
:*Just because something isn't our ''top'' priority doesn't mean that we shouldn't be proud of our new articles. Getting some of them on the main page, even for a few hours, generates interest and may lead to more editors signing up to create articles. ] (]) 13:46, 23 July 2011 (UTC) :It does. "With distinctive bay windows that expand the floor space of the second storey, the Sam Kee Building was recognized by Guinness World Records as the narrowest commercial building in the world." ] (]) 19:54, 22 January 2025 (UTC)
*'''Oppose''' this half-baked idea, and for the umpteenth time, why do some users feel the need to continually start polls when there hasn't been any preceding discussion? Polls are supposed to occur at the ''end'' of a discussion, not the start. ] (]) 13:47, 23 July 2011 (UTC)
::Well for such a "half-baked idea" I count at least 5 problems it would solve in one go.♦ ] 13:53, 23 July 2011 (UTC)
*'''Support'''. I'd also link the new-content-DYK subpage with the new "interested in contributing?" section I hope we'll see on the Main Page. These would be candidates for improvement and expansion. At the end of the day, the act of creating a new article carries one of the highest intrinsic rewards, I think; and therefore rewarding this action further with Main Page exposure like now never made much sense to me. A subpage is a bit of a compromise, allowing the system to persist but with less use of scarce Main Page space. Also worth noting that a lot of the problems with DYK-as-is may be traced, I think, to over-incentivising. Over-incentivise something (like easily measurable quantity) and you inevitably under-incentivise something else (like hard-to-measure quality). ] <sup>]</sup> 13:51, 23 July 2011 (UTC)
*'''Strong Oppose'''. I have participated in GA and in DYK. Of both of these, I have enjoyed DYK far more. The "drug" of seeing a DYK through a new article is enhanced by my involvement in topics completely new to Misplaced Pages. Edit for edit, DYK was more satisfying, fruitful than any GA I wrote or reviewed. DYK motivated me to search for interesting new facts which were new in Science but not on Misplaced Pages. The resultant stub often hosted more information than the solitary source contained. On occasion, when the authors of the papers from which the facts were taken were contacted, some awaited the DYK keenly and responded by adding images and providing more references, ] being a case in point. In the case of ], two Flickr authors with restricted licensing & changed their licensing to allow me to upload their images for the DYK stubs. From my point of view, the DYK mechanism promoted me to deveop quality stubs. It is highly doubtful whether I would have got involved with DYK through GA or had a fraction of the pleasure. GA does not need DYK to incentivise it, but new articles and stubs do. The problem here is not with DYK or with the new articles per se as it is with the system or the actions of individual editors. Trying to solve that particular problem by switching from new articles to GA, or develop hybrid systems, is akin to throwing out the baby with the bath-tub. If GA needs to be revitalised and brought to the Main Page, a different scheme may be used which adds another box for highlighting GAs in a different manner. As such, I am in favour of correcting the problem in DYK, retaining the existing system and not in fundamentally changing its nature in any way to do away with the problem. ] (]) 14:12, 23 July 2011 (UTC)
*'''Oppose''' - not every article is meant to be a GA. How do you make a 1500 character article into a GA anyway (that's for those who opposed my proposal to up the char limit)? I can also see this dragging GA standards down while failing to drag DYK standards up. Add GAs to the main page but not replace.] (]) 14:29, 23 July 2011 (UTC)
*'''Support''' in general anything that gets DYK off the mainpage, but I suspect instead that we'll be back here another year from now, still looking at enablers and denialists still putting copyvio, BLP vios and faulty sourcing on the mainpage. ] (]) 14:42, 23 July 2011 (UTC)
*'''Oppose'''. Until the the], Misplaced Pages's going to continue to need expansion in terms of breadth as well as depth. FA and GA serve a valuable purpose by encouraging the latter; DYK encourages the former. Both should be represented on the main page. Several reasonable proposals for increasing quality control have been made on this page in the past 24 hours, and so far most of SandyGeorgia's complaints appear to focus on the closely-paraphrased contributions of a single editor. I don't feel like we're facing an insurmountable problem here. -- ] (]) 14:57, 23 July 2011 (UTC)
::I don't see how moving DYK to a sub page and replacing it on the main page with better GA articles would suddenly disrupt wikipedia's breadth or potential. If all that motivates editors to expand articles is a brief view on the main page there is something wrong. Yes, we do need editors building up stubs but what proportion of articles are still stubs? If we ''really'' want to do something about that then losing DYK for new articles on the main page will make little difference. In replacement we need something which will give editors more encouragement than ever before to expanding existing content.♦ ] 15:07, 23 July 2011 (UTC)
::: Blofeld, c'mon, do you really need to ] every oppose vote here? But to reply to your concerns anyway, my experience is that the promise of having other immediate eyes on an article is 1) an added motivation to create it; 2) an added motivation to do it well; and 3) provides an extra round of article improvement when that new article does hit the main page. You say that's a bad reason for me to be writing, but I'd argue we have to accept that not all Misplaced Pages editors do this through perfect altruism; sometimes we do it because it's fun. For me, getting that immediate feedback and exposure (which the current, hopelessly backlogged GA system doesn't provide) is part of that fun, and also a key part of improving what I'm writing. -- ] (]) 15:54, 23 July 2011 (UTC)
* '''Support'''. Too many inherent qualitative problems with DYK that the simplest 'fix' is to replace it with a more proven quality mechanism. ] (]) (aka Ohconfucius) 15:28, 23 July 2011 (UTC)
:::Speaking as a DYK contributor myself, the increasing pressure of late and negative press about hooks and quality of text/sources had made me seriously address what is going on. It largely comes down to the fact that many editors, myself included believe the main page should be representative of our best content and standards. There's no denying we regularly have articles hitting the front page which are cringeworthy and should never have got through. The fact remains that we just do not have the numbers to maintain the sort of universal quality that many expect of the main page. If we simply moved it to a sub page linked from the main page, sure we might lose 50% at least of people viewing the articles but it would alleviate the pressure on editors. My feeling is that if we moved to a sub page we could give the whole thing a revamp and customize it and make it more fun that it ever was before. We could even split it into subjects like geography, wildlife, sport etc and have different themed days or collaborative drives on certain topic to make it more fun. Do DYK contributors ''really'' care about their article being on the main page for three hours? I most certainly don't, what I enjoy is working with other great editors and expanding stubs into something half decent and having a log I can look back over and choose the best ones to develop into GAs.♦ ] 15:48, 23 July 2011 (UTC)
::::While all editors may not feel the same, I do feel the pleasure and pride of having a DYK on the Main Page. ] (]) 16:09, 23 July 2011 (UTC)
'''Comment'''. Dr Blofeld has canvassed for opinions on his proposal from talk page watchers at . Possibly he has also made similar approaches to people who are not quite so keen to see the DYK part of the mainpage re-used for more thoroughly audited content, or possibly he forgot to do so. If the latter, then it might be a good idea to assist in that. --] (]) 16:24, 23 July 2011 (UTC)
:::Rubbish. I was talking to Sandy about this issue anyway and said I'd let her know when I propose something. If I was going to canvass everybody I'd go to talk pages such as Iridescent, Malleus, Giano, Hans Adler, anybody who has expressed disgust of DYK. If these people really want to vote oppose! or support! then they'll do so regardless. In fact I have informed some people about this who would like strongly oppose me.♦ ] 17:08, 23 July 2011 (UTC)
::::Letting her know is one thing; also making a specific appeal to her talk page watchers, as you did, is quite another. --] (]) 18:09, 23 July 2011 (UTC)
*'''Strong Oppose'''. As stated in countless prior votes, DYK serves a vital and valuable purposes. In addition to promoting the creation of content (which remains today and will remain for many years a needed function), the DYK process encourages new editors and is the best forum for the widest base of editors to get their content featured (even if briefly) on the Main Page. As a Misplaced Pages newbie four years ago, someone took an article I created and nominated it for DYK (which I didn't even know existed). I thought that was a nice gesture and it served as a pat on the back. I am sure it has served a similar encouragement for hundreds (probably thousands) of other editors. It seems as though there is a group who comes back here every few months with a new proposal on dismantling DYK, citing one or two errant hooks (out of hundreds) to support that goal. In response, DYK supporters (myself included) seem timid in defending what is an incredibly good and valuable part of the project. I love DYK and oppose all of these efforts to dismantle, destroy, or dilute it. Timid no more. Alliterative and loud in my support of DYK. ] (]) 16:29, 23 July 2011 (UTC)
::How exactly are dull as dishwater factoids such as "...Karen Stollznow writes for two skeptical magazines (Skeptic and Skeptical Inquirer) and hosts two skeptical podcasts (Point of Inquiry and Monster Talk)" or "...a small single-runway airport serves Kapoeta South County in the Greater Kapoeta region of South Sudan" supposed to encourage people to contribute to Misplaced Pages? Are they supposed to be inspired by banality or is it the low standard of article as highlighted by SandyGeorgia? ] (]) 17:36, 23 July 2011 (UTC)
:@Cbl62 4.8 million people on average visit main page daily. Few DYK articles get more than 2000 hits. if you do the maths roughly 2499 out of every 2500 ignore DYK. Doesn't that concern you? I've contributed a high number of DYK article and I can count those who actually expand them with meaningful content beyond basic edits when they hit the main page on one thumb. There is an extremely high percentage who couldn't care less about our DYK feature as they choose to ignore it and search for whatever they want. The stats speak for themselves.♦ ] 17:41, 23 July 2011 (UTC)
*'''Support''' - DYK material on the front page needs to be of the highest quality, and isn't that what the GA process is for? Adopting this proposal would ensure higher DYK quality, and increase the attention on the GA process. I suggest that DYK simply be a follow-on step to the GA process: when an article achieves GA, a hook from it goes into DYK. --] (]) 17:49, 23 July 2011 (UTC)


===]===
== Multiple RFCs confusing, simply remove DYK from the mainpage==
{{yo|AstrooKai|SL93|Royiswariii}} As far as I can tell, the promoted hook was explicitly rejected on interestingness grounds, and I think quite rightly.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:17, 22 January 2025 (UTC)
There are at least five RFCs running now on DYK, so I can't endorse the idea of weighing in on any one of them specifically. What is abundantly apparent is that the DYK regulars who endorse the poor quality they are putting on the main page are doing so because they truly do not understand Misplaced Pages's sourcing policies or copyvio. DYK does *not* have enough knowledgeable editors to prevent the daily debacles that have been occurring for over a year, and DYK is encouraging editors who never improve their skills to the GA or FA level to plagiarize, commit copyvio, violate BLP, and put up articles based on blogs and other non-reliable sources. It is not a service to Misplaced Pages, as we no longer have enough editors to clean up the deficient content these editors create. Good and able editors do use DYK, but those editors will go on to get GAs and FAs, while those who never improve their editing knowledge beyond the rudimentary level of DYK continue to fill Misplaced Pages with content that violates our policies. There is no solution to DYK: this discussion has gone on for years, and many of the regulars here are tone deaf.
:That's true. I only approved the first hook. ] (]) 19:36, 22 January 2025 (UTC)


===]===
Remove DYK from the main page, period. We have plenty of other options that can take that space, and we can use those where editors improve the quality of our articles rather than churning out hundreds of deficient articles that DYK regulars don't even recognize as deficient.
{{yo|TheLonelyPather|Toadspike}} The hook is contradicted elsewhere in the article; it says she published the book "in 1908, when she was sixteen years old" but the article claims she was born in 1893, which would make her 14 or 15.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:17, 22 January 2025 (UTC)


:@] I'm guessing this is down to ], which adds a year or two. ] </span>]] 19:22, 22 January 2025 (UTC)
* '''Support'''. ] (]) 14:09, 23 July 2011 (UTC)
::In my opinion, this is not an error, and the hook can run as-is. However, we can also add a footnote to the article clarifying the Chinese age counting system once TLP has confirmed that the dates and ages accurately reflect the sources. ] </span>]] 19:26, 22 January 2025 (UTC)
:::I think adding a footnote would be an excellent idea.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:29, 22 January 2025 (UTC)
::::I support a footnote. ] (]) 20:18, 22 January 2025 (UTC)


===]===
* '''Strong oppose'''. Vide the reasons I gave in previous RFC. ] (]) 14:17, 23 July 2011 (UTC)
{{yo|An anonymous username, not my real name|Ornithoptera}} Where's the hook?--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:17, 22 January 2025 (UTC)
*'''Oppose'''. If Dr. Blofeld's suggestion above was likened to throwing the baby out with the bathwater, this is throwing all the interior plumbing as well. Working to improve DYK (and perhaps participating in some reviews) would be much more effective than sensationalistically suggesting it be scrapped altogether. ] (]) 14:13, 23 July 2011 (UTC)
*'''Oppose''' and while I'm at it, how many FA's exactly did Rlevse manage to score and over what period of time before the oh-so-vigilant regulars at FAC noticed that ''he'' was a serial "close paraphraser"? Just curious. ] (]) 14:23, 23 July 2011 (UTC) :"Eoscorpius was placed in the newly erected family Eoscorpionidae by American paleontologist Samuel Hubbard Scudder in 1884. While other experts of the time, such as Ben Peach, considered the genus to be hardly different from modern scorpions, Scudder believed that it was sufficiently distinct to warrant the creation of a new family." ] (]) 19:37, 22 January 2025 (UTC)
::@], for some reason, this hook wasn't picked, even though Ornithoptera explicitly preferred it. Is it possible to change it? — ''''']''''' 19:40, 22 January 2025 (UTC)
* '''Oppose''' A proposal without an obvious rationale other than to get rid of that annoying DYK section, or that is how it comes over. Some of those RFCs that are being derided look like coming to useful conclusions (I'm actually a little surprised that's the case) that should improve the process and are generating more light than heat, which is a nice change. ] (]) 14:25, 23 July 2011 (UTC)
* '''Oppose''' Overblown and per Gatoclass.] (]) 14:31, 23 July 2011 (UTC) :::ALT1 is fine by me. I wasn't sure if there was a preference because both hooks were approved. ] (]) 19:41, 22 January 2025 (UTC)
:::"British geologist Ben Peach expressed regret that the name Eoscorpius was given to a genus so similar to modern scorpions, speculating a much earlier origin for scorpions as a group." for ALT1. "Ben Peach, considered the genus to be hardly different from modern scorpions" for ALT0. ] (]) 19:51, 22 January 2025 (UTC)
* '''Strong oppose'''. DYK has an important mission; several reforms are in motion; and per Gatoclass. -- ] (]) 14:42, 23 July 2011 (UTC)
*'''Support'''. It's quite obvious that DYK has been getting worse, not better over the years, and it shows no real signs of accepting the need for improvement. Time to scrap it; Misplaced Pages doesn't need ''more'' articles, it needs ''better'' articles, and DYK is the antithesis of that. ] ] 16:29, 23 July 2011 (UTC)
*:In the field of Science, that is certainly not the case that we have adequate number of articles, imho. ] (]) 16:31, 23 July 2011 (UTC)
*::And how many science DYKs have you seen? There isn't even one on the main page right now for instance, so it seems disingenuous for you to argue that DYK encourages the production of new science articles. If there is a lack of such articles, as you claim, then that seems to be yet more evidence that DYK isn't working. ] ] 16:44, 23 July 2011 (UTC)
:::You just missed ] being on the main page by a few minutes.] (]) 17:28, 23 July 2011 (UTC)
*'''Oppose'''. Strong supporter of DYK per my comments in the proposal above, which also seeks to dismantle DYK. ] (]) 16:34, 23 July 2011 (UTC)
*'''Support'''. ] (]) 17:06, 23 July 2011 (UTC)
*'''Oppose''' I think it's been demonstrated that there are problems, but reform is the way to go, rather than scrapping the program. Let's work towards that goal. ] ] 17:12, 23 July 2011 (UTC)
*'''Support''' Advocates of the current format assert that it encourages new editors, but apparently without consideration. If the purpose of DYK is encourage new contributors, a well-written article is more likely to encourage faith in Misplaced Pages and get people involved that the examples of poor work SandyGeorgia has highlighted. More over, having poor articles on the front page might create the impression that such standards are not just acceptable but encouraged as by appearing on the front page an article appears to have been endorsed by the Misplaced Pages community. If DYK cannot be reformed then it needs to be scrapped. ] (]) 17:28, 23 July 2011 (UTC)
*'''Comment'''. Misplaced Pages regularly has articles that don't live up to our standards. If we were realiou trulio serious, we would not publish the stuff and wait until it was more finished. Like a normal website. And people see them all the time, people Google into the 'pedia WAY more than using the main page (adding all the article views). Now, I can consider a view that the MP should be a standard setter, etc. But that's a subtley different issue.] (]) 17:51, 23 July 2011 (UTC)
*'''Strong Oppose'''. There is an increasing drive to drive new content and new editors away. This idea is one of them. We should rather be thinking on how to capture the willingness of people and looking for ways to include them in the process. ] (]) 18:40, 23 July 2011 (UTC)
*'''Oppose''' DYK does have problems, but I trust that some of the reform ideas will really end up benefiting the project. ] (]) 18:43, 23 July 2011 (UTC)


===]===
== Messiah Part II ==
{{yo|UndercoverClassicist|Zeete}} Article and hook attribute, source doesn't.--<span style="background:#FF0;font-family:Rockwell Extra Bold">]]]</span> 19:17, 22 January 2025 (UTC)


:It's in the St. Clair source, cited in both: {{green|"Among those who contributed to the debate in the local Athenian press was L. Kaphtantzoglou, who described the tower as Turkish, and compared it to the droppings of birds of prey."}}. This is ], who was a Greek academic. '']'' <sup>]·]</sup> 19:43, 22 January 2025 (UTC)
From discussion to work: I have an admittedly unusual nomination running for ] which might profit from more eyes. I will be off for now. --] (]) 13:08, 23 July 2011 (UTC)
:It does. "Was everything built on the Acropolis between ancient and modern Hellas to be regarded as a temporary intrusion? Among those who contributed to the debate in the local Athenian press was L. Kaphtantzoglou, who described the Tower as Turkish, and compared it to the droppings of birds of prey." I had to scroll down to page 494 because the search option didn't work. ] (]) 19:49, 22 January 2025 (UTC)
:As the first reviewer of this article, I would like to second the request for more eyes and opinions. Thank you. ] (]) 13:15, 23 July 2011 (UTC)


== ] ==
==Billy Hathorn==


===]===
Since several recent articles submitted by this user have been found to include examples of ], all his submissions will need to be thoroughly checked against their sources before being promoted. As a precautionary measure I have tagged all his current submissions at T:TDYK while this issue is under investigation. ] (]) 15:19, 23 July 2011 (UTC)
:Agreed. Two articles need to be removed (from the queues and preps respectively) for double checking, as I've mentioned above. ] (]) 15:27, 23 July 2011 (UTC) {{u|Di (they-them)}} {{u|Cremastra}} {{u|Hilst}} I don't see why "humanity's cradle" was used rather than "Cradle of Humankind". ] (]) 20:14, 22 January 2025 (UTC)


:: I've done that, and returned them to the top of T:TDK until someone finds time to check them. ] (]) 15:44, 23 July 2011 (UTC) :I just used a descriptive phrase rather than the actual title to create intrigue. ] (]) 20:15, 22 January 2025 (UTC)
::I'm not sure how I feel about using a descriptive phrase for it, but I will see what others think. ] (]) 20:16, 22 January 2025 (UTC)
:::Just a fancy form of a name that was pretty poetic in the first place. Some wordplay is allowed. ] (]) 20:42, 22 January 2025 (UTC)
:::Either one is fine by me. – 🌻 ] (] &#124; ]) 20:57, 22 January 2025 (UTC)
::::Thanks for the input. ] (]) 20:59, 22 January 2025 (UTC)


===]===
== Lost picture for promoted hook ==
{{u|Generalissima}} {{u|EchetusXe}} The article says "in late 1452 or early 1453", but the hook says "in 1453". ] (]) 20:14, 22 January 2025 (UTC)


:Rephrased the article portion a bit - the eruption may have occurred in either year, but the cooling occurred in 1453. <small> ] (]) (it/she) </small> 20:24, 22 January 2025 (UTC)
So the picture associated with my hook got lost in the move from the suggestions page to the prep area. I know that there are more picture hooks nominated than there are spots, but I don't often nominate hooks with pictures (this would be my second with a picture) and was looking forward to this one, and I'd like to draw attention to the nanotechnology/history of science areas which (I think) are not usually as well represented on DYK. I don't know what the etiquette is surrounding this and I don't want to unilaterally promote my own article; would it be permissible to return the hook to the suggestions page, or even move the hook to an empty prep area with the picture? On the other hand, if there was some problem with the picture making it less suitable please let me know. The hook in question is . Thanks. ] (<sup>]</sup>⁄<sub>]</sub>) 18:31, 23 July 2011 (UTC)
::That works for me. ] (]) 20:25, 22 January 2025 (UTC)

Latest revision as of 20:59, 22 January 2025

Error reportsPlease do not post error reports for the current Main Page template version here. Instead, post them to Misplaced Pages:Main Page/Errors. Error reports relating to the next two queues to be promoted can also be posted to ERRORS. If you post an error report on one of the queues here, please include a link to the queue in question. Thank you.
DYK queue status

There are currently 7 filled queues – all good!

Earliest time for next DYK update: 00:00, 23 January 2025 (UTC)

Current time: 22:04, 22 January 2025 (UTC)

Update frequency: once every 24 hours

Last updated: 22 hours ago( )
Did you know?
Introduction and rules
IntroductionWP:DYK
General discussionWT:DYK
GuidelinesWP:DYKCRIT
Reviewer instructionsWP:DYKRI
Nominations
Nominate an articleWP:DYKCNN
Awaiting approvalWP:DYKN
ApprovedWP:DYKNA
April 1 hooksWP:DYKAPRIL
Holding areaWP:SOHA
Preparation
Preps and queuesT:DYK/Q
Prepper instructionsWP:DYKPBI
Admin instructionsWP:DYKAI
Main Page errorsWP:ERRORS
History
StatisticsWP:DYKSTATS
Archived setsWP:DYKA
Just for fun
Monthly wrapsWP:DYKW
AwardsWP:DYKAWARDS
UserboxesWP:DYKUBX
Hall of FameWP:DYK/HoF
List of users ...
... by nominationsWP:DYKNC
... by promotionsWP:DYKPC
Administrative
Scripts and botsWP:DYKSB
On the Main PageT:DYK
Main Page errorsWP:ERRORS
To ping the DYK admins{{DYK admins}}
Shortcut
Archiving icon
Archives
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37, 38, 39, 40
41, 42, 43, 44, 45, 46, 47, 48, 49, 50
51, 52, 53, 54, 55, 56, 57, 58, 59, 60
61, 62, 63, 64, 65, 66, 67, 68, 69, 70
71, 72, 73, 74, 75, 76, 77, 78, 79, 80
81, 82, 83, 84, 85, 86, 87, 88, 89, 90
91, 92, 93, 94, 95, 96, 97, 98, 99, 100
101, 102, 103, 104, 105, 106, 107, 108, 109, 110
111, 112, 113, 114, 115, 116, 117, 118, 119, 120
121, 122, 123, 124, 125, 126, 127, 128, 129, 130
131, 132, 133, 134, 135, 136, 137, 138, 139, 140
141, 142, 143, 144, 145, 146, 147, 148, 149, 150
151, 152, 153, 154, 155, 156, 157, 158, 159, 160
161, 162, 163, 164, 165, 166, 167, 168, 169, 170
171, 172, 173, 174, 175, 176, 177, 178, 179, 180
181, 182, 183, 184, 185, 186, 187, 188, 189, 190
191, 192, 193, 194, 195, 196, 197, 198, 199, 200
201, 202, 203, 204

• 2011 reform proposals
• 2020 RFC LT Solutions
• All RfCs
• Removed hooks: 2023–24


This page has archives. Sections older than 5 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present.

This is where the Did you know section on the main page, its policies, and its processes can be discussed.

Back to 24 hours?

@DYK admins: As of this moment, we've got five filled queues. If we can fill another two queues before midnight UTC (eight hours from now), we'll keep running 12 hour updates for another three days. Otherwise we're back to 24. RoySmith (talk) 16:06, 2 January 2025 (UTC)

I've promoted one more, but don't think I'll have time for the last one. ♠PMC♠ (talk) 21:50, 2 January 2025 (UTC)
Thanks. I'm working on Queue 5 right now, so we're good to keep going until 0000 6 Jan UTC. RoySmith (talk) 22:03, 2 January 2025 (UTC)
And somebody needs to back-fill the holes that got left in Queue 3 after various yankings. RoySmith (talk) 22:04, 2 January 2025 (UTC)
@DYK admins: just to make sure everybody is aware, we're going to extend 12-hour mode (at least) another 3 days now that we have 7 full queues. We do have quite a backlog to dig out of. By my count, we've got 165 approved hooks, and there's another GAN review drive that just started so I expect another big influx of nominations. I expect it'll take us several more 3-day sprints to get back to normal and it'll be less disruptive to keep them going back-to-back vs flitting back and forth between modes. RoySmith (talk) 22:28, 2 January 2025 (UTC)
So long as queue 3 is filled by midnight and the two date requests in queues 4 and 5 are suitably kicked back, I have no valid objections.--Launchballer 22:38, 2 January 2025 (UTC)
I filled one of the holes in queue 3. RoySmith (talk) 23:11, 2 January 2025 (UTC)
I'm getting confused as to where the SOHA hooks need to go; anyone able to get their head around it? ~~ AirshipJungleman29 (talk) 13:11, 3 January 2025 (UTC)
5 and 6 January, but they're already there. Brain fog is brain fogging, clearly.--Launchballer 13:31, 3 January 2025 (UTC)
As a reminder, WP:DYKSO says The reviewer must approve the special occasion request, but prep builders and admins are not bound by the reviewer's approval. The relevance to this discussion is that keeping the queues running smoothly is a higher priority than satisfying special date requests. I'm all for people putting in the extra effort shuffling hooks around to satisfy SOHA requests, but we can't let "perfect" get in the way of "good enough". It would have been a mistake to force a change to the update schedule because of SOHA. RoySmith (talk) 14:32, 3 January 2025 (UTC)

5 January

We need one more queue to get filled in the next 8 hours to keep going with 12 hour mode RoySmith (talk) 16:20, 5 January 2025 (UTC)

I can take the next one if no-one else does in the next five hours. I'd need more eyes on the Tyler hook though.--Launchballer 16:36, 5 January 2025 (UTC)
Doing, although Glucoboy in prep 6 looks interesting and I might swap it and Tyler to avoid outsourcing. I'll make that decision after in nine articles' time.--Launchballer 21:43, 5 January 2025 (UTC)
Another six sets of 12 hour mode it is.--Launchballer 00:03, 6 January 2025 (UTC)

8 January

@DYK admins: We've got about 10 hours left in the current sprint. There's only 4 queues filled right now; unless we get 3 more filled today, we'll go back to 24 hour sets at 0000Z. By my count, we've currently got 156 approved hooks, and there's still that GA backlog drive going on, so I would expect another influx of nominations from that. RoySmith (talk) 14:47, 8 January 2025 (UTC)

I see you and @Hilst: have queues 1 and 2 in hand. If no-one else does prep 3 in the next four hours, I'll take it.--Launchballer 17:40, 8 January 2025 (UTC)
I took it. Next decision to be made on 11 January. ~~ AirshipJungleman29 (talk) 18:00, 8 January 2025 (UTC)

11 January

@DYK admins: we're down to 127 approved hooks, which is great progress, but still above the threshold for another sprint if we can get 4 queues filled in the next 8 hours. RoySmith (talk) 15:51, 11 January 2025 (UTC)

I'll take the next one.--Launchballer 15:59, 11 January 2025 (UTC)
@RoySmith: I've queued prep 6 and can probably do prep 1 this evening.--Launchballer 17:39, 11 January 2025 (UTC)
I did 7 (which, by the way, was totally clean, which made it easy). RoySmith (talk) 18:22, 11 January 2025 (UTC)
I'll take 1 once I've cooked.--Launchballer 19:00, 11 January 2025 (UTC)
Doing now.--Launchballer 20:06, 11 January 2025 (UTC)
And the last one's all yours.--Launchballer 21:42, 11 January 2025 (UTC)
I'm assuming somebody else will step up. This is a team effort. RoySmith (talk) 22:04, 11 January 2025 (UTC)
Sorry, would do but am annoyingly indisposed. ~~ AirshipJungleman29 (talk) 23:51, 11 January 2025 (UTC)
Someone needs to update User:DYKUpdateBot/Time Between Updates as it's protected.--Launchballer 00:11, 12 January 2025 (UTC)
OK, I've put us back to 24 hour mode. I think this was the first time we've tried the "3 day sprint" thing and from what I can see, it worked well. We ran for 12 days, knocked the backlog down from (I think) 165 to 128, and always knew where we were. No more panic when the queues ran down to empty. So, good job everybody. I haven't been keeping careful track, but I think Launchballer probably gets the prize for most sets promoted to queue during this.
My guess is we'll need to run some more sprints in the near future as the GA review drive throws more work our way. But for now, we get to stand down and get some more rest. RoySmith (talk) 00:53, 12 January 2025 (UTC)

We are now back to a significant backlog. SL93 (talk) 02:07, 17 January 2025 (UTC)

@SL93 We need more @DYK admins: to keep the queues filled, and then we could go back to 12 hour sets. If you're willing to help out in that department, I'd be happy to nominate you for WP:RfA. Or, if you prefer, I could just give you WP:TPE. RoySmith (talk) 02:37, 17 January 2025 (UTC)
RoySmith I thought that I needed to meet "The editor should have made at least 150 total edits to the Template and Module namespaces." for TPE. We also don't have that many prep builders so I wouldn't want to stop helping fill preps just so that I could promote them to queues. SL93 (talk) 02:41, 17 January 2025 (UTC)
I see now that template namespace also refers to DYK nominations. I should have figured. SL93 (talk) 02:59, 17 January 2025 (UTC)
Just for the record, I've granted WP:TPE to SL93. It'll be good to have more hands working the queues! RoySmith (talk) 15:40, 17 January 2025 (UTC)
I hit something of a wall last week after attempting two in a day, but I plan on resuming in the next couple of days.--Launchballer 17:24, 17 January 2025 (UTC)
Thank you. I do have one question about moving a prep to queue. For example, I promoted two hooks that are in prep 2. Could I still promote those two hooks to a queue and leave a note on the DYK talk page for someone else to check over it? I wouldn't want to promote prep 7 or prep 1 because I filled those preps by myself, but I'm curious about if only a small amount of the hooks were promoted by me. SL93 (talk) 17:45, 17 January 2025 (UTC)
I used to do both preps and queues, and often found myself in this kind of dilemma, so I decided to mostly work one side of the street. But, yeah, when I promote a set to a queue where I've had hands on one or two of the hooks, I'll post a request here for somebody else to look at those. RoySmith-Mobile (talk) 18:08, 17 January 2025 (UTC)
RoySmith I listed Noel Hilliam under the section Prep 2 to have someone look over the article because I promoted it to prep. I wonder if using the @DYK admins template would be acceptable in such a case. SL93 (talk) 02:16, 18 January 2025 (UTC)
I don't usually bother with the {{dykadmins}}, but it can't hurt. RoySmith (talk) 02:50, 18 January 2025 (UTC)
👍 Like. Welcome aboard! —Kusma (talk) 08:42, 18 January 2025 (UTC)

18 January

If someone can queue Prep 2, we can go to 12-hour backlog mode tomorrow. ~~ AirshipJungleman29 (talk) 13:32, 18 January 2025 (UTC)

Queued, currently finishing checks. —Kusma (talk) 16:53, 18 January 2025 (UTC)
12-hour mode should be activated between midnight and 12:00 noon UTC tomorrow. If nobody has done it by then, I'll flip the switch after I wake up tomorrow. —Kusma (talk) 17:25, 18 January 2025 (UTC)
The instructions say For a variety of technical reasons, you should only make a change shortly after midnight UTC. I've always assumed that means "sometime before noon", but I'be never been quite sure if there's not more to it than that. RoySmith (talk) 17:30, 18 January 2025 (UTC)
I am not sure when the bot does its runs to update User:DYKUpdateBot/Errors, whether that depends on update frequency and how long it takes for the bot to notice a change in updates per day, but I don't really think anything will break if we change the time between updates in the late UTC morning. I wouldn't flip the switch at 11:55, but 8:30 should be pretty safe. —Kusma (talk) 17:49, 18 January 2025 (UTC)
The last queue I promoted was a few minutes after midnight. I must have caught it in mid-update and confused something because as soon as I saved it, I got the "Oh no, all queues are empty!" warning box (which tankfully turned into something more encouraging shortly after). RoySmith (talk) 18:21, 18 January 2025 (UTC)

A friendly reminder that the lead hook of Queue 3 is a special occasion hook that is supposed to run on 26 January. It will have to moved soon: if we don't continue twice a day on 22 January, then it will have to go into Queue 6. If we do continue, then it would need to end up in Prep 2 if we don't again continue on 25 January, or Prep 3 if we continue twice a day on 25 January as well. The key, of course, is to get it out of Queue 3. Thanks. BlueMoonset (talk) 21:39, 20 January 2025 (UTC)

BlueMoonset I took care of it. However, the new first hook in Queue 3 will need to be reviewed by someone else because I promoted it to prep. @DYK admins: SL93 (talk) 18:07, 21 January 2025 (UTC)
 Done. The Silicon Island hook and article look OK to me.  — Amakuru (talk) 18:20, 21 January 2025 (UTC)

10 hook sets?

We switched to 9 hooks per set a while ago. That has certainly kept us closer to keeping up with nominations, but we're still falling behind and having to run in 12-hour mode once in a while to keep up. I suggest we try 10 hooks per set and see how that goes. RoySmith (talk) 01:12, 12 January 2025 (UTC)

Not worth it. The current rate will even out over time. ~~ AirshipJungleman29 (talk) 01:27, 12 January 2025 (UTC)
I'm not sure if one extra hook per set will help much if at all. I do think that more prep builders would help. SL93 (talk) 01:29, 12 January 2025 (UTC)
I do not mind going to 10 hooks a set. If we start running out, we can always return to 9-a-set at a later date. Z1720 (talk) 03:14, 13 January 2025 (UTC)
Nine is already more than enough IMO. Apart from the extra work required in verifying a 10-hook set, it becomes much harder not to repeat topics with longer sets, and longer sets just tend to look cluttered. 12-hour mode has long been a staple of DYK anyhow and one extra hook per set is not going to change that. Gatoclass (talk) 12:32, 15 January 2025 (UTC)
I think we're getting to the point where DYK is at risk of getting so long that hooks won't get the attention they deserve. I'd rather not move to 10 unless the overall backlog situation gets worse. —Kusma (talk) 12:42, 15 January 2025 (UTC)

Queue 6

Good Riddance (album) (nom)

@Locust member, Phibeatrice, and SL93: the hook says that the breakup was the only inspiration for the album, but both the lead and body say that it was also inspired by friendships and family. Surely the hook will need rewriting to match the article? ~~ AirshipJungleman29 (talk) 11:28, 17 January 2025 (UTC)

The hook doesn’t use the word “only” or “inspired”. The hook is “… that Gracie Abrams wrote Good Riddance about her breakup from her former collaborator and boyfriend, Blake Slatkin” and that is what the song is about. SL93 (talk) 12:04, 17 January 2025 (UTC)
I did not include the word "only" in the hook; I used Slatkin for the hook since it is much more interesting to know an album was written about her ex boyfriend and former collaborator (a notable person) than just friendships and family. Locust member (talk) 12:37, 17 January 2025 (UTC)
As others have stated, the hooks don’t use the word “only”—and if we’re talking about the insinuation of “only” given that the hooks omit mention of other inspirations, I don’t feel compelled by that either. I believe the hooks are fine as they are in this regard. Phibeatrice (talk) 15:39, 17 January 2025 (UTC)

Ethel Lote (nom)

@Spiderpig662: I wonder if it's worth including the factoid that she only stopped because she couldn't get her foot over the back of her neck. I can't do that and I'm around 20% as old as she was! ~~ AirshipJungleman29 (talk) 11:28, 17 January 2025 (UTC)

@AirshipJungleman29: That might be a good idea. Would a consensus be needed before that was added to the hook? Spiderpig662 (talk) 17:21, 18 January 2025 (UTC)

Prius Missile (nom)

@AlphaBetaGamma, Viriditas, Lajmmoore, and SL93: I can't read Japanese, so are we really sure this meets WP:NEOLOGISM? ~~ AirshipJungleman29 (talk) 11:28, 17 January 2025 (UTC)

I would hope so after the long discussion. SL93 (talk) 11:59, 17 January 2025 (UTC)
Looking the title up in Japanese brings up a lot of hits.
Following sources use the subject in its title:
ABG (Talk/Report any mistakes here) 23:30, 17 January 2025 (UTC)
AirshipJungleman29 asks a good and needed question. ABG, I think your sourcing is pretty poor, but the search results you provide show that the term has currency in Japan, particularly in the car industry and related niche sites, so much so, so that it appears that many of your cited sources are in part, a response from the car industry to the trend. So with that said, I think it's clear the term has currency in Japan. There's also the related and associated legal case(s) and general phenomenon of elderly drivers and unintended acceleration (usually involving a Prius) that appears in many related articles, scholarly journals, and news articles. The problem AirshipJungleman29 poses then becomes a bit narrower in terms of Misplaced Pages. In other words, while the phenomenon and term can be said to exist and are in use, do the sources meet the criteria for inclusion (in other words NEOLOGISM)? The article by Yoshitaka Kimura that you cite, which appears to be an article in an auto industry news site known as "Mediavague" (which I think might be funded by the auto industry to promote their products), argues that the term has been in use since at least early 2019, which establishes that it was a problem for Toyota, and was very real and threatened their business. I think this meets the RS criteria, and it reads as a kind of industry hybrid between Consumer Reports and Car and Driver. Your second link also mentions the Prius Missile but is more of a used car site run by Nextage. I'm not convinced this is a great RS, but we have a lot of others to choose from based on your search results. From there, I see a link to an article by MOTA, which is a car industry trade group, again, likely trying to dispel the internet slang which could harm Toyota's brand. Moving on, I see an interesting blog post about the phenomenon with some detail over "Creative Trends", but I don't think this meets RS. On the other hand, I see an article about the Prius Missile by jidounten lab, which appears to be a respected, reliable auto and tech journalism site. I also see a BuzzFeed Japan article about the term in your results. I think the problem here is that the sources in the current Misplaced Pages article, while accurate, might need to have better sources added, which I can clearly see in your google search results. Viriditas (talk) 00:24, 18 January 2025 (UTC)
My horrible attention span may have caused me to misunderstand some parts. I got lost on the last part, were you referring to links in the article or the previous message I sent here? I know it's an annoying question... ABG (Talk/Report any mistakes here) 10:57, 18 January 2025 (UTC)
It’s really simple. Use the best sources you can find. Viriditas (talk) 11:41, 18 January 2025 (UTC)
I think what Viriditas is saying @AlphaBetaGamma is that you should add some of the other sources (that are reliable) from the google search you linked, into the article since they are missing. Lajmmoore (talk) 18:24, 19 January 2025 (UTC)
I replaced two sources that seem weird. I don't remember citing blogs in this article so I'm confused. ABG (Talk/Report any mistakes here) 05:05, 20 January 2025 (UTC)

Prep 2

Last Song for You

Pinging Prince of Erebor The fifth reference on Last Song for You seems unreliable. Google Translate reveals that it is a WordPress blog. I'm planning on promoting prep 2 when it is ready, and I'm just doing some early checking. SL93 (talk) 22:43, 17 January 2025 (UTC)

Hey SL93, I believe you are referring to Film Pilgrimage, which should be considered a reliable source because Gary Wong Kwun-ho (王冠豪) is an established film historian and writer with a long career researching on film location scouting and his books are widely cited in this field. (He is also a notable figure that warrants an article, and I have had him on my to-write list for a long time.) So I believe he qualifies as a subject matter expert according to WP:RSPWORDPRESS. (Film articles on zhwiki have also cited Film Pilgrimage for the same rationale.) Also, the article is an exclusive interview with the director and lead actress, discussing the filming locations (which falls within Wong's expertise and does not contain exceptional claims). So I see no issue with citing Wong's piece in this case. —Prince of Erebor（The Book of Mazarbul） 04:38, 18 January 2025 (UTC)
That’s great. Thank you. SL93 (talk) 12:16, 18 January 2025 (UTC)

Arthur Swanstrom

Pinging 4meter4 The Unruh, Delbert (2018). Forgotten Designers Costume Designers of American Broadway Revues and Musicals From 1900–1930 reference was published by Page Publishing. It is a self-publishing company. The source can work if Delbert Unruh received significant coverage over his work. SL93 (talk) 22:54, 17 January 2025 (UTC)

@SL93 You have not actually looked at the article and what sources are physically cited in the article for the hook. Unruh isn't cited in the article for the source. Hischak is for the quote which is from Scarecrow Press. But Hischak oddly excluded Swanstrom from the lyrics credits. That's why I provided two different sources verifying Swanstrom as a co-lyricist of this work when I proposed the hook. One was Unruh, but the same content is also found in Bloom which is the source actually cited for the hook content in the article. Bloom is published by Schirmer Books. There isn't a verifiability issue here.4meter4 (talk) 00:43, 18 January 2025 (UTC)
4meter4 I never said that the Unruh source was used for the hook. I brought it up just in case because no unreliable sources should be used in articles. If the self-published source doesn't help anything, I fail to see why you want it there. Checking preps is not just about checking hooks. SL93 (talk) 00:47, 18 January 2025 (UTC)
SL93 Here is Delbert Unruh's obituary here. He was a full professor of theatre at the University of Kansas where he taught for forty years. He was a Fullbright scholar and was honored by the United States Institute of Theatre Technology and by the Kennedy Center for his work as a theatre scholar and educator. He's clearly a subject matter expert. Given the source is only used to support a single non-controversial sentence in the article I don't think this should be issue. The Internet Broadway Database has the same content, but I think Unruh is a better source to cite given who he is over a database without an attributed author. Best.4meter4 (talk) 00:58, 18 January 2025 (UTC)
4meter4 That is all that I needed, and you did not need to assume bad faith on my part. You should also know better. Well, it certainly isn't an issue now. SL93 (talk) 00:59, 18 January 2025 (UTC)
I'm sorry, I misinterpreted your objection because I had mention Unruh as a supporting source of the hook in my nomination. I didn't realize initially that you were objecting to its inclusion in the article overall. I didn't mean to make you feel attacked or slighted in my comments. Best.4meter4 (talk) 01:01, 18 January 2025 (UTC)
It's fine. I guess I will be clearer next time. SL93 (talk) 01:02, 18 January 2025 (UTC)
This has been resolved. SL93 (talk) 01:46, 18 January 2025 (UTC)

Noel Hilliam

I promoted this to prep. Can someone check over it? SL93 (talk) 02:02, 18 January 2025 (UTC)

Are NZ Short Walks and The End is Naenae reliable? Pinging Petersmeter and Schwede66. SL93 (talk) 02:32, 18 January 2025 (UTC)
I've had a look, SL93, and are happy to share my thoughts:
  • NZ Short Walks – that's obviously a blog and I couldn't figure out who the blogger is. Seems a well-informed person but without knowing more about who is doing the blogging, the default position has to be that this isn't a reliable source.
  • The End is Naenae – this is a blog by Dr Anna McMartin, Wikidata Q131787008 (I've made a Wikidata entry for her). She's a reasonably senior civil servant, and the area she's blogging about falls squarely within her professional expertise. I suggest that WP:ACCORDINGTO is appropriate guidance and this content, if presented as McMartin's opinion, is acceptable to be used. And I've just spotted that the same story has been published by North and South; that's a rather well regarded magazine and gives the whole affair a lot of credence. The full story is behind a paywall and if anyone has access to it, that would obviously be preferable to use as a source.
That's at least my 2c. Schwede66 05:04, 18 January 2025 (UTC)
NZ Short Walks is by Joanne Rolston. She is the author of The Kingdom (ISBN 9780473338923) but appreciate that is fiction. I believe she is working on a book on NZ history - but not yet published. I can't find much about her background/qualification etc. So accept that we have to default to not a reliable source. Petersmeter (talk) 11:01, 20 January 2025 (UTC)
I have removed NZ Short Walks from the article. SL93 (talk) 22:23, 18 January 2025 (UTC)

Queue 7 (23 January)

Raul Meza Jr.

@SL93, It is a wonderful world, and Narutolovehinata5: there is substantial WP:CLOP which needs to be resolved before this can run. RoySmith (talk) 00:18, 18 January 2025 (UTC)

I wrongly assumed that there was something that I was missing when I checked for CLOP because two substantial editors participated in the DYK. I swear to not do that again, and to follow my gut instinct. I will see about fixing it. SL93 (talk) 00:24, 18 January 2025 (UTC)
RoySmith I believe that I have taken care of it. SL93 (talk) 01:08, 18 January 2025 (UTC)
I am admittedly a less experienced editor, but are most of these changes needed? Does stating that someone was "sentenced to life imprisonment without the possibility of parole" actually violate CLOP? Swinub★ 01:30, 18 January 2025 (UTC)
I would say yes if there is a way to reword it. SL93 (talk) 01:37, 18 January 2025 (UTC)
What caught my eye was Records show that he had at least three different stepfathers and three half-siblings by the time he was 15 years old. Meza began using drugs at age eight and was first arrested in 1973 on shoplifting and burglary charges; the following year, he was accused of arsonCounty and state marriage records show Meza had at least three different stepfathers and three half-siblings before he was 15 years old ... Meza began using drugs at the age of 8 and was first arrested in 1973 on shoplifting and burglary charges ... The following year, the report stated, Meza was accused of arson That's classic close paraphrasing, which is defined as "superficial modification of material from another source". Once I saw that, I kept looking and found other examples. Yeah, most of the changes were needed. RoySmith (talk) 01:46, 18 January 2025 (UTC)
I see. I will be more careful about this from now on. Thanks. Swinub★ 01:50, 18 January 2025 (UTC)
Thanks. I didn't intend to single you out. WP:CLOP is one of our most commonly misunderstood policies. RoySmith (talk) 02:10, 18 January 2025 (UTC)

Robert Yelverton Tyrrell

@SL93, UndercoverClassicist, and Thriley: The hook is, at best, deceptive. He may have spent six weeks at Flynn's School, but he spent four years at Trinity College. RoySmith (talk) 00:26, 18 January 2025 (UTC)

RoySmith Maybe this as a rewording - "...that Robert Yelverton Tyrrell, a professor of classics, spent six weeks at a private school?" or maybe "... that Robert Yelverton Tyrrell, a professor of classics, was mostly home-schooled as a child?" SL93 (talk) 01:18, 18 January 2025 (UTC)
@RoySmith: this is probably a British-ism, where "school" and "university" are separate: "at school" excludes "at university". We could add "was accepted to university and became a professor of classics" to clarify that distinction? Alternatively, there are two ALTs:
I might add an abbreviated version of ALT1: "... that the classics professor Robert Yelverton Tyrrell tried to get Oscar Wilde released from jail?" Source: Beard, Mary (2002). "Ciceronian Correspondences: Making a Book out of Letters". In Wiseman, Timothy Peter (ed.). Classics in Progress: Essays on Ancient Greece and Rome. Oxford University Press. p. 107. ISBN 0-19-726323-2. (Housman); Stanford, William Bedell (Winter 1978). "Robert Yelverton Tyrrell" (PDF). Hermathena. 125: 17. JSTOR 23040586. Archived from the original (PDF) on 2021-10-20.} (Wilde) UndercoverClassicist 08:30, 18 January 2025 (UTC)
I was not aware of that British usage, thanks for that. I'm not opposed to any of those, but maybe the simplest fix would be to say "... six weeks at secondary school". RoySmith (talk) 15:28, 18 January 2025 (UTC)
That would work too! UndercoverClassicist 16:18, 18 January 2025 (UTC)
Done RoySmith (talk) 17:25, 18 January 2025 (UTC)

Queue 1

Joy to the World (Doctor Who) (nom)

@TheDoctorWho and Sammi Brie: the way this article mentions the incident (captioned the poster with "Joy to the Worlds", mirroring the title "Joy to the World") is not entirely clear, especially the word "mirroring". Would it not be better to simply state that the title was misspelled? ~~ AirshipJungleman29 (talk) 13:46, 18 January 2025 (UTC)

@AirshipJungleman29 Responded with a reword. Hope you don't mind the tweak, TheDoctorWho. Sammi Brie (she/her • t • c) 17:19, 18 January 2025 (UTC)
Don't mind at all, was just about to take care of it myself but you beat me to it, thanks! TheDoctorWho (talk) 17:30, 18 January 2025 (UTC)

Queue 2

KZJO (nom)

Needs end of sentence citation. @Sammi Brie, @Bagumba, @AirshipJungleman29. —Kusma (talk) 16:57, 18 January 2025 (UTC)

@Kusma Done. Sammi Brie (she/her • t • c) 17:18, 18 January 2025 (UTC)
@Sammi Brie, forgive me if I'm being dense, but don't we need this to be one sentence earlier? —Kusma (talk) 17:21, 18 January 2025 (UTC)
@Kusma Combined the two sentences instead for DYK purposes. Sammi Brie (she/her • t • c) 19:38, 18 January 2025 (UTC)
That works! Apologies for the pedantry. —Kusma (talk) 19:41, 18 January 2025 (UTC)

2/day

I have just activated 2/day, 12-hour set backlog mode. Hope a few people can pitch in and help promote hooks to prep and preps to queue so we can do this without burning out anyone. —Kusma (talk) 07:20, 19 January 2025 (UTC)

There are only five queues filled after the midnight promotion was made, so it's time to go back to 1/day, 24-hour set backlog mode. Pinging @DYK admins: so that this can be done in the next few hours. Many thanks. BlueMoonset (talk) 01:14, 22 January 2025 (UTC)
I'm sorry, is the current rule that we only do 12-hour sets for three days at a time? I must have missed that change, but I'll trust BlueMoonset to be on top of it.  Done :) theleekycauldron (talk • she/her) 08:18, 22 January 2025 (UTC)
It doesn’t seem like a good idea with 135 approved nominations. It also looks like we will have to go back to two sets a day again soon. SL93 (talk) 08:28, 22 January 2025 (UTC)
IIRC the three day cut off was put in place to ensure the rate was reduced before admins (and now template editors?) burnt out. Being able to trigger it a second time quickly is I believe part of the intended design, dependent on there being filled preps and queues that show that volunteers have not yet burnt out. CMD (talk) 08:34, 22 January 2025 (UTC)
That makes sense. Thanks for the information. SL93 (talk) 16:50, 22 January 2025 (UTC)
I pushed for the 3-day rule exactly to prevent burnout. Previously, our only criteria for mode change was how many noms were stacked up in the approved pile. So we'd start doing 12-hour sets and quickly run the queues empty with nobody willing to put in the work to keep it going. Now at least we find out if we've got the work capacity to handle it without getting to the crisis stage of zero queues filled.
Informally, I think flitting back and forth between modes is a bad idea because it complicates the job of people trying to schedule special occasion hooks. I'd rather see us stay in 12-hour mode for a bunch of consecutive cycles, but not at the cost of running the queues down to zero. RoySmith (talk) 17:11, 22 January 2025 (UTC)
I've done one, though I notice that PSHAW hung when I clicked the button - pinging @Theleekycauldron:. The next one has one of mine in it; will do the other eight if no-one else does in the next three hours.--Launchballer 19:27, 22 January 2025 (UTC)

Queue 3

Doug Hamlin (nom)

@Queen of Hearts: The hook fact lacks an end-of sentence citation. —Kusma (talk) 07:33, 19 January 2025 (UTC)

@Kusma, do you mean in the article? TarnishedPath 10:05, 19 January 2025 (UTC)
@TarnishedPath, yes. Thank you for adding it. —Kusma (talk) 10:07, 19 January 2025 (UTC)
@Kusma no worries. I didn't worry about it when I was promoting the hook because it was at the end of the paragraph anyway. Can't hurt to have it at the end of each sentence though. TarnishedPath 10:17, 19 January 2025 (UTC)
@TarnishedPath, it is actually a requirement per WP:DYKHFC. —Kusma (talk) 11:29, 19 January 2025 (UTC)

Scientific Research Institute of Medicine of the Ministry of Defense in Sergiyev Posad (nom)

@Le Loy/Ле Лой, @Geni: The lead should be expanded a bit to make the article properly presentable. —Kusma (talk) 08:03, 19 January 2025 (UTC)

@Kusma, done, please take a look. I got so sick of this institution it took me a while to return to the article. Le Loy (talk) 11:46, 19 January 2025 (UTC)
@Le Loy: much better, thanks! —Kusma (talk) 11:49, 19 January 2025 (UTC)

Queue 4

Du Toit's torrent frog

Olmagon AmateurHi$torian AirshipJungleman29 - How does anyone know that only two people are known to have seen the frog alive? The article even says this about the first discoverer - "He collected three individuals, which would later be studied and recognized as a new species by British biologist Arthur Loveridge in 1935." That would be two people already if those specimens were alive, and that is without mentioning the next discoverer of live specimens named Ronalda Keith. SL93 (talk) 12:21, 19 January 2025 (UTC)

@Olmagon: I guess the collected species are presumed to be dead, but is there a source which says that? If there is none, maybe ALT1 can be used instead. -AmateurHi$torian (talk) 12:41, 19 January 2025 (UTC)
SL93, collected specimens are dead. The source clearly says that they were preserved in formalin after their collection in the field. ~~ AirshipJungleman29 (talk) 12:58, 19 January 2025 (UTC)
AirshipJungleman29 Collected specimens are not always dead. As for the source, I only have access to an abstract that didn't answer my question. SL93 (talk) 13:06, 19 January 2025 (UTC)
See Zoological specimen. If they are not dead and preserved, they are not yet considered specimens. ~~ AirshipJungleman29 (talk) 13:09, 19 January 2025 (UTC)
Not true. Searching "living specimen" and "living specimen meaning" shows otherwise. Cambridge dictionary along with this and this are just three of many examples. Although it doesn't matter now. SL93 (talk) 13:28, 19 January 2025 (UTC)
The source right after mentioning Arthur Loveridge makes it clear that they were preserved. The View Article link originally didn't show up on my screen. I just had to refresh. I'm sorry. SL93 (talk) 13:59, 19 January 2025 (UTC)
I suppose it's always possible that someone saw this frog alive but never reported it or didn't realize it was this species, that's why I specified "known", but I suppose you seem to have solved the issue already without me anyways. Olmagon (talk) 21:18, 20 January 2025 (UTC)

Sitaleshwar Temple

AmateurHi$torian MartinPoulter AirshipJungleman29 - A direct citation is needed after the hook fact. SL93 (talk) 12:21, 19 January 2025 (UTC)

@SL93: Added -AmateurHi$torian (talk) 12:36, 19 January 2025 (UTC)

Tokyo Expressway

Mccunicano A citation is needed after "Southbound exit." SL93 (talk) 12:21, 19 January 2025 (UTC) @SL93: That's what the Google Maps reference is for at the top of the junction list, but the information also exists within the page linked to the junctions that are to be closed, it's redundant to attach it for a junction that is not impacted by the closures. ❯❯❯ Mccunicano☕️ 23:44, 19 January 2025 (UTC)

Mccunicano I wrongly assumed that everything in the notes was meant to be sourced to the 6th reference, and I didn't think Google Maps was the best option when another source is available. I came to that conclusion after searching recent discussions about if Google Maps was completely reliable, and I came across WP:GOOGLEMAPS a few minutes ago which revealed to me that it can be used to such a purpose as this. You can remove the citation. SL93 (talk) 00:12, 20 January 2025 (UTC)

Queue 6

Caffey family murders

Jolielover Pbritti Hilst Caffey family murders has WP:CLOP issues per Earwig such as "to be tried as an adult" and "All four defendants were initially charged with three counts of capital murder". SL93 (talk) 14:41, 20 January 2025 (UTC)

Jolielover Will you be taking care of this? SL93 (talk) 22:19, 21 January 2025 (UTC)
Hi there, some false positives due to quotations & things such as names of shows the case was featured on. I have paraphrased the rest, hope it works, thanks. jolielover♥talk 02:22, 22 January 2025 (UTC)
Thank you. SL93 (talk) 02:27, 22 January 2025 (UTC)

Orlando Bagwell

This is my nomination so someone else needs to look over it. @DYK admins: SL93 (talk) 14:41, 20 January 2025 (UTC)

Will take shortly.--Launchballer 15:01, 20 January 2025 (UTC)
 Done (edit conflict) Hi @SL93: I've taken a look at this and looks good to me. The only thing is, I thought the Career section seemed to be missing coverage from between 1987 and 2012, but then I noticed that was contained in the Filmography section. I've taken the liberty of folding those two into one as that seems to offer a better chronology. It's still a bit on the short side and could do with expansion on more of his career, but fine for a DYK IMHO. Cheers  — Amakuru (talk) 15:06, 20 January 2025 (UTC)

Queue 5

Loew's Jersey Theatre

@Epicgenius: The newspaper.com link for the restored organ clipping is incorrect. It links to a completely different article. The ProQuest link is fine, though. – 🌻 Hilst (talk | contribs)

@Hilst, thanks for pointing it out. I found the correct clipping and fixed it. – Epicgenius (talk) 15:37, 20 January 2025 (UTC)

The Hangover (Suzanne Valadon)

@Viriditas, Jonathan Deamer, and AirshipJungleman29: Do we need to include the fact that it "features model Suzanne Valadon and the stylistic influence of Vincent van Gogh"? I don't see what those tidbits add to the hook. – 🌻 Hilst (talk | contribs) 15:24, 20 January 2025 (UTC)

The model can be cut; I find it interesting that a painting inspired by van Gogh could be found suitable for a nightclub. ~~ AirshipJungleman29 (talk) 15:33, 20 January 2025 (UTC)
The suggestion of @AirshipJungleman29 sounds good! Jonathan Deamer (talk) 17:31, 20 January 2025 (UTC)
Works for me. Viriditas (talk) 19:06, 20 January 2025 (UTC)
 Done – 🌻 Hilst (talk | contribs) 20:55, 20 January 2025 (UTC)

Older nominations needing DYK reviewers

The previous list was archived yesterday, so I've created a new list of 31 nominations that need reviewing in the Older nominations section of the Nominations page, covering everything through January 8. We have a total of 271 nominations, of which 156 have been approved, a gap of 115 nominations that has decreased by 8 over the past 8 days. Thanks to everyone who reviews these and any other nominations!

More than one month old

Other nominations

Please remember to cross off entries, including the date, as you finish reviewing them (unless you're asking for further review), even if the review was not an approval. Please do not remove them entirely. Many thanks! BlueMoonset (talk) 21:31, 20 January 2025 (UTC)

Edit top section

I tried to correct a grammatical error but this page doesn't seem to edit like others: "go to article's talk page" should be "go to the article's talk page". Al Begamut (talk) 15:29, 21 January 2025 (UTC)

I corrected it at Template:DYK archive header.--Launchballer 21:45, 21 January 2025 (UTC)

DYK's use of the T: pseudo-namespace

There is currently a proposal (Misplaced Pages:Village pump (proposals)#Proposal to prohibit the creation of new "T:" pseudo-namespace redirects without prior consensus) to fully deprecate the T: pseudo-namespace. A significant chunk of the remaining T: pages (Special:PrefixIndex/T:) are related to DYK, including the main T:DYK redirect and redirects to all the preps and queues. Some of these are directly referred to in our Template:DYKbox, and in places such as the Misplaced Pages:Did you know/Prep builder instructions. I've !voted to exclude DYK from the proposed sunsetting, but perhaps we should also think of switching to using TM: shortcuts as standard. CMD (talk) 16:03, 21 January 2025 (UTC)

What I can't promote

The nominations that I have participated in and that are not being promoted is getting longer. Here is a list of the oldest ones needing promotion.

Template:Did you know nominations/2019 NFC Divisional Playoff game (Seattle–Green Bay)
Template:Did you know nominations/Science Fiction Chronicle
Template:Did you know nominations/Their Highest Potential: An African American School Community in the Segregated South
Template:Did you know nominations/The Scarecrow (children's book) SL93 (talk) 02:33, 22 January 2025 (UTC)

Eye-rolling hook in Q5

"* ... that the discontinuation of a Warsaw-based Yiddish literary journal in the summer of 1939 was unrelated to the invasion of Poland?"

If you read the article, you learn that the journal folded due to financial shortcomings and published its last issue on June 30 of that year ... about two months before the Germans invaded. At a time when no one was expecting that to occur, at least not imminently. Hell, if you read the hook and know basic history, your first thought would not be "Well, I'd like to read the article and find out why" but "Whoever would have thought it was?" Just because the war in Europe started on September 1 of that year does not mean every event in Poland that year, especially those prior to that date (save, of course, the Gleiwitz incident) must automatically have something to do with it.

Put it this way: it would be like a hook saying that the cancellation of an American TV show that happened to occur in spring 2001 was "unrelated to 9/11".

I could understand, perhaps, if the sources showed that it was a common perception that the journal had been shut down due to the invasion. But they do not appear to. We do appear to have one source offhandedly saying this, but purely on its own. That's the sort of thing that really shouldn't have made it into the article because of SYNTH-y ness like this. Pinging @AirshipJungleman29: (reviewer) and @Generalissima: (creator, who in fairness did say during the nomination that they were open to alternate hook ideas. Daniel Case (talk) 05:27, 22 January 2025 (UTC)

I'm pretty sure there was a much higher volume of Yiddish literature curtailed in Poland after the Nazi invasion than there were American TV shows cancelled after 9/11 also, the invasion happened in the summer, so your comparison doesn't even make sense Generalissima (talk) (it/she) 06:57, 22 January 2025 (UTC)

Queue 1

Sam Kee Building

@Yue, Jeromi Mikhael, and Hilst: Article and hook attribute, source doesn't.--Launchballer 19:17, 22 January 2025 (UTC)

It does. "With distinctive bay windows that expand the floor space of the second storey, the Sam Kee Building was recognized by Guinness World Records as the narrowest commercial building in the world." SL93 (talk) 19:54, 22 January 2025 (UTC)

Pantropiko

@AstrooKai, SL93, and Royiswariii: As far as I can tell, the promoted hook was explicitly rejected on interestingness grounds, and I think quite rightly.--Launchballer 19:17, 22 January 2025 (UTC)

That's true. I only approved the first hook. SL93 (talk) 19:36, 22 January 2025 (UTC)

Liang Sishun

@TheLonelyPather and Toadspike: The hook is contradicted elsewhere in the article; it says she published the book "in 1908, when she was sixteen years old" but the article claims she was born in 1893, which would make her 14 or 15.--Launchballer 19:17, 22 January 2025 (UTC)

@Launchballer I'm guessing this is down to East Asian age reckoning, which adds a year or two. Toadspike 19:22, 22 January 2025 (UTC)
In my opinion, this is not an error, and the hook can run as-is. However, we can also add a footnote to the article clarifying the Chinese age counting system once TLP has confirmed that the dates and ages accurately reflect the sources. Toadspike 19:26, 22 January 2025 (UTC)
I think adding a footnote would be an excellent idea.--Launchballer 19:29, 22 January 2025 (UTC)
I support a footnote. SL93 (talk) 20:18, 22 January 2025 (UTC)

Eoscorpius

@An anonymous username, not my real name and Ornithoptera: Where's the hook?--Launchballer 19:17, 22 January 2025 (UTC)

"Eoscorpius was placed in the newly erected family Eoscorpionidae by American paleontologist Samuel Hubbard Scudder in 1884. While other experts of the time, such as Ben Peach, considered the genus to be hardly different from modern scorpions, Scudder believed that it was sufficiently distinct to warrant the creation of a new family." SL93 (talk) 19:37, 22 January 2025 (UTC)
@SL93, for some reason, this hook wasn't picked, even though Ornithoptera explicitly preferred it. Is it possible to change it? — Anonymous 19:40, 22 January 2025 (UTC)
ALT1 is fine by me. I wasn't sure if there was a preference because both hooks were approved. SL93 (talk) 19:41, 22 January 2025 (UTC)
"British geologist Ben Peach expressed regret that the name Eoscorpius was given to a genus so similar to modern scorpions, speculating a much earlier origin for scorpions as a group." for ALT1. "Ben Peach, considered the genus to be hardly different from modern scorpions" for ALT0. SL93 (talk) 19:51, 22 January 2025 (UTC)

Frankish Tower (Acropolis of Athens)

@UndercoverClassicist and Zeete: Article and hook attribute, source doesn't.--Launchballer 19:17, 22 January 2025 (UTC)

It's in the St. Clair source, cited in both: "Among those who contributed to the debate in the local Athenian press was L. Kaphtantzoglou, who described the tower as Turkish, and compared it to the droppings of birds of prey.". This is Lysandros Kaftanzoglou, who was a Greek academic. UndercoverClassicist 19:43, 22 January 2025 (UTC)
It does. "Was everything built on the Acropolis between ancient and modern Hellas to be regarded as a temporary intrusion? Among those who contributed to the debate in the local Athenian press was L. Kaphtantzoglou, who described the Tower as Turkish, and compared it to the droppings of birds of prey." I had to scroll down to page 494 because the search option didn't work. SL93 (talk) 19:49, 22 January 2025 (UTC)

Queue 2

long-legged lovebird

Di (they-them) Cremastra Hilst I don't see why "humanity's cradle" was used rather than "Cradle of Humankind". SL93 (talk) 20:14, 22 January 2025 (UTC)

I just used a descriptive phrase rather than the actual title to create intrigue. Di (they-them) (talk) 20:15, 22 January 2025 (UTC)
I'm not sure how I feel about using a descriptive phrase for it, but I will see what others think. SL93 (talk) 20:16, 22 January 2025 (UTC)
Just a fancy form of a name that was pretty poetic in the first place. Some wordplay is allowed. Cremastra (talk) 20:42, 22 January 2025 (UTC)
Either one is fine by me. – 🌻 Hilst (talk | contribs) 20:57, 22 January 2025 (UTC)
Thanks for the input. SL93 (talk) 20:59, 22 January 2025 (UTC)

1453

Generalissima EchetusXe The article says "in late 1452 or early 1453", but the hook says "in 1453". SL93 (talk) 20:14, 22 January 2025 (UTC)

Rephrased the article portion a bit - the eruption may have occurred in either year, but the cooling occurred in 1453. Generalissima (talk) (it/she) 20:24, 22 January 2025 (UTC)
That works for me. SL93 (talk) 20:25, 22 January 2025 (UTC)
Category:
Misplaced Pages talk:Did you know: Difference between revisions Add topic