User talk:ModernDayTrilobite

February music

story · music · places

Thank you for your support for the composer, with spring flowers and a songbird (in places)! --Gerda Arendt (talk) 18:17, 28 February 2025 (UTC)[reply]

Your close at xkcd

Thanks for providing such a thorough rationale for your close of Talk:xkcd § Requested move 29 March 2025, much appreciated. ("Dispreferred"? You should write press releases. ;) ) Paradoctor (talk) 17:11, 9 April 2025 (UTC)[reply]

I came here to say the same thing! I left that discussion after I felt I had contributed all I could to steer it and ensure participants understood the request and the tradeoffs. I was thrilled to see those tradeoffs accurately described in the closure notice. Thanks!
As for you, @Paradoctor - I know we've had some communications blunders, and I couldn't agree more that it was tiresome, but I hope you don't think ill of me. I think we can both learn from that interaction to define terms unambiguously when it becomes apparent that they are being interpreted differently by different people. I have a much greater appreciation for why every technical and legal document starts with Definitions! NeatNit (talk) 04:26, 10 April 2025 (UTC)[reply]
You stayed civil and responsive throughout, even when the temperatur was high, that's apt to make me think the opposite of "ill" of you.
And if our interaction gave you an appreciation for the ambiguities running through all natural-language communication, then it was effort well spent. No worries here. Paradoctor (talk) 05:21, 10 April 2025 (UTC)[reply]

You have given weight to the argument that this title falls to MOS:GEOCAPS. This is clearly a pettifogging argument that should have been WP:DISCARDED. A simplistic definition of a proper noun/name is that it is the name of a particular person, place or thing. A fuller definition, such as our own article or this definition, is that a proper noun is not descriptive. As stated in debate: While specificity of referent is a property of proper names, it is not a defining property, since specificity is also achieved by use of the definite article (the). The notion that GEOCAPS applies was only introduce after the penultimate VOTE!. It was debated and garnered no support. The ultimate VOTE! did not even tacitly acknowledge it. The assertion that GEOCAPS was tacitly acknowledged by other editors is not supported. Where they have referred to it as being a proper noun it is reasonably apparent they have done so from the view of the simplistic definition. However, WP relies on evidence of usage and not definition to determine what should be capped. To the statement: per MOS:GEOCAPS—the term "Galactic Center" refers to a specific location within the Milky Way and therefore meets the guideline's standard for capitalization, one needs to consider the spirit and intent of the guidance evidenced through the examples: These are treated like other proper names and take an initial capital letter on all major elements: Japan, Mount Everest, Gulf of Tonkin. Terms for types of places and features do not take capitals: the town hall; the capital city; an ocean; the savannah; karst topography. Japan, Everest and Tonkin are not descriptive but the capitalisation of mount and gulf are determined by usage. The town hall, the capital city and the savannah all have specific referents by virtue of the definite article - as does the galactic center per the lead of the article. GEOCAPS specifically links to Wikipedia:Manual of Style#Geographical items and Wikipedia:Naming conventions (geographic names). There is nothing that would suggest that the pertinent guidance applies to a descriptive name (galactic center) except by virtue of usage in sources or that the guidance is intended to apply to the celestial domain, for which we have separate guidance. Where you state: ...arguing that the capitalization served to distinguish the Milky Way's galactic center from others, is capitalisation for distinction that explicitly falls to MOS:SIGNIFCAPS - a matter specifically raised in discussion and which we don't do. Cinderella157 (talk) 12:00, 13 April 2025 (UTC)[reply]

  • Thank you for your very good close. The Galactic Center of the Milky Way is surely a geographical place (although I wouldn't want to visit). Walls of text are also a geographical place, but not subject to MOS:GEOCAPS, unlike the Galactic Center. Randy Kryn (talk) 12:17, 13 April 2025 (UTC)[reply]
As I see it, your comment has two main arguments in respect to my close, so I'll aim to address each one individually:
  • First, re: whether it is appropriate to "read into" a !vote as being implicitly backed by a policy or guideline. I believe this is an appropriate and normal part of evaluating a discussion. The policies and guidelines give us direction as to which considerations to prioritize over others, but they are also intended as documentation of our values as an encyclopedia, and arguments that are aligned with those values should be considered even if the speaker doesn't fish out the exact policy name that described them. To use an example, someone who supports an RM because it "removes ambiguity" is clearly gesturing to WP:PRECISE, even if they don't realize it themselves. I'm not trying to say this scenario was as clear-cut as my example, but—when one person cites a policy or guideline in making their case ("GEOCAPS holds that we should capitalize this because...") and others make substantially the same argument but without alluding to the policy/guideline—I believe it to be reasonable to treat the same level of policy backing as applying to the other comments too. Of course, this approach hinges upon the actual policy interpretation being correct, which leads us to the other point...
  • Re: the underlying interpretation of GEOCAPS. My responsibility as a closer is not to impose my own interpretation of any guideline but to reflect the interpretation that prevailed among the discussion participants; I shouldn't be overriding their interpretations unless they're obviously faulty, such as an argument citing WP:PRECISE to support clear overprecision. While there were certainly debates in the RM over how to interpret the guidelines that came into play (CELESTIALBODIES, GEOCAPS, SIGNIFCAPS), I don't feel any of the arguments from either side were clearly erroneous enough to merit outright discarding, so my role was to compare the interpretations on offer and gauge which interpretations were more strongly supported by the participants at large. (This does necessarily involve some consideration of numerical support, but I aim to make sure it's not a simple headcount by according additional weight to participants who are able to cogently lay out arguments for why their preferred interpretation should hold.)
