Wikipedia talk:Did you know

From Wikipedia, the free encyclopedia


"Did you know...?"
Discussion WT:DYK
Rules WP:DYK
Supplementary rules WP:DYKSG
Noms (awaiting approval) WP:DYKN
Reviewing guide WP:DYKR
Noms (approved) WP:DYKNA
Preps & Queues T:DYK/Q
Currently on Main Page
Main Page errors WP:ERRORS
Archive of DYKs WP:DYKA
Stats WP:DYKSTATS


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

Do you have a suggestion for improving DYK, or would like to comment on the suggestions of others? Have your say at Wikipedia:Did you know/2017 reform proposals.


Contents

Template:Did you know nominations/Holly Beth Vincent

I was reviewing Template:Did you know nominations/Holly Beth Vincent and the nominator is claiming eligibility via 2-fold BLP expansion. The old version has some sources but it's tagged with {{BLP refimprove}}, not {{BLP unsourced}}. Would articles with refimprove tags count toward 2-fold expansion, or does it have to be completely unsourced? epicgenius (talk) 16:10, 11 February 2018 (UTC)

epicgenius, the article has to be completely unsourced. Not merely without inline citations, but no references of any kind. So DYK nominations that claim the two-fold BLP expansion are almost invariably ineligible for this, since completely unreferenced BLPs are supposed to be deleted on Wikipedia, though one very occasionally slips through the cracks. This nomination had six inline source citations before it was expanded, so it needs to be a five-fold expansion. This was expanded from 5704 prose characters to 13037 prose characters, or a nearly 2.3× expansion. It needs to expand to 28520 prose characters, which seems highly improbable; the only feasible route is to try for Good Article status. BlueMoonset (talk) 16:47, 11 February 2018 (UTC)
@BlueMoonset: Thank you for the clarification. Now it looks like I have to break some bad news... Face-sad.svg epicgenius (talk) 16:53, 11 February 2018 (UTC)

Remove the 2x BLP criterion

It almost seems as though we should dump that particular criterion. Vanamonde (talk) 17:18, 11 February 2018 (UTC)
Agree with Vanamonde93, as we have almost no unsourced BLPs anymore, it's a meaningless crieterion. Joseph2302 (talk) 17:19, 11 February 2018 (UTC)
Yes, this criterion is terribly outdated and makes minimal sense nowadays; let's develop a consensus here and remove it. Alex Shih (talk) 17:24, 11 February 2018 (UTC)
Agree with Alex Shih and support removal of the 2xBLP. Yoninah (talk) 00:01, 12 February 2018 (UTC)
I also agree that this is a criterion that has outlived its purpose, and no longer needs to be offered. Count me as another who is in favor of its removal. BlueMoonset (talk) 00:10, 12 February 2018 (UTC)
I'll make it six people who want to remove this criterion. Should this be an RFC? epicgenius (talk) 01:20, 12 February 2018 (UTC)
I don't think RfC is necessary. Many of the DYK rules, if I am not mistaken, were added only after a short discussion here. This feels fairly uncontroversial to me, so I think anyone who has yet to comment here can feel free to remove the criterion, attributing a permanent link citing this section. Alex Shih (talk) 06:38, 12 February 2018 (UTC)
Yes lets get rid of that criterion. It will be a slight simplification, we seldom get that around here! Graeme Bartlett (talk) 06:46, 12 February 2018 (UTC)
I am also in favour of removing it. Cwmhiraeth (talk) 06:55, 12 February 2018 (UTC)
Yes, the BLP exception should have been eliminated years ago. It was proposed in 2010 as a temporary rule during a BLP sourcing drive when over 20,000 BLPs contained absolutely no sources of any kind. I haven't seen a valid submission in many years, but there have been lots of invalid ones. It is worse than a useless rule, because virtually all of the rare attempts to use it are incorrect. People who apparently misunderstand what "unsourced" means end up disappointed and frustrated when their DYKs are rejected, and everyone's time is wasted. MANdARAX  XAЯAbИAM 09:37, 13 February 2018 (UTC)
I am going to be the dissenting voice here and say we should keep it. I know it has been used incorrectly but there are still a lot of unsourced orphan BLPs out there that this particular rule is designed to encourage work on. Often I find there are unsourced paragraphs which make it impossible due to lack of available sources to 5x expand and the 2xBLP rule still allows for and encourages people to work on them where otherwise there is little or no incentive to improve them. They may be as rare as a drop goal in American football, but that doesn't mean it's not a valid method of "scoring". Personally this should be discussed in a separate section of this talk page (NOT as a RFC) because a lot of people could miss it under this heading. The C of E God Save the Queen! (talk) 10:25, 13 February 2018 (UTC)
Not quite sure what you mean by referring to unsourced paragraphs, The C of E; the entire article has to be completely unsourced. It just doesn't happen here at DYK. If you find them "often", and there are "a lot" of them, then what was the last one you saw that qualified? As we've noted, any old ones should have long since been deleted per BLP rules. BlueMoonset (talk) 21:47, 15 February 2018 (UTC)
The "completely unsourced" rule is bollocks, a complete disincentive to improve shoddy BLPs. Most of the time these days, if we ever see a "completely unsourced" BLP, it's up for deletion. This needs attention. Finding and improving a shitty BLP should be applauded and lauded, and right now, if it has one citation in three thousand unreferenced claims, DYK deems it unacceptable. Nonsense. The Rambling Man (talk) 22:01, 15 February 2018 (UTC)
No, it's not unacceptable, and you know it. It just needs to follow the same rules as any other expanded article, which means five times the original size. We get plenty of BLPs in the normal way of things, both new and 5x expanded. BlueMoonset (talk) 07:18, 16 February 2018 (UTC)
From what I've seen of the rare attempts to use this generous exception, the real incentive that it provides is the easiest way to quickly throw together a DYK with the most minimal effort possible. A shoddy unreferenced BLP is turned into a shoddy referenced BLP. I've seen all of the references and most of the content removed from several BLPs, with claims of 2x expansions from those newly unsourced, newly shortened BLPs. The rule is abused, misused, and most of all, simply unused. MANdARAX  XAЯAbИAM 20:41, 23 February 2018 (UTC)
Someone show me five examples of completely unreferenced BLPs being taken to DYK in the last three months (i.e. 5 hooks out of a possible 90–180) and I'll re-consider. The Rambling Man (talk) 21:10, 23 February 2018 (UTC)
Alright, show me TWO! The Rambling Man (talk) 21:28, 23 February 2018 (UTC)

DYK Admin role RFC

The role of admins in the DYK process as defined in the instructions, and the role as practiced, differ widely. Moreover, different admins treat their role differently, and based on past discussions, have widely divergent views on what the role should be. For folks unfamiliar with the process, admins are required to move approved DYK hooks from Prep areas to Queues. The question here is what, if any, further checks admins are required to perform during this process.

Since there are many possible combinations here, I have structured this to permit maximum flexibility in the outcome. Therefore, please feel free to add additional checks that you think admins are required to do, that I may have left out. Vanamonde (talk) 17:27, 11 February 2018 (UTC)

Survey

Hook interest

Should administrators be required to check hooks to ensure they are reasonably interesting?

  • Yes. Administrators should absolutely be checking whether hooks are sufficiently interesting in my view, and removing them if they think they are not up to scratch. It does no harm to return a suspect hook for further discussion, while replacement hooks (from other nominations) are readily available. I think this is the first thing admins should be doing in checking a set. It's something I have done for years, it takes only a few seconds and there is no excuse for allowing a potentially substandard hook to reach the main page IMO. Gatoclass (talk) 04:00, 12 February 2018 (UTC)
  • I'm probably going against the grain here, but no, at the moment, because the DYK community has not come to a consensus about what constitutes an interesting hook anyway. Some folks have far higher standards for "interesting" than others do. Furthermore, I think this check is less about keeping the main page problem-free and more about making it as good as it could be; which is a responsibility I'm okay leaving with reviewers and promoters. Or to put it another way: I think admins may be said to have a better idea of what constitutes a BLP violation or a WP:V violation. I don't think we necessarily know better than the average community member what constitutes an interesting hook. Vanamonde (talk) 04:27, 12 February 2018 (UTC)
    • It's true that there's a surprising amount of confusion about what constitutes "interest". I personally think there are some very clear criteria one can look for in assessing that and I have intended to add a guideline to that end a number of times but never quite gotten around to it. This is one of the many things I am hoping to be able to address in the near future. Gatoclass (talk) 04:42, 12 February 2018 (UTC)
    • I'm afraid that in my original comment I managed to conflate two different issues and that some users have responded to the wrong issue here. I have since refactored my comment for clarity. But Vanamonde, while I agree that administrators "don't necessarily know better" than other users what constitutes an appealing hook, they do constitute a third check on hook quality after the initial reviewer and set builder, and if any of the three checkers feel a hook is not up to scratch, chances are it isn't and it needs further work. My point is that the promoting administrator cannot renege on his responsibility in this regard, any more than the initial reviewer or set builder should. If in doubt, pull, because it's better to be safe than sorry. If the pull turns out to be unnecessary, nothing is lost because the original hook can simply be restored at a later time. In my experience however, further discussion about a hook's interest factor almost invariably results in a much better hook than the one that was originally proposed. Gatoclass (talk) 12:28, 12 February 2018 (UTC)
  • No, that is up to assessment and discussion at an earlier stage. Single person assessment by an admin will cause controversy. Graeme Bartlett (talk) 07:01, 12 February 2018 (UTC)
  • I am leaning toward no unless if the hook is seriously sub-standard, as I am not in favour of admins pulling hooks unilaterally just because they think it's not interesting. This reminds me of a relevant discussion here back in last August. Alex Shih (talk) 07:16, 12 February 2018 (UTC)
    • Graeme Bartlett, Alex Shih, I refactored my comment above as I realized that with my original comment I had inadvertently raised a different issue to the one intended for discussion here. Hopefully my meaning is more clear now. Gatoclass (talk) 07:53, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:23, 12 February 2018 (UTC)
  • No I've seen too many complaints about this where the real problem was the ignorance of the complainant. I'd approve it only if a complainant faced an automatic block for a false report. Hawkeye7 (discuss) 10:00, 12 February 2018 (UTC)
  • No Admin powers are not assessed or granted on a basis of such editorial judgement and so the admin corps is dominated by men with specific interests such as sport or military history. They cannot be expected to have a good appreciation of other types of topic such as embroidery or romance. The structure of DYK is to rate the hook according to their reception by readers. It's our readership that thus determine the success of a hook. We should therefore focus upon publishing the statistics so that contributors get good feedback and can adjust their submissions accordingly. Andrew D. (talk) 13:21, 12 February 2018 (UTC)
  • No due to previous experiences where admins have removed hooks that were clearly interesting ([1]). This should happen prior to the admin step in the process. Nomader (talk) 21:30, 12 February 2018 (UTC)
    Seven and a half years ago? Seriously? The Rambling Man (talk) 21:34, 12 February 2018 (UTC)
Wow, I feel really old? I really didn't think it was that long ago... I just remember it because it happened to one of my hooks and no one notified me-- I was absolutely livid and it was a pretty big deal here then. I think if this is implemented, it has be made sure that admins don't remove hooks from the main page, but instead make sure to address the process while they are still in the queue/in the nominations phase. Nomader (talk) 21:39, 12 February 2018 (UTC)
For the record, that hook pull was done out of process and generated quite a bit of controversy.[2] I should also add that "mak[ing] sure to address the process while they are still in the queue/in the nominations phase" is precisely what I am advocating here. Gatoclass (talk) 23:14, 12 February 2018 (UTC)
I think that hook pull addresses exactly why administrators shouldn't be *required* to look for hook interest, though. It's a subjective call-- I disagree that it should be a requirement but I think it should be something they *can* do before it goes onto the front page. An administrator can bring these issues up and so can anyone else-- the requirement issue is the problem here. Nomader (talk) 14:33, 13 February 2018 (UTC)
Okay Nomader, I've given it my best shot and I can't keep repeating myself. I maintain that it's very important for admins to ask themselves whether or not they think hooks are sufficiently interesting before promoting them to the queue, because it never hurts to pull a hook for further discussion if there is any doubt. But for some reason, it seems that argument is just not getting any traction here. Regardless, thank you for at least considering my point of view. Gatoclass (talk) 14:57, 13 February 2018 (UTC)
I completely understand where you're coming from and thanks for continuing the discussion-- I'm sorry that I can't agree. Thanks for putting all of the work behind it though, Gatoclass. Nomader (talk) 15:09, 13 February 2018 (UTC)
  • No, because what constitutes interest to one person may not be interesting to another. Any "uninteresting hooks" should be discussed on a case by case basis. An administrator can definitely bring this issue up. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • I might also add that when an administrator pulls a potentially problematic hook from prep or the queue for further discussion, they are actually doing the nominator a favour, because if a hook with issues makes it to the main page without those issues being first addressed, it becomes liable to summary yanking by any drive-by admin and once removed, it can be impossible to return to the main page in a timely manner, resulting in the hook losing the main page exposure the nominator might otherwise have expected because the issues with it weren't ironed out first. Gatoclass (talk) 00:14, 13 February 2018 (UTC)
  • No Subjective opinions should play no part in if a hook can run. I have always said exactly what Epicgenius said above and I stand by it here. The C of E God Save the Queen! (talk) 09:55, 13 February 2018 (UTC)
  • No What's is "interesting" and "not interesting" is very subjective. –Ammarpad (talk) 11:09, 13 February 2018 (UTC)
    • But hook interest is not merely subjective. Hooks, for example, which highlight only the everyday or mundane are, by definition, uninteresting. "Did you know that Littletown, Texas has both rainy and sunny days?" is clearly an uninteresting hook because you can say exactly the same thing about virtually any town on earth. Contrary to popular opinion, there are plainly some objective criteria that can be applied when assessing hook interest. Gatoclass (talk) 11:11, 13 February 2018 (UTC)
  • No I would much prefer that hooks were boring and accurately reflect the most important parts of an article than "interesting" and misleading. Interesting hooks should be WAY down the list of concerns. --Jayron32 15:37, 13 February 2018 (UTC)
"Interesting" does not equate to "misleading". I happen to agree though that some hooks try too hard to be interesting when all that is necessary in many cases is to simply outline what is notable about a particular topic - in fact I was arguing as much just days ago on this page - but that's a separate issue. The point I have tried to make in this section is simply that administrators have a responsibility to try and prevent plainly substandard hooks getting to the main page (like the example given above). What I am finding particularly ironic about this entire debate thus far is that DYK has been pilloried for years about the number of fatuous hooks that have made it to the main page, but when given the opportunity to !vote on even the mildest and most obvious preventative measure, the community's attitude seems to be oh no, we couldn't possibly do that. Gatoclass (talk) 16:27, 13 February 2018 (UTC)
Because people "own" their hooks and don't like the idea of someone telling them that they're boring. People continually forget that it's one of DYK's major themes (interesting to a broad audience) and summarily ignore it. Of course, very little is done about it and those of us who highlight hooks which are mediocre in this regard are cast as the pantomime villains. People want to "pile it high, sell it cheap" on DYK, and given the voting across this RFC, that's been certainly reinforced. The Rambling Man (talk) 16:31, 13 February 2018 (UTC)
  • No: I've had to fight in WP:ERRORS to keep a hook of mine up that an editor thought was "meh", and yet it ended up doing well with 6,000 views -- clearly not everyone is in agreement on what is interesting or not, and hooks shouldn't be removed due to one person's subjective opinions. Umimmak (talk) 04:15, 14 February 2018 (UTC)
  • No: A hook may be unexciting to a broad audience, but may still be the most interesting hook available. Boring hooks should be intercepted earlier in the process, as admins have more important matters to deal with when moving sets into queues. Cwmhiraeth (talk) 14:42, 14 February 2018 (UTC)
  • No. Too subjective. Everyone has different interests. There is no evidence admins are better at judging whether something is interesting or not than non-admins. feminist (talk) 17:39, 23 February 2018 (UTC)
Request to close

I think it's become clear at this point that I messed up this proposal by phrasing the question in the wrong way. The question should have said something like: Should administrators be required to check that hooks are not unacceptably banal or uninteresting? By stating the question as I did, proposing that admins be required to decide whether or not hooks are "reasonably interesting", it seems I have given the impression, judging by the responses above, that I was proposing that administrators be encouraged to return hooks from the prep/queue areas based on what they personally do or do not fancy.

That was absolutely not my intended meaning, rather, I had in mind something more akin to Alex Shih's suggestion that hooks only be pulled if they are "seriously substandard", as he put it - or else in accordance with clear criteria, such as the one I outlined in the "Littletown, Texas" example above.

What I think I should probably do at this point is go and work on establishing some clear criteria for identifying substandard hooks, and then based on that put a modified version of the above question to the community, perhaps in a few week's time. I would like to suggest therefore that this proposal be closed forthwith by an uninvolved administrator, with no prejudice toward a possible future RFC on a related question. Gatoclass (talk) 07:21, 14 February 2018 (UTC)

