Wikipedia talk:Did you know: Difference between revisions

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.
Content deleted Content added
Extended confirmed users, Page movers, Template editors
65,353 edits
Line 121: Line 121:
== Follow-up RFC: Should recreations of articles deleted as copyright violations be allowed to re-run on DYK? ==
== Follow-up RFC: Should recreations of articles deleted as copyright violations be allowed to re-run on DYK? ==


<div class="boilerplate vfd xfd-closed" style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;">
<!-- [[User:DoNotArchiveUntil]] 23:01, 1 May 2023 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1682982081}}
:''The following discussion is an archived record of a [[Wikipedia:Requests for comment|request for comment]]. <span style="color:red">'''Please do not modify it.'''</span> No further edits should be made to this discussion.'' ''A summary of the conclusions reached follows.''
{{rfc|proj|rfcid=63F7490}}
<div style="margin: 0 2.5em;">There is broad consensus that such articles should be '''generally excepted''' from the normal rule against reruns, so long as they would otherwise qualify as "new". Edge cases, such as a rerun after a very short period of time, can be handled [[WP:UCS|using common sense]]. There's an implementation question here about how a non-admin reviewer can actually verify newness; I would suggest either [[:Category:Wikipedia administrators willing to provide copies of deleted articles|requesting a copy of the deleted page]] or enquiring here on WT:DYK.{{pb}}Since the 5X copyvio rule is codified in [[WP:DYKSG]] rather than the main rules, I will do the same with this consensus, as an amendment to D1. <span class="nowrap"> <span style="font-family:courier">-- [[User:Tamzin|<span style="color:#E6007A">Tamzin</span>]]</span><sup>[''[[User talk:Tamzin|<span style="color:#E6007A">cetacean needed</span>]]'']</sup> (she&#124;they&#124;xe)</span> 19:53, 4 April 2023 (UTC)</div>
<!-- Template:rfc top

Note: If you are seeing this page as a result of an attempt to register a new request for comment, you must manually edit the nomination links in order to create a new discussion page using the name format of [[Wikipedia:Requests for comment/''subject'' (Second)]]. When you create the new discussion page, please provide a link to this old discussion.

-->
----