In summary, when taking this approach, I feel that it was within reasonable discretion to weigh the arguments as I did. I think a no-consensus closure could also be a plausible interpretation of how the different arguments balanced against each other, and I would be willing to shift my close to "no consensus" if people feel that that more closely captures the relative weight of the different strands of argument, but I don't feel that the discussion could be reasonably described as having reached a consensus to move. ModernDayTrilobite (talk • contribs) 14:59, 14 April 2025 (UTC)[reply]
And why aren't you teaching a class in how to write up a closing analysis? Your close seems correct, as the fact that the Galactic Center is a defined 'place' gives adequate weight to the use of MOS:GEOCAPS. Understanding that the counter arguments in favor of lowercasing the page to a name that would fit any galaxy's center if further Wikipedia pages become written - and given the technology and discoveries the James Webb Space Telescope has already made, new pages may occur - also brings a bit of commonsense into the mix. Thanks for the time you take in presenting thoughtful closes. Randy Kryn (talk) 15:25, 14 April 2025 (UTC)[reply]
Of the oppose comments, two out of four specifically make an a priori assertion that it is a proper name and a third, that it the formal name. None of these offer a substantive reason or evidence to support the assertion consistent with the prevailing P&G. They are a personal opinion falling to WP:DISCARD. In your example, using the word precision rather than a direct link (WP:PRECISE) is not a great leap. However, just invoking a particular piece of P&G does not give weight to a comment. Weight comes for establishing how a particular guideline applies to a particular case and that the conclusion is consistent with what the guideline actually says. Many that might cite precision to support their view actually argue for WP:OVERPRECISION - ie the P&G is being misconstrued. A closer is expected to discern that the P&G actually contradicts the argument being made - particularly if it is refuted in the debate as being incorrect. In this case though, it would be a substantial leap of faith to assume or imply that any of these comments (apart from Randy) is making even the vaguest allusion to GEOCAPS. All four comments assert capitalisation for distinction - which is flatly contradicted by MOS:SIGNIFCAPS as a rationale for capitalisation on WP. Randy's argument is essentially: Milky Way's [galactic centre], which, like Moon, is uppercased per MOS:GEOCAPS and naming convention. But each galaxy has a galactic center, so to differentiate the Milky Way's from the others (like the uppercased Moon) it is a proper name. Setting aside that the Moon is capitalise because of CELESTIALBODIES not GEOCAPS, the argument is that because it is a specific place, it is a proper name capitalised for distinction. However, as explained in the debate, specificity of referent is not a defining property of proper names and the examples at GEOCAPS bares this out - eg the savannah has a specific referent but is not capitalised. There is more to GEOCAPS (and what is a proper name) than just having a specific referent. The spirit and intent of the GEOCAPS is being misconstrued. Per WP:DISCARD: Closers are also required to exercise their judgment to ensure that any decision complies with the spirit of Wikipedia policy. As you say, it was convincingly shown that there isn't a usage-based case for uppercasing the term. The rationales given in the close appear to try way too hard to give weight to a pettifogging argument to overturn an argument for which the consensus is otherwise very clear. Cinderella157 (talk) 02:16, 15 April 2025 (UTC)[reply]
I had to look up the word "perttifogging". For readers in the same boat I was: "Pettifogging refers to giving too much attention to small details that are not important. It is an old-fashioned term and is often used disapprovingly to describe behavior that focuses on insignificant matters or is meanly petty." The 'small detail' here is that the Galactic Center, in astronomical and scientific circles, describes an exact place. Something you can put your finger on. Thus it fits MOS:GEOCAPS. Pettifogging, as defined, is not used correctly here. Randy Kryn (talk) 02:37, 15 April 2025 (UTC)[reply]
When all's said and done, I think we ultimately have incompatible interpretations of the underlying policies. I evidently read MOS:GEOCAPS as having a broader mandate than you do (and conversely, read MOS:SIGNIFCAPS as having a narrower one), and I think that dichotomy is what's at the root of our disagreement here. To my eye, the participants in the RM drew a clear semantic distinction between a general "galactic center" and the specific location "Galactic Center" within the Milky Way—and because of this semantic distinction, I don't believe that SIGNIFCAPS covers this situation in the way you've been describing. Meanwhile, I don't feel that the Galactic Center being an example of a galactic center necessarily precludes GEOCAPS from applying. I agree that it's necessary to ensure compliance with the spirit of policy, but doing so becomes a complex question when we're not in agreement about what the spirit of policy is in the first place.
Admittedly, my view has shifted slightly since my initial close, such that I think a no-consensus closure is probably more appropriate than a consensus-against-moving. While I still think that the GEOCAPS argument is sound, you've also highlighted a salient point that any questions around the policy basis for or against uppercasing the term are ultimately competing against a mixed usage pattern, with the result that I think the usage argument and the GEOCAPS argument counterweight each other enough to prevent either from becoming clearly dominant. The reason I'm just describing this shift and not yet editing my actual close is because I imagine, if you're still looking to overcome the underlying differences in our policy interpretations, an MRV will probably resolve our debate more decisively than further one-on-one conversation would. Changing my close shortly before a likely MRV seems like it would needlessly muddy the waters of that discussion, so I'm happy to hold off on making any edits to my close until I know whether you'd like to pursue the MRV route or not. ModernDayTrilobite (talk • contribs) 04:47, 15 April 2025 (UTC)[reply]
If you are actually going to edit your close please consider adding more weight to the the Simbad uppercasing brought forward near the end of the discussion. Instead of a minor point, Wikipedia asks us to consult Simbad in situations like this. When the editor did so they arguably, and correctly, cemented uppercasing. In addition, and importantly, if you are accepting new arguments like those above, here's a new one which further places Galactic Center uppercasing in place: Wikipedia's naming conventions tell us to first and foremost consult IAU for anything related to galaxies. Here is what IAU has to say about it. Thanks. Randy Kryn (talk) 05:11, 15 April 2025 (UTC)[reply]
You would give more weight to GEOCAPS but less weight to SIGNIFCAPS, which raises several questions.
  1. If I said that I am going to: Japan; Mount Everest; the Gulf of Tonkin, Boston (which could be one of two dozen odd places); or, the town hall, the capital city or the savannah; in each case, I am referring to and going to a definite specific place. In the latter, this is because of the definite article (the). How is it (why does) the galactic centre (of the Milky Way) fall to the former examples and not the latter? What in GEOCAPS makes the distinction clear?
  2. SIGNICAPS states: This includes over-capitalization for signification, i.e. to try to impress upon the reader the importance or specialness of something in a particular context. Those that oppose the move assert a need to capitalise to distinguish the Milky Way's galactic centre from that of other galaxies. Isn't this a case of impress[ing] upon the reader the importance or specialness of our galaxy's centre? Capitalising for distinction is inherently using caps to denote the specialness of the Milky Way's centre compared with the centre of other galaxies. How is it that, capitalisation for distinction does not fall to SIGNIFCAPS in a way that the assertion is flatly contradicted by the P&G and should be discarded?
  3. Where an argument is made that caps are necessary for distinction, this has been effectively rebutted: While an argument is made that there is a distinction in capitalisation between the galactic centre of our galaxy and that for other galaxies, this is not bourn out by evidence, where the majority of references are to our galaxy [made in the context of a review of google scholar]; and, Per the actual evidence indicated, it is far from always capped in sources in the context you indicate and is not a proper name that we would cap per NCCAPS, where the indicated evidence would be google scholar. To paraphrase this a question: If capitalisation to distinguish the Milky Way's centre is necessary, why then is it that a good majority of authors writing about the Milky Way's centre see no need to capitalise galactic centre?