@Gatoclass: I'm involved here and am not going to close, but FWIW, I do think you got your point across; just that myself and some other folks are unwilling to get behind it given the current uncertainty in the community as to what counts as interesting. That is a problem I would be interested in helping fix, and if we manage that, in implementing a requirement for admins to check it. I'm unwilling at the moment not so much because I'm worried about admins abusing the criterion and making arbitrary pulls. I'm more worried that if we require admins to pull "uninteresting" hooks without defining "uninteresting", we're going to have situations where folks are going to yell and shout about admin incompetence because a hook they disliked was not pulled. Vanamonde (talk) 12:10, 14 February 2018 (UTC)
We should remove the interesting to a broad audience aim of DYK in that case. By the time a hook gets to a queue, it's only going to be looked at by two people in general, the reviewer who is looking for a QPQ and the promoting admin (who we're led to believe here is not the right person to judge "interesting"). So beyond the person who wrote the hook (which they'd inevitably believe or hope would be interesting) and the reviewer (QPQ done!), no-one is looking at this fundamental tenet of DYK. Absurd. The Rambling Man (talk) 12:17, 14 February 2018 (UTC)

Formatting

Should administrators be required to check hook formatting for any errors?

  • I would say that administrators should be absolutely required to check for hook interest. This isn't currently a question in this survey but should be IMO. (Issue addressed, see above). As for "formatting", that's a little vague as a question but certainly, I think admins should be checking for grammatical errors, redundancies and possible tweaks to improve readability. Very basic responsibilities in my view. Gatoclass (talk) 03:10, 12 February 2018 (UTC)
  • Yes; as I see it, the admin role here is to keep the main page free bad content; so yes, absolutely, we should check formatting and grammar. @Gatoclass: Feel free to make that a separate question. Vanamonde (talk) 03:44, 12 February 2018 (UTC)
  • Yes admins should check basic things such as it is bolded correctly, and that pictured is used appropriately. For example once I found a hook that did not link to the DYK page. This is quite easy to spot! Graeme Bartlett (talk) 06:39, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:23, 12 February 2018 (UTC)
  • Yes Checking of basic issues like the bold formatting of the primary topic is sensible because this is quite standard and formalised. Andrew D. (talk) 13:25, 12 February 2018 (UTC)
  • Yes as the hook is the thing being promoted, it needs to be correct. Joseph2302 (talk) 13:35, 12 February 2018 (UTC)
  • Yes, definitely. Nomader (talk) 21:35, 12 February 2018 (UTC)
  • Yes. A check for basic errors is good. epicgenius (talk) 23:52, 12 February 2018 (UTC)

Image license

Should administrators be required to check the licensing and use of the image in each set?

  • I'm not sure what "use" refers to here but certainly, it's a yes to checking the image licence. Okay, I recall the guideline about image use and it's a yes to that too. Gatoclass (talk) 03:12, 12 February 2018 (UTC)
  • Admins should absolutely check whether the image is licensed appropriately and used appropriately in the lead article. Vanamonde (talk) 03:45, 12 February 2018 (UTC)
  • yes a straight forward check, that could be done if the file is being protected as well. Graeme Bartlett (talk) 07:05, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:23, 12 February 2018 (UTC)
  • No. We can check that the image has an appropriate licence; but we are absolutely forbidden from judging whether the licence itself is appropriate. (WP:NOCONSENSUS) Hawkeye7 (discuss) 10:03, 12 February 2018 (UTC)
  • No This is one of the points checked by the reviewer and it's no big deal if a fair use image, say, gets through. See WP:Avoid copyright paranoia. Andrew D. (talk) 13:37, 12 February 2018 (UTC)
  • No. I wouldn't say admins should be required, because this should be the reviewer's responsibility, but if they're concerned about the copyright status, admins or set reviewers could definitely have a second look. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No, it should not be required-- but it can still be encouraged. Definitely should not be part of the requirements, however. Nomader (talk) 14:36, 13 February 2018 (UTC)

Hook BLP compliance

Should admins be required to check whether hooks are compliant with WP:BLP?

  • Yes. Surely an obvious point. Gatoclass (talk) 03:14, 12 February 2018 (UTC)
  • Yes. Vanamonde (talk) 03:55, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:24, 12 February 2018 (UTC)
  • No Seen too many cases where NPOV boiled done to POV pushing. Hawkeye7 (discuss) 10:09, 12 February 2018 (UTC)
  • No Admins are obviously able to use their commonsense if a hook stands out as being too provocative but they should not be required to accept responsibility for everything which they are promoting in good faith. Andrew D. (talk) 13:43, 12 February 2018 (UTC)
  • Comment @Gatoclass, The Rambling Man, Hawkeye, and Andrew Davidson: This question has been split, following a discussion below. It is now BLP specific. I have left your !votes in this section. Vanamonde (talk) 14:26, 12 February 2018 (UTC)
  • Fixing malformed ping: @Hawkeye7:. Vanamonde (talk) 14:27, 12 February 2018 (UTC)
  • Yes, this is similar to errors. We wouldn't want insults or something reaching the front page. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • Yes: I think this is the only time where hooks should be reviewed by administrators for any subjective/objective reason based on their content. Nomader (talk) 14:37, 13 February 2018 (UTC)

Hook neutrality

Should admins be required to check whether hooks are compliant with WP:NPOV?

  • Yes, as above. I do not believe flagging NPOV violations on the mainpage constitutes a violation of WP:INVOLVED, if the admin is already involved, or that it would make an admin INVOLVED, if they weren't. Vanamonde (talk) 14:36, 12 February 2018 (UTC)
  • Per Vanamonde93, you cannot as an administrator simply stand by and allow blatant POV hooks to hit the main page because you think it might compromise your UNINVOLVED status to prevent that occurring. Indeed, if you promote a blatantly POV hook to the queue which then goes to the main page, you have arguably done far more damage to your uninvolved status than you would have done simply by returning the hook to the nominations page and asking for a less contentious hook. As I said below, hooks are not, strictly speaking, content in any case, they are pointers to content. I have challenged plenty of hooks for being too contentious and nobody has ever accused me as a result of being INVOLVED. I also think it would be quite a stretch to make such an argument given that in most cases I've never even made a single edit in the topic area in question. Gatoclass (talk) 14:46, 12 February 2018 (UTC)
  • Yes, this is similar to errors and BLP. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • Yes, especially if it is blatant. I think the process for taking hooks down needs to be made clear and the correct editors and this page must be notified. Nomader (talk) 14:38, 13 February 2018 (UTC)
  • Yes, but if an admin perceives that a hook may violate NPOV but isn't blatant, the correct approach is to discuss it with other editors, rather than to remove it unilaterally. feminist (talk) 08:28, 24 February 2018 (UTC)

Hook citation

Should admins be required to check if hooks are mentioned in the article, and have a citation in support?

  • No, but should be strongly encouraged to do so. See response to hook verification below for more explanation. Gatoclass (talk) 03:20, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:24, 12 February 2018 (UTC)
  • No, this should be checked by the reviewer. But an admin can definitely have a re-review. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No, this should be checked first by the reviewer-- if the admin wants to look, they should be encouraged to do so but it is by no means mandatory. Nomader (talk) 14:39, 13 February 2018 (UTC)
  • No, I think this should be checked by the editor who promotes the hook to prep. Cwmhiraeth (talk) 14:47, 14 February 2018 (UTC)
  • No already checked by two people. feminist (talk) 17:43, 23 February 2018 (UTC)

Hook verification

Should admins be required to check if hooks are supported by the cited source, if possible?

  • No, but should be strongly encouraged to do so. I would love to be able to say yes to this question, but given the lack of participation by admins in prep promotion now, we need all the help we can get and can't afford to add requirements that very few admins will be willing to take on. I think "strong encouragement" is the best we can hope for here. Gatoclass (talk) 03:20, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:24, 12 February 2018 (UTC)
  • No, this should be checked by the reviewer. But an admin can definitely have a re-review. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No. Encourage, but not require. Too time-consuming if all promoting admins are required to check to see if all hooks are supported by their sources. This should be checked by the hook reviewer. feminist (talk) 08:24, 24 February 2018 (UTC)

DYK eligibility

Should administrators be required to check if the article meets the length/age/expansion/QPQ requirements?

  • I don't have a strong opinion on this but leaning no because this is something reviewers and set builders should be able to do. Gatoclass (talk) 03:23, 12 February 2018 (UTC)
  • No. If reviewer/promoter carelessness leads to somebody getting a DYK credit they shouldn't, I'm not fussed about it (and I can't recall the last time it happened). Admin time is better spent elsewhere. Vanamonde (talk) 03:56, 12 February 2018 (UTC)
  • This should be part of the initial DYK check, but it is worth checking if the right people are listed for credit. Also they should take a quick look at the article to make sure it is at least big enough and not total rubbish writing. Graeme Bartlett (talk) 06:41, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:24, 12 February 2018 (UTC)
  • This should have been done automatically; but I have seen it where text was removed from an article, bringing it below the minimum. Hawkeye7 (discuss) 10:06, 12 February 2018 (UTC)
  • No, this should be checked by the reviewer. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No, this is to be done by the reviewer. Nomader (talk) 14:41, 13 February 2018 (UTC)
  • No, That's the reviewer's and set builder's job. Otherwise you may as well just hand over all reviews to admins only. The C of E God Save the Queen! (talk) 08:11, 14 February 2018 (UTC)
  • No, this is the responsibility of the reviewer, and if an article that is only 1497 B gets to the front page, or a hook with 202 characters makes it, that is absolutely unimportant. Cwmhiraeth (talk) 14:53, 14 February 2018 (UTC)
  • No. However, if the article was eligible when approved by the reviewer but subsequently had changes made to it that caused it to be ineligible, the correct approach should be to restore to the approved version, rather than to pull the hook. This can be done by any editor with WP:Twinkle or similar. feminist (talk) 08:26, 24 February 2018 (UTC)

Article copyright

Should admins be required to check the article for copyright issues?

  • No, but should be encouraged to do so. See my response to hook verification question above for reasons. Gatoclass (talk) 03:25, 12 February 2018 (UTC)
  • No, because it places too much of a burden on the promoting admin. I would certainly spot-check articles occasionally, as a way of keeping reviewers accountable, but I think we cannot require the promoting admin to check everything. Vanamonde (talk) 04:22, 12 February 2018 (UTC)
  • No, this should be a discretionary call. Promoting admin should read the article to see if there are any issues, and if any suspicions are raised, than it makes sense to double check with the nomination page and run a copyvio check if deemed necessary. It's counter-intuitive to force promoting admin to manually check every single article in a 8-hooks set for copyright issues when it's something that should have been done at the very beginning of a DYK review. If the process is broken, it's the review part that needs to be addressed and fixed in this case. Alex Shih (talk) 06:19, 12 February 2018 (UTC)
  • No as this should already have been done before. Since this is time consuming, few admins would bother. Graeme Bartlett (talk) 07:03, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:24, 12 February 2018 (UTC)
  • No, this should be checked by the reviewer. An admin or set builder can use the copyvio detector if there are any concerns. epicgenius (talk) 23:52, 12 February 2018 (UTC)

Article verifiability

Should administrators be required to check sourcing in the article?

  • That depends on what is meant by "check". I would say admins have a responsibility to do a quick scan of the article to see that it is well presented and that content is appropriately cited. I don't think you can expect them to go combing through sources trying to figure out whether or not they are sufficiently reliable. Gatoclass (talk) 03:34, 12 February 2018 (UTC)
  • Sort of. I'd say admins are required to check if references are present where they should be, and that appear reliable. If somebody uses facebook as a source, I do think admins are required to catch that, in the unlikely event that reviewers and promoters have missed it. Vanamonde (talk) 04:01, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:25, 12 February 2018 (UTC)
  • Not really. An admin could have a quick look but this should be checked by the reviewer. Admin intervention should only be required if there is a blatant and obvious violation. epicgenius (talk) 23:52, 12 February 2018 (UTC)

Article BLP compliance

Should administrators be required to check the article for BLP issues?

  • As above, admins should do a quick scan of the article to ensure there are no obvious issues. I don't think you can expect them to thoroughly read every word looking for such issues. Gatoclass (talk) 03:34, 12 February 2018 (UTC)
  • No per Gatoclass, I do not expect that admins can check every article for anything more than blatant violations. Vanamonde (talk) 03:59, 12 February 2018 (UTC)
  • Yes because the review process is not fit for purpose and therefore when an admin sanctions an item for the main page they need to be responsible for its quality and content. The Rambling Man (talk) 08:25, 12 February 2018 (UTC)
  • No Seen too many cases where NPOV boiled done to POV pushing. Hawkeye7 (discuss) 10:09, 12 February 2018 (UTC)
  • Comment As above, question split per discussion below, !votes left here, pinging @Gatoclass, Hawkeye7, and The Rambling Man: Vanamonde (talk) 14:29, 12 February 2018 (UTC)
  • Not really. An admin could have a quick look but this should be checked by the reviewer. Admin intervention should only be required if there is a blatant and obvious violation. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No, Have a quick look yes, but it should not be an admin's main role. The C of E God Save the Queen! (talk) 08:09, 14 February 2018 (UTC)

Article neutrality

Should administrators be required to check the article for NPOV issues?

  • No, as above. I do not think admins can be expected to check for anything more than blatant violations. Vanamonde (talk) 14:33, 12 February 2018 (UTC)
  • As above, I think a quick scan is all that's necessary. If you have reason to believe a particular article might contain significant bias, you may want to take a closer look, but submissions of this type are pretty rare at DYK these days anyhow, so it's not as if it's a major addition to your workload. Gatoclass (talk) 15:08, 12 February 2018 (UTC)
  • Not really. An admin could have a quick look but this should be checked by the reviewer. Admin intervention should only be required if there is a blatant and obvious violation. epicgenius (talk) 23:52, 12 February 2018 (UTC)
  • No per my other responses. Nomader (talk) 14:44, 13 February 2018 (UTC)
  • No. This should be checked by the reviewer, plus maybe the set builder. feminist (talk) 08:29, 24 February 2018 (UTC)

Threaded discussion

@Vanamonde93: Are you asking if admins should perform or re-check all reviews? I'm just wondering, since this is what the RFC sounds like. epicgenius (talk) 18:26, 11 February 2018 (UTC)

Similar question, when you say "are they" do you mean "should they"? The Rambling Man (talk) 19:25, 11 February 2018 (UTC)

"Are" and "should" are very different questions, and I would answer them differently: are they now supposed to versus should they do it. If this RfC is to produce useful information, I'd suggest going with one or the other rather than a mixture of both, and I imagine that "should" will point the way forward. BlueMoonset (talk) 19:44, 11 February 2018 (UTC)
IMO I think the current admin instruction is clear on that the key role for admins at DYK is to approve hooks to queue. I presume that's why they are being asked with "should" here. But I don't see any questions surrounding this. Running a copyvio check prior to approving is ideal but quite unrealistic in real time (unless if there are obvious concerns from a quick reading; this is when I'd move on to check the nomination page, as checking for copyvio is one of the first tasks in a proper review, which I think will be addressed in the next planned RfC?). Alex Shih (talk) 20:01, 11 February 2018 (UTC)
It's absolutely not unrealistic for admins to run a copyvio check (apparently Earwig doesn't take too long), and since articles can change drastically between review and promotion, it's absolutely incumbent on admins to not promote items to the main page with copyvios (for instance) so they must check for that, and abuse of fair use images too in my opinion. The Rambling Man (talk) 20:07, 11 February 2018 (UTC)
Theoretically any admin moving something to a queue should check for anything that's not policy-compliant (BLP, NFCC, COPYVIO). Anything else (i.e. hooks that are wrong or misleading) should have been picked up previously (hollow laugh). Black Kite (talk) 21:23, 11 February 2018 (UTC)
You realize that this is going to result in less admins working in this area, right? The (very) few times I've promoted a hook I've viewed it as a purely technical task. I'll obviously look for BLP vios but am trusting the DYK reviewers have done their jobs. I'm not saying there's anything wrong if the community wants to assign extra responsibility to the promoting admin, just that the admins who occasionally assist might not want to do so going forward. --NeilN talk to me 03:45, 12 February 2018 (UTC)
  • @Epicgenius: Hmm. I thought I had created a clear rfc, but apparently not. I'm asking each question separately. We can decide that admins should check everything, some things, or nothing. That is up to the community. @The Rambling Man: I will amend the wording inconsistencies,but I'm essentially asking what admins should be doing. Given your statement here, might I ask you to vote yes on the relevant options above? Karellen93 (talk) (Vanamonde93's alternative account) 03:03, 12 February 2018 (UTC)
  • Addendum: TRM: I've now fixed the wording. I didn't realize it was confusing, but it was. There are of course several things admins are required to do at the moment according to the instructions, but current practice (and, I suspect, consensus) has moved away from some of them. @Black Kite: Since I've now fixed the wording, would you care to express those opinions above? Vanamonde (talk) 03:41, 12 February 2018 (UTC)
  • One thing I am wondering about with regard to this RFC is, should responses be limited to administrators only? After all, this only pertains to admin responsibilities, these are not questions that non-admins are ever going to have to consider. I'm not sure it's even possible to limit RFCs in such a way though. Gatoclass (talk) 03:48, 12 February 2018 (UTC)
  • @Gatoclass: I did consider this; in particular, I was worried that a set of responsibilities considered too burdensome may drive admins away. But fundamentally I think this is about the DYK process and main-page integrity, questions which I do not think we can limit to admins. Cheers, Vanamonde (talk) 04:06, 12 February 2018 (UTC)
I'm just a little concerned that non-admins are going to look at these options, think to themselves, oh sure, it would great if admins did all these checks! - without considering the burden it would add to administrators who might otherwise be willing to contribute to the running of DYK and the likely exodus of admins from participation as a result (see comment by NeilN as an example of the likely response). Gatoclass (talk) 04:15, 12 February 2018 (UTC)
Fair enough; but I'd rather try to sort that out by asking admins concerned about the burden of these checks to comment above and make it clear that a large number of tasks would lead to them reducing their participation, rather than by limiting participation in the RFC, which would lead to tremendous ill-feeling (even if there was a basis in policy for it, which I'm unsure about). Vanamonde (talk) 05:20, 12 February 2018 (UTC)

I think this sadly a waste of time really. This isn't really where the conversation needs to be going. What's the primary issue with DYK at the moment? Bad quality reviews leading to items being passed. The admin role at the very end of the process may need some examination, but if all the checks and measures that should have been performed correctly by the reviewers has been performed correctly by the reviewers, the admin role is perfunctory. We need to talk about the root cause of the problem, not the peripheral issues which, it's already clear, is not going to change anything. But as far as I'm concerned, right now the admin has to do the whole review process from scratch because the system is so broken. That's the reality of the situation. Hooks can't be trusted, sources can't be trusted, articles are being promoted regularly which fail DYK rules and supplementary rules. Hooks are going into sets days or weeks after they're ticked during which time anything can have happened to them so they need re-review.... there's too much wrong at the source here to worry about the role of the individual at the last step of the process right now. The Rambling Man (talk) 07:34, 12 February 2018 (UTC)

Okay, but there are a lot of things that need addressing at DYK and we can't deal with all of them at once. Vanamonde93 has long wanted clarification of the role of administrators and since it's a relatively straightforward issue to examine, it just happens to have become the first thing we are looking at. Accountability of reviewers and other matters have also been raised in the process of discussion and I'm sure we will be getting to some of these other more complex issues soon enough. Gatoclass (talk) 08:33, 12 February 2018 (UTC)
No, it's not clear what the expectations of the role of an admin here are until we have defined what they are faced with which, at the moment, is a load of unreliable reviews which need to get re-done from scratch. People who are charged with promoting items to the main page have to be 100% responsible for the content, so if they're not bothering to do the job properly knowing that what they're promoting is probably deficient then they ought not to do the job at all. The Rambling Man (talk) 08:36, 12 February 2018 (UTC)
The admin role is generally perfunctory. All the checks should have already been already performed by the reviewers. It is possible for the article to have changed in the meantime. We must be more tolerant of errors if we are to promote a collegial atmosphere where people enjoy contributing to DYK (and Wikipedia). Hawkeye7 (discuss) 10:23, 12 February 2018 (UTC)
Wikipedia is not a social club, we're not here to be "nice", we're here to create quality content and serve our readers. Remember: we are here for the readers. We absolutely must not tolerate errors, especially from those who make them time after time. The Rambling Man (talk) 10:26, 12 February 2018 (UTC)
TRM, nobody is avoiding any issues here, and I am sorry you see this RFC that way. I agree that the core issue is review quality; which is why I have made proposals above to address this. Those proposals are just not ripe for an RFC yet, in my view, and require further discussion. If you feel otherwise, feel free to start such an RFC. The admin role was ripe for an RFC, and so I started one. It's a manageable problem. Nobody's saying it's the only one. Vanamonde (talk) 13:41, 12 February 2018 (UTC)
I'm not suggesting anyone is avoiding issues, just not focusing on the real issues. A little like rearranging deckchairs on the Titanic. If reviews are conducted 100% correctly, then admins should do nothing beside promote preps. If reviews aren't conducted 100% correctly, what an admin needs to do is on a sliding scale from nothing to complete re-review. That seems obvious to me. The Rambling Man (talk) 13:51, 12 February 2018 (UTC)
That assumes the review process is going to remain unchanged, though: whereas there are proposals above to fix those. I'm trying to find a comprehensive set of fixes, not a single magic bullet. Vanamonde (talk) 14:31, 12 February 2018 (UTC)
No it just assumes that reviewers aren't good enough. The Rambling Man (talk) 14:44, 12 February 2018 (UTC)

Why are the neutrality questions combining NPOV and BLP issues? Admins are empowered to address BLP issues anywhere on the project but there's no way in hell I'm judging NPOV (content issue) as an admin. That opens me up to WP:INVOLVED accusations, and rightfully so. --NeilN talk to me 13:58, 12 February 2018 (UTC)

@NeilN: Fair point; would you like to split those off into separate questions? Vanamonde (talk) 14:10, 12 February 2018 (UTC)
@Vanamonde93: Probably should as I'd imagine most admins feel the same way. As in, yes I'll go the extra mile and check for BLP issues the reviewers might have missed but addressing NPOV is beyond my remit. --NeilN talk to me 14:18, 12 February 2018 (UTC)
NeilN, sometimes we get incredibly biased hooks, for example, demonizing one side in a political conflict. As an administrator, you can't just stand idly by and let crap like that hit the main page, because if you do there may well be an uproar (and rightly so). So you have to be prepared to simply say "this hook isn't ready for prime time, you need to come up with something less contentious." I don't think that will fatally compromise your UNINVOLVED status at all. Hooks are not, strictly speaking, content in any case, they are pointers to content. But if you are keen to remain strictly UNINVOLVED, there's no harm in you simply skipping a queue promotion with NPOV issues and leaving it to another administrator. Far better to do that than make yourself party to a blatant POV violation on the main page. Gatoclass (talk) 14:29, 12 February 2018 (UTC)
@Gatoclass: Can you please give some examples of these hooks where an admin overrode editor consensus? --NeilN talk to me 14:36, 12 February 2018 (UTC)
We actually very rarely get blatantly POV hooks, and I don't have the inclination to go searching for an example right now. Maybe I'll take a look tomorrow if I can find time. But pulling a hook is not "overriding consensus" anyhow, it's more like asking for a clearer consensus. Gatoclass (talk) 14:52, 12 February 2018 (UTC)

Admins are not editors (although they are editors with extra buttons, it's a different function). We should not give admins per se editorial function, so I will again suggest something I had suggested awhile ago, we have an elected board of overseers or coordinators, who oversee, including editorial, resolve disputes, etc. -- Alanscottwalker (talk) 13:59, 12 February 2018 (UTC)

Alanscottwalker, are you talking about DYK specifically or the project as a whole? Gatoclass (talk) 14:33, 12 February 2018 (UTC)
Gah! :) No, I don't think we can take on the whole project, here, just DYK. (My idea partly comes from FAC, which at one time elected coords, I assume they still do and partly just the idea of a semi-editorial board that allows for ease of functioning not fighting - or delegating to committee, if you will) -- Alanscottwalker (talk) 14:42, 12 February 2018 (UTC)
Oh okay, the old "DYK directorate" notion. At one time I probably would have been strongly in favour of that. These days, they would probably have to offer me a very attractive wage to serve on it. Gatoclass (talk) 14:59, 12 February 2018 (UTC)
Well some others might (just like some volunteer to be admins :)) and you would have the legitimacy of a beautiful hat, or rather, visor. Alanscottwalker (talk) 15:32, 12 February 2018 (UTC)
  • Comment this is, as I predicted, a complete waste of time. We have no agreement over the fundamental and important issues of what an admin should be doing here, moreover we have complete failure to understand the fact that no-one besides the QPQ (yes, it passes!) reviewer is doing all this heavy work. My original point (reviewers aren't doing the job properly) completely defines what admins need to do, not the other way round, until such a time that we have confidence that the review process works. In the meantime, this well-meaning poll of DYK regulars is of no use at all. The Rambling Man (talk) 22:06, 14 February 2018 (UTC)
I believe the set builders are also supposed to fact check the hooks. So there are three levels of built-in review: initial reviewer, set builder and promoting administrator, not two as you have stated here. Gatoclass (talk) 04:30, 15 February 2018 (UTC)
While I suspect the three levels of built-in review were meant to be the case, to maximize the chances that errors in the original review would be caught before hooks made it to the main page, there has never been agreement that it should be done. So we currently have a hodge-podge: some set builders do comprehensive checks, while others will do only a few, generally related to the hook. Some admins will do comprehensive checks before moving a set from prep to queue, while others will just do a quick look-over. So instead of guaranteed redundancy in all checking, we have some sets that are well checked, while there are others that get minimal checking at both prep and queue stages.
It seems to me that this RfC has put the cart before the horse: until we determine what we're going to require of DYK reviewers and what strategies we're going to employ at the review stage to try to ensure the best possible results at that stage, we don't know what level of checking we're going to need from people putting prep sets together—where the redundancies need to be—and then, based on that, what checks are most critical for admins to make. Not just whether the original reviewer caught everything, but also what we want in terms of checking changes to the article since the most recent review, because articles can be the same, enhanced, or made less reliable while waiting to be promoted and while sitting in prep. BlueMoonset (talk) 06:44, 15 February 2018 (UTC)
@BlueMoonset: I see where you're coming from, but I disagree. There is no disagreement whatsoever over what an initial reviewer is supposed to do; which is, to thoroughly check each and every one of the DYK criteria. The question we have to work out is how to ensure that they perform these checks. This issue isn't yet ripe for an RFC, but there are proposals above (why do I keep having to repeat this?) to address this issue. I would be interested in hearing your thoughts there. Vanamonde (talk) 13:05, 15 February 2018 (UTC)
I agree BlueMoonset. This is rearranging deckchairs. We need to understand what's so wrong with the review process before we worry about what an admin needs to do. Admins should be just promoting preps to queues and nothing more. The fact they can't because of quality issues means they have to effectively do the whole review again themselves as in promoting to queues, they're accepting responsibility for what's going to appear on the main page. The Rambling Man (talk) 13:21, 15 February 2018 (UTC)
It looks like I disagree with you both. Vanamonde, no matter how carefully one thinks one has done a review, it's always possible to overlook something: we have to allow for error despite general competence in addition to error due to lack of understanding or inexperience or failure to adequately check all the criteria. (It isn't just how to ensure they perform the checks; it's how to ensure they perform them well. Earwig is a blessing and a curse: a blessing in that sometimes copyvios/close paraphrasing is found, and a curse in that most people do not understand its limitations and miss copyvios due to misunderstanding the results and close paraphrasing because they don't realize Earwig rarely finds it.) The next line of defense is currently at the point of promotion to prep, though there could be others added at the review stage. However, unlike The Rambling Man, I don't see admin promotion to queue ever being a straight promotion without checking because admins have to take responsibility for what's going to appear on the main page. I don't see how they can safely trust that everything was done perfectly at the prior stages; even with the best of intentions and following the expected process, human error will occur. BlueMoonset (talk) 19:09, 15 February 2018 (UTC)
Well if you truly believe that, than admins need to fully re-review hooks - they don't get credits, they're not gaining QPQs, so they're ideally placed to check every rule of DYK is being followed. Too much COI for reviewers seeking out QPQ, or WikiCup points or whatever, the end result being that there's no real quality control going on at DYK at all. The Rambling Man (talk) 19:53, 15 February 2018 (UTC)
I agree with you BlueMoonset that administrator promotion to the queue can never be a rubber stamp for the reasons you outline. But neither can we expect admins to do complete reviews of entire sets. The question is where to strike the right balance. That's what this RFC is about, and for the reasons given, I don't think it matters a great deal whether we hold it now or wait to see what additional safeguards can be added to the earlier reviews. Gatoclass (talk) 07:03, 16 February 2018 (UTC)
It's absurd. There is no "right balance", either admins believe reviews have been conducted correctly, or they don't. If they don't, they need to review articles from scratch because there's no telling what could be wrong. If they do, they just promote to a queue and accept that when the shit hits the fan, it's their responsibility or at least they defer their responsibility to the one reviewer. That's what makes this entire RFC a waste of time. What a promoting admin should do is ensure that everything that goes to the main page is suitable. How that's achieved is entirely down to the quality of review beforehand. Let's deal with that first, and then worry about what admins should be doing. The Rambling Man (talk) 20:25, 16 February 2018 (UTC)
What it all boils down to is whether admins can rely on the nominator, reviewer and promoter to get things right. When promoting an article, the main check I always make is whether the hook is accurate, the hook facts are in the article and are backed up by inline citations. Sometimes this is easy and sometimes it isn't, and on occasions it is a matter of opinion and I don't always get it right. The admin moving the set into the queue needs to ensure that things have not changed materially since each hook was reviewed and promoted. I think it questionable whether they need to check the hook in detail again, and think their time is better used if they check that the article is policy compliant and free from copyvios. In this regard, people like TRM and Nikkimaria, who informally check the hooks in prep, are performing a useful service. Cwmhiraeth (talk) 09:54, 18 February 2018 (UTC)

We can do it!

The article Naomi Parker Fraley showing the iconic poster was requested for 3 Feb. That didn't work. How about postponing it to March, possibly even 8 March IWD? Now lead in prep 2. --Gerda Arendt (talk) 18:47, 11 February 2018 (UTC)

If we B & Q it? (sorry @Martinevans123:! Had to make that joke.) The C of E God Save the Queen! (talk) 19:30, 11 February 2018 (UTC)
This kind of blatant commercial linking will see you banned, C of E It's up there with Elon Musk's Tesla Roadster. (well, not literally of course). Although all the stars go there, apparently. Martinevans123 (talk) 19:49, 11 February 2018 (UTC)
I'm still concerned that the article doesn't even agree with the hook, that Parker was the "most likely" inspiration for the poster. Indeed, it's even pointed out that the artist rarely worked from photographs anyway. (Even further, I'm not 100% convinced that Parker is even notable, since it can't be confirmed that she was the poster girl, but that's not relevant to DYK). Black Kite (talk) 19:41, 11 February 2018 (UTC)
There was some discussion on the talk page about this being made a redirect to We Can Do It. Yoninah (talk) 22:17, 11 February 2018 (UTC)
I have pulled the hook from prep 2 given the above concerns and, per Gerda Arendt's suggestion, placed it in the special occasions section for March 8, which should give plenty of time for the issues to be addressed or the article to be redirected or whatever. BlueMoonset (talk) 07:33, 15 February 2018 (UTC)
I think there is some overthinking here. Lets imagine that we find definite proof that its not Naomi in the photo or poster. In that case, then she would be in exactly the same position as Geraldine_Doyle. Its certain that Geraldine is not the girl in the poster, but she has a Wiki article and she's in the Michigan Hall of Fame - for good reason! What matters here is not what one or another editor thinks, but does a reliable source say she is "most likely" and has she been the source of substantial interest by reliable sources? YesY Victuallers (talk) 16:56, 21 February 2018 (UTC)

