Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receive and impart information and ideas through any media and regardless of frontiers.
— Article 19 of the Universal Declaration of Human Rights
Orphaned non-free image File:Doomsday (Doctor Who).jpg
Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --TedEdwards 20:20, 29 October 2022 (UTC)
RM of 90377 Sedna
Hello Sceptre,
Thanks for taking the time to assess the RM of 90377 Sedna. Please don't forget to move back Quaoar. Renerpho (talk) 01:28, 22 November 2022 (UTC)
- Hi Sceptre, Please could you reopen and relist the RM? There wasn't that much participation, !votes were pretty split and I think there was a lot more to be discussed about the matter, warranting a relist. I would certainly vote in favour of the move, as the WP:COMMONNAME in sources is not "90377 Sedna" as far as I can see. — Amakuru (talk) 23:24, 23 November 2022 (UTC)
- @Amakuru: FWIW, there's a larger discussion over whether Sedna is definitively a dwarf planet or not going on at the talk page, and I didn't want to tip the scales one way or the other with the closure. The predominant view in the RM was against moving, so I could've closed it as "not moved", but "no consensus to change how we've done stuff, therefore we stick with the status quo ante" is also a valid closure, and FWIW, I don't think another few days of discussion would've created a consensus. Sceptre (talk) 07:12, 25 November 2022 (UTC)
ArbCom 2022 Elections voter message
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:20, 29 November 2022 (UTC)
Guild of Copy Editors December 2022 Newsletter
Guild of Copy Editors December 2022 Newsletter
Hello and welcome to our latest newsletter, a quarterly digest of Guild activities since October. Don't forget you can unsubscribe at any time; see below. Blitz: Our October Copy Editing Blitz focused on July and August 2022 request months; and articles tagged for c/e in December 2021 and January 2022. Seventeen of those who signed up claimed at least one copy-edit, and between them copy-edited forty-six articles. Barnstars awarded are here. Drive: In the November Backlog Elimination Drive, thirty editors signed up, twenty-two of whom claimed at least one copy-edit. Both target months—December 2021 and January 2022—were cleared, and February was added to the target months. Sixteen requests were copy-edited and 239 articles were removed from the backlog. Barnstars awarded are here. Blitz: Our seven-day-long December 2022 Copy Editing Blitz begins on 17 December at 00:01 (UTC)*. It will focus on articles tagged for copy-edit in February 2022, and pending requests from September and October. Barnstars awarded will be available here. Progress report: As of 22:40, 8 December 2022, GOCE copyeditors have processed 357 requests since 1 January, there were seventy-four requests outstanding and the backlog stands at 1,791 articles. We always need skilled copy-editors; please help out if you can. Election news: Nomination of candidates for the GOCE's Election of Coordinators for the first half of 2023 is open and continues until 23:59 on 15 December. Voting begins at 00:01 on 16 December and closes at 23:59 on 31 December. All editors in good standing (not under ArbCom or community sanctions) are eligible and self-nominations are welcomed. Coordinators serve a six-month term that ends at 23:59 on June 30. If you've thought about helping out at the Guild, please nominate yourself or any editor you consider suitable—with their permission, of course!. It's your Guild and it doesn't coordinate itself. Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers and best seasonal wishes from your GOCE coordinators, Baffle gab1978, Dhtwiki, Miniapolis, Tenryuu, and Zippybonzo. *All times and dates on this newsletter are UTC.
To discontinue receiving GOCE newsletters, please remove your name from our mailing list. |
Sent by Baffle gab1978 via MediaWiki message delivery (talk) 00:26, 9 December 2022 (UTC)
Guild of Copy Editors December 2022 Newsletter error
The GOCE December 2022 newsletter, as sent on 9 December, contains an erroneous start date for our December Blitz. The Blitz will start on 11 December rather than on 17 December, as stated in the newsletter. I'm sorry for the mistake and for disrupting your talk page; thanks for your understanding. Sent by Baffle gab1978 via MediaWiki message delivery (talk) 21:30, 9 December 2022 (UTC)
Palestinian exodus close
Hi, I must take issue with the recent close. It states:
the closer stated the discussion and arguments were fairly balanced
when what the closer actually said was
While the discussion and arguments seem fairly balanced in number.....my decision that those who support the move have a better understanding of the article and what its title should be
Furthermore, the review closure also stated
Please do note that the community takes issue with UtherSRG's method, not his outcome. It will be in order for someone else to re-close this requested move as move if that is their assessment of the consensus
Afaics, the current close amounts to a vote count that takes no account of the quality of the arguments in support of either the original or the proposed title, the "better understanding", I request that you take another look.
Thank you. Selfstudier (talk) 11:18, 10 December 2022 (UTC)
- @Selfstudier: At the same time, I cannot create a consensus where there clearly is none. Nothing happened in the RM after it was re-opened. At the MRV, overturning to no consensus was supported by a good proportion of people, and I agree with them. Sceptre (talk) 14:06, 10 December 2022 (UTC)
- Agree with Selfstudier, Sceptre, because far too many editors agreed that the first closure, which did find a consensus to move, was correct. You say you did not see a consensus, but you don't say why? The support args far outweighed the oppose args, which is the main reason the first closure's review ended in "vacate" rather than in "overturn to no consensus". Please reassess the arguments to find what we say here is true. That article needs to be renamed as proposed. P.I. Ellsworth , ed. put'r there 06:28, 12 December 2022 (UTC)
- Yes, agreed. I noted at the MRV that there was consensus to close, just that the previous closer gave a spurious reason for seeing consensus there. Closure is supposed to be viewed through the lens of policy, not by counting heads, and in this case there was strong evidence by those in support, invoking the WP:NPOV policy, that the term "expulsion and flight" is better and more neutral wording than the status quo. I wish I'd cast another "support" !vote at the discussion now, because the arguments to move were vastly more persuasive and rooted in evidence than those in opposition, and I didn't really expect a no-consensus closure after all that had been said at the MRV, it was simply that a more clear close was required than that previously given. Cheers — Amakuru (talk) 15:09, 12 December 2022 (UTC)
- Agree with Selfstudier, Sceptre, because far too many editors agreed that the first closure, which did find a consensus to move, was correct. You say you did not see a consensus, but you don't say why? The support args far outweighed the oppose args, which is the main reason the first closure's review ended in "vacate" rather than in "overturn to no consensus". Please reassess the arguments to find what we say here is true. That article needs to be renamed as proposed. P.I. Ellsworth , ed. put'r there 06:28, 12 December 2022 (UTC)
Palestinian exodus move
Your close doesnt seem to address the merits of the arguments at all, and ask that you reconsider by either relisting (it had only been relisted for three days prior to your close) or address the merits of the arguments. When one group provides sources and the other side just says POV that should not result in no consensus. nableezy - 14:53, 12 December 2022 (UTC)
- I see this has already been requested, if you are going to refuse can you say so in order to open a new move review? nableezy - 14:54, 12 December 2022 (UTC)
- @Paine Ellsworth, Amakuru, and Nableezy: Hey all. Having a second look at the RM, although the arguments to move were more detailed than those opposing the move, I still cannot create a consensus where there is none. I'm sympathetic to the argument, and personally I believe the people arguing in favour of a move are right. But as a closer, my role is to evaluate the discussion, and I cannot see a consensus either way. Nor was it likely that a consensus was going to develop; there was no participation in the RM after it was reopened. In such circumstances, I can't do anything but close as "no consensus". Sceptre (talk) 17:04, 13 December 2022 (UTC)
- Yes, you can, you can not close a move that was relisted for 3 days, especially when experienced closers and admins are telling you that you are incorrect in your reading of the discussion and of "consensus". But fine, Ill open a move review. nableezy - 17:10, 13 December 2022 (UTC)
- @Paine Ellsworth, Amakuru, and Nableezy: Hey all. Having a second look at the RM, although the arguments to move were more detailed than those opposing the move, I still cannot create a consensus where there is none. I'm sympathetic to the argument, and personally I believe the people arguing in favour of a move are right. But as a closer, my role is to evaluate the discussion, and I cannot see a consensus either way. Nor was it likely that a consensus was going to develop; there was no participation in the RM after it was reopened. In such circumstances, I can't do anything but close as "no consensus". Sceptre (talk) 17:04, 13 December 2022 (UTC)
Move review for 1948 Palestinian exodus
An editor has asked for a Move review of 1948 Palestinian exodus. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. nableezy - 17:26, 13 December 2022 (UTC)
Closure of Maori Party RM
Hi,
I request that you reopen and relist your recent closure of this RM. To close this RM based on counting !votes is inappropriate. Consensus is not based on just counting the number of heads.
In addition, in my opinion your closing statement does not address the arguments raised during the RM. Did you consider WP:CRITERIA-based arguments? Did you consider that the party does not use one name over the other on it's website, when at least three support !votes stated that they do? -Spekkios (talk) 23:58, 10 December 2022 (UTC)
- @Spekkios: I did consider WP:CRITERIA, and found arguments for "Māori Party" and "Te Pāti Maori" to be relatively equal in weight. At such a point, I have to fall back on the direction of the discussion, which was clearly in favour of the move. Sceptre (talk) 17:04, 13 December 2022 (UTC)
- If the arguments are relatively equal in weight, that would imply a "no consensus" closure instead of a "move" closure. How does the discussion "direction" or the number of !votes matter if the policy based arguments are equal in weight? --Spekkios (talk) 21:51, 13 December 2022 (UTC)
- ==Move review for Te Pāti Māori==
- An editor has asked for a Move review of Te Pāti Māori. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Spekkios (talk) 23:33, 17 December 2022 (UTC)
- If the arguments are relatively equal in weight, that would imply a "no consensus" closure instead of a "move" closure. How does the discussion "direction" or the number of !votes matter if the policy based arguments are equal in weight? --Spekkios (talk) 21:51, 13 December 2022 (UTC)
Introducing arguments in closures
Hi, um, slightly awkward to pile on like this, but I don’t actually have any issue with the decision of your closure. Rather I came to advise on a less central detail: you should avoid introducing new arguments in your closures. In this case, the point about NZ English being quick to adopt Māori vocab seems to come out of nowhere and doesn’t reflect the discussion. I think a better summary would have mentioned something like “proponents emphasised that the party refers to itself as te Pāti Māori (in English)”, which seems to be one of two dominant arguments (along with commonness). — HTGS (talk) 01:17, 11 December 2022 (UTC)
- @HTGS: In hindsight, you're right about the wording. I didn't think the comment came out of nowhere; there is a propensity in NZ-related RMs for people less familiar with NZEng to treat Māori vocabulary as "not English enough", which I felt was being introduced in this RM. But yes, the key point is that the use in English, not the use of English (see also also: Senedd), for which I was satisfied "Te Pāti Māori" was common enough to be a COMMONNAME. Sceptre (talk) 17:04, 13 December 2022 (UTC)
I don't notice any objection to moving that to Day of Reckoning (disambiguation). I think that could have been the outcome, rather than "no consensus". — BarrelProof (talk) 17:33, 11 December 2022 (UTC)
Should no consensus mean reverting to previous title?
I see you recently closed a requested move as no consensus. I agree there wasn't any consensus. Should this mean that the article should revert back to its previous long-term and stable title? the article was called "Tehrik-i-Taliban Pakistan" from 2008 to May 2022, when it was moved after this discussion. But this discussion doesn't seem to have enough participation to constitute consensus (2 supports and 1 oppose). This rationale was also mentioned by Paine Ellsworth. VR talk 16:44, 14 December 2022 (UTC)
- For what it's worth, move requests don't need to have a certain magnitude of participation for them to be regarded as legitimate (vide WP:RMNOMIN), as decisions are made by a consensus process, which factors in the policy-based reasoning of participants, and not vote-counting; and an absence of objection does contribute to the consensus too. As someone who participated in the discussion, I find the above bid to solicit a move indirectly without notifying the editors on the talk page to be quite discourteous inasmuch as the magnitude to which it was vehemently opposed (being eloquent of disagreement) by a laundry list of long-term contributors (including Andrewa and Amakuru), who argued against the move on policy grounds, in contrast to the support it garnered from a considerable number of SPAs, block-evading socks, and topic banned users who trivialized the consensus process by construing the discussion to be some sort of a votestacking contest; not to mention the fact that the title had been stable for about half a year until a block-evading IP began, and thereupon tainted the RM with more socks. In my view, the foregoing quite clearly forecloses the possibility of a revert back to old title. MBlaze Lightning (talk) 22:36, 14 December 2022 (UTC)
- To editors VR and MBlaze Lightning: might have handled this differently; however, the outcome in this case is a reasonable one. And this due to ML's argument above for a set new consensus being in place long enough to matter. And I trust Andrewa's and Amakuru's opinions beyond words. So in the end there's a good possibility I would have closed the same way Sceptre did. P.I. Ellsworth , ed. put'r there 23:15, 14 December 2022 (UTC)
Likewise, Andrewa reiterated the underlying essence of his argument, when he proffered:Oppose - it has been clearly demonstrated above, using Google hits as well as G-books hits, that the common name for this group is "Pakistani Taliban". It's also clearly the primary topic for that term, compared to the topic of other Taliban who hail from Pakistan or other groups operating there. Although the !vote here looks split, I think this is a "consensus against move" scenario because the policy arguments for the present title are a lot stronger than those for the alternative
— User:Amakuru 12:00, 28 November 2022
.. If that term is ambiguous and the current article is not the Primary Topic (about which I am not convinced), should it be a DAB?Andrewa (talk) 15:58, 12 November 2022 (UTC). I too had recapitulated the essence of my argument a day before your closure[1]. In consequence, I don't think putting these quality arguments grounded in policies upon the same footing as those advanced by proponents of the move (whose chief reasoning was debunked, with the residual taking the form of rehash, primarily from socks and SPAs) was justified or meticulous. I did give it a food for thought before voicing my dissent, because a few months down the road this is likely to become an issue again with socks crawling out of the woodwork all over once again, and some of us may not be around (as much) on Wikipedia for it. MBlaze Lightning (talk) 11:31, 15 December 2022 (UTC)
- Yes, thanks @MBlaze Lightning: for this thoughtful response, and that would be my viewpoint as well. There are two separate issues here, firstly whether the May RM was sufficient to establish a "new status quo" to be the baseline default in the event of a subsequent "no consensus", and secondly whether the close of no consensus was itself valid. On the first, I'd say it's borderline; if the RM was very recent, I'd probably include its findings in and amongst the !votes for the second RM; but 6+ months, for an RM which was conclusively decided (i.e. not just moved without discussion) is getting to the point where it should be binding. So (with my obviously biased hat on) I wouldn't fault Sceptre for not moving back to the original name. On the second issue, I agree that it definitely should have been a "consensus against moving" close, when evaluating through the strength of argument, WP policy and evidence. Furthermore, in a contentious and close RM such as this, I would expect a summary from the closer as to why they've come to the conclusion they have... not just a single-line "no consensus"... as indeed was the case at the Talk:1948_Palestinian_exodus#Requested_move_8_September_2022 RM mentioned in the sections above and now at move review. WP:CONSENSUS is formed by viewing !votes through the lens of policy, and both supporters and opposers need to know why a closer reached the conclusion they did. Cheers — Amakuru (talk) 11:51, 15 December 2022 (UTC)
- @MBlaze Lightning: this is a rehash of the argument in made during the RM, but you are confusing two different topics here. Just because a title has a WP:PRIMARY TOPIC doesn't mean that that topic unambiguously refers to only that primary topic. A great example is given in policy itself[2], at WP:COMMONNAME, and that is Heart attack. The Primary topic of Heart attack, and the page it redirects to, is Myocardial Infarction. However, heart attack can also refer to cardiac arrest. VR talk 19:49, 15 December 2022 (UTC)
- User:Vice regent, yeah, thanks for recollecting that you conceded to Amakuru on their primary topic contention in the discussion ([3]). This consensus then should have informed Sceptre's close, for the policy left no room for doubt that the title had to reflect the primary topic (as discerned by common usage in English RS). The guidline is perspicuous: if an expression has a primary topic, then that is what it leads to, per its dictates. This is not to say that its application is ubiquitous: as with any other MOS, exceptions do exist; and medicine domain embodies the niche where the nomenclature is conditioned by the scientific or recognised medical name commonly occuring in "recent, high-quality, English-language medical sources, rather than a lay term (unscientific or slang name)[1] or an historical eponym that has been superseded" (vide WP:NCMED). This is why the colloquial term, Heart attack, redirects to MI, despite being the primary topic. However, such exceptions do not impeach the rule itself; the latter is the established norm; whereas the former, a narrowly carved out exception to suffice the specific needs of a niche community. MBlaze Lightning (talk) 21:20, 15 December 2022 (UTC)
- Again, I think you're mistaken about Primarytopic. You seem to implying that if a title X has a primary topic Y, then our article on Y must necessarily be called X. But that's not true. The only thing the primary topic implies is that X must point to the article Y, whatever it is called. In fact, we have a whole template (Template:Redirect) that deals with such cases. Besides the "heart attack" example above, other examples include:
- The primary topic for "Soccer" is Association football. And "soccer" has 647M google hits, vs only 10M hits for "Association Football", yet we pick the less common name.
- The primary topic for "Western Allies" (2.3M hits) is Allies of World War II (0.2M hits), but we avoid the title that is ambiguous.
- The primary topic for "Midwest" (171M hits) is Midwestern United States (only 1.2M hits), but again we avoid the ambiguous title. I could go on and on with dozens more examples.
- The primary topic for "Pakistani Taliban" is indeed "Tehrik-i-Taliban Pakistan". In this case too, we should avoided the ambiguous name even if it gave somewhat more google hits.
- Likewise many times during the discussion I argued that "Tehrik-i-Taliban Pakistan" was more precise, because scholarly sources used the term "Pakistani Taliban" to refer to groups/individuals that were not TTP ([4][5][6]), for example splinter groups from TTP, groups similar to the TTP but never a part of it, as well as Pakistani members of the (Afghan) Taliban. VR talk 00:40, 16 December 2022 (UTC)
- Merely rehashing that some expression is ambiguous doesn't cut it for an argument where you have acknowledged that there is a primary topic. Matters end right there for all intents and purposes. The redirects embody an exception scenario to the aforesaid guideline, and they occur when any of the conditions set forth in WP:PRIMARYREDIRECT hold good, which wasn't remotely the case with this article; indeed, it was no one's argument, forget an effort that convinced others. The results were lopsided and weighed in favour of the existing title. Your filibustering to derail the efforts to solicit Sceptre's construction of a "no consensus" (which didn't account for the strong policy and evidence based reasoning in oppose) is getting to the point of being unconstructive; this isn't a new RM, where you rehash and even dwell on the issue anew with previously unmentioned examples; desist, please. MBlaze Lightning (talk) 06:39, 16 December 2022 (UTC)
- Again, I think you're mistaken about Primarytopic. You seem to implying that if a title X has a primary topic Y, then our article on Y must necessarily be called X. But that's not true. The only thing the primary topic implies is that X must point to the article Y, whatever it is called. In fact, we have a whole template (Template:Redirect) that deals with such cases. Besides the "heart attack" example above, other examples include:
- User:Vice regent, yeah, thanks for recollecting that you conceded to Amakuru on their primary topic contention in the discussion ([3]). This consensus then should have informed Sceptre's close, for the policy left no room for doubt that the title had to reflect the primary topic (as discerned by common usage in English RS). The guidline is perspicuous: if an expression has a primary topic, then that is what it leads to, per its dictates. This is not to say that its application is ubiquitous: as with any other MOS, exceptions do exist; and medicine domain embodies the niche where the nomenclature is conditioned by the scientific or recognised medical name commonly occuring in "recent, high-quality, English-language medical sources, rather than a lay term (unscientific or slang name)[1] or an historical eponym that has been superseded" (vide WP:NCMED). This is why the colloquial term, Heart attack, redirects to MI, despite being the primary topic. However, such exceptions do not impeach the rule itself; the latter is the established norm; whereas the former, a narrowly carved out exception to suffice the specific needs of a niche community. MBlaze Lightning (talk) 21:20, 15 December 2022 (UTC)
- @MBlaze Lightning: this is a rehash of the argument in made during the RM, but you are confusing two different topics here. Just because a title has a WP:PRIMARY TOPIC doesn't mean that that topic unambiguously refers to only that primary topic. A great example is given in policy itself[2], at WP:COMMONNAME, and that is Heart attack. The Primary topic of Heart attack, and the page it redirects to, is Myocardial Infarction. However, heart attack can also refer to cardiac arrest. VR talk 19:49, 15 December 2022 (UTC)
Please fix the many incoming links to this dab page, which previously pointed to the page now at "(building)". Thanks. PamD 05:28, 17 December 2022 (UTC)
Orphaned non-free image File:Doomsday (Doctor Who).jpg
Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --TedEdwards 03:16, 31 December 2022 (UTC)
Happy New Year, Sceptre!
Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.
— Moops ⋠T⋡ 17:21, 2 January 2023 (UTC)Closure of Prinz von Preussen RM
Hello!
I was curious to know why you closed the recent RM on Franz Willem Prinz von Preussen in favor of the move? The majority (albeit 7-6, by my count) were opposed to the move. Further, the official website of the princes of Prussia [8] refers to "Georg Friedrich, Prince of Prussia" not the current article title. I would suggest revisiting this RM, as it does not even seem reliable english sources use the title. I would also argue the discouragement of hypothetical titles in WP:NCROY doesn't apply because reliable sources do in fact use the title. Here are some: [9] [10] [11][12] Estar8806 (talk) 23:26, 19 January 2023 (UTC)
FAR for Partners in Crime (Doctor Who)
I have nominated Partners in Crime (Doctor Who) for a featured article review here. Please join the discussion on whether this article meets the featured article criteria. Articles are typically reviewed for two weeks. If substantial concerns are not addressed during the review period, the article will be moved to the Featured Article Removal Candidates list for a further period, where editors may declare "Keep" or "Delist" in regards to the article's featured status. The instructions for the review process are here. Z1720 (talk) 16:32, 28 January 2023 (UTC)
Mergers
Hello @Sceptre!
I had never proposed mergers until recently, and most of my proposals haven't been gaining much traction. I would appreciate your insight on these 3 proposals of mine: 1, 2, 3
Any insight is greatly appreciated. Thank you for your time! Mooonswimmer 21:40, 28 January 2023 (UTC)
- @Mooonswimmer: If nobody objects to the proposal after a decent amount of time, just feel free to do the merge yourself. :) Sceptre (talk) 21:48, 28 January 2023 (UTC)
1948 Palestinian exodus close
Why would you close this when you were involved with a previous near-identical close that was challenged and which came up with no consensus on the quality of your close? Part of the complaint was that you did a vote count and didn't expand on the arguments or policy. Now you have closed an almost identical RM (with yourself now arguably involved in the overall imbroglio) and performed what appears to be another vote count without any mention of the arguments or policy, and in part referred to the previous close with which you were involved. In the most unflattering light, this close could even be interpreted as you returning with the specific intent of reiterating your own previous, challenged verdict to make a point. I would strongly suggest that you re-open and leave it to a closer that is more obviously uninvolved. Iskandar323 (talk) 05:04, 29 January 2023 (UTC)
- WP:INVOLVED explicitly does not apply to actions taken in a purely administrative role. As I've said, if there was truly a consensus to move the article, I would be perfectly happy to do so. But if anything about the past six months of discussion over three extended RM periods and two MRV periods has shown, it's not only that there isn't a consensus, but also that there won't be a consensus forthcoming. If you disagree, you can go for a third move review of this RM, but honestly, I think we'd all be better off if we let the matter rest for a while. Sceptre (talk) 05:35, 29 January 2023 (UTC)
- Regardless of the letter of the law, your involvement at this stage was unwise to the say the least given your past involvement in a similar case and the subsequent contention. In addition, the combined lack of policy/argument reflection and similarly off-topic reflections on past closes used to justify the close (again) was of course almost guaranteed to raise recurring questions. If you don't have the energy to engage fully with a subject of this nature, don't engage with it. The handling of contentious topic discussions is often best left to administrators. I think you closing this almost guarantees another move review, but if that is an outcome you are happy with, so be it. Iskandar323 (talk) 06:25, 29 January 2023 (UTC)
That is an absurd close, and you emphatically do not have authority to impose a moratorium. nableezy - 16:56, 13 February 2023 (UTC)
- Please see Wikipedia:Move_review/Log/2023_February#1948_Palestinian_exodus nableezy - 17:12, 13 February 2023 (UTC)
Royal Rumble 2023
Thank you for undoing my edits. Yes, at the article Royal Rumble (2023), WWE officially lists Rhea Ripley as staying in the women's Royal Rumble match 1 second longer than Liv Morgan, although other sources say that the match ended as soon as Morgan was eliminated, and Ripley and Morgan set the record. If you have further issues, please discuss it in the article's talk page. GodofDemonwars (talk) 00:18, 1 February 2023 (UTC)
Guild of Copy Editors 2022 Annual Report
Guild of Copy Editors 2022 Annual Report
Our 2022 Annual Report is now ready for review.
Highlights:
– Your Guild coordinators:
Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo
To discontinue receiving GOCE newsletters, please remove your name from our mailing list.
|
Sent by Baffle gab1978 using MediaWiki message delivery (talk) 00:30, 6 February 2023 (UTC)
Orphaned non-free image File:Doctor Who series 2 soundtrack.jpg
Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 18:15, 10 February 2023 (UTC)
Recent move
Hi there,
How did you determine that the consensus for this move was not the proposed title? Spekkios (talk) 21:00, 10 February 2023 (UTC)
- @Spekkios:: HTGS's argument was the most persuasive, both to me and other editors in the discussion. When it comes to NZEng, there's no bright line to go to for the English, Māori, or dual names and it ultimately comes down to which has the most evidence to go with. In this case, based mostly on HTGS's comment, I determined it was the Māori one. Sceptre (talk) 14:03, 12 February 2023 (UTC)
Requested move at WikiProject Ukraine
Regarding the close at Wikipedia talk:WikiProject Ukraine#Requested move 7 February 2023. The statement about the decision completely ignores the important point about the difference between the names in article titles and parenthetic disambiguation strings, as well as the cited precedent, citing examples that are not analogies for this at all (on top of that, Istanbul and Constantinople are completely different names, not just a spelling variation in a city name that hasn’t changed in over a millennium). It seems a completely unsatisfactory rationale, as in it gives no indication that you read the proposal or considered the points made in it.source] ]] —Michael Z. 20:52, 16 February 2023 (UTC)
- @Mzajac: although Constantinople may arguably be or not be an adequate comparison, I believe that Calcutta/Kolkata is; they’re both changes in (Western) English orthography to the local orthography, where the local orthography is more common. However, it’s not always the case that the change is consistent when talking retrospectively; although "Mumbai" is almost universally used these days, usage is split on the 1993 Bombay bombings. Regardless, there isn’t a consensus for a move anyway, and the retrospectivity (or lack thereof) of COMMONNAME was brought up in the discussion. Sceptre (talk) 23:33, 16 February 2023 (UTC)
- That’s all academic because the change was to the parenthetic disambiguation text, not the name. COMMONNAME doesn’t apply to disambiguation text.
- WP:PRECISION says to use the least-precise version sufficient to disambiguate. The main-article-title spelling of the city is good enough, and there’s no point in narrowing it to a historical spelling that is only used in restricted contexts.
- WP:TITLEDAB reinforces the idea: “use only as much additional detail as necessary.” The examples there make it clear to use the broadest term possible, not one that applies only in a specific context, like a historical one.
- And WP:CONSISTENCY is violated, because the new decision conflicts with the precedent cited in the proposal: the consensus move of a similar article to Folkstsaytung (Kyiv).
- And there is no consensus to use the dated spelling Kharkov in historical contexts.
- It’s not the end of the world if these are not moved, but it seems to be contrary to best practices. I urge you to reconsider the decision or even reopen it to get more input, but I’ve had my say and I won’t belabour it further if you choose not to. Thanks for closing the RM anyway. Cheers. —Michael Z. 04:09, 17 February 2023 (UTC)
Maize -> Corn RM
Thanks for taking the time to read that novel. I'd just like to know what arguments you found most compelling, so I can understand more about Wikipedia guidelines.
Your reasoning on the talk page itself is that the common name may change from Maize to Corn, but it hasn't yet, similar to Iroquois → Haudenosaunee. However, the arguments used to show that Iroquois is still the most commonly used name is the exact sort used to show why Corn is the most commonly used name. Most relevantly, even in scientific and scholarly papers Maize is used about 1/3rd as much as Corn, as shown in the RM.
Could you explain the differences between the two situations? Without knowing more about your point of view, one could look at these two examples and assume that the default is 'no consensus' when a tough decision needs to be made. OuroCat (talk) 23:12, 16 February 2023 (UTC)
FYI
You have recently made edits related to the Arab–Israeli conflict. This is a standard message to inform you that the Arab–Israeli conflict is a designated contentious topic. This message does not imply that there are any issues with your editing. Additionally editors must be logged-in have 500 edits and an account age of 30 days, and are not allowed to make more than 1 revert on the same page within 24 hours for pages within this topic. For more information about the contentious topics system, please see Wikipedia:Contentious topics. nableezy - 13:46, 17 February 2023 (UTC)
RM closure
Hello, Sceptre. Regarding your closure at Aguascalientes City, I notice you wrote that "documentary evidence has been provided to the contrary" only for Chihuahua City, which you exempted... but an even greater volume of documentary evidence was provided for Oaxaca City, which you didn't. Was that intentional, and if so could you share the rationale? Thanks for any clarification. ╠╣uw [talk] 17:09, 20 February 2023 (UTC)
I'll add that a lot of evidence was introduced for Queretaro City, as well. Red Slash 17:12, 20 February 2023 (UTC)
- @Huwmanbeing and Red Slash:: It was completely unintentional, but from looking further at the discussion, I can see there's no reason to not apply that exemption for Oaxaca and Querétaro. I'll happily reverse those moves and amend my closure in those cases. Sceptre (talk) 17:21, 20 February 2023 (UTC)
- Thank you. Chihuahua City, Oaxaca City, and Querétaro City were the only ones actually tested for evidence of common usage; that they all showed it suggests the others are likely the same. I feel like it would've been preferable for the nominator to investigate this before making the bulk proposal, but it sounds like individual RMs or a second bulk RM will be needed for these now. ╠╣uw [talk] 19:50, 20 February 2023 (UTC)
- Yes, I didn't test all the other ones, because it would have been exhausting, but I think you probably would've found the same for all the others (possible exceptions might include Colima, which is--slight exaggeration--basically a microstate, or maybe some extremely small cities/states like Aguascalientes itself that don't have much of any English-language coverage at all, but no evidence was offered in the move request whatsoever). Thanks for putting the accent in Querétaro City, btw--my bad for being lazing and omitting it. Red Slash 17:17, 22 February 2023 (UTC)
- RS: Yes, I think it just comes down to the original bulk request being poorly formed, in that it wrongly assumed that none of the listed cities commonly use the "City" form, whereas spot checks showed that wasn't true for several (and suggested it might not be true for any). I think ideally those that haven't been checked wouldn't be moved until they have, but it's not the end of the world either way and I'm fine with whatever solution's easiest. Recommendations, Scepter? ╠╣uw [talk] 18:19, 22 February 2023 (UTC)
Sceptre, I must applaud you for your efforts. But I think there’s a bit of confusion lurking here. There is no community consensus, nor local consensus in this RM, that says that demonstration of some common usage of a given natural disambiguation for a topic means that this natural disambiguation, and not parenthetic disambiguation of the undisputed most common name, must be used as the title. As noted in the discussion, NATURAL merely notes that the natural disambiguation may be preferred. Well, in all of these cases, without any exceptions, consensus in this RM clearly prefers the parenthetic disambiguation. Please close according to community and local consensus. Thank you. —В²C ☎ 02:19, 21 February 2023 (UTC)
- Sceptre, hello? Would you prefer to address this in an MR? —В²C ☎ 06:15, 22 February 2023 (UTC)
- Funnily enough, I was considering a move review as well, since no evidence was provided for the vast majority of the cities that the X City name was not common; I provided several counterexamples for Chihuahua and Queretaro specifically (and I believe Huw did the same for Oaxaca), and I think I provided enough evidence to show that if those two or three were off, than everything was off.
- Frankly, I think the move request should've been dropped as no consensus, and then people individually could've made proposals at each one to look at how much English-language usage the X City form had for each one individually. Most likely Chihuahua would've failed (stayed at City); perhaps Aguascalientes itself would've succeeded; in any case, I was thinking of a move review. (Also, B2C, I have so much respect for you, even ywith this disagreement, but like... you gave Spectre 28 hours to respond, give her a bit more time ) Red Slash 17:17, 22 February 2023 (UTC)
- I repeat, even if evidence of common usage of Name City was shown for every city on the list that wouldn’t be sufficient to override the consensus to move them all to parenthetic disambiguation, as proposed, nonetheless. While lack of common usage is sufficient reason to not use a given alternative name, evidence of common usage is not sufficient to use it rather than parenthetic disambiguation. There are other considerations to be made and ultimately it’s decided by consensus, not the closer. The closer is only supposed to decide what the consensus is. Otherwise it’s a WP:SUPERVOTE. Here, the closer’s unilateral decision to exclude first 1, then 2 then 3, from the list, when consensus for/against the move of each was equal for all, is a super vote. —-В²C ☎ 18:09, 22 February 2023 (UTC)
- Bizarre as it may seem, I'd say exactly the opposite. Got lots of respect for you, B2C, but to me, saying "yeah the amount of supports for Durango City vis-a-vis Chihuahua City were the same, but Chihuahua City had actual evidence presented and Durango didn't, so I'm going to treat them differently" sounds like something a good closer would do.
- But of course that ignores the more important point that there was no evidence provided whatsoever that Durango City isn't a common name for the city. Which is why we're going to go to Move Review. Red Slash 17:29, 23 February 2023 (UTC)
- I repeat, even if evidence of common usage of Name City was shown for every city on the list that wouldn’t be sufficient to override the consensus to move them all to parenthetic disambiguation, as proposed, nonetheless. While lack of common usage is sufficient reason to not use a given alternative name, evidence of common usage is not sufficient to use it rather than parenthetic disambiguation. There are other considerations to be made and ultimately it’s decided by consensus, not the closer. The closer is only supposed to decide what the consensus is. Otherwise it’s a WP:SUPERVOTE. Here, the closer’s unilateral decision to exclude first 1, then 2 then 3, from the list, when consensus for/against the move of each was equal for all, is a super vote. —-В²C ☎ 18:09, 22 February 2023 (UTC)
- Frankly, I think the move request should've been dropped as no consensus, and then people individually could've made proposals at each one to look at how much English-language usage the X City form had for each one individually. Most likely Chihuahua would've failed (stayed at City); perhaps Aguascalientes itself would've succeeded; in any case, I was thinking of a move review. (Also, B2C, I have so much respect for you, even ywith this disagreement, but like... you gave Spectre 28 hours to respond, give her a bit more time ) Red Slash 17:17, 22 February 2023 (UTC)
- @Born2cycle and Huwmanbeing:: I think this is a problem with these multi-page RMs; indeed, I went into the closing process hoping that I wouldn't have to move the pages. But as it was, the RM was balancing on the scales of "move" vs "no consensus"; the consistency argument isn't as strong given the examples of other cities (in Mexico, Japan, and of course, Cork). I also agree that "X City" would be a decent enough NATURAL disambiguation, were it not for the "don't use natural disambiguations that are obscure" part of WP:NATURAL"; except for the three cases I exempted, I didn't see anything in the RM that adequately rebutted that argument. With all that said, I don't oppose starting new singular RMs if the evidence for "X City" can be shown for the other cities in the list. Sceptre (talk) 19:34, 22 February 2023 (UTC)
- If you don’t see anything in the RM that adequately rebutted that, it’s because you’re ignoring my rebuttal (in the last comment in the RM discussion) which points out that the "don't use natural disambiguations that are obscure" part of WP:NATURAL simply points out an extreme limit to where natural disambiguations are not to be used. It’s quite a leap not supported by local or community consensus to interpret that to mean, “if the natural disambiguation in question is not obscure then it must be used.” Yet you are inexplicably interpreting it to mean that. The key question here is not about whether the natural disambiguation may be used. I mean, in those cases where it’s obscure it may not be used, of course. But in any case where it’s (at least arguably) not obscure that just means it may be used, not that it must be. So, in those cases where the natural disambiguation is not obscure the key question is which disambiguation form is preferred. And, again, consensus was the same for every city in the list: parenthetic disambiguation is preferred to Name City disambiguation in each of these cases. Whether natural disambiguation is allowed or not by NATURAL due to level of obscurity is entirely besides the point. Yet you chose to take that into account. That’s a SUPERVOTE. —В²C ☎ 21:36, 22 February 2023 (UTC)
Move review for Aguascalientes City
An editor has asked for a Move review of Aguascalientes City. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Red Slash 19:24, 23 February 2023 (UTC)
Your userpage
Hi @Sceptre! I landed on your userpage following a recent ANI post of yours and I just wanted to say that I am really quite impressed with the visual structure. I am sure you get this a lot, but it's such a pleasure to read through. I've probably spent more time editing my userpage than I care to admit (lmao) and it's always nice to see some inspirations. Ppt91talk 20:18, 26 February 2023 (UTC)
Hi. I would ask you to reconsider this close. The nomination and support votes were based on a flawed premise, that Confait identified as a trans woman. As I said in the discussion, there is no reliable evidence for this. An editor added it to the article a few years ago and the editors who supported the nomination clearly just supported without checking the evidence (or lack of). In any case, this is a well-known murder in British criminal history and the victim is invariably referred to as Maxwell Confait. We cannot apply modern ideas to something that happened fifty years ago. The rename is a clear violation of WP:COMMONNAME. Thanks. -- Necrothesp (talk) 11:18, 27 February 2023 (UTC)
- @Necrothesp: The relevant guideline here is MOS:GENDERID, which applies to anyone whose gender might (operative word) be questioned. There's no dispute that there's a question about Confait's gender, and furthermore, it's not disputed that they preferred to be known as "Michelle". Additionally, WP:COMMONNAME allows divergence if the most common name is problematic; the amount of "per nom" comments indicate a general agreement that that's the case. Sceptre (talk) 11:55, 27 February 2023 (UTC)
- Yes, but, as I said, the whole nomination seems based on an unsourced edit made to the article some years ago that has clearly been taken as true without any evidence. The supporters have merely accepted that it is true without any knowledge of the situation (note they all came before I pointed this out). Nobody fifty years ago would have referred to themselves as a trans woman. We cannot change history to what we think it should be. We can only report what it was. This is a famous murder case and is invariably referred to as the murder of Maxwell Confait. How is it helping our users to use a name that was never actually used in the many reliable sources on the case? -- Necrothesp (talk) 13:03, 27 February 2023 (UTC)
- @Necrothesp: Whether Confait would've used the phrase "trans woman" or not isn't within the spirit of MOS:GENDERID; indeed, I have a suspicion that the "might be questioned" line was to catch historical cases such as Sylvia Rivera (et. al) where the line between "homosexual transvestite" and "trans woman" are blurred. I've found two other sources further to what was mentioned in the RM which also talk about Confait in the context of being transgender: Reclaiming Genders by Whittle et al, and this Salon article about Amanda Milan, which talks about Confait's murder being at the top of a long list of murdered trans sex workers. As far as I'm concerned, the Gianassi book, alongside those two sources I've listed in this reply, should be enough to meet the "might be questioned" part of GENDERID. Sceptre (talk) 14:57, 27 February 2023 (UTC)
- Yes, but, as I said, the whole nomination seems based on an unsourced edit made to the article some years ago that has clearly been taken as true without any evidence. The supporters have merely accepted that it is true without any knowledge of the situation (note they all came before I pointed this out). Nobody fifty years ago would have referred to themselves as a trans woman. We cannot change history to what we think it should be. We can only report what it was. This is a famous murder case and is invariably referred to as the murder of Maxwell Confait. How is it helping our users to use a name that was never actually used in the many reliable sources on the case? -- Necrothesp (talk) 13:03, 27 February 2023 (UTC)
Move review for Murder of Michelle Confait
An editor has asked for a Move review of Murder of Michelle Confait. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. -- Necrothesp (talk) 14:54, 1 March 2023 (UTC)