Following up on [[#Queue 7: Nitpicking Edition]] and [[#Follow-up question on DYK re-eligibility]], should an exception to DYK [[Wikipedia:DYKCRIT|eligibility criterion]] 1c (namely "An article is ineligible for DYK if it has previously appeared on the main page as a bold link at DYK.") be added which permits articles previously featured on DYK to be re-eligible if they have been deleted as a copyright violation and recreated? It has been pointed out that discussion above does not indicate a formal consenus, and as such this RfC seeks to more formally assess whether or not there is consensus to modify the criterion. Note that this is only discussing copyright violations and recreations, not broader re-runs, which a different RFC could address. [[User:Eddie891|Eddie891]] <small>''<sup> [[User talk:Eddie891|Talk]]</sup> <sub>[[Special:Contributions/Eddie891|Work]]</sub>'' </small> 22:39, 27 March 2023 (UTC)
Following up on [[#Queue 7: Nitpicking Edition]] and [[#Follow-up question on DYK re-eligibility]], should an exception to DYK [[Wikipedia:DYKCRIT|eligibility criterion]] 1c (namely "An article is ineligible for DYK if it has previously appeared on the main page as a bold link at DYK.") be added which permits articles previously featured on DYK to be re-eligible if they have been deleted as a copyright violation and recreated? It has been pointed out that discussion above does not indicate a formal consenus, and as such this RfC seeks to more formally assess whether or not there is consensus to modify the criterion. Note that this is only discussing copyright violations and recreations, not broader re-runs, which a different RFC could address. [[User:Eddie891|Eddie891]] <small>''<sup> [[User talk:Eddie891|Talk]]</sup> <sub>[[Special:Contributions/Eddie891|Work]]</sub>'' </small> 22:39, 27 March 2023 (UTC)
: Pinging participants in the prior discussions: {{u|David Eppstein}}, {{u|Johnbod}}, {{u|Aoidh}}, {{u|Chipmunkdavis}}, {{u|Amakuru}}, {{u|theleekycauldron}}, {{u|Narutolovehinata5}}, {{u|Joseph2302}}, {{u|RoySmith}}, {{u|Cielquiparle}}. [[User:Eddie891|Eddie891]] <small>''<sup> [[User talk:Eddie891|Talk]]</sup> <sub>[[Special:Contributions/Eddie891|Work]]</sub>'' </small> 22:39, 27 March 2023 (UTC)
: Pinging participants in the prior discussions: {{u|David Eppstein}}, {{u|Johnbod}}, {{u|Aoidh}}, {{u|Chipmunkdavis}}, {{u|Amakuru}}, {{u|theleekycauldron}}, {{u|Narutolovehinata5}}, {{u|Joseph2302}}, {{u|RoySmith}}, {{u|Cielquiparle}}. [[User:Eddie891|Eddie891]] <small>''<sup> [[User talk:Eddie891|Talk]]</sup> <sub>[[Special:Contributions/Eddie891|Work]]</sub>'' </small> 22:39, 27 March 2023 (UTC)
Line 147: Line 155:
*'''Yes''' if an article is deleted as a copyvio and a new article written, that article is new and meets all the new article criteria. And exceptions for copyvios are consistent with how we calculate 5x expansions on DYK. [[User:Joseph2302|<b style="color:#0033ab">Joseph</b>]][[User talk:Joseph2302|<b style="color:#000000">2302</b>]] ([[User talk:Joseph2302|talk]]) 11:11, 28 March 2023 (UTC)
*'''Yes''' if an article is deleted as a copyvio and a new article written, that article is new and meets all the new article criteria. And exceptions for copyvios are consistent with how we calculate 5x expansions on DYK. [[User:Joseph2302|<b style="color:#0033ab">Joseph</b>]][[User talk:Joseph2302|<b style="color:#000000">2302</b>]] ([[User talk:Joseph2302|talk]]) 11:11, 28 March 2023 (UTC)
*'''Yes'''. Trainsandotherthings left me a note on my talk page about this RFC. In all honesty, I was going to go the exact route Maile66 pictured, and rewrite some of the Hathorn articles that were presumptively deleted, especially since I'm involved at CCI and I clean up a lot of this...questionable content. (Half the challenge is finding something that has RS and is clearly notable in that trainwreck of a CCI). @[[User:Narutolovehinata5|Narutolovehinata5]]: The Doug Coldwell ones in particular are the most recent. Much of the "ran at DYK" articles were created or expanded before 2020 I would say, so there's not a super large risk of one running in <3 years of its first DYK unless it's DC. Rewrites on the CCIs with massive amounts of presumptive deletions are almost always done by people not involved in the CCI, because most of the subjects are blocked as well. [[User:Sennecaster|<span style="color:#A91E4A">Sennecaster</span>]] ([[User talk:Sennecaster|<span style="color:#9511AC">Chat</span>]]) 19:41, 28 March 2023 (UTC)
*'''Yes'''. Trainsandotherthings left me a note on my talk page about this RFC. In all honesty, I was going to go the exact route Maile66 pictured, and rewrite some of the Hathorn articles that were presumptively deleted, especially since I'm involved at CCI and I clean up a lot of this...questionable content. (Half the challenge is finding something that has RS and is clearly notable in that trainwreck of a CCI). @[[User:Narutolovehinata5|Narutolovehinata5]]: The Doug Coldwell ones in particular are the most recent. Much of the "ran at DYK" articles were created or expanded before 2020 I would say, so there's not a super large risk of one running in <3 years of its first DYK unless it's DC. Rewrites on the CCIs with massive amounts of presumptive deletions are almost always done by people not involved in the CCI, because most of the subjects are blocked as well. [[User:Sennecaster|<span style="color:#A91E4A">Sennecaster</span>]] ([[User talk:Sennecaster|<span style="color:#9511AC">Chat</span>]]) 19:41, 28 March 2023 (UTC)
<div style="padding-left: 1.6em; font-style: italic; border-top: 1px solid #a2a9b1; margin: 0.5em 0; padding-top: 0.5em">The discussion above is closed. <b style="color: #FF0000;">Please do not modify it.</b> Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.</div><!-- from [[Template:Archive bottom]] -->
</div><div style="clear:both;"></div>


== Wording of [[Matar judíos]] hook ==
== Wording of [[Matar judíos]] hook ==

Revision as of 19:53, 4 April 2023

Did you know?
Introduction and rules
IntroductionWP:DYK
General discussionWT:DYK
GuidelinesWP:DYKCRIT
Reviewer instructionsWP:DYKRI
Nominations
Nominate an articleWP:DYKCNN
Awaiting approvalWP:DYKN
ApprovedWP:DYKNA
April 1 hooksWP:DYKAPRIL
Preparation
Preps and queuesT:DYK/Q
Prepper instructionsWP:DYKPBI
Admin instructionsWP:DYKAI
Main Page errorsWP:ERRORS
History
StatisticsWP:DYKSTATS
Archived setsWP:DYKA
Just for fun
Monthly wrapsWP:DYKW
AwardsWP:DYKAWARDS
UserboxesWP:DYKUBX
Hall of FameWP:DYK/HoF
List of users ...
... by nominationsWP:DYKNC
... by promotionsWP:DYKPC
Administrative
Scripts and botsWP:DYKSB
On the Main Page
To ping the DYK admins{{DYK admins}}

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

Sandbox proposal

I've been wanting to get back into promoting for a while now, but thankfully, it seems that Cielquiparle and Bruxton are usually on top of it :) that being said, it would be nice if I could promote a hook when i have the energy, without doing the prep work to fill a whole set or wait until one is empty. So, I propose that there be a single faux-prep area of unlimited size (PSHAW can automatically create a new slot in a full set) that anyone can pop by and promote a hook to, without regard for hook placement. This has quite a few benefits:

  • It's always accessible, even when the preps are full.
  • The preps can be full, because there'll always be an emergency place to dump hooks.
  • It allows promoters to decouple the steps of re-checking and scheduling – as a longtime promoter, I found that dealing with one of those at a time was much, much easier than having to balance both in my head while looking for nominations I could verify.
  • Promoters can easily fill multiple sets in the sandbox this way, too; instead of having to deal with U.S. and bio hook problems in each set individually while promoting, that can be worked out at the end.
  • It allows promoters to decide on a hook ahead of time.
  • It gives new promoters a way to dangle their feet in the water without being too worried about consequences.
  • I don't personally like this, but admins frequently take replacement hooks when one is pulled from prep – it would be nice if they could do that without screwing up finished preps.

The only drawback I can think of is that DYKHousekeepingBot might need an update if we allow an arbitrary number of hooks to be promoted at any time, to adjust how we handle two-a-day sets. This good with everyone? theleekycauldron (talkcontribs) (she/her) 08:45, 18 March 2023 (UTC)[reply]

I agree that it makes sense to uncouple reviewing from assembling a prep set. Different people might be interested in (and good at) certain aspects, but not others. And as leeky points out, doing a full prep set may be more than somebody can handle in one session. And I certainly agree that stealing a hook from a previously-completed prep set to backfill a hole is sub optimal.
But I'm not sure a variable-length sandbox is the right solution. Why not just do your re-review right on the nomination template? If it passes, add a second tick (or we can come up with some snazzy new icon). Prep builders will be instructed to not promote a hook unless it has two ticks (kind of like Saul Goodman not having enough parking stickers). It's also easy to decide which of several hooks to use; just specify that with your re-tick. -- RoySmith (talk) 15:55, 18 March 2023 (UTC)[reply]
@RoySmith: I gave a lot of thought to that myself, but I think there are a couple of speed bumps that pop up with that solution. First off, Prep builders will be instructed to not promote a hook unless it has two ticks very quickly runs into problems, as that just creates more headache for prep builders who want to promote directly – the sandbox is more out-of-the-way. Second, two-ticks makes it more complicated for new promoters to get started – a sandbox, by contrast makes it simpler. Third, it would break any kind of promotion–counting tools someone might be intent on building, since the person who closes the subpage is no longer necessarily the credited promoter. For overall user-friendliness, I think the sandbox is a less bureaucratic and more easily understood solution than "wait, I need another approval before I can see my hook on the Main Page? And a separate closure?"
I'm not entirely opposed to a two-ticks solution: it has a lot of advantages, to be sure, and I'd probably support it if it were the only thing on the table. But I think a sandbox is just a lower-cost way of gettin' it done, and given that I really do want to get back into promoting, I think it's the best pick. It'd truly suck to have a no-consensus-defaults-to-status-quo on this one. theleekycauldron (talkcontribs) (she/her) 10:02, 19 March 2023 (UTC)[reply]
i admittedly prefer the sandbox proposal over the two-ticks proposal. the sandbox proposal hides the additional complexity from editors who are still just trying to get used to nominations. in addition, promoters who don't wish to use the sandbox can just ignore it, while implementing the two-ticks proposal appears to necessarily disrupt their current workflow. offhand, the only downside i can think of that hasn't already been mentioned is that if a hook with a preferred run date is promoted to the sandbox, the editor moving the hook from the sandbox to one of the prep areas may not be aware of the date request. (this issue seems easily solvable, though; invisible comments could be one solution.)
what if we tried the sandbox proposal for a month? i assume its implementation is fairly simple, so trying the idea out shouldn't cost us much. we can always revert to our current practice if it turns out that the sandbox causes more problems than it solves.
theleekycauldron, i don't know if you already have a name for the sandbox in mind, but what do you think about calling it prep area 0? i think this would make it more clear that hooks in the sandbox have already gone through an additional review by a promoter, and are simply waiting to be scheduled. (i assume that this will also make it easier to update the code for pshaw.) dying (talk) 19:59, 27 March 2023 (UTC)[reply]
@dying: I think calling it "prep area 0" might be a little confusing; how about "preparation area sandbox", or the cheekier "pre-preparation area sandbox"? pshaw probably handles it fine either way (although "0" might still be the code to access it there). @RoySmith: any objection to us going through with a trial period? theleekycauldron (talkcontribs) (she/her) 06:21, 28 March 2023 (UTC)[reply]
Mumble. I don't think it's a great solution, but I'm just one opinion. My objection shouldn't be a blocker if there's wider consensus to go ahead. -- RoySmith (talk) 16:14, 28 March 2023 (UTC)[reply]
RoySmith, the two-ticks proposal sounds interesting, but there seem to be a number of details that have yet to be worked out. (will promoters now be required to add a second tick before directly promoting a hook to the prep areas? if so, will theleekycauldron be able to find the time to implement this in pshaw, or will it have to be done manually? will there be a separate wp:dyknaa page? if so, how would wp:dyknaa differ from the sandbox? will wugbot need to be recoded as well?) i think theleekycauldron's is the better of the two proposals i know of so far, though i am open to other solutions.
theleekycauldron, that sounds good. i think my main worry was that, if the sandbox was simply located at "Template:Did you know/Sandbox", nominators unfamiliar with the promotion process might worry that the sandbox was some sort of indefinite purgatory. calling it "preparation area sandbox" should hopefully make it more clear that hooks in the sandbox were going through the normal promotion process. i wasn't sure if there should be an additional indicator that the sandbox was a step between the initial approval and the current prep areas, but had only suggested using '0' because it comes before the numbers of the other prep areas, and integrating it into existing code would hopefully be fairly simple. your other suggestions are also fine by me, though if we're going to use the word "pre-preparation", i would also suggest dropping "sandbox" as redundant. dying (talk) 19:11, 28 March 2023 (UTC)[reply]
WP:DYKQ as "pre-preparation area"? theleekycauldron (talkcontribs) (she/her) 19:15, 28 March 2023 (UTC)[reply
]
theleekycauldron, that's fine by me. i am assuming the name "preparation area 0" is being used to make the code easier to implement, while the term "pre-preparation area" is being used to refer to it on wp:dykq to make the use of the new page more clear. perhaps a redirect from "Template:Did you know/Pre-preparation area" to "Template:Did you know/Preparation area 0" would also be helpful.
by the way, i just realized that the set of images used for the numbers on {{DYK queue/navigation}} includes an image for '0', so the new page can easily be integrated into the navigation template if desired. dying (talk) 20:06, 28 March 2023 (UTC)[reply]
I am kind of worried that hooks promoted to the sandbox could linger there for a long time and that this just hides the backlog in yet another place that people have to watch. "Prep sets are always full" seems not a common problem from a five-year perspective, but more a temporary issue. So count me as unconvinced, I guess. (But I'm not very active at DYK these days, mostly because all queues are always full when I want to help...) —Kusma (talk) 20:28, 28 March 2023 (UTC)[reply]
Why is it again that we can't have the number of Queues and Preps expanded to, say, 10 each? Is it simply too complex to expand because of the way everything is interconnected and/or physically impossible under the current setup? Cielquiparle (talk) 20:33, 28 March 2023 (UTC)[reply]
Kusma, given that 1. it's far easier to take a hook out of the sandbox than it is to do the verification work to promote an entirely new nomination, and 2. the sandbox is pretty noticeably placed in the queues, I'm not sure I see that becoming an issue. Cielquiparle, expanding the number of Ps and Qs isn't technically infeasible, but I think it just kicks the can back down the road. theleekycauldron (talkcontribs) (she/her) 20:40, 28 March 2023 (UTC)[reply]
@Theleekycauldron So does that mean that anything in the sandbox has already been verified? Or is it a sandbox where you spend time verifying hooks? Cielquiparle (talk) 20:43, 28 March 2023 (UTC)[reply]
Cielquiparle, it'd be the former – a nomination generally shouldn't be closed unless it's verified. theleekycauldron (talkcontribs) (she/her) 20:49, 28 March 2023 (UTC)[reply]
@Theleekycauldron Is the sandbox then like a long list? We just put hooks in there as they are verified? And then they don't get assembled into prep sets until they make it out of the sandbox? Cielquiparle (talk) 20:53, 28 March 2023 (UTC)[reply]
Cielquiparle, the sandbox is optional – no one is required to put hooks there, they can be promoted directly to prep sets as normal. But yes, it is a long list that preppers can use to store emergency hooks and sort through what's available to use. theleekycauldron (talkcontribs) (she/her) 20:55, 28 March 2023 (UTC)[reply]
@Theleekycauldron Thanks I'm starting to understand a bit better what it is. My question then is what happens when there are multiple "good" hook candidates? I guess the promoter always has the option go open the nomination back up and choose a different hook? Sometimes you choose a different hook based on what is in the set, etc. But sometimes you don't realize the "best" or "only viable" hook was the one that was chosen for a reason. (I'm realizing now that I have to be clearer and more explicit if I'm absolutely ruling out a hook before closing, because otherwise people have questions and/or the wrong one could still get chosen after the fact.) Cielquiparle (talk) 21:01, 28 March 2023 (UTC)[reply]
Cielquiparle, I'm not sure how that problem applies more here than it does to prep sets as normal. The promoter gets to choose a hook, and that about settles it unless someone takes issue post hoc. theleekycauldron (talkcontribs) (she/her) 21:09, 28 March 2023 (UTC)[reply]
We already have a long list at /Approved. I wouldn't want an additional place where hooks can stay for a long time. Having zero to three more prep sets (maximum 24 additional hooks, ideally fewer) sounds much better to me than an unlimited list. —Kusma (talk) 21:20, 28 March 2023 (UTC)[reply]
If that issue crops up during the trial period, we can always can the idea, but I'm fairly sure it won't. theleekycauldron (talkcontribs) (she/her) 21:27, 28 March 2023 (UTC)[reply]
I don't think there is a major technical problem with that (might require a slight update to the bot and a few edits). —Kusma (talk) 20:42, 28 March 2023 (UTC)[reply]

Would the sandbox count against the "at least ten prep/queue sets" mentioned in

WP:DYKROTATE? -- RoySmith (talk) 21:07, 28 March 2023 (UTC)[reply
]

RoySmith, given that the sandbox can't really be "full", and will usually remain near-empty unless the preps get full, I would imagine no... theleekycauldron (talkcontribs) (she/her) 21:08, 28 March 2023 (UTC)[reply]

I assume an arbitrary number of image hooks could be added, and not necessarily at the top?

I don't think it should be called a "sandbox", which is an established name for a place where anybody can play around, doing pretty much anything they want to (as long as it doesn't violate a few rules). MANdARAX • XAЯAbИAM 21:33, 28 March 2023 (UTC)[reply]

multi-image implementation would take a bit of extra PSHAW work, but it's doable – probably as a commented-out bit of wikicode after the hook. theleekycauldron (talkcontribs) (she/her) 21:37, 28 March 2023 (UTC)[reply]
Ugh, no. Whatever we end up with, it needs to be parsable/editable using the standard wikitext parsing tools. Embedding essential information in comments is a non-starter.
I'm getting more and more convinced this is the wrong direction. If we want to have more prep space, just generate more prep sets which are identical to the existing prep sets in structure. Let's not invent yet another kind of thing with its own custom structure and its own custom rules for how to use it. Then the only change that has to happen to tools is to understand that there's more than 7 of them, and everything else just works. -- RoySmith (talk) 13:52, 29 March 2023 (UTC)[reply]
... or we can just only do one image in the sandbox. Or we can be fine with it looking a little rough sometimes. Or we can let the images break up the list. All of those are preferable to creating prep sets willy-nilly – if you create more prep sets, there will simply be an expectation that those prep sets will be filled. That is exactly what happened the last time we created a new prep set, and now we're right back where we started and it didn't help with backlog reduction. It's not a workable solution. This is just a prep set. The only thing that separates from other prep sets is the fact that it doesn't rotate. I can extend the size of any prep set right now, it'd just have to get shrunk back down. theleekycauldron (talkcontribs) (she/her) 18:44, 29 March 2023 (UTC)[reply]
theleekycauldron, i am admittedly not familiar with how you've coded pshaw, but i think handling multiple image hooks per set can be more easily implemented by treating each hook in a set as potentially being an image hook when you are parsing it, and disallowing the moving of a hook if (1) the hook does actually contain an image and (2) the destination slot does not accommodate an image. if you only consider the newline characters at the end of lines that begin with '*' as the delimiters for the hooks, your code should be able to handle more unusual situations, such as editors placing invisible comments above hooks to note requested run dates. dying (talk) 23:59, 1 April 2023 (UTC)[reply]

i feel like there has been some misunderstanding due to the proposal being called a sandbox, when it's simply a new prep area with unlimited capacity that has hooks ready to be scheduled. (this is why i had suggested the name "preparation area 0".) what if, instead, we simply agreed that the last prep area available has unlimited capacity? presumably, administrators would never promote this set so there isn't really any danger of an abnormal number of hooks showing up on the main page. also, whenever a set in a prep area is promoted to the queue, anyone can just move the supernumerary hooks (if there are any) from the formerly last prep area available to the newly cleared prep area. dying (talk) 23:59, 1 April 2023 (UTC)[reply]

April Fool's Day

If we switch to 24-hour cycles at midnight GMT, then would the April Fool's Day set run as Queue 7? And if so, can we just build it, say, in Prep 7 and then have the whole set slotted in to Queue 7 after the fact? Cielquiparle (talk) 15:19, 26 March 2023 (UTC)[reply]

@Bruxton We have to put the April Fool's Day prep set somewhere. Cielquiparle (talk) 18:32, 26 March 2023 (UTC)[reply]
Moved Bruxton (talk) 19:06, 26 March 2023 (UTC)[reply]

I'm not familiar with the April Fool's rules, but Harold H. Piffard (nom) may be appropriate, has a quirky hook. Thanks for checking, Zeete (talk) 14:00, 27 March 2023 (UTC)[reply]

@Zeete: I enjoy that hook and promoted it. I left a question in the nomination about an image caption. Bruxton (talk) 14:46, 27 March 2023 (UTC)[reply]
I certainly read the caption wrong. Nevermind. Bruxton (talk) 14:51, 27 March 2023 (UTC)[reply]
I will review it now. Bruxton (talk) 15:51, 27 March 2023 (UTC)[reply]
  • For another April Fool's Day candidate, I am liking Twelves the monkey...it would probably need a different hook but if you read the article there is SO MUCH POTENTIAL. Cielquiparle (talk) 16:17, 27 March 2023 (UTC)[reply]
It is low hanging fruit. I reviewed it and proposed hooks. The article needs a bit more copyediting as well. Bruxton (talk) 17:17, 27 March 2023 (UTC)[reply]
I just reviewed another which is a possibility: The Beautiful Letdown (NOM). Bruxton (talk) 19:51, 27 March 2023 (UTC)[reply]
@Bruxton I was thinking of proposing a football + baseball mashup (rabbit + Castellanos). I could easily be talked out of it though as the mashup thing is very hard. I will go propose it in the newer nom. Cielquiparle (talk) 21:29, 27 March 2023 (UTC)[reply]
@Cielquiparle: It is up to you, I have to leave the last of the prep to you since I reviewed the candidates. I can check out a hook that you may propose. Bruxton (talk) 21:50, 27 March 2023 (UTC)[reply]
@Bruxton: the hook at Template:Did you know nominations/Charles III, Count of Alençon would seem to be a very good candidate for April Fool's Day. In fact, I would be far less inclined to support the "deliberately misleading" wording of those hooks if they were run on any other day. Cheers  — Amakuru (talk) 22:00, 27 March 2023 (UTC)[reply]
@Amakuru: I may want to move the Wikipedia related quirky hook to another set, what do you think about moving it out @Cielquiparle:? Bruxton (talk) 22:22, 27 March 2023 (UTC)[reply]
@Amakuru: I will probably leave the rest of the set to another promotor. Looks like you stopped that nomination for cause. Coming down to the wire. Bruxton (talk) 22:43, 27 March 2023 (UTC)[reply]
@Bruxton: oh yeah I did stop it... Silly me, because I imagine the points I raised are rather trivial to fix. Would be good to revive it IMHO, unless there are better candidates for AFDay.  — Amakuru (talk) 22:57, 27 March 2023 (UTC)[reply]
@Bruxton Sure... The Wikipedia Covid-19 one is genuinely positive and not a joke – in fact it's a very serious topic – so I'm fine with moving it (and probably coming up with a different hook for it). On another note... Maybe we should ask the DYK admins to leave room for swapping in April Fool's Day set from Prep 7 once we're actually done...? Hopefully tomorrow? Cielquiparle (talk) 23:04, 27 March 2023 (UTC) 22:57, 27 March 2023 (UTC)[reply]
I am with you @Cielquiparle:. I will move that hook to another set! Bruxton (talk) 23:08, 27 March 2023 (UTC)[reply]
@Amakuru That April Fool's Day hook probably only makes sense to British people. But anyway I've pinged the nominator and asked if the issues you flagged can be addressed ASAP. Let's see. Cielquiparle (talk) 13:38, 28 March 2023 (UTC)[reply]

Edge case breaking PSHAW

Per the discussion above, @dying, I believe PSHAW doesn't like upside down. Cielquiparle (talk) 19:34, 26 March 2023 (UTC)[reply]

haha, yeah, Cielquiparle, i wasn't sure how pshaw would handle that. apologies for making you do it manually. (normally, i'd offer to help, but in this case, i'm not allowed to promote my own hook.) thankfully, i believe DYKUpdateBot simply copies everything between the comments to the main page, so hopefully there shouldn't be any issues there. dying (talk) 19:56, 26 March 2023 (UTC)[reply]
@dying It doesn't seem to like it even when you do it manually (just tried and looked at it in Preview) – it flips the image and sends it far left for some reason. Cielquiparle (talk) 20:10, 26 March 2023 (UTC)[reply]
strange, Cielquiparle, previewing seems to work for me. are you copying both the line above and the line below the line with the {{main page image}} template? the line above begins with "<div class", and the line below is "</div>". dying (talk) 20:28, 26 March 2023 (UTC)[reply]
@dying @Mandarax This was my very first time promoting a DYK hook manually, ever. Could you please check to make sure everything is ok now? Thanks in advance.
As a side note: I momentarily managed to turn three whole prep sets upside down on
T:DYK/Q, but I've fixed it now. I accomplished this by using PSHAW to try to slot in a hook above the Mondrian one (because it has added a few extra slots within the tool). Cielquiparle (talk) 06:29, 27 March 2023 (UTC)[reply
]
oh, sorry for causing such havoc, Cielquiparle! it looks like pshaw wasn't expecting the closing div tag. thanks for fixing that.
i only found one minor issue with the closing of the nomination, which i have taken the liberty to correct. (i assume fixing such technical issues isn't considered a conflict of interest, but feel free to revert me if otherwise.) my assumption is that you were emulating how recently closed nominations looked, and weren't aware that you can simply substitute the {{DYKsubpage}} template. (for future reference, the manual instructions are here, though it seems everyone ignores step 2 when closing a nomination nowadays.) the credits in the set of hooks also seemed out of order, so i have sorted them, but please revert me if that was deliberate and pshaw doesn't work properly otherwise.
anyway, everything else looks good. thanks, Cielquiparle! dying (talk) 11:44, 27 March 2023 (UTC)[reply]
I was unable to promote to 7 with PSHAW, so i did so manually. I enjoy the caption on the image, so I am ok with manually promoting. Bruxton (talk) 14:47, 27 March 2023 (UTC)[reply]
thanks, Bruxton. dying (talk) 19:11, 28 March 2023 (UTC)[reply]

Follow-up RFC: Should recreations of articles deleted as copyright violations be allowed to re-run on DYK?

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
There is broad consensus that such articles should be generally excepted from the normal rule against reruns, so long as they would otherwise qualify as "new". Edge cases, such as a rerun after a very short period of time, can be handled
WP:DYKSG rather than the main rules, I will do the same with this consensus, as an amendment to D1. -- Tamzin[cetacean needed] (she|they|xe) 19:53, 4 April 2023 (UTC)[reply
]

Following up on

eligibility criterion 1c (namely "An article is ineligible for DYK if it has previously appeared on the main page as a bold link at DYK.") be added which permits articles previously featured on DYK to be re-eligible if they have been deleted as a copyright violation and recreated? It has been pointed out that discussion above does not indicate a formal consenus, and as such this RfC seeks to more formally assess whether or not there is consensus to modify the criterion. Note that this is only discussing copyright violations and recreations, not broader re-runs, which a different RFC could address. Eddie891 Talk Work 22:39, 27 March 2023 (UTC)[reply
]

Pinging participants in the prior discussions: David Eppstein, Johnbod, Aoidh, Chipmunkdavis, Amakuru, theleekycauldron, Narutolovehinata5, Joseph2302, RoySmith, Cielquiparle. Eddie891 Talk Work 22:39, 27 March 2023 (UTC)[reply]
missed ping: Trainsandotherthings. Eddie891 Talk Work 22:40, 27 March 2023 (UTC)[reply]

Survey

  • Yes per my reasoning above, namely: since the article has been deleted and completely rewritten in this case, it should be considered a new article and we want to be encouraging such re-writing. Eddie891 Talk Work 22:39, 27 March 2023 (UTC)[reply]
  • Yes, provided some time has passed and it's not the same creator. Different article, by a different author, and long enough ago that few people will remember the topic running before. ~
    problem solving 22:42, 27 March 2023 (UTC)[reply
    ]
  • Per my comments above, there should be a general understanding that all article that have been deleted were deleted, and new article are not the same article and thus cannot have a DYK rerun. Articles are not their title. CMD (talk) 22:44, 27 March 2023 (UTC)[reply]
    That's rubbish. If the DYK is on the same topic then it's a repeat. The same would apply if an article was moved, so your "title" argument isn't what we're discussing here.  — Amakuru (talk) 22:46, 27 March 2023 (UTC)[reply]
    A moved article is the same article with the same history. A new article is not. CMD (talk) 01:15, 28 March 2023 (UTC)[reply]
  • No. This was argued at great length in the RFC earlier this year, and certainly I agree that we should be "encouraging re-writing", but that applies to any article which is 5x expanded from an earlier DYK or promoted to GA with substantial new content. But the community rejected that, and we remained with the strict rule that DYKs can not be re-run. Either we stick to that, or we revisit and allow re-runs across a wide spectrum, making it fair for all content creators. There shouldn't be niche exceptions like this.  — Amakuru (talk) 22:45, 27 March 2023 (UTC)[reply]
    @Amakuru: Do you have a link to this RfC? I apologize if it's already been linked, I can't find a link on this talk page nor can I find the RfC itself, unless it's this one from late last year. - Aoidh (talk) 03:24, 28 March 2023 (UTC)[reply]
    @Amakuru and Aoidh: The RfC can be found at Follow-up RfC: for articles previously featured as bolded links on the Main Page, how long should it be before they are eligible for DYK?. I do want to point out that it's incorrect to say that the community rejected the possibility of repeat DYKs: as I remark in my close, there was no consensus on the proposal. Being against niche exceptions is valid, but I would myself say that a viable compromise in a narrower field is a good way to deal with a lack of consensus on a broader question. theleekycauldron (talkcontribs) (she/her) 06:06, 28 March 2023 (UTC)[reply]
  • Yes. If somebody re-creates an article from scratch after that article was deleted due to pervasive copyright violations in the deleted version, it would only make sense for them to be able to DYK it. Using DYK as something that serves as an encouragement to re-create articles deleted for copyright violations seems like a way to encourage people to write encyclopedic content. And, isn't that the whole point of DYK? — Red-tailed hawk (nest) 22:52, 27 March 2023 (UTC)[reply]
  • No per Amakuru. If the point was to encourage people to write encyclopedic content, we should allow reruns for those old (pre-2010), awfully written, short DYK articles too as they certainly have room for expansion and improvements. BorgQueen (talk) 23:14, 27 March 2023 (UTC)[reply]
  • I'm on the fence in this one, but I think it should be done on a case-by-case basis. The example scenario being done here is a bit of an edge case and, apart from Doug's articles, are theoretically very rare, and I don't know if it would be worth it to ban them entirely considering how rare they are. On the other hand, as much as I am sympathetic towards DYK reruns, it really depends on the circumstances and I don't think we should encourage reruns too soon after their initial run. Narutolovehinata5 (talk · contributions) 23:27, 27 March 2023 (UTC)[reply]
  • Yes, with the caveat that attempts to game this will be frowned upon (though it would be quite hard to game, I'd imagine). I'd also like it to be a rule that you can't use the same hook as the original DYK. I realize the impetus for this is likely the Coldwelling, and this is an egregious example where most of the DYKs he ran were garbage or outright fabrications, but unfortunately I'm certain this will come up again in the future. If someone is rewriting an article from scratch after it was deleted for copyvio, I cannot see any reason to exclude that from DYK. Trainsandotherthings (talk) 23:41, 27 March 2023 (UTC)[reply]
  • I was pinged, so I guess I should respond. I kind of feel that we've got enough good submissions that we don't need to be carving out exceptions to allow more, but I don't really have any strong opinion either way. -- RoySmith (talk) 00:32, 28 March 2023 (UTC)[reply]
  • Yes. Specifically, I'd support adding something to
    eligibility criterion 1c, articles that have been recreated after having been deleted for copyvio are eligible, even if they had run as a bold link at DYK before deletion. DYK participants are less likely to support using this exception if the last DYK run was recent or if the nominator is the same as the previous run." I don't think this is going to be a common enough exception that it'd be worth cluttering up DYKCRIT. Firefangledfeathers (talk / contribs) 01:25, 28 March 2023 (UTC)[reply
    ]
  • Yes per my comments in the previous discussion. I don't think this will happen very often, & I don't think gaming is a risk. In the Lithophane case the "gap" would be 15 years - if it were say 2 I can understand there might be objections. It should always be said in the nom (when known - I didn't know about Lithophane, as the page was deleted) & probably brought here. Johnbod (talk) 03:42, 28 March 2023 (UTC)[reply]
  • Neutral for the moment. I wasn't clear on what you were referring to ... until the names Billy Hathorn and Coldwell were mentioned. I haven't followed the Coldwell chronicles in detail, but I sure have vivid memories of Hathorn - he was unique. I see Hathron was blocked from Wikipedia in 2015, but was still active at Commons into 2019. With Billy Hathorn as an example, I probably wouldn't object if an article of his was completely re-written and nominated. We probably shouldn't dismiss a subject matter revived and done correctly ... as long as it has nothing to do with who messed up on the original. — Maile (talk) 04:08, 28 March 2023 (UTC)[reply]
  • Sure, why not. RoySmith makes a good point on repeats not really being needed for DYK's output, and I do hear Amakuru's point that maybe this gets a bit too much into the rules creep. For me, I think the encouragement to clean up these messes outweighs those concerns – I don't think it cheapens the value of a DYK credit to encourage more work. I'm also pretty okay with an exception not being made, but I am strongly opposed to any mandate for case-by-case handling, as that's bound to just cause unnecessary clutter. A clear guideline is more important than getting every single case right. theleekycauldron (talkcontribs) (she/her) 06:10, 28 March 2023 (UTC)[reply]
  • Yes. It doesn't matter why a past DYK article was deleted. If an article got deleted, presumably for a valid reason, and later gets recreated and resubmitted for DYK, it should be treated as a new article. I imagine this will happen very rarely, so it's not worth overengineering a complicated set of rules; nor does it make sense to enforce the "no DYK repeats" rule with such rigidity that it requires hundreds of hours of editor time wasted on verifying whether or not each and every "new" article submitted for DYK might have had a past life, not to mention the uneven playing field for non-admins and non-DYK regulars who may not be privy to such information. (Imagine you are a relative newcomer to Wikipedia, create a new article or take it to GA, then submit it to DYK, only to learn through the DYK process that it was in fact a previously deleted article that had appeared as a DYK ten years prior.) Keep the rules simple and easy to follow; don't waste editor time on unproductive "enforcement". Cielquiparle (talk) 11:08, 28 March 2023 (UTC)[reply]
  • Yes if an article is deleted as a copyvio and a new article written, that article is new and meets all the new article criteria. And exceptions for copyvios are consistent with how we calculate 5x expansions on DYK. Joseph2302 (talk) 11:11, 28 March 2023 (UTC)[reply]
  • Yes. Trainsandotherthings left me a note on my talk page about this RFC. In all honesty, I was going to go the exact route Maile66 pictured, and rewrite some of the Hathorn articles that were presumptively deleted, especially since I'm involved at CCI and I clean up a lot of this...questionable content. (Half the challenge is finding something that has RS and is clearly notable in that trainwreck of a CCI). @Narutolovehinata5: The Doug Coldwell ones in particular are the most recent. Much of the "ran at DYK" articles were created or expanded before 2020 I would say, so there's not a super large risk of one running in <3 years of its first DYK unless it's DC. Rewrites on the CCIs with massive amounts of presumptive deletions are almost always done by people not involved in the CCI, because most of the subjects are blocked as well. Sennecaster (Chat) 19:41, 28 March 2023 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Wording of Matar judíos hook

Matar judíos means "killing Jews" – this is explained in the article – but can we really run it like this in the hook? Thoughts and suggestions welcome, preferably directly in the nomination template: Template:Did you know nominations/Matar judíos Cielquiparle (talk) 12:53, 28 March 2023 (UTC)[reply]

I passed it over because it may be too provocative. Bruxton (talk) 15:44, 28 March 2023 (UTC)[reply]
OK I've marked it as requiring more work and/or discussion on the hook. Cielquiparle (talk) 15:52, 28 March 2023 (UTC)[reply]

Seeking military history fan...

...to please read the latest version of Buchanan's Station. Perhaps @Hawkeye7 or @Hog Farm could take a fresh look (as the article has changed significantly since you first looked at it), or perhaps we have another military history or American history buff in the house who could please take a look and then review/approve the DYK nom? I promise it is worth a read. Thanks in advance. Cielquiparle (talk) 13:58, 28 March 2023 (UTC)[reply]

I'll take a look on my lunch break. Hog Farm Talk 13:58, 28 March 2023 (UTC)[reply]
I have taken a quick glance at the article, checking neutrality only. I am concerned at the repetition of "Indian(s)", outside the context of quotations or article titles. In many cases, that word could be replaced by "warrior" or tribal names, or something else which may be considered acceptable. There is also the phrase "Native American". As an outsider myself, I would not presume to use those terms, so could you please either change those terms in the article, or let me know your grounds for using those terms in a WP article? This is not a complaint or political activism on my part, it just looks to me as if the article gives a voice to the white pioneers only, and that the warrior tribes do not have enough of a balancing voice in this? What initially hit me in this article, was the phrase "successfully repelled" (instead of just "repelled") in the lead: That expression sounds like the voice of the white-hat pioneer hero in the old black and white films. In those films, we never heard the voice of those hundreds of incredibly skilled riders and stuntmen who rode bareback and barefoot. Those are the actors I remember. Are we re-writing history by leaving out their voices? If we at least name their nations considerately, that would be a start. Storye book (talk) 16:39, 28 March 2023 (UTC)[reply]
@Storye book: - I don't think there's any major concerns with "Native Americans" given that's what American schoolchildren are generally taught to use, although I'd advise against using "Indians" in articles, except for specific terms like "Indian Territory" or "Indian agent". And as to the names of the warriors, that frankly often isn't recorded in existing sources. Keep in mind the Cherokee syllabary didn't exist at the time of the battle. The sourcing is by nature going to be limited in some areas for these topics. Hog Farm Talk 16:51, 28 March 2023 (UTC)[reply]
@Storye book Regarding how to refer to Native Americans: It's very complicated and I could fill up pages, but basically there is no simple answer to any of this, nor any single term that will make everyone happy. One of the best concise explanations I have seen was written by @Kevin1776 and is available here: Talk:Tecumseh#Rewrite in progress
Regarding the wording you suggested, we even argue about the appropriateness of the term "warrior" which conjures Western stereotypes of Native Americans. (Why not just call everyone "soldier"?) That said, I would just ask that you actually sit down and take the time to read the entire article very carefully. I spent a ton of time and took great pains to try to make this a balanced article explaining the complexity of relationships between all the different actors and interests, because I wasn't entirely convinced or comfortable with the previous version. I will also try to look at it "fresh" to see if there is more than I can fix.
(Your feedback about the hook is noted. Maybe it's a good argument for throwing out that hook.)
I generally try very hard not to use the word "Indian" but in this case, there were a few instances where "Native American" was going to be an awkward substitute, and this was a complicated story involving three different tribal affiliations, and sometimes you did not know which one was where. As Kevin1776 points out, in those instances, there is a school that says to go ahead with "Natives" but I think that has plenty of potential to offend as well. Meanwhile there are also communities of Native Americans that claim "Indian" as an identity preferable to NA – e.g. Indian Country Today, etc. But I will have another look and see if there are places where I can remove it without confusing things. Cielquiparle (talk) 17:05, 28 March 2023 (UTC)[reply]
(Edit conflict. I had written:} OK, though I'd better make clear that I wasn't asking for the names of the warriors - just the names of their nations. Presumably there was a limited number of nations involved in this bit of history? I accept that the sources are limited, but when paraphrasing we must interpret the wordage of those sources in a manner respectful to all. You say that you advise against using "Indians" as a single word, so could we please have examples of that usage removed and replaced? Thank you. (Update after edit conflict): Thank you, for your answers. You know best. Good luck. Storye book (talk) 17:15, 28 March 2023 (UTC)[reply]

Earwig

Appears to be down, as I cannot check this nomination. Bruxton (talk) 15:43, 28 March 2023 (UTC)[reply]

There was some routine maintenance earlier today which apparently had some unexpected consequences. Lots of tools are down. It's being discussed on IRC #wikimedia-cloud. -- RoySmith (talk) 16:00, 28 March 2023 (UTC)[reply]
Actually, it looks like it just got fixed a few minutes ago. -- RoySmith (talk) 16:03, 28 March 2023 (UTC)[reply]
Looks to be back up, I got Violation Unlikely 8.3%. My question was more with the sourcing, specifically with the niche blogs given that it's a BLP (Jews in the City etc.) but am leaning toward it's probably ok...? Cielquiparle (talk) 16:03, 28 March 2023 (UTC)[reply]
I added several other references to the article before promotion. Bruxton (talk) 20:02, 28 March 2023 (UTC)[reply]
@
WP:BLPSPS standpoint but I guess Jew in the City for example isn't "self published" in the sense that there's a rather large nonprofit organization with staff behind it. (So yes, technically it's a blog, and it's not exactly a news organization, but it's also not self-published in the sense of a lone ranger publishing whatever with no oversight.) Cielquiparle (talk) 20:41, 28 March 2023 (UTC)[reply
]

Correcting a nomination

I can't easily see how to correct a nomination after posting. Could someone kindly look at Template:Did you know nominations/Testimonies (novel) for me, please? There should be one hook, with the source text included. I think it needs to be edited above the words "Please do not edit above this line". Many thanks. MichaelMaggs (talk) 17:28, 28 March 2023 (UTC)[reply]

Hmm, not sure what happened there, but I'll fix it up. -- RoySmith (talk) 17:37, 28 March 2023 (UTC)[reply]
Many thanks! MichaelMaggs (talk) 17:38, 28 March 2023 (UTC)[reply]
Looks like some kind of copy-paste snafu. Not to worry, these things happen. Thanks for your submission. -- RoySmith (talk) 17:45, 28 March 2023 (UTC)[reply]

Are we stuck?

Prep area says: Last updated: 25 hours ago... Bruxton (talk) 01:07, 29 March 2023 (UTC)[reply]

Pinging Shubinator, DYKUpdateBot appears to be down. theleekycauldron (talkcontribs) (she/her) 01:12, 29 March 2023 (UTC)[reply]
Also pinging the DYK admins for a manual update. theleekycauldron (talkcontribs) (she/her) 02:17, 29 March 2023 (UTC)[reply]
I've done that twice already this year lol. I'll leave it to someone else... BorgQueen (talk) 02:20, 29 March 2023 (UTC)[reply]
I was wondering about that. I'm happy to manually do so, but if I'm going to be the one doing it (I've obviously never done it before) I'd need the "how to" broken down barney style for me. - Aoidh (talk) 02:22, 29 March 2023 (UTC)[reply]
@Aoidh It's the "Manually posting the new update (if the bot is down)" section at the bottom of every queue template. Every time I've looked at it, I've run away screaming in the other direction. Have fun! -- RoySmith (talk) 02:33, 29 March 2023 (UTC)[reply]
 Done Please feel free to double-check what I did, but I followed the instructions exactly and everything should be handled now. - Aoidh (talk) 02:52, 29 March 2023 (UTC)[reply]
You're a better man than I -- RoySmith (talk) 03:08, 29 March 2023 (UTC)[reply]
Thanks for being Johnny on the spot. @Aoidh: Bruxton (talk) 03:15, 29 March 2023 (UTC)[reply]
Both bots are back online :) From the logs, both were unable to access Wikipedia's API (unclear if the issue was on the bot side, with Toolserver, or with Wikipedia), and after 22 minutes of retries, both bots gave up. Thanks BlueMoonset for the talk page ping, and Aoidh for the manual update. Overall the manual update looks solid! It was missing the article talk page credits though (when updating manually, it's the "tag" button on the credit template), I've gone ahead and issued the article talk page credits by script. Everything should be back to normal :) Shubinator (talk) 11:27, 29 March 2023 (UTC)[reply]
Is there a way somebody else can see the status of the bot and restart it? It's really not good for an essential process like this to have a
bus number of 1. -- RoySmith (talk) 13:47, 29 March 2023 (UTC)[reply
]
Yep it's possible to see whether the bot processes are running, see the link at the Kubernetes migration update. Restarting it is currently only possible by me; it's possible to onboard another admin with technical know-how to be able to restart it, not sure if this is worth it though - the bot is designed to fail closed, and spamming restarts erodes this design choice. Also, in my opinion, rare manual updates aren't a bad thing, as they help admins understand how the updates work, and ensure the community is not 100% reliant on the bot. Shubinator (talk) 14:13, 29 March 2023 (UTC)[reply]
I disagree that manual updates are a good thing. They lead to increased delays, increased workload and stress for admins, and a greater chance of something going wrong. -- RoySmith (talk) 14:28, 29 March 2023 (UTC)[reply]
Let's chip away at reducing the difficulty of manual updates then :) For example, who can update the manual update instructions to make it clearer that credits should be distributed to both user talk pages and article talk pages? Shubinator (talk) 14:42, 29 March 2023 (UTC)[reply]
@Shubinator: would modifying PSHAW to include a "to Main Page" option help, or do most of the breaks that kill the bot end up killing a user script as well? theleekycauldron (talkcontribs) (she/her) 18:10, 29 March 2023 (UTC)[reply]
My sense is this would exacerbate the problem we're trying to avoid, of over-reliance on one or two people. Shubinator (talk) 19:55, 29 March 2023 (UTC)[reply]

Prep 7 April Fool's Day edition

We now have a complete April Fool's Day set in Prep 7. (Famous last words.) Thanks to everyone who provided hooks. Quite frankly, I was surprised we didn't have more hooks "banked" for this year – but we did what we could and all the suggestions were very helpful. Hopefully if it looks ok, it can get promoted to Queue 7 after midnight? Cielquiparle (talk) 06:29, 29 March 2023 (UTC)[reply]

So it needs to go where Queue 7 currently sits, correct? That's what I'm seeing on Template:Did you know/Queue#Local update times. What's the best way to shuffle around those Queues, because the April Fool's Day set needs to replace what's currently in Queue 7. I could bump everything down by one queue so that what's currently at Queue 7 would go to Queue 1, and 1 to 2 and so on. Is that the best way to handle that? The only issue I see is that every set would have to be shifted down one, even the preps. There's got to be a better way to do that? - Aoidh (talk) 07:56, 29 March 2023 (UTC)[reply]
@Aoidh I was thinking you wait until midnight (1 am BST) until Queue 5 is free, then move the current Queue 7 to Queue 5, and slot in Prep 7 to Queue 7. Of course, I'm not an admin, but that's what I would do if I had a fox, a chicken, and a bag of grain. (Or, does it not actually work that way, and you can only shift things by one?) Cielquiparle (talk) 08:09, 29 March 2023 (UTC)[reply]
@Cielquiparle: I don't know, because if I just move 7 to 5, we'd have a Queue 5 and also a Prep 5, and I'm not sure if that would mess things up (like with PSHAW for example); up to this point every time I've moved a prep to queue it's been the prep number to the corresponding queue number. I'm sure I'm overthinking this and there's an easier way to do it though. Maybe I could just shift Queue 7 to 5, and then Prep 5 to 3 or something I'm not sure. - Aoidh (talk) 08:13, 29 March 2023 (UTC)[reply]
@Aoidh Or simply drop Queue 7 to Prep 3? Pinging @BorgQueen for input. Cielquiparle (talk) 08:37, 29 March 2023 (UTC)[reply]
Why not just swap the two sets: Queue 7 to Prep 7 and Prep 7 to Queue 7? An extra edit window can hold one of the sets if necessary during the swap. BlueMoonset (talk) 15:20, 29 March 2023 (UTC)[reply]
Are there another special date hooks interfering with the switch? Only one switch would be ok, though.
talk) 15:52, 29 March 2023 (UTC)[reply
]
 Done I've switched Prep 7 and Queue 7 so that the April Fool's Day set is in Queue 7 and will run on April 1. I did check and didn't see anything in the set I moved out of queue that requested any sort of special date or anything so I think it should be good to go in that respect. - Aoidh (talk) 20:30, 29 March 2023 (UTC)[reply]

Introduction of error into hook

So this is fun. The original hook

Was approved. Then @UndercoverClassicist and @DigitalIceAge decided to change it, not bothering to, oh, say, ping the nominator. Or apparently to read the article. Which resulted in the promotion of a factually incorrect hook. Which now has caused this lovely mess. Can someone please just change back to the originally approved hook? Valereee (talk) 16:01, 29 March 2023 (UTC)[reply]

In my defense, I only changed the wording from UndercoverClassicist's hook to avoid using gerunds (murdering and dismembering → the murder and dismemberment). DigitalIceAge (talk) 16:21, 29 March 2023 (UTC)[reply]
I need to put my hands up for that one: I'd (wrongly) assumed that simply replying would ping the nominator, and I inadvertently introduced the factual error. UndercoverClassicist (talk) 17:12, 29 March 2023 (UTC)[reply]
My apologies, both, I was unnecessarily snippy. :) I was rushing out of the house and didn't have time to rein myself in. Valereee (talk) 17:14, 29 March 2023 (UTC)[reply]
No problem. I should've caught the error at the time, but as the case was particulary gruesome my eyes must've glazed over that detail. DigitalIceAge (talk) 18:11, 29 March 2023 (UTC)[reply]
Thanks for being understanding about me being snippy. :) Next time just ping the nom. I'd seen that the hook was approved and hadn't realized there was discussion happening afterward. Valereee (talk) 18:15, 29 March 2023 (UTC)[reply]
Insert {{group hug emoji}} here.
-- RoySmith (talk) 20:35, 29 March 2023 (UTC)[reply]

Would an 18-hour rotation be useful?

Over the last ~15 months (per [1]), DYK has been on a 24-hour rotation about 58% of the time, and a 12-hour rotation the rest of the time. That implies that, on average, a 19-hour cycle (12 + 0.58*12) would very closely match the rate at which DYK hooks are approved. Over the same period, the DYK rotation period has been changed between 12 and 24 hours every 21 days on average, effectively maintaining this 19-hour average.

Now, 19 hours is awkward, but 18 hours could work well – it's four sets every three days, with four times of day that rotations can possibly occur (vs. one or two now). In the past, the rotation has been set to 6 or 8 hours, so this is not new ground, except that some sets will cross from one day to the next (which they already do for everyone not on UTC).

I see two advantages to this: 1) By using a rotation that closely matches the hook approval rate, it should be possible to go far longer between adjustments to the rotation rate – it may even be possible to never change the rotation rate, and just modulate the number of hooks per set ±1 to keep the number of approved hooks within bounds. 2) Hooks would be treated more equally, in terms of waiting time to get the main page, and display time once there.

