Talk:Bombing of Mokha

Latest comment: 1 year ago by CSJJ104 in topic Did you know nomination

Did you know nomination edit

The following is an archived discussion of the DYK nomination of the article below. Please do not modify this page. Subsequent comments should be made on the appropriate discussion page (such as this nomination's talk page, the article's talk page or Wikipedia talk:Did you know), unless there is consensus to re-open the discussion at this page. No further edits should be made to this page.

The result was: promoted by CSJJ104 (talk) 17:58, 1 October 2022 (UTC)Reply

5x expanded by Mhhossein (talk). Nominated by Mhhossein (talk) at 12:17, 22 July 2022 (UTC).Reply

  • @Mhhossein: Can you provide a QPQ for this? Thanks, Z1720 (talk) 03:58, 30 July 2022 (UTC)Reply
  •   No QPQ was provided within seven days of the nomination, despite a ping above and activity elsewhere. This is purely procedural and the nomination can resume if a QPQ is provided. Narutolovehinata5 (talk · contributions) 05:41, 1 August 2022 (UTC)Reply
Having done dozens of DYKs so far, due to the usual backlog, it takes numerous days for the QPQed nominations to be reviewed and promoted. It is just a surprise seeing this comment and ridiculous for a QPQnomination to be closed solely for lack of QPQ. The QPQ will be provided within the coming days. --Mhhossein talk 10:43, 1 August 2022 (UTC)Reply
It's per a recent recent rule change to DYK. See WP:DYKCRIT: Ideally, a QPQ should be submitted within a week of a nomination. After one week, and a reminder to the nominator, a nomination may be closed as "incomplete." Narutolovehinata5 (talk · contributions) 10:58, 1 August 2022 (UTC)Reply
  Nominator was notified of the lack of a QPQ on July 30. This nomination should be rejected if no QPQ is supplied within a week from then, that is August 6. Flibirigit (talk) 16:44, 1 August 2022 (UTC)Reply
General: Article is new enough and long enough
Policy: Article is sourced, neutral, and free of copyright problems

Hook eligibility:

  • Cited:   - ?
  • Interesting:  
QPQ: Done.

