User talk:BilledMammal
Hello, BilledMammal,
I found this page interesting and I wanted to encourage you to update it every few days or maybe once a week, taking off SPI cases that have been closed. I'm not sure how much work it takes to put this together but I found it useful. Liz Read! Talk! 05:21, 4 September 2024 (UTC) Reply
- Hi Liz, I've updated it.
- I'm going to be retiring from Wikipedia soon, so won't be able to continue doing so for long, but if you are interested I can provide the code that produces the table - it's very little effort to run. Send me an email if you are. BilledMammal (talk) 09:53, 28 September 2024 (UTC) Reply
- @Liz: Is this still something that would be helpful? If so, I'm back and can resume producing it, and maybe make Platybot do it automatically. BilledMammal (talk) 01:50, 9 April 2026 (UTC) Reply
- I want to just say Hello and Thank you to Billed Mammal. If there's something you would like me to say, I would be happy to. ~2026-29416-95 (talk) 20:01, 16 May 2026 (UTC) Reply
- Hi User:~2026-29416-95, you're welcome. Can I ask what this is about? BilledMammal (talk) 04:02, 17 May 2026 (UTC) Reply
Hi BilledMammal, glad to see you're back. When Move+ makes an RM/TR request, its rationale ("per consensus at Special:Permalink/1234567890...") always gives the last permalink before the closure, which makes it difficult to just click the link and see what the result was. (See here for examples.) Would it be possible to have it instead give the permalink that includes the closure? Thanks, Extraordinary Writ (talk) 03:56, 4 April 2026 (UTC) Reply
- It's something I've been planning to fix for years now; I'll make it a priority. BilledMammal (talk) 04:01, 4 April 2026 (UTC) Reply
- @Extraordinary Writ: Done! However, this does now mean the page has to be edited twice; for example, the RM close and the addition of the old moves template . BilledMammal (talk) 01:48, 9 April 2026 (UTC) Reply
- Thanks! I guess it doesn't really matter, but you could probably still do it in one edit by using "next": for instance, Special:Diff/1346680076/next#Requested move 1 April 2026 will work even if you don't know the diff number for the closure itself. Extraordinary Writ (talk) 02:11, 9 April 2026 (UTC) Reply
- Does everyone know about the self-citing diff trick except me? According to leek, there is some issue that prevents that from working? Otherwise, would be a good solution. BilledMammal (talk) 02:27, 9 April 2026 (UTC) Reply
- Heh, great minds think alike. The issue is that it doesn't work for Special:PermaLink, but you can still make a pseudo-permalink with Special:Diff, as in the example I gave above. Extraordinary Writ (talk) 02:54, 9 April 2026 (UTC) Reply
- That makes sense. I just looked into doing that and unfortunately it won't be a quick change. At the moment, I handle moves where the page the move is taking place on is not the page listed at the top of the move template by treating the closure of the move and the addition of the "old moves" template as separate events. If I combine these into a single event again then that will require quite a bit of code to properly handle; I'll add it to the todo list, but unless the double edit really bothers some editors, or I find additional reasons to combine them into a single event, I probably won't make it a priority. BilledMammal (talk) 03:07, 9 April 2026 (UTC) Reply
- Heh, great minds think alike. The issue is that it doesn't work for Special:PermaLink, but you can still make a pseudo-permalink with Special:Diff, as in the example I gave above. Extraordinary Writ (talk) 02:54, 9 April 2026 (UTC) Reply
- Does everyone know about the self-citing diff trick except me? According to leek, there is some issue that prevents that from working? Otherwise, would be a good solution. BilledMammal (talk) 02:27, 9 April 2026 (UTC) Reply
- Thanks! I guess it doesn't really matter, but you could probably still do it in one edit by using "next": for instance, Special:Diff/1346680076/next#Requested move 1 April 2026 will work even if you don't know the diff number for the closure itself. Extraordinary Writ (talk) 02:11, 9 April 2026 (UTC) Reply
- @Extraordinary Writ: Done! However, this does now mean the page has to be edited twice; for example, the RM close and the addition of the old moves template . BilledMammal (talk) 01:48, 9 April 2026 (UTC) Reply
I thought you had the page mover perm. Can you please request it as you're obviously experienced enough. Cheers for closing those RMs. TarnishedPath talk 05:04, 4 April 2026 (UTC) Reply
- I asked for it to be revoked before leaving; I've asked for it back, but I've been told to show some more editing first. BilledMammal (talk) 05:59, 4 April 2026 (UTC) Reply
Hello, BilledMammal. Your account has been granted the "extendedmover" user right, either following a request for it or demonstrating familiarity with working with article names and moving pages. You are now able to rename pages without leaving behind a redirect and move subpages when moving the parent page(s).
Please take a moment to review Wikipedia:Page mover for more information on this user right, especially the criteria for moving pages without leaving a redirect. Please remember to follow post-move cleanup procedures and make link corrections where necessary, including broken double-redirects when suppressredirect is used. This can be done using Special:WhatLinksHere. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password. As with all user rights, be aware that if abused, or used in controversial ways without consensus, your page mover status can be revoked.
Useful links:
- Wikipedia:Requested moves
- Category:Requested moves, for article renaming requests awaiting action.
If you do not want the page mover right anymore, just let me know, and I'll remove it. Thank you, and happy editing! Toadspike [Talk] 13:40, 7 April 2026 (UTC) Reply
- Thanks! BilledMammal (talk) 00:55, 9 April 2026 (UTC) Reply
[画像:Information icon] There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Jack (talk) 20:20, 7 April 2026 (UTC) Reply
I started the ANI discussion without realising you have apparently returned, unless it was a flying visit. I'm copying the text from there so that you can see what the issue is, and we can discuss it here instead:
- At WP:CRIC, we have just been informed that a discussion has begun about an RfC called User:BilledMammal/Lugstubs3 (Olympian stubs), and that it will be followed by User:BilledMammal/Lugstubs4 (cricketer stubs). I have no objection to a discussion about whether mass-created stubs should be redirected to a team/club list. In fact, I support the idea.
- What I do object to is the way that Lugnuts is still being pilloried by BilledMammal's RfC titles. There's another one which names me, but I'm here to defend myself if I want to (I don't). Lugnuts is not here, and he should be treated with respect. Whatever Lugnuts may have done that was "wrong", he was a good writer of sports and film articles who got his facts right. What is more, when he joined Wikipedia, the emphasis was on quantity, not quality, and creation of stubs was viewed favourably, because we were creating articles that were placeholders for development. Okay, it did get out of hand, and the goalposts shifted.
- All of BilledMammal's RfC titles need to be renamed. This Lugstubs3 thing should be called something like User:BilledMammal/Olympicstubs# and the forthcoming Lugstubs4 should be User:BilledMammal/Cricketstubs#. These alternatives are descriptive of the RfC scope, which means they are both relevant and respectful. Something BilledMammal should have considered as an alternative to being vindictive.
I'll leave this here a few days. I've asked for the ANI to be put on hold. Jack (talk) 21:01, 7 April 2026 (UTC) Reply
- When I open the RfC, it will be with a title like "RfC on draftifying a subset of mass-created Olympian microstubs". I use the creators username in my userspace so that it's easier to identify what the subject is. For example, User:BilledMammal/Cricketstubs could refer to either you or Lugnuts.
- I do understand your concern that the current title may focus too much on Lugnuts, and so to partially address it I've renamed User:BilledMammal/Lugstubs3 to User:BilledMammal/Boilerplate Olympian stubs (Lugnuts).
- However, since we are discussing, I would ask you to avoid personal comments on editors including myself like "Unlike some people I could name including BilledMammal, Lugnuts was actually a good editor" and "Lugnuts, for all his alleged faults, was an infinitely better writer of articles (he did much more than stubs) than you could ever be" . I don't think this is aligned with WP:CIVIL. BilledMammal (talk) 00:28, 9 April 2026 (UTC) Reply
- Okay, thanks, that's fair enough, and I will tone down my comments.
- By the way, I'm happy for any cricket stub to be redirected if there is no short-term prospect of its expansion. Apart from rare exceptions, our biographies are about people who played in top-class matches. We have always dealt with the exceptions ourselves, via AfD. I agree that people who made a handful of appearances should be in a club/team list, but there is nothing wrong with them having a redirect too. For example, there have been numerous cases of a cricketer piece being expanded because it was discovered that they were notable in another sphere.
- I've recently built up some 18th century bios by using multiple book references. Cricket has a vast literature, more than any sport except chess, and it is always possible that a player will have coverage if we can find it, but that's the hard part. Jack (talk) 09:21, 9 April 2026 (UTC) Reply
- Thank you.
- Regarding cricket stubs, if there is any thing I can do to help let me know. I'm more conservative with your stubs than with Lugnuts, because yours tend to rely on offline sources, though I believe in many cases they are cricket almanacs? BilledMammal (talk) 02:12, 10 April 2026 (UTC) Reply
- Wisden and Playfair are annuals. Both contain a certain amount of statistics, but it's minimal compared with the narrative content. There have also been some weekly and monthly publications. Again, the vast majority of content is narrative.
- The online sources are the only questionable ones, and they should be used with caution. For example, if the article is pre-1860s, I will only refer to CricketArchive for a scorecard, and sometimes basic profile info like full name and dates of birth and death. The issue is incomplete data, because CA treats what is available as final, so anyone using one of its statistical tables is uploading false information. I regard CA as fully reliable from 1864, however. Jack (talk) 08:47, 10 April 2026 (UTC) Reply
It wasn't clear to me whether I thought ArbCom should accept the case until I started writing about it, and saw that it has two aspects of ArbCom cases. First, it requests an overview of a topic that is already a contentious topic, to see whether existing remedies are working. Many contentious topics need to be reviewed periodically. We know that Palestine and Israel is the worst, but we also had a recent review of the South Asian topic area, and before that we had a review of Azerbaijan and Armenia. Second, there has been a long-term low-level pattern of misconduct that usually stayed under the WP:ANI radar. The Maghreb case was an example of that.
As I continued writing my statement, it became more obvious that it should be a statement asking them to accept the case.
I think you should start rearranging your opening statement into the form of an evidence presentation. Robert McClenon (talk) 05:27, 17 May 2026 (UTC) Reply
- I am currently working on my evidence, but I'm not sure how best to present it. I'm currently thinking that I'll organize evidence by editor, but that will take a lot of words and result in some duplication of evidence - for example, evidence that Jimcastor communicates off-wiki with Mr Boar1 is also evidence that Mr Boar1 communicates off-wiki with Jimcastor.
- I'm assuming I'll have 1000 words, since you were a party for SchroCat and aslivering was a party for Magreb, which will help, but it's still going to be difficult to present everything I need to present. BilledMammal (talk) 05:36, 17 May 2026 (UTC) Reply
Hello, I saw that you closed the RM. I agree that it turned into a trainwreck, and I probably bear the lion share responsibility for that. As nobody actually addressed my second proposal, I think I am going to discard your advice and start a new RM for the second proposal relatively soon. Though, I am going to wait a week or until the AfD closes, whichever later, so that the craziness has passed and I have some distance from it all. Would you mind striking through the part advising to wait a few months? Page traffic is largely irrelevant and so I don't think waiting for it to settle matters, the Chengalpattu village has always been dwarfed by at minimum five-fold by the streamer, by other metrics nine- or forty-fold. I can't imagine it changing in such a way that it aids the Chengalpattu village in retaining primary topic. Perhaps in making the streamer primary topic, but the opposition to that was largely unrelated to pageviews, and I'm fine not pushing it right now. 1brianm7 (talk) 06:44, 17 May 2026 (UTC) Reply
- You're welcome to discard my advice, but I think I will keep it there as I think it will be helpful to have a few months more data. BilledMammal (talk) 05:46, 20 May 2026 (UTC) Reply
- That's fair. I'm not particularly experienced with RMs to know how the existence of a disambiguation page at (disambiguation) will affect reader traffic when it is my contention that the Chengalpattu village was frequently wrongly given to them prior to the disambiguation page's creation. I think I'm still going to do it, if only because, in the hypothetical scenario where the Chengalpattu village was disambiguated and the disambiguation page was at Vedal, I cannot imagine a RM finding the Chengalpattu village the primary topic, even when assuming that the two other villages receive 0 views/day. 1brianm7 (talk) 05:58, 20 May 2026 (UTC) Reply
All the best, Mini apolis 22:56, 17 May 2026 (UTC) Reply
You were recently listed as a party to a request for arbitration. The Arbitration Committee has accepted that request for arbitration and an arbitration case has been opened at Wikipedia:Arbitration/Requests/Case/Michael Jackson. Evidence that you wish the arbitrators to consider should be added to the evidence subpage, at Wikipedia:Arbitration/Requests/Case/Michael Jackson/Evidence. Please add your evidence by June 1, 2026 at 23:59 UTC, which is when the evidence phase closes. You can also contribute to the case workshop subpage, Wikipedia:Arbitration/Requests/Case/Michael Jackson/Workshop. For a guide to the arbitration process, see Wikipedia:Arbitration Committee/Party Guide/Introduction. For the Arbitration Committee, ~delta {talk • cont • 🇰🇷 • 🎢} 22:12, 18 May 2026 (UTC) Reply
- That's a lot of evidence of coordination .... Robert McClenon (talk) 05:56, 21 May 2026 (UTC) Reply
- I hope it's enough - Katzrockso's commons discovery will really help here, as the claim that they're not only monitoring each other's enwiki contributions but also their global contributions is difficult to believe. BilledMammal (talk) 06:02, 21 May 2026 (UTC) Reply
- Thank you for proposing Episteme Aletheia as a party. I was weighing whether to do that since I found their editing history suspicious from the get-go, but I first wanted to get confirmation that ArbCom will consider the Commons evidence. Katzrockso (talk) 06:37, 21 May 2026 (UTC) Reply
- I hope it's enough - Katzrockso's commons discovery will really help here, as the claim that they're not only monitoring each other's enwiki contributions but also their global contributions is difficult to believe. BilledMammal (talk) 06:02, 21 May 2026 (UTC) Reply
- That's a lot of evidence of coordination .... Robert McClenon (talk) 05:56, 21 May 2026 (UTC) Reply
I am contacting you because you previously voted in elections related to the Universal Code of Conduct Coordinating Committee (U4C). You may be eligible to vote in the current U4C election, which is open now and closes on 2 June 2026. You can find out more about the candidates and the election on the election page on Meta, and from there you can access the vote itself. Your participation in these elections is important to the governance of Wikimedia communities, and your time spent learning about the candidates and voting is appreciated.
-- In cooperation with the U4C, Keegan (WMF) (talk)
I originally posted this at VPWMF but it was tangential to the larger point I wanted to make. Of the little communication the board has given about candidate exclusion, one thing that has been made clear at least to me is the board members felt they had a fiduciary - and thus legal - obligation to exclude who they did. So 2 doesn't really move the needle in that regard. Best, Barkeep49 (talk) 02:39, 22 May 2026 (UTC) Reply
- I wasn't aware of that, but #2 goes further than that; affiliates are able to shortlist the list of candidates. That is something I would like to stop. BilledMammal (talk) 02:43, 22 May 2026 (UTC) Reply
- Yes. I understand that piece. It's why, despite that note, I still characterized it as the right general ideas. Best, Barkeep49 (talk) 02:46, 22 May 2026 (UTC) Reply
Hi, you recently closed the RM at 2024 Florence, Kentucky shooting with consensus to move to the proposed title, but the proposed target was 2024 Florence, Kentucky, shooting. I'm guessing either you meant to write that there wasn't consensus to include the second comma, or a typo in the move. Raskuly 🐰 17:38, 16 June 2026 (UTC) Reply
- Disagree with this point. I don't think there was consensus to add the extra comma in particular. With a few exceptions, participants generally prefer omitting it, and the majority of articles with state names in don't have the second comma, e.g. 2023 Columbus, Ohio mayoral election. — Amakuru (talk) 21:43, 16 June 2026 (UTC) Reply
- It wasn't a point, I was just confused. Raskuly 🐰 22:52, 16 June 2026 (UTC) Reply
- When assessing consensus I found a slight preference for omitting the comma, even though the original proposal included it. BilledMammal (talk) 06:51, 17 June 2026 (UTC) Reply
Hi, thank you for acting as closer in this discussion. I note that Bed Bath & Beyond Inc. should redirect to the dabpage, not Bed Bath & Beyond (1987–2023), with incoming links updated accordingly. 162 etc. (talk) 20:03, 22 June 2026 (UTC) Reply
An arbitration case, Wikipedia:Arbitration/Requests/Case/Michael Jackson, has been now closed. The final decision is available at the link above.
The following remedies have been passed regarding this case:
- TruthGuardians (talk ·contribs ), TheWikiholic (talk ·contribs ), Guitarjunkie22 (talk ·contribs ), Jimcastor (talk ·contribs ), and MraClean (talk ·contribs ) are indefinitely banned from Wikipedia. This ban may be appealed six months after the enactment of this remedy, and every six months thereafter.
- TruthGuardians (talk ·contribs ), TheWikiholic (talk ·contribs ), Israell (talk ·contribs ), EpistemeAletheia (talk ·contribs ), Guitarjunkie22 (talk ·contribs ), Jimcastor (talk ·contribs ), MrBoar1 (talk ·contribs ), MraClean (talk ·contribs ), Never17 (talk ·contribs ), and PinkSlippers (talk ·contribs ) are indefinitely topic banned from Michael Jackson, broadly construed. This restriction may be appealed six months after the enactment of this remedy, and every six months thereafter.
- NE0mAn7o! (talk ·contribs ) is warned that future misconduct in the Michael Jackson topic area will result in restrictions under the Michael Jackson community contentious topic.
For the Arbitration Committee, ~delta {talk • cont • 🇰🇷 • 🎢} 21:16, 22 June 2026 (UTC) Reply
This was long overdue. Thank you. Popcornfud (talk) 03:22, 23 June 2026 (UTC) Reply
[画像:Information icon] There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. The thread is Am I attacking the collaborative nature of the project?. -- Tamzin [cetacean needed] (they|xe|🤷) 04:45, 29 June 2026 (UTC) Reply
Hi there, thank you for closing Talk:Shaka#Requested move 26 June 2026. I agree with the outcome, however, I disagree with your summary of the arguments. Would you be willing to give it a second look and consider amending your closing statement? You stated: Editors in favor of a move argued that use is equal here, editors against a move argued that long term significance is greater.
With these arguments being equally strong, it came down to a numerical advantage. However, multiple editors, including myself, argued that the king is also the primary topic by usage. In addition to my !vote, I read Kowal2701, DrKay, and Ladtrack as referring to primary topic by usage as part of their arguments. Several editors also argued that Shaka Zulu is simply not an appropriate name for the subject or the article. The current closing summary inaccurately suggests that opposers relied solely on long-term significance and either did not address WP:PT1 or perhaps even conceded that point. —Myceteae 🍄🟫 (talk) 02:50, 20 July 2026 (UTC) Reply
- I didn't give the use argument by opposers much weight because the guideline says
the topic sought when a reader searches for that term
, and the arguments in favor of significance by use didn't address that - Google trends evidence addresses this, Google ngrams does not. BilledMammal (talk) 02:55, 20 July 2026 (UTC) Reply- Hmmm. WP:DPT says:
Usage in English-language reliable sources matters the most.
Google Ngram, Books, and Scholar are all listed under §Tools. Although the entry at WP:PT1 does not say this, the guidance at DPT and Tools follows directly and these are all under §Is there a primary topic?. In practice at RM, a common interpretation ofusage
is that this refers to high quality reliable sources of the sort that we use for other article content decisions. Such usage arguments are common and are usually accepted at RM. —Myceteae 🍄🟫 (talk) 03:15, 20 July 2026 (UTC) Reply- I don't consider those to override the plain language of the guideline which refers to use by readers, not by writers. If you want to use a broader definition I suggest proposing it on the talk page. BilledMammal (talk) 03:21, 20 July 2026 (UTC) Reply
- I don't intend to follow up on this any further. Thanks for explaining your thinking and engaging with my inquiry. —Myceteae 🍄🟫 (talk) 03:55, 20 July 2026 (UTC) Reply
- I don't consider those to override the plain language of the guideline which refers to use by readers, not by writers. If you want to use a broader definition I suggest proposing it on the talk page. BilledMammal (talk) 03:21, 20 July 2026 (UTC) Reply
- Hmmm. WP:DPT says:
You closed this discussion as "no consensus", but you wrote: While editors in support of a move were more numerous, the arguments of editors opposed to a move were more aligned with policy
. Okay, cool, but how? Raskuly 🐰 03:26, 20 July 2026 (UTC) Reply
- Largely per the arguments of Pascuet and Station1. BilledMammal (talk) 04:26, 20 July 2026 (UTC) Reply
- Per recent consensus, there is no need for there to be multiple incidents of the same nature at the same location for a year to be included. Pascuet wrote that WP:NOYEAR doesn't mandate a year in every title, which is obviously true, but they failed to argue why this one did not need a year other than writing
prepending one here could falsely imply other shootings occurred at this location in other years
which it does not and completely goes against consensus. Regarding WP:OVERPRECISION, WP:NCEVENTS has its own naming guidelines, and the OVERPRECISION explicitly says:Exceptions to the precision criterion may sometimes result from the application of some other naming criteria
. Regarding CONCISE, I only see that being used to completely wave away the application of NCWWW. Raskuly 🐰 04:36, 20 July 2026 (UTC) Reply- There doesn't need to be multiple events, but the numerical support was not sufficiently great to overcome the guideline-based opposition. I don't see the discussion you link as relevant; if you want to use a year disambiguator more widely, I suggest opening an RFC proposing that there should be an expectation of using the year. BilledMammal (talk) 04:39, 20 July 2026 (UTC) Reply
- I completely fail to see why or how the support is not based on naming guidelines. WP:NCWWW also states that in the majority of cases, the article title for events should say when, where, and what–so I don't see any need for it. If a majority of event articles need the when, why was there no guideline based argument about how this met NOYEAR? It can't be a requirement to have multiple events as you've written yourself. Raskuly 🐰 04:45, 20 July 2026 (UTC) Reply
- There isn't a requirement to have multiple events, but having multiple events addresses WP:CONCISE and WP:OVERPRECISE, and without multiple events there is a greater bar to be met to use the disambiguated title. As written, WP:NCWWW leaves a lot of room for the application of other guidelines and policies - if you want NCWWW to be more binding, then you need to open an RFC proposing that. BilledMammal (talk) 04:53, 20 July 2026 (UTC) Reply
- Yes, clearly we need to get back to working out a clarification for that NC, but to be fair that previous RfC was very much about this and established that event titles using years are not disambiguated, the year is just a part of the descriptive title. I understand Raskuly's confusion considering other RMs with almost or completely identical arguments as this one (Station1 posts the exact same templated comment in every RM to add a year per WP:NCWWW because they disagree with the previous RfC consensus) have been closed with the closer evaluating the CONCISE and OVERPRECISE arguments as being weak because they ignore NCWWW and the RfC consensus. –Maltazarian ᚾparley {\displaystyle \lor }investigateᛅ 11:08, 20 July 2026 (UTC) Reply
- I did not realize an RfC had been started when I posted this. Whoops. –Maltazarian ᚾparley {\displaystyle \lor }investigateᛅ 11:13, 20 July 2026 (UTC) Reply
- @Maltazarian and Raskuly: That RfC is a little confusing to me, and I'm not convinced it will resolve the issues - maybe some workshopping first? BilledMammal (talk) 02:22, 22 July 2026 (UTC) Reply
- Yeah we did have a workshop open for weeks that editors subscribed to NCEVENT could see. Comments that had objections were pretty much exclusively focused on the substance of the previous RfC's consensus, which is beyond the scope as we merely want to clarify what that existing consensus is rather than alter it. There wasn't any alternative suggestions for how to do that, and so the RfC ended up the way it currently is. –Maltazarian ᚾparley {\displaystyle \lor }investigateᛅ 03:19, 22 July 2026 (UTC) Reply
- @Maltazarian and Raskuly: That RfC is a little confusing to me, and I'm not convinced it will resolve the issues - maybe some workshopping first? BilledMammal (talk) 02:22, 22 July 2026 (UTC) Reply
- I did not realize an RfC had been started when I posted this. Whoops. –Maltazarian ᚾparley {\displaystyle \lor }investigateᛅ 11:13, 20 July 2026 (UTC) Reply
- Yes, clearly we need to get back to working out a clarification for that NC, but to be fair that previous RfC was very much about this and established that event titles using years are not disambiguated, the year is just a part of the descriptive title. I understand Raskuly's confusion considering other RMs with almost or completely identical arguments as this one (Station1 posts the exact same templated comment in every RM to add a year per WP:NCWWW because they disagree with the previous RfC consensus) have been closed with the closer evaluating the CONCISE and OVERPRECISE arguments as being weak because they ignore NCWWW and the RfC consensus. –Maltazarian ᚾparley {\displaystyle \lor }investigateᛅ 11:08, 20 July 2026 (UTC) Reply
- There isn't a requirement to have multiple events, but having multiple events addresses WP:CONCISE and WP:OVERPRECISE, and without multiple events there is a greater bar to be met to use the disambiguated title. As written, WP:NCWWW leaves a lot of room for the application of other guidelines and policies - if you want NCWWW to be more binding, then you need to open an RFC proposing that. BilledMammal (talk) 04:53, 20 July 2026 (UTC) Reply
- I completely fail to see why or how the support is not based on naming guidelines. WP:NCWWW also states that in the majority of cases, the article title for events should say when, where, and what–so I don't see any need for it. If a majority of event articles need the when, why was there no guideline based argument about how this met NOYEAR? It can't be a requirement to have multiple events as you've written yourself. Raskuly 🐰 04:45, 20 July 2026 (UTC) Reply
- There doesn't need to be multiple events, but the numerical support was not sufficiently great to overcome the guideline-based opposition. I don't see the discussion you link as relevant; if you want to use a year disambiguator more widely, I suggest opening an RFC proposing that there should be an expectation of using the year. BilledMammal (talk) 04:39, 20 July 2026 (UTC) Reply
- Per recent consensus, there is no need for there to be multiple incidents of the same nature at the same location for a year to be included. Pascuet wrote that WP:NOYEAR doesn't mandate a year in every title, which is obviously true, but they failed to argue why this one did not need a year other than writing
You recently offered a statement in a request for arbitration. The Arbitration Committee has accepted that request for arbitration and an arbitration case has been opened at Wikipedia:Arbitration/Requests/Case/Gun control 2. Evidence that you wish the arbitrators to consider should be added to the evidence subpage, at Wikipedia:Arbitration/Requests/Case/Gun control 2/Evidence; private evidence may be sent to arbcom-en-b[画像:@]wikimedia.org. Additional parties may be proposed during the first week of the evidence phase. Please add your evidence by August 15, 2026 at 23:59 UTC, which is when the evidence phase closes. You can also contribute to the case workshop subpage, Wikipedia:Arbitration/Requests/Case/Gun control 2/Workshop. For a guide to the arbitration process, see Wikipedia:Arbitration Committee/Party guide/Introduction. For the Arbitration Committee, GoldRomean (talk) 18:11, 1 August 2026 (UTC) Reply