Cinderella157 (talk) 10:00, 15 April 2025 (UTC)[reply]
Re: GEOCAPS, I think the fundamental distinction is whether a given appellation is an established name of an entity or just a descriptor of it. Sometimes, the name of a location can overlap with one of its descriptors—London's Natural History Museum is just one of many natural history museums—in a way that blurs those lines. You ask what in GEOCAPS makes the distinction clear, but honestly, I don't think there is a clear distinction drawn for these particular cases; we have to evaluate the evidence on a case-by-case basis to gauge whether there's a proper noun or not.
Re: SIGNIFCAPS, I disagree that capitalizing for distinction is attempting to indicate the importance or specialness of what's being distinguished—it's simply indicating that the term covers a meaning distinct from that of its lowercase version. The example given in SIGNIFCAPS is of a capitalized "Scientific Consensus", where the caps are solely being used to identify the term as a significant piece of terminology within its passage. In this example, a Scientific Consensus is not identified as being anything different from a lowercased scientific consensus, and so the caps are purely for signification. By contrast, supporters of the capitalized "Galactic Center" made the case that there did exist a semantic distinction to justify the capitalization.
Ultimately, though, while I wanted to clarify my thinking, I still can't help but feel like our views on this policy are too divergent to really be bridged. In the interest of not going around in circles any further, I'm going to vacate my close and reopen the RM. ModernDayTrilobite (talk • contribs) 14:42, 15 April 2025 (UTC)[reply]
Withdrawing the close resolves the key issue. However, you may or may not realise a very pertinent point you have made in reply: but honestly, I don't think there is a clear distinction drawn for these particular cases; we have to evaluate the evidence on a case-by-case basis to gauge whether there's a proper noun or not - which takes us back to the evidence of usage. What is a proper name is something generally poorly understood since many rely on the simplistic definition. A true proper name is not descriptive and unfortunately, people are inclined to categorise all of the things that are conventionally capitalised in English as proper names. For example, we conventionally capitalise the names of businesses and institution such as London's Natural History Museum, even though such names are often descriptive. Whether the title of a work (eg a book) is a proper name is debatable. There are many books printed with the same name and we would use the indefinite article: I was reading a book called "To Kill a Mocking Bird". The intellectual property is abstract, not concrete and cognitive development studies relate that proper names are associated with the concrete. Rather than categorising titles of works as proper nanmes (even though the title might be quite descriptive of content), it is perhaps better to say that we use title case for the titles of works. Place/feature names like: London, Pacific, Tonkin and Nile may have an etymology but are not descriptive, though they sometimes have an associated class descriptor such as: ocean, gulf or river, which is sometimes near always or sometimes much less often capped. Wikipedia:Naming conventions (geographic names) acknowledges these descriptors should not always be capitalised. In some ways, it begs the question of whether it is galactic or centre which is the descriptor here, but both are. Something like the Rocky Mountains are inherently descriptive but it is still an arbitrary name, in as much as it might just as easily have been given a different name (eg what if the Pacific had been stormy when Magellan sailed into it?). My working hypothesis on the capitalisation of these descriptors is that we tend to translate cartographic conventions into prose. SIGNIFCAPS refers to terms of art, which are part of the jargon of any field of study or occupation. Such descriptive terms often have a more specific meaning than denoted by the descriptive phrase and are often distinguished by capitalisation. This is directly analogous to capitalisation of galactic centre to denote the centre of the Milky Way, rather than any other galaxy. WP:SSF addresses this use of capitalisation and that essay is supported by citation. The understanding of vocational jargon as a barrier to learning was part of my studies as a vocational educator. This isn't so much to convince you but you may be interested in a different perspective. Cinderella157 (talk) 04:16, 16 April 2025 (UTC)[reply]
Again, you didn't answer my added information above, especially the IAU link which, alongside the Simbad focus brought late in the discussion, should have addressed your concerns about maybe-maybe not. Reopening the discussion seems to be giving into the noisiest bell, but on the other hand it does give me the chance to introduce IAU and the galaxy guideline into the mix. Randy Kryn (talk) 15:03, 15 April 2025 (UTC)[reply]
In my original close, I hesitated to place too much weight on the capitalization in Simbad, since I thought a fair concern was raised in the discussion as to whether Simbad uses sentence case or title case for titling its entries. A title-case source won't be much help for determining whether a term is capitalized or not in sentence case, after all. That said, the reopened discussion will hopefully allow editors to discuss Simbad in more depth; if that further discussion leads us to a consensus, whatever that consensus may be, then it will have been a success in my book. ModernDayTrilobite (talk • contribs) 16:32, 15 April 2025 (UTC)[reply]
I don't know if this is done, but if it is maybe you can come by and reinstate your original close edited with information provided since you relisted the page a couple of weeks ago. If anything the case for "not moved" is stronger since the relist. Thanks. Randy Kryn (talk) 03:33, 29 April 2025 (UTC)[reply]
I appreciate the outreach, but personally, I prefer not to reclose discussions I've already closed and reopened—even if more discussion has taken place, it still feels to me like I'd be taking two bites of the apple by closing the same discussion again. ModernDayTrilobite (talk • contribs) 04:07, 29 April 2025 (UTC)[reply]
Thanks, thought I'd ask as you got it right last time. Makes me wonder now where that expression came from and what is wrong with taking a second bite of an apple. I'll look around and try to find out. Thanks again. Randy Kryn (talk) 04:11, 29 April 2025 (UTC)[reply]
aha, seems to be taking two turns at bobbing for apples. Randy Kryn (talk) 04:14, 29 April 2025 (UTC)[reply]

