Wikipedia:Village pump (proposals)#Authority Control Integration

{{redirect|WP:PROPOSE|proposing article deletion|Wikipedia:Proposed deletion|and|Wikipedia:Deletion requests}}{{short description|Discussion page for new proposals}}{{Village pump page header|Proposals|alpha=yes|

The proposals section of the village pump is used to offer specific changes for discussion. Before submitting:

Discussions are automatically archived after remaining inactive for nine days.|WP:VPR|WP:VP/PR|WP:VPPRO|WP:PROPS}}__NEWSECTIONLINK__

{{centralized discussion|compact=yes}}

__TOC__

{{anchor|below_toc}}

Category:Wikipedia village pump

{{PAGENAME}}

Category:Pages automatically checked for incorrect links

{{User:MiszaBot/config

| algo = old(12d)

| archive = Wikipedia:Village pump (proposals)/Archive %(counter)d

| counter = 217

| maxarchivesize = 300K

| archiveheader = {{Wikipedia:Village pump/Archive header}}

| minthreadstoarchive = 1

| minthreadsleft = 5

}}

{{clear}}

mass-creation of china township articles

hello i want to mass-create china township articles i have this brilliant python codelink redacted — Tamzin that i spent weeks creating that mass-creates the pages and then posts them like bam bam bam and it cites citypopulation.de which is a good source for its population and demographics and exact coordinates and area and even its chinese/pinyin text. its very robust and if there's a single bit with an error or if the formatting doesn't add up its like "nope" and skips onto the next article so it never posts buggy stuff and i could red-to-blue like 90% of the china township articles with it in all provinces. i already generated 90% of a-g hebei townships (until someone threatened me) like this one this one and this one and this one and even ethnic townships with no mistakes they're all 100% perfect can i do it thankyou. i can also reprogram it so that submits them all to the draftspace for review if you dont trust theyll be up to standard for publication. Mayeva8823 (talk) 12:42, 9 April 2025 (UTC)

:and yes ill be around to look at them and make sure theyre ok before theyre published i wont just leave the script on while im at college or something Mayeva8823 (talk) 12:46, 9 April 2025 (UTC)

:Never heard of citypopulation.de but I can see it's popular around here:[https://en.wikipedia.org/w/index.php?search=%22citypopulation.de%22&title=Special%3ASearch&ns0=1] Gråbergs Gråa Sång (talk) 14:44, 9 April 2025 (UTC)

::It may be popular, but is it reliable? From a quick look it seems to be the work of one person. Phil Bridger (talk) 14:58, 9 April 2025 (UTC)