Template:Did you know nominations/Christ the Lord Is Risen Today

The C of E wants this to go up on Easter (which this year happens to fall on April Fools Day), but Gatoclass has raised an objection, stating that the April Fools hook isn't funny enough; he is instead proposing that a more seriously-worded hook run on a different day. How should this be resolved? Narutolovehinata5 tccsdnew 01:00, 14 February 2018 (UTC)

Just so that people know what is being talked about here (and I'd much rather have the discussion here rather than at the nomination page where not enough people will see it), the supposed April Fools hooks are as follows:

... and the straight alt proposed is:

  • I would support a more serious hook to be run on a different day. The current hook is almost recycled from the Jesus Christ Is Risen Today hook back in April 2014 (... that "Jesus Christ is Risen Today"?), which created a time sink for everyone involved. If anything, I would exercise more care (learn from past mistakes) and creativity (don't duplicate). Alex Shih (talk) 04:34, 14 February 2018 (UTC)

As I said at the nomination page, I think a straight hook, such as ALT2 proposed above, could be run on April Fools day (probably in the slot normally reserved for a quirky because it would look totally incongruous in the middle of a bunch of joke hooks), because April 1 apparently happens to be the right date for this hook this year and there's no actual rule that says we can't run a straight hook or two on April Fools anyway. Alternatively, as Alex notes, it could just be run on a different day close to the day in question.

Apart from that, what concerns me about the original hook proposed is that firstly, it isn't the least bit funny or April Fools-ish, and secondly, it smacks of proselytism. It just has nothing to recommend it in my view, especially as an April Fools hook because it's neither misleading nor funny. Gatoclass (talk) 04:52, 14 February 2018 (UTC)

There is nothing wrong with the originals as they are taking the articles and presenting them in way that can be taken either way. You can either take it as an April Fools hook that ties in with Easter (which is how most people will see it) or you can take it seriously. As for the storm in a teacup that happened last time, the feeling I got from that was that many people thought it was an April Fools hook being used on a non-April Fools Day. Not to mention there were no complaints about it until days after. This cannot run on any other day as I had specifically written it for Easter. The C of E God Save the Queen! (talk) 08:07, 14 February 2018 (UTC)

Avoid the time sink, go with something like ALT2. The Rambling Man (talk) 08:10, 14 February 2018 (UTC)

I'd go for a clear Easter hook, without refreshing the sad memory of the consequences of attempted quirkyness, but ALT2 wouldn't raise my interest.
In the context: how many more Easter-related hooks may we have on 1 April? --Gerda Arendt (talk) 08:10, 14 February 2018 (UTC)
If you want quirky, use the factoid about the Llanfair tune variant of the hymn being written by "Robert Williams in Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch" (but please disambiguate Robert Williams before Easter...) The Rambling Man (talk) 08:14, 14 February 2018 (UTC)
Could always do ALT3 ... that Christ the Lord Is Risen Today in Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch? The C of E God Save the Queen! (talk) 08:16, 14 February 2018 (UTC)
ALT4: ... that the "Llanfair" tune commonly used for the Christian hymn Christ the Lord Is Risen Today is named after Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch? The Rambling Man (talk) 08:18, 14 February 2018 (UTC)
Or we could merge both alt3 and the original together as a compromise and say ALT5 that it was discovered in the first Methodist chapel that Christ the Lord Is Risen Today? The C of E God Save the Queen! (talk) 08:26, 14 February 2018 (UTC)
  • ALT4 looks acceptable to me, it looks to be both accurate and a good fit for April Fools, given that it's hard to believe there's a place with a name like that. Gatoclass (talk) 09:56, 14 February 2018 (UTC)
    • I disagree, it takes the focus off the hooked article plus its too descriptive and gives too much away to the point where it loses its AFD sting. The C of E God Save the Queen! (talk) 10:01, 14 February 2018 (UTC)
It's fine to keep the focus on the hooked article where possible, but it shouldn't be done at the expense of every other consideration, such as a professional and accurate presentation. Gatoclass (talk) 10:17, 14 February 2018 (UTC)
  • I don't see any policy-based reason to strike original hook/ALT1. The nom stated his intent was to run it on Easter. Unless we're going to carve out some new policy to specifically deal with hooks we don't like, we should approve original/ALT1.– Lionel(talk) 10:04, 14 February 2018 (UTC)
  • Lionel, please look up the sad history. It went to the talk page of the admin who had promoted it, questioning his integrity and ability to be an admini. Long live his memory. - How about a wording that the hymn was written by W., a co-founder of the Methodist church? --Gerda Arendt (talk) 10:15, 14 February 2018 (UTC)

The C of E seems to be begging to be blocked for disruption if he thinks his hooks were in any way acceptable, after the previous attempt to have such proselytizing on the main page backfired quite badly. Perhaps some topic ban may help. In any case, I would expect someone so keen on pushing his faith to the front page of an encyclopedia to know that Easter is not the same as Ascension, which is the current image in that article. Or is that part of the April Fool's Joke, to make enwiki look even more ridiculous?

Furthermore, isn't it somewhat against the rules of DYK to first remove 961 bytes of text[3] ("coincidentally" on April 1 2017) to be able to get a 5-fold expansion one year later, by among others re-introducing the information about the LLanfair and Easter Hymns tunes? In reality, counting from before the C of E removed correct information, we get a 3-fold expansion, not a 5-fold one. Basically, this nomination should be failed and the C of E trouted for numerous infractions and refusal to get the point that DYK (and enwiki) is not the place to push his belief. Fram (talk) 09:33, 19 February 2018 (UTC)

I think The C of E is hoist on his own petard for this one. April Fools' Day has special rules regarding newness/expansion: April Fools DYKs are subject to the usual exclusions regarding prior Main Page appearance, but the normal rules for special occasions do not apply: the article need only have been created/expanded/brought to GA in the year immediately preceding the April 1 on which it will appear. This means that the expansion dates back to the previous April 1, which is also the date on which the article was cut back and then left unedited until earlier this year when it was expanded. So it is indeed an expansion of 1531 to 4938 prose characters, far from the 7655 characters needed to be five times its pre-revision size. BlueMoonset (talk) 15:44, 19 February 2018 (UTC)
I suggest the nomination is re-opened and formally failed then. The Rambling Man (talk) 15:50, 19 February 2018 (UTC)

How can there even be a consideration of rewarding such blatant gaming of rules with a spot on the main page? It would send an entirely wrong message and will be bound to be repeated. Removing content, waiting a few months and then re-adding some of the previously removed content while expanding the article... seriously?!? 91.49.68.207 (talk) 19:38, 20 February 2018 (UTC)

@Fram: Just curious: how is a religious-themed hook on DYK considered proselytizing? Since we've had hooks on topics related to religion before. And as an aside, I'll now mark the nomination for closure. Narutolovehinata5 tccsdnew 23:50, 20 February 2018 (UTC)

  • Let's see, how could claiming on the front page that "Did you know that Christ the Lord Is Risen Today?" be considered proselytizing? It is not really presenting a wel-sourced fact from the article, it is presenting the title as literal truth. No, that can't be proselytizing, that's standard behaviour. Certainly from someone who already got "Did you know that Jesus Christ is Risen Today?" on DYK 4 years ago and got a lot of well-deserved flak for that as well, someone who promotes church in his user name and fundamentalist religion on his user page quite blatantly. If you can't see how this is prosletyzing, then please saty away from DYK review as you are clearly not able to judge the appropriateness of hooks at all. Fram (talk) 05:42, 21 February 2018 (UTC)
  • Thank you, Narutolovehinata5, for closing this nomination. I don't think you were aware of the past history (with the editor, and this re-used hook). I hope this brings closure. Alex Shih (talk) 05:52, 21 February 2018 (UTC)
Thanks for the messages @Fram: and @Alex Shih:. I wasn't aware of the user's previous history, nor the fact that this had already had a previous failed nomination. I had reviewed the nomination in good faith, not being aware of its previous problems (I even used the tools, which all checked out). Had I been aware of the issues, I would have failed the nomination immediately. Narutolovehinata5 tccsdnew 07:03, 21 February 2018 (UTC)

I have now closed the nomination as unsuccessful. Narutolovehinata5 tccsdnew 07:05, 21 February 2018 (UTC)

...and The C of E has re-opened it. This might need some more eyes. Narutolovehinata5 tccsdnew 12:00, 21 February 2018 (UTC)
The C of E is proposing to expand the article to correctly meet the x5 requirement, so I think we can wait and see how he goes with that. Gatoclass (talk) 13:02, 21 February 2018 (UTC)

Jackie Wallace

Before I move this hook to prep, are people happy with the hook, or do you think it raises BLP issues? Homelessness and addictions seem to have been a major part of his later life. Cwmhiraeth (talk) 07:37, 16 February 2018 (UTC)

My concern about this hook is that it could be seem as misleading to suggest that Jackie Wallace became homeless shortly after/because of having appeared in two Super Bowls, which really isn't the case. Personally I would add some additional lines, for instance ALT1 ... that Jackie Wallace, a former NFL player who appeared in two Super Bowls, was found living on the streets after his playing career? Pinging Muboshgu and Epicgenius for thoughts. Alex Shih (talk) 08:26, 16 February 2018 (UTC)
Seems like the alternate hook would be a decent alternative. It doesn't really violate WP:BLP since it merely states facts that are already discussed in the article. Narutolovehinata5 tccsdnew 10:04, 16 February 2018 (UTC)
My thought process here is that the best hooks are the shortest hooks, the ones that give away less detail. So, I didn't spell it out to "became homeless after his playing career", but perhaps in this case I should have. Does that ALT 1 say too much? – Muboshgu (talk) 14:59, 16 February 2018 (UTC)
Well, in terms of length, ALT1 isn't a problem. But more to the point, neither hook violates BLP policy because all parts of each hook are sourced. epicgenius (talk) 15:04, 16 February 2018 (UTC)
What about this?

None of the above. We're not supposed to focus on negative aspects of life, so this is just a bit too shitty to post. Can we come up with something more uplifting please? Addendum: wow, the guy's whereabouts are currently unknown following another relapse and you people want to make a DYK about it? What? The Rambling Man (talk) 21:47, 16 February 2018 (UTC)

There's something distasteful about the thought that this poor guy's out on the street somewhere and a DYK about it is being splashed on WP's main page. EEng 22:48, 16 February 2018 (UTC)
Exactly. Fail the nom, get something better. We are better than this. To even consider this as a nomination is sickening. The Rambling Man (talk) 22:49, 16 February 2018 (UTC)
It would be different if he'd recently given an interview or something i.e. participated in telling his own story. But just feels exploitative, though I know that's not the intention. EEng 22:54, 16 February 2018 (UTC)
Have you not read this? He's fully taking part in this story. In no way is this exploiting the man. – Muboshgu (talk) 00:28, 17 February 2018 (UTC)
No, I hadn't read it. The article said In July 2017, Wallace disappeared again, having relapsed and returned to the streets. Since then, his exact whereabouts are unknown and I was going by that. EEng 01:30, 17 February 2018 (UTC)
That article was actually very interesting. How about this? epicgenius (talk) 01:26, 17 February 2018 (UTC)
  • ... that Jackie Wallace, who appeared in two Super Bowls, has not been seen since July 2017?
  • ... that Jackie Wallace, who appeared in two Super Bowls, was found on the streets of New Orleans in 1990 after not having been seen in a decade?
  • ... that Jackie Wallace, who appeared in two Super Bowls, got sober after a photojournalist found him on the streets of New Orleans in 1990?

Thanks, epicgenius. I'm thinking your first suggested alt would be a safe but still interesting option. The second might be a pass, I'm not keen on the third. Another issue we might want to look at here however is whether the coverage of Wallace's later life in the article is somewhat WP:UNDUE, given that that section is as long as the section covering the career for which he is notable. Gatoclass (talk) 01:47, 17 February 2018 (UTC)

Well, given that his post-career life is about 7 times longer than his NFL career, I think that's fair. But the homelessness aspect is interesting to me. The only thing that might be problematic is a lack of info in "Early life". epicgenius (talk) 01:56, 17 February 2018 (UTC)
Given that his career was some time ago, and he wasn't exactly one of the best players in the league, I believe the weight is appropriate. – Muboshgu (talk) 02:00, 17 February 2018 (UTC)

I don't think this ought to be on DYK at all. This is not a criticism of the article, which is indeed interesting, but it's in poor taste to feature the misfortunes of the man on the main page. I've already complained about the original hook here, which just shows how disoriented I am in this part of Wikipedia. It obviously wasn't the right place, and nobody answered me. Anyway.. not sure non-regulars are welcome on this page either, but now I've found it, I don't really think any of the suggested modifications make a difference. Having Jackie Wallace on the main page still amounts to rubbernecking at misfortune. Of course I don't think that was the intention! But IMO it's the effect. And while I appreciate Epicgenius's attempt at a more uplifting hook, "... that Jackie Wallace, who appeared in two Super Bowls, got sober after a photojournalist found him on the streets of New Orleans in 1990?", it's quite misleading as to the narrative arc of the article. As, frankly, any kind of "uplifting" hook would be. Bishonen | talk 16:19, 18 February 2018 (UTC).

Sorry if this is getting away from the main issue, but it looks to me as if Wallace only appeared in one Super Bowl. The articles says "He spent his rookie season on the Vikings' practice squad, including Super Bowl VIII." That means he did not play (appear) in VIII. He did play in IX. His final chance to "appear" according to the article was "His final game in the NFL was Super Bowl XIV as a member of the Rams. After the game, he berated his coach in the Rose Bowl locker room for not using him in the game." So that says he didn't play, but stayed on the sidelines the whole game. Smallbones(smalltalk) 17:11, 18 February 2018 (UTC)
Of course non-regulars are welcome here Bishonen! We generally don't get nearly enough feedback on this page (and please, feel free to get involved in any of the other current discussions here).
With regard to this article, I am concerned as I said that the focus on his post-NFL difficulties in the article is UNDUE, at least for a DYK nomination. But admittedly, it is kind of hard to ignore the issue. I did try to improve things a bit by linking his homelessness to the concussion issue, but it still doesn't seem like enough somehow. Gatoclass (talk) 17:07, 18 February 2018 (UTC)

This is a fail. Find something about his career or drop the stick. We don't celebrate homelessness. DYK is plumbing the depths of pathetic here. The Rambling Man (talk) 21:33, 18 February 2018 (UTC)

We don't ignore reality either. The Main Page isn't supposed to be some fantasy world where everybody is A-OK. This isn't a BLP violation, there should be no problem with this. – Muboshgu (talk) 17:27, 20 February 2018 (UTC)

Here's an editorial from The Times-Picayune over the weekend about the viral success of their article that formed the basis of this five-fold expansion. It makes it pretty clear that the Wiki article has due weight. – Muboshgu (talk) 17:32, 20 February 2018 (UTC)

Then create a hook about the viral success, not simply based on the "Super Bowl vs homelessness" thing. The Rambling Man (talk) 22:41, 20 February 2018 (UTC)
@The Rambling Man: @Muboshgu: How about:
ALT1: that an article published by the The Times-Picayune on former NFL player Jackie Wallace was retweeted 131,000 times, liked 279,000 times, and generated 4,600 comments?
ALT2: that an article published by the The Times-Picayune on former NFL player Jackie Wallace led Sports Illustrated writer Richard Deitsch to declare "BREAKING: Journalism not dead"?
ALT2a: that an article published by the The Times-Picayune on former NFL player Jackie Wallace led Sports Illustrated writer Richard Deitsch to declare that "journalism is not dead"?
Source: [4]
Of course, these hooks are dependent on the information being added to the article, which shouldn't be hard to do. Narutolovehinata5 tccsdnew 23:56, 21 February 2018 (UTC)
@Narutolovehinata5: ALT2a (new) looks good to me, though I'm just the original reviewer, so I'm not sure if I have any say in this anymore... epicgenius (talk) 01:58, 22 February 2018 (UTC)
yes new alt 2a is ok, don’t forget to put Sports Illustrated in italics. The Rambling Man (talk) 06:19, 22 February 2018 (UTC)
ALT2a is the best of these IMO. Gatoclass (talk) 12:15, 22 February 2018 (UTC)
This is weak tea. – Muboshgu (talk) 20:49, 22 February 2018 (UTC)
Oh well, consensus rules, and consensus says we don't main page homelessness in some foul quest for pageviews. What a shame. The Rambling Man (talk) 21:01, 22 February 2018 (UTC)
I'm sorry to see the issue of homelessness is too difficult to address head on. How dare we show reality on the main page. – Muboshgu (talk) 21:03, 22 February 2018 (UTC)
Nice try! Better luck next time, eh? The Rambling Man (talk) 21:09, 22 February 2018 (UTC)
Is there any reason you enjoy gloating over a failure of WP:NOTCENSORED? – Muboshgu (talk) 21:11, 22 February 2018 (UTC)
Try things like "good taste" or "not glorifying the destitute"? I dunno, there are probably a few other reasons. Of course, NOTCENSOR away to your heart's content, but I'm glad to see some COMMONSENSE from our community. Cue violins! The Rambling Man (talk) 21:13, 22 February 2018 (UTC)

Muboshgu, if you're not keen on ALT2a, how about something like:

  • ALT3: ... that Jackie Wallace was cut from the Los Angeles Rams after telling the coach to "kiss his ass" for failing to field him in the 1980 Super Bowl? Gatoclass (talk) 18:18, 23 February 2018 (UTC)
    • I like that better than Alt 2a, but isn't that going to be subject to the same criticism that how dare we suggest putting anything that isn't sunshine and rainbows on the front page? – Muboshgu (talk) 19:06, 23 February 2018 (UTC)
      • Oh dear, time to stop taking your opinion into account with comments like that. I think this is more interesting and less exploitative, so go for it, but link the 1980 Super Bowl properly. The Rambling Man (talk) 19:18, 23 February 2018 (UTC)
        • Does this hook not imply causation? Most readers won't take it to literally say one event happened at a later point than the other. We don't know why the coach cut him; the source also only implies that was the reasoning. Maybe it's okay since the hook says "after" and not "due to", though. Umimmak (talk) 20:48, 23 February 2018 (UTC)
          • Not sure, but I think this hook might be a slight BLP violation due to the emphasis on the "kick his ass" comment. Narutolovehinata5 tccsdnew 22:33, 23 February 2018 (UTC)

To address the issue of "implied causation" raised by Umimmak, I suggest the following change:

Narutolovehinata5, I don't see how "kiss his ass" would constitute a BLP violation. Gatoclass (talk) 07:58, 24 February 2018 (UTC)

Or for a safer but still interesting option:

  • ALT5: ... that Jackie Wallace led the NFL in punt returns and punt return yards in 1978? Gatoclass (talk) 08:17, 24 February 2018 (UTC)

Question about elections rule

Template:Did you know nominations/Armando Ríos Piter is about a candidate for the Mexican general election, 2018 on 1 July. The hook is unrelated to the election, but I was still unsure- can we run the hook now, or do we need to wait until after 1 July? Joseph2302 (talk) 16:24, 16 February 2018 (UTC)

The rule says "featuring election candidates up to 30 days before an election" So, I would say it's OK if it's run before June 1. — Maile (talk) 19:46, 16 February 2018 (UTC)
 Done I put it in Prep 1. Yoninah (talk) 22:49, 19 February 2018 (UTC)

More BLP questions, this time regarding Template:Did you know nominations/Annalisa Crannell

Is a quote from a living person, posted by a Facebook account that belongs to a major international society of mathematicians, an acceptable source for a biography of said living person? Question is about Template:Did you know nominations/Annalisa Crannell. Jo-Jo Eumerus (talk, contributions) 21:06, 18 February 2018 (UTC)

Maybe we could have a reviewer who reads more carefully, or summarizes more accurately? The facebook account in question is used purely as a hosting service (not as a personal facebook page) by a community of professional mathematicians. It does not belong to the International Mathematical Union, the society JJE refers to, nor to the subject. The IMU listed it as one of a small number of high-quality resources about women in mathematics in this listing, and another major resource on women in mathematics included it in this listing. The page in question in this community is an interview with the subject of the article, and the information used from the page is purely drawn from direct quotes from the subject. —David Eppstein (talk) 21:15, 18 February 2018 (UTC)
My reading of the article right now is that it's just fine, and Crannell really does use chopsticks for perspective purposes. It's published in Scientific America and there's even a photo of her doing her "thing". So I think it's okay, good to go, (although I've yet to review the rest of the article); please don't be so aggressive towards those only seeking for accuracy and verifiability on our main page. The Rambling Man (talk) 21:25, 18 February 2018 (UTC)
So, I take that that source https://www.facebook.com/womeninmaths/posts/1590214304524741:0 is fine for the article (not the hook, that has another source)? Jo-Jo Eumerus (talk, contributions) 21:14, 19 February 2018 (UTC)
By posting it by its bare url you are casting it in an unnecessarily negative light. Say, rather, that it is an interview with the subject posted by the Women in Maths community. Facebook is merely their hosting service. —David Eppstein (talk) 21:26, 19 February 2018 (UTC)
This situation seems quite similar to the situation a few weeks ago regarding wordpress, where authoritative texts were being banned simply because of the hosting site.[5] Were it her personal Facebook page, that would be problematic, but from an authoritative source who is simply using a platform as a hosting site, I think we have to use common sense. The Women in Maths community is a reputable source according to information we can glean from other sources about their group, thus, like a blog which belongs to a university, museum, etc. it is acceptable. SusunW (talk) 22:47, 19 February 2018 (UTC)
So it is OK then. Thanks, I'll go pass the DYK. Jo-Jo Eumerus (talk, contributions) 10:09, 20 February 2018 (UTC)

Prep 3 missing one.

Just been looking through the preps and it seems that Prep 3 is missing one hook. Also Prep 1 hasn't been moved the the queue yet. The C of E God Save the Queen! (talk) 10:22, 19 February 2018 (UTC)

Thanks. I left the slot in Prep 3 for another bio, but can't promote one since I worked on them. Yoninah (talk) 11:07, 19 February 2018 (UTC)
Missing hook added by Cwmhiraeth. Alex Shih (talk) 22:26, 19 February 2018 (UTC)

Template:Did you know nominations/Elcor, Minnesota

Can someone archive Template:Did you know nominations/Elcor, Minnesota? The nominator attempted to nominate this article for DYK. Unfortunately, it has already passed FAC and is an upcoming TFA. What I am confused about is why the nominator would want to nominate this for DYK if this is appearing on TFA, which arguably has a much larger daily audience. epicgenius (talk) 19:16, 19 February 2018 (UTC)

Done. Left a note on the nominator's page that the article wasn't eligible for DYK. BlueMoonset (talk) 23:42, 19 February 2018 (UTC)

DYK is almost overdue

In less than two hours Did you know will need to be updated, however the next queue 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:

  1. Check the prep areas; if there are between 6-10 hooks on the page then it is probably good to go. If not move approved hooks from the suggestions page and add them and the credits as required.
  2. Once completed edit queue #6 and replace the page with the entire content from the next update
  3. Add {{DYKbotdo|~~~}} 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, DYKUpdateBot (talk) 22:08, 19 February 2018 (UTC)

Prep 5

  • ... that the Thai Buddhist Dhammakaya Foundation built a large monument that contains a million Buddha images?

@Farang Rak Tham: @Gerda Arendt:

The article, actually titled Wat Phra Dhammakaya, is about a Buddhist temple complex (wat). The piped link in the hook, however, makes it look like this article is about a foundation. Other hooks proposed for the nomination made it clearer that the temple contains a monument with one million Buddha images, and I think one of them should be used instead. Yoninah (talk) 00:22, 20 February 2018 (UTC)
The other hooks all had other problems. "Foundation" came in to avoid having "contains" twice, and the foundation built the complex. Any more elegant solution to avoid saying "* ... that the Thai Buddhist Wat Phra Dhammakaya contains a large monument that contains a million Buddha images?" welcome. --Gerda Arendt (talk) 04:49, 20 February 2018 (UTC)
I think it's fine to say "... contains a large monument with a million Buddha images..." as in Yoninah's reply above. EricEnfermero (Talk) 05:10, 20 February 2018 (UTC)
The repetition of Buddh(a)/(ist) is jarring. Just "that Wat Phra Dhammakaya contains a large monument with a million images of Buddha?" is much more to the point. The Rambling Man (talk) 07:38, 20 February 2018 (UTC)
I appreciate the simplified version (that Wat Phra Dhammakaya contains a large monument with a million images of Buddha?"), but images of Buddha is really quite unusual; Buddha images on the other hand, is common usage. I confirmed this by a scan on this English language corpus, this one and this one. You could use another synonym though: Buddha statues or Buddha sculptures are both found in the corpi, but nothing with of Buddha.
With regard to the terms Dhammakaya Foundation, this foundation is part of the temple, as indicated in the section Wat Phra Dhammakaya#The foundation, but I am okay with both Wat Phra Dhammakaya and Dhammakaya Foundation.--Farang Rak Tham (Talk) 08:23, 20 February 2018 (UTC)
No, "images of Buddha" really is not quite unusual at all. In fact it gets about the same number of Google hits as "Buddha images". The Rambling Man (talk) 09:16, 20 February 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Indeed, Google does give hits for images of Buddha. But on Google Scholar, I found the hits are different in number though:

  1. Images of Buddha gives 1760 hits
  2. Images of the Buddha gives 2340 hits
  3. Buddha images gives 5050 hits.
--Farang Rak Tham (Talk) 10:40, 20 February 2018 (UTC)
On Google Search, the numbers are: for images of Buddha 23.900.000 hits, for images of the Buddha 23.700.000 hits, and for Buddha images 40.900.000 hits. It should also be noted, that images of Buddha can refer to pictures as well, whereas Buddha images is only used for sculptures, as can easily be established from the Google results and the language corpi as linked above.--Farang Rak Tham (Talk) 10:45, 20 February 2018 (UTC)
So, in actuality "images of Buddha" is not unusual at all, and can be used in this context. "Buddha images" is definitely not only used for sculptures, as a straightforward Google will demonstrate. The Rambling Man (talk) 11:10, 20 February 2018 (UTC)
So is everyone agreeable to this:
ALT1: ... that Wat Phra Dhammakaya contains a large monument with a million images of Buddha? Yoninah (talk) 11:58, 20 February 2018 (UTC)
I prefer Buddha images for reasons stated above, as I think hooks should follow the most common usage. But I won't lose sleep over it. I'm glad the hook got through anyhow.--Farang Rak Tham (Talk) 12:16, 20 February 2018 (UTC)
I can't let corpi pass. It's corpora. Corpi is the Queen's dogs or something. EEng 13:16, 20 February 2018 (UTC)
  • @Farang Rak Tham: Please clarify: are they "Buddha images" or "Buddha sculptures"? Or a little of both? Yoninah (talk) 16:06, 20 February 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Yoninah, I would say you could use both words, but here is a close-up, so you can judge for yourself. They are not pictures, no.

...the Queen's dogs, huh? - lol EEng#s
"Corpi is the Queen's dogs or something" is an amazing construction in itself. Applause! The Rambling Man (talk) 22:12, 20 February 2018 (UTC)
I do the best I can with the material available. EEng 23:08, 20 February 2018 (UTC)
Going with "Buddha statues", thanks. Yoninah (talk) 22:39, 20 February 2018 (UTC)

Queue 2 - forcing fumbles

... that Indianapolis Colts defensive back D. J. White forced a fumble every year he played for Georgia Tech? Daniel Case, Church

So I took a quick look at the article, it contained gems like " a month later to force a fumble against North Carolina a month later" which the reviewer must have read, because it turns out the "fact" has to be derived from four sentences in the article, with a knowledge of the nomenclature of the namings of the years, i.e. you have to read "as a true freshman for the Yellow Jackets, played in the last 10 games of the season and forced a fumble in conference play against North Carolina" (what's a "true freshman"?!) together with "A week later, he stopped a 75-yard run by forcing a fumble on a 75-yard run out of the back of the end zone for a touchback against Pitt" (which we have to assume happened the following year, is that his "junior" year? Who's Pitt? Whats a touchback? Why 75-yard run twice?), together with "and also registered one forced fumble", (is that the same forced fumble as before? Is this the same season?) together with "He went on a month later to force a fumble against North Carolina a month later." in his "final" year. This is pretty much inaccessible to anyone outside the in-universe world of collge football, and it'd be much more appropriate to have this factoid (which isn't even interesting because I think it means three in three years, so what?) cited in one place. The Rambling Man (talk) 15:58, 20 February 2018 (UTC)

Struck out link to reviewer, the promoter was Cwmhiraeth, the reviewer was Daniel Case. The Rambling Man (talk) 19:57, 20 February 2018 (UTC)

And the source in the nom claims he made eight force fumbles across his four year time at college. So the hook isn't right either, it should be "one or more forced fumble" or "at least one forced fumble"... Ouch. The Rambling Man (talk) 16:00, 20 February 2018 (UTC)

Not commenting on most of this, but a true freshman is in the context of Redshirt (college sports), it's an American NCAA thing. Pitt is Pittsburg State University, an abbreviation which shouldn't be used in an encyclopedic context. 78.26 (spin me / revolutions) 16:07, 20 February 2018 (UTC)
Okay, thanks for your help with some of the jargon. The primary issues remain unresolved at this time. The Rambling Man (talk) 16:37, 20 February 2018 (UTC)
Minor clarification: Pitt in this case is the University of Pittsburgh, as in the Pittsburgh Panthers.[6] U of P is in NCAA Division I, while PSU is in NCAA Division II. I know that doesn't fix the problems, but it helps accuracy. – Muboshgu (talk) 16:46, 20 February 2018 (UTC)

Well, since I was not consulted by TRM before he posted this rant casting aspersions on my reviewing abilities, and he does not seem to have found it worth his time to look at the nomination, I will point out that a) I raised exactly this issue there, as anyone can see, and b) as you can further see, it was resolved when I read further beyond the "college career" section and found it stated under "professional career" and sourced to his NFL draft scouting report, published on nfl.com.

If you're going to make sport of someone else's reviewing, at least take the time to do something more than a superficial review yourself. Daniel Case (talk) 17:15, 20 February 2018 (UTC)

Addendum: The cited source says "Forced a fumble all four years at Ga Tech. " Daniel Case (talk) 17:17, 20 February 2018 (UTC)
By the way, this is the place to discuss nominations, I don't need to "consult" anyone before coming here. The article is littered with inaccessible jargon including the "He went on a month later to force a fumble against North Carolina a month later", is that acceptable? Did you review that line of prose and think it was ok? And all that notwithstanding, he didn't force a fumble every year, he appeared to force at least one fumble every year. The review I made was superficial based on the fact I'm reviewing dozens such articles per day, and in a superficial review I found numerous issues. What more would like, a detailed review? The Rambling Man (talk) 17:59, 20 February 2018 (UTC)
Addendum: the article says " impressed that he had forced a fumble every year he was at Georgia Tech.[7]", there is not one element of "impressed" in the source, merely a statement of fact: "Forced a fumble all four years at Ga Tech". Not "Impressed that he forced a fumble all four years at Ga Tech". So the sentence relating to the hook is actually incorrect as well. The Rambling Man (talk) 18:05, 20 February 2018 (UTC)
@The Rambling Man: OK, you can take "impressed" out of the article; I think it's sort of implicit that if a draft scout takes note of that in his report on a player that he was impressed by the fact but I'll agree that if we are strict about this, we won't say it ourselves.

Had the fact been stated in the "college career" section (where tbh it should have been because I will admit there is the contradiction you noted), I might have removed the redundant adverbial phrase. But I generally don't get heavily involved in copyediting DYK noms I review because I don't think there's much of it you can do before you're effectively a contributor to the article yourself and shouldn't be reviewing it. Besides, the whole point of linking it from the Main Page is to expose it to the opportunity for others to improve it; I generally defer to those other editors.

"I don't need to 'consult' anyone before coming here." No, you don't. But I generally don't start discussions like this on project talk pages without going to the common courtesy of letting the editors whose work you will be discussing know that their work will be a topic of discussion. It's part of assuming good faith. Daniel Case (talk) 21:28, 20 February 2018 (UTC)

Hopefully you can get over it. I used the conventional method (a ping) to alert you. AGF has nothing to do with this, and to attempt to claim that I didn't AGF (or even imply it) is contrary to your "position" on Wikipedia. Don't do it again. Generally (and I mean 100% of the time) hooks that are in queues which are subject to debate get discussed here. If you're unaware of that or uncomfortable with it, then I guess I'm sorry, you need to be prepared to have your reviews scrutinised, and in this case it's evident that there were problems that needed to be fixed. That you reacted in such a vitriolic fashion is a shame; meanwhile Church worked hard on fixing up the issues. An interesting difference in approaches which has not gone unnoticed. The Rambling Man (talk) 21:57, 20 February 2018 (UTC)
@The Rambling Man: "Hopefully you can get over it." I should have expected no less, but I made the request anyway. I consider that method of pinging someone, when you are being critical of their work, little better than the equally deplorable practice of subtweeting. It's acceptable if you don't necessarily expect the other person to respond, an absurd expectation when you have suggested the person thus pinged was less than adequately diligent in reviewing a DYK nom (and even more so when your critique seemed itself to be based on an insufficient review).

As for Church, I would first note that he himself asked you to "keep your tone uncombative". And secondly, by the time I was able to see what all the commotion was about, Church had already done a great deal of work on the article (something that was really more his task anyway as he had developed the article), so to imply that I was neglecting that is disingenuous.

I wasn't asking that you discuss the hook on my talk page, just that I get a more formal notification about it there to come to this discussion here. I don't know how you could have misread what I wrote to imply that, save willfully.

Look, TRM, you undeniably do a lot of good work on DYK; I appreciate very much the copyediting you've done on articles I've developed between DYK approval and the Main Page, and I have thanked you more than once for this. In this case six words—"I'm sorry you feel that way"—would have mooted this whole rather-beside-the-point aspect of this discussion. I certainly don't mind have my work scrutinized; I do mind the person doing it making it seem like they're holding it up as an object of ridicule. Daniel Case (talk) 16:28, 22 February 2018 (UTC)

Church had overlooked your instant hostility, for which he apologised. Any implication or so-called "ridicule" you may have felt from a simple ping to let you know the topic was being discussed is entirely down to you. Once Church had joined in, the discussion proceeded productively to a good end result. Once again, the difference in approaches has not gone unnoticed. The Rambling Man (talk) 16:37, 22 February 2018 (UTC)
A heads up, Im at work right now so I won't have time to respond in depth for a bit. TRM if you want to pull this to allow issues to be addressed then I am not opposed. I just ask that you keep your tone uncombative. Regards--Church Talk 18:22, 20 February 2018 (UTC)
It works both ways, I don't appreciate the tone here: he posted this rant casting aspersions on my reviewing abilities so please refer to everyone when you make such a request. The Rambling Man (talk) 19:13, 20 February 2018 (UTC)
You're right, and I offer my apologies. Let's all remember that we all want what is best for the encyclopedia here and I can certainly admit that this particular article is not my best work. Just so I can make sure I understand your viewpoint The Rambling Man, You are concerned about the hook being incorrect based on the conflicting sources correct? In addition, you are also concerned that the article contains to much "insider" knowledge that wouldn't be known to people who don't follow the sport? --Church Talk 19:25, 20 February 2018 (UTC)
Firstly I'd like to know if forcing a fumble is really that significant, so doing it at least once a year for four years, is that really of note? Secondly, yes the hook implies that it was "one" forced fumble a year, whereas the slightly more detailed source shows at least eight forced fumbles during the four years. Thirdly (and not directly related to DYK) yes, I found the jargon too hard to follow. I corrected one blatant issue with the English but there were other issues (I noted a couple of them in my initial post) that I simply didn't understand. I haven't had time to look at the article in detail, I was just reading through the sections to see where the hook was verified and found conflicting and inaccurate information, as noted above. P.S. I can't pull it, it's now protected, so if you need more time then we'll need an admin to do that. The Rambling Man (talk) 19:30, 20 February 2018 (UTC)
You've got a bit of time before this appears on the main page, but ping me if you still want this pulled. 78.26 (spin me / revolutions) 19:56, 20 February 2018 (UTC)
The Rambling Man Admittedly, forcing a fumble isn't the greatest thing that can happen in college football. However, forcing a fumble is impressive enough as a corner as that it does not happen that often. (Most corners) are known for their coverage ability and not so much for the ability to jar the ball lose. In terms of the source conflict, I'm not sure who exactly would be more reliable but I am perfectly fine with changing the hook to "one or more fumbles" just to cover our bases. I'll go through and see if I can at least elaborate and clarify some of them. I believe it's just simply a case of something that is almost second nature to me (as a former player, albeit not at a collegiate level), getting too technical. Thank you for taking the time you have already. --Church Talk 19:43, 20 February 2018 (UTC)
No worries. As I said, the jargon issue isn't directly part of DYK's purview but when I ever review DYKs I do it from the "whole hog" perspective, not just the checklist, so when looking at this one, I found myself thinking "Whaaaa?" too many times. And I do understand a little about American Football having been forced to watch Superbowl a few times and the much maligned World League of American Football (go London Monarchs...!) so yes, it's altogether possible that it's way beyond the average (non-college football) reader. Most importantly is getting the hook and the article to match, and getting the hook and article correct and correctly sourced. The Rambling Man (talk) 19:48, 20 February 2018 (UTC)
Just pointing out that I did not review this article, as TRM has falsely claimed, I promoted it to Prep. I investigated what a "fumble" was, and I checked that D.J.White had forced a fumble in each of his years at Georgia Tech. Cwmhiraeth (talk) 19:50, 20 February 2018 (UTC)
Just pointing out that he forced more than one fumble in at least two years, and therefore the hook was wrong. And the sentence with the citation said the author of the source was "impressed" and that was not in the source, so therefore the article was wrong. At the time of review and promotion. The Rambling Man (talk) 19:54, 20 February 2018 (UTC)
So how do we need to correct this? Just elaborate the hook for "one or more?" Regards--Church Talk 19:57, 20 February 2018 (UTC)
Well "at least one" would work perhaps, and the article needs to remove the "impressed" claim. Then we're just left with the "is it a big deal" issue, and the jargon. The Rambling Man (talk) 19:58, 20 February 2018 (UTC)
I have remove impressed and am in the process of proofreading and elaborating the article as much as I can here on my lunch break. If an admin could please change the hook, I'd appreciate it. --Church Talk 20:03, 20 February 2018 (UTC)
I gave the entire section a good copyedit, unfortunately I'm out of time on my lunch break. Hopefully I was able to fix the concerns regarding the article.--Church Talk 20:12, 20 February 2018 (UTC)
You're still relying on the source that says he made "a forced fumble" every season, whereas the other source clearly notes he made more than one in more than one season. The Rambling Man (talk) 20:24, 20 February 2018 (UTC)
Perhaps I'm not following. Where is that being relied on? In the draft section that is mainly the opinion of a draft scout. --Church Talk 20:38, 20 February 2018 (UTC)
I think what I'm trying to say is that he made more than one forced fumble at least twice in a season at Ga, so you should probably reflect that rather than just rely on the simplified source which says (incorrectly) that he "Forced a fumble all four years at Ga Tech" where it should really be "Forced at least one fumble all four years at Ga Tech". The Rambling Man (talk) 20:49, 20 February 2018 (UTC)
I think I corrected what you meant. Cheers. --Church Talk 21:15, 20 February 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── 78.26 Could you please change the hook per the above discussion?--Church Talk 21:16, 20 February 2018 (UTC)

On it. 78.26 (spin me / revolutions) 21:22, 20 February 2018 (UTC)
I have modified the hook. @Church: @The Rambling Man:, does it meet with each of your approvals? 78.26 (spin me / revolutions) 21:35, 20 February 2018 (UTC)
Good with me 78.26 Thanks!--Church Talk 21:49, 20 February 2018 (UTC)
78.26 maybe I haven't cleared my cache, but I'm seeing "... forced least one fumble fumble ..." which should be "... forced at least one fumble ..." (add at, remove one fumble). The Rambling Man (talk) 21:59, 20 February 2018 (UTC)
The Rambling Man nope, not your cache, that's all me. Fixed, and thank you! 78.26 (spin me / revolutions) 22:09, 20 February 2018 (UTC)
No wuckers. The Rambling Man (talk) 22:11, 20 February 2018 (UTC)
The Rambling Man- Is there any other issues you'd like me to attempt to address? --Church Talk 22:44, 20 February 2018 (UTC)
I think we're all good. Thanks to you, Church, and User:78.26 for your help in fixing up the issues raised. Good job. The Rambling Man (talk) 22:50, 20 February 2018 (UTC)

Queue 2 - Howard Marks' autobiography

... that Howard Marks concluded a drug deal at the Warwick Castle in Maida Vale, London, with half a consignment of Thai grass hidden in a car parked outside? Edwardx, Widefox, Philafrenzy, Ritchie333

This is an interesting hook, although "half a consignment" isn't a "traditional" method of measurement, according to the source it was half of a 2000kg consignment, so maybe one ton would be more to the point (and actually, much more interesting). Then, thinking about it, 1000kg in a "car"? Really? The sourcing for this claim is from Marks' self-penned autobiography, so for us to stay safe, I would advocate "claimed to conclude" rather than "concluded", and would replace "half a consignment" with "a ton". The Rambling Man (talk) 16:21, 20 February 2018 (UTC)

I will leave the quantities to others, but I assume you know Marks is dead? Philafrenzy (talk) 16:26, 20 February 2018 (UTC)
What exactly does that have to do with the veracity of the claim? I'm not suggesting BLP here, I'm suggesting his own stories in his own words ought not be considered as fact. The Rambling Man (talk) 16:28, 20 February 2018 (UTC)
And please consider the logic, I've got a Mondeo and it can carry around 350kg, the estate version around 500kg. What kind of car can carry a load of one ton? The Rambling Man (talk) 16:31, 20 February 2018 (UTC)
Just checking what your concerns are. Philafrenzy (talk) 16:32, 20 February 2018 (UTC)
Sorry, you're just checking, or you going to check to see if you can address the issues? If anyone knows of a "car" in which you could "hide" a ton of anything, could you let me know please? The Rambling Man (talk) 19:26, 20 February 2018 (UTC)
Wait... a Mondeo?!? I thought you would get a brand new Tesla for the Falcon Heavy hook... Or has it just not arrived yet? lol 91.49.68.207 (talk) 19:29, 20 February 2018 (UTC)
It's "in the post" according to Elon. But I think he meant the post on Mars... The Rambling Man (talk) 19:31, 20 February 2018 (UTC)
And you wouldn't get a ton of grass in a Tesla, not a chance... The Rambling Man (talk) 21:12, 20 February 2018 (UTC)
Of course, the volume alone would make it impossible, or at least very improbable. But i doubt they cared much about the manufacturer recommended cargo capacity. Hardly impossible to overpack a car massively. Just that the frame may bend and so on. Something drug dealers, dealing in tons, probably would not care about. But that is obviously conjecture and not really important. On a side note, if you took the batteries out of a Tesla, it would perhaps be possible to load that sort of weight without damaging the frame... But obviously it is not very useful like that anymore, hahaha. 91.49.66.66 (talk) 07:19, 21 February 2018 (UTC)
  • Comment this is still very much outstanding and needs some new eyes as Philafrenzy has declined to comment on the substance of the issue. The Rambling Man (talk) 21:11, 20 February 2018 (UTC)
I've pulled the hook and put it back into review. I personally thought "consignment" was some abstract quality, that was not specifically related to the 2,000kg mentioned further up, that sounds like something else. Not being part of an organised drug-dealing racket, I'm a bit naive about these things. Ritchie333 (talk) (cont) 22:55, 20 February 2018 (UTC)
Ritchie333 I could be wrong, I read the source given and it seemed to state that the consignment was 2000kg, and that Marks claimed to bring "half" of it to the pub in his car. I'm just trying to apply a little reality to the situation... The Rambling Man (talk) 22:57, 20 February 2018 (UTC)
I'm more considering the actual logistics. A ton of dope, especially grass (lightweight) would be physically huge, you'd never conceivably get it in a car, or even a van. Look at this, where a ton of dope even packed in tubes had to be transported in a giant tractor-trailer. Black Kite (talk) 23:00, 20 February 2018 (UTC)

Possible image copyright issue

I Saw the Figure 5 in Gold

The image used in Queue 1 includes a US postage stamp. According to Commons:Stamps/Public domain#United States, these are "Copyrighted by the United States Postal Service after 1 January 1978 .... Written permission is needed". I believe this applies even though the painting depicted on the stamp is public domain. I suggest replacing it with the image of the painting, which I think is a much better picture anyways. The (pictured) and caption should, of course, be adjusted accordingly.

Also, according to MOS:US, "U.S." should be replaced with "US".

This will hit the Main Page in about four hours. MANdARAX  XAЯAbИAM 20:06, 20 February 2018 (UTC)

I concur. You can list this at WP:ERRORS for a faster and more objective response, by the way. The Rambling Man (talk) 20:09, 20 February 2018 (UTC)
I'm not so good on copyright, and my instinct says this is probably OK, but to be on the safe side, I'll swap it out for File:Susanna Innes-Ker, Duchess of Roxburghe.jpg. --Jayron32 20:15, 20 February 2018 (UTC)
@Jayron32: As the person who submitted the DYK, I would have preferred that it be removed from the Queue and held over either until the stamp copyright issue was resolved or a decision made to use the image of the painting rather than the DYK be used without an image. I feel robbed. David notMD (talk) 01:38, 21 February 2018 (UTC)
It was never my intention for this to be bumped from the image slot. Quite the contrary. The iconic painting should have been featured. Beyond the importance of the painting, it's very desirable to have a wide variety of DYK images, and this is certainly unlike the usual things pictured. MANdARAX  XAЯAbИAM 07:12, 21 February 2018 (UTC)
You had written as much when you started this discussion, and I appreciate your comment after the fact. I would still like to see a response from Jayron32, who apparently could not imagine my dismay at my lost image from my first attempt at a pictured DYK. David notMD (talk) 09:22, 21 February 2018 (UTC)

If there wasn't such a mind-numblingly inane obsession over pageviews, we could switch the hooks round right now, along with the images, to get at least half a day on the main page for this candidate. Jayron32 could consider doing that rather than just simply saying "OK" to your note. The Rambling Man (talk) 12:14, 21 February 2018 (UTC)

I've transcluded the image at WP:CMP. We can make the switch as soon as the bot protects it at commons. Vanamonde (talk) 12:26, 21 February 2018 (UTC)
I am perfectly happy with the half-day (and not obsessed about page views). Thanks to all who contributed to the salvage. David notMD (talk) 13:14, 21 February 2018 (UTC)
Thank you Vanamonde93 for working that out. That seems like a really good idea. --Jayron32 13:20, 21 February 2018 (UTC)
You're welcome. The Rambling Man (talk) 13:41, 21 February 2018 (UTC)

And, even though I am not obsessed with page views (really), it was nice to see that this one, even with the image included less than 12 hours, got close to 10,000 views. David notMD (talk) 10:44, 23 February 2018 (UTC)

Oldest nominations needing DYK reviewers

The previous list was archived a day ago, with very few entries crossed off on it. Here is an updated list with 36 older nominations (through February 11) that need reviewing . Right now we have a total of 202 nominations, of which 89 have been approved. Thanks to everyone who reviews these, especially the one from last year that continues to elude reviewers well into this year.

Over two months old:

Over one month old:

Other old nominations:

Please remember to cross off entries as you finish reviewing them (unless you're asking for further review), even if the review was not an approval. Many thanks! BlueMoonset (talk) 04:38, 21 February 2018 (UTC)

Robin Surgeoner

Ahh DYK, it's been a while. Before I submit Robin Surgeoner could someone tell me if it's acceptable to have missing medal information? Sources support his nine golds but recordkeeping in old Paralympic games was poor and data for one of his golds is missing. I think it might meet the DYK criteria other than that. violet/riga [talk] 16:41, 21 February 2018 (UTC)

It looks OK to me, I suggest you go ahead and nominate it. Cwmhiraeth (talk) 06:16, 22 February 2018 (UTC)

February Black History Month

There's still an open prep set (Prep 2) for the last day of the month, February 28, if anyone has any more articles to nominate. I just approved two more Black History Month hooks and moved them to the Special Occasions holding area for this month. Yoninah (talk) 21:22, 21 February 2018 (UTC)

Symbol redirect vote 4.svg New reviewer needed ASAP to approve Template:Did you know nominations/And the Walls Came Tumbling Down. Yoninah (talk) 10:56, 22 February 2018 (UTC)

Nov20

There are no DYK noms for Nov20, but it is still listed on the "Count of DYK Hooks." I've deleted the header on the nom page and purged the cache, but that didn't resolve it. Help? ―Biochemistry🙴 04:00, 22 February 2018 (UTC)

Takes a while for the bot to update that stuff. Wait 24 hours. Looks like it's updated every 30 minutes. EEng 04:25, 22 February 2018 (UTC)
@EEng: Thanks! ―Biochemistry🙴 01:11, 23 February 2018 (UTC)

DYK Process issues straw poll

The previous discussion about process issues was archived, largely, it would appear, because, disappointingly, nobody seemed interested in seriously discussing the many proposals presented therein. The discussion was also complicated by a lack of clarity on what exactly we were trying to address.

So, let's try this again, with a little more structure. This is restricted to proposals trying to address a single issue; errors in the hooks reaching queues or the main page.

This is a straw poll, so the results are non-binding, and the proposals are intentionally general, so we know which ideas to pursue further, and where to spend effort hashing out tricky details. I've taken these proposals from the previous discussion, and tried to simplify them to their basic ideas. Feel free to add additional proposals. Vanamonde (talk) 07:51, 22 February 2018 (UTC)

Survey

Penalize incomplete inadequate reviews

Should we disallow QPQ credit for reviews later found to have missed a basic issue with the article/hook? (By "basic criteria" I mean whether the article is compliant with core policies, whether the hook is in the article, and whether it is cited there.)

  • Yes. This seems to me to be fairly basic, and enforceable. If you didn't do a review properly, you don't get to count it as a review. Vanamonde (talk) 09:28, 22 February 2018 (UTC)
  • YES if they haven't checked this properly, it's not a proper QPQ review. Joseph2302 (talk) 10:09, 22 February 2018 (UTC)
  • I don't think this question is sufficiently clear, but I do think a QPQ credit should not be given where the reviewer has approved a hook that contains a clear factual error, or where the hook statement is unsourced or improperly sourced in the article. I do think there are more considerations to this question however, rather than simply having a black-and-white "yes" or "no" option. Gatoclass (talk) 11:38, 22 February 2018 (UTC)
  • Perhaps, but WP:AGF. All the best: Rich Farmbrough, 13:45, 23 February 2018 (UTC).

More reviews from experienced reviewers

Based on EEng's suggestion; should experienced reviewers/nominators be required to perform more than 1 QPQ after a certain point?

  • No. We've had this discussion a couple of times previously, my view now as it was then is that forcing experienced reviewers to do an additional QPQ review for every nomination they make will do absolutely nothing to improve the quality of reviewing which is the principal goal - in fact, it is likely to have the opposite effect of leading to even more sloppy reviewing. Gatoclass (talk) 11:45, 22 February 2018 (UTC)
Completely illogical. It stands to reason that experienced reviewers will do at least a somewhat better job than less experienced ones. Someone has to do extra reviews [added later:] needed to address the constant backlog that is the inevitable result of giving the first five noms for free, and it might as well be people who have done 10+ themselves. EEng 06:17, 23 February 2018 (UTC)
The backlog is due to the total number of nominations and has nothing to do with the number of approved nominations. Gatoclass (talk) 08:06, 23 February 2018 (UTC)
There are two backlogs. One is the, since each editor's first five noms don't require that editor to do a review, there's a permanent pool of noms languishing unreviewed. The other is that, depending on the burn rate, there are sometimes a lot of approved noms waiting to be run. I'm talking about the first one. EEng 15:20, 23 February 2018 (UTC)
The "permanent pool of noms languishing unreviewed" is immaterial. It would only be of concern if we lacked a sufficient pool of approved nominations, and I can't even remember the last time that happened. Right now, for example, we have 105 approved nominations on the nominations page, and another 40 loaded into prep. Given that we only feature 8 per day, that's more than 2 1/2 weeks' supply. Gatoclass (talk) 16:01, 23 February 2018 (UTC)
Your memory is short. Right now there are about 50 noms that haven't been touched -- no reviewer has volunteered -- since they were created. Every new nom with a QPQ adds one to that list, and subtracts one from that list, so the number remains constant -- except when a "no-QPQ-required" new editor drifts in and starts making their "first-5-free" noms, which increments the size of this permanent unreviewed pool to 51, then 52, and it goes up and up until (independently) DYK has one of its periodic crises of running out of approved noms and there are emergency pleas for quick reviews, and this backlog is driven back down. It makes no sense. Reviews should be begin reasonably promptly as a matter of course, and a sensible way to do that is to have nominators with 10+ credits do two reviews for each new nom if there's a backlog of noms awaiting review (which will be only some fraction of the time). But I tire of speaking sense to a crowd that denies there are problems in the first place. EEng 04:54, 24 February 2018 (UTC)
Well maybe it is, because I can't remember the last time we had a "reviewing drive" to increase the number of reviews. If they are still occurring, they must be a pretty rare event, and if so, can be readily managed by a few volunteers putting up their hands to help. Gatoclass (talk) 06:51, 24 February 2018 (UTC)
... on an emergency basis so errors go up. My proposal is simply that experienced reviewers do these needed extra reviews on a routine basis when there's a backlog instead of having to call all hands on deck. It's amazing the resistance to even minor, logical, incremental adjustments to procedure, apparently just for the sake of never changing anything. Please, now you contribute one last non sequitur objection. I'll check back in another year or two when the community's completely had it with the DYK mess and its intransigence to any change at all. EEng 07:24, 24 February 2018 (UTC)
Not at all. When volunteers take over reviewing, quality if anything probably goes up - not that we often need to do this anyway. Gatoclass (talk) 11:26, 24 February 2018 (UTC)
More fuzzy thinking. We're talking about the same people: your "volunteers" -- those who hang around on this page -- are the selfsame experienced nominators who under this proposal would be required to do 2 QPQs for each nom (only when there's more than a handful of unreviewed noms waiting -- when there's not, then it's 1-for-1 like usual). Just under this proposal, it happens normally and naturally and promptly, instead of waiting until the system is clogged up. EEng 13:50, 24 February 2018 (UTC)
  • No I don't think we have enough articles for this to be workable. However, we do need more reviews than are catered for by QPQ. Each editor's first five noms is one reason; but other, which is more significant, is articles requiring second reviews. A possible solution is to require an extra QPQ in this case. Hawkeye7 (discuss) 20:01, 23 February 2018 (UTC)
There's no such thing as "not enough articles" (by which I guess you mean nominations). This would be a requirement only to the extent there's a backlog of nominations needing review. When there isn't, then only one QPQ is required per nom by an experienced nominator. As soon as the backlog grows a bit again, then the next few noms by experienced reviewers require two QPQs again, until the backlog's gone again. Repeat. It's simple and effective, and puts the burden of extra reviews on those best able to handle it -- experienced nominators/reviewers. EEng 07:24, 24 February 2018 (UTC)
  • Yes, albeit reluctantly. A DYK isn't that onerous when you get down to it, and I'd be quite happy to do more than one per DYK (and indeed have done). I'm reluctant only because I suspect that a) folks who nominate frequently aren't going to like this, and b) any form of this as a rule, combined with the suggestion above, is going to be rather bureaucratic; and if we've to choose between the two, I'd much rather just disallow poor reviews. Vanamonde (talk) 08:32, 24 February 2018 (UTC)