RfC on guidance for alternative/bonus track-listings on album articles

I've started an RfC about the guidance at MOS:ALBUMS for alternative and bonus tracks. I've notified you because you've participated in a past discussion of the issue. See the discussion at Wikipedia_talk:WikiProject_Albums#RfC_on_bonus_and_alternate_track_listings.--3family6 (Talk to me|See what I have done) 17:48, 14 May 2025 (UTC)[reply]

Thank you for the notification! I'll take a look. ModernDayTrilobite (talk • contribs) 18:32, 14 May 2025 (UTC)[reply]

RM closure on Kiko Pangilinan

I know that it's not a vote, and you alluded it on the close, with the nominator, Pat, and Royiswariii supporting and only me opposing. Pat's !vote rested solely on the fact that it was the "WP:COMMONAME", and was disproved by the replies to my !vote. Royiswariii materially misrepresented his !vote. I would have appreciated this to have been relisted for the meantime. Howard the Duck (talk) 15:29, 27 June 2025 (UTC)[reply]

To expound on my reasoning in a bit more detail: given your criticism of the sources Royiswariii linked, I spot-checked them myself to confirm how Pangilinan's name was used, and I noticed that—while you correctly pointed out that both ABS-CBN and the Senate biography first mention him as Francis "Kiko" Pangilinan—they also both go on to refer to him later as "Kiko" alone. Thus, I felt it was ultimately fairest to factor in those sources when making my analysis, with the result that there were a comparable volume of sources provided in the discussion supporting either name. Accordingly, I don't think the WP:COMMONNAME argument was disproved so much as contested. And, while a discussion as a whole isn't a vote, I think that—where a discussion includes a dispute on the interpretation of a given policy, and the arguments are of comparable strength—it can nevertheless be useful to consult the relative numbers supporting either interpretation to determine which interpretation is the "mainstream" one, so to speak. When I took all of those factors into account, I felt that a closure of "moved" was ultimately most appropriate. ModernDayTrilobite (talk • contribs) 16:47, 27 June 2025 (UTC)[reply]
FWIW, the ABS-CBN article was the WP:RS among the two, with the official Senate biography being WP:SELFPUBLISHED. With that being said, Pat's reasoning was ill-informed; he thought that "Most media outlets" referred to Bongbong Marcos as "Ferdinand Marcos" when it wasn't the case. His !vote was based on wrong information.
Ultimately, it boils down to the nominator TheNuggeteer, who did not offer proof(!) and Royiswariii, who misrepresented sources, vs. my findings (and comparisons to other people, notwithstanding Marcos). Howard the Duck (talk) 18:57, 27 June 2025 (UTC)[reply]
Fair point on the Senate biography being self-published, but even if we remove that from consideration, that doesn't dramatically change the ratio of sources presented. (The GMA article, which I forgot to mention before, is analogous to ABS-CBN in first using both names but using "Kiko" later down.) As for the other concerns you mention, I'm not sure any of them rise to the level of affecting my findings. Media outlets' discussion of Bongbong Marcos isn't relevant to this RM; Pat may have been wrong about how media outlets refer to Marcos, but that doesn't have any bearing on the actual topic of the RM. TheNuggeteer may not have furnished proof for their claim, but it was substantively the same claim for which Royiswariii later offered evidence, namely that "Kiko" is Pangilinan's best-known—i.e., common—name. If multiple editors make the same claim, it would be needlessly bureaucratic to require them each to independently prove it. Finally, as I mentioned in my previous message, I evaluated Royiswariii's sources myself due to the dispute over how they name Pangilinan—and while Royiswariii could have been more forthcoming about the sources mentioning the name "Francis", I don't believe they "misrepresented sources" in a materially significant way. ModernDayTrilobite (talk • contribs) 19:57, 27 June 2025 (UTC)[reply]
I did offer other WP:RS that exclusively use "Francis Pangilinan", exclusively without the "Kiko" name (it was a reply to Pat's reply); while I do not expect that completely invalidates Royiswariii's materially misrepresented submissions, it should have been given at least a relisting (sorry I dunno if WP:RMs are relisted).
To recap:
  • TheNuggeteer made a claim with no basis.
  • Pat seconded TheNuggeteer's claim, also with no basis, and even had the wrong impression on other things, that had it apply to the discussion at hand.
  • I presented WP:RS that specifically excluded the "Kiko" name, and pointed out Pat had the wrong impression on how Marcos was primarily known, and that it should not had applied on how Pangilinan's article is titled here.
  • Royiswariii materially mispresented some of his findings. He is the only person aside from me to present actual proof from WP:RS.
At the very least, this could had been relisted if that was an option. Howard the Duck (talk) 20:34, 27 June 2025 (UTC)[reply]
I considered the RS you mentioned in your comment on the RM as well, yes; I apologize if I gave the impression that I had overlooked them. However, reviewing the evidence collectively from all parties suggested that both names were used for Pangilinan, at roughly comparable frequencies. With the evidence not obviously preferring either name, I also factored in editors' broad appraisals of the overall usage, to get a sense of which interpretations of the COMMONNAME argument appeared to be found most compelling by the community of participants. To that end: while an evidence-free assertion like those made by Pat or TheNuggeteer would not have been convincing in a vacuum, it was significant to me that they were substantively identical claims to the one made with evidence by Royiswariii. Roy's evidence made clear that the COMMONNAME argument was at least plausibly sound (again, I disagree that any misrepresentations he made were material). With that evidence presented, it would be unduly bureaucratic to throw out other comments that made the same argument, even if those other comments were posted chronologically before the evidence was provided. Finally, as I said in my previous comment, Marcos was not the topic of this RM and questions of how to present his name did not impact my decision-making process. ModernDayTrilobite (talk • contribs) 21:39, 27 June 2025 (UTC)[reply]
To sumarrize, TheNuggeteer initiated the RM with no proof. If this was AFD this should have been pointed out already. Pat then seconded TheNuggeteer. Again, if this was AFD both !votes should had been discounted. I then said people know this guy as "Francis" with the nickname "Kiko". It's different from the list of people I listed on my first comment. Now, I should not have brought Bongbong Marcos onto the discussion; that's on me. Pat asked about the exception (people know Bongbong's given name is "Ferdinand"), since if people know Bongbong=Ferdinand, so Francis=Kiko, with him saying " media outlets and government sources refer to him as President Ferdinand Marcos Jr.", which is empirically false. I had the impression he based his !vote on TheNuggeteer's opening statement not based on any policy, then asked me if my !vote was grounded in policy. Which I did, and presented two WP:RS that use the name "Francis Pangilinan" without the name "Kiko" (to demonstrate the difference with Paolo Benigno, Christopher Lawrence, Victor Ma. Regis, Maria Josefina Tanya).
Royiswariii then, and materially represented saying "all sources"... "recognized as 'Kiko Pangilinan'"... "demonstrate the WP:COMMONAME". This is an empirical example of material misrepresentation LOL. Only one of his submissions "demonstrate the WP:COMMONAME"... "as 'Kiko Pangilinan'". One other submission was not WP:RS, or what were indeed WP:RS combine Kiko with Francis. If he's arguing for the article to be named as "Francis Kiko Panglinan" his argument made sense.
Again, I am not saying for you "to throw out other comments". I was asking for relist. Howard the Duck (talk) 21:59, 27 June 2025 (UTC)[reply]
A relist is certainly possible, but the RM was already relisted once prior, and I'm generally skeptical of the utility of RM relists beyond the first. The discussion had been open for 45 days and hadn't received a comment in 22; I think it's very well within standard norms to close an RM that's been languishing unedited for three weeks, and to be honest, I'm not at this point convinced that I've made any errors in my close that would necessitate overturning it.
To further clarify my thinking on Royiswariii in particular—while several of the sources he linked did indeed use the structure "Francis 'Kiko' Pangilinan" when first introducing Pangilinan, each source that did that also went on to refer to Pangilinan at least once as simply "Kiko" in the article body (and never as just "Francis"). I can furnish quotes if desired. Where both of these behaviors coexist in a source, my interpretation is that that source views "Kiko" as the subject's most recognizable name, and uses a more comprehensive form at the start for purely introductory purposes (not unlike how, in biographical articles here on Wikipedia, we break out a subject's full birth name a single time at the very beginning of their lead). That reason is why I didn't view Royiswariii as having made "material" misrepresentations; he didn't describe the sources he linked with complete accuracy, but when checking the actual source content, I believed that they still supported the argument he was trying to make.
(I think I've already explained my views on all of the other comments you refer to, so I'll avoid making this already-long comment any longer, but please feel free to let me know if there's any points on which further clarification would be useful.) ModernDayTrilobite (talk • contribs) 01:57, 28 June 2025 (UTC)[reply]
If you can relist so many number of times, I'd concede that at that stage of the discussion, it may have been extended to a point nobody cares anymore.
As for material misrepresentation, we are not moving the article to "Kiko" or even "Francis Kiko Pangilinan". News articles do not use the entire name, and my personal rule on this is how the subject was referred to in the first reference, that's how the article wants to call the person. Otherwise, we move Michael Jordan to "Jordan" and Michael Jackson to "Michael", Or that Cristiano Ronaldo is "Ronaldo", ignoring WP:PRIMARYTOPIC.
I'm glad though you conceded that Royiswariii "didn't describe the sources he linked with complete accuracy", which is a rather lengthy way to say he materially misrepresented his !vote, and his vote being the only material of those who supported, including the nominator. With that being said, I'll see what else can be done about this. Howard the Duck (talk) 02:19, 28 June 2025 (UTC)[reply]
For reference, if you're interested in formally contesting the close, the standard venue for that is Wikipedia:Move review. ModernDayTrilobite (talk • contribs) 16:26, 28 June 2025 (UTC)[reply]

Discussion regarding the "Non-lethal weapon" move request closure

Hello ModernDayTrilobite,

You recently closed the move request for "Non-lethal weapon" to "Less-lethal weapon." I appreciate you taking the time to close the discussion.

However, having reviewed the decision in the context of previous discussions on this same topic from 2021 and 2020, I believe the closure warrants a second look. The rationale that "non-lethal weapon" remains the WP:COMMONNAME doesn't seem to fully account for the significant, policy-based arguments that have been consistently raised. I would like to discuss this with you before considering a formal move review. My main concerns are as follows:

1. Flawed Interpretation of WP:COMMONNAME and Consensus: Your closing statement suggests a clear consensus around WP:COMMONNAME. However, this issue has a long history of being contentious, with the 2021 move request on this exact topic being closed as "no consensus" because there were "valid argument[s] made on either side." The arguments in the most recent discussion were largely the same, yet the outcome was a firm "not moved." This suggests the current closure may have relied more on a simple headcount of !votes rather than weighing the policy-based arguments, which is how consensus on Wikipedia is determined. When a common name is not definitively established or is actively contested, other policies like WP:PRECISION must be given greater weight.

2. Weight of Evidence for COMMONNAME and Authoritative Sources: The claim that the "data furnished appeared to corroborate" the use of "non-lethal weapon" is an oversimplification that ignores compelling counter-evidence. Usage Data: The discussion about Google Ngrams showed that combined usage for "less-lethal weapon(s)" in books has overtaken or matched non-lethal. Additionally, my point about Google News traffic—which reflects more current, common usage in media—was not substantively addressed. As was detailed in the 2021 discussion, a closer look at sources like The Washington Post reveals a clear editorial shift toward "less-lethal" in recent years, indicating that common usage among high-quality sources is actively evolving.

3. Authoritative Sources: Furthermore, the argument about WP:OFFICIALNAME is not as clear-cut as presented. While the Department of Defense and NATO may use "non-lethal" in official definitions, many other authoritative bodies, particularly in law enforcement and justice, have adopted "less-lethal." For instance, the U.S. National Institute of Justice uses the term "Less-Lethal Methods" in its use-of-force continuum, and the California Penal Code provides a specific legal definition for "Less lethal weapon." This is echoed internationally by the United Nations, which uses "less-lethal" in both its Peacekeeping standards and Human Rights guidance, and the UK's College of Policing. This indicates "less-lethal" is not an informal term but one with formal standing among a wide array of authoritative sources.

4. Ignoring the Core Issue of Accuracy (WP:PRECISION): The central, recurring argument across all discussions is that "non-lethal" is factually inaccurate. These weapons can and do kill. As one editor noted in 2020, this isn't an opinion, it's a fact. Even sources that use the term "non-lethal" often feel compelled to add a caveat explaining they can be fatal, which itself proves the term is misleading. Wikipedia's naming conventions aim for accuracy. When faced with a choice between a precise term ("less-lethal") and a demonstrably imprecise, even propagandistic, one ("non-lethal"), the encyclopedia should favor precision and NPOV.

This is not a new or frivolous request; it is a long-standing issue rooted in a fundamental conflict between an inaccurate, though historically common, term and a more precise, modern alternative now widely used by authoritative sources. The persistence of this debate shows a genuine, policy-based concern that has not been adequately resolved.

Given the prior "no consensus" result and the significant evidence favoring a shift in usage and the importance of precision, I believe the recent closure was premature. I would appreciate it if you could reconsider your close or provide a more detailed rationale in light of this history.

Thank you for your time and for your work as a page mover. Sincerely,Poketama (talk) 03:57, 2 July 2025 (UTC)[reply]

To address your points in turn:
  1. It's important to remember that consensus can change—an argument that fails to gain consensus at one time could gain consensus at another, due to shifts over time in any number of factors. The whole reason that this RM was started was to pursue a consensus that was not found in 2021, so it seems illogical to argue that finding consensus on a previously no-consensus topic is inherently suspect. Additionally, while a discussion is certainly more than a simple headcount, it's also the case that—where a discussion involves competing (but both plausible) interpretations of the same policy, as happened with WP:COMMONNAME here—it can be useful to refer to the numbers favoring each argument to get a sense of whether one interpretation is substantially more mainstream than another.
  2. The full discussion of the Ngrams made a compelling case that the data showing "less-lethal" as having surpassed "non-lethal" was rooted in methodological errors. When reviewing the final Ngrams data presented at the end of the conversational thread, even when adding "less lethal weapons" as you'd suggested in the discussion, I saw a clear lead for the various forms of "non-lethal weapons" over the forms of "less-lethal weapons". As for Google News, when I reviewed the Google News links you shared, it showed me 22,300 results for "non-lethal weapons" vs. 13,700 for "less-lethal weapons". Thus, even if Google News is inherently more reflective of common usage than Google Books (a premise that I'd want to see more widely supported before accepting, honestly), its findings don't seem to change the calculus.
  3. This is a fair point, but it moves the argument of "what name predominates in official definitions" to "it's inconclusive" rather than "less-lethal weapons is clearly favored". In any case, it's long-held practice that COMMONNAME supersedes arguments based on official names, so this point would not significantly change the result of the discussion unless there was a strong consensus that the COMMONNAME should not be used.
  4. WP:PRECISION is about avoiding ambiguity, not about enforcing accuracy. Many topics are known by names that aren't fully accurate—as an example off the top of my head, the flying squirrel can't actually fly. What matters for Wikipedia's naming conventions is that the title is accurate to what the topic is called, rather than necessarily reflecting how it functions in practice. (Descriptive titles are an exception to this, as those are titles that by design are specifically crafted for Wikipedia, but this isn't one such case.)