Thoughts? —

bad idea 17:41, 29 March 2023 (UTC)[reply
]

This has been discussed before. I can't find it in the archives, but I'm pretty sure there was an extended thread about this within the past couple of months. The general consensus is that it makes things too complicated when the rotation interval doesn't divide a day into equal parts. It becomes harder to think about which queue a scheduled special event hook should go into, and also makes computing historical statistics messier. -- RoySmith (talk) 17:51, 29 March 2023 (UTC)[reply]
It would be much simpler to simply do 2-a-days with sets of six instead of eight. That would produce the same average number of hooks over time as an 18-hour rotation of sets of eight. Valereee (talk) 18:19, 29 March 2023 (UTC)[reply]
damn, i never thought of that, that's clever! Removing two hooks from every prep and queue would be absolutely nuts without an interim place to store a large number of hooks, though. theleekycauldron (talkcontribs) (she/her) 20:42, 29 March 2023 (UTC)[reply]
The problem is that six hooks would be far too short a set to balance OTD and ITN on the other side of the page. The left side where we are is shorter today, even with eight hooks. (When I started, six or seven hooks per set was the norm, with two or three sets per day, but we get fewer hooks now, and OTD and ITN were both shorter back then.) As noted above, having a daily midnight switchover is preferable for a number of reasons. BlueMoonset (talk) 21:53, 29 March 2023 (UTC)[reply]
There's little hassle swapping between 12 and 24-hour rotations. You change a number on one page sometime after midnight UTC and that's it. Sometimes, a time-sensitive hook then needs to be go into a different prep or queue, and that's also easily done. Schwede66 06:06, 30 March 2023 (UTC)[reply]
@BlueMoonset, just a thought for length on the page...would increasing the size of the image and/or relaxing the single-sentence expectation/max length be helpful? (In general I think 200 is a good limit just for readability of a single sentence, but there are often hooks that could be longer, including by being more accepting of multiple sentences.) Valereee (talk) 12:12, 30 March 2023 (UTC)[reply]
I'm gonna be honest: does anyone actually even care about Main Page balance? Like if certain parts are too long or too short, does anyone even notice? Or is this one of those things that editors care more about than actual readers? Narutolovehinata5 (talk · contributions) 12:14, 30 March 2023 (UTC)[reply]
Good to see the return of the 18 hour suggestion, as the way to actually fix things with much less effort than continually flipping between 12 and 24 hours. I support this same as all the other times it's been suggested. Joseph2302 (talk) 12:45, 30 March 2023 (UTC)[reply]
We really need to gather these discussions somewhere. The relative logistical issues for the people actually doing the work have been explained multiple times. Valereee (talk) 13:00, 30 March 2023 (UTC)[reply]
I've said it before, "main page balance" is a problem that we force on ourselves for no good reason and then complain about how it means we can't do other things. JUST MAKE THE MAIN PAGE A SINGLE COLUMN. Issue immediately goes away, never to teturn, and sections on the Main Page can be whatever length is most appropriate for the material available. You know, just like virtually every other page.--User:Khajidha (talk) (contributions) 20:19, 31 March 2023 (UTC)[reply]
@Valereee I suppose it's a matter of taste, but I much prefer shorter hooks. I think most of our hooks are too wordy, with people trying to cram everything in. Also, as somebody who learned layout back in the xacto-knife and glue-stick days, the extra white space we leave at the bottom of the box bothers me. Maybe we should be running a variable number of hooks per day. If people get verbose, we only have room for 8. But if we tend pithier on a given day, we could do 9 or 10 and fill the box. On the other hand, I could see that creating a whole new set of challenges for prep-set builders, so maybe not a great idea. -- RoySmith (talk) 13:43, 30 March 2023 (UTC)[reply]
This is like the Goldilocks principle. Most prep builders might agree that two sets a day is an onerous schedule. But one set a day is like watching paint dry. Maybe 18 hours would be just right; the only way to know would be to try it. Bruxton (talk) 16:50, 30 March 2023 (UTC)[reply]
Two sets of six every 12 hours vs. one set of 8 every 18 comes out to the same number of promotions required per day. The impact on promoters is the same. Valereee (talk) 17:18, 30 March 2023 (UTC)[reply]
I think you mean 9 every 18 hours? That makes it the same as 6 every 12, but it also exceeds the current promotion rate. —
bad idea 20:11, 30 March 2023 (UTC)[reply
]
Each hook gets 18 hours, that is the difference for me. Bruxton (talk) 17:22, 30 March 2023 (UTC)[reply]
Well, but each hook also gets to be one of only six...? Valereee (talk) 17:28, 30 March 2023 (UTC)[reply]
I think the same sets, 8 hooks, 18 hours. But I am ok with whatever is decided. Bruxton (talk) 17:49, 30 March 2023 (UTC)[reply]
I guess I'm just afraid it would be chaotic. Maybe a test run? Valereee (talk) 17:52, 30 March 2023 (UTC)[reply]
A test run could be good, and we could clearly document everything we learn from it, so that we can put the question to rest if it doesn't work. I agree with Bruxton that the difference between 12 hours and 24 hours feels extreme. Cielquiparle (talk) 19:17, 30 March 2023 (UTC)[reply]
Would it take any more work to set up a test run than the normal switch from 1 to 2 a day? Valereee (talk) 19:32, 30 March 2023 (UTC)[reply]
You don't need to remove any hooks from the queues that are already finished, just put only six into prep sets from that day. (It doesn't matter if there are a few 12-hour 8-slot sets or a few 24-hour 6-slot sets). —Kusma (talk) 17:04, 30 March 2023 (UTC)[reply]
@
bad idea 20:23, 30 March 2023 (UTC)[reply
]
I don't know exactly what is the process for getting the main page layout to change, but I suspect the level of bureaucracy it would involve would put to shame anything we could generate here at WT:DYK :-) -- RoySmith (talk) 20:26, 30 March 2023 (UTC)[reply]
Not something we can handle here. Likelihood of success: nil. Valereee (talk) 20:27, 30 March 2023 (UTC)[reply]
Suppose for a moment it were possible. Would it help? And then, where would one raise such a suggestion? —
mutual 20:29, 30 March 2023 (UTC)[reply
]
Redesigning the MP to make the space taken up by each project flexible would certainly reduce objections here to white space issues. It would best be broached at Talk:Main Page to start, I'd think. Valereee (talk) 20:37, 30 March 2023 (UTC)[reply]