Overall:   A few issues need to be addressed:

  • For some reason, DYKcheck reports this as not sufficiently expanded, but a manual comparison of before and current (as of 20 August) shows an expansion of just over 5x prose content. So I'm accepting the length as sufficient.
  • (Earwig finds some similarity with the Reuters article, although I think it's because of the quotations.) Not really an issue, imo, just wanted to note that I checked that.
  • The article also needs an inline ref directly after each sentence containing a quotation – maybe just duplicate some of the refs.
  • Currently the hook prose is in the lede, but the source cited there does only speak of "more than 120 dead", which is not what's written there. It would probably be better to write this as "65(inline one) to 120(inline two) dead" or something. The "150" currently in the hook is definitely wrong – this many were wounded, according to US News (btw this is not cited in the infobox).
  • The article needs some copyediting, for example "The airstrike hit the residential area in dedicated to the plant workers." I can help with that if needed, although some things are quite obvious.

Nothing major and all these things can be fixed. @Mhhossein best ping me when you are done. --LordPeterII (talk) 10:23, 20 August 2022 (UTC)Reply

Thank you LordPeterII. The CNBC source clearly says "a power plant in Mokha that killed at least 120 people". I have changed the lead wording so that it shows the correct sourcing for the number of dead and will as GOCE to copyedit the page. How about the following hook:
Alt1: ... that the bombing of Mokha in Yemen by Saudi Arabia-led coalition was described as of the "deadliest" attacks by Saudi Arabia against Yemen, leaving 65 – more than 120 dead including 10 children?
--Mhhossein talk 13:09, 21 August 2022 (UTC)Reply
@Mhhossein: My issue was primarily with the hook fact not corresponding to a cited article sentence. This is now resolved, but I find that with the dash it looks weird. How about instead:
This removes also the duplicate "Saudi Arabia" and "Yemen", so the hook is shorter and I think it is still very clear. --LordPeterII (talk) 17:01, 21 August 2022 (UTC)Reply
Okay I just realized I also removed the "children" part, feel free to add that back in (I was worried it would be too long, but with the dupicate country names removed it is quite short now). And I also piped a link to the Saudi coalition, not sure if you want that or not. You can propose another modified hook if you want, until we find something we both like. --LordPeterII (talk) 17:04, 21 August 2022 (UTC)Reply
Thanks, then I suggest going with the version including the children toll.
It is 186 characters which is not too long. --Mhhossein talk 10:32, 22 August 2022 (UTC)Reply
@Mhhossein: Yes, that's short enough. I will approve that hook once the copyediting is done (and some bare sources converted to use citation templates, but I will look at that myself). --LordPeterII (talk) 19:36, 23 August 2022 (UTC)Reply
Because of the ambiguous way the sentence is constructed, it can be read to mean that the bombing was done by the Saudi Arabian-led coalition, or it can be read to mean that the attack was described by the Saudi Arabian-led coalition. The cited source article stated it this way: "A Saudi-led coalition airstrike hit a funeral hall with thousands of mourners... ...in one of the deadliest single attacks of the country’s civil war, a U.N. official said." Using similar language, it could be rephrased this way:
In that regard, the ambiguity is avoided and the sentence is also a very close read to the way it is phrased in the original source article. Regards, AzureCitizen (talk) 01:21, 30 September 2022 (UTC)Reply
@Mhhossein and AzureCitizen: Sorry, I was ill & then very busy irl, am checking in quickly to finish this and other things. I agree ALT3 is better still, I can see the ambiguity. Also thanks @Drmies for doing the copyediting. If anyone could take a look at the sentence "The airstrike hit the residential area in dedicated to the plant workers" that would be great, it's the only thing that still reads weird imo, not sure what it's supposed to say.
  Approve ALT3. –LordPeterII (talk) 15:00, 30 September 2022 (UTC)Reply
User:LordPeterII, done. Thanks. Drmies (talk) 15:07, 30 September 2022 (UTC)Reply
Uh oh, looking more closely at this after reading the part above about hitting a residential area dedicated to plant workers versus the source article talking about hitting a packed funeral hall, apparently these are two different air strikes. The residential area bombing was in Mokha in July 2015 and the funeral hall bombing was in Sanaa in October 2016. That should probably be worked out before proceeding further? Regards, AzureCitizen (talk) 15:31, 30 September 2022 (UTC)Reply
@AzureCitizen: Can you clarify what you mean? There definitely must not be a mix-up with other airstrikes. I read the source for the sentence that now is The airstrike hit the residential area with housing for the plant workers from The Independent as being about the airstrike on Mokha. Where is the one about Sanaa? –LordPeterII (talk) 16:34, 30 September 2022 (UTC)Reply
It's the second sentence in the second paragraph of the article's lead, which reads "The attack was one of the deadliest attacks by Saudi Arabia against Yemen", and uses this source from CNBC, which is actually referring to the 2016 Sanaa bombing instead of the 2015 Mokha bombing. Does that help? Regards, AzureCitizen (talk) 16:39, 30 September 2022 (UTC)Reply
Ah yes, now I got it: The CNBC source is indeed primarily about a later airstrike on Sanaa. In fact, that news article is even more confusing because it mentions three separate airstrikes: The one on Mokha in July 2015, one on Mastaba in March 2016, and finally the (at the time) most recent one on Sanaa in October 2016. It says: Saturday's attack comes after a Saudi-led coalition March 15 airstrike on a market in Yemen's northwestern city of Mastaba that killed at least 119 people. Saudi forces reportedly used U.S. munitions in that strike, which at the time was described as the second-deadliest of the Saudi campaign, after a July 2015 attack near a power plant in Mokha that killed at least 120 people. The article and the DYK hook really only need the comparison here, which means that the minimum 120 deaths for Mokha is a sad second place in deadliness at the point of the CNBC article. I remember that this had confused me as well a while back, so good catch, if not an actual error. It would have been an easy mistake to e.g. slip in the wrong number (140 for Sanaa) from that news into the article. I checked twice and it didn't, so I think we're good. –LordPeterII (talk) 16:47, 30 September 2022 (UTC)Reply
Looks good and it all makes sense now. Thanks for parsing that out! AzureCitizen (talk) 16:55, 30 September 2022 (UTC)Reply

Mokha or Mocha edit

@Theleekycauldron: Hey, did you consider the reliable sources used in this article before moving it? Mhhossein talk 04:33, 27 August 2022 (UTC)Reply

Hey, @Mhhossein! I was sure i responded to this... I considered the reliable sources at Mocha, Yemen, as well as adjusted Google ngrams data. Come to think of it, I didn't see it as definitive – you're welcome to revert under MOS:VAR, if you'd like. theleekycauldron (talkcontribs) (she/they) 06:27, 31 August 2022 (UTC)Reply
Hi Theleekycauldron, 'Mokha' is the common title used when the incident is covered by the sources. I double checked the ones used in this page, which actually are the most relevant sources I found when I was authoring the page. --Mhhossein talk 06:39, 31 August 2022 (UTC)Reply
@Mhhossein: I gathered that too – it's your call :) theleekycauldron (talkcontribs) (she/they) 06:40, 31 August 2022 (UTC)Reply
@Mhhossein and Theleekycauldron: I think the issue is that the letter "خ" is transliterated in different ways. Duolingo spells it as "kh" for me, so maybe that's the newer variant, compared to the historically more prominent "ch". It's actually worse in German, we have Mokka, which leads to a needlessly bad pronunciation – if it was spelled "Mucha" in German, we'd actually have a 50% chance of pronouncing it mostly correct (that is, almost like an Arabic speaker would). Alas, historical transliterations were a little imprecise. I've adjusted the Mokha (or Mocha) article to give all the possible spellings in the lede there, maybe that will help clarify things for confused readers. --LordPeterII (talk) 10:43, 31 August 2022 (UTC)Reply
I assume it's /x/, like the hebrew Heth? theleekycauldron (talkcontribs) (she/they) 17:16, 31 August 2022 (UTC)Reply
It would transcribed as 'kh' these days, yes, but it's known in older sources as "Mocha". That's the dilemma. Iskandar323 (talk) 08:22, 1 September 2022 (UTC)Reply
Thank you guys for your interest. --Mhhossein talk 10:35, 1 September 2022 (UTC)Reply
@Theleekycauldron: Probably? I don't know Hebrew, but yes, it's kinda like the "ch" in "loch". --LordPeterII (talk) 11:01, 1 September 2022 (UTC)Reply
Yes, that's right - the other advantage of Mokha is that it prevents pronunciation like the coffee. Iskandar323 (talk) 11:37, 1 September 2022 (UTC)Reply