In summary, based on the arguments presented on each side of the discussion, I felt that the strength of argument supported the claim that "non-lethal weapon" remained the common name for the topic; the common name question occupied a large majority of the discussion, and other arguments were mentioned passingly enough (or, in the case of the official name, were dubious enough) that they didn't have a substantial impact on the overall consensus of the discussion. Let me know if there are any points that would benefit from further clarification. ModernDayTrilobite (talk • contribs) 14:25, 2 July 2025 (UTC)[reply]

Very nice close, imo, and a good reading of the consensus. Great job! I think it's very likely that the eventual title of the article should be Nuseirat raid, but this discussion provided insufficient consensus to justify that move. Cheers, Suriname0 (talk) 22:03, 25 July 2025 (UTC)[reply]

  • Thanks for the closure at Talk:Nuseirat rescue and massacre. Since you wrote such a detailed and thoughtful closure, may I ask you questions about your interpretation of WP:COMMONNAME policy, as you cited it in your closure? COMMONNAME requires a "prevalence in a significant majority of independent, reliable, English-language sources". But how do we determine "prevalence" and how do we compute "significant majority"? It seems that many places where we prefer "massacre", the name is perhaps not actually used by >50% of sources that actually use that name (see this comment) – and those results on whether you consider "massacre" to be a common noun or part of the proper noun (see this comment). I would love your thoughts on this issue. VR (Please ping on reply) 14:41, 10 September 2025 (UTC)[reply]
    It's been long enough since the closure that I can't recall my exact thought process from the time in detail, but I can certainly talk about general principles. The "significant majority" threshold is, in my opinion, deliberately inexact; its intent is to allow editors to review the fact patterns of an individual case and (strive to) come to a holistic consensus about whether a prospective title has reached it, rather than to create a bright-line standard at some percentage. (For one example of how fact patterns might affect the calculations at play: a common convoluting factor in RMs is WP:NAMECHANGES, which can make it desirable to downweight a large amount of sourcing due to its age.) Accordingly, when I'm closing a discussion, I don't come into it with a preconceived idea of "what constitutes a significant majority"; instead I review the specific arguments made in the discussion for strength and influence to determine how the discussion participants feel a "significant majority" should be defined in relation to the topic. ModernDayTrilobite (talk • contribs) 17:52, 10 September 2025 (UTC)[reply]