Desert

Not sure what to do with Template:Did you know nominations/Desert of Maine. The participants have not returned to the nomination for more than one month despite pings. Other editor involvement included editing the article and proposing hooks. Can someone just adopt the approval process or should we mark for closure? Bruxton (talk) 17:46, 29 March 2023 (UTC)[reply]

IMHO, the nominator has a duty to remain engaged with the process. I would close it as rejected. It's not like we're struggling to find enough good nominations that we need to babysit things when a nominator walks away. -- RoySmith (talk) 17:54, 29 March 2023 (UTC)[reply]
@AverageEstoniaEnthusiast is currently editing. Valereee (talk) 18:16, 29 March 2023 (UTC)[reply]
@Valereee: I am hoping they can approve a hook, because it is ready. Bruxton (talk) 18:25, 29 March 2023 (UTC)[reply]
All is well that ends well I was worried that I was too demanding in the nomination. They approved on their talk page and I promoted. Bruxton (talk) 18:37, 29 March 2023 (UTC)[reply]

BRAAAM

@Ravenpuff: Regarding this, the longer caption was inspired by a conversation with Theleekycauldron where they mentioned that sounds don't typically get the engagement that pictures do. Since there are sources which acknowledge variation in the spelling (e.g. the number of As), I made the caption longer to maximize interest/attention. Content to defer to others regarding whether this creates a policy problem (it doesn't strike me that it takes more liberties with representing the sources than, say, the April Fools hooks). FWIW. — Rhododendrites talk \\ 20:27, 29 March 2023 (UTC)[reply]