:::Some hits at RSN [https://en.wikipedia.org/wiki/Special:Search?fulltext=Search+the+noticeboard+archives&fulltext=Search&prefix=Wikipedia%3AReliable+sources%2FNoticeboard&search=%22citypopulation.de%22&ns0=1], including Wikipedia:Reliable_sources/Noticeboard/Archive_339#citypopulation.de. Gråbergs Gråa Sång (talk) 15:03, 9 April 2025 (UTC)

::::Not reliable. Some of the UK tien and cities quote census results but they don't match. Davidstewartharvey (talk) 16:29, 9 April 2025 (UTC)

:Absolutely opposed. Mass geostub creation has wasted more cleanup time around here than almost anything else. How are you going to demonstrate that these are real settlements which really are at the locations given, and really have the names supplied? If you are willing to go over the output of this script and check it, one by one, then I might reconsider. But given that someone else is going to have to do just that, I have to object. We have spent several years cleaning up the US mass creation spree, and we're nowhere near finished. China is surely a much larger project, and verification is surely going to be more difficult considering the PRC's location falsification. Also, haven't we already agreed we aren't going to do this anymore? Mangoe (talk) 16:02, 9 April 2025 (UTC)

::Total agreement! Mass creation should be banned. Davidstewartharvey (talk) 16:30, 9 April 2025 (UTC)

:::Yes, we had bad experiences with GNIS, but that doesn't mean that every country has equivalently bad databases. Phil Bridger (talk) 19:17, 9 April 2025 (UTC)

::::I also think we should keep in mind the systemic bias aspect. A stub is better than nothing, and often for non-Western countries, the choice is between having a mass-generated stub or having nothing. I'm not saying this alone is sufficient reason to let OP go forward, but it leaves a sour taste in my mouth for us to say that we were willing to permit and then spend the effort to clean up mass stub creation for U.S. municipalities but that we're not willing to do likewise for China. Sdkbtalk 19:29, 9 April 2025 (UTC)

:::::An inaccurate or completely false stub is worse than nothing, and we've had too many problems to assume that any source is reliable enough. And I'm sorry, but even where the databases are relatively good, we still have to interpret them properly. I don't think it is unreasonable to expect some degree of human verification on everything we publish, and for geography that means checking to see that it's really there. The choice is never between having a mass-generated stub or nothing, and our experience here is that database dumps for third-world countries have been particularly bad precisely because of the poor quality of information about them. Mangoe (talk) 19:58, 9 April 2025 (UTC)

::::::Looking at what this now blocked editor has added today, he has just added stubs based upon an unreliable website which reportedly use census data, which probably do not meet WP:GEOLAND. Davidstewartharvey (talk) 20:33, 9 April 2025 (UTC)

:What do you mean by "threat"? The closest I can find is {{slink|User talk:Mayeva8823#Rapid recreation of many articles}}, and {{u|Chaotic Enby}} was not threatening you there. jlwoodwa (talk) 16:41, 9 April 2025 (UTC)

If a bot could be coded to be consistent and accurate with decent facts using PRC sites it would actually be beneficial long term and reduce inconsistencies. We do need the articles on township divisions. But it needs to be done right and ideally a start class article or meaty stub. I would allow this editor to generate an example and we can survey it. But use direct government sources, not that website. If all you add is a population figure and create short stubs I oppose. They've got to be informative and accurate if using a bot.♦ Dr. Blofeld 19:44, 9 April 2025 (UTC)

Since I got a question on my talk assuming otherwise, just to clarify, I've blocked Mayeva for account security reasons ancillary to this thread, but this is not a for-cause block related to their editing. -- Tamzin[cetacean needed] (they|xe|🤷) 20:18, 9 April 2025 (UTC)

: Not advocating for or against, but one might look into Qbugbot, which created about 20k insect articles, and Lsjbot, which has created ~3M articles in Swedish, Dutch, Cebuano, and Waray Wikipedias.

: Mathglot (talk) 05:50, 10 April 2025 (UTC)

::I think the Swedes decided to stop Lsjbot because problems. Gråbergs Gråa Sång (talk) 06:01, 10 April 2025 (UTC)

::I think it's terrible what has happened to Cebuano and Swedish Wikipedia, so many bot generated articles renders them soulless. But for missing places where there is generic data I think long term it works out better if started consistently with a bot. Spanish municipalities are a mess and some still without infoboxes, basic data and maps. They should have been generated consistently back in like 2006. Somebody competent with coding bots should sort out China.♦ Dr. Blofeld 09:57, 10 April 2025 (UTC)

:::I don't know about China in particular, but we've had issues with setting bots to work using official census data that turned out to include a lot of statistics tied to census dropoff locations that are not standalone places. In particular, this was a problem for Iran and Russia, with the former listing gas stations and convenience stores as census locations, and the latter assigning arbitrary geolocations in rural areas where there are no distinct populated settlements. I would be very hesitant to do any automated locality-article creation unless the datasets have first been vetted by editors fluent in the language and familiar with the country in question, and at that point the benefits of automation in terms of time saved would likely be marginal. signed, Rosguill talk 15:57, 12 April 2025 (UTC)

::::Lsjbot is possibly the worst thing that ever happened to Wikipedia. Because of it we have about 10 million out-of-date, rotting stubs that are full of bogus information from low-quality self-published databases and will never be updated or maintained. Even worse, the 10 million junk articles have polluted Wikidata and other projects due to efforts to synchronize content (e.g. Joopwikibot on Vietnamese Wikipedia). So now in Wikidata we have entries for places and taxa that never actually existed but are impossible to remove since they have articles in 3 or 4 different wikis (two of which are ghost towns), all created by Lsjbot. Please don't let this happen again. Nosferattus (talk) 18:26, 13 April 2025 (UTC)

:::::Agreed that Swedish wiki bot articles are hideous and that there are potential problems. The Demographics bloat in US place articles are also hideous due to the generic bot generation and 2010 and 2020 updates. But with a country like China, articles run the risk of being a mess and inconsistent without at least some sort of organized manual approach. Any thoughts {{u|Markussep}} ? For me I want to see consistency with data and infoboxes, but loathe seeing hundreds of articles in categories which all read the same. It makes us look soulless and like a database. ♦ Dr. Blofeld 18:43, 13 April 2025 (UTC)

: I think this would work if the articles were created in a liminal space such as draftspace, project space, or userspace, and then promoted to mainspace upon some minimal review. BD2412 T 18:55, 13 April 2025 (UTC)

::Yup, just said the same thing. Ideally a bot which can mass generate basic entries with consistent data in the WikiProject space and then an editor or two gradually manually working through them writing unique content for each and gradually creating in the mainspace would be better. At the very worst, meaty stubs which are consistently formatted and sourced with government data and sites and which are individually written on top of the raw data, no generic soulless articles allowed.♦ Dr. Blofeld 18:59, 13 April 2025 (UTC)

:::For the interested, [https://www.abc.net.au/news/science/2025-04-15/wikipedia-cebuano-lsjbot-ai-article-generation-non-english/105123090 Wikipedia's largest non-English version was created by a bot. Generative AI poses new problems]. Gråbergs Gråa Sång (talk) 10:46, 19 April 2025 (UTC)

a few standards

I have a system I would like to suggest. How about picking a few of the simplest and most frequently used templates or luas and designating them as something like "Standard Lua" or "Standard Templates"? These templates or luas would use the same scripts and syntax in all language versions and sister projects. Whatback11 (talk) 15:01, 12 April 2025 (UTC)

:I've left a note at Wikipedia:Village pump (technical) about this discussion as folks there are likely to be interested/knowledgeable. 15:08, 12 April 2025 (UTC) — Preceding unsigned comment added by Thryduulf (talkcontribs)

:That could be interesting (I'm thinking of templates connected to a Wikidata item), but the issue is that it might require a lot of standardization as each project might have its technical ecosystem already adapted to specific variants of these templates. In my opinion, the benefits of intercompatibility outweigh the cost of changing the syntax of frequently-used templates on many projects.{{pb}}One point where this has already been done is citation templates, where foreign-language parameters are often interpreted correctly when copy-pasted from one language version to another. However, these are implemented as aliases for similar parameters, and don't imply that all the versions of the citation templates must function the same way "under the hood". Chaotic Enby (talk · contribs) 16:21, 12 April 2025 (UTC)

:phab:T121470 is an old request. There are other connections there that you can look at. Izno (talk) 16:37, 12 April 2025 (UTC)

:This is being implemented as [https://www.wikifunctions.org WikiFunctions] {{tq|In the future: It will be possible to call Wikifunctions functions from other Wikimedia projects and integrate their results into the output of the page.}}, which has... an interesting approach to things. The wiki-functions are already available on the Dagbani wiki. Aaron Liu (talk) 18:10, 13 April 2025 (UTC)

Space tourists: "crew" or "passengers"

Our spaceflight articles seem to continue to call the paying passengers without duties on recent spaceflights "crew", despite the fact that this doesn't match the normal meaning of the word. While this glorifying of what these actually do (spend 1 minute in actual space, have no duties at all on board), is uncritically repeated by too many news reports, I don't think Wikipedia should contribute to such incorrect promotalk. We clearly use the distinction in every other type of article (e.g. for airline crashes, we list "crew" and "passengers" separately), and no one would dream of calling themselves crew simply for boarding a plane or train. Can we please bring back some accuracy to our spaceflight articles as well? Fram (talk) 16:48, 14 April 2025 (UTC)

  • Personally I agree, but what matters is what terminology sources use and how. It's possible that "crew" in reference to a spaceflight means "anyone on board a spacecraft" while with aircraft it means "those tasked with operating the aircraft". 331dot (talk) 16:57, 14 April 2025 (UTC)
  • We could use quotes around crew, as did you. O3000, Ret. (talk) 17:05, 14 April 2025 (UTC)
  • :WP:SCAREQUOTES might be a reason not to. Sdkbtalk 17:45, 14 April 2025 (UTC)
  • ::I don't think that applies in a case where the word is used metaphorically. We're not making an accusation. O3000, Ret. (talk) 17:53, 14 April 2025 (UTC)
  • I agree with Fram (which doesn't happen often!). Six people who take a boat on a pleasure cruise are no "crew" and nor are these people. In the same way that we don't uncritically repeat other neologisms from press releases, we shouldn't stretch the plain-English definition of a term here and there's nothing in policy that binds us to the exact wording used by the sources. HJ Mitchell | Penny for your thoughts? 17:28, 14 April 2025 (UTC)
  • I'm inclined to agree here, but I would like to know a little more about how much safety training etc. is involved for paying voyagers on spacecraft. Another way to look at the promotionalism concern is that these companies may want to minimize how much preparation is required to make the flights seem more routine than they actually are yet. Sdkbtalk 17:49, 14 April 2025 (UTC)

:Might be worth using the NASA definition Mrfoogles (talk) 19:22, 14 April 2025 (UTC)

::{{tq2|Crew. Any human on board the space system during the mission that has been trained to monitor, operate, and control parts of, or the whole space system; same as flight crew.}}

::{{tq2|Passenger. Any human on board the space system while in flight that has no responsibility to perform any mission task for that system. Often referred to as "Space Flight Participant."|source=[https://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_8705_002C_&page_name=AppendixA NASA Procedural Requirements 8705.2C, Appendix A: Definitions]}}

::I don't know if those are the right NASA definitions, but using NASA definitions or other scientific/academic expert definitions, rather than promotional media spin, seems to be the better choice for wikivoice. Levivich (talk) 20:03, 14 April 2025 (UTC)

:Have you got an example as to when this comes up? Can we not just say that eight people were "on-board" rather than give them a job. Lee Vilenski (talkcontribs) 20:07, 14 April 2025 (UTC)

::Every article about a human spaceflight names the participants, currently called the "crew". Having passengers not involved in the operation of the craft is a relatively recent development. 331dot (talk) 20:11, 14 April 2025 (UTC)

:First let me say that I know everyone working on these articles has been doing so with good intent and every effort at NPOV, it's just that language evolves very quickly sometimes and there may not be good models on how to write about very recent innovations, and thus Fram has identified a received weakness in existing published matter on this topic.

:In any case: If you pay for a ride you are a passenger; if you get paid for going on a ride, you are crew.

:I personally think we should use Fram's first phrase in his subhed and just should call them space tourists. Why? Because they're not even passengers on a journey to a destination in the sense that the spaceship is going from a port on Earth to a port on the Moon. They're going on a canned tourist cruise to see whales in the bay or look at that famous rock formation or view the reef by glass-bottom boat, and then return from whence they began. Similarly, people who pay for passage on submersible trips to shipwrecks should be referred to as deep-sea tourists.

:FWIW, there is already sitcom-theme-song canon law on this issue:

:The mate was a mighty sailing man,

:The skipper brave and sure.

:Five passengers set sail that day

:For a three hour tour, a three hour tour.

:So yeah I vote passengers over crew (although I would personally prefer tourists over both although I'm simultaneously concerned it has a slightly disparaging connotation).

:jengod (talk) 20:50, 14 April 2025 (UTC)

::You mean Tina Louise and Jim Backus weren't crew members? O3000, Ret. (talk) 21:15, 14 April 2025 (UTC)

:::For those three hours, they were just passengers. But then the weather started getting rough... oknazevad (talk) 18:04, 15 April 2025 (UTC)

::We call Dennis Tito a "space tourist", Donald Albury 22:59, 14 April 2025 (UTC)

:::Did I mention that I'm an official part of the crew of planet Earth? O3000, Ret. (talk) 23:01, 14 April 2025 (UTC)

:::Tito was a space tourist, who was a member of the 3-Man SM-24 mission crew*, people can be multiple things at the same time. (According to NASA [https://nssdc.gsfc.nasa.gov/nmc/spacecraft/display.action?id=2001-017A NASA - NSSDCA - Spacecraft - Details] JeffUK 17:25, 15 April 2025 (UTC)

::You still call people on boats passengers though even if the route is a circular sightseeing one. Same goes for other forms of transport, cf. Mount Erebus disaster. In this case I think passengers is the best term  novov talk edits 00:52, 15 April 2025 (UTC)

:Wait, does this mean that the flight was "uncrewed"? We have been using that term for robotic missions. Hawkeye7 (discuss) 01:04, 15 April 2025 (UTC)

::We could say the Blue Origin flight earlier today was "unmanned". (Duck and run.) Donald Albury 01:23, 15 April 2025 (UTC)

:I would just urge some caution here. I wouldn’t count the passengers of the New Glenn flight as crew. It’s a fully-automated capsule on a suborbital flight. They get basic training on “safety systems, zero-g protocols, and execute mission simulations”. They’re tourists/passengers.

:However, the occupants of the recent Fram2 mission trained for months and while the Dragon is highly automated, it’s not fully automated. They still had a lot to learn. They’re definitely a crew.

:The problem with the term spaceflight participant is that the Russians define pretty much everyone who’s paying them for a ride as a spaceflight participant… including those who undergo extensive professional training and for whom conducting scientific research is the primary reason for their spaceflight. RickyCourtney (talk) 07:03, 15 April 2025 (UTC)

:They are as much made crew by the safety briefing as my going to muster drill on a cruise ship makes me a member of its crew. If they are a) not paid for their services aboard ship and b) take no real part in controlling the craft or operating onboard equipment, I don't see them as crew. That being said, there is always going to be a gray zone.Wehwalt (talk) 13:10, 15 April 2025 (UTC)

{{block indent|em=1.6|1=Notified: Wikipedia talk:WikiProject Spaceflight. Sdkbtalk 17:50, 14 April 2025 (UTC)}}

I dropped a note about this discussion at Talk:Blue Origin NS-31#"Crew" or "passengers", which has so far fewer participants but a quite different point of view... Fram (talk) 13:25, 15 April 2025 (UTC)

:Crew is clearly the common term. NASA refer to the 'participants' on a missions who's only purpose was tourism as 'crew' here [https://www.esa.int/ESA_Multimedia/Images/2007/06/Soyuz_TM-34_crew_with_l-r_Yuri_Gidzenko_Roberto_Vittori_and_Mark_Shuttleworth The Soyuz MS-20 and Expedition 66 crews - NASA]

:The [https://www.esa.int/ESA_Multimedia/Images/2007/06/Soyuz_TM-34_crew_with_l-r_Yuri_Gidzenko_Roberto_Vittori_and_Mark_Shuttleworth European Space Agency] refer to the 'tourists' amongst the crew here too.

:'Crew' is clearly just 'the people on board' when talking about spaceflight. Maybe that will shift if the distinction between 'crew' and 'passengers' continues but it hasn't yet. The recent 'all-female crew' aboard the latest Blue Origins flight are referred to in all reliable sources as 'A crew', as are the crew-members of all previous blue origins flights. JeffUK 17:11, 15 April 2025 (UTC)

I am going to drop out of this convo now bc I realized I might reinforcing or enabling misogynist presumptions that "if a bunch of women can do it must not be hard work." And that's absolutely on me because I have long-standing bitter POV feelings about Lauren Sanchez dating to So You Think You Can Dance. ANYWAY, my take is that the bifurcation is very clear and has been so since humans first started offering to ferry other humans across the river on janky rafts:

If you pay for a ride, you're a passenger. If you get paid to give a ride, you're crew. Participation in tasks onboard is not the determinant.

If we have reliable sources stating that someone paid money or items of equivalent value (publicity valued at X?) to go on a space trip or were sponsored to go on a space trip, they are passengers (and space tourists).

If we have reliable sources stating that someone is getting paid money by any space agency or rocketship-owning private company to go on a space trip, they are crew.

If we have no reliable sources about the financial/funding arrangements that determined which people are getting onboard a rocket ship, it seems fine to fall back on the default and current practice of using crew. But also don't let marketing practices and publicity stunts fool you.

This debate is a legacy of the Space Age when all space flight was quasi-military, government-sponsored, and "exploration." The transition to commercial space flight and private exploitation of extra-atmospheric travel is obviously well underway and will require a transition in perspective, including perhaps additional skepticism about motive.

Good luck on your debate and I hope you all have a wonderful April!!

jengod (talk) 17:57, 15 April 2025 (UTC)

:Space tourists are barely one step up from luggage and are not crew, are not astronauts, are not exceptional except perhaps in the size of their bank accounts. Simonm223 (talk) 20:13, 15 April 2025 (UTC)

::Some might qualify as “experiments”… so “equipment”. :) Blueboar (talk) 20:17, 15 April 2025 (UTC)

::Participation in tasks onboard is absolutely a determinant.

::I’d argue that if you have an active role in the operation of the craft, you’re part of the crew… even if you’re paying for the privilege.

::If you’re paying to be there and you’re just along for the ride without any active operational duties (and knowing what to do in an emergency doesn’t count)… you’re a passenger. RickyCourtney (talk) 00:21, 16 April 2025 (UTC)

:::As Jengod says, choosing the moment that Blue Origin first send an all-female contingent into space to start referring to them as 'equipment' does not pass the smell test. All the relevant articles make it very clear that they are paid participants, and describes them as 'tourists' so I really don't see a reason to rush to change this immediately. JeffUK 08:58, 22 April 2025 (UTC)

:We don't need specific rules for this, we should follow what the reliable sources say, regardless of what we think about what they say as we do in other situations. If reliable sources disagree, either just go with the majority or note and/or explain the disagreement as we usually do. Thryduulf (talk) 09:46, 16 April 2025 (UTC)

  • We should follow what reliable sources say, but perhaps we do need clarifying guidance that this doesn't mean we have to or should follow the particular wording they use. That's mimicry, not neutral point of view. It's not so unusual for otherwise reliable sources to use terminology in an incorrect or misleading way, especially in niche topics. This is a good example of that. If reliable sources say that a person did something that meets the commonly understood definition of a 'passenger', then we can and should call them a 'passenger', even if the source itself (for whatever reason) uses the word 'crew'. – Joe (talk) 10:15, 16 April 2025 (UTC)
  • :I think what we do already is a perfect balance between those. We refer to the people on board as 'Crew' in aggregate, then describe the role of each crew member (Tourist, Space Participant, Payload Specialist) etc. JeffUK 08:52, 18 April 2025 (UTC)
  • ::The word crew implies assigned duties. A passenger has no assigned duty. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:57, 18 April 2025 (UTC)
  • :::Some airline passengers are given assigned duties. Hawkeye7 (discuss) 09:50, 22 April 2025 (UTC)
  • ::That sounds rather odd to me. Passengers on a ship, train, etc. aren't usually described as crew members or part of the crew in aggregate. – Joe (talk) 09:23, 22 April 2025 (UTC)

: As a matter of convenience it can be useful to describe the humans on board a 'crewed spacecraft' as the crew of that spacecraft. We just don't have readily available terms like 'passenger spacecraft' or 'human-occupied spacecraft' in common use. (— 𝐬𝐝𝐒𝐝𝐬 — - talk) 03:03, 17 April 2025 (UTC)

:: How about 'autonomous spacecraft' or 'pilot-less spacecraft'? -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:57, 18 April 2025 (UTC)

:::We already have autonomous spacecraft. Also known as uncrewed spacecraft or robotic spacecraft. CambridgeBayWeather (solidly non-human), Uqaqtuq (talk), Huliva 00:30, 24 April 2025 (UTC)

  • I support the principle of using "crew" for people who operate the spacecraft, and "passenger" for those who have paid for the privilege of going into or near space, or had it gifted to them, and who do not operate the spacecraft. BastunĖġáḍβáś₮ŭŃ! 10:43, 24 April 2025 (UTC)
  • :On commercial flights, stewards are considered crew but do not operate the aircraft. Similarly, on military aircraft there are important crew members who do not operate the aircraft. Isn't the situation with spacecraft analogous? There are people who operate the spacecraft, there are mission-critical people who do not operate the spacecraft, whom I would consider crew. I would use passenger for those who do not have any assigned support role. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:53, 24 April 2025 (UTC)

RfC: Date-fixing bots

{{User:ClueBot III/DoNotArchiveUntil|1748055670}}

{{rfc|style|rfcid=E30D20D}}

I would like to formally understand what the community would think of a date-fixing bot. Such a bot would fix dates in articles to conform either {{tlx|Use dmy dates}} or {{tlx|Use mdy dates}}. To be clear, this bot would not revert any good faith changes that add content and dates of the wrong format; instead, it will just change the date format. In my opinion, there are a few different ways such a bot could be implemented (or not):

  • Option 1: no bot, everything stays as is
  • Option 2a: a supervised bot (so every edit is manually reviewed before publication) that would have to pass BRFA to be implemented. I think this would alleviate any concerns of the bot creating errors based on context (such as changing date formats in quotes, links, references, etc.)
  • Option 2b: an automatic bot that does something similar in proposal 2a, but wouldn't actually have its edits be checked before implementation
  • Option 3: some other solution; no guarantee that this is actually feasible

Thanks for your consideration – PharyngealImplosive7 (talk) 02:35, 19 April 2025 (UTC)

:I'm an extensive user of a script that automates date style fixes. My experience has been that it's crucial to spend time reviewing the edits both to fix errors and to ensure that I am not making a purely cosmetic edit (e.g. by only changing dates in citations which are automatically rendered in the preferred style identified by a "Use XXX dates" tag). I have some doubts that it would be possible to create a date-fixing bot that wouldn't have the same issues, so I I would be unlikely to support 2b. That said, I'm happy to hear from those with more techincal capability.

:On a procedural note, is the goal here just to see if this effort is supported by the community? Any bot created would still need to go through BRFA, right? Firefangledfeathers (talk / contribs) 02:41, 19 April 2025 (UTC)

::Yes, the goal here is to see whether the community supports the creation of such a bot. A BRFA would still be necessary to ensure the technical competence of any bot. – PharyngealImplosive7 (talk) 03:18, 19 April 2025 (UTC)

  • Option 1: no bot, everything stays as is. Experience indicates that bot edits that are supposed to be manually reviewed don't actually get reviewed. Just look at the never-ending complaints at User talk:Citation bot. --Jc3s5h (talk) 02:44, 19 April 2025 (UTC)
  • Strong oppose option 2b. There are many examples of contexts where dates should never be altered, articles about/discussing different date formats, including but not limited to direct quotations, version numbers, timestamps, and things that look like dates but aren't. Many, probably the vast majority, of these will not be able to be correctly identified by bot. If something supervised is desirable (and I am presently unconvinced it is) then adding to something like AWB would seem a more useful and safe option. Thryduulf (talk) 03:32, 19 April 2025 (UTC)
  • It's difficult to evaluate this in the abstract. I could theoretically be persuaded to support 2a or even 2b if the error rate is shown to be low enough, but we can't know the error rate until implementation gets farther along. If fixing dates to conform with an article's tag doesn't turn out to be feasible, I think there might be potential in having a bot assist with identifying articles to tag with formats based on their categories. Such a bot would have to be tuned to handle exceptions, but I think it could be tailored to an uncontroversial set that'd still be quite large. Sdkbtalk 04:30, 19 April 2025 (UTC)
  • :I guess you raise a chicken-and-egg type problem: you want to see the error rate, but to start a bot trial we need consensus first. – PharyngealImplosive7 (talk) 06:42, 19 April 2025 (UTC)
  • ::A supervised bot working on a limited sample of pages, with human review, could be a good way to evaluate whether such a bot can actually be fit. Chaotic Enby (talk · contribs) 10:59, 19 April 2025 (UTC)
  • Option 1, because option 3 has already happened. The dmy and mdy templates already transform citation display. CMD (talk) 05:00, 19 April 2025 (UTC)
  • BAG note... 2B is a non-starter per WP:BOTPOL. All bots have to go through BRFA, and a bot like this would definitely need testing and review. Headbomb {t · c · p · b} 07:21, 19 April 2025 (UTC)
  • This RFC is probably for Wikipedia:Bots/Requests for approval/PharyngealBOT, which is currently on hold pending a consensus discussion like this one. Anomie 11:34, 19 April 2025 (UTC)
  • Option 1 no bot. This proposal assumes that all {{tl|Use dmy dates}} and {{tl|Use mdy dates}} tags are correct and should be enforced throughout the article. It ain't so. Yesterday I spent too long checking and reverting a new editor's mass additions of these tags, almost all contrary to MOS:DATERET and/or MOS:DATETIES, seemingly made without having read Template:Use mdy dates/doc or Template:Use dmy dates/doc, and otherwise inappropriate. A bot of this sort would have made that a considerably more tedious task.{{pb}}Dates within quotations should never be changed. The technical difficulty of doing this, catching quotes between quotation marks as well as in {{tl|blockquote}}, has defeated other autoformatting attempts and I see no suggestion here that a solution has been found. NebY (talk) 09:11, 19 April 2025 (UTC)
  • :Would your concern be somewhat alleviated if the bot checked that the "use xxx dates" template was on the article at least 6 months prior to the revision it checks? – PharyngealImplosive7 (talk) 19:15, 19 April 2025 (UTC)
  • ::Not really. Many of the tags I corrected yesterday were on low-traffic articles; many of our articles are, and the tags are invisible to readers and to editors reviewing the article in reading mode or editing a specific section of the article; and even those editing the lead may have no reason to pay any attention to the tag. I was also reminded yesterday how long errors can survive, when I examined and corrected a factual error in the text of a high-traffic article (105,213 page views in 30 days); that one had survived over 3500 edits since 2011. NebY (talk) 19:39, 19 April 2025 (UTC)
  • Option 3, have a supervised trial, similar to option 2a (with human review) but on a limited sample of pages, to evaluate the error rate and find out whether it is fit for deployment. Chaotic Enby (talk · contribs) 11:02, 19 April 2025 (UTC)
  • Option 1 Uniformity is a vastly overrated condition. It's small value, if any, is not worth the downsides of having a bot mess with dates. North8000 (talk) 13:22, 19 April 2025 (UTC)
  • Option 1 Thanks for thinking about this but experience shows that automated edits lead to disruption. As outlined above, exceptions exist and many good editors become highly agitated when bots repeatedly fiddle with article style without an understanding of context. No significant benefit would result, for example, from protecting readers from the horror of encountering "April 1, 1725" in an article on a British monarch. Johnuniq (talk) 04:19, 20 April 2025 (UTC)
  • Option 1 As per Johnuniq, to many issues with bots, and would hate to see American dates on pages fir any article that should be DMY.Davidstewartharvey (talk) 06:30, 20 April 2025 (UTC)

Superscript and subscript typography guideline

{{User:ClueBot III/DoNotArchiveUntil|1748149267}}

{{rfc|style|rfcid=CFC697A}}

Is there support to upgrade Wikipedia:Manual of Style/Superscripts and subscripts to a guideline? 04:14, 20 April 2025 (UTC)

Rationale of the proposer: The main effect would be to officially recommend using HTML superscripts and subscripts instead of Unicode subscripts and superscripts (e.g. {{char|2}} instead of {{char|²}}. This has generally been done on a de facto basis, for example in widely used templates like {{tl|convert}}, {{tl|frac}}, and {{tl|chem2}}. I estimate only about 20,000 out of about 7 million articles use the Unicode characters outside of templates, mostly for square units of measure or in linguistic notation that should be put into a template. A lot of articles have already been converted to the HTML method, either organically or systematically.

This would also bless the exceptions for linguistic notation, which have arisen after complaints from some editors of that topic, who say these Unicode characters are specifically intended for that purpose.

The other exceptions and sections are I think just summaries of other guidelines, put in one place to help editors who are working on typography or e.g. asking the on-site search engine "how do I write subscripts?" when they really want to know how to write chemical formulas specifically. -- Beland (talk) 04:14, 20 April 2025 (UTC)

  • Support upgrading to guideline. I don't see any reason not to and this looks like good advice. However, I am also no expert on HTML/Unicode, so if some compelling issue with this proposed guideline emerges, please ping me. Toadspike [Talk] 09:11, 20 April 2025 (UTC)
  • Support as someone who is reasonably knowledgable about HTML/Unicode.  novov talk edits 09:49, 20 April 2025 (UTC)
  • Support as good HTML/Unicode practice. However, it could be good to have input from editors who might be more directly affected by this (maybe editors who use screenreaders?) to make sure this will not cause any unforeseen accessibility issues. Chaotic Enby (talk · contribs) 12:59, 20 April 2025 (UTC)
  • :For context, the reason Unicode characters are allowed for only {{frac|1|2}}, {{frac|1|4}}, and {{frac|3|4}} is that these are the only fractions in ISO/IEC 8859-1; others can cause problems, according to {{u|Graham87}} comments at Wikipedia talk:Manual of Style/Mathematics/Archive 4#Accessibility of precomposed fraction characters. The only superscript or subscript characters in ISO/IEC 8859-1 are superscript "2", "3", "a", and "o". I would expect using HTML superscripts and subscripts consistently should avoid screenreaders skipping unknown characters (certainly mine reads out footnote numbers). I use a screenreader for convenience and not necessity, though, and I welcome comments from others! -- Beland (talk) 17:41, 20 April 2025 (UTC)
  • ::Yes, exactly this. Graham87 (talk) 03:51, 21 April 2025 (UTC)
  • Oppose. Wikipedia talk:Citing sources is currently having extensive discussions about which rules apply to citations and which do not. {{User|Beland}} is heavily involved in these discussions. I believe those discussions should be resolved before any new related guideline are created. Failing that, I notice the essay has no mention of citations. This means whoever wrote it wasn't giving any thought to citations. Therefore an prominent statement should be added that it does not apply to citations. Jc3s5h (talk) 13:24, 20 April 2025 (UTC)
  • :I don't think anyone is proposing to use Unicode superscript characters for endnote indicators? It seems reasonable for endnote contents to follow the general guidance on the use of superscript and subscript markup. isaacl (talk) 17:09, 20 April 2025 (UTC)
  • Support with the obvious exceptions of references to characters themselves. I don't see why citations would have an exception here. Headbomb {t · c · p · b} 10:50, 21 April 2025 (UTC)

Provisional Initiative: Improving Judy Garland Content on Wikipedia

Hello Wikipedia editors,

I’m thrilled to announce that I’ve created a provisional project page aimed at organizing efforts to improve and expand coverage related to Judy Garland—her extraordinary career, her lasting cultural impact, and her place in classic Hollywood history.

This initiative invites passionate editors to collaborate on enhancing articles about Judy Garland and the broader context of musical cinema and classic film. Whether you’re a film buff, a musical theatre enthusiast, or someone interested in the nuances of biographical research, there’s room for your expertise in this project.

Why Join This Initiative?

  • Judy Garland’s legacy deserves more thorough and systematic documentation.
  • Articles related to her life and career can benefit from improved research, quality upgrades, and expansion.
  • It’s a great opportunity to work together and foster collaboration within the Wikipedia community.

Explore the Project Page: Check out the provisional draft, where you can find goals, activities, and ways to contribute: User:Jorge906/WikiProject_Judy_Garland

Your participation, feedback, and suggestions are invaluable as we build this collaborative effort. Whether you’re interested in drafting new content, refining existing articles, or organizing edit-a-thons, every contribution matters.

Feel free to share your thoughts on the draft project page or reply to this post. Together, we can create a meaningful space to celebrate Judy Garland’s influence while enriching Wikipedia’s coverage of film history and musical performance.

Thank you for considering this opportunity to contribute—let’s make a difference together!

Best regards, Jorge Lobo Dos Santos (talk) 10:09, 21 April 2025 (UTC)

:See Wikipedia:WikiProject Council/Guide - proposals for new Wikiprojects should be made at Wikipedia:WikiProject Council/Proposals. AndyTheGrump (talk) 10:25, 21 April 2025 (UTC)

::thanks. Jorge Lobo Dos Santos (talk) 10:29, 21 April 2025 (UTC)

:::It's good to have a goal to work on a particular set of articles collaboratively, even outside of a formal WikiProject, although there needs to be a list of articles for that to work. I would advise against relying on AI-generated text for such a project, as llms can easily misunderstand Wikipedia's goals, for example not being great at understanding aims such as WP:IMPARTIAL and other parts of WP:NPOV. CMD (talk) 10:31, 21 April 2025 (UTC)

:Jorge, I wish you luck, but fear that you will need a lot of it. The scope of your proposal seems very narrow. Please read carefully the advice given at the page Andy linked. Phil Bridger (talk) 10:35, 21 April 2025 (UTC)

Proposal to clarify which MOS guidelines apply to citations

I have proposed to clarify which MOS guidelines apply to citations. Please see the discussion at Wikipedia talk:Manual of Style#Proposal to clarify which MOS guidelines apply to citations. Jc3s5h (talk) 13:14, 22 April 2025 (UTC)

Add the templates “More citations needed” and “More citations needed section” to the Suggested edit template list

{{atop|1=Further discussion should take place at {{section link|Wikipedia_talk:Growth_Team_features#Add_the_templates_“More_citations_needed”_and_“More_citations_needed_section”_to_the_Suggested_edit_template_list}} to avoid a talk fork. Sdkbtalk 06:55, 23 April 2025 (UTC)}}

At the page MediaWiki:GrowthExperimentsSuggestedEdits.json, for the “References” task, I’m noticing that the templates “More references” and “More references needed section” are listed there, instead of the far more widely-used templates they redirect to (“More citations needed” and “More citations needed section”). This has resulted in the vast majority of the articles/sections suggested on the “References” task being entirely unsourced, which would be more difficult for newcomers to fix. The “references” templates have around ~3000 transclusions combined, while the “citations” templates have hundreds of thousands of transclusions, resulting in a lot more suggestions. Simply adding the two more widely-used templates to the list would likely result in a lot more newcomers attempting to do the task, and greater newcomer retention on Wikipedia.

(I wasn’t sure where to post this, so sorry if this is the wrong topic for the village pump.) ApexParagon (talk) 21:12, 22 April 2025 (UTC)

: WT:Growth Team features would probably the proper venue. Support doing this by the way. * Pppery * it has begun... 21:21, 22 April 2025 (UTC)

::Added there ApexParagon (talk) 21:29, 22 April 2025 (UTC)

{{abot}}

Grant move-subpages to template editor user group

{{Moved from|Wikipedia:Village pump (idea lab)#Grant move-subpages to template editor user group|To gain a wider consensus here before filing a phab ticket. – robertsky (talk) 14:21, 24 April 2025 (UTC)}}

At Wikipedia:Requested moves/Technical requests, a request was made to move {{tl|Myprefs}} to {{tl|Preferences}}. While the requestor could move the template, the rationale for filing was because there are a number of subpages to move as well and moving a number of subpages can be error-prone.

Given that current practices for Template development oblige everyone to use at least 3 subpages, /docs, /sandbox, /testcases, if a template editor chooses to move a Template, they may run into similar situations more often than not.

In the request, @Pppery raised the idea of granting move-subpages right (Move pages with their subpages) to the template editors, and I find that it is a good idea and template editors are a group of trusted editors already. This would reduce the friction template editors who are not page movers face when moving templates on their own. – robertsky (talk) 18:43, 20 April 2025 (UTC)

:If there is a way of restricting move-subpages to the template namespace then this is an absolute no-brainer. If there isn't then I still think on balance it will be a positive - the number of template editors who would abuse this in other ways is going to be extremely small. Thryduulf (talk) 18:54, 20 April 2025 (UTC)

::I agree. If really needed we could tag rapid bulk moves in mainspace with an edit filter, but as you say I doubt that's how rogue template editors would choose to disrupt a wiki. Aaron Liu (talk) 20:04, 20 April 2025 (UTC)

::I don't think the namespace limitation is necessary or a good idea. Firstly template editor is a much higher trust position than page mover - if we trust people to make edits that could break millions of pages we should trust them to be able to move pages. Secondly a lot of templates are not located in the template namespace - lots of templates are in the user and wikipedia namespaces, for example. 86.23.109.101 (talk) 08:25, 21 April 2025 (UTC)

:Agree with this too, either limited to the template namespace if possible or in general. I don't think pagemove vandalism by template editors is really a concern, or that it would raise the bar for granting template editor. Chaotic Enby (talk · contribs) 20:11, 20 April 2025 (UTC)

::Agreed. Subpages are disabled in the main namespace though, therefore so are subpage moves. Graham87 (talk) 06:43, 21 April 2025 (UTC)

:Add me to the group of people that agrees with this whether or not it's limited to just the template namespace; template editors can do a lot more harm than moving subpages if they want to disrupt Wikipedia, and I doubt we'll run into many issues with template editors moving subpages against policy. Skarmory (talk • contribs) 00:09, 22 April 2025 (UTC)

:I'm okay with this, though I think limiting to the template-space as a social constraint (doesn't need to be a technical one, just revoke template editor from those who can't follow the namespace restriction, as it proves they can't adhere to the requisite guidelines) would be a good idea. If they need to move other types of pages, I doubt most template editors would have much trouble asking for page mover anyways. EggRoll97 (talk) 03:54, 22 April 2025 (UTC)

::I do not think that there is an easy way to prevent template editors from moving subpages with edit filter. If there's any side effect of a template editor with the right moving articles nomally, it would probably be moving of archive subpages of the accompanying talk pages in a single move, which I wouldn't begrudge as well. – robertsky (talk) 12:22, 22 April 2025 (UTC)

:::It would be possible with an edit filter, though not necessarily worthwhile. Presumably template editors can be trusted not to click the box to move subpages when moving a mainspace article or a page in another namespace than Template or Module. TPEs without the page mover flag would be limited to 8 moves per minute (the page move rate limit for non-page movers), so it's not like they could cause too much of a problem even if they went rogue anyways. EggRoll97 (talk) 22:34, 23 April 2025 (UTC)

::::Just to confirm: A single move of all the subpages with the move-subpages right counts as one move, not the number of subpages, right? Aaron Liu (talk) 22:46, 23 April 2025 (UTC)

:::::From a technical standpoint, yes. It's up to 100 subpages at once according to T16356 (anything past that needs to be manually moved I think?), which means a malicious actor could theoretically move 800 pages a minute with move-subpages, but for trusted editors like TPEs, I doubt they'd be doing that kind of thing. EggRoll97 (talk) 00:16, 24 April 2025 (UTC)

: Do we have sufficient consensus to request this be deployed on Phabricator now, or does this need to be moved to some other venue as the ideal lab is an odd place to obtain consensus for something? * Pppery * it has begun... 18:29, 22 April 2025 (UTC)

::I'd either move the discussion to WP:VPPRO or put a pointer there back to here and add links to the discussion from Wikipedia talk:Template editor and Wikipedia talk:WikiProject Templates, and give the 'crats a heads-up at WP:BN that we might be increasing their workload. After doing that I'd give it at least another 3-4 days. Thryduulf (talk) 18:38, 22 April 2025 (UTC)

:::Question: Would you mean AN? Crats don't grant template editor (at least not as crats, they would as admins, I suppose). EggRoll97 (talk) 21:28, 23 April 2025 (UTC)

::::yes, I think I was conflating this with the electadmin proposal. Thryduulf (talk) 02:59, 24 April 2025 (UTC)

:I agree this is a good idea. Sending requests like that to RM/TR is inefficient, since I'm pretty sure non-template editor pagemovers can't move template-protected pages, so an admin would have to do it, and requests in the admin section tend to take a while to get done. I agree with EggRoll97 that we can say "please don't use this to do mass-moves unrelated to templates", though enforcement would be case-by-case and not via edit filters or other tools. Toadspike [Talk] 09:18, 23 April 2025 (UTC)

::Er.. RM discussions for Templates, if move consensus is found, may still come RM/TR's way, especially if pageswapping is required, but TEs effectively can effect the move of Templates listed on RMTR with ease now if no pageswap is required. But I would encourage the TE to apply for pagemover rights if they enjoy being on RM/TR. – robertsky (talk) 14:41, 24 April 2025 (UTC)

:::There's probably far more moves that require moving subpages but not swapping. Aaron Liu (talk) 14:43, 24 April 2025 (UTC)

:{{small|Note: Topic moved to VPP for further discussion. Pinging @Aaron Liu, @Chaotic Enby, @EggRoll97, @Graham87, @Pppery, @Skarmory, @Thryduulf, @Toadspike for awareness. WP:AN has been notified. – robertsky (talk) 14:35, 24 April 2025 (UTC)}}

:I am jumping the gun here, planning on a succesful closure, ha!

:# Do we notify existing TEs about the change? If yes, all 189 of them (as counted on Wikipedia:Template editor)? Or we revoke some first based on Wikipedia:Template editor#Criteria for revocation? There may be bots or alternate accounts (for testing maybe?), so those can be excluded from the alerts.

:# And how? a one time special Mass Message?

:# The change can also be updated in the admin newsletter and Signpost, but not all TEs subscribe to them (neither do all admins).

:# WP:AN will definitely be notified as well once the change is in effect.

:# WP:Template editor, WP:User rights, and other pages (are there?) should be updated accordingly as well.

:– robertsky (talk) 15:36, 24 April 2025 (UTC)

:: Personally I don't think any kind of notice is necessary. * Pppery * it has begun... 15:44, 24 April 2025 (UTC)

::Probably just AN and VPT or some other relevant noticeboards. Mass message is a bit far. Aaron Liu (talk) 15:47, 24 April 2025 (UTC)

:::Chiming in possibly a bit late to say that 68 of the 189 template editors already have the page mover right, if [https://en.wikipedia.org/wiki/Special:ListUsers?username=&group=extendedmover&wpsubmit=&wpFormIdentifier=mw-listusers-form&limit=1000 this is a list of page movers] and I did my "find duplicate lines" text processing correctly. If we haven't seen any problems with those 68, the other 121 probably won't cause much trouble. I support this proposal as someone who already has both rights, but who has to clean up incomplete template moves from time to time. – Jonesey95 (talk) 16:30, 24 April 2025 (UTC)

  • Support move-subpages is restricted because one can easily make a big mess with it. Template editors are trusted on technical matters, though, so I see no cause for concern (the level of trust for template editor is generally higher than that for page mover, especially regarding technical matters). Oppose restricting this to template-space for that reason as well. If someone without the permission wants to move a page with a bunch of subpages, they can do it manually (there's no policy against someone doing that); there's no reason to inconvenience our template editors with that. Elli (talk | contribs) 19:16, 24 April 2025 (UTC)

:Support with template restriction. Not necessarily in template space, just a restriction to using this right only for template moves. As for Elli's concern above, from a technical perspective, sure, they could move a random page with subpages manually, but they'd quickly run into the 8 page moves per minute rate limit. EggRoll97 (talk) 22:31, 24 April 2025 (UTC)

::Okay, but what's the point of having the restriction? The restriction on doing this isn't high-trust; it's just to prevent people from making a mess. We know template editors won't make a mess. Elli (talk | contribs) 23:02, 24 April 2025 (UTC)

:::You have a point. My insistence on the template restriction is fairly weak. I just don't see necessarily why a template editor should be using this outside of..well, templates, given that we have page mover as a more general flag for move-related things. In any case, whoever ends up evaluating consensus here may feel free to consider this perhaps neutral, or the weakest possible support on the template restriction. EggRoll97 (talk) 02:10, 25 April 2025 (UTC)

Finishing [[WP:LUGSTUBS2]]

We had consensus at WP:LUGSTUBS2 way back in March 2024 to draftify a bunch of articles, which was never implemented. Is it finally time to implement it now? * Pppery * it has begun... 14:26, 24 April 2025 (UTC)