Vanamonde, firstly, the fact that you might be happy to do extra QPQ reviews doesn't mean that everybody would be happy to do so, and forcing that on people who are already reluctant to review is only likely to result in a decline in reviewing standards. Secondly, if you would "much rather disallow poor reviews" why didn't you include that as an option in the poll? It makes no sense at all to be !voting for your second preference because you didn't include your first. Gatoclass (talk) 14:49, 24 February 2018 (UTC)
@Gatoclass: Re: extra burden: fair point, and hence my reluctance, but at the moment I'm still thinking that a reviewer's reluctance will be more than balanced out by experience (I'm assuming we mean substantially experienced, not just a 5-DYK editor). Re: poor reviews; that's the point of the first question above, though...I admit "incomplete" may have been unclear, but folks voting have clearly understood the thrust of the proposal. Vanamonde (talk) 14:54, 24 February 2018 (UTC)
Vanamonde - sorry, my mistake, that option has attracted so little interest, I guess I completely forgot it was there. I'm also having trouble with Firefox which is slowing down over time to unusable levels since their "speed update", I just restarted again to try and restore some speed. With regard to your comments about double reviews, I might have something to say about it later, but right now I'm taking a break as I'm tired of fighting my browser. Gatoclass (talk) 15:04, 24 February 2018 (UTC)
@Gatoclass: No worries. I'm baffled about the lack of attention too; it seems the most obvious fix, particularly given the frequent complaints about reviews; but let's deal with that later. Try Chrome; I switched away from Firefox following very similar trouble. Vanamonde (talk) 15:31, 24 February 2018 (UTC)
  • Yes as a simple and appropriate way to clear the backlog of noms waiting for reviews, and makes an appropriate symmetry to the no-review requirement for new nominators. EEng 13:39, 24 February 2018 (UTC)

Quick fails for experienced nominators

If a nomination from an experienced DYK contributor fails basic requirements (whether the article is compliant with core policies, whether the hook is in the article, and whether it is cited there), should it be failed immediately, rather than dragged out until it passes? Alternatively, should it be failed after two reviews (to prevent abuse by a single reviewer with a grudge?)

  • Yes. Experienced nominators should know better than to submit articles with core policy issues. If there's any hesitation about this because of the possibility of the first reviewer abusing their position, I'm okay with allowing for a second opinion. Also, to be clear, I have no issues with discussions about finding the best possible hook; I see this as being distinct from, say, a hook that is unreferenced in the article. Vanamonde (talk) 10:12, 22 February 2018 (UTC)
  • No, this is too harsh. I recently nominated a multi-article hook where all the articles were new except for one. By the time I nominated it, I had forgotten that one article was an expansion, and this particular article was a few hundred characters short. When this was pointed out I expanded it further. It would be unfair to disallow this nomination. Cwmhiraeth (talk) 10:50, 22 February 2018 (UTC)
  • No, because per Cwmhiraeth, it's easy for even the most experienced nominators to miss some minor issue in putting together a nomination. Quick failing for some criteria might be justified, but again, that would require a more detailed discussion. Gatoclass (talk) 11:51, 22 February 2018 (UTC)
  • @Cwmhiraeth and Gatoclass: I've modified this proposal to clarify what I mean by "basic requirements". Vanamonde (talk) 15:53, 22 February 2018 (UTC)
Quite honestly, I'm not sure I'd support quick fail of nominations for anything, because anybody can make a mistake when putting together a nomination. Are there, perhaps, examples you have in mind Vanamonde, of nominations that should have been quick failed? Also, I'm not sure what you mean by core policies, if you mean things like BLP or NPOV, they are often judgement calls rather than black-and-white issues and I would think that quick failing on those grounds could lead to controversy. Gatoclass (talk) 17:05, 22 February 2018 (UTC)

GAs only

Should DYK nominations be restricted to articles that have passed GAN?

  • Oppose Certainly not. I thought a proposal like this might eventually come up the moment they allowed GAs in. GAs make up a very small percentage of the nominations that come through and indeed there is no guarantee that their proposed hooks meet the criteria as GAs can still have sourcing issues or have incorrect facts buried within walls of text. Besides, this is not what DYK is all about. It's about getting new material an audience where it can be further improved with others. The C of E God Save the Queen! (talk) 08:38, 22 February 2018 (UTC)
    Then it should be renamed to reflect its true purpose. Something like Crocks in need of help perhaps? Eric Corbett 09:10, 22 February 2018 (UTC)
  • Definitely not, for several reasons. I see DYK as a way of showcasing interesting facts from a variety of topics. Most topics on Wikipedia, including those that I do most of my work on, cannot be brought to GA-level anytime soon, simply because of a lack of coverage in accessible English sources. Indeed much of the work I see here tends to be near as complete as it can be, and I see no reason to exclude it. Furthermore, the GA process has just as many flaws as the DYK process, if not more. It just receives less scrutiny because it's not putting items on the main page. GANs are dependent on a single reviewer, and the status of the article is rarely questioned even when the review hasn't covered certain criteria. Finally, there's only a handful of GAs passed every day; we'd have to reduce our throughput by an order of magnitude even if every GA were nominated, which it won't be. Vanamonde (talk) 09:19, 22 February 2018 (UTC)
  • Most topics ... cannot be brought to GA-level anytime soon -- Most of our 6 millions articles can't be 5X expanded either, or be brand new, and so will never qualify under the current rules. The rules have always been arranged to make sure almost no articles qualify, 'cause otherwise we'd be overwhelmed. It's just arbitrary.
  • I see DYK as a way of showcasing interesting facts from a variety of topics -- GAs have plenty of interesting facts.
  • the GA process has just as many flaws as the DYK process -- Under current rules, a GA has to also pass DYK's check. We could keep it that way.
EEng 06:13, 23 February 2018 (UTC)
  • Strongly oppose DYK is for new articles, that's its purpose. I'm not even sure why GA are allowed on DYK, and turning it into just GAs would be crazy, and you wouldn't get enough hooks anyway. Joseph2302 (talk) 10:11, 22 February 2018 (UTC)
  • DYK is for new articles, that's its purpose -- Circular reasoning: you're just saying that DYK should be for new articles (i.e. not just GAs) because DYK is for new articles. Why should new articles be DYK's purpose?
  • you wouldn't get enough hooks -- Enough for what? What would be wrong with running 5 non-embarrassing articles each day, instead of 16 skeletons with frequent errors?
EEng 06:13, 23 February 2018 (UTC)
  • No, definitely not. The main point of DYK is to encourage article creation and expansion. Cwmhiraeth (talk) 10:53, 22 February 2018 (UTC)
Again, that's just circular reasoning: DYK is about article creation and expansion because DYK is about article creation and expansion. Why? Why can't it be about bringing articles to a reasonably complete state and so on i.e. GA? EEng 06:13, 23 February 2018 (UTC)
  • No, not the idea of the section. Perhaps mark Good articles as such on the Main page (by the green symbol), to tell readers in advance what to expect? --Gerda Arendt (talk) 11:00, 22 February 2018 (UTC)
not the idea of the section -- more circular reasoning. EEng 06:13, 23 February 2018 (UTC)
  • No, I've only recently been doing DYKs, and that for articles I improved to GA, but I see the 5X criteria as much more central to how DYK is an incentive to improving Wikipedia. If any change in criteria, perhaps increasing minimum length, so that DYK obsessed editors are less inclined to create short articles. Speaking of which, could the minimum length requirement be automated, so that when a DYK is submitted the submitter would get an immediate prompt if too short? David notMD (talk) 11:08, 22 February 2018 (UTC)
Increasing the minimum length is a great idea. EEng 06:13, 23 February 2018 (UTC)
  • No, DYK is supposed to be primarily about new content, not old articles somebody has given a few tweaks to. Confining DYKs to GAs would mean less diversity of topics as GAs tend to be top-heavy in certain topics, and it would also in all likelihood mean a lot fewer nominations being featured as fewer GAs get passed on a daily basis. Restricting DYKs to GAs could also cause a sharp decline in the (already questionable) standard of GAs as you could just end up with DYKers rubber-stamping each other's GA nominations in order to get them featured at DYK. There are just so many things wrong with this idea, these are just the first few that come to mind. Gatoclass (talk) 12:02, 22 February 2018 (UTC)
  • DYK is supposed to be primarily about new content -- circular reasoning again: it's supposed to be about new content because it's supposed to be about new content, QED.
  • you could just end up with DYKers rubber-stamping each other's GA nominations -- Because that sure doesn't happen now.
EEng 06:13, 23 February 2018 (UTC)
EEng, you don't have to keep repeating yourself. It's about new content to encourage people to continue to create new content and as a reward for doing so, as well as reminding readers that Wikipedia is a dynamic and ever-growing body of knowledge, amongst other things. And I think it highly unlikely that DYK contributors are rubber-stamping each other's GAs now, because they don't need to take an article to GAN to get it featured in the DYK slot, but that would obviously change if they did have to do so. Gatoclass (talk) 15:34, 23 February 2018 (UTC)
  • you don't have to keep repeating yourself -- I appreciate your cutting me this slack, but as long as people keep repeating the same circular arguments ("DYK is supposed to be this way because that's the way DYK is") I'll go the extra mile by pointing out that that's what they're doing.
  • And I think it highly unlikely that DYK contributors are rubber-stamping each other's GAs ... but that would obviously change if they did have to do so -- so you agree the DYK process has a tendency to be a rubber stamp?
EEng 05:00, 24 February 2018 (UTC)
As I said in an earlier thread, I think most reviewers try to do their jobs conscientiously, but a few may not, or may simply not be aware of the kinds of issues they need to be on the lookout for. And as I've said on numerous previous occasions, I strongly support the idea of greater accountability of reviewers to address the problems we encounter, particularly with regard to hook accuracy. But I do think that if there's a tendency for some people to review sloppily, that tendency could only be exacerbated by expecting them to do even more work to earn a QPQ. Accountability is the solution IMO, not piling more work on the shoulders of those who are already struggling to meet existing requirements. Gatoclass (talk) 07:03, 24 February 2018 (UTC)
Higher standards are a bad idea because it would be too hard for some people. Great reasoning! Maybe some people shouldn't have an expectation of having their can't-meet-moderate-standards content featured on the main page. EEng 07:30, 24 February 2018 (UTC)
Straw man much? What I said is that higher standards My point is that "higher standards", as you put it, would be best achieved by greater accountability, not by simply piling extra requirements on those already struggling to meet the existing requirements and expecting them to somehow do better. Gatoclass (talk) 09:31, 24 February 2018 (UTC)
Misquoting yourself, much? You said nothing about higher standards. EEng 13:51, 24 February 2018 (UTC)
This is getting ridiculous. What do you think I was referring to when I said we need greater accountability to address the problems we encounter, particularly with regard to hook accuracy if not higher standards? When people start playing semantics it's generally a good indicator that they have run out of valid arguments. Gatoclass (talk) 14:21, 24 February 2018 (UTC)
That's not higher standards, that's struggling to meet even the standards we already have, because we continue the mythology that short, brand new articles can be featured on main page without frequent embarrassment. When someone keeps saying one thing and then later saying they meant something else, it's generally a good indicator of fuzzy thinking. EEng 15:49, 24 February 2018 (UTC)
Perhaps my expression wasn't as clear as it might have been, but I think my position is clear enough, your non-sequiturs notwithstanding. Gatoclass (talk) 17:18, 24 February 2018 (UTC)
  • No but I don't think the above arguments are valid. However DYK was started when the wiki was fairly small, so that "old" articles might be familiar to "the regulars". I would support removing/relaxing the newness requirements. All the best: Rich Farmbrough, 13:48, 23 February 2018 (UTC).
Absolutely. The stupid newness requirement is the dumbest thing by far about DYK, and the root source of its quality problems. "I know! Let's feature on the main page rough drafts only one person has looked at!" Brilliant. EEng 15:31, 23 February 2018 (UTC)
Rich, we did already relax the "newness" requirement. In case anyone forgot, GAs are already eligible for being featured in the DYK slot along with new articles. This proposal would not merely relax the "newness" requirement, it would eliminate it. Gatoclass (talk) 15:40, 23 February 2018 (UTC)
Thanks for letting me know. And reversing it I am against. All the best: Rich Farmbrough, 16:52, 23 February 2018 (UTC).
  • No - Amongst many reasons... the Main Page has featured content but also needs to showcase new articles that could draw in new editors. violet/riga [talk] 15:48, 23 February 2018 (UTC)
  • Yes there’s no reason why DYK should continue being for mostly “new” articles. We are not desperately short of articles, and while I appreciate significant changes would be needed to enable this to happen, I think the ultimate goal should be on quality, and spreading out the reviews over two different processes seems like madness to me. Aiken D 15:56, 23 February 2018 (UTC)
    I tend to agree, this imaginary DYK thing about encouraging new editors to create content is bollocks. Rewarding someone for creating a dull stub or for making temporary content forks for credits in one place or another is hardly the same as rewarding someone for taking an article (or even creating one) and bringing it to good article status which is far more onerous and demanding. Those people, who aren't just in it for the quick win, should be the ones being rewarded. The Rambling Man (talk) 15:58, 23 February 2018 (UTC)
You would not eliminate the need for two reviews by having only GAs, because you would still have to have most of the DYK checks including the hook statement checks. As for GAN reviews, they are only as "onerous and demanding" as the user doing the review, and I know from personal experience that many GAN reviews are appallingly slapdash, which is why many of them have to be improved before they can even be featured at DYK. And they would probably get more slapdash still if DYK participants were forced to migrate there to get their articles on the main page. Gatoclass (talk) 16:32, 23 February 2018 (UTC)
I've got around 170 good articles (and conducted about an equal number of reviews), I can tell you that your experience is very odd and you should have rejected the reviews. Ironically, until lately there's been no reward for GAs besides WikiCup. Whereas toss together a junk stub with no grammar checks, no spelling checks, no real reference checks, no real fair use image checks, and you can be featured, in an equally slapdash review process which is fundamentally worse because of QPQ! The reward for getting a half decent article (a GA) onto the main page is clearly a good one and should be encouraged way more than these tedious junk stubs or pretend content forks which we see every WikiCup. My experience of reviewing GAs nominated at DYK is that they are literally a shoo-in. That's exactly how every single nomination should be but sadly it's not how it is. The Rambling Man (talk) 16:43, 23 February 2018 (UTC)
There is another reward for new GAs apart from Wikicup. It's called DYK, remember? New GAs can already be featured here, so you can't claim they are not getting the same "encouragement". Gatoclass (talk) 16:56, 23 February 2018 (UTC)
Yeah, I get it, but DYK is shamed and a running joke, so it would be much better to flip the requirements, i.e. GAs are the de facto articles we run, and new articles need to meet much higher standards than they currently do (and be properly reviewed, which they're currently not by any means). Placing boring detritus on the main page is something that should have stopped about five years ago, this myth that DYK is about encouraging new editors to contribute is total bunkum, and the lackadaisical approach to reviewing DYKs has rendered it not fit for purpose for a decent encyclopedia. I don't see Britannica operating a similar free-for-all joke. The sooner we extinguish this "every nomination eventually passes" paradigm and the sooner we start getting shot of reviewers or promoters who simply aren't doing the job properly, the better a chance DYK has of surviving. GAs are an essential part of that, and even if we only featured half a dozen GAs per day, that would be better than some of the honestly tedious rubbish that currently runs at DYK. The Rambling Man (talk) 17:02, 23 February 2018 (UTC)
The "not fit for purpose" claim has mostly been bandied about over hook inaccuracies, how exactly do you imagine that confining DYK to GAs only would address that? Of course, it wouldn't, because you'd still have the same issues cropping up and most probably you would still need to retain QPQs. With regard to quality, most DYK articles are well presented and of reasonably good quality, to the point where I don't think imposing GA standards would lead to a great improvement, except perhaps that nominations would get a bit longer on average, and that's not necessarily an advantage as articles of different lengths add variety. Not everybody wants to wade into a long article every time they click on a link. Gatoclass (talk) 17:36, 23 February 2018 (UTC)
No, we wouldn't (and in practice, we don't) have the same issues with GAs here. They are infinitely better prepared for the main page than most of the dross stubs and content forks. "Not everybody wants to wade into a long article"? Seriously, you're using that as an actual argument here? I think this has hit the buffers now...! The Rambling Man (talk) 07:17, 24 February 2018 (UTC)
I'd be willing to bet we have roughly the same number of hook issues, proportionally speaking, as we do with non-GAs, which is the main criticism raised about DYKs. As for "hitting the buffers", not at all, I've scarcely scratched the surface here, but since we've been debating this on and off for years and have yet to reach agreement, there doesn't seem much point in repeating myself. Gatoclass (talk) 08:46, 24 February 2018 (UTC)
No, we don't have anywhere near as many problems with GAs which are currently running alongside the usual dross as we do with the usual dross. As for "Not everybody wants to wade into a long article", about as close to clutching at straws as I've ever seen in this discussion, why then do TFAs draw ten times the audience of a "decent" DYK? Interesting, and per someone's suggestion below, we could simply ditch DYK for "TGA" Today's Good Article, and we'd almost certainly see more pageviews of a decent quality single article than all the dross articles in a typical set added together. That would be doing our readers a good service in other words. The Rambling Man (talk) 15:57, 24 February 2018 (UTC)
I thought for one delirious hour that I'd actually managed to get the last word in a discussion with you for once. Oh well, it was nice while it lasted. As for "why TFAs draw ten times the audience", my impression from looking at past statistics is that the DYK section collectively is often not far behind TFA in page hits and sometimes actually comes out ahead, which IMO is quite an achievement given that the TFA is visible on mobile devices and DYK isn't. Gatoclass (talk) 16:43, 24 February 2018 (UTC)
Oh no, not at all, but I do have a life outside Wikipedia. The point I was making was that FAs are long articles and draw 10 times the audience of the average start class DYK, so this curious "not everybody wants to wade into a long article" thing seems to make little or no sense under logical analysis. The Rambling Man (talk) 16:50, 24 February 2018 (UTC)
I mean, each DYK is competing with 7 other DYKs and takes up far less space, and is also below the far longer blurb for the TFA; that seems more a reason for that difference, and also I doubt that the average reader knows that the FA is longer than an DYK so it really is meaningless data IMO Galobtter (pingó mió) 16:53, 24 February 2018 (UTC)
Maybe it's meaningless, but what you said just backs up the suggestion that people are looking for short articles to read is somewhat silly. The Rambling Man (talk) 16:56, 24 February 2018 (UTC)
No. Johnbod (talk) 17:39, 23 February 2018 (UTC)
No I have argued that the DYK requirement for full referencing and not a work in progress approximate B-class criteria B1 and B2. That leaves grammar, structure and supporting materials to reach B-class, and these are normally easily met. So DYK articles should be capable of passing GA; but this is me thinking in terms of MilHist articles. The GA backlog for other articles is excruciatingly long, and flooding GA with DYK articles would not help. Hawkeye7 (discuss) 20:01, 23 February 2018 (UTC)
The GA backlog for other articles is excruciatingly long -- imagine if all the effort here at DYK were redirected to GA reviews instead. EEng 07:28, 24 February 2018 (UTC)
No. This was a bad idea the first time EEng proposed it, and it remains a bad idea after multiple times at bat. Fortunately, most people see that. BlueMoonset (talk) 05:50, 24 February 2018 (UTC)
Well, they keep repeating the same circular arguments anyway (with one or two exceptions above). EEng 07:28, 24 February 2018 (UTC)
  • No: But this reminds me of the idea that the landscape of English Wikipedia has moved past the stage of content creation, and we are now in the stage of continuously improving existing content. I suspect that if the trend of intensive focusing on the quality of DYK article continues, we may find ourselves adopting a variation of this proposal in the near future. Alex Shih (talk) 07:36, 24 February 2018 (UTC)
  • English Wikipedia has moved past the stage of content creation Alex, I'm surprised to see that comment from you of all people. You've worked on topics related to the history of China and Hong Kong, IIRC. You should know that the depth of coverage we have with respect to literally anything in the English-speaking world since the 20th century is far greater than that of any topic outside that category. How have we moved past content creation? Vanamonde (talk) 08:26, 24 February 2018 (UTC)
  • Vanamonde93, I wasn't necessarily endorsing the idea, just presenting a different perspective on what I thought the rationale behind this proposal could be, despite of it being a rather bad proposal. Perhaps I didn't phrase it well, of course content creation will never stop, but I do feel these days more emphasis should be put on improving what we already have (I often find myself going back to articles I created 10 years ago, and updating them with the current standards accordingly). Alex Shih (talk) 14:50, 24 February 2018 (UTC)
  • No. Obviously not. I've seen many articles that have passed GAN, but failed at DYK (which shows that the GA review was unacceptable, though that's another matter). Does not solve any problem regarding core content policies. feminist (talk) 08:53, 24 February 2018 (UTC)
  • No - DYK exists for a reason: to showcase newly-created or newly-improved articles and allow them to see a wider audience; at the same time, it encourages article improvement by both new and experienced reviewers. And besides, GANs are no means perfect: some GAs even end up being delisted or rewritten after failing at DYK. If you want to want DYK to only features GAs, then might as well rename it "Today's Good Article": even then, considering GA approval rates remain low, we'd be resorting to repeating hooks (which is already allowed at TFA, albeit after five years). Narutolovehinata5 tccsdnew 15:30, 24 February 2018 (UTC)
  • More circular "DYK should be the way it is because that's the way DYK is" reasoning.
  • The proposal is to still have the DYK review, like now.
  • If all the DYK effort were redirected to improving articles to GA status, there's be a lot of additional GAs. Not as many additional GAs as there are now DYKs, but there'd be nothing wrong with running 1/3 as many articles of much better quality.