That's fair enough. However I think that this one might just be quirky enough that it might get substantial engagement anyway. Also, I'm not sure how much lengthening the audio caption might increase engagement by (I reckon that the main reason is that it won't as eye-catching as an image). But I'm happy to leave the decision to consensus. — RAVENPVFF · talk · 20:50, 29 March 2023 (UTC)[reply]
Yes, I am fond of the hook, article and sound file. I preferred the original exaggerated caption. I am sure readers will make the connection. Bruxton (talk) 20:51, 29 March 2023 (UTC)[reply]
I've restored the longerrrrr caption. BorgQueen (talk) 21:03, 29 March 2023 (UTC)[reply]
Agreeeed. Schwede66 06:08, 30 March 2023 (UTC)[reply]
maaarbelous. dying (talk) 23:59, 1 April 2023 (UTC)[reply]
noice! theleeeeeekycauldron (talkcontribs) (she/her) 04:01, 2 April 2023 (UTC)[reply]
I'm not liking this hook much at all. I think the original ALT0 was better, but why not the even shorter
ALT2: ... that the origin of BRAAAM (featured) is disputed?
with the audio player right there, it'll be obvious we're talking about a sound and it's a lot easier to read. -- RoySmith (talk) 20:33, 3 April 2023 (UTC)[reply]

Scheduled tools downtime next week

There's two periods of scheduled toolforge downtime next week. This means most tools and bots will be down. Details were sent to the cloud-announce mailing list (see message archive for details). The expected downtime windows include most of the day on Monday, and about an hour on Thursday.

This will impact lots of DYK things. I'm guessing the April 3 0000Z main page update will fail, depending on exactly when they start taking things out of service. We'll certainly want to keep an eye on things. -- RoySmith (talk) 21:29, 29 March 2023 (UTC)[reply]

Pinging Shubinator, since it's his bots that will be affected. Not sure whether it will also affect WugBot (Wugapodes), but also pinging just in case. BlueMoonset (talk) 21:57, 29 March 2023 (UTC)[reply]
WugBot might be fine but either way it should restart gracefully whenever things come back online. It doesn't do much writing to disk so it depends on the specifics of the shutdown. Wug·a·po·des 22:30, 29 March 2023 (UTC)[reply]
Good to know, will try to be online around then. I can run either bot from another computer temporarily. Shubinator (talk) 13:39, 30 March 2023 (UTC)[reply]
Reminder: this is starting in a few minutes. -- RoySmith (talk) 23:51, 2 April 2023 (UTC)[reply]

Process of moving a hook to special occasions slot

It's been awhile since I had a special occasions request, and the DYK reviewer for Template:Did you know nominations/William Y. Slack recommended a special occasions date of April 17. Am I allowed to move it over to that holding area myself, or does that need an independent party? Hog Farm Talk 13:53, 31 March 2023 (UTC)[reply]

Anyone can do it, except I'm not sure if the nominator is allowed to do so. In any case, there has to be agreement from the reviewer first. Narutolovehinata5 (talk · contributions) 15:19, 31 March 2023 (UTC)[reply]
Is agreement from the reviewer actually a rule? I don't see it anywhere in
WP:DYKSG. -- RoySmith (talk) 15:46, 31 March 2023 (UTC)[reply
]
I moved it to April 17 Special Holding for you. Looked through the rules and don't see anything about this. I think it's OK as long as the date of special holding was agreed on the review or here at the talk page. I don't know of any discussion about such a rule one way or the other. — Maile (talk) 16:22, 31 March 2023 (UTC)[reply]
RoySmith, this is from Wikipedia:Did you know#Date requests: The proposed occasion must be deemed sufficiently special by reviewers. theleekycauldron (talkcontribs) (she/her) 19:16, 31 March 2023 (UTC)[reply]
Ah. I was looking at the fine print. I should have been looking at the big type on the front of the box :-) -- RoySmith (talk) 19:26, 31 March 2023 (UTC)[reply]
@Hog Farm, FFR, you can just ask your reviewer if they'd please move it so it doesn't get overlooked. Valereee (talk) 14:36, 1 April 2023 (UTC)[reply]