Orion (constellation) move request

Great close :) (and a cookie)

Raladic (talk) 16:01, 14 August 2025 (UTC)[reply]

Mario Move Review

Thanks for closing the Mario move review. I think you made a typo in the second sentence when you wrote "Interestingly, several proponents of vacating the existing close argued that the result of the MRV..." because I think it's supposed to say RM not MRV. ~~ Jessintime (talk) 04:15, 16 August 2025 (UTC)[reply]

Whoops, yes, that is indeed a typo— thank you for catching it! ModernDayTrilobite (talk • contribs) 05:15, 16 August 2025 (UTC)[reply]

Richard Baumhammers RM closure

I believe there was no objection to Richard Baumhammers shooting spree. I thought we had settled on using that (or something similar). —⁠ ⁠BarrelProof (talk) 19:25, 19 August 2025 (UTC)[reply]

Parakanyaa continued to show opposition to an event-based title even after "Richard Baumhammers shooting spree" was proposed (diff); also, while Cutlass' latest comment didn't explicitly state whether "Richard Baumhammers shooting spree" addressed their concerns, their choice of phrasing—"the perpetrator is worthy of discussion in other ways besides the event"—suggested to me that they still found the biographical title preferable to any event-based title. Thus, even though the opponents of the original proposal seemed more amenable to "Richard Baumhammers shooting spree" than to "2000 Pittsburgh shooting", I didn't get the impression that either of them had swung as far as to be actively in favor of it. For that reason, I felt that the title "Richard Baumhammers shooting spree" hadn't managed to make it across the line of consensus. ModernDayTrilobite (talk • contribs) 19:42, 19 August 2025 (UTC)[reply]
Thanks. I hadn't noticed that. —⁠ ⁠BarrelProof (talk) 21:57, 19 August 2025 (UTC)[reply]