EEng 15:49, 24 February 2018 (UTC)
Yes, but at most, there would still be very few articles being promoted per day. I see some sense in the idea, but it would be wildly impractical. GA promotion is still gonna be slow, and considering reaching GA status can be daunting, it can be very unfriendly for newcomers (unlike the new article or 5x expansion nominations, which are easier for newer editors). Like most of our current GAs were promoted long before GAs were allowed to go up for DYK (remember that new GAs weren't even DYK eligible until about four years ago). Narutolovehinata5 tccsdnew 16:01, 24 February 2018 (UTC)
  • Comment I know this is just a straw poll, but considering this particular proposal has only been supported by two users so far (one of whom is the proposer), this feels the most snowy among the questions. You asked "should DYKs be limited to GAs?", and from the way things are going, the result looks like a resounding "No". Narutolovehinata5 tccsdnew 16:01, 24 February 2018 (UTC)

Threaded discussion

  • @Cwmhiraeth and Gatoclass: Fair enough; indeed, when I made this suggestion, I did not mean to suggest failing under the circumstances Cwm mentions. I mean basic article requirements, not basic DYK requirements. Essentially, is it policy-compliant? If we're okay about approving quick-fails for a subset of the criteria, let's look at what those should be. Vanamonde (talk) 14:21, 22 February 2018 (UTC)
  • This was very unclear. As this is DYK, naturally it's going to be viewed here in that context, and policy compliance is one of the specified DYK criteria. Although it's annoying to people who have already answered (and it would really help if before you posted something like this you did a draft somewhere and invited comments to avoid this sort of thing happening), I'd like to suggest you reword this one, if not split it into two: failing to identify issues with the DYK criteria, and failing to identify issues with the non-DYK-specific Wikipedia policies. But it seems that there is something further here: whether people should get credit if they identify a serious basic issue like the article is too short, and (sensibly) don't do a complete review because they'd just have to redo the review once the extra material was added. If the nominator never expands the article to minimum length, should the reviewer not receive QPQ credit for the review? If the reviewer does do a full review initially, then they should get credit; if they point out the basic flaw but no more, then only when the nomination closes should a QPQ be considered, though I'm on the fence about that one: I don't think we should generally encourage piecemeal reviews. BlueMoonset (talk) 15:21, 22 February 2018 (UTC)
  • Well, I for one haven't the stamina to create a draft for a straw poll which itself is a precursor to a draft of an RFC that will be discussed before the RFC. It's a non-binding poll. People can add things mid-way. Also, I did explain what I meant by "basic" requirements; a few rows higher up, in the first question. I am personally unenthusiastic about quick fails for a nomination that fails to meet DYK's technical requirements that are not related to core policy (expansion, QPQ, etc). So I'm not going to create a separate question for that. I'll just copy over what I mean by "basic", and leave it at that.

    I'm personally not in favor of a quick identification of a serious issue receiving QPQ credit; whenever I've identified such an issue, I've never claimed it as a QPQ. But I see this as an issue separate from that of review quality. Users who identify a serious issue with a nomination and then move on are not contributing to a drop in review quality, whether they count it as a QPQ or not. Vanamonde (talk) 15:46, 22 February 2018 (UTC)

  • Actually I am against the idea of quick failing anything (with the exception of nominations way off the mark I suppose). If we accept the basic premise that DYK is here to encourage article creators and expanders, then non-compliance with DYK rules or Wikipedia policy should be met with help and guidance, which is what usually happens here, and definitely not with criticism and ridicule. Cwmhiraeth (talk) 19:02, 22 February 2018 (UTC)
    How many DYK proposers are new editors? The Rambling Man (talk) 20:24, 23 February 2018 (UTC)
Well, here are some stats. I started on https://en.wikipedia.org/wiki/Template_talk:Did_you_know and looked at the first 20 nominations since February 1. Feel free to continue adding to this list if you would like a bigger sample. 70.67.222.124 (talk) 22:12, 23 February 2018 (UTC)
edit counts for DYK nominators
  1. Sutton Hoo Helmet (sculpture – Created/self-nominated by Usernameunique, 11,804 edits
  2. Wang Bingzhang (general) – Created/self-nominated by Zanhe, 77,610 edits
  3. 1838 Georgetown slave sale - Created by Antony-22 15,255 edits and Fuzheado 22,741 edits, nominated by Antony-22 15,255 edits
  4. Fidel Castro Díaz-Balart - Created by BD2412 more than 350,000 edits and Moscow Mule 783 edits, nominated by BD2412, more than 350,000 edits
  5. Pythagoras - Improved to GA/self-nominated by Katolophyromai, 10,918 edits
  6. Saudi Arabia and weapons of mass destruction - Created/expanded/self-nominated by Ali Ahwazi, 531 edits
  7. Rodriguinho Marinho - Created/expanded/self-nominated by Royroydeb, 18.824 edits
  8. Marcel Cordes – Created and self-nominated by Gerda Arendt, 165,711 edits
  9. Chandra Khonnokyoong - Improved to Good Article status by Farang Rak Tham, 5,656 edits and Thanissaro, 924 edits, nominated by Farang Rak Tham, 5,656 edits
  10. Transforming Infrastructure Performance - Moved to mainspace and self-nominated by Dumelow, 22,962 edits
  11. Scherzo (Stravinsky) - Created by Ron Oliver, 2,467 edits, nominated by Gerda Arendt, 165,711 edits
  12. Infrastructure Cost Review - Moved to mainspace and self-nominated by Dumelow, 22,962 edits
  13. Stanley Gelbier - Created by Whispyhistory, 2,501 edits and Philafrenzy (talk), 162,400, nominated by Whispyhistory, 2,501 edits
  14. Charles LiMandri – Created and self-nominated by Lionelt, 22,030 edits
  15. The Infinity Gauntlet - 5x expanded and self-nominated by Argento Surfer, 19,654 edits
  16. Sainte-Anne Hospital Center - Created and self-nominated by Robert K S, 15,822 edits
  17. Museum of Geometric and MADI Art - Moved to mainspace and self-nominated by Michael Barera, 15,512 edits
  18. EastEnders in Paris - Moved to mainspace by Kelvin 101, 14,255 edits and nominated by Soaper1234, 10,808 edits
  19. Devante Mays - 5x expanded and self-nominated by Church, 9,228 edits
  20. Ian Stephens (editor) – Created and self-nominated by SlimVirgin, 158,769 edits
Well that speaks for itself, although nothing different from what I analysed a few years ago when the average nominator was around the 30,000 edit mark. So please, everyone, stop claiming this about encouraging new editors. It's not at all, it's about churning out credits for old and savvy editors, with the odd newbie sprinkled in. The Rambling Man (talk) 22:44, 23 February 2018 (UTC)
We all were beginners once. My first article was deleted, then I got help to revive it by Cmadler who nominated it for DYK (without telling me), and I liked the system. I am prouder of nominating for others than for myself, and wouldn't mind someone to write me the 200 medal ;) --Gerda Arendt (talk) 22:58, 23 February 2018 (UTC)
  • I'm probably plowing a lonely furrow once again, but here goes...the process isn't about new users, it's about new content. Newly created or expanded articles are likely to be from topics that need to be represented better. Therefore, DYK should continue to provide an incentive to create and expand articles. If new users take advantage of it, then that's great; but even if it's experienced users working on poorly covered topics (wildlife, pre-20th century history, literally anything outside the anglosphere) that's a good thing, and we should encourage it. Examples from my own work include Betty Tebbs, Carlos Enrique Díaz de León, Erol Önderoğlu, Strike Vilakazi, Muzoon Almellehan, and many more. Waiting to bring articles such as these to GAN is impractical; and if folks find them tedious, then I'm sorry that they are unable to be engaged in things outside their sphere of interest. @Hawkeye7 and EEng: this is relevant to what you both were saying above, too. Vanamonde (talk) 05:00, 24 February 2018 (UTC)

Expedited review request

I recently nominated Disappearance of Gary Mathias; my hope is to have it on the Main Page for February 24-25 (Queue 5 would be ideal), the 40th anniversary. Can someone do this? Daniel Case (talk) 16:40, 22 February 2018 (UTC)

I'd be delighted. The Rambling Man (talk) 16:42, 22 February 2018 (UTC)
De-lighted
Fixing link to nomination template. BlueMoonset (talk) 17:15, 22 February 2018 (UTC)
@The Rambling Man: does that mean you're reviewing this? Yoninah (talk) 20:12, 22 February 2018 (UTC)
Yes, Yoninah, he's reviewed it. There are also issues with the submitted QPQ. BlueMoonset (talk) 20:17, 22 February 2018 (UTC)
Indeed, I was waiting for the "thanks, that'd be great" but it never arrived. Nevertheless, given the timeliness of the review, I waded in. Keep up everyone! The Rambling Man (talk) 20:24, 22 February 2018 (UTC)
Now approved and in special occasion section; can someone please promote to Prep 5 as requested before the prep is promoted to queue and we need an admin to do it? (I'm a little too involved to do it myself.) One of the current hooks there will need to be moved to another prep to make room. BlueMoonset (talk) 20:19, 23 February 2018 (UTC)

Wahey, fuck the cynicism and the arcane methods, we did what we needed to do. And hey, it might just have worked for the benefit of everyone. The Rambling Man (talk) 20:27, 23 February 2018 (UTC)

DYK is almost overdue

In less than two hours Did you know will need to be updated, however the next queue 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:

  1. Check the prep areas; if there are between 6-10 hooks on the page then it is probably good to go. If not move approved hooks from the suggestions page and add them and the credits as required.
  2. Once completed edit queue #3 and replace the page with the entire content from the next update
  3. Add {{DYKbotdo|~~~}} 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, DYKUpdateBot (talk) 22:08, 22 February 2018 (UTC)

Busing

I have just promoted this hook to Prep2. From the British point of view, the use of the word "busing" here is very unsatisfactory. In the UK we might talk of "bussing" or "school transport", but the link to desegregation busing shows there is more to it than just that. Can anyone think of a better way to phrase this hook to suit US readers and the rest of us? Cwmhiraeth (talk) 08:32, 23 February 2018 (UTC)

  • I'd say pull this, unless a way of avoiding the desegregation busing link can be found. That article is horribly substandard and shouldn't be linked from the main page, with whole unsourced sections. More important, it doesn't mention New York at all and thus is completely irrelevant to the hook. Black Kite (talk) 19:47, 23 February 2018 (UTC)
    What if we just said "struggled with school integration from the 1960s to the 1980s?" (I also changed "between" to "to" since "between" implies fixed moments in time as the endpoints, and "1960s" is not a moment but a span). Does that work? --Jayron32 19:51, 23 February 2018 (UTC)
  • Black Kite, Jayron32, Cwmhiraeth, can I ask what part of the article (and, for that matter, what source) talks about desegregation struggles extending into the 1980s? The words "desegregation" and "busing" each appear once, in the same sentence, one that talks about the late 1960s and early 1970s. The only things mentioned about the 1980s are that the white percentage of the population went from 90% to 75%, and that the school board was far whiter than the school student body, which in 1983 was 75% black. I don't see that the hook fact of 1960s to 1980s is supported by the article. If I've missed something, I apologize. If not, however, it would probably be best if the hook were pulled and a new hook or hooks considered in the context of a reopened review. BlueMoonset (talk) 05:37, 24 February 2018 (UTC)
  • Actually, the article discusses specific desegregation attempts through 1994, ones you missed in your reading include " In 1978, a NYCDOE integration plan was tentatively approved by the state. Black students from Brownsville could enroll in Canarsie schools as long as they did not make up a majority of the student population there" and "This disproportionate representation continued through 1994, when the mostly-white members of District 18 opposed a plan to split off several schools into a nearby district in order to increase the proportion of black votes in both districts." --Jayron32 05:43, 24 February 2018 (UTC)
  • Jayron32, I see the 1978 one as applicable, so we get into the late 1970s (was the plan in the source ultimately put into effect?), but the "disproportionate representation" in the second is referring to the school board of District 18 and their holding on to power, is it not? It's a stretch to equate this to school desegregation without more specific evidence. BlueMoonset (talk) 06:02, 24 February 2018 (UTC)

Template:Did you know nominations/List of court cases involving Alliance Defending Freedom

Please, this is about to hit the main page, yet it's a pure copy/paste from another article, i.e. Alliance Defending Freedom. There's no attribution given, the reviewer (Church) and the promoter (Cwmhiraeth) need to understand this sort of thing is completely unacceptable (again). Did anyone check if this page was an orphan? Did anyone bother checking the only article that it was related to, from which the entire list was created? The Rambling Man (talk) 21:34, 23 February 2018 (UTC)

Criterion 1.a. "For DYK purposes, a "new" article is no more than seven days old, and may not consist of text spun off from a pre-existing article." Chris857 (talk) 21:41, 23 February 2018 (UTC)
In other words, this should be be pulled, and the reviewer and promoter notified that this is yet another example of a badly managed DYK. The Rambling Man (talk) 21:44, 23 February 2018 (UTC)
The Rambling Man I apologize, but given my current medical condition I won't be able to help fix any problems this time around. Although I will note as I understood the criteria there was nothing regarding it being a violation for being based on on another page. I have reread the criteria and offer my apologies for my mistake. --Church Talk 00:11, 24 February 2018 (UTC)
As pointed out by TRM in his inimical fashion, this article is not eligible for DYK as it does not meet the newness criterion, having being wholly copied from another article (without the necessary attribution). Cwmhiraeth (talk) 07:58, 24 February 2018 (UTC)
As missed by the promoter in their "inimical fashion"... The Rambling Man (talk) 08:01, 24 February 2018 (UTC)
You're quick off the mark, I meant "inimitable fashion". Cwmhiraeth (talk) 08:22, 24 February 2018 (UTC)
Point remains, you missed these kinds of simple issues, again. The Rambling Man (talk) 13:17, 24 February 2018 (UTC)
  • Perhaps everyone could try to be more imical and itable. EEng 15:24, 24 February 2018 (UTC)
TRM has invented a whole array of hoops through which he thinks a prep builder should jump. The actual instructions for prep builders are here. Cwmhiraeth (talk) 18:33, 24 February 2018 (UTC)
And you have created some kind of record by building preps which inevitably contain fundamental errors. This one was absolutely trivial to detect, yet it got close to the main page (yet again). Prep building is not an excuse to just send detritus or errors to the main page. If you don't think that applies, please stop doing it. The Rambling Man (talk) 20:21, 24 February 2018 (UTC)
Not sure what the great problem would be if it did hit the main page since it is DYK pedantry and not an actual problem.. Galobtter (pingó mió) 20:26, 24 February 2018 (UTC)
Well then, let's get rid of most of the arcane shit that surrounds this corrupted process! Or maybe move DYK to a Main Page sandbox in toto so we can publish everything that gets nominated to a safe zone that doesn't continually embarrass the encyclopedia. The Rambling Man (talk) 20:33, 24 February 2018 (UTC)
Mostly that its the reviewer's job to check that, and that only "serious" errors really need checking by the prep builder Galobtter (pingó mió) 20:41, 24 February 2018 (UTC)
P.S. it is DYK pedantry well actually, no, correct attribution is a sitewide requirement, not unique to DYK. Please don't confuse the issue. The Rambling Man (talk) 20:34, 24 February 2018 (UTC)

Prep 5 - Arsenal home games

... that Arsenal reached the 2018 EFL Cup Final against Manchester City today after playing four out of the five previous matches at home? The C of E, SounderBruce

SO WHAT? Manchester City played three out of the four at home. This is NOT INTERESTING TO A BROAD AUDIENCE. Suggest this is quickly pulled in favour of some alternative which is actually interesting. The Rambling Man (talk) 22:51, 23 February 2018 (UTC)

"Coincidentally, the two team's respective women's teams will contest the WSL League Cup Final two weeks after the match.[7]" MORE INTERESTING. The Rambling Man (talk) 22:52, 23 February 2018 (UTC)
"Arsenal reached the final without leaving London as four of their five games were at home,[18] with the away leg of the semi final being played in London.[18] " MORE INTERESTING. The Rambling Man (talk) 22:53, 23 February 2018 (UTC)
"It will be the first League Cup final contested under the "Carabao Cup" name following the sponsorship of Carabao Energy Drink." MORE INTERESTING. The Rambling Man (talk) 22:53, 23 February 2018 (UTC)
Agree that one of the first two suggested by TRM would be more interesting. Last one I like less as it's about sponsorships and advertising. Joseph2302 (talk) 23:32, 23 February 2018 (UTC)
If you check the nomination page, you'll notice that the proposed hook was "... that Arsenal reached the 2018 EFL Cup Final against Manchester City today without leaving London" but the reviewer insisted that it could not be used while I was sure it could. If we could use that, it would be better in my view. The C of E God Save the Queen! (talk) 06:10, 24 February 2018 (UTC)
The "not leaving London" one is definitely the best IMO. Suggest something like "... that Arsenal reached the 2018 EFL Cup Final without playing a game outside London, after four home games and one away game, which was at Chelsea? The claim at the nomination page that this is synthesis despite sources saying all of the games were played in London is ridiculous IMO. Black Kite (talk) 10:40, 24 February 2018 (UTC)
@Black Kite: I am happy for my originally proposed hook to go in the prep if you're happy for it to? The C of E God Save the Queen! (talk) 11:39, 24 February 2018 (UTC)

The C of E, I don't think your original hook is quite precise enough. I suggest we go with a meld of your original hook and Black Kite's:

I have substituted the following hook:

I changed the location of "today" because I assume the hook is meant to be referring to tomorrow's cup final rather than that Arsenal only reached the final "today" (since it apparently did that a month ago). I haven't fact checked the hook myself on this occasion, I'm assuming it is correct based on the preceding discussions. Somebody still has to load this set into the queue though, I probably won't be able to find time to do it myself. Gatoclass (talk) 15:40, 24 February 2018 (UTC)

  • I think that's fine. Black Kite (talk) 16:57, 24 February 2018 (UTC)
  • I should note that I rejected the original hook because it was not properly sourced within the article and I could not find a source that said that Arsenal played most of their cup matches in London. SounderBruce 21:23, 24 February 2018 (UTC)
  • It wasn't "most", it was "all"... I guess it's difficult if people don't realise that Chelsea (or Stamford Bridge) is in London, otherwise the fact that they had played all other matches at home (plus the Chelsea two-legged affair) is clearly an all-London run of games. The Rambling Man (talk) 22:07, 24 February 2018 (UTC)

Prep 3 – Tomasz Mackiewicz

... that during his seventh attempt to summit 8,126 m (26,660 ft) high Nanga Parbat, Polish mountain climber Tomasz Mackiewicz went missing on January 27, 2018? Yoninah, Yoninah, Usernameunique

Presumably this should say "summit the 8,126 m...." plus it would be better the other way round, i.e. "Polish mountain climber Tomasz Mackiewicz went missing on January 27, 2018, while climbing Nanga Parbat...", yet even then the article says he disappeared at the summit, not during an "attempt to summit", so either he made it or he didn't, either way the article and the hook disagree. The Rambling Man (talk) 23:01, 23 February 2018 (UTC)

Hook has been moved from Prep 5 to Prep 3 to make a space available for a special occasion hook for tomorrow. This also gives more time for an acceptable hook to be agreed upon. BlueMoonset (talk) 05:18, 24 February 2018 (UTC)
"Summit" is a verb now? What's wrong with just "climb"? Black Kite (talk) 10:36, 24 February 2018 (UTC)
Well, professional climbers are more interested in reaching the top than just climbing the mountain. Yoninah (talk) 20:33, 24 February 2018 (UTC)
TRM, he was left behind by his climbing partner at 7400 m; the summit is 8126 m. What do you think of this alt based on your recommendation?
  • ALT1: ... that Polish mountain climber Tomasz Mackiewicz went missing on January 27, 2018, during his seventh attempt to reach the summit of the 8,126 m (26,660 ft) high Nanga Parbat in Pakistan? Yoninah (talk) 20:39, 24 February 2018 (UTC)
  • Better, you need to treat the height adjectively, so "... the 8,126-metre (26,660 ft) high ..." but otherwise fine by me. The Rambling Man (talk) 20:43, 24 February 2018 (UTC)

Prep 5 - Blame the Russians!

... that a white supremacist organization claimed the racial integration of schools in the United States was a plot created by the government of Russia to "mongrelize" White Americans? Yoninah, Coffee, Casliber

The article says that the organisation's spokesperson said "plan that was founded in Moscow in 1924 to mongrelize the white race in America". This is not the same as saying "the government of Russia", and being absolutely precise, there's a mild difference between "plan" and "plot". I realise this hook has been written to somewhat "sensationalise" the claim, but it's wandered too far from the original source in my opinion. The Rambling Man (talk) 08:25, 24 February 2018 (UTC)

Moscow implies the government of Russia, just as saying "the Kremlin" does. However, I'm fine with changing it to "Moscow" if that's found necessary. Plan vs. plot I'm neutral on however; they are synonyms and it is indeed (in full context) what the spokesman said just a more descriptive word. But I'm not hard set on anything. Face-smile.svg Coffee // have a ☕️ // beans // 09:47, 24 February 2018 (UTC)
ok I tweaked it per this discussion to align it closer to the source Cas Liber (talk · contribs) 13:30, 24 February 2018 (UTC)

Template:Did you know nominations/Saori Ōnishi

Hi. So my DYK nomination was reviewed, and now it's in the Approved section. I had requested for a special occasion hook on March 20: will this be okay, or should the hook not be put up on that date? Thanks. Narutolovehinata5 tccsdnew 15:35, 24 February 2018 (UTC)

Once it's approved, you can move it yourself to the Special Occasion holding area. Yoninah (talk) 17:40, 24 February 2018 (UTC)
I have moved it to the Special Occasion holding area for March 20th. Cwmhiraeth (talk) 18:24, 24 February 2018 (UTC)
Yoninah, people should not move their own special occasion requests, because not all requests are appropriate. Someone other than the nominator should decide whether it is a reasonable request—we've had a few that weren't and the request was declined—and if it is then it should be moved. BlueMoonset (talk) 22:47, 24 February 2018 (UTC)
It probably doesn't matter, people who are creating sets are doing little more than just moving hooks in and doing nothing much else. The Rambling Man (talk) 22:52, 24 February 2018 (UTC)
Neither to the point nor helpful in this thread. But you knew that. BlueMoonset (talk) 00:07, 25 February 2018 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Did_you_know&oldid=827496551"
This content was retrieved from Wikipedia : http://en.wikipedia.org/wiki/Wikipedia_talk:Did_you_know
This page is based on the copyrighted Wikipedia article "Wikipedia talk:Did you know"; it is used under the Creative Commons Attribution-ShareAlike 3.0 Unported License (CC-BY-SA). You may redistribute it, verbatim or modified, providing that you comply with the terms of the CC-BY-SA