Self promotion allowed???

WP:DYKSG#Rules of thumb for preparing updates says Promoting your own articles is generally discouraged. Is there any situation where it's considered acceptable? Would anybody object if I changed that to say it was prohibited? -- RoySmith (talk) 15:48, 31 March 2023 (UTC)[reply
]

More precisely: Promoting articles you have nominated, perhaps? No one actually owns the article per
WP:OWN. Cielquiparle (talk) 16:29, 31 March 2023 (UTC)[reply
]
no, that'd be a reasonable reflection of standard practice. I'd say go ahead and change it. theleekycauldron (talkcontribs) (she/her) 16:59, 31 March 2023 (UTC)[reply]
I can't think of a case when it would be needed or appropriate, hence "prohibited" is better than "discouraged". Schwede66 18:26, 31 March 2023 (UTC)[reply]
Like Roy and Schwede I can't think of a case where it would be needed or appropriate. Valereee (talk) 20:29, 31 March 2023 (UTC)[reply]
I could see it as being reasonable if there are no other admins who are active to move from P to Q. Granted,
nothing is prohibited if there is a good reason to ignore the prohibition, but I do think that hedging a bit is better for handling edge cases. — Red-tailed hawk (nest) 23:59, 31 March 2023 (UTC)[reply
]
That's a different issue, though. I think it's okay for an admin to move to queue a set that contains an article they nominated or reviewed, particularly if the queues are nearly empty. An admin who is a frequent nominator could theoretically have a hard time avoiding that occasionally. But there's no real need for anyone to be promoting to prep an article they nominated or reviewed. Any editor can do that, and there's no time urgency to it. Valereee (talk) 09:04, 1 April 2023 (UTC)[reply]
The real question is: Does this mean we're no longer saying it's a "no-no"? Cielquiparle (talk) 09:44, 1 April 2023 (UTC)[reply]

