Wikipedia talk:Did you know: Difference between revisions
→Prep 4 - David M. Wilson: Comment |
|||
Line 493: | Line 493: | ||
'''Anyone please feel free to push back on any of the above''' but for now I'll press on, assuming ALT6'''A''' is the popular choice. I do think that the ''supports'' above were somewhat ambiguous as to whether, in each case, the support-er was simply expressing a preference for this particular hook, or was (also) specifically joining in the opinion that ALT6 is policy compliant. Therefore, given the ruckus over this, I suggest we have a final round of discussion ''specifically on that point''. |
'''Anyone please feel free to push back on any of the above''' but for now I'll press on, assuming ALT6'''A''' is the popular choice. I do think that the ''supports'' above were somewhat ambiguous as to whether, in each case, the support-er was simply expressing a preference for this particular hook, or was (also) specifically joining in the opinion that ALT6 is policy compliant. Therefore, given the ruckus over this, I suggest we have a final round of discussion ''specifically on that point''. |
||
*'''Support ALT6A as [[WP:BLP]] compliant.''' There is undeniably ''some'' merit to the idea that you shouldn't have to follow the links to understand the hook{{snd}}but remember this is scheduled for April 1; whether that worries you or not the ''(map pictured)'', together with the map itself (and its caption), make it clear that the hook's text isn't to be taken at face value. Concerns about exotic platforms dismembering the hook-image combination seem far-fetched. [[User:EEng#s|<b style="color: red;">E</b>]][[User talk:EEng#s|<b style="color: blue;">Eng</b>]] 03:40, 10 February 2018 (UTC) |
*'''Support ALT6A as [[WP:BLP]] compliant.''' There is undeniably ''some'' merit to the idea that you shouldn't have to follow the links to understand the hook{{snd}}but remember this is scheduled for April 1; whether that worries you or not the ''(map pictured)'', together with the map itself (and its caption), make it clear that the hook's text isn't to be taken at face value. Concerns about exotic platforms dismembering the hook-image combination seem far-fetched. [[User:EEng#s|<b style="color: red;">E</b>]][[User talk:EEng#s|<b style="color: blue;">Eng</b>]] 03:40, 10 February 2018 (UTC) |
||
* Coffee suggested above that the WMF would not approve of our posting this. I therefore raised the matter with [[Katherine Maher]], the current CEO of the WMF, when she spoke on the [[c:Category:Wikimedia Day at Newspeak House, February 3 2018|Future of Wikipedia]], last week. She had not heard of the Trump Street connection with Russia Row before and thought it was an amusing story. When I pressed on the issue of its suitability, she made it fairly clear that we have [[editorial independence|editorial freedom]] for such matters and so the WMF would not intervene. It is up to us then. [[user:Andrew Davidson|Andrew D.]] ([[user talk:Andrew Davidson|talk]]) 16:03, 10 February 2018 (UTC) |
|||
* On the question of the hook choice, I myself really don't like Americanised hooks such as ALT6A and [[WP:ENGVAR]] should apply. ALT1 is my preference as the humour of the juxtaposition is not forced and it can be read in a matter-of-fact way. Our readers are smart enough to get the joke and so we have no need to fool them. [[user:Andrew Davidson|Andrew D.]] ([[user talk:Andrew Davidson|talk]]) 16:03, 10 February 2018 (UTC) |
|||
== Template:Did you know nominations/Stephen Court Fire == |
== Template:Did you know nominations/Stephen Court Fire == |
Revision as of 16:03, 10 February 2018
![]() | Error reports Please do not post error reports for the current Main Page template version here. Instead, post them to Wikipedia:Main Page/Errors. Errors reports relating to the next queue to be promoted can also be posted to ERRORS. If you post an error report on one of the queues here, please include a link to the queue in question. Thank you. |
Index no archives yet (create) |
This page has archives. Sections older than 7 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present. |
![]() | DYK queue status
Current time: 14:13, 24 August 2024 (UTC) Update frequency: once every 24 hours Last updated: 14 hours ago() |
This is where the Did you know section on the main page, its policies and the featured items can be discussed.
Do you have a suggestion for improving DYK, or would like to comment on the suggestions of others? Have your say at Wikipedia:Did you know/2017 reform proposals.
DYK and COI/paid editors
Template:Did you know nominations/Denise Stephens raises a few issues, including:
- If an article was created and/or nominated by paid a COI editor, should that be explicitly disclosed in the nomination?
- Should articles created and/or nominated by paid COI editors be eligible for DYK?
Personally, my instinct would be for a blanket ban: No DYK if any COI or payment is involved. --BrownHairedGirl (talk) • (contribs) 19:37, 29 January 2018 (UTC)
- One imagines that DYK should follow whatever guidelines the project overall has deemed appropriate for such scenarios. The Rambling Man (talk) 19:43, 29 January 2018 (UTC)
- I'm more concerned about whether she is actually notable. In US academia, being an "associate professor" does not count for much. Edwardx (talk) 20:00, 29 January 2018 (UTC)
- Right, well response (a) DYK should follow Wikipedia's response to COI/paid editing and not make it's own rules up (b) if you don't like the notability, WP:AFD is the place to determine it. The Rambling Man (talk) 20:16, 29 January 2018 (UTC)
- Paid editing is frowned upon but not actually forbidden so as long as it's disclosed (WP:PAID). COI editing is discouraged but not actually prohibited (WP:COI). That's for general wiki practice. Jo-Jo Eumerus (talk, contributions) 20:33, 29 January 2018 (UTC)
- (ec) It's not so black-and-white, @TRM.
- WP:DYK "showcases new or expanded articles that are selected through an informal review process". Allowing COI/paid editing does not require that it be eligible to be showcased.
- COI/paid editing is subject to some restrictions, and it would be perfectly reasonable for the community to choose (if it so wished) to decide that one of those restrictions is that COI/paid content doesn't get showcased. --BrownHairedGirl (talk) • (contribs) 20:38, 29 January 2018 (UTC)
- Right, well response (a) DYK should follow Wikipedia's response to COI/paid editing and not make it's own rules up (b) if you don't like the notability, WP:AFD is the place to determine it. The Rambling Man (talk) 20:16, 29 January 2018 (UTC)
- I'm more concerned about whether she is actually notable. In US academia, being an "associate professor" does not count for much. Edwardx (talk) 20:00, 29 January 2018 (UTC)
- notified[1] at WP:VPP. --BrownHairedGirl (talk) • (contribs) 20:43, 29 January 2018 (UTC)
No, Wikipedia should have a site-wide guideline with which DYK complies. Unless you're going to apply it to all other aspects of the main page. By which point just use the site-wide approach. A "special approach" to DYK is yet another burden the project could do without. The Rambling Man (talk) 20:47, 29 January 2018 (UTC)
- Support banning paid/COI editors from DYK. The thought of such editors getting extra pay for DYK exposure is repulsive. -Zanhe (talk) 20:49, 29 January 2018 (UTC)
- Oppose per site-wide application of tolerance with honesty and compliance with all other guidelines and policy. If it improves Wikipedia, no problem. The Rambling Man (talk) 20:54, 29 January 2018 (UTC)
- Regarding question 1, as I understand it, DYK articles are new or newly expanded, so the relevant edits should comply with the paid editing disclosure requirements in Wikipedia's terms of use. So I don't see any need to repeat a disclosure in the nomination. The answer for question 2 depends if the community wants to alter the goals for DYK to acknowledge the work of unpaid editors, versus all editors. isaacl (talk) 21:30, 29 January 2018 (UTC)
- (edit conflict) Oppose this would discourage people to declare their COI/paid editing status. If people do it properly, then they should be judged on the usual DYK criteria. Joseph2302 (talk) 21:32, 29 January 2018 (UTC)
- Oppose I agree with the above that people would just not declare it if the rules said that. Furthermore, if the hook and article are of decent enough quality and of the required standards, then who are we to rob the community and the wider world of being able to see it and improve it? The C of E God Save the Queen! (talk) 21:43, 29 January 2018 (UTC)
- I agree with editors who say that DYK should follow what the rest of the project does, so there should not be a blanket ban. Of course, if it is found out that there was undisclosed paid editing in violation of the Terms of Use, before the hook makes it to the main page, the hook should be disqualified by that. And there is nothing wrong with reviewers setting a high standard that anything that sounds promotional should be fixed before approving a nomination. --Tryptofish (talk) 22:01, 29 January 2018 (UTC)
- But are we seriously having a discussion on whether or not a DYK hook should be "disqualified"?? If someone is caught paid editing without disclosure etc, a DYK credit is probably the last thing we should really give a toss about. The Rambling Man (talk) 22:08, 29 January 2018 (UTC)
- Agreed. Although in that case, they should lose the DYK too. Joseph2302 (talk) 22:14, 29 January 2018 (UTC)
- Oppose We already have the Terms of Use. Hawkeye7 (discuss) 22:11, 29 January 2018 (UTC)
- yes for disclosure and
noweak support for ban. If we don't ban, It should absolutely be disclosed here - editors with any sort of COI and acting in the spirit of the COI guideline (and for paid editors the spirit of the PAID policy) should disclose locally in whatever forum they are in, to be sure that people with whom they are interacting understand that they have a COI. So yes it should be disclosed. Butitshouldnotit be barred? - I could see a situation where we don't, and the DYK nomination should be reviewed on the content merits, with the COI in mind (this is the purpose of the disclosure). I want to remind folks that the heart of the scandal around the Gibraltarpedia matter, was that the project had seventeen DYKs in a single month, and one of the editors organizing it (and doing DYK nominations) was being paid by the Gibraltar Tourism Board for organizing the project. Whatever you think of paid editing or GLAM stuff, the optics of that were terrible. It was actually a thread at this talk page, here, that first raised that issue, as was reported on here for example. So I weakly support the ban to make things simple and avoid repeating what happened with Gibraltarpedia and the Tony Ahn stuff... but this is much less of a big deal to me than disclosure. If the ban fails, then we absolutely should require disclosure Jytdog (talk) 22:22, 29 January 2018 (UTC) (nuance this Jytdog (talk) 15:51, 30 January 2018 (UTC))- @Jytdog: the nom which prompted me to open this discussion was Template:Did you know nominations/Denise Stephens, where the paid editor @Skyes(BYU) has disclosed their status on their user page, but did not repeat that disclosure in the DYK nom. The DYK reviewer @Whispyhistory spotted the userpage and noted it ... but shouldn't Skyes(BYU) have disclosed it in the nom? --BrownHairedGirl (talk) • (contribs) 22:37, 29 January 2018 (UTC)
- This is hard thing, since nobody has to undergo training before they start doing stuff. The COI guideline makes it clear that somebody with a COI (paid or not) should make it clear to who ever they are talking with, in whatever forum, that they are conflicted. Sometimes people fail to do this out of ignorance; sometimes they are trying to hide. I haven't looked at what went on here in particular but I will do. If there is a template used for nominations it would be good to include something about disclosing any COI in it, and in the instructions... Jytdog (talk) 22:45, 29 January 2018 (UTC)
- @Jytdog: yes, the template is {{NewDYKnomination}}. I really like the idea of including a COI disclosure line in it. --BrownHairedGirl (talk) • (contribs) 23:43, 29 January 2018 (UTC)
- OK, it would be easy to slot in there (conceptually at least; i have no idea how hard it would be to implement). Let's see if consensus develops to do that... Jytdog (talk) 23:59, 29 January 2018 (UTC)
- @Jytdog: yes, the template is {{NewDYKnomination}}. I really like the idea of including a COI disclosure line in it. --BrownHairedGirl (talk) • (contribs) 23:43, 29 January 2018 (UTC)
- Oh, hm. The person is working for BYU so is GLAMish. But yes they should have disclosed this at the nomination. Will leave them a note. Jytdog (talk) 22:52, 29 January 2018 (UTC)
- This is hard thing, since nobody has to undergo training before they start doing stuff. The COI guideline makes it clear that somebody with a COI (paid or not) should make it clear to who ever they are talking with, in whatever forum, that they are conflicted. Sometimes people fail to do this out of ignorance; sometimes they are trying to hide. I haven't looked at what went on here in particular but I will do. If there is a template used for nominations it would be good to include something about disclosing any COI in it, and in the instructions... Jytdog (talk) 22:45, 29 January 2018 (UTC)
- @Jytdog: the nom which prompted me to open this discussion was Template:Did you know nominations/Denise Stephens, where the paid editor @Skyes(BYU) has disclosed their status on their user page, but did not repeat that disclosure in the DYK nom. The DYK reviewer @Whispyhistory spotted the userpage and noted it ... but shouldn't Skyes(BYU) have disclosed it in the nom? --BrownHairedGirl (talk) • (contribs) 22:37, 29 January 2018 (UTC)
- Oppose per TRM etc. On the other hand, Denise Stephens doesn't look very notable to me. Black Kite (talk) 23:26, 29 January 2018 (UTC)
- Support COI and Paid editing being forbidden on the main page unless it passes GA or FA review (which include detailed analysis for POV). We have had instances of paid editors charging money to take an article through DYK and get it on the main page for promotional purposes, which disgraces Wikipedia and puts the credibility of the main page at risk. I have added a note about this discussion over at WP:COIN. — Insertcleverphrasehere (or here) 23:34, 29 January 2018 (UTC)
Has anyone not noticed that the source given for the hook doesn't support the wording of the hook? The hook states "that Denise Stephens discovered a planet larger than Jupiter?", whereas the Salt Lake Tribune article being used as a cite states that the planet was discovered by three of Stephens' former undergraduates. PaleCloudedWhite (talk) 23:50, 29 January 2018 (UTC)
- (edit conflict) Oppose hard rule - I'm against undisclosed paid editing and all, but I guess that provided that the payment was properly disclosed, and the edits otherwise follow our policies and guidelines, then provided the edits are constructive, then I don't think such edits should prohibited in DYK. Nevertheless, whenever such edits are paid, more scrutiny should be given to such edits to ensure that they don't fall afoul of WP:COI. Narutolovehinata5 tccsdnew 23:53, 29 January 2018 (UTC)
- Comments - as far as the specific case leading to this - the editor seems to have tried following the spirit of our rules, but it's not among the best work on Wikipedia. Not the best application of our rules, only marginal notability (at best), not the best coverage of an article's subject. Shouldn't be disqualified from DYK based on policy, but ...
- As far as the broader issues raised, many folks have said that we don't need a special rule for DYK and Paid/COI, but rather should follow a "site-wide guideline". We have a site-wide policy WP:Paid and a site-wide guideline WP:COI that should all but eliminate any paid editing at DYK, and eliminate much COI editing here. It would be easier to just inform everybody "No paid editing on DYK articles, and COI editing should be declared on the nomination."
- Part of WP:PAID that applies here
- Editors must disclose their employer, client, and affiliation with respect to any paid contribution to Wikipedia. (italics added) which means that even nominating a DYK requires disclosure.
- from WP:PAY, parts of the guideline WP:COI - note that some folks say about this guideline that we don't need to follow guidelines - but they rarely say that about other guidelines
- you should make the disclosure on your user page, on affected talk pages, and whenever you discuss the topic;
- you are very strongly discouraged from editing affected articles directly.
- you may propose changes on talk pages (by using the {{request edit}} template), or by posting a note at the COI noticeboard), so that they can be peer reviewed;
- you should put new articles through the Articles for Creation (AfC) process instead of creating them directly; (bolding added - this is very tough for paid editors)
- you should not act as a reviewer of affected article(s) at AfC, new pages patrol or elsewhere;
Since paid editors have to follow both the policy and guideline - it's fair to say "please don't bother even trying". It's pretty hard for other financial COI editors to work with here as well. Smallbones(smalltalk) 01:55, 30 January 2018 (UTC)
- A couple more notes:
- In case of doubt on any DYK nom, please just inform WP:COIN and they'll check it out in detail.
- So why is the specific case not against policy? The editor should likely declare as a Wikipedian-in-Residence, who only have to declare their employer on their user page. Perhaps there is a reason they haven't done so, so please check with other WiRs (e.g. User:Wittylama) Smallbones(smalltalk) 02:30, 30 January 2018 (UTC)
- WiR/GLAM editors are supposed to use the resources of their host institution to improve articles (e.g. images from the British Museum to illustrate articles about art or archeology). When a WiR/GLAM editors writes about their host institution (in this case, faculty at their employer's institution) they are solidly in COI territory. This is discussed at Wikipedia:Conflict_of_interest#Wikipedians_in_residence,_reward_board and see also the guidelines on meta. Jytdog (talk) 03:09, 30 January 2018 (UTC)
"When a WiR/GLAM editors writes about their host institution (in this case, faculty at their employer's institution) they are solidly in COI territory. This is discussed at Wikipedia:Conflict of interest#Wikipedians in residence, reward board"
That page says nothing about faculty. Please stop putting your own overly-restrictive spin on agreed poliices. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:51, 30 January 2018 (UTC)- Most university PR is about the Great Stuff their faculty is doing. This is directly in line with that.Jytdog (talk) 15:09, 30 January 2018 (UTC)
"Most university PR"
We were discussing Wikimedians in Residence, not ""university PR". You continue - wrongly - to conflate the two. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 30 January 2018 (UTC)- You are not dealing with the issues here; that is what it is. This article and DYK are definitely university PR and this is not even a little ambiguous. This is not what the WiR program is for, and when WiR people do this sort of stuff, they are no different from say a person who is actually working in the university PR office and should behave accordingly per PAID and COI. Jytdog (talk) 18:50, 30 January 2018 (UTC)
- "The issues here" are not a single article, but a proposed change to DYK policy which as written would prohibit WiRs from working here; in that context, "this sort of stuff" is not PR. You still continue - still wrongly - to conflate the two. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:26, 30 January 2018 (UTC)
- You are not dealing with the issues here; that is what it is. This article and DYK are definitely university PR and this is not even a little ambiguous. This is not what the WiR program is for, and when WiR people do this sort of stuff, they are no different from say a person who is actually working in the university PR office and should behave accordingly per PAID and COI. Jytdog (talk) 18:50, 30 January 2018 (UTC)
- Most university PR is about the Great Stuff their faculty is doing. This is directly in line with that.Jytdog (talk) 15:09, 30 January 2018 (UTC)
- Since I was tagged by Smallbones here... These kinds of debates about paid-editing and COI really irritate me so much. They conflate the ideas of covert advocacy on an article (in breach of NPOV and usually also RS), with the idea of being paid. In a venn-diagram of 'advocacy' and 'payment' there is certainly an overlap - undisclosed paid advocacy. But there are people who do the former and not the latter (ideologues, fanboys...), and the latter but not the former (e.g. experts, academics...). What we ought to be cracking down on is paid [and undeclared] ADVOCACY not paid EDITING. This is ESPECIALLY since the concept of 'paid editing' seems to be thrown around so loosely as to also include anything related to an academic's field of expertise, not merely about when editing the article about their employer/boss/company. If we start inventing bans and disclosure rules for DYK about 'paid editing' we not only a) duplicate the rules already in place about COI disclosures, AND make it that much harder to convince cultural/educational organisations to get involved in content creation on Wikipedia. What next, are we going to stop people like Doc James from being allowed to submit DYK nominations on medical topics because he is paid! to be a doctor? Wittylama 14:56, 1 February 2018 (UTC)
- WiR/GLAM editors are supposed to use the resources of their host institution to improve articles (e.g. images from the British Museum to illustrate articles about art or archeology). When a WiR/GLAM editors writes about their host institution (in this case, faculty at their employer's institution) they are solidly in COI territory. This is discussed at Wikipedia:Conflict_of_interest#Wikipedians_in_residence,_reward_board and see also the guidelines on meta. Jytdog (talk) 03:09, 30 January 2018 (UTC)
- Oppose: As much as I am against paid editing in general, I am against adding anymore additional unnecessary rules to DYK. Notability and promotional concerns should be dealt with at the nomination page for what it is; as long as the article and hook conforms to policy and guidelines, I have no issues with them appearing on DYK. Alex Shih (talk) 07:13, 30 January 2018 (UTC)
- To clarify, I support disclosure, but any signs of UPE should be subject to immediate block already. I oppose adding this additional rule to prohibit editors with COI from DYK, as I think the rule would be unnecessarily redundant. Alex Shih (talk) 06:23, 31 January 2018 (UTC)
- Oppose: Mostly per TRM. Wikipedia already has site-wide guidelines regarding Paid/COI, the existing DYK guidelines are (for the most part) concerned with the quality of the article not who made it. Notability is handled by AFD. Only in death does duty end (talk) 10:00, 30 January 2018 (UTC)
- Oppose Although I am against concept of paid-editing in its entirety, I don't see any benefit that this proposal will provide or the problem it is seeking to solve. If content (paid, unpaid or unknown) passes all other criteria and makes it to the last hurdle of DYK I see no point of barring it, after all it is just few hours that they remain on the main page. Without detailed problem that paid articles caused on the mainpage, this looks like a solution in search of problem. –Ammarpad (talk) 10:33, 30 January 2018 (UTC)
- Oppose per WP:BITE, WP:BURO and WP:CREEP. DYK is intended for new content and so is especially suitable for new editors. Naturally, these may come with some baggage but it's part of our mission to help them integrate well. For example, I nominated a bunch of articles for DYK which were written by the Women's Classical Committee. This group naturally includes lots of women classicists and so, in promoting their academic field and gender, they have a vested interest and some of them are professionals. But such an interest is true of most of our content creators who naturally prefer to write about things that interest and involve them. So long as the material is of reasonable quality and presented to us in good faith then it's fine. Andrew D. (talk) 13:18, 30 January 2018 (UTC)
- Oppose as, once again, the Wikimedian in Residence baby is in danger of being thrown out with the spamming bathwater. (Disclsoure: I am often paid as a Wikimedian in Residence). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:44, 30 January 2018 (UTC)
- There are two proposals; it is becoming unclear as to what people are !voting on. (people are also using the words "oppose" and "support" in opposite ways, which is going to make the close difficult) Jytdog (talk) 15:09, 30 January 2018 (UTC)
- No and No - Yes, those are two different proposals but I oppose both. 1) DYK is not the place to deal with undeclared PAID/COI problems. If someone lied when creating the article, they won't admit it during DYK review and there is nothing DYK-specific to be done in those cases anyway. And 2), if an article is created in compliance with policy, it hould be eligible for DYK. It would be counterintuitive if we banned articles from DYK that are otherwise not treated differently. Regards SoWhy 15:17, 30 January 2018 (UTC)
- No and No. The Rambling Man expressed it best for me. Gerda Arendt (talk 15:28, 30 January 2018 (UTC)
- Support ban Wikipedia is not a means of advertising or promotion. We have had examples in the past where paid editors use their ability to nominate a page for DYK as a means of soliciting future clients. If having a Wikipedia page can be an advertisement in itself, regardless of the neutrality of the wording (which I very strongly believe to be the case), then having the article appear on the main page is even more so. Putting paid advertisements on the main page is against everything Wikipedia stands for, and is arguably native advertising, which brings with it legal considerations in several jurisdictions. Under no circumstances should we allow this. TonyBallioni (talk) 15:31, 30 January 2018 (UTC)
- Support ban. Even asking the question is like, there's this guy going around the neighborhood selling stolen auto parts, shouldn't we buy them if he's offering a good price? No. The answer is No. – Athaenara ✉ 15:35, 30 January 2018 (UTC)
- By the way, Wikipedia:Conflict of interest/Noticeboard#Tony Ahn PR/Reputation Management has a long discussion of one of the most cynical examples of this, someone who knew the ins and outs of Wikipedia and how to persuade innocent non-promotional editors to support his sleazy cause, he prided himself on getting his clients DYK'd and hence on the main page. – Athaenara ✉ 15:41, 30 January 2018 (UTC)
- And related: Template:Did you know nominations/Tony Ahn. – Athaenara ✉ 15:53, 30 January 2018 (UTC)
- Support ban NOTPROMO and all that - even if the article is neutral, appearing on the main page for promotion shouldn't be allowed, which is the general aim of paid editors in DYK.... Galobtter (pingó mió) 16:15, 30 January 2018 (UTC)
- WP:NOTPROMO does not say that articles that conform to the rules can be treated differently because of who created them. Regards SoWhy 17:00, 30 January 2018 (UTC)
- Support/Oppose Support disclosure but oppose the ban. Emir of Wikipedia (talk) 16:27, 30 January 2018 (UTC)
- Oppose Not necessary. Symptom of moral panic. Disclosure as standard. !dave 18:40, 30 January 2018 (UTC)
- The only people panicking anytime that phrase is brought up is the people panicking over the moral panic that doesn't exist. En.wiki policy is already clear that spam is not allowed (which in a way makes this conversation redundant, as even a neutrally written advertisement is still an advertisement, and thus forbidden by policy), and those of us who favour a tougher stance on it are simply trying to make sure existing policy is enforced. Please stop decrying this moral panic: if it exists, it is not on the side you think it is on. TonyBallioni (talk) 18:55, 30 January 2018 (UTC)
- Oppose both disclosure and ban. The Wikipedian in residence issue is of particular concern, as noted above, but also this would apply to things like institutional editathons. Let's not make some editors wear a Scarlet Letter, and also open the door to endless debate over where the line is. It is clear from other guidelines that, for example, a history professor can write about history, a biochemist can write about biochemistry, the "hard line" is if someone is PAID to write a SPECIFIC article, not if they happen to be editing wikipedia during their work time. Frankly, the extreme (and absurd) application of this would argue that if you have any knowledge about anything at all, and maybe once had a job doing it, then you must have a COI. By that standard, EVERYONE has a COI. Example, I'm a lawyer, so do I have a COI any time I edit an article on a legal topic? I think not. Their article and editor is either in line with policy or it is not. DYK has enough to do without having to play COI traffic cop too. Montanabw(talk) 18:56, 30 January 2018 (UTC)
- Oppose. DYK is a subset of article writing; we don't need more warnings and labels. In this case an excellent COI disclosure was added to the talk page. I would argue that we don't need to know there is a COI to recognize writing that is spam. Are we all nit wits? What happens if we start to label everything is that, one, we lose the ability to discriminate for ourselves and two, we bias ourselves. In this case if the article was not neutral BHG might have gone to the editor's page and noted the COI then taken some action. (Not a criticism of BHG just another approach) We are sailing in the water of totalitarian control, power in the hands of a few which I personally don't like. The encyclopedia that anyone can edit is not the encyclopedia that a few can control. Already we have issues: WiR is being conflated with COI issues and this has given some the implied permission to harass. Second, positive content is being confused with COI/spam /advertising as we become almost fixated on COI. Some warning/ notice labels are fine; too many and we are creating problems for ourselves and have lost sight of the founding statement which is unique in its simplicity and ease- the encyclopedia anyone can edit. Note I am not advocating for COI editing here just for the tone that comes when we don't lose sight of the overarching goal of the encyclopedia. When we become fixated on an issue the ease is gone and so probably the editors. The editor in this case may become a good Wikipedia editor as she moves from what she is doing now to other areas. She needs support not more regulations.(Littleolive oil (talk) 20:30, 30 January 2018 (UTC))
- Oppose broadly as it's already taken care of by other processes; agree with Alex Shih. Hmlarson (talk) 22:56, 30 January 2018 (UTC)
- Oppose Already the article has to be within policy, which includes disclosure of paid editing, lack of promotion, and neutrally written. Also the topic has to be notable enough to be retained. Anyway I do not think an extra rule is required. I would be more concerned about the QPQ reviews of such people. Every one has some sort of I in the COI, so the standard checking should reveal if COI causes a bias. Graeme Bartlett (talk) 23:08, 30 January 2018 (UTC)
- support disclosure -- consider a possible ban later. The motivation for this is that at lease some paid editors have been usign their ability to get DYKs as a credential. amd therefore have a motive in tryingtoget DYKs that would not otherwise be featured. Thenomination process needs to make sure to consider this element in the decision. DGG ( talk ) 03:07, 31 January 2018 (UTC)
- Oppose per TRM and Joseph2302. Double sharp (talk) 03:26, 31 January 2018 (UTC)
- Support a total ban on DYK nominations from paid editors and even DYK that include contributions from paid editors. I make no secret of the fact that I support a total ban on paid editing in all its forms except perhaps for WIR. There is no foundation in claims that allowing any form of paid editing will encourage paid editors to declare theier activity which is but a very small tip of an extremenly large iceberg that is already undeground (under water?) The last place we want their spam or advertorial is on the mainpage. Kudpung กุดผึ้ง (talk) 06:16, 31 January 2018 (UTC)
- Oppose as a classic case of throwing the baby out with the bathwater. At Wikipedia:Articles for deletion/Denise Stephens, I see one editor has commented "Are we here to build an encyclopedia? Or to run a fanzine for football fans and porn users?" Well no, we do a good line on disused railway stations too .... but again, I think people are missing the wood for the trees. If an article written by a paid editor is that bad, we already have WP:CSD#G11. Ritchie333 (talk) (cont) 17:36, 31 January 2018 (UTC)
- Oppose but support disclosure, per DGG. Gatoclass (talk) 20:09, 31 January 2018 (UTC)
- Support a ban that explicitly excludes GLAM editors and Wikipedians in Residence. Gamaliel (talk) 20:31, 31 January 2018 (UTC)
- Oppose in favor of just going with existing paid/COI policy. Don't see why we need a special case here. --SarekOfVulcan (talk) 21:29, 31 January 2018 (UTC)
- Support. The "focus on content, not the contributor" arguments fail to recognize the fact that, except in the most obvious cases, volunteer amateurs generally cannot identify the promotional content inserted by marketing professionals. The claim that the restriction would deter good-faith COI contributors from disclosing is a slippery slope leading to abolishing all COI regulations, which is absurd. I think we need to find a way to systematically distinguish the GLAM, WiR and other potentially productive paid editors from the undesirable kind of paid advocates that most of us would like to get rid off. I often see policy proposals aimed at the latter opposed by those who think of the former, which I think is very unfortunate. Rentier (talk) 21:47, 31 January 2018 (UTC)
- @Rentier: "The "focus on content, not the contributor" arguments fail to recognize the fact that, except in the most obvious cases, volunteer amateurs generally cannot identify the promotional content inserted by marketing professionals." I can't easily find a way of calculating how many of the 5,800 articles I have deleted were because of WP:CSD#G11 "Unambiguous advertising or promotion", but I would be surprised if I have deleted less than 2,000 articles as blatant spam. Do you have any examples? Ritchie333 (talk) (cont) 11:56, 1 February 2018 (UTC)
- Support both proposals, with an exception to the ban for GLAM/WiR editors only when "using the resources of their host institution to improve articles", as Jytdog describes above. DYK is especially attractive to promotional/COI editors due to its prominent placement and relatively easily satisfiable requirements. A bright-line rule is necessary to deter them. James (talk/contribs) 23:40, 31 January 2018 (UTC)
- Oppose, I'm sympathetic to #1 but ultimately if they're playing by the rules then they should already have disclosed in accordance with the TOU their paid editing status. Totally opposed to #2; if the content is good enough to meet DYK's standards then why shouldn't it be put up there? Biased content should be rejected for being biased, not because of it's origin. Lankiveil (speak to me) 01:52, 1 February 2018 (UTC).
- Strong oppose both. The first part per The Rambling Man - there is nothing to be gained from a special rule and potential for it to cause problems. The second part per Joseph2302's comments about discouraging compliance with the COI and disclosed paid editing policies. If someone is a disclosed paid editor there are enough rules in place already, and if they add content suitable for a DYK listing then they're improving Wikipedia which is something we should encourage not restrict. If they aren't following the rules about paid editing that currently exist, why would they follow any new ones? If someone is engaging in spamming, intentional non-neutral editing, etc, then they should not be near the mainspace regardless of whether they are paid or not. Thryduulf (talk) 04:13, 1 February 2018 (UTC)
- Strongly support disclosure, and support blanket ban. There's too much pressure from promoters wanting their promotional material to appear here, and too much potential for the whole DYK process to become corrupted by promotional material. Better to put a clean stop to it. —David Eppstein (talk) 19:20, 1 February 2018 (UTC)
- Can you provide any examples in the last two years that support your claims? The Rambling Man (talk) 20:24, 1 February 2018 (UTC)
- Oppose per Hawkeye7. We already have measures to check CoI editing. Chris Troutman (talk) 21:02, 1 February 2018 (UTC)
- Strongly support disclosure: we have other sensible disclosure rules in place already and this seems like just another obvious one to make it clear to everyone involved that a major contributor has been paid for their work. Support ban for those who are paid specifically to get a DYK (so in this instance it would not apply, as the user clearly states on their userpage that they are paid by the hour and not by DYK), but I am neutral on a ban for other paid contributors (not including WiRs). I am frankly very surprised at the consensus forming on this page – though I wasn't around for Gibraltarpedia, and don't know the exact situation, I would have thought that a very strong rule would already be in place to stop that sort of thing from happening again (rather than, I understand, a very short-sighted plan discussing only the specific Gibraltar case). — Bilorv(talk)(c)(e) 16:53, 2 February 2018 (UTC)
- Disclosure is already required by site-wide policy. The Rambling Man (talk) 17:50, 2 February 2018 (UTC)
- Oppose per TRM: if it improves Wikipedia, no problem. As with all articles featured at DYK, an article created by a COI editor should meet all relevant guidelines, including the Terms of Use, thus disclosure should naturally be expected and no explicit DYK-specific requirement should be set in this regard. It is up to editors to scrutinize articles created by COI editors more thoroughly, though the mere fact that the article was paid to be written should not affect its DYK eligibility at all, as long as other criteria are met. feminist (talk) 16:01, 5 February 2018 (UTC)
- Oppose: Overkill solution to a small problem. Esquivalience (talk) 20:53, 5 February 2018 (UTC)
- nah I understand the idea here, the very concept that you can buy exposure on the main page is contrary to everything Wikipedia is about. But as many others have already said, we already ave policies tht cover this, and if those policies are being followed there is no need for DYK to ahve astricter standard. Beeblebrox (talk) 23:36, 5 February 2018 (UTC)
- Yes and No (as former Wikipedian in Residence, though I don't believe I personally did any DYK's as part of this). Disclose in the nom, but should not be banned. Johnbod (talk) 02:30, 7 February 2018 (UTC)
- Oppose banning, support disclosure. Banning all paid editing from DYK is an overreach since it's UPE is already against the rules, but getting notice that some more caution in assessing the article is required is fine, given that successful DYKs will end up on the main page. ---- Patar knight - chat/contributions 15:55, 7 February 2018 (UTC)
- Support disclosure as second choice; first choice is ban. Coretheapple (talk) 16:34, 7 February 2018 (UTC)
- Oppose ban - Assuming paid editing has been properly disclosed, one topic is just as valid as the next. Play the ball, not the ballplayer... Carrite (talk) 00:56, 9 February 2018 (UTC)
Simple wording
This should be non-controversial. We already have a policy and a guideline to deal with this. Some folks have already said that we should just follow these, but others seem to be arguing for a special exemption for DYK from them.
Perhaps the most relevant part of the guideline is that COI editors (which includes paid editors) "should make the disclosure on your user page, on affected talk pages, and whenever you discuss the topic," (bolding added) which includes the DYK template. So I'll propose the following simple wording
Paid editors and other editors with a conflict of interest should declare this when nominating an article for DYK. The article's talk page should also contain a COI or paid editor disclosure. Any deviations from the WP:PAID policy or the WP:COI guideline should also be reported, either on the template page or at WP:COIN.
Support as proposer. Smallbones(smalltalk) 16:16, 30 January 2018 (UTC)
- The original question 1 did not assume that the editor paid for editing the article in question was making the nomination. Did you want to propose wording that covers the case where an editor is nominating an article that was created/expanded by someone else who is a paid editor? The case where the nominator is the paid editor for the nominated article is already covered by existing policy. isaacl (talk) 16:51, 30 January 2018 (UTC)
- Well the specific case discussed was a self-nom, but to make it clear I added "The article's talk page should also contain a COI or paid editor disclosure." (and further bolded the WP:COI extract to include on affected talk pages, and whenever you discuss the topic," (bolding added)). That should cover it and avoid the question of "What if the nominator didn't know the article was paid for." Smallbones(smalltalk) 17:20, 30 January 2018 (UTC)
- Note: Tony Ahn and his crew, as discussed at length in the COI/N discussion I linked above, were experts at getting other editors to ride point for them on these things. – Athaenara ✉ 17:33, 30 January 2018 (UTC)
- Of course if you are nominating a DYK at the behest of a paid editor - that should be disclosed per WP:COIRESPONSE and WP:COIATTRIBUTE. And the proposed wording avoids the exceedingly rare case of "What if the editor who nominated the article at the behest of a paid editor didn't know that the paid editor was paid?" In general IMHO we should avoid letting extremely rare "borderline" cases determine what we decide here. Trying to make this complete for every possible case just makes it complex and opens other interpretations and borderline cases, and plays into the hands of paid editors. Let's just stick with the sense of the current policy and guideline. Smallbones(smalltalk) 17:53, 30 January 2018 (UTC)
- I feel the current policy and guidelines on disclosure are enough when paid editors are nominating their own articles. So the only additional case covered by question 1 is as follows: Let's say there are nice paid editors who just want to improve Wikipedia's articles (maybe Wikipedians-in-residence). So they create articles and don't ask anyone to nominate them for DYK. Then an editor who goes through new pages looking for DYK opportunities sees an article and nominates it. Maybe it's more important to remind reviewers to look at the article talk page for disclosure notices. isaacl (talk) 18:35, 30 January 2018 (UTC)
- Of course if you are nominating a DYK at the behest of a paid editor - that should be disclosed per WP:COIRESPONSE and WP:COIATTRIBUTE. And the proposed wording avoids the exceedingly rare case of "What if the editor who nominated the article at the behest of a paid editor didn't know that the paid editor was paid?" In general IMHO we should avoid letting extremely rare "borderline" cases determine what we decide here. Trying to make this complete for every possible case just makes it complex and opens other interpretations and borderline cases, and plays into the hands of paid editors. Let's just stick with the sense of the current policy and guideline. Smallbones(smalltalk) 17:53, 30 January 2018 (UTC)
- Note: Tony Ahn and his crew, as discussed at length in the COI/N discussion I linked above, were experts at getting other editors to ride point for them on these things. – Athaenara ✉ 17:33, 30 January 2018 (UTC)
- The thing to do would be include it in the template for creating the DYK nomination. This looks fairly easy if we can get consensus for it. Jytdog (talk) 18:10, 30 January 2018 (UTC)
- That would really be all that is needed. I'd hope folks would also read WP:PAID and WP:PAY. Smallbones(smalltalk) 19:46, 30 January 2018 (UTC)
- Comment. There's a difference between paid editing and paid advocacy. Wikipedians-in-Residence fall in the former category but not the latter. (I myself am a Wikipedian-in-Residence, and use an alternate account when editing in that capacity.) It's appropriate and probably a good idea for Wikipedians-in-Residence to disclose their status on the DYK nomination page, but it's not current practice to do a talk page declaration. The wording of any provision like this should take into account how it affects both commercial paid editors and Wikipedians-in-Residence. FWIW, WP:PAID requires disclosure "on their main user page, or on the talk page accompanying any paid contributions, or in edit summaries," emphasis added; only one of these is required. Antony–22 (talk⁄contribs) 07:16, 3 February 2018 (UTC)
Discussion
For those opposing disclosure of any COI here at DYK, can you please explain how the community should avoid another debacle like the Gibraltarpedia matter? The heart of the scandal was that the project had seventeen DYKs in a single month, and one of the editors organizing it (and doing DYK nominations) was being paid by the Gibraltar Tourism Board for organizing the project. Whatever you think of paid editing or GLAM stuff, the optics of that were terrible, and this is what was made hay of in the press, and damaged the reputation of Wikipedia. It was actually a thread at this talk page, here, that first raised that issue, as was reported on here for example.
In my view if the COI is disclosed then the people who work this board at least can be aware of what is going on, review the nomination with the COI in mind, and can consider whether something is getting (to import a policy that may not usually be applied to the trend in DYKs) UNDUE weight. I don't much care for blanket bans or more "regulation" but disclosure locally is really just common sense.
Those who don't learn from the past, blah blah.
So, I am interested in hearing a response to that from folks like User:The Rambling Man amd User:SoWhy, and anybody else of course. Jytdog (talk) 15:47, 30 January 2018 (UTC)
- Yet another false extrapolation. No-one is "opposing disclosure of any COI here at DYK". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 30 January 2018 (UTC)
- I don't know why you thought I said that. I said we should comply with the site's blanket approach to COI and paid editing. Read my statement again. The Rambling Man (talk) 16:30, 30 January 2018 (UTC)
- What he said. COI is not a problem of DYK, it's a site-wide problem. The proposal here was to institute a special check at DYK and that's something we don't need. We should treat articles created in violation of PAID/COI like the rest of the project does, not create special DYK rules or procedures. Regards SoWhy 16:53, 30 January 2018 (UTC)
- User:The Rambling Man and User:SoWhy, the COI guideline calls for local disclosure. Why would you then oppose having COI disclosed as part of the DYK template which would indeed be exactly in line with sitewise guidance? Jytdog (talk)
- Because we don't need to repeat site-wise guidance at every hierarchical step of Wikipedia. We don't do it for V or RS or NPA or other policies, why we'd pick this one and roll it out at just one or two "key" locations, I know not. Anyway, I've made my point abundantly clear so no more badger cheers. The Rambling Man (talk) 19:04, 30 January 2018 (UTC)
- "V" is a policy, not a stage an article goes through where we are actually evaluating it. DYK is much more akin to say AfC where we very much look for local disclosure of COI so the reviewers there, review with the COI in mind. Other similar stages an article goes through are GA or FA review, and I would expect COI/PAID to be disclosed locally there as well. The primary reason disclosure is made, is so that review can be done with disclosure in mind. That is what disclosure is for- it is not just some silly checkbox we tack here and there randomly. Jytdog (talk) 19:15, 30 January 2018 (UTC)
- My guess is that checking for verifiability is already ingrained in DYK reviewers, so they already are well aware to make appropriate checks. How about we add item 4(b) to the eligibility criteria, to examine if there are any signs that appropriate disclosures have not been made? isaacl (talk) 20:03, 30 January 2018 (UTC)
- Fail, DYKs frequently fail on V, even after they've been reviewed. Local disclosure is covered by the site-wide guidance. Nothing more needs to be added here. If someone is going to hide it, they'll hide it. If someone inadvertently fails to state it, yet the article gets passed (!!) by the DYK review "process", (and even after being re-reviewed by an independent reviewer), there's no actual harm done to the encyclopedia. That's all there is to it. Now, remember, no badgers! The Rambling Man (talk) 20:27, 30 January 2018 (UTC)
- Sorry, I guess I should have worded that differently: I disagreed with the previous statement that verifiability isn't something to be evaluated by DYK reviewers. Perhaps it should be given a subitem under eligibility criterion 4. isaacl (talk) 20:53, 30 January 2018 (UTC)
- Fail, DYKs frequently fail on V, even after they've been reviewed. Local disclosure is covered by the site-wide guidance. Nothing more needs to be added here. If someone is going to hide it, they'll hide it. If someone inadvertently fails to state it, yet the article gets passed (!!) by the DYK review "process", (and even after being re-reviewed by an independent reviewer), there's no actual harm done to the encyclopedia. That's all there is to it. Now, remember, no badgers! The Rambling Man (talk) 20:27, 30 January 2018 (UTC)
- My guess is that checking for verifiability is already ingrained in DYK reviewers, so they already are well aware to make appropriate checks. How about we add item 4(b) to the eligibility criteria, to examine if there are any signs that appropriate disclosures have not been made? isaacl (talk) 20:03, 30 January 2018 (UTC)
- "V" is a policy, not a stage an article goes through where we are actually evaluating it. DYK is much more akin to say AfC where we very much look for local disclosure of COI so the reviewers there, review with the COI in mind. Other similar stages an article goes through are GA or FA review, and I would expect COI/PAID to be disclosed locally there as well. The primary reason disclosure is made, is so that review can be done with disclosure in mind. That is what disclosure is for- it is not just some silly checkbox we tack here and there randomly. Jytdog (talk) 19:15, 30 January 2018 (UTC)
- Because we don't need to repeat site-wise guidance at every hierarchical step of Wikipedia. We don't do it for V or RS or NPA or other policies, why we'd pick this one and roll it out at just one or two "key" locations, I know not. Anyway, I've made my point abundantly clear so no more badger cheers. The Rambling Man (talk) 19:04, 30 January 2018 (UTC)
- User:The Rambling Man and User:SoWhy, the COI guideline calls for local disclosure. Why would you then oppose having COI disclosed as part of the DYK template which would indeed be exactly in line with sitewise guidance? Jytdog (talk)
- What he said. COI is not a problem of DYK, it's a site-wide problem. The proposal here was to institute a special check at DYK and that's something we don't need. We should treat articles created in violation of PAID/COI like the rest of the project does, not create special DYK rules or procedures. Regards SoWhy 16:53, 30 January 2018 (UTC)
- The key question is on how many guidance pages are we going to put reminders to comply with Wikipedia's terms of use? There are lots of embarrassing situations that can arise, some of them with non-paid editors too. It's a gradual tragedy of the commons: sure, it doesn't hurt to put one more reminder about X on page Y, but as more and more points are added to more pages, people are less likely to read and retain the details. And paid editors interested in following the rules only need to read about the disclosure requirements once; protests from them that they didn't see a mention in subsection XYZ on guidance page ABC aren't valid excuses. isaacl (talk) 17:00, 30 January 2018 (UTC)
- Actually, there is only one page that really needs a clear reminder, i.e. Special:CreateAccount. If there was a big message that undisclosed paid editing is forbidden when people register their account, no one could ever claim to not have known about it. Regards SoWhy 17:08, 30 January 2018 (UTC)
- "those opposing disclosure of any COI here at DYK": I am not one of those, the question wasn't "any", at least I understood that the question was if we need "extra" declaration on top of what is required project-wide, and I say "No". The normal declaration on user and article is enough for me. --Gerda Arendt (talk) 17:10, 30 January 2018 (UTC)
- So this thread arose, because a DYK reviewer felt that they "discovered" that the nominator was a paid editor instead of having that simply diclosed locally. This is something that happens to people, when they assume they are dealing a volunteer and find out after the interaction begins that the person has a COI of some sort.
- This sort of unpleasant surprise happens, and when it does, it is kind of icky for everybody, and is easily avoided. This is why the COI guideline calls for people to disclose locally. Jytdog (talk) 18:08, 30 January 2018 (UTC)
- And the local disclosure is mandated by the site-wide guideline: COI editors (which includes paid editors) "should make the disclosure on your user page, on affected talk pages, and whenever you discuss the topic," (bolding added). i.e. disclosing on this page is not an extra disclosure, simply the same type of disclosure required from everybody. Smallbones(smalltalk) 18:13, 30 January 2018 (UTC)
- "mandated" is not really the appropriate word. These discussions about COI become so difficult because so there is some much ...overloading and misdirection. Jytdog (talk) 18:33, 30 January 2018 (UTC)
What about having paid editors perform two or three reviews for every one they submit? This is somewhat apart from the specific question(s) on the table above. DYK, as with other "formal" community processes (e.g. I'd like to see the same thing at GAN) requires a great deal of time/effort by volunteers -- time/effort which is spread quite thin at times. Paid editing is allowed, and can be done in a way that follows community policies and guidelines as well as the terms of use. But when paid editing activities place a great burden on structured community processes, it doesn't seem unreasonable to ask for a little extra engagement with those processes. Sorry if this has already been suggested somewhere above -- coming to this when it's already rather long. :) — Rhododendrites talk \\ 23:04, 30 January 2018 (UTC)
- Honestly I would rather that paid editors didn't do any reviews at all, too much risk of QPQ between paid editors. — Insertcleverphrasehere (or here) 23:39, 30 January 2018 (UTC)
- If they're required to disclose, that would be rather transparent if we had a rule against doing so. Doesn't seem like something that would preclude having them do 2 reviews. Of course that's presuming there is not a ban on it (which it does not look like there is going to be). — Rhododendrites talk \\ 00:22, 31 January 2018 (UTC)
Hi everyone. Skyes(BYU) is one of my student workers. She just started working this month. I do review the pages my students work on but there is no substitute for having feedback from other editors, so thank you for that. I think the process of going through DYK is more rigorous than a new page patrol and if anything, it provides a good check on the neutrality of new pages. There is a real problem with gender imbalance in the hard sciences in Mormonism, and I felt like we could work to combat this by making pages for Mormon women in hard sciences. I made Cynthia B. Lee and had a successful DYK nomination with her page, but I think the key difference is that she doesn't work at BYU. Skyes(BYU) made Laura Bridgewater as part of this effort and most recently the Denise Stephens page. I've also worked on pages of other previous BYU professors because we had their papers in special collections. Obviously, I'm opposed to banning paid editors from DYK nominations. I am open to hearing a good solution to frequent disclosure of my paid editing for a GLAM institution. Maybe I could put it in my signature? Rachel Helps (BYU) (talk) 17:05, 31 January 2018 (UTC)
- @Rachel Helps (BYU): You make a good case for my argument. I am 100% certain that a key factor that made my other half sign up to the Women in Red World Contest is that there was money involved. I myself am happy to have got some books as a prize for doing the West Country Challenge. I don't think I'd have been motivated to expand A431 road and Colston bun without some sort of hope of an intrinsic reward at the end of it. In both those articles, I really felt I was trying to squeeze blood out of a stone a bit too much just to get it past a magical 1500 character limit that would count towards a prize, and you can almost see it in the edit summaries. Of course, in my case, the reward was entirely dependent on the work being done properly. I got paid (if you count a free lunch as "paid", which I do because there ain't nothing else) for improving The Minories, Colchester and taking it through DYK, but that was more of a token of gratitude that I'd voluntarily done the work for them. PS: And thank you Wittylama for expressing my views more eloquently than I have been able to.Ritchie333 (talk) (cont) 17:54, 31 January 2018 (UTC)
- Comment it may just be my take on it but here it is, summed up:
- We have a site-wide policy on paid editing and COI, so it doesn't need repeating.
- If editors avoid scrutiny and get away with paid editing or COI but it's not picked up during the DYK review process then it should be just fine, after all the DYK process is designed to assess quality for main page inclusion.
- If editors don't want to confess to paid editing or COI, trying to make them declare it will have no impact. Obviously.
- If editors are subsequently found to have paid edited or edited contrary to COI, they will be blocked/banned per the site-wide policy.
- If editors have succeeded in getting an article to "DYK standard" without being exposed to the COI/paid editing policy, (a) that's amazing and (b) oh well, they've improved Wikipedia at someone else's expense.
- We don't repeat policies and guidelines at every hierarchical step down the chain from the five pillars.
- The fear of promotional floods is completely and utterly unfounded. The reviewers and promoting admins will spot this kind of thing. And as I've said already, even if they don't and the articles are in decent condition, hey ho, the encyclopedia just got a little bit better. The Rambling Man (talk) 20:23, 1 February 2018 (UTC)
- Agreed. Not to mention when we have had floods of articles on similar topics, it gets managed appropriately as DYK is capable of self-regulating these things by limiting the flow. Gibraltarpedia and recently WIR are good examples of how we have controlled this. The C of E God Save the Queen! (talk) 18:18, 2 February 2018 (UTC)
Template:Did you know nominations/Trump Street - a controversy-sparking, ticking time bomb... right where we don't need it
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
This request has been handled by the appropriate administrator, Ceranthor, who erroneously approved a hook. There is to be no more discussion or jokes made about the AP2 topic area. |
---|
The following discussion has been closed. Please do not modify it. |
I know we like to "hook" readers in... but this is a serious accusation to make on our main page, even ff it is tongue-in-cheek type fun. I highly suggest the currently approved hooks by @Ceranthor: be correctly marked as
Other alts might be somewhat more active, with something like ALT 1 (b)... that Trump Street heads into to Russia Row? (c) ... that Trump Street careens into to Russia Row? (that might be too liberal a use of careens) (d)... that Trump Street stops in Russia Row? (e)... that Trump Street ends in to Russia Row? ATL2 That Russia Row leads to Trump Street, etc. Alanscottwalker (talk) 22:12, 31 January 2018 (UTC)
How about "DYK investigators finally mapped out Trump/Russia intersection?" It skewers all. --DHeyward (talk) 00:06, 1 February 2018 (UTC)
ALT6 continued discussion![]() Ignoring the protected DYK page, does anyone else have any support/opposition to ALT6 to add?: In addition, it should only appear as the top hook for April Fools, not on any other day (due to requiring April Fools exemption to non-'least surprise' links).
Support ∰Bellezzasolo✡ Discuss 03:33, 2 February 2018 (UTC)
|
Collapse moot smackdown
|
---|
Coffee, at this point the joke is you.
I'll leave your hat above as a monument to your need to be the big man in charge, but am copying out below the subthread that was underway. Make your argument, like the rest of us, for why one hook or another is OK or not OK, and if in the end consensus arrives at a hook you don't think is policy-compliant, then at that time you can raise it at AE or wherever it is that wiser heads decide stuff like that. But an advance supervote to shut down discussion of something that might go to Main Page two months from now? -- bullshit. I don't edit in these areas where people act crazy so maybe there's something in your supervote text above that entitles you to block me, and if so then so be it; it will simply move you closer to the desysopping that's on the horizon for you anyway – or, even more to be hoped for, hasten real action on allowing the community to reign in unfit admins. (Or maybe you'll just add me to your enemies list [3].) |
ALT6 continued discussion (again)
![Map of London showing "Russia Row" connecting to "Trump Street"](http://upload.wikimedia.org/wikipedia/commons/thumb/a/ac/Russia_Row_%26_Trump_Street_map_cropped.jpg/133px-Russia_Row_%26_Trump_Street_map_cropped.jpg)
Ignoring the protected DYK page, and now Coffee's absurd supervote, does anyone else have any support/opposition to ALT6 to add?
In addition, it should only appear as the top hook for April Fools, not on any other day (due to requiring April Fools exemption to non-'least surprise' links).
- Support - Fantastic Hook to headline the April Fools DYK. Has the advantage of being just as funny as ALT0, while not requiring the reader to click any links to make it clear that we are not actually talking about Donald Trump. This resolves the main BLP concern that applies to ALT0 raised by myself and others. I also support ALT1 should this not gain support, but to a lesser level than ALT6 as it is not nearly as funny (and ALT1 probably isn't funny enough for April Fools). — Insertcleverphrasehere (or here) 03:05, 2 February 2018 (UTC)
- Support-Smeat75 (talk) 03:11, 2 February 2018 (UTC)
- Support. Even if you believe there was a problem before with mentally impaired readers being unable to interpret an April 1 hook, the addition of the image and caption puts that to rest entirely. EEng 03:31, 2 February 2018 (UTC)
- Just to reiterate, Support for ALT6 was expressed by the following, either in the prior subthread above, or at the nom page. In listing them here I'm pinging them now to ensure they're OK with my listing them here:
- Support ∰Bellezzasolo✡ Discuss 03:33, 2 February 2018 (UTC)
- Support as per everyone above and my comments above too. –Davey2010Talk 03:39, 2 February 2018 (UTC)
- Support as a way to preserve the humor of the hook while preventing anyone sane from thinking we are actually alluding to connections between Donald Trump and the country of Russia that could cause us to be subject to discretionary sanctions while editing this page. —David Eppstein (talk) 05:21, 2 February 2018 (UTC)
- Gosh, David Eppstein, I probably should have warned you that by posting here, you risk getting blocked by Coffee. He's an admin, you know, so he has a lot of power and authority over the rest of us to tell us what we can and cannot discuss. EEng 05:28, 2 February 2018 (UTC)
- Oppose I would nominate Russia Row for AfD (which would make the hook not work), except for the fact that such a nomination would obviously be disruptive in the current situation. It's a one-block street in London that appears to not notable in any way; the references are of the type "somebody non-notable lived on this street 150 years ago, according to court papers". power~enwiki (π, ν) 05:33, 2 February 2018 (UTC)
- If the Russia Row article is AfD'd we can just unlink it in the hook. EEng 18:04, 2 February 2018 (UTC)
Esteemed fellow editors:
- We had a short detour to AE, now resolved with presumably not the result anticiapted by the admin who raised it [4].
- Since many eyes are upon us, let me state explicitly that which really doesn't need to be stated, to wit that no one here is suggesting that a BLP violation be foisted on the main page. We all want a policy-compliant hook, and given the combination of the subject matter and the main page appearance, we should be especially thorough in our discussion.
- Once our normal DYK process has arrived at a choice of hook, if someone's aggrieved they can route their concerns through appropriate channels. No more supervotes, please.
- At the AE discussion someone pointed out that some of our readers are unable to see the image and thus won't be able to incorporate it into their understanding of ALT6. I've fixed that by adding |alt==Map of London showing "Russia Row" connecting to "Trump Street".
At this point we can pick up discussion where we left off. More thoughts on the suitability of ALT6, please? EEng 18:04, 2 February 2018 (UTC)
- Support but with the reservation that "Russia" is now subject to possible deletion. Should we tell someone? The Rambling Man (talk) 18:07, 2 February 2018 (UTC)
- Putin already knows. He'll tell Trump on their daily phone call. WARNING: FORBIDDEN JOKE. DO NOT LAUGH. (Also not a very good joke, but I had to say something.) EEng 18:32, 2 February 2018 (UTC)
- Actually, it was my joke to start with, and it was funny, that we're going to delete Russia. Step away from stealing my material. The Rambling Man (talk) 18:34, 2 February 2018 (UTC)
- But since no jokes are allowed here, you're in more trouble than I am, because the greater the laugh the greater the libel. EEng 18:52, 2 February 2018 (UTC)
- Actually, it was my joke to start with, and it was funny, that we're going to delete Russia. Step away from stealing my material. The Rambling Man (talk) 18:34, 2 February 2018 (UTC)
- Putin already knows. He'll tell Trump on their daily phone call. WARNING: FORBIDDEN JOKE. DO NOT LAUGH. (Also not a very good joke, but I had to say something.) EEng 18:32, 2 February 2018 (UTC)
- Support This hook with the image on AFD, however I will say that there should also be a fallback non-image hook if we cannot get the cast iron guarantee that the image will be used in the set. The C of E God Save the Queen! (talk) 18:09, 2 February 2018 (UTC)
- What do you mean
the image on AFD
? EEng- April Fools Day. The C of E God Save the Queen! (talk) 18:20, 2 February 2018 (UTC)
Facepalm Of course. I thought you meant, you know, AFD AFD. EEng 18:22, 2 February 2018 (UTC)
- April Fools Day. The C of E God Save the Queen! (talk) 18:20, 2 February 2018 (UTC)
- What do you mean
- Support for 1/4 (or 4/1 if you write stuff the wrong way round). Definitely with the image though, it fails badly without that. Black Kite (talk) 18:37, 2 February 2018 (UTC)
- Support since my !vote was collapsed above. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 18:44, 2 February 2018 (UTC)
- NOTE: Now that Russia Row has been expanded roughly 5x by Philafrenzy, can I suggest that we also bold "Russia"? It also meets the DYK criteria (double DYK). — Insertcleverphrasehere (or here) 20:00, 2 February 2018 (UTC)
side discussion
|
---|
|
- I think bolding both is a good idea, puts the two words on an equal footing. I'll go ahead and do that. When we seem to have come to a decision I'll ping everyone who commented earlier back for a confirmation they're OK with any little changes we make like that. EEng 23:03, 2 February 2018 (UTC)
- I have another suggestion. How about if we have (pictured) twice: ... that Trump (pictured) is directly connected to Russia (pictured)? EEng 23:06, 2 February 2018 (UTC)
- I'd expect two pictures. (And so would my grandpa). Martinevans123 (talk) 23:10, 2 February 2018 (UTC)
- Pictured just at the end is fine. — Insertcleverphrasehere (or here) 23:14, 2 February 2018 (UTC)
- I agree. Adding it twice is more confusing. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 23:19, 2 February 2018 (UTC)
- OK, dumb idea on my part. EEng 05:55, 3 February 2018 (UTC)
- I agree. Adding it twice is more confusing. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 23:19, 2 February 2018 (UTC)
- Pictured just at the end is fine. — Insertcleverphrasehere (or here) 23:14, 2 February 2018 (UTC)
- Support as is, with both links bolded and (pictured) at the end, with the map, and on April Fools Day. And God bless America. nagualdesign 00:56, 3 February 2018 (UTC)
- Oppose political jokes I know I'm pissing in the wind here and that the support votes are going to carry the day, and that people here will just think I'm being a boring twat, but I don't want to silence myself out of fear of being a lone voice. I don't think an encyclopedia should be making jokes about politics/politicians. Not because of BLP reasons or possible libel or anything like that, but because an encyclopedia should be as neutral as possible in order to maintain credibility with all readers. Making jokes and creating satire is heading more in the direction of Private Eye, rather than an encyclopedia. Admittedly putting this up on 1 April ameliorates it somewhat, but not enough to convince me that it's a good idea. PaleCloudedWhite (talk) 10:58, 3 February 2018 (UTC)
- That's a perfectly fair point. These discussions often seem to get a bit "heated", don't they. One single political joke on the front page, one day a year, probably won't worry Lord Gnome too much. Perhaps this extreme rationing explains the clamour. But maybe the days of the April 1 DYK are numbered? Martinevans123 (talk) 11:24, 3 February 2018 (UTC)
- Or possibly, we could create and maintain a joke mainpage where EVERY DYK is a joke (and every other element). Eh? Eh? ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 20:50, 3 February 2018 (UTC)
- Oppose PaleCloudedWhite expressed my thoughts exactly. Factual wording does not make putting this on the main page neutral. The "joke" (I don't have any sense of humour when I edit Wikipedia, sorry) falls within the overall theme of ridiculing Trump - only one side of the political debate does that, so this is a partisan joke, the opposite of neutral. Thus, it will ever so slightly diminish Wikipedia's credibility as a neutral source of information. In my view, the proposed version is the least harmful, but still a net negative. Rentier (talk) 11:42, 3 February 2018 (UTC)
- Among the majority of Trump's supporters, WP is already considered extremely biased to the left and full of false claims, mostly because they believe things which simply aren't true. Your argument is that this would damage WP's reputation for those folk, but the reality is that it really wouldn't. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 20:50, 3 February 2018 (UTC)
- If that's true, then I consider it a good reason to avoid further antagonizing the (nearly half of Americans you characterise as) Trump supporters. Rentier (talk) 12:37, 4 February 2018 (UTC)
- Among the majority of Trump's supporters, WP is already considered extremely biased to the left and full of false claims, mostly because they believe things which simply aren't true. Your argument is that this would damage WP's reputation for those folk, but the reality is that it really wouldn't. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 20:50, 3 February 2018 (UTC)
- Support because reasons. Only in death does duty end (talk) 13:05, 3 February 2018 (UTC)
- Comment One aspect of neutrality, especially neutrality as WP defines it is choosing one's language and statements without consideration of how one side or another of a partisan readership would take it. Just as comedians traditionally mocked whomever was in office at the time (many of us will recall our recently-retired Deporter in Chief here), we should be free to choose whatever joke we like for our April 1 DYK, without consideration of whether or not it appears to be a partisan joke. As EEng previously pointed out, if we had an article on Uranium on Mt. Everest, we could equally joke that Hillary let the uranium go. I'd have supported that joke just as ardently as I supported this one. Not because of the political isle it rolls down, but because it's funny. It also being topical and relevant would also be a factor. I'd have supported that joke even more had Hillary won the election, and I don't mind admitting that I voted for her.
- Mocking and criticizing the sitting president has been described as an American tradition by far more than comedians. Foreign statesmen, journalists, authors and notable persons of all sorts have said this. WP, while striving to maintain an international editor base and readership, is nonetheless the product of America, and is used and edited mostly by Americans. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 20:57, 3 February 2018 (UTC)
- Well, quite. Political satire doesn't equate to partisan rhetoric. It's just a joke, and any public figure is fair game. The Leader of the Free World doubly so. Nor do such jokes contravene WP:NPOV since it isn't pushing any sort of POV, and the assumption that if you satirize Party A you must be a supporter of Party B is ridiculous. You'd be forgiven for not getting or appreciating a joke, but to stop other people enjoying them is the mark of a killjoy. Life is hard enough without sucking the joy out of it. Live and let live. nagualdesign 21:25, 3 February 2018 (UTC)
assumption that if you satirize Party A you must be a supporter of Party B is ridiculous
- yet somehow both the creator and the most vocal supporter of this DYK are very openly hostile to Trump. I don't buy the claim that this is apolitical (neither is it a BLP violation; I think it's just an assertion of Wikipedia's liberal bias). Off-topically, as an European, I have been stunned by the meanness that many well-educated Americans express towards the close-to-half of their society characterized as "Trump supporters". I think it matches the things that Trump sometimes says. Rentier (talk) 12:37, 4 February 2018 (UTC)yet somehow...
You've managed to completely miss the point. In a two-party political system there will of course be plenty of jokers that are partisan, but that still doesn't mean that a bit of satire must therefore be part of their rhetoric. And you're ignoring all those who don't support the opposition but still find the joke funny. By your rationale anyone with any political opinion cannot satirize the party they don't support without it being politically motivated, which is a ridiculous assumption. (I'm an European too, I don't support the US Democratic Party, I do find the pun rather amusing and I don't think that satire is at all mean. It's just a joke.) nagualdesign 13:21, 4 February 2018 (UTC)
- Well, quite. Political satire doesn't equate to partisan rhetoric. It's just a joke, and any public figure is fair game. The Leader of the Free World doubly so. Nor do such jokes contravene WP:NPOV since it isn't pushing any sort of POV, and the assumption that if you satirize Party A you must be a supporter of Party B is ridiculous. You'd be forgiven for not getting or appreciating a joke, but to stop other people enjoying them is the mark of a killjoy. Life is hard enough without sucking the joy out of it. Live and let live. nagualdesign 21:25, 3 February 2018 (UTC)
- Support Alt1 Let me first admit that I was trying to avoid this but then I saw the comment soapboxing about humor and how Wikipedia is American. All that is rather irrelevant and useless. As for the humor of it, meh -- humor is different to different people, and the differential of the humor between Alt1 and Alt6 is not measurable. My take is Alt6 is just trying too hard (as was the original alt) - I'm sure there are 'rules' of drollery about not trying too hard. Apart from humor, it is a noted coincidence, and therefore that alone makes Alt1 interesting/unexpected enough for 2018 April Fools. Alanscottwalker (talk) 21:15, 3 February 2018 (UTC)
- Strongest oppose The "joke" that avoids the BLP requires that the reader sees the picture and understands the hook talks about street. There is no guarantee a reader will see that picture (eg blind users, etc.) This makes this a clear BLP violation given that some readers will not have the benefit of the picture to understand that. --Masem (t) 23:29, 3 February 2018 (UTC)
- Sure, and you can imagine a hook which is a BLP violation if only its first half is read – and there's no guarantee a reader will read to the end of the hook, after all. EEng 05:29, 4 February 2018 (UTC)
- There's a difference between assuming a person will only read part of a hook when the entire hook is one sentence (which is their fault for stopping short), and where the key information is "buried" outside of the sentence (which is our fult). --Masem (t) 13:34, 4 February 2018 (UTC)
- Someone who doesn't consider the entirety of what we're presenting (text and image, with the image explicitly referenced in the text) is the one at fult. The fult, dear Brutus, is not in our browsers, but in ourselves.
- You know, I was just watching Jeopardy and one of the categories was "Impeached, removed or just quit"; apparently the show's producers and advertisers aren't worried about a backlash for a good-natured reference to current events, and neither should be we. (or... should we be or... I don't know...) EEng 17:53, 4 February 2018 (UTC)
- There's a difference between assuming a person will only read part of a hook when the entire hook is one sentence (which is their fault for stopping short), and where the key information is "buried" outside of the sentence (which is our fult). --Masem (t) 13:34, 4 February 2018 (UTC)
- Sure, and you can imagine a hook which is a BLP violation if only its first half is read – and there's no guarantee a reader will read to the end of the hook, after all. EEng 05:29, 4 February 2018 (UTC)
- As I've pointed out to several others: the notion that this is a BLP vio requires one to simultaneously read between the lines (which are literally about streets), while refusing to read between the lines (wherein it's obviously a joke). I'm sorry, but reading this as an attack absolutely requires the presumption of bad faith on the part of the authors. And while the most rabid Trump supporters will, in fact do exactly that; they would have done so anyways. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 00:50, 4 February 2018 (UTC)
- I fully understand the joke, it's a reasonably crafted joke. The problem is that when you strip all context from the presentation on Wikipedia, the joke is not obviously a joke and makes a very strong , yet-proven contentious claim. That's not the fault of those presenting the DYK, but it is a problem with the nature of web browsers. That's how it becomes a BLP, not by any direction action of an editor. --Masem (t) 02:30, 4 February 2018 (UTC)
- Even for blind users using screen readers, the caption on the image is really super clear about what is actually meant. — Insertcleverphrasehere (or here) 02:36, 4 February 2018 (UTC)
- OK, well what if they're blind and deaf? Huh? How do we avoid an inadvertent BLP violation then? Huh? HUH? A Braille map, you say? Well, what if they're blind and deaf and have no hands? Answer that! EEng 05:29, 4 February 2018 (UTC)
- There are other reasons that the image may not appear with the text. Mobile browsers may omit it, for example. If the key element is not part of the same text html element (the sentence with the blurb), do not assume the reader will necessarily see it. And when they can't see it , this is a BLP issue. You could preface it by saying "... on a street map of London, Trump is directly connected to Russia?", eliminating the picture and any potential ambiguity. --Masem (t) 13:34, 4 February 2018 (UTC)
- How about "... that Trump is directly connected to Russia (London connection pictured)"? EEng 16:29, 4 February 2018 (UTC)
- I'm really having trouble understanding why people take it as a given that no-one will check the links in the hook. Seriously; ignoring links in an HTML document is on par with ignoring random words in a plain text document: It's fucking stupid and it makes the whole reading pointless. The map is a great addition because it it initially seems to offer evidence, only to slap the reader in the face with the joke. WP has a standard format, and worrying about users using a browser that intentionally alters that format is just pointless: we can't predict what every browser should do, and we should not try to cater to every browser. We should simply ensure that our content works on the most common browsers, and then it's the reader's problem if their browser doesn't work. And again; anyone whose browser doesn't render the image or the alt text of the image, then gets offended by the joke has only themselves to blame because they didn't bother clicking on the fucking links. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 17:28, 4 February 2018 (UTC)
- Because most people don't check the links in a hook. Jo-Jo Eumerus (talk, contributions) 17:47, 4 February 2018 (UTC)
- What that proves is that most people who visit main page don't click the links in any given hook. But I'm pretty sure that most people who visit main page don't look at DYK in the first place, so your graph tells us nothing. EEng 18:01, 4 February 2018 (UTC)
- Congrats, you've discovered that people aren't very interested in a 900 year old volcanic eruption. I'm the kind of guy who loves reading articles about things I've never heard of before (or don't remember hearing of), and I've no particular desire to read that page. Also note that whatever DYK hook linked to that page was probably not a joke that piques an interest of approximately 70% of Americans and god knows how many non-Americans.
- And bear in mind: 50% of all people are, by definition of below average intelligence. Not clicking on links doesn't become less stupid as it becomes more popular. Writing to the least common denominator is not encyclopedic, and we have a different project for that, anyways. We write for those who are actually interested. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 18:09, 4 February 2018 (UTC)
- Because most people don't check the links in a hook. Jo-Jo Eumerus (talk, contributions) 17:47, 4 February 2018 (UTC)
- I'm really having trouble understanding why people take it as a given that no-one will check the links in the hook. Seriously; ignoring links in an HTML document is on par with ignoring random words in a plain text document: It's fucking stupid and it makes the whole reading pointless. The map is a great addition because it it initially seems to offer evidence, only to slap the reader in the face with the joke. WP has a standard format, and worrying about users using a browser that intentionally alters that format is just pointless: we can't predict what every browser should do, and we should not try to cater to every browser. We should simply ensure that our content works on the most common browsers, and then it's the reader's problem if their browser doesn't work. And again; anyone whose browser doesn't render the image or the alt text of the image, then gets offended by the joke has only themselves to blame because they didn't bother clicking on the fucking links. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 17:28, 4 February 2018 (UTC)
- How about "... that Trump is directly connected to Russia (London connection pictured)"? EEng 16:29, 4 February 2018 (UTC)
- There are other reasons that the image may not appear with the text. Mobile browsers may omit it, for example. If the key element is not part of the same text html element (the sentence with the blurb), do not assume the reader will necessarily see it. And when they can't see it , this is a BLP issue. You could preface it by saying "... on a street map of London, Trump is directly connected to Russia?", eliminating the picture and any potential ambiguity. --Masem (t) 13:34, 4 February 2018 (UTC)
- OK, well what if they're blind and deaf? Huh? How do we avoid an inadvertent BLP violation then? Huh? HUH? A Braille map, you say? Well, what if they're blind and deaf and have no hands? Answer that! EEng 05:29, 4 February 2018 (UTC)
- Even for blind users using screen readers, the caption on the image is really super clear about what is actually meant. — Insertcleverphrasehere (or here) 02:36, 4 February 2018 (UTC)
- I fully understand the joke, it's a reasonably crafted joke. The problem is that when you strip all context from the presentation on Wikipedia, the joke is not obviously a joke and makes a very strong , yet-proven contentious claim. That's not the fault of those presenting the DYK, but it is a problem with the nature of web browsers. That's how it becomes a BLP, not by any direction action of an editor. --Masem (t) 02:30, 4 February 2018 (UTC)
- Support. If you really wanted to remove all traces of ambiguity, it could say "(map pictured)" instead. Anarchyte (work | talk) 01:38, 4 February 2018 (UTC)
- That's a great idea, because it even more clearly alerts the reader, "Hmmmm... map?... wait... what?" EEng 05:29, 4 February 2018 (UTC)
- I'm not comfortable with ALT6 either and I wouldn't be comfortable promoting it. Regardless, I think you guys are really overestimating the appeal of ALT6, to me it's just another obviously deceptive DYK hook that everyone will twig is an Easter egg before they even hit it. And I think you are seriously underestimating the humour in ALT1, which employs the same humorous association but does it in a wry, understated manner that doesn't bang the reader over the head with the punch line. Some hooks just try too hard IMO and for my money this is one of them. So you can put me down as an oppose. Gatoclass (talk) 06:01, 4 February 2018 (UTC)
- Um. I completely disagree with everything you said about humor there. The wry-est version in ALT0, because it states something in an unremarkable tone and allows the reader to "get the joke" by clicking the links on their own. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 17:28, 4 February 2018 (UTC)
- But don't you think we get the same effect from ALT6, which lets the reader get the joke by glancing over at the map? (And since there's a little less effort to that, we thereby further reassure the BLP fearfuls among us.) EEng 18:55, 4 February 2018 (UTC)
- I think Alt6 is an awesome version because it changes the joke from pure deadpan snark to a bait and switch. It says "Trump's connected to Russia, proof is in this picture!" and then it's a picture of Trump St. connected to Russia Row. The target of the joke is shifted from Trump supporters to Trump haters, so that makes for a wider audience, as well. It's no longer just a joke on 31% of Americans, but a joke on the entire rest of the world! ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 13:15, 5 February 2018 (UTC)
- But don't you think we get the same effect from ALT6, which lets the reader get the joke by glancing over at the map? (And since there's a little less effort to that, we thereby further reassure the BLP fearfuls among us.) EEng 18:55, 4 February 2018 (UTC)
- Um. I completely disagree with everything you said about humor there. The wry-est version in ALT0, because it states something in an unremarkable tone and allows the reader to "get the joke" by clicking the links on their own. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 17:28, 4 February 2018 (UTC)
![](http://upload.wikimedia.org/wikipedia/commons/thumb/7/7e/Borat_in_Cologne.jpg/220px-Borat_in_Cologne.jpg)
- Look, consider Borat's "Throw The Jew Down The Well", homo-erotic wrestling, and teasing misogynistic right-wing views out of a couple of students. That's an entire film of which the whole premise is made of people not getting the joke - and yet it was hugely popular and a best-seller. This DYK hook doesn't even approach that! Ritchie333 (talk) (cont) 20:59, 4 February 2018 (UTC)
- OK, but you'll settle for A6 I hope? EEng 01:54, 5 February 2018 (UTC)
- Look, consider Borat's "Throw The Jew Down The Well", homo-erotic wrestling, and teasing misogynistic right-wing views out of a couple of students. That's an entire film of which the whole premise is made of people not getting the joke - and yet it was hugely popular and a best-seller. This DYK hook doesn't even approach that! Ritchie333 (talk) (cont) 20:59, 4 February 2018 (UTC)
- Just taking a moment, while there's a pause in the commentary, to note that nothing apparently came of [5]. Surprise! EEng 22:47, 5 February 2018 (UTC)
- Support and (map pictured) should alleviate any concerns with blind users not being able to see a map. feminist (talk) 07:42, 6 February 2018 (UTC)
- Ah, but what about people that are just incredibly stupid? Or people who've had a stroke or something and can only see things on the left clearly? Did you think about them??? I think we should provide a link to Trump's rebuttal so they can hear the truth from the horse's mouth. nagualdesign 17:12, 6 February 2018 (UTC)
- Hey, that's my shtick. Get your own. Jeesh. EEng 17:57, 6 February 2018 (UTC)
- Yes, but your jokes are just bitter partisan rhetoric, whereas I'm an European with no horse in this race and I'm just incredibly witty.[FBDB] nagualdesign 18:08, 6 February 2018 (UTC)
- Hey, that's my shtick. Get your own. Jeesh. EEng 17:57, 6 February 2018 (UTC)
- Ah, but what about people that are just incredibly stupid? Or people who've had a stroke or something and can only see things on the left clearly? Did you think about them??? I think we should provide a link to Trump's rebuttal so they can hear the truth from the horse's mouth. nagualdesign 17:12, 6 February 2018 (UTC)
Taking stock
Discussion has died down, so let's take stock. To summarize:
- The hooks that were seriously in the running were:
- ALT0 ... that Trump is directly connected to Russia? i.e. no picture
- ALT1 ... that Trump Street is directly connected to Russia Row?
- ALT6: ... that Trump is directly connected to Russia (pictured)? i.e. same as ALT0 but with the picture, and alt=Map of London showing "Russia Row" connecting to "Trump Street"; for those who don't know, that alt= is the text given to readers who for whatever reason can't view the image.
Map showing Trump St connected to Russia Row
- The overwhelming favorite hook is ALT6.
- There was a suggestion, late in the discussion, that (pictured) be changed to (map pictured), which even more alerts the reader that there's something fishy going on i.e
Anyone please feel free to push back on any of the above but for now I'll press on, assuming ALT6A is the popular choice. I do think that the supports above were somewhat ambiguous as to whether, in each case, the support-er was simply expressing a preference for this particular hook, or was (also) specifically joining in the opinion that ALT6 is policy compliant. Therefore, given the ruckus over this, I suggest we have a final round of discussion specifically on that point.
- Support ALT6A as WP:BLP compliant. There is undeniably some merit to the idea that you shouldn't have to follow the links to understand the hook – but remember this is scheduled for April 1; whether that worries you or not the (map pictured), together with the map itself (and its caption), make it clear that the hook's text isn't to be taken at face value. Concerns about exotic platforms dismembering the hook-image combination seem far-fetched. EEng 03:40, 10 February 2018 (UTC)
- Coffee suggested above that the WMF would not approve of our posting this. I therefore raised the matter with Katherine Maher, the current CEO of the WMF, when she spoke on the Future of Wikipedia, last week. She had not heard of the Trump Street connection with Russia Row before and thought it was an amusing story. When I pressed on the issue of its suitability, she made it fairly clear that we have editorial freedom for such matters and so the WMF would not intervene. It is up to us then. Andrew D. (talk) 16:03, 10 February 2018 (UTC)
- On the question of the hook choice, I myself really don't like Americanised hooks such as ALT6A and WP:ENGVAR should apply. ALT1 is my preference as the humour of the juxtaposition is not forced and it can be read in a matter-of-fact way. Our readers are smart enough to get the joke and so we have no need to fool them. Andrew D. (talk) 16:03, 10 February 2018 (UTC)
Template:Did you know nominations/Stephen Court Fire
I have another question about a DYK nomination. I am reviewing Template:Did you know nominations/Stephen Court Fire, and the nominator has responded to my feedback. However, they will not be able to address the issues I raised until February 22 at least, which is 3 weeks away. Is there a maximum amount of time that we are allowed to put DYK reviews on hold? epicgenius (talk) 14:27, 2 February 2018 (UTC)
- If the user has given a definite time at which they will return and address your concerns (presumably they are off-wiki in the interim) I see no issues with a three-week hold. If, on the other hand, they are clearly on-wiki but cannot be bothered to come over and fix issues, I personally would mark for closure fairly soon. Vanamonde (talk) 15:23, 3 February 2018 (UTC)
Seven days
Would anyone consider expanding this to a month please?Zigzig20s (talk) 09:13, 3 February 2018 (UTC)
- It already got expanded from 3 days to 7 days and I think that is sufficient. I would have to say no personally as it would lead to a slippery slope whereby it could end up being we just allow anything on. The C of E God Save the Queen! (talk) 09:23, 3 February 2018 (UTC)
- Nope. The Rambling Man (talk) 23:47, 3 February 2018 (UTC)
Natalie Grams
Something has happened to the nomination template of Natalie Grams so that it doesn't archive in the normal way. The hook is currently in Prep 4. Cwmhiraeth (talk) 06:57, 4 February 2018 (UTC)
- Try closing it now Cwmhiraeth. Gatoclass (talk) 07:30, 4 February 2018 (UTC)
- Thank you. I guess it is something to do with curly brackets and the stray bit of text under "Articles created/expanded on January 18". Something different has happened to the Riders (1993 film) template. In this case the hook is in Prep 6 and I can only archive half of the template. Cwmhiraeth (talk) 07:42, 4 February 2018 (UTC)
- Yes it's the curly brackets, for every opening pair there has to be a closing pair, and there should be a closing pair right at the bottom of the page. Try that nomination now Cwmhiraeth and see if it closes. Gatoclass (talk) 07:52, 4 February 2018 (UTC)
- Both are now correctly closed. I guess the pair of brackets that I had noticed were not at the bottom, were half way up, but I couldn't make out which ones they were. Thank you. Cwmhiraeth (talk) 08:37, 4 February 2018 (UTC)
- Yes it's the curly brackets, for every opening pair there has to be a closing pair, and there should be a closing pair right at the bottom of the page. Try that nomination now Cwmhiraeth and see if it closes. Gatoclass (talk) 07:52, 4 February 2018 (UTC)
- Thank you. I guess it is something to do with curly brackets and the stray bit of text under "Articles created/expanded on January 18". Something different has happened to the Riders (1993 film) template. In this case the hook is in Prep 6 and I can only archive half of the template. Cwmhiraeth (talk) 07:42, 4 February 2018 (UTC)
Blurb changed without informing nominator - why?
![](http://upload.wikimedia.org/wikipedia/commons/thumb/2/2c/A_group_of_mentally_ill_patients_sitting_around_and_staring_Wellcome_V0016652.jpg/370px-A_group_of_mentally_ill_patients_sitting_around_and_staring_Wellcome_V0016652.jpg)
![](http://upload.wikimedia.org/wikipedia/commons/thumb/8/8f/A_group_of_mentally_ill_patients_dashing_around_a_burning_ro_Wellcome_V0016654.jpg/370px-A_group_of_mentally_ill_patients_dashing_around_a_burning_ro_Wellcome_V0016654.jpg)
I've just discovered that the blurb I wrote for Ethel Page was changed to a far less interesting one while on the main page. This was done unilaterally, despite no one else in the DYK process raising any concerns with it. What's the point of asking people to write their own blurbs if an admin can just come in and change it willy-nilly without even consulting or informing the author? Ivar the Boneful (talk) 13:05, 4 February 2018 (UTC)
- Ivar the Boneful, admins can change anything they believe necessary to material on the main page; there is typically not time to ask. That said, you can always ask their reason (pinging Stephen to save time), since if her husband set her on fire, it's true whether accidentally or deliberately, and there are no BLP issues here, the event having occurred over a century ago. BlueMoonset (talk) 13:52, 4 February 2018 (UTC)
- Once items go to the main page, the "ownership link" disappears (and rightly so). There's not one single obligation for an admin correcting poorly phrased or inaccurate hooks at DYK on the main page to go follow it up to seek "permission" from the nominator to make the change. It's well recognised that the review process here is currently flawed, so it's highly likely that items will be modified all the up to and after posting with little affection towards those who nominated, reviewed and promoted the items in the first place. The Rambling Man (talk) 22:12, 4 February 2018 (UTC)
- TRM's right -- there's just too much going on putting out fires (see right) as hooks move along the assembly line for various interested persons to get notified all the time. If they're concerned about this, nominators and others interested really need to keep their eye on the hook as it passes through all stages up to and including its main page appearance, so they can be aware of any changes (which often are formatting, punctuation, etc.) and object if needed. That's not easy for the neophyte to know how to do, however, because it means adding a series of obscure pages to the watchlist at various times. I've thought about writing a how-to, but I worry it may cause more trouble than it prevents. EEng 00:14, 5 February 2018 (UTC)
- Once items go to the main page, the "ownership link" disappears (and rightly so). There's not one single obligation for an admin correcting poorly phrased or inaccurate hooks at DYK on the main page to go follow it up to seek "permission" from the nominator to make the change. It's well recognised that the review process here is currently flawed, so it's highly likely that items will be modified all the up to and after posting with little affection towards those who nominated, reviewed and promoted the items in the first place. The Rambling Man (talk) 22:12, 4 February 2018 (UTC)
- The hook in question was accepted during the nomination, review and promotion process by two other editors: Tryptofish and Yoninah. A consensus of three editors was thus established which should not have been overturned lightly. An issue was then raised at WP:ERRORS by The Rambling Man. The discussion can be seen in this version. Gatoclass opposed the supposed error report but Stephen made a change regardless. Ivar the Boneful subsequently protested but Stephen failed to respond. Stephen's action of editing through protection without consensus and then failing to respond to reasonable complaints about this was quite improper, being contrary to WP:PER. Ivar is quite right to be outraged by this and to seek redress. As WP:ADMINACCT explains, "Administrators are accountable for their actions involving administrator tools, as unexplained administrator actions can demoralize other editors who lack such tools. Subject only to the bounds of civility, avoiding personal attacks, and reasonable good faith, editors are free to question or to criticize administrator actions. Administrators are expected to respond promptly and civilly to queries about their Wikipedia-related conduct and administrator actions and to justify them when needed." Andrew D. (talk) 13:07, 5 February 2018 (UTC)
- I should clarify that my statement above described the way things are, given the Rube Goldberg, oh-geez-glad-we-caught-that-one state of DYK's approval and QA process. The fact that many things get to Q or main page that really do need fixing has the unfortunate effect of making changes at those late stages common, so that people get comfortable changing things that don't really need changing. I'll say it again: the QA process needs to be pushed upstream to the nom page itself, so that by the time it goes into prep the "eagle eyes" like TRM have already looked it over. Prep should only be about balancing sets, maybe something about what particular day/time a particular hook will appear, etc. The hook itself should be absolutely locked down by then. EEng 13:15, 5 February 2018 (UTC)
- I agree with Andrew Davidson's evaluation of what happened here. I'd also like to note that the change to "accidentally set her on fire" was not a malicious one, but is in keeping with the way the admins at ERRORS try to take into consideration every reader who won't understand that this is a hook. The original wording – he "set her on fire" – was a great hook; even you, EEng have to admit that, longtime hooker that you are. The addition of "accidentally" just watered it down for those readers who will never get it. Yoninah (talk) 13:27, 5 February 2018 (UTC)
- The main problem is it was factually incorrect. You don't 'set' accidental fires. You either cause an accidental fire, or you set something alight deliberately. Only in death does duty end (talk) 13:32, 5 February 2018 (UTC)
- Nonsense. "I fell asleep smoking and set the couch on fire" has no implication of intention, and if it did, then accidentally set on fire (which is what the hook was changed to) would be an oxymoron. We've got too many unread language "experts" running around. EEng 16:06, 5 February 2018 (UTC)
- In your example you didn't set the couch on fire, your cigarette did and the sentence should be changed to reflect that. When a person is said to set something afire, that implies intention. When an inanimate object is said to set something afire, it does not. --Khajidha (talk) 15:17, 6 February 2018 (UTC)
- Even more nonsensical. Except for The Human Torch, none of us can set something aflame without some intermediate instrumentality, so by your logic it is impossible for a person to "set X on fire" – it has to be the match, the cigarette, the stove left on, but not the person. But then you go on to assign a connotation to what you've just implied is an impossible situation in the first place. "He threw his match in the trash after lighting his pipe, and set the house on fire", "He dropped the candle and set the drapes on fire", "She overheated the oil and set the house on fire – these are all perfectly good passages, and imply no intention, any more than "By writing that letter he set in motion a disastrous sequence of events" implies intentionality. EEng 18:36, 6 February 2018 (UTC)
- In your example you didn't set the couch on fire, your cigarette did and the sentence should be changed to reflect that. When a person is said to set something afire, that implies intention. When an inanimate object is said to set something afire, it does not. --Khajidha (talk) 15:17, 6 February 2018 (UTC)
- Nonsense. "I fell asleep smoking and set the couch on fire" has no implication of intention, and if it did, then accidentally set on fire (which is what the hook was changed to) would be an oxymoron. We've got too many unread language "experts" running around. EEng 16:06, 5 February 2018 (UTC)
- Thanks for the ping. I think that Yoninah's description gets it right: done in good faith, but probably a net loss. Having already read the page, I cannot imagine that the fire setting could have been done as a murder attempt, and I rather doubt that any of our readers would have been bamboozled by it (and we are well past the realm of BLP). But I can see it as an attempt at greater accuracy during a hurried process. I think that the big picture is that Ivan did a real good job in starting an interesting page and crafting a brilliant hook. Please don't let this incident diminish your enjoyment of that. --Tryptofish (talk) 18:22, 5 February 2018 (UTC)
- The main problem is it was factually incorrect. You don't 'set' accidental fires. You either cause an accidental fire, or you set something alight deliberately. Only in death does duty end (talk) 13:32, 5 February 2018 (UTC)
- I agree with Andrew Davidson's evaluation of what happened here. I'd also like to note that the change to "accidentally set her on fire" was not a malicious one, but is in keeping with the way the admins at ERRORS try to take into consideration every reader who won't understand that this is a hook. The original wording – he "set her on fire" – was a great hook; even you, EEng have to admit that, longtime hooker that you are. The addition of "accidentally" just watered it down for those readers who will never get it. Yoninah (talk) 13:27, 5 February 2018 (UTC)
- I should clarify that my statement above described the way things are, given the Rube Goldberg, oh-geez-glad-we-caught-that-one state of DYK's approval and QA process. The fact that many things get to Q or main page that really do need fixing has the unfortunate effect of making changes at those late stages common, so that people get comfortable changing things that don't really need changing. I'll say it again: the QA process needs to be pushed upstream to the nom page itself, so that by the time it goes into prep the "eagle eyes" like TRM have already looked it over. Prep should only be about balancing sets, maybe something about what particular day/time a particular hook will appear, etc. The hook itself should be absolutely locked down by then. EEng 13:15, 5 February 2018 (UTC)
Comment is any of this helpful any longer? The blurb was changed because I raised a concern which was handled by an admin. If nefarious or out-of-process actions have taken place, take it to ANI or some dispute resolution or Arbcom, but nothing actually sinister or corrupt took place, let's just move on. Everything we donate to Wikipedia can be modified. Remember that folks, especially here at DYK where ownership of hooks ends the micro-second after they're "published". They're not "your hooks", they're Wikipedia's, and can be dealt with as seen fit. If anyone doesn't like that, well there are plenty of other options for getting material onto the main page, so I'd focus on those rather than the Woolworths of Wikipedia. The Rambling Man (talk) 19:56, 6 February 2018 (UTC)
- Something I have always said about promotion is that there is a lack of courtesy towards the nominators once its in the preps. Most editors don't watch all the preps and queues in case it clogs up the watchlist and don't have time to go looking in the histories for any changes. I think it would be good practice (as an unwritten rule) that if there are any substantial changes to a hook (as in adding or taking away words,) then the nominator is informed prior to the hook running as much as is practically possible. The C of E God Save the Queen! (talk) 10:53, 8 February 2018 (UTC)
- This thread is discussing changes made to DYK hooks when on the main page. If nominators can't be bothered to follow their nominations through to the main page and then get testy if they get tweaked and modified in prep, oh dear. No-one owns the hooks anyway. As for clogging up watchlists or not having time to look in the article history, those aren't serious blockers are they? I have around 9000 items on my watchlist and cope fine, and checking an article history takes all of five seconds. The Rambling Man (talk) 10:56, 8 February 2018 (UTC)
You do realise that the solution to so many of the problems DYK tears itself apart with is to have many fewer items? Say 1 set per day that are really excellent. I realise that gives people fewer chances to earn shiny things but my how much shinier they'll be. Much like when FA became much more rigorous about 10 years ago. --Dweller (talk) Become old fashioned! 11:44, 8 February 2018 (UTC)
- It's a symptom of the acceptance criteria being far too weak. Gone are the days when DYK was around to encourage new editors to have a go, this is no longer about getting fresh editors to participate and see their work in lights, basically no nominations get failed. So the backlog grows (especially when projects like WiR and WikiCup are running) and the project needs to pile it high and sell it cheap to keep up. The Rambling Man (talk) 12:07, 8 February 2018 (UTC)
- Silliness. Low acceptance criteria inevitably leads to problems with people looking after Main page. If the DYK criteria and protocols aren't fit for purpose, there are two choices: endless conflicts over ERRORS picking things up, or changing the criteria and protocols. --Dweller (talk) Become old fashioned! 12:32, 8 February 2018 (UTC)
Oldest nominations needing DYK reviewers
We have 32 older nominations that need reviewing, this time including all those that are no longer current (through January 27). Right now we have a total of 176 nominations, of which 58 have been approved. Thanks to everyone who reviews these, especially the four from last year.
Over three months old:
Over two months old:
November 22: Template:Did you know nominations/Kirsty McGuinness- November 24: Template:Did you know nominations/Amusement
December 2: Template:Did you know nominations/Long face syndrome
Over one month old:
December 12: Template:Did you know nominations/China's 100 major archaeological discoveries in the 20th centuryDecember 17: Template:Did you know nominations/Robin Lee WilsonDecember 23: Template:Did you know nominations/1976 Anapa mid-air collisionJanuary 4: Template:Did you know nominations/Pacific Architects and Engineers
Other old nominations:
January 6: Template:Did you know nominations/Fragments of HorrorJanuary 7: Template:Did you know nominations/William Chaney- January 14: Template:Did you know nominations/Sankaralinganar
January 14: Template:Did you know nominations/Gurbachan Singh SalariaJanuary 15: Template:Did you know nominations/Jérémie AzouJanuary 15: Template:Did you know nominations/Bambang SoesatyoJanuary 16: Template:Did you know nominations/Karl Maria Zwißler- January 16: Template:Did you know nominations/Juliana Walanika
January 16: Template:Did you know nominations/Denise Stephens- January 16: Template:Did you know nominations/Aubervilliers Congress
- January 16: Template:Did you know nominations/Zherichinius
- January 17: Template:Did you know nominations/History of speciation
January 17: Template:Did you know nominations/Yanmen CommanderyJanuary 17: Template:Did you know nominations/Holy Trinity Church, CorkJanuary 18: Template:Did you know nominations/Philip Jacobson- January 20: Template:Did you know nominations/Warwick Castle, Maida Vale
- January 20: Template:Did you know nominations/Henry Liebman
- January 21: Template:Did you know nominations/Reclaiming Health and Safety For All
January 22: Template:Did you know nominations/Siegfried Lorenz (baritone)- January 22: Template:Did you know nominations/John Johnson (1807-1878)
- January 23: Template:Did you know nominations/Henry V. Plummer and H. Vinton Plummer
- January 23: Template:Did you know nominations/2018 Gulf of Alaska Earthquake
- January 23: Template:Did you know nominations/Mica McNeill (two articles)
January 24: Template:Did you know nominations/General Alliance against Racism and for Respect for French and Christian IdentityJanuary 24: Template:Did you know nominations/Taivoan peopleJanuary 25: Template:Did you know nominations/Michael F. Adubato- January 26: Template:Did you know nominations/Anny Felbermayer
January 26: Template:Did you know nominations/Joan Benesh- January 26: Template:Did you know nominations/Novodinia antillensis
- January 27: Template:Did you know nominations/D. J. White (American football)
Please remember to cross off entries as you finish reviewing them (unless you're asking for further review), even if the review was not an approval. Many thanks! BlueMoonset (talk) 17:09, 4 February 2018 (UTC)
Prep 3 - Chinese/Japanese boarders
- ... that Chinese naval commander Zhang Wendan boarded a Japanese warship to exchange information on pirate activity, in a rare occasion of military cooperation between the two countries? Cwmhiraeth, Zahne, Alex Shih
Now, this will doubtless be shot down in flames by the DYK regulars, the "pile it high, sell it cheap" brigade, or whoever, but upon reading into this remarkable act of Chinese generosity, it appears that actually following a visit from the Japanese beforehand, which to me, at least, demonstrates enormous magnanimity on behalf of the Japanese, and a cultural obligation from the Chinese in this case. So, once again, while it's factually accurate, it's possibly incredibly misleading because it isolates the visit without the context of the prelude. The article as well somewhat obfuscates the chronology... The Rambling Man (talk) 21:06, 4 February 2018 (UTC)
- Ok, posting at ERRORS. The Rambling Man (talk) 05:36, 5 February 2018 (UTC)
- I don't really see your problem. Both article (Zhang Wendan) and hook reflect a slight reduction in tension between the two countries. Cwmhiraeth (talk) 06:23, 5 February 2018 (UTC)
- You "don't really see" my "problem"? Never mind. I'll leave it to others at other places to fix, especially given the continued approach of this project to issues raised here. The Rambling Man (talk) 07:17, 5 February 2018 (UTC)
- "It wasn't an error" (Statement by TRM at main page errors). Cwmhiraeth (talk) 09:47, 5 February 2018 (UTC)
- I already said while it's factually accurate, it's possibly incredibly misleading above. I think this conversation has expired, and don't worry, I won't bother you again with the numerous issues with which you may be related, I'll skip your pings. The Rambling Man (talk) 10:37, 5 February 2018 (UTC)
- "It wasn't an error" (Statement by TRM at main page errors). Cwmhiraeth (talk) 09:47, 5 February 2018 (UTC)
- You "don't really see" my "problem"? Never mind. I'll leave it to others at other places to fix, especially given the continued approach of this project to issues raised here. The Rambling Man (talk) 07:17, 5 February 2018 (UTC)
- I don't really see your problem. Both article (Zhang Wendan) and hook reflect a slight reduction in tension between the two countries. Cwmhiraeth (talk) 06:23, 5 February 2018 (UTC)
DYK is almost overdue
In less than two hours Did you know will need to be updated, however the next queue either has no hooks or has not been approved by an administrator. It would be much appreciated if an administrator would take the time to ensure that DYK is updated on time by following these instructions:
- Check the prep areas; if there are between 6-10 hooks on the page then it is probably good to go. If not move approved hooks from the suggestions page and add them and the credits as required.
- Once completed edit queue #3 and replace the page with the entire content from the next update
- Add {{DYKbotdo|~~~}} to the top of the queue and save the page
Then, when the time is right I will be able to update the template. Thanks and have a good day, DYKUpdateBot (talk) 22:07, 4 February 2018 (UTC)
- Now overdue. Pinging Maile, Alex Shih, Cas Liber, Gatoclass, or any other admin who sees this to get Prep 3 into Queue 3 as soon as practicable. Many thanks. BlueMoonset (talk) 01:59, 5 February 2018 (UTC)
- Done. — Maile (talk) 02:08, 5 February 2018 (UTC)
Hook for February 6
I had my nomination for Zhengzhou Airport riot approved in time to be put in the hooks for February 6, the riot's four-year anniversary. However, until I did it myself a couple of days ago it was not in the section for hooks with specific dates. It seems the prep areas for the corresponding queues have been done. Could someone see if my date request can still be fulfilled? Daniel Case (talk) 05:34, 5 February 2018 (UTC)
- I noticed it this morning and swapped the hook into the correct place. Cwmhiraeth (talk) 09:37, 5 February 2018 (UTC)
Queue 5
Not sure what happened here, but the bios and non-bios are bunched up together. Could an admin please move the 7th hook for Stuart Mustow up to the 4th slot, after HPgV-2? Thanks, Yoninah (talk) 17:46, 6 February 2018 (UTC)
- Pinging @Maile66: @Alex Shih: @Casliber: @Gatoclass: for help here. Yoninah (talk) 21:41, 6 February 2018 (UTC)
- I can only see two bio hooks adjacent, I don't think that's too much of an issue. There are other considerations with regard to hook order, such as alternating long and short hooks for variety and ease of reading, in fact that is always a very important consideration for me when ordering sets. I did try reordering the set in line with your request, but I think the existing order reads better. Gatoclass (talk) 22:13, 6 February 2018 (UTC)
- @Gatoclass: right, there are 2 bios adjacent (in slots 6 and 7) and 3 non-bios adjacent (in slots 3, 4, 5). I understand the need for a short hook now and then, but this back-to-back duplication is exactly what I work so hard to avoid while building prep sets. Yoninah (talk) 22:37, 6 February 2018 (UTC)
- Yoninah, the guideline regarding this issue reads: Mix your hooks up. Try to avoid having two hooks of the same general type next to one another in the update (for example, two US hooks or two bio hooks together). The keyword here IMO is try. I did try to re-sort the hooks to separate the bios, but every time I did, the set looked denser and harder to read. A hook set is not just a collection of hooks; it's an entity of its own, like a paragraph in a piece of prose. If your paragraph has lots of long sentences one after the other, it becomes tiresome to read, if you break up the monotony with sentences that vary in length, it's much more effortless. With a hook set, I think it's very important to strive for as much effortlessness as possible because readers on the main page are not looking for anything in particular and you have to try and draw them in with an attractive presentation. Gatoclass (talk) 23:09, 6 February 2018 (UTC)
- @Gatoclass: OK, I hear you. And I agree with you on balancing short and long hooks. I actually had nothing to do with building this prep set; I think hooks might have been removed and added by others to make what we have now. No problem, we're not writing prep sets for posterity. Yoninah (talk) 23:33, 6 February 2018 (UTC)
- Yoninah, I've been offline for a few hours, but looks like you and Gatoclass have come to a meeting of the minds. — Maile (talk) 00:21, 7 February 2018 (UTC)
- @Gatoclass: OK, I hear you. And I agree with you on balancing short and long hooks. I actually had nothing to do with building this prep set; I think hooks might have been removed and added by others to make what we have now. No problem, we're not writing prep sets for posterity. Yoninah (talk) 23:33, 6 February 2018 (UTC)
- Yoninah, the guideline regarding this issue reads: Mix your hooks up. Try to avoid having two hooks of the same general type next to one another in the update (for example, two US hooks or two bio hooks together). The keyword here IMO is try. I did try to re-sort the hooks to separate the bios, but every time I did, the set looked denser and harder to read. A hook set is not just a collection of hooks; it's an entity of its own, like a paragraph in a piece of prose. If your paragraph has lots of long sentences one after the other, it becomes tiresome to read, if you break up the monotony with sentences that vary in length, it's much more effortless. With a hook set, I think it's very important to strive for as much effortlessness as possible because readers on the main page are not looking for anything in particular and you have to try and draw them in with an attractive presentation. Gatoclass (talk) 23:09, 6 February 2018 (UTC)
- @Gatoclass: right, there are 2 bios adjacent (in slots 6 and 7) and 3 non-bios adjacent (in slots 3, 4, 5). I understand the need for a short hook now and then, but this back-to-back duplication is exactly what I work so hard to avoid while building prep sets. Yoninah (talk) 22:37, 6 February 2018 (UTC)
- I can only see two bio hooks adjacent, I don't think that's too much of an issue. There are other considerations with regard to hook order, such as alternating long and short hooks for variety and ease of reading, in fact that is always a very important consideration for me when ordering sets. I did try reordering the set in line with your request, but I think the existing order reads better. Gatoclass (talk) 22:13, 6 February 2018 (UTC)
Prep 3
- ... that a tripwire can be used to prevent salami attacks?
- Salami attacks redirects to Salami slicing, which is a pejorative term for a cost-cutting strategy. I'm wondering if the hook (and article) should be talking about Salami tactics, defined as "a divide and conquer process of threats and alliances used to overcome opposition"–in which case the term "salami attacks" is being used incorrectly here. Yoninah (talk) 21:28, 6 February 2018 (UTC)
- Yoninah - thanks for noticing. That would definitely be a more appropriate wikilink. I thought salami slicing was fine due to it mentioning salami tactics in the fourth paragraph of the lead, but was unaware the more appropriate article Salami tactics existed. I've updated Salami tactics to include "also known as the salami-slice strategy or salami attacks" and we may want to re-pipe there. Chetsford (talk) 22:52, 6 February 2018 (UTC)
- @Chetsford: thank you. I piped the link to Salami tactics in the hook in Prep 3. We're good now. Yoninah (talk) 23:30, 6 February 2018 (UTC)
- Thanks Yoninah, I appreciate it. Chetsford (talk) 00:55, 7 February 2018 (UTC)
- @Chetsford: thank you. I piped the link to Salami tactics in the hook in Prep 3. We're good now. Yoninah (talk) 23:30, 6 February 2018 (UTC)
- Yoninah - thanks for noticing. That would definitely be a more appropriate wikilink. I thought salami slicing was fine due to it mentioning salami tactics in the fourth paragraph of the lead, but was unaware the more appropriate article Salami tactics existed. I've updated Salami tactics to include "also known as the salami-slice strategy or salami attacks" and we may want to re-pipe there. Chetsford (talk) 22:52, 6 February 2018 (UTC)
Prep 6 - ... that the seeds of the Bredasdorp sceptre are carried underground by ants?
Why is this interesting? Indeed, we have a whole article dedicated to the dispersal of plant seed by ants at Myrmecochory. Is this an attempt to find something, just anything, to get the article onto the main page? The Rambling Man (talk) 22:14, 6 February 2018 (UTC)
- Ok, I agree that it is tricky to find things of interest...but I think if you're a kid or wanting to learn more about nature then it is interesting yes. A lot of people might find anything about Ipswich Town deadly boring too...Cas Liber (talk · contribs) 22:49, 6 February 2018 (UTC)
- I thought it was interesting, as I know nothing about ants. Yoninah (talk) 22:51, 6 February 2018 (UTC)
- What's been through DYK recently featuring Ipswich Town? And we've all seen videos of ants taking stuff underground. All of us. It's even featured on Ben and Holly for god's sake (they even take grandfather clocks and pianos...). The Rambling Man (talk) 22:54, 6 February 2018 (UTC)
Here's a better one: did you know that Bredasdorp sceptre doesn't even exist on Wikipedia, even as a redirect? The Rambling Man (talk) 22:56, 6 February 2018 (UTC)
Maybe you can do something with "It is a rare endemic species that is only known from ten locations near the southern coast of the Western Cape province of South Africa."? The Rambling Man (talk) 22:57, 6 February 2018 (UTC)
Or even go large with "did you know that the English plantsman Joseph Knight described Breadsdrop sceptre in his 1809 work On the cultivation of the plants belonging to the natural order of Proteeae?" "PLANTSMAN"?! And that title! The Rambling Man (talk) 23:00, 6 February 2018 (UTC)
![](http://upload.wikimedia.org/wikipedia/commons/thumb/4/4a/Paranomus_abrotanifolius_Potberg_01.jpg/220px-Paranomus_abrotanifolius_Potberg_01.jpg)
- I agree with Yoninah on this; I didn't know ants take seeds underground either, particularly seeds of a particular plant. So the hook looks fine to me. Gatoclass (talk) 23:16, 6 February 2018 (UTC)
- I also agree with Yoninah, many people dont know that plants such as the Bredasdorp sceptre rely on ants to reseed and spread. There is nothing at all wrong with the hook.--Kevmin § 02:37, 7 February 2018 (UTC)
Then if it's so interesting, the hook should link Myrmecochory to allow our readers to learn even more about the fact that this behaviour is commonplace and not in the slightest bit unique. The Rambling Man (talk) 05:34, 7 February 2018 (UTC)
- I agree with that. bluelink introduced now Cas Liber (talk · contribs) 08:59, 7 February 2018 (UTC)
- What seems to be more unusual in this instance is that the plant benefits because the underground seeds are protected from fire, rather than being protected from predators or provided with good conditions for germination. I think it's a shame this hook isn't going to feature an image; I suppose the image might be a bit fussy at a small size, but those flowers look rather incredible, like a wildly furry Cleome [6]. PaleCloudedWhite (talk) 21:15, 7 February 2018 (UTC)
- Yes, that's the point somewhat, ants take many objects away (per Ben and Holly) but this case is different from the majority it would seem. Plus you're right, that plant looks cool, the image is of a really decent resolution so it could easily be cropped to an individual flower for the benefit of the small thumb on the main page. The Rambling Man (talk) 21:21, 7 February 2018 (UTC)
OH WELL! At least the completely unremarkable fact was erroneous. The Rambling Man (talk) 19:28, 8 February 2018 (UTC)
- Erroneous in what way? AFAIK nobody until now has claimed the hook was erroneous. Gatoclass (talk) 18:35, 9 February 2018 (UTC)
Pulled hook - possible BLP issue
I pulled the following hook from p6:
- ... that the character of Rupert Campbell-Black in Riders was based partly on the late Duke of Beaufort?
The reason I did so is because of a statement in the article: In 2002, Jilly Cooper revealed that Rupert Campbell-Black was a composite of Andrew Parker Bowles, Rupert Lycett Green, Michael Howard, 21st Earl of Suffolk, and the 11th Duke of Beaufort, commenting on their place in the development of Campbell-Black: "a wildly dashing and exciting group, and their bravery and charisma were the essential elements... his shittiness was entirely my invention" (my emphasis). My concern is that a fictional character whom the program's audience has presumably come to associate with shittiness is being associated with a recently deceased individual. As a possible fix for this, I suggest the following alt:
- ... that the character of Rupert Campbell-Black in Riders was based partly on the late Duke of Beaufort, though Campbell-Black's "shittiness" was entirely the author's invention? Gatoclass (talk) 19:38, 7 February 2018 (UTC)
- Yes, thank you. This would be ALT1 and looks fine with me. Courtesy ping to Moonraker, The C of E and Cwmhiraeth. Alex Shih (talk) 04:25, 8 February 2018 (UTC)
- Well, Alex Shih, as the duke has been dead for some time I don't see a BLP issue, unless Gatoclass thinks he may be a vampire; and in any event the point is surely covered by the word "partly"? I don't much like to see bad language on the main page. But no doubt you will suit yourselves. Moonraker (talk) 10:32, 8 February 2018 (UTC)
- Actually, BLP also applies to people recently deceased in the past two years, which applies in this case. And no, obviously I don't think the word "partly" covers this or I would not have brought it up as an issue. But I also happen to think that my alt will probably result in a higher page hit score, as people will be interested to read about a "shitty" character, so I think this will be a win for you as well as addressing the BLP issue. Gatoclass (talk) 17:13, 8 February 2018 (UTC)
- Actually BLP defines two years for "recently deceased" as being the extreme end of it, it doesn't set a minimum length that the policy applies for. The C of E God Save the Queen! (talk) 18:47, 8 February 2018 (UTC)
- Actually, BLP also applies to people recently deceased in the past two years, which applies in this case. And no, obviously I don't think the word "partly" covers this or I would not have brought it up as an issue. But I also happen to think that my alt will probably result in a higher page hit score, as people will be interested to read about a "shitty" character, so I think this will be a win for you as well as addressing the BLP issue. Gatoclass (talk) 17:13, 8 February 2018 (UTC)
- I prefer the original hook - I think we might be overthinking this one. :-) I really think "partly" covers things sufficiently. (If I were at all familiar with the character, I might feel differently, but not from the facts in evidence here...) --SarekOfVulcan (talk) 19:21, 8 February 2018 (UTC)
No BLP here. If anything, it's like BLP's second cousin, twice removed. Restore original. The Rambling Man (talk) 19:28, 8 February 2018 (UTC)
- Okay, but as I still think there is arguably a BLP issue here, I won't be returning it to prep, somebody who thinks it's fine can do it. Gatoclass (talk) 18:46, 9 February 2018 (UTC)
Review requested
I nominated Template:Did you know nominations/Mica McNeill (2 articles) with intent that it could be run on 20/21 February. That date is approaching, so could someone please review? Joseph2302 (talk) 14:53, 8 February 2018 (UTC)
- Done. I will move it to the special occasion holding area when the bot has transferred it over to the approved nominations page. Cwmhiraeth (talk) 18:48, 8 February 2018 (UTC)
Prep 3 - European urban voters
I had to read this three times to parse it, and even then I had to understand that the Finnish National Coalition Party was not a conservative party, to understand it. It's not hooky in the slightest and not interesting in the least. And ironically, the poster used to highlight the hook is from an era where the party was unelected for more than two decades, so it's hardly appropriate illustration either. Especially as the hook is written in the present tense, that poster dates back to the 1960s, what's the relevance?? There's a lot of text in the article, mostly just bullet points of election facts, but the dull hook combined with the inappropriate image is enough to kick this back to noms for a further look for something realistically interesting and suitably described. The Rambling Man (talk) 22:49, 8 February 2018 (UTC)
- I guess everyone is entitled to their opinion, but I'm quite lost at your rationale. "Finnish National Coalition Party was not a conservative party" ??? It is considered a conservative party? "the party was unelected" I guess you're trying to say was not in government, but I fail to see how that connects to a voter base hook in any case. "Especially as the hook is written in the present tense, that poster dates back to the 1960s, what's the relevance??" I'm not the greatest, most world-renowned political scientist, but voter base composition staying stable is the rule, not the exception. "There's a lot of text in the article, mostly just bullet points of election facts" Ok. Manelolo (talk) 23:13, 8 February 2018 (UTC)
- I think your piecemeal analysis of my comment has let the situation down a little. My main point is that the hook is turgid and unweildly. My corollary points are the our readers (i.e. 99% of them are not Finnish) may not be aware of the political alignment of the Finnish National Coalition Party, so the hook dies immediately. The poster is not the current poster, and relates back to a time where the voting public were actually not in favour of voting for a "conservative party" (which apparently the Finnish National Coalition Party is). I tried quickly to find something more interesting in the article, but as it's a collection of election facts and not much else (not that that's wrong, or bad, just a fact), so I couldn't suggest a better alternative. But the points I made remain unanswered. The Rambling Man (talk) 23:20, 8 February 2018 (UTC)
- "I guess everyone is entitled to their opinion" was my comprehensive analysis! Manelolo (talk) 23:30, 8 February 2018 (UTC)
- My main issue here is this - can a party that supports "multiculturalism, work-based immigration, gay rights and same sex marriage" actually be described as conservative? Its article even describes it as "liberal-conservative". Leading on from that, surely that particular ideology is the reason for its appeal in urban areas (well, such as it is, it got 18% of the vote in 2015)?. I can't support this one, sorry. Black Kite (talk) 00:32, 9 February 2018 (UTC)
- With no opinion on the actual hook, Black Kite WTF? Outside the US—in which "conservative" and "liberal" have taken on different meanings to their meanings elsewhere—
a party that supports "multiculturalism, work-based immigration, gay rights and same sex marriage"
describes pretty much every conservative party in the world, including the one that gave its name to all the others. ‑ Iridescent 00:41, 9 February 2018 (UTC)- @Iridescent:: Yes, but this party has those things as a main plank of its policies and manifestos. You won't see those things pushed to the fore in any Tory manifesto or being touted by their spokespeople in an election campaign, even though they may pay lip service to them. Remember that more Tories voted against gay marriage than for it, for instance. Black Kite (talk) 21:10, 9 February 2018 (UTC)
- Surely it can, as RS do on several occasions? Not on the extreme right, but on the right nevertheless when it comes to European and Nordic definitions (for example, it is a part of the EU-level conservative political group). Then again, from an American viewpoint all Nordic parties are wayyy on the left. Defining parties, that are made out of dozens of people generating opinions on all spheres of a society, with global-esque shorthands is usually shooting oneself in the leg in any case (especially since American and European views differ quite a lot). I'll rest my case now (that the hook is supported by an RS), let the powers that be decide and focus my energy on something actually productive. Manelolo (talk) 01:00, 9 February 2018 (UTC)
- With no opinion on the actual hook, Black Kite WTF? Outside the US—in which "conservative" and "liberal" have taken on different meanings to their meanings elsewhere—
Suggest this is pulled and worked on in slower time, and concerns over the odd image use are addressed as well. The Rambling Man (talk) 11:51, 9 February 2018 (UTC)
- I'm always open to critique and more than happy to amend anything that I write and subject to peer review—but it helps if there is something more to go by than "its boring" or "a poster of the party in question is not relevant to the party in question". See DYK review at Template:Did_you_know_nominations/National_Coalition_Party. Manelolo (talk) 16:16, 9 February 2018 (UTC)
- I don't think your comment is a fair summary of the various concerns raised here. There are sufficient for it to be re-opened and pulled from the set until such a time a consensus is reached. The Rambling Man (talk) 16:18, 9 February 2018 (UTC)
- "My corollary points are the our readers (i.e. 99% of them are not Finnish) may not be aware of the political alignment of the Finnish National Coalition Party, so the hook dies immediately." Don't have to be since the hook straightforwardly implies it IMHO. Or you could suggest something like adding 'conservative' in front the party, but that would be a bit repetitive for a simple contrast phrase, no? "The poster is not the current poster, and relates back to a time where the voting public were actually not in favour of voting for a "conservative party" (which apparently the Finnish National Coalition Party is)." The hook does not refer to the voting public, but voters of urban areas i.e. urban voters. Other than that, the poster is of the party in question, PD is 50 years after creation so an image of a current poster is quite hard to harness here, and it seems to be in alignment with WP:DYKIMG. Happy to be of further assistance, but I think this is just getting out of hand on nitpicking and being unproductive. If there were factual errors, grave mistakes or smth that contradicts knowledgeable sources that me or the reviewers missed, that would be a different case, no? Cheerio! Manelolo (talk) 16:30, 9 February 2018 (UTC)
- I think the use of the image is gravely in error, I think the hook is almost unreadable, and I think the concerns brought up above in toto rise beyond "nitpicking and being unproductive" but I'll take the NPA on the chin as I always do around here. Cheerio to you to!! The Rambling Man (talk) 16:39, 9 February 2018 (UTC)
- "My corollary points are the our readers (i.e. 99% of them are not Finnish) may not be aware of the political alignment of the Finnish National Coalition Party, so the hook dies immediately." Don't have to be since the hook straightforwardly implies it IMHO. Or you could suggest something like adding 'conservative' in front the party, but that would be a bit repetitive for a simple contrast phrase, no? "The poster is not the current poster, and relates back to a time where the voting public were actually not in favour of voting for a "conservative party" (which apparently the Finnish National Coalition Party is)." The hook does not refer to the voting public, but voters of urban areas i.e. urban voters. Other than that, the poster is of the party in question, PD is 50 years after creation so an image of a current poster is quite hard to harness here, and it seems to be in alignment with WP:DYKIMG. Happy to be of further assistance, but I think this is just getting out of hand on nitpicking and being unproductive. If there were factual errors, grave mistakes or smth that contradicts knowledgeable sources that me or the reviewers missed, that would be a different case, no? Cheerio! Manelolo (talk) 16:30, 9 February 2018 (UTC)
I pulled it. The lead sentence of the article states: The National Coalition Party (NCP; Finnish: Kansallinen Kokoomus; kok. or KOK; Swedish: Samlingspartiet; Saml.; lit. national coalition) is a centre-right[6] political party in Finland considered to be liberal,[2] conservative,[3] and liberal-conservative.[4] So what is it? If it isn't clearly a conservative party, I don't see how the hook works, also, I agree the intended meaning of the hook isn't crystal clear. I can't see an issue with the image however. Gatoclass (talk) 19:13, 9 February 2018 (UTC)
- Hmm yes true the lead sentence for NCP is a bit too all over the place, thx! I amended it to "considered to be conservative, but showing increasing signs of liberalism" as one source neatly put it and which might be the best way to describe it for simplicity's sake. Hope that helps! Manelolo (talk) 20:29, 9 February 2018 (UTC)
- Manelolo, if it's increasingly liberal, it still seems to me to be undermining the point of the hook. I'm thinking it would be better at this point for you to simply propose a different hook. Gatoclass (talk) 21:33, 9 February 2018 (UTC)
- Naah, I think I'll pass, thx. Used enough time already. Manelolo (talk) 10:27, 10 February 2018 (UTC)
- On second thought, how about this: "... that the push by the Finnish National Coalition Party (poster pictured) for Prince Frederick Charles of Hesse to become King of Finland failed?"
- Don't have a good English source within this timeframe, only Finnish: [7]. A Google Translate of the relevant part here. Manelolo (talk) 11:18, 10 February 2018 (UTC)
Maybe we should take this discussion to the nomination page now Manelolo, as I suspect it is not going to be an instant wrap and would be better managed there. Gatoclass (talk) 12:00, 10 February 2018 (UTC)
- Let's withdraw the nom then. Enough text and time has been spent swishswashing it around. Manelolo (talk) 12:30, 10 February 2018 (UTC)
A subsequent matter
- I've promoted another hook to prep area 3 to replace it. Seeing as it's newly promoted, somebody more experienced might want to give it a shuffle or a thorough vetting! I also moved one or two around within area 3, due to the lack of an image. Two hooks within the area had images - Hardware-based encryption and Mintaro, South Australia. The mintaro hook said "produces world class slate (pictured)", but the picture was of workers mining the slate, so that left HBE. Now, this is my DYK submission, and it didn't have a tie in with the picture in the hook. I've swapped from:
- ... that hardware-based encryption is probably in your computer?
- to
- ... that hardware-based encryption is probably in your computer, and not as a separate card (pictured)?
- Reference for addition -
have native instructions
— same as for main (emphasis added) - It's all a bit of a rush, given that it's the top prep area, but please can somebody approve the changed hook, or swap it back and sort something else out. ∰Bellezzasolo✡ Discuss 20:22, 9 February 2018 (UTC)
Bellezzasolo, I have reverted your changes as you are not permitted to promote your own nomination to the lead spot - and definitely not while tweaking your own hook with an additional statement not independently verified. It will be more than 24 hours before the next prep needs to be promoted, so there is plenty of time to find a suitable lead hook to replace the pulled hook. I also moved the hook you added to prep 1 to make room for a new lead hook. Thanks, Gatoclass (talk) 20:42, 9 February 2018 (UTC)
- @Gatoclass: I just went in with an attitude of "get it fixed". As soon as I made the changes I discussed here, requesting for verification. If another editor verifies the hook, do you have an objection to it being reinstated as lead? ∰Bellezzasolo✡ Discuss 20:52, 9 February 2018 (UTC)
- Bellezzasolo, I accept your changes were made in good faith; however, we do have longstanding rules about this. With regard to a proposed reinstatement, I would have to oppose that, partly because I think it would in effect be rewarding a breach of the rules (albeit made in good faith), and partly because I think the image is uninteresting. Gatoclass (talk) 21:06, 9 February 2018 (UTC)
- Gatoclass, while the image being interesting is a legitimate concern, flipping around "rewarding a breach of rules" sounds a bit like WP:PUNI to me. The policy on promotion only seems to refer to from DYKNA to Q, not within a prep area - or at least, that's how they read. Regarding the picture, it's been quite some time since there was a computing DYK was a lead. ∰Bellezzasolo✡ Discuss 21:45, 9 February 2018 (UTC)
- Bellezzasolo, DYK has never allowed people to promote their own hooks or move them to better positions within a prep. You can always request a change here on the talk page, but you shouldn't be editing or moving your own hook or a hook you've reviewed once it hits prep. I don't think it was particularly good image to begin with, so I can see why the nomination wasn't originally promoted with it. BlueMoonset (talk) 22:04, 9 February 2018 (UTC)
- I've cropped the image, rotated it a bit, and adjusted brightness/contrast. The end result is this:
- Bellezzasolo, DYK has never allowed people to promote their own hooks or move them to better positions within a prep. You can always request a change here on the talk page, but you shouldn't be editing or moving your own hook or a hook you've reviewed once it hits prep. I don't think it was particularly good image to begin with, so I can see why the nomination wasn't originally promoted with it. BlueMoonset (talk) 22:04, 9 February 2018 (UTC)
Concern about a review
Template:Did you know nominations/Oriental Basin pocket gopher: I came across this nomination, and I have some concern with the reviewer thinking the article is "too long". Just because it is longer than the gopher article is not in itself a problem. Chris857 (talk) 19:37, 9 February 2018 (UTC)
- I don't see the article length as an issue, it's only 800-odd words long after all. I don't know what the usual layout for articles on species is, and while this is strictly speaking not a DYK issue, I don't think it does any harm for reviewers to raise such issues if it's going to result in a better and more standardized presentation. Just as long as such objections are not overdone, because DYK articles are not expected to be perfect. Gatoclass (talk) 20:02, 9 February 2018 (UTC)
- Of course, no article on Wikipedia is expected to be perfect, even featured articles, but it's good for a reviewer to elevate their review standard away from the standard QPQ checkbox exercise which normally results in error reports and upset at the last moment. Regardless of DYK's "mission", it should not (and will not be allowed to) place sub-standard articles on the main page, and I applaud any reviewer who is capable and willing to stand up to the tidal wave of mediocrity that has overwhelmed the project such that any article passes. I would work with the reviewer to improve the article accordingly. The Rambling Man (talk) 20:07, 9 February 2018 (UTC)
Unreviewed Winter Olympics hook
I'd like to note that Template:Did you know nominations/Asa Miller, which has yet to be reviewed (but was only posted a day ago) is about an athlete competing in the Winter Olympics, so I believe we should try to get it onto the Main Page while the Games are still under way. Miller's event is scheduled for 18 February, and there are already five days' worth of full sets of queues and prep areas, so I hope someone will review this nomination ASAP. To make the Main page by 18 February (unless it replaces another hook in a set), it probably needs to be reviewed, approved and promoted within the next 48–72 hours. It's not yet in the "Special occasion holding area", under "February 14–20 (Winter Olympics event)", because only approved nominations can be placed there. Surprisingly, this nom is the only Winter Olympics-related nom in the entire list of yet-to-be approved nominations, and the Special occasion holding area has only two such nominations, so it's not as though DYK has lots of Winter Olympics nominations right now. Thanks. SJ Morg (talk) 11:40, 10 February 2018 (UTC)
Prep 4 - David M. Wilson
- ... that Sir David M. Wilson went from being an expert on Vikings to the Director of the British Museum? Yoninah, Usernameunique
Firstly we don't normally append titles like "Sir" within links. Secondly, he's still an expert on Vikings (as far as I can tell). The fact isn't particularly noteworthy, it might be more interesting to say something like he became just the 17th director of the museum in 221 years (per this? The Rambling Man (talk) 15:12, 10 February 2018 (UTC)
- The Rambling Man, happy either way. Requisite information has been added to the article. Here's a proposal:
- ... that Viking expert Sir David M. Wilson became just the 17th Director of the British Museum in its 224 years?
- "Sir" can be bolded or not; one advantage of bold is it makes the link (and his significance) a bit more obvious. 224 years instead of 221, since apparently the BM was founded in 1753, but didn't have a director (then "Principal Librarian") until 1856. --Usernameunique (talk) 15:26, 10 February 2018 (UTC)