Gamergate MRV

On Wikipedia:Move review/Log/2025 July#Gamergate: I think you're right that there isn't a consensus, but maybe a more interesting question is whether this is a situation where it'd be more appropriate to treat a finding of "no consensus" as equivalent to a "relist", as Wikipedia:Move review#Closing reviews allows. I don't have a firm opinion either way (and ultimately it's left to the closer's discretion), but I was just curious whether you'd considered that option and, if so, how you went about deciding. Extraordinary Writ (talk) 03:57, 3 September 2025 (UTC)[reply]

I did briefly consider relisting, but I ultimately leaned against it for a couple of reasons. I think the core philosophical point that underlay my decision is that, past a certain point, I believe extending an already lengthy and complex discussion begins to have diminishing returns; an already long, vigorous debate is harder to get involved in as either a participant or a closer, creating a risk that—if there's no influx of new editors to enter or close the RM—relisting the discussion would only get us farther away from a resolution of the titling question. Paradoxically, I think letting a discussion remain closed can actually lead to better discussion of the topic in the long term, as—if the same debate reemerges—both sides will have refined their arguments through the previous discussion's back-and-forth and will be able to subsequently present their strongest arguments with minimal "required reading" baggage.
With these ideas in mind, I was reluctant to reopen/relist the RM unless it was clearly one of the most preferred outcomes by the MRV participants—but it didn't seem to pick up significant support. Instead, my read was that even the majority of pro-overturn editors favored overturning directly to no consensus rather than relisting the original discussion. The age of the MRV also caught my eye, as reopening a discussion two months after its closure is undoubtedly a more drastic step than reopening that same discussion when only a week has passed. Reopening a discussion that has been closed for months can be a destabilizing or disruptive event for an article, and it was a solution that attracted only modest traction in the MRV, so ultimately I felt that "no consensus at MRV → the RM closure is allowed to stand" was the route that felt most in keeping with the will of the discussion and the longer-term pursuit of consensus. ModernDayTrilobite (talk • contribs) 05:54, 3 September 2025 (UTC)[reply]
Yeah, that's definitely fair. I've always thought it's an interesting rule (one that explicitly gives the closer total leeway and zero guidance), so I enjoy getting a sense of how others think about it. A while back I jotted down a few notes on some of the basic considerations, but a bullet-point list can only capture so much, of course. I tend to use my discretion similarly to what you're describing, but more creative/unintuitive approaches (like this one) can be tempting sometimes too.
Anyways, thanks for indulging me. Your closures are consistently excellent—I'm always glad when I see one pop up on my watchlist. Extraordinary Writ (talk) 07:08, 4 September 2025 (UTC)[reply]
Thank you for saying so! It can definitely feel at times like people only comment on discussion closures when they want to contest them, so it makes me happy to know when they've left a positive impression. :)
I enjoyed the chance to read the essay you linked, as well—it's a good breakdown of the types of considerations that tend to come into play. ModernDayTrilobite (talk • contribs) 13:37, 4 September 2025 (UTC)[reply]