alt1q: to not promote / a hook you wrote, / it's no no-no!

dying (talk) 23:59, 1 April 2023 (UTC)[reply]
  • I've updated the rules. When I looked at it again, it turned out that J1 already said what I wanted it to say, so I just deleted the extra text from the intro. -- RoySmith (talk) 14:33, 1 April 2023 (UTC)[reply]

Queue 6

I have a few questions regarding Queue 6, which is almost a bit too good for my taste:

  • the lead image is an allegory of marriage, only the third day after we enjoy an allegory of peace.
  • hook 3 is about a ballet, and 4 about a ballet dancer - hook 3 doesn't say ballet but I believe that should be changed, and perhaps a link to suite might prevent misunderstandings, - The Firebird is not a hotel ;)
  • hook 4 doesn't need a link to Paris Opera, after one to Paris Opera Ballet saying it's "an integral part" of the other
  • hook 6 mentions another opera with an opera singer and an opera conductor (after we enjoy an opera also in the previous set)

4 hooks in one set about European high culture - almost too good. -- Gerda Arendt (talk) 20:20, 31 March 2023 (UTC)[reply]

Just 4? What, ABBA doesn't count as European high culture? -- RoySmith (talk) 20:27, 31 March 2023 (UTC)[reply]
It does seem to contain pretty much all US/European hooks. I think some swapping is in order for balance. Valereee (talk) 20:34, 31 March 2023 (UTC)[reply]
@Valereee I've swapped two. BorgQueen (talk) 10:10, 1 April 2023 (UTC)[reply]
Thanks, I was just thinking I should circle back to this! Valereee (talk) 10:13, 1 April 2023 (UTC)[reply]
I'm sad. Point taken but there was a logic to how the hook themes and words tied together. Cielquiparle (talk) 16:34, 1 April 2023 (UTC)[reply]
@Cielquiparle, you're thinking maybe we should do theme-based sets? I could see doing it for a special occasion. I think if you've built a set intentionally around a theme, you probably want to open a discussion. Valereee (talk) 16:36, 1 April 2023 (UTC)[reply]
The fewer hooks we have to work with, the fewer choices we have. Sometimes it "feels" like after an extended run of 12-hour cycles, we've burned through all the "best" hooks super quickly and are left with...what's left. So we make the best of what we have. This, to me, is the strongest argument for why we seriously need to consider 18-hour cycles. It's not just a "fairness" argument. It's because it affects the quality of the sets. Cielquiparle (talk) 16:41, 1 April 2023 (UTC)[reply]
I would argue the opposite. I'd prefer to be more selective about what we publish. 8 hooks every 19 hours is about 10 hooks every 24 hours. If we published the best 8, we'd still have an acceptance rate of 80%, which is astoundingly high for any publication that cares about quality. Looking at my own submissions, I can easily identify 20% (if not more) which technically met the rules but were still pretty marginal in terms of article quality. -- RoySmith (talk) 17:21, 1 April 2023 (UTC)[reply]
@RoySmith I have tried very hard to hit a higher quota in terms of rejections and withdrawals. I would appreciate it if you would take a look at the ones I have rejected, or questioned with serious reservations, and close them. Cielquiparle (talk) 17:27, 1 April 2023 (UTC)[reply]
Could you suggest a few specific ones that I should look at? -- RoySmith (talk) 17:36, 1 April 2023 (UTC)[reply]
Hooks that need a second look either way:
CC: RoySmith. Added one more. Cielquiparle (talk) 17:51, 1 April 2023 (UTC)[reply]
I closed one, and left an ALT suggestion for another. I'll try to take a look at the others tomorrow. -- RoySmith (talk) 03:07, 2 April 2023 (UTC)[reply]
For me it's a strong argument for rejecting hooks that no promoter thinks are worth promoting, per @EEng's (sorry, didn't like to mention without pinging) proposal. Valereee (talk) 17:32, 1 April 2023 (UTC)[reply]
@Valereee I would argue that the promoters and others have actually been very thorough recently in encouraging withdrawals and rejecting hooks that are not suitable or weak. But I don't think this information is tracked anywhere. (The other thing of course is that we actually do spend quite a bit of energy trying to improve hooks, so that other promoters can promote them.) Cielquiparle (talk) 17:52, 1 April 2023 (UTC)[reply]
The argument about "bottom of the barrel" is not to imply that what is left after the 12-hour cycles are done are the weakest hooks. What it does mean, though, is that the variety of what is left can be lopsided: Of course it's easier to space out picture hooks about paintings, if there are more picture hooks to choose from. But not if you just used them all up in a frenzy of 12-hour cycles. Cielquiparle (talk) 18:04, 1 April 2023 (UTC)[reply]
I will also say that I would encourage some kind of reform to prioritize quality control over scheduling perfection – the latter lends itself to hard rules much more easily than the former, but that does sometimes lead to us putting too much attention on the wrong thing. theleekycauldron (talkcontribs) (she/her) 03:10, 2 April 2023 (UTC)[reply]

Queue 7 Prep 7 swap for April 7?

We have a request from @Gerda Arendt to run a Good Friday hook on April 7, which maps to Queue 7. As soon as the citation needed tags are resolved in the article, we could either promote it to the existing Queue 7, or build a new set around it in Prep 7, and swap the sets. Thoughts? Cielquiparle (talk) 06:15, 2 April 2023 (UTC)[reply]

I don't know which nom is being referred to, but as long as it doesn't unbalance the Queue in terms of bios or locations I think it would be simpler to just swap out one of the hooks and replace it with the date-sensitive one, once any issues with the article are resolved. That same set has already been pushed out of the Queue once to accommodate for April 1, so ideally I think we should avoid pulling the entire set back out a second time. - Aoidh (talk) 06:32, 2 April 2023 (UTC)[reply]
@Aoidh Thanks, makes sense. No wonder it sounded so familiar. The hook in question is currently at the top of the "Requested dates" section: Template:Did you know nominations/Passions (Homilius) Once the cn-tags are resolved, we'll ask for help from an admin to get it promoted into one of the Queue 7 slots, as long as there are no further objections. Cielquiparle (talk) 06:45, 2 April 2023 (UTC)[reply]
Cielquiparle, Aoidh, the hook should go into Queue 6, not Queue 7; Queue 6 is the one scheduled to run on April 7. The hook should be inserted into Queue 6 and the displaced hook put into a free slot in a prep set. (Replacing set for set made sense for a whole-day set like April Fools' Day, but it doesn't for one or even a couple of hooks.) BlueMoonset (talk) 18:03, 2 April 2023 (UTC)[reply]
Thanks @BlueMoonset for clarifying. I've restored the tick on Template:Did you know nominations/Passions (Homilius), so it is ready to be swapped into Queue 6 by an admin. (I would ping the admins but have not figured out how do do it in Visual Editor.) Cielquiparle (talk) 19:46, 2 April 2023 (UTC)[reply]
@BlueMoonset: thanks for catching that, but now that I'm looking at Template:Did you know/Queue#Local update times, it looks like it would be Queue 5 that runs on April 7, rather than Queues 6 or 7. Unless I'm missing something, Queue 6 looks to start at 00:00, 8 April (UTC). - Aoidh (talk) 01:44, 3 April 2023 (UTC)[reply]
Okay...when I checked Template:Did you know/Queue#Local update times yesterday it clearly said that Queue 5 would start at 00:00, 7 April (UTC), but now that I'm looking at it again it now says Queue 6 is indeed what runs at that time. I'll take a look at Queue 6 now. - Aoidh (talk) 16:59, 3 April 2023 (UTC)[reply]
 Done - Aoidh (talk) 17:06, 3 April 2023 (UTC)[reply]
Aoidh, thanks. If you're looking at the Local update times section right as a queue is being promoted to the main page, the table can be a day off for a few minutes while things are being updated and moving around, but it's correct the rest of the time. That might have happened to you. BlueMoonset (talk) 21:24, 3 April 2023 (UTC)[reply]
Sorry to cause more problems. The Homilius is now in Queue 6 which is fine, thank you Aoidh, but the nomination wasn't closed, and I now have two musical hooks in that set. Can the opera (with Johanna Geisler) please be swapped instead of whatever was? - Completely different request, just seeing a few admins active: I have a nomination open for Recent deaths which needs a third support, and then someone to move it to the template. James Bowman was the second countertenor to revived the voice part. --Gerda Arendt (talk) 22:09, 3 April 2023 (UTC)[reply]
 Done - I've restored the Eurovision hook and switched out Johanna Geisler for Passions (Homilius). I won't close the nom yet since there's an ongoing discussion; I'll let the details discussed below get resolved and either myself or another editor can then close it whenever is appropriate. - Aoidh (talk) 01:03, 4 April 2023 (UTC)[reply]
  • Sorry to be a party pooper, but the promoted hook is currently not good, and possibly even misleading if read as I would propose a rather natural reading is (the 2023 performance is not a "first" one, but the context makes it appear as if it is, especially since the relevance of said performance is totally unclear if it isn't a first one). See the nomination page for more. SnowFire (talk) 23:11, 3 April 2023 (UTC)[reply]
    @Gerda Arendt and SnowFire: I do want to acknowledge that I've seen these comments and I agree that any issues should certainly be ironed out before the queue runs, but I will be indisposed for a little while so I might not be able to immediately address this. @Cielquiparle, Bruxton, and C messier: I know the three of you were involved with reviewing the nomination and the hooks, would you mind taking another look at this? - Aoidh (talk) 00:54, 4 April 2023 (UTC)[reply]
    I don't have access to all the sources, but if I understand correctly, it could very well be a first-ever live performance of the full work, but as we all know, "firsts" can be hard to prove, especially if ~300 years have gone by (during which time territorial boundaries weren't even the same). (Sounds like small excerpts have been performed before, and to Gerda's point, the full work was even recorded in 1992, which counts as a "performance" depending on how you look at it.) So it is not intended to mislead but is rather trying not to assert or overstate something, based on the sources. But if the feedback from @SnowFire is that the hook is bad, that's different. I have also had a nagging feeling that the hook is fixable in a different way and burned quite some time on this yesterday, but will take a look again. Hope you feel better soon @Aoidh Cielquiparle (talk) 04:06, 4 April 2023 (UTC)[reply]
    Just found the FAZ article republished on Yahoo! and it does refer to other "performances" around the time of the recording, as well as "reduced" performances (with fewer parts in the cast), so for sure not a "first" performance but clearly very rarely performed, since it seems like the handwritten dots on paper were barely kept together. Cielquiparle (talk) 04:27, 4 April 2023 (UTC)[reply]
    My suggestion is just to cut the fact entirely regardless of the research (although that is appreciated!). We should just avoid a hook that says something like "Did you know about this obscure piece that is just SO obscure." The quasi-interesting part is the long gap in time with the "resurrection" of the piece being the cool part. So something like ALT1c might be better. (The other option is to highlight some other interesting-and-verifiable fact about the 2023 performance - but not just its existence, because mere existence isn't interesting.) SnowFire (talk) 05:00, 4 April 2023 (UTC)[reply]
    @SnowFire: I proposed a new ALT hook in the nomination template. Cielquiparle (talk) 05:16, 4 April 2023 (UTC)[reply]

Reporting a missing hook in Prep area 5

Hello! I just wanted to report that Prep 5 (starting with TVBoy) is still missing one hook at the very bottom: I think it just went unnoticed by accident, but still...

Oltrepier (talk) 18:17, 2 April 2023 (UTC)[reply]

@Oltrepier thanks for noticing, but that's actually normal. The prep areas are often in a state of flux, as people build them up and shuffle hooks around until they're happy. If you ever see a queue that's missing a hook, please report that, however; the queues should pretty much never be incomplete. -- RoySmith (talk) 18:43, 2 April 2023 (UTC)[reply]
@RoySmith Thank you for clarifying! Oltrepier (talk) 19:25, 2 April 2023 (UTC)[reply]

Older nominations needing DYK reviewers

The previous list was archived earlier today, so I've created a new list of all 28 nominations that need reviewing in the Older nominations section of the Nominations page, covering everything through March 25. We have a total of 202 nominations, of which 70 have been approved, a gap of 132 nominations that has decreased by 1 over the past eight days. Thanks to everyone who reviews these and any other nominations!

More than two months old

More than one month old

Other 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. Please do not remove them entirely. Many thanks! BlueMoonset (talk) 18:47, 2 April 2023 (UTC)[reply]

Adding a couple that need hook reviewers. Cielquiparle (talk) 08:59, 4 April 2023 (UTC)[reply]

Queue 3: Hook update request

Queue 3 is scheduled to post at 4 April 00:00 (UTC).

As the nominator, I would like to request the hook be slightly changed with more timely information, if possible:

... that UCLA basketball player Jaylen Clark was named the Pac-12 Conference Defensive Player of the Year Naismith Defensive Player of the Year in 2023, after also significantly improving on offense?

Clark won the Naismith award today (Sunday), and it's a more recognized national award, compared to the regional Pac-12 honor. The Los Angeles Times said it's "widely considered the nation’s top defensive award among college players" [2]

It's already stated and sourced in the body: "One of the top defensive players in the country, he won the Naismith Defensive Player of the Year Award, and the National Association of Basketball Coaches named him their defensive player of the year.[27]" (Source text: "The UCLA junior guard on Sunday was honored as the school’s first Naismith defensive player of the year..." (Los Angeles Times))

Thanks in advance. —Bagumba (talk) 04:13, 3 April 2023 (UTC)[reply]

@Onegreatjoke: Courtesy ping as you were the original reviewer.—Bagumba (talk) 04:15, 3 April 2023 (UTC)[reply]
In case OGJ doesn't get to this in time, I'm happy to endorse the change. I reviewed the new hook and checked the sources. Looks good. Firefangledfeathers (talk / contribs) 14:11, 3 April 2023 (UTC)[reply]
I'm fine with the new hook. Onegreatjoke (talk) 14:31, 3 April 2023 (UTC)[reply]
Pinging admins working on the queue: @Aoidh and BorgQueen. Firefangledfeathers (talk / contribs) 15:16, 3 April 2023 (UTC)[reply]
 Done - Aoidh (talk) 16:49, 3 April 2023 (UTC)[reply]

Requesting credit for DYK

Could I receive a credit for the DYK for Buchanan's Station please? I normally wouldn't ask, but I ended up going deep on that one – as borne out by the page statistics. It is currently sitting in Prep 1. (I am receiving a credit for Sally Buchanan, but that was a minor work in comparison.) Cielquiparle (talk) 09:28, 3 April 2023 (UTC)[reply]

Sorry @Cielquiparlez: I thought you were trying to credit yourself for the sally hook so I swapped that credit in for the double hook. Bruxton (talk) 14:18, 3 April 2023 (UTC)[reply]
Perpetual pinging problems. @Cielquiparle: Bruxton (talk) 14:38, 3 April 2023 (UTC)[reply]
Done. BorgQueen (talk) 11:02, 3 April 2023 (UTC)[reply]

Passions (Homilius) Nom@Aoidh: Can we make room in the queue for this Good Friday request? It was nominated March 16, but finally wrapped up today. If it is too late for that set we can promote it to a later set. Bruxton (talk) 14:15, 3 April 2023 (UTC)[reply]

 Done, see above at Wikipedia talk:Did you know#Queue 7 Prep 7 swap for April 7? - Aoidh (talk) 17:06, 3 April 2023 (UTC)[reply]

Here we go again

I've done a manual update, again. @Aoidh could you please take care of the credits? BorgQueen (talk) 00:09, 4 April 2023 (UTC)[reply]

@BorgQueen: On it. - Aoidh (talk) 00:18, 4 April 2023 (UTC)[reply]
Credits on user and article talk pages are both  Done - Aoidh (talk) 00:35, 4 April 2023 (UTC)[reply]

Both bots are back online. In the future, the best way to reach me is to drop a message on my talk page, which ideally would have happened ~a day ago when Queue 2 was manually cleared as the bot failed to do so. If I was notified then, I might've seen this in time to restart the bots for today's update. Help me help you. Shubinator (talk) 02:04, 4 April 2023 (UTC)[reply]

Misconception about Earwig

I notice a lot of reviewers using WP:EARWIG to claim that an article has no copyright violations or plagiarism. Remember that, as a general rule, Earwig does not catch copyright violations or plagiarism. It checks a handful of websites to see if the article is an exact copy or nearly an exact copy. Virtually all forms of copyright violation and plagiarism beyond a simple copy-paste will get past Earwig. It's not designed to do a full copyright check, it's designed to check if an article is a duplicate of another website. Thebiguglyalien (talk) 18:42, 4 April 2023 (UTC)[reply]

Exactly. Earwig is a good tool, but it's only a tool. One must examine more than just the big percent number at the top. False positives could be somebody else copying from us. Or they could be direct quotes which are appropriately cited to the original source. More troubling is that, as @Thebiguglyalien says, Earwig misses places where somebody has basically copied the original sentence-for-sentence but changed enough words so Earwig doesn't catch the problem. That takes using your human brain to compare the two texts.
It can also completely fail to report anything simply because the plagiarised source isn't within its field of view. Sometimes I read an article and there's something that just screams out "This wasn't written by the same person who wrote the rest of this", so you need to go digging on your own. -- RoySmith (talk) 19:16, 4 April 2023 (UTC)[reply]