Your Opinion is More Important than You Think

The Detective Barnstar
Thank you for your thorough research and insightful analysis on the Wahhabi war's talkpage.👍🏼TheEagle107 (talk) 22:49, 8 September 2025 (UTC)[reply]

Addition to the "List of animated television series by episode count" page.

Hello, I hope your day is going great so far.

I have a question, do you mind if you move "Earth to Luna!" up behind Winx Club, since Earth to Luna! has 8 seasons and 26 episode? I'm contacting you about this because you were the last person to edit it. I don't know If you mind doing this, you can decline if you want. This page is also semi-protected and I don't have an account with 10 edits. If you accept to do this, thanks! 74.78.27.64 (talk) 00:43, 22 September 2025 (UTC)[reply]

Sure thing! I took a look at the Earth to Luna article and your suggestion seems correct to me, so I went ahead and implemented it on List of animated television series by episode count.
For future reference, if there's an edit you want to make but you aren't able to take care of it directly, making an edit request on the article's talk page is probably the most reliable way to get the request quickly noticed by other users. ModernDayTrilobite (talk • contribs) 03:44, 22 September 2025 (UTC)[reply]
Thanks! I appreciate it, I will do that next time. 74.78.27.64 (talk) 16:39, 22 September 2025 (UTC)[reply]

Survey

Hi and thanks for your recent participation in AfD. I would like to hear your thoughts about the process. Please check this survey if you are willing to respond. FYI I found your participation via XTools.Czarking0 (talk) 02:46, 6 October 2025 (UTC)[reply]

Thank you for reaching out! My participation in AfD is pretty rare, though, so unfortunately I'm not sure I have enough experience in the area to be able to respond helpfully to the survey. ModernDayTrilobite (talk • contribs) 13:18, 6 October 2025 (UTC)[reply]

ITN recognition for D'Angelo

On 16 October 2025, In the news was updated with an item that involved the article D'Angelo, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. Ad Orientem (talk) 01:15, 16 October 2025 (UTC)[reply]

Thanks

Thanks for closing some of the RM discussions that I had recently opened. I appreciate that you tend to append detailed closing statements. –Gluonz talk contribs 18:18, 4 November 2025 (UTC)[reply]

ArbCom 2025 Elections voter message

Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. 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 2025 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:47, 18 November 2025 (UTC)[reply]

Airport destination lists sourcing RfC

Hi there,

I'm leaving this message because you contributed to the recent RfC regarding the inclusion of airport destination lists. As promised, now that that RfC has closed, I've initiated a further discussion about the sourcing standards to be applied to these lists.

If you wish to contribute to the discussion, please do so at Wikipedia:Village pump (policy)#Airport destination lists - sourcing requirements.

Cheers! Danners430 tweaks made 15:32, 19 January 2026 (UTC)[reply]