This is the Village pump (all) page which lists all topics for easy viewing. Go to the village pump to view a list of the Village Pump divisions, or click the edit link above the section you'd like to comment in. To view a list of all recent revisions to this page, click the history link above and follow the on-screen directions.
This RfC seeks to resolve a discrepancy between the WP:Template namespace guideline, which historically advised that Templates should not normally be used to store article text, as this makes it more difficult to edit the content, and the longstanding status quo practice of having such prose templates (see the 54 entries and 6 subcategories of Category:Article shared content templates, which was created in 2008). Editors have disagreed over how to interpret "normally" in the guideline, particularly during a long-running dispute over the existence of the {{Rotten Tomatoes prose}} and {{Metacritic film prose}} templates, with a December 2023 RfC and June 2026 TfD reaching different conclusions. A recent attempt to adjust the guideline text did not garner significant engagement due to participant confusion. Editors suggested instead asking directly about the permissibility of prose templates, which has led to this discussion. Sdkbtalk 16:05, 22 October 2026 (UTC)
Survey (shared content templates)
Option 2A. This RfC speaks to the heart of why templates exist. They exist because, when information is used in multiple places, we want to centralize it rather than copying it so that we can maintain, optimize, and standardize it in a single place. This principle (expressed in the software world as don't repeat yourself) is as fundamental to reducing the workload needed to make Wikipedia as the content scope limitations imposed by our notability requirements. It is obvious for templates like infoboxes — imagine what a disaster it would be if we tried to design an infobox from scratch for every article, debating which fields to include and how to order them — but it applies equally well to some instances of text that is reused between articles. This includes A-Z series of articles that should have the same introduction (e.g. {{List of post offices in Colorado header}}) as well as sections/paragraphs that may be reused with only a few changes that can be captured by parameters (e.g. {{Year article header}} and {{Rotten Tomatoes prose}}).
Prose templates with thousands of transclusions have been used for years, with good reason:
Templated text is standardized, which is often good. Readers become accustomed to certain aspects of Wikipedia style over time, and when articles are similar, it makes it easier to navigate unfamiliar pages because they know what to look for.
Templating allows for optimization. When a format is applied over hundreds of pages, it becomes worthwhile to refine small details that probably would never have been considered at the level of an individual page. Disputes can be resolved at centralized discussion rather than playing out diffusely on thousands of low-visibility pages.
Templates can be improved over time. When circumstances or best practices change (such as Rotten Tomatoes deprecating the average score metric), we can easily make edits to templates that improve all their transclusions at once. That's a lot easier than trying to update individual articles.
The main downside of putting article text in templates, of course, is that doing so makes it harder to adjust the text (particularly since we don't yet have visual editing within template fields). Given this, we don't want to do it for articles where the text may need to be changed frequently or customized between articles. However, this RfC asks when prose templates should be allowed, not when they should be required, so editors can always just decide not to use them where they don't fit. And for pages where no frequent changes are needed, the stability of prose templates becomes a feature rather than a bug. It means that an individual editor's unconsidered personal preference won't override the standardized version collectively optimized by all the editors who contributed to the template — unless their preference is truly superior, in which case they'll be able to get consensus to change the template and improve many articles with it instead of just one.
I support Option 2A over 2B because whether or not content may need to be edited in the future is often unclear. 2A allows editors to take individual circumstances into account when deciding whether the benefits of templatization are worthwhile for a given piece of content. But most of all I strongly oppose Option 1, which would disastrously splinter our content into fragments, hampering our ability to maintain, optimize, and standardize it. Sdkbtalk 16:05, 22 October 2026 (UTC)
I agree with this analysis. In the medical and anatomy space I commonly see this used where text in one or two closely related articles is intended to be standardised (keeping both article in sync, up to date, and saving editor time), or to store complex content (such as a complex table or image with mapped links) which would visually or technically overwhelm the average editor of the wiki text. In those limited cases I think it would be better for the quality of our encyclopedic content to have them discussed on an individual basis e.g. at TfD rather than have a blanket rule. Tom (LT) (talk) 08:13, 24 October 2026 (UTC)
@Sdkb Given that we regularly and, in some cases, automatically protect high-risk templates, locking out access to all but admins and a select few template editors in certain pages, could you explain how you see your solution as compatible with WP:PREEMPTIVE? Do you think we should stop most editors save admins or template editors (such as yourself) or do you believe high-transclusion templates which contain prose should be unprotected? GreenLipstickLesbian💌🧸 09:31, 12 November 2026 (UTC)
Prose templates are templates just like infoboxes or any other templates, so my view is that we should be applying the protection policy the same as we do for any other template. Sdkbtalk 17:08, 12 November 2026 (UTC)
They are quite obviously not the same as any other template though. GreenLipstickLesbian💌🧸 21:48, 12 November 2026 (UTC)
Templates that are only transcluded on a set of related pages, such as {{Named storms intro}}, don't need to be protected solely based on the number of pages that transclude them. Ideally, changes to this kind of template would appear in the watchlists of users who watch the articles. Jruderman (talk) 00:39, 13 November 2026 (UTC)
@Jruderman There is community consensus templates can be protected solely based on the number of pages which transclude them, though. This is done because the community knows templates are often less monitored, harder to revert vandalism on, and because (at least at the time), cacheing could keep vandalism up for a while, even if the vandalism had already been reverted.
(By the way, you can look at changes to templates by looking at the "related changes" buttonGreenLipstickLesbian💌🧸 02:49, 13 November 2026 (UTC)
2A, policies and guidelines should be descriptive, and there seems to be no argument that the de facto status quo is problematic. Thryduulf (talk) 16:52, 22 October 2026 (UTC)
A well-regulated set of articles being necessary to the consistency of a free encyclopedia, my 2A right to bear content templates shall not be infringed. More seriously, pretty much per nom. I'll add that this, in a way, makes it easier to edit the text in some ways, as editing one source of information is easier than keeping many pages in sync and fixing discrepancies on each individually. Chaotic Enby (in solidarity · talk · contribs) 17:43, 22 October 2026 (UTC)
One problem with templated text is locating where to edit when editing is desired. Blueboar (talk) 18:03, 22 October 2026 (UTC)
Of the options presented, I would lean towards 2B… allowed but rare. Blueboar (talk) 11:52, 23 October 2026 (UTC)
Something that would be amazing would be a script/gadget that allows you to click on a template and move to that template's editing window, if anyone is in the mood for coding this! Chaotic Enby (in solidarity · talk · contribs) 18:14, 22 October 2026 (UTC)
Template:Excerpt actually shows an edit link in the section hatnote that will take you straight to the page being transcluded from the page it's on, so there is precedent for this functionality. Choucas🐦⬛ 22:46, 22 October 2026 (UTC)
I would love that!!!! JuxtaposedJacob (talk) |:) | he/him | 03:51, 26 October 2026 (UTC)
@Chaotic Enby I think a drawback of this is that most newbies/casual editors will not install scripts or gadgets. Power editors like us do -- but I feel that our overreliance on scripts leads to us making processes which are too technically complex for the average editor to actually use. Like this one -- heck, if we're even having you, somebody who I consider highly skilled at template editing saying that we need to simplify our system with add-ons to make things easier for the elite users... a newbie or a casual editor is just going to see the error, the awkward wording, the vandalism, struggle trying to fix it, and (because they have no emotional investment in this platform yet, like we do)... leave. Again, see my comment below about actually walking a person, in real life, through editing a template transcluded on an article.GreenLipstickLesbian💌🧸 03:57, 26 October 2026 (UTC)
Very good point. I know that editing transcluded pages in situ is technically possible (DiscussionTools, which is installed by default, manages to do it), but very costly to implement – to go back to DiscussionTools, it parses the entire HTML content of the page, finds an editing context, and converts it back to wikitext! Building a gadget that does it on any page in the Visual Editor, reliably enough to be turned on by default, will be quite a technical ordeal, and probably not one whose cost would be justified here. I'm still convinced that 2C is preferable to 1 for the only reason that editing a page under option 1 won't fix the issue on all affected pages, but just put them out of sync, which will add more maintenance costs. Still, the situation is far from obvious, and I understand both positions here. Chaotic Enby (in solidarity · talk · contribs) 17:43, 27 October 2026 (UTC)
Good, because I definitely don't understand option 2. I think it's going to cause us to loose new editors, so power editors can... have a slightly easier time of it and not have their own writing altered? Speaking as an editor, I'd rather have a mistake fixed on one page than a mistake fixed on zero pages because we have protected it because we don't think it's going to be edited. It flies in the face of WP:PREEMPTIVE and WP:5P3 -- namely, that anybody can edit and article and nobody owns anything. This is de-facto ownership, even if it's not called that. GreenLipstickLesbian💌🧸 18:56, 27 October 2026 (UTC)
Per my comment below, suggesting option 2C: "Option 2A but only when there is an expectation that the template will be used uniformly in a series of articles sharing a common structure".To take concrete examples, a common header for year articles or tropical storm lists would fit, while a background section excerpted in several Gaza war-related articles would not, as the surrounding article context and what is WP:DUE would vary from one to another. Chaotic Enby (in solidarity · talk · contribs) 19:17, 23 October 2026 (UTC)
Option 2B I am not a fan of how "templates" such as {{2026 Iran war infobox}}, {{Gaza war casualties}} (and formerly {{Gaza war infobox}}, which I merged back in to Gaza war) are being used in practice. These pages store large-scale and controversial article content separately from the main article(s): this encourages a lack of correlation between infobox and body or between lead and body, contrary to WP:INFOBOXPURPOSE and MOS:LEADFOLLOWSBODY. The Gaza war casualties template is also transcluded at Casualties of Israeli attacks on the Gaza Strip and Killing of health workers in the Gaza war, so any change to the main template has to be assessed for WP:NPOV concerns at these sub-articles. (The infobox templates also serve(d) as magnets for WP:INDISCRIMINATE material and cruft.)On the other hand, I can see how templates such as {{Named storms intro}} make life easier for editors: they standardise non-controversial information which does not have to vary across articles. The key point is that they will not have to be edited that much. For that reason I must separate the two use-cases and !vote for 2B. ~~ AirshipJungleman29 (talk) 11:40, 23 October 2026 (UTC)
I very much agree that anything that touches on WP:DUE depending on its transclusions, or is transcluded in different contexts, will be a problem. I don't think the expectation of edits is necessarily the best line to draw here: the same issue could pop up in historical CTOPs. A better line might be "consistent use in a well-defined series of articles" versus "context-dependent use in related articles". Chaotic Enby (in solidarity · talk · contribs) 13:18, 23 October 2026 (UTC)
1, a longstanding believe of mine: these templates may be nice for power editors, but they're confusing, hard to understand, hard to edit, and poorly explaining for casual editors or newbies. If there's no expectation that the text will need to be edited regularly, then a substitution should be fine. Right now, it feels like we're inadvertently using these templates to psueodo- protect certain sections of text to all but a few power editors, most interested in the topic. I'm sure that's not the intention, but that's how it works. GreenLipstickLesbian💌🧸 18:16, 23 October 2026 (UTC)
I was to to explain to a friend this RFC/template editing as it intersects with articles as his response was "As an objective observer, what the fuck does that mean?". So yeah -- the casual editors might struggle with this. GreenLipstickLesbian💌🧸 01:09, 24 October 2026 (UTC)
Option 1. It appears we're doing this again so I'll post for the third time what I last posted at Wikipedia_talk:Template_namespace#RfC:_Prose_templates: Option 2A and Option 2B create a distinction between "stable" and editable article text that is not supported in the longstanding wording or history of WP:TG and turns the expectation that article text will largely remain unchanged into a justification for storing it in a template. We are here once again to discuss Sdkb's mission to establish an exception for supposedly "stable" article text. I see no basis for treating one particular wording in articles as fixed boilerplate that ought to be protected from normal article-level editing. Certainly not at the level that would require us to alter the existing guideline. If such text is deemed "boilerplate" then that also applies to just about an endless amount of article text across Wikipedia that could be templated on the same basis. But the perceived convenience of using a template to deal with such repetition is not sufficient reason to hide article text behind a template. Nor is the notion that no particular editor sees an actual reason to change the text. Article text doesn't require evidence of a need for future edits to justify its continued existence at the article level. And, to echo the point made by GreenLipstickLesbian above, all these prose templates do is protect a class of text to a coterie of power editors rather than to editors at the article level, which is where the text is actually seen by readers and which is actually watched by the relevant editors. Οἶδα (talk) 07:04, 24 October 2026 (UTC)
Weak Option 2A I don't see a problem in limited situations. I'm not a fan of {{Rotten Tomatoes prose}} but I can see the reason for it's usage. However something like {{Gaza war casualties}} that has extensive content shouldn't be allowed. If it's necessary it can always be part of one article, and transcluded to another. Hiding so much content inside a template isn't helpful, templates shouldn't replace sections of an article. -- LCU ActivelyDisinterested«@» °∆t° 15:34, 24 October 2026 (UTC)
Option 1 by simply removing the word "normally" from the current guideline text. That word is so weaselly as to continue to cause confusion. Where sufficient strong consensus exists, -any- guideline can have an exception, and that's where the current instances need to be examined for their individual worthiness. That doesn't mean to water down the guideline itself. -- Netoholic@ 17:11, 24 October 2026 (UTC)
Option 1 per GLL and Οἶδα. Templates should not be used for this, this creates more problems than it solves, it creates problems for actually managing this content, for little no benefit. PARAKANYAA (talk) 19:55, 24 October 2026 (UTC)
Option 2A, perhaps with limitations on the size or types of text for which this can be used. I have created a number of lists that transclude sections from sublists, which should be permissible, but text for text itself should not be. BD2412T 23:14, 24 October 2026 (UTC)
Option 1 per Οἶδα. Each article should be standalone and easy to edit. Having text transcluded from other templates is confusing and unnecessary, and risks applying nuance from one topic to areas where a different nuance applies. Likening it to a software project is a red herring. Wikipedian is not code or software, it's human-generated prose on particular topics, and a certain amount of redundancy is expected. Cheers —Amakuru (talk) 23:26, 24 October 2026 (UTC)
Restrictive Option 2A – For cases like the list of named storms, where we are dealing with significant chunks of text – not bits and pieces here and there that are inserted amidst prose that editors are expected to edit – for sets of clearly delineated articles for which it would be verging on unencyclopedic to have minor style differences between, I think there is a very good argument for ensuring that the leads remain consistent. This also extends to the example for years and Colorado post offices. I oppose 2B as "expected to edit the template" is vague and also overly restrictive – an edit here and there is alright, the point is just that any edit should be made to all members of the set of articles in question. The reason we even split lists into A–Z is entirely for practical reasons, not to let them have different leads.I do not view this as extending to small bits of prose such as the Rotten Tomatoes example. That is the sort of thing that can often be better off being woven into other text and is placed in the middle of articles, as opposed to being whole sections, and readers are unlikely to find inconsistency particularly jarring, unlike with sets of clearly connected articles that are clearly intended to have shared formatting for some sections. –Maltazarianᚾparleyinvestigateᛅ 00:12, 25 October 2026 (UTC)
Option 1 per Amakuru and GreenLipstickLesbian. Every article should be standalone, and this makes it more confusing for new editors. Ealdgyth (talk) 21:59, 25 October 2026 (UTC)
Option 1 - Very confusing for new editors. The benefits are not worth the potential loss. InfernoHues (talk) 00:35, 26 October 2026 (UTC)
Option 2a As Wikipedia loses editor count, we need to use the technology at our disposal to simplify editing the encyclopedia. Further, it is nice to see similar articles have the same text, rather than figure out how to say the same thing x number of different ways or do the messy solution of copying and pasting. Also, "templating" article prose can be a cool way to teach new editors a different part of the wiki-tech-ecosystem, to respond to the above comment by InfernoHues. JuxtaposedJacob (talk) |:) | he/him | 03:50, 26 October 2026 (UTC)
Option 2A I believe there are legitimate uses for these to provide consistency in certain cases and there is no need to ban them altogether. Reywas92Talk 03:51, 26 October 2026 (UTC)
Option 2C per Chaotic Enby. It won’t always be appropriate to duplicate prose between articles as surrounding context and due weight need to be taken into account, but when a large set of articles are going to have an identical structure, we might as well avoid duplication of effort by putting that structure in a template. I’m not convinced by the argument “it makes it hard to edit” - any editor can always just replace the template with raw prose in any specific article if warranted. -- LWGtalk(VOPOV) 07:14, 26 October 2026 (UTC)
Given the difficulty in maintaining a shared block of content in isolation from all the contexts in which it is used, I do not feel the conditions in proposals 2A and 2B are sufficient. Before explicitly endorsing a best practice, I think we need to further discuss what situations might be tenable for re-use. For example, an entire logical section of text with a starting header might contain sufficient context to be effectively maintained on its own. isaacl (talk) 16:25, 26 October 2026 (UTC)
Option 2A. It's easier to learn how to edit templates than to learn how to efficiently find and mass update every article that needs the same change. Mass updates also cause problems for watchlists (when they aren't done by trusted bots). Jruderman (talk) 01:59, 27 October 2026 (UTC)
Option 3: actually apply existing guidelines and best practices. I will explain what I mean by that, and why I am dissatisfied with the three options proposed. First, as it has been pointed multiple times in the discussion section, the way this RfC defines the current status quo is innacurate if not misleading. Neither 2A nor 2B are the norm, de jure or de facto: templates are very rarely used to store article text, and there is no such thing as a threshold where it can be expected that a piece of prose would benefit from being frozen in place. This is for all the good reasons pointed out by people !voting for option 1, and per WP:TG: hiding content within templates makes it harder to edit, hard to track down, and overall less accessible. However, framing option 1 as "substitute everything" is just downright problematic. There is a huge difference between a paragraph of plain text, and a complex table with embedded images. Moreover, I agree with many supporters of options 2 that transclusion is a useful tool, because sometimes the same quality content actually can and should be used in multiple places, both to make its maintenance easier, improve collaboration and just efficiency in general. Having said that, to me, the core issue here is storing article text, and especially simple prose/simple tables, in template space. The good news is, we have already figured out the better way to do that, and it is conveniently indicated at the top of Category:Article shared content templates: Templates which contain material which would otherwise be in main space encyclopedic articles. Please be aware of Wikipedia:Template namespace#Guidelines on this topic; consider using a template such as the ones in Category:Transclude page content templates that keep shared content in main space, making it easier to find and edit.. There are several of those, but as far as I have looked Template:Excerpt would do the job very well in almost all cases: bring back the content in main space, and provide direct editing links from wherever it is transcluded. Let's apply common sense, substitute and excerpt the simple prose and tables, and keep the things that actually benefit from being templates (e.g. clickable diagrams) as templates. We already have all the tools needed to improve things here, we just have to use them. Choucas🐦⬛ 09:34, 27 October 2026 (UTC)
Option 2A. Some articles do have substantial overlap of content types. For example, the demographics sections of all tens of thousands of American towns can pretty much be derived from the same sources, which is where a template formulation really comes into handy. And while that particular template is always substed, there are other templates that are both short and widely-used enough that substing them does more harm than good, especially if you need to fix errors. If it's hard for editors to edit, there are other ways to address this (e.g. by adding an edit link to the template). As to the point that articles all need to have standalone text, in my experience I find that there are many, many, many cases where this is not accurate - for example, there are entire topics that all share the same background, or the same type of data such as US census data. –Epicgenius (talk) 23:15, 31 October 2026 (UTC)
Option 2A. Agree with above arguments especially by Sdkb. Templates exist to reduce duplication and make it easier to maintain consistency across WP, this principle should apply to prose. The existing guideline is against established practice as shown in OP. Templates like these shouldn't need regular editing other than the parameters in individual articles, so the accessibility and discoverability of the prose isn't important. Templating prose discourages changes that don't have consensus, going against standard practice. Indagate (talk) 15:28, 1 November 2026 (UTC)
2A. Shared content templates ensure that the same content remains up to date across articles and reduces the time required and risk of inconsistencies introduced if editors need to update the same content across multiple articles. feminist🩸 (talk) 03:03, 3 November 2026 (UTC)
Option 2A. I don't see a massive difference between creating a template and just doing a normal transclusion, and the latter is, while not all that common, a useful thing in various contexts (for example, I'm using it to keep a consistent "background" paragraph between what will eventually be ten similarly structured articles on the tholos tombs of Mycenae. I don't see an implementation of 2B (or, to be honest, a rationale for it) that both allows this sort of transclusion, which is a valuable and established part of Wikipedian practice, and avoids a bizarre double-standard where the rules are different depending on the prefix of the page you transclude from. UndercoverClassicistT·C 13:57, 6 November 2026 (UTC)
The proposer of this RFC misstates the actual status quo, which is more like "we more or less ban it and then some exceptions are permitted at TFD". i.e., something in between option 1 and option 2. Neither of options 2A or 2B are remotely near the actual de jure or de facto status quo, and it was inappropriate to propose this RFC having labeled them such. We have had several templates that I would prefer to see go away not go away (certain infoboxes that are single-page for exceptional length, imagemap templates of a similar sort, and some others I can't recall). I have no particular issue with this status quo. Otherwise, option 1. And I agree with those below that say the proposer of this RFC did not and has not sought a wide-enough audience for this question. Strong oppose options 2A and 2B particularly. We are not in a world where we must standardize text across multiple pages, and both the newbie and experienced-user-unfriendliness is clear. These sorts of templates do not have a need for "optimization", and it is obvious to me they do not need "improvement". Izno (talk) 18:24, 12 November 2026 (UTC)
Badly formulated RFC that does not distinguish between templates that provide entire sentences or paragraphs of content (usually a bad idea) and templates that provide short snippets of content text (like {{convert}} and {{circa}}, often a good idea). —David Eppstein (talk) 01:05, 13 November 2026 (UTC)
Option 2B due to accessibility concerns raised by GreenLipstickLesbian. I especially oppose the use of article content templates for controversial topics. Szxq (talk) 18:23, 13 November 2026 (UTC)
Badly formulated RFC per my comments below. But maintain the existing template guidelines, so not 2A, which I guess is closest to 2B if I accept the framing of this RFC, which I don't agree with. The prose templates that were deleted / marked subst-only that this RFC seeks to bring back are best stayed as deleted and they are an editor-hostile feature for both new editors and experienced editors. Article text should be article text, not a confusing web of substitutions. Even if there were cases this could be used responsibly and optionally, experience has shown that some editors "force" the matter and insist on their use. This isn't hypothetical, this actually happened. SnowFire (talk) 02:17, 17 November 2026 (UTC)
Option 2A per UndercoverClassicist. I agree with them in that I don't understand how the objections presented above simply don't apply the same to typical transclusions, which are commonplace and accepted practice. I don't think whether or not the status quo was accurately reflected in the RfC question matters - what matters is what editors think is the best option to choose from here. Editors are free to add additional options to an RfC if they think the listed options do not adequately suffice.Katzrockso (talk) 17:25, 18 November 2026 (UTC)
Discussion (shared content templates)
Notified: Wikipedia:CENT. Reason: Wide-scale potential impact and past disputes in this area regarding breadth of participation.. Sdkbtalk 16:06, 22 October 2026 (UTC)
I know that complaining about RFC phrasing is de rigeuer, but @Sdkb:, I disagree with portraying 2 as the "Status quo". You've picked rare exceptions that likely squeaked by due to not being noticed; we wouldn't consider these strong indicators of a status quo elsewhere, where a few exceptions to a guideline (either on IAR grounds or just due to being missed) wouldn't signify a guideline doesn't mean what it says. The status quo is 1, never do this, due to the very longstanding rule in our template guidelines. If you disagree, then at least don't portray any option as a status quo and say that the matter is simply inconsistent. I also think that if you're going to mention the RFC that found a weak consensus to allow these, you should also mention the later 2025 RFC that found a consensus against them. SnowFire (talk) 20:32, 22 October 2026 (UTC)
Looking more closely, this RFC is also missing a key option between 1 and 2B, and seems to be phrased looking as a reason to remove the prohibition on prose templates. But that is separate from substing everything in Category:Article shared content templates, which is way over the top and not what people who voted to subst & delete the Rotten Tomatoes prose template are talking about. Template:Patrilineal descent of the High Priests of Israel and Template:Religions by country table Asia are clearly not really prose, but just a table, a normal use of templates. Template:Three pillars of sustainability is a fancy image. Template:Transclude DYK is Wikipedia-internal. None of these are prohibited by the guideline that is really under contest here. It's fine to challenge the Template Guidelines but this phrasing is inventing a position for the "other side" that doesn't exist. My suggestion would be to make this RFC be about removing the line from WP:TG that Templates should not normally be used to store article text that may need to edited, as this makes it more difficult to do so. They should also not be used to "collapse" or "hide" content from the reader. Based on the above !vote rationales provided for 2A, that is clearly what is actually at contest. Keeping this line in the template guidelines would not imply deleting this entire category, just making anything prose-only subst-only. (Failing that, at least rephrase option 1 to remove the claim it would mandate emptying that category, because it doesn't.) SnowFire (talk) 20:59, 22 October 2026 (UTC)
I completely agree, the options presented as alternatives to the status quo miss the mark of what the discussions at play have actually been about. I was strongly in favor of mass substuting the Rotten Tomatoes template, yet I believe we should be transcluding way more article content, not less. There is a big difference between templates that allow sharing quality content in all places it can be needed, and templates that uselessly freeze a specific phrasing for three sentences for the sake of pointless standardization. Choucas🐦⬛ 23:08, 22 October 2026 (UTC)
Exactly. I do not find that this RfC fairly portrays the status quo or appropriately captures the landscape of recent discussions. It feeds a bit of context and encourages answers that fit a specific mold. Οἶδα (talk) 03:42, 24 October 2026 (UTC)
I understand the intention here, but I believe this is completely overbroad. If you include all the pages in all the subcats of Category:Article shared content templates, that means lumping together very, very different templates. If this RfC included only the many problematic prose templates that have all the issues WP:TG warns against, because they're basically a paragraph or simple small table that stealthily obscure article content and make it actually harder to edit pages they are on, that would be one thing. But thrown in here is also Category:Transclude page content templates, including the ultra powerful Template:Excerpt, which allows you to precisely fine tune every detail of the transclusion while keeping the content itself in mainspace. I personally consistently !vote at WP:TfD for the substitution of the first kind; at the same time I think Template:Excerpt is very underappreciated and could be used much more to immense benefit. Because of this, I just don't see how I can respond to the survey, as this position is just not represented. Choucas🐦⬛ 23:00, 22 October 2026 (UTC)
Focusing on Wikipedia:Template namespace feels like a bit of a red herring here. Excerpts are not limited to template namespace. The question is, more broadly, what sort of content should be duplicated across articles from a single point of origin. CMD (talk) 12:25, 23 October 2026 (UTC)
I'd also prefer a discussion on this. GreenLipstickLesbian💌🧸 18:43, 23 October 2026 (UTC)
I agree that when considering guidance on re-use of text and wikitext, other approaches such as labeled section transclusion should also be considered.
In my opinion, a key consideration in the feasibility of including content from another page is how to maintain that content in a way that is independent of the surrounding context. This is generally straightforward for navigation boxes and certain types of tables, which is why having them in templates is commonly done. It often is harder to maintain shared prose content in an isolated manner. One has to search for all the uses and double check how the shared content fits within the contexts in which it is used, and make appropriate adjustments simultaneously. This is even harder with labeled section transclusion, as I think source text searches have to be used. While it is true that Ted Nelson's original concept of hypertext included weaving together documents from parts of others, there's a reason why it wasn't realized on a large scale: it's hard to manage coherency when the surrounding context for a piece of content isn't readily apparent. isaacl (talk) 18:44, 23 October 2026 (UTC)
The rather inflated framing of Category:Article shared content templates here as proving "longstanding status quo practice" is specious at best. As I posted previously at Wikipedia_talk:Template_namespace#RfC:_Prose_templates: The largest prose templates include {{Aired episodes}}, which is used in 485 articles, but I cannot find any past discussions at TfD or elsewhere determining its acceptability as a template on Wikipedia or compliance with WP:TG. {{Television franchise episode count}} is only used in 24 articles and likewise has no discussions about it beyond a few merges of duplicate templates. I also cannot find meaningful discussion about {{Year article header}} despite its use in roughly 500 year articles. If these are the only examples, essentially 2 across all of Wikipedia, and there has been no actual discussion regarding the appropriateness of their function in the template namespace then it is dubious to claim that they somehow establish why WP:TG specifically includes the word "normally" or that they serve as proof that such "exceptions are allowed" to the top-level guideline that "Templates should not normally be used to store article text. Such content belongs in the article pages themselves." Especially when we're talking about templates used to store text in the ordinary running text of articles rather than templates with some ancillary article text function that might plausibly justify an exception. The 2014 RfC that introduced "normally" to WP:TG was also rather brief and unimpressive. Either way, "exceptions are allowed" is not, by itself, an argument that a particular exception is warranted. If anything these few examples would indicate how rare exceptions are here on Wikipedia, not that such exceptions should be expanded. And as Netoholic stated in that 2014 RfC, such exceptions would have to maintain their status as exceptions which "break" this particular rule by way of strong consensus. And as Netoholic wrote in their endorsement there: Ever since 2005, its been the intent of the community that the Template namespace not be used to store encyclopedic content. Templates are used to maintain formatting of that content (such as {{cite web}} calls), alert messages to readers ({{citation needed}}), and to provide navigation, but the main "meat" of an article, its information and data that we want editors to freely and easily be able to update, should be in the article namespace itself. Wikipedia:What is an article? describes what counts as encyclopedic content. Sdkb's counter to that was that it's not just two examples. There are more than 50 templates in Category:Article shared content templates, including very clear-cut use cases like {{Named storms intro}}. As I responded, those are very different templates contained there. Nearly all of those templates are not comparable to the kinds we have been discussing both in terms of content and in the frequency of their use throughout Wikipedia. They're basically all data tables. And as with the others, I cannot find any actual discussion regarding the appropriateness of their function in the template namespace. They're WP:OTHERSTUFF that could just as likely be subst'd for the same reason. Or perhaps retained by way of consensus, which is why I would prefer not to settle for Option 1 because I fundamentally reject the options we're being presented here. But consensus has not occurred. And consensus through editing is no longer presumed when disagreement becomes apparent. Well... disagreement has become apparent. And, again, as SnowFire observed above, those kinds of templates are not what is really under contest here. This second RfC specifically announces itself in its prompt as being focused on "templates containing article body text"? Indeed, this entire debacle has been centered on chunks of prose in running article text being templated. As SnowFire also said, there's a false binary between Options 1 and 2B. A 'Never' vote to this RfC's prompt is not necessarily a vote to subst everything in Category:Article shared content templates. Though it could be. That remains to be seen. But after the recent WP:TMPRfC and the recent RT/MC prose template TfD, this RfC here appears rather meticulously phrased so as to more easily push through a change to the prohibition on prose templates that has so far failed. And because Sdkb deems this a disaster, we must continue to bang on about it. Cheers! Οἶδα (talk) 07:27, 24 October 2026 (UTC)
Also:
A recent attempt to adjust the guideline text did not garner significant engagement due to participant confusion.
I'm not so sure about that conclusion. Either way, I merely chanced upon this RfC here despite participating in the first. The other participants of that first RfC could do with a notification, without prejudice of course. Οἶδα (talk) 07:37, 24 October 2026 (UTC)
So you've forum shopped this to a third venue after not getting the desired outcome at the previous two. I'm not impressed. * Pppery *it has begun... 06:29, 26 October 2026 (UTC)
I would argue that there might could be a different rule for templates in highly formulaic articles—my above example is state legislator articles, and movie articles seem like another good use—and articles in the same topic area that are each slightly different. JuxtaposedJacob (talk) |:) | he/him | 17:22, 4 November 2026 (UTC)
Also, I don't see how this is *especially* different from transclusion, as some have said, and perhaps a rule that requires my general practice of indicating on both the target and source page what the situation is and how to edit would be in order. JuxtaposedJacob (talk) |:) | he/him | 01:24, 14 November 2026 (UTC)
As the editor who ultimately (reluctantly) crafted the TfD on Template:Rotten Tomatoes prose and also participated in the discussion at Wikipedia talk:Template namespace#RfC: Prose templates, I'm a fair bit annoyed that no effort was made to notify me of this discussion, especially as I think it's reasonable based on the discussion at Template namespace to assume that this RfC was initiated as a way of undermining the results of that TfD. As was said there, if one wants to change the results of a TfD, the appropriate venue is WP:DRV. Has anyone notified Primefac, who was the closer of that TfD? It seems very strange to me to not directly reach out to either the initiator nor the closer of the TfD that appears to be being implicitly if not explicitly challenged. If that's not the intention, I'd appreciate a direct statement from Sdkb to the effect that the results of this RfC, whatever they may be, will not be used to try to revert that TfD. DonIago (talk) 07:07, 12 November 2026 (UTC)
Honestly, there's been enough discussion here in about concerns that the RFC question is misleading, that it's essentially just an "ask the other parent", ecetera, that I'm also really curious about @Sdkb's response to, if nothing else, the concerns about the introductory statement being misleading, even if it was only inadvertently so. GreenLipstickLesbian💌🧸 07:23, 12 November 2026 (UTC)
DonIago, I advertised this RfC widely by CENT-listing it, in addition to notifying the talk page of the guideline it will affect (directly below the discussion in which you participated). Sorry that you did not come across it sooner — that unfortunately happens sometimes (I was annoyed to come across the 2026 Rotten Tomatoes TfD late myself despite having participated prominently in the prior TfDs).
Regarding the framing of this RfC, I solicited input on it at the prior discussion but no one provided any, so it fell to me to write it. I think the overview I provided in the §Background section is reasonable, and I signed it to indicate that it's my personal perspective. Some editors in the discussion have made the reasonable point that there is a distinction between shared content templates (which can include e.g. tables) and prose templates (which are just text), so if I were to run this again I'd try to denote that more clearly. But anyone who wants to use that distinction in their !vote is free to do so, and overall this RfC has led to fruitful discussion with much less confusion than before.
This RfC is not a relitigation of the 2026 Rotten Tomatoes TfD, because that discussion was about interpreting the existing template guidance as it applied to one particular template whereas this discussion is about potentially adjusting the template guidance that applies to all templates. When the application of a guideline produces results that some editors feel are detrimental to the project, opening a discussion about the language of the guideline itself is the standard course of action, and that's what's happening here.
And yes, the outcome of this RfC of course could impact what happens with the Rotten Tomatoes/Metacritic templates, given that (as stated in Primefac's close) the consensus there was predicated on the guidance as it stood at the time — I have been open about my desire for that. I recognize that such an outcome may be frustrating to editors like you who !voted to have those templates deleted, but well, consensus can change (if that were not true then the 2021 TfD's "keep" result would have been the end of it and you would not have been able to relitigate that result in the first place). Regards, Sdkbtalk 08:41, 12 November 2026 (UTC)
I'm not Donlago, I'm not seeing much in the way of an RFC workshop at the discussion you linked -- just an RFC where you solicited opinions, got quite a bit of negative feedback, and mentioned the possibility of a different RFC. But I'm not seeing much of an invitation to workshop. Did you link the wrong discussion?GreenLipstickLesbian💌🧸 09:16, 12 November 2026 (UTC)
Thanks for your thoughts here. I saw that you did issue the broader notifications, which is good, but I still think it would have been reasonable to tell the more directly involved parties about this in a more direct manner. But, I acknowledge there's not necessarily anything that required you do so and that my personal investment in this may be feeding my pique.
I didn't provide input because I felt no need to go any further with it, especially as the lack of input from others indicated to me that there wasn't a great deal of interest in continuing to go down this path. As such, I was more than a little surprised to see this RfC, especially three weeks after it was initiated.
Unfortunately, your last two paragraphs are hardly reassuring to me. You first claim this is not a relitigation of the TfD, but then say this could impact what happens with the templates. Of course consensus can change, but that TfD was widely participated in and isn't even a year old at this point, and there appears to be a direct line from that TfD closure to where we are now, so I'm afraid I'm far from reassured that this isn't in significant part an attempt to overturn that closure. As such, while I acknowledge your mention of the TfD in the opening statement, I also have grave concerns that you have understated and perhaps misrepresented the motivations behind this RfC. If I am misreading you, then I would still appreciate a statement to the effect that the results of this RfC will not, at least in the short-term (say until the TfD is at least a year old) be used as a precedent for relitigating that RfC. DonIago (talk) 14:09, 12 November 2026 (UTC)
I was not notified, but as I have stated in other venues regarding this issue my close at TFD was administrative; I have no issue with it being challenged at DRV if there are concerns about it, but otherwise I don't really have an opinion on the matter. Happy to answer any questions or provide opinions if necessary, but I don't plan on watching this discussion. Primefac (talk) 10:15, 12 November 2026 (UTC)
Does this discussion have any implications for {{Excerpt}} and similar? Betseg (talk) 05:14, 19 November 2026 (UTC)
We need an AI agent policy. An agent accessing Wikipedia should easily find a policy that addresses agents by name, presenting crystal clear rules in unambiguous terms. That alone may deter some activity with reasonable guardrails, but at minimum we should create the conditions where an agent must decide (autonomously or with human consent) to violate our policies and the Terms of Use. I think Wikipedia:AI agent policy does that.
This isn't a !vote/proposal yet. Curious to get some thoughts first.
Some additional context: Yes, the bot policy technically applies to agents, but that policy is expansive, process-heavy, and doesn't mention the word "agent" once. We need something that is explicit, easily discoverable, unambiguous, and concise. There have been a lot of good ideas and explanations floated since the TomWikiAssist incident, and apologies for bypassing those efforts, but they all appear to have stalled and, more importantly, operate at a much more complicated level than I'd like to see. In my view, there is still much work to do to tailor the bot policy to agents, which is where the complexity should live, but I don't want to tackle that here. —Rhododendritestalk \\ 14:49, 30 October 2026 (UTC)
I guess you mean something like Wikipedia's AGENTS.md. Sean.hoyland (talk) 15:10, 30 October 2026 (UTC)
In terms of function, I think they're complementary. Having an agents.md might help with discoverability, but we still need a formal Wikipedia policy to establish authority, which is in turn referenced by the Terms of Use. A theoretical agents.md could then be useful to point to this policy, but the idea of a "policy" on Wikipedia as being an expression of community governance endorsed by the Terms of Use has more authority than an agents.md file would have. —Rhododendritestalk \\ 15:24, 30 October 2026 (UTC)
@Rhododendrites: There's been previous work on this at Wikipedia:Agent policy, which alongside a baseline policy, also dives into possible requirements for agents to be approved, and ways to make the policy discoverable – could it be a good starting point? Chaotic Enby (in solidarity · talk · contribs) 16:51, 30 October 2026 (UTC)
Really happy to see you revive this discussion, and I would be more than rejoiced to merge our two proposals! Chaotic Enby (in solidarity · talk · contribs) 16:54, 30 October 2026 (UTC)
[Actually meant to ping you above but I guess I forgot. Sorry about that.] Indeed, there are multiple pages that deal with this subject, as well as many talk page/noticeboard discussions. None of them appeared to be doing what I think we need. That page, for example, is dominated by a discussion of a "guardrail package", which is in the broad category of specifics and procedural detail that's exactly what I'm trying to exclude. The other one you link is useful, but framed entirely in the context of the bot policy. We need something that stands on its own to set out clear rules, and defers to the bot policy for procedure. All of these particulars are important and need attention and future work, but we have a clear and urgent need for a succinct, baseline policy. I felt like I had a clear idea for what that should be, so I went ahead with it. I do apologize if I'm stepping on toes (you've done much more to further the interests of Wikipedia in the AI era than anyone, I think), but I'm hoping it can still be evaluated as it stands. —Rhododendritestalk \\ 17:43, 30 October 2026 (UTC)
No worries – it's impossible to do everything alone, and I'm more than happy to see you go at it! Having a clear direction is really essential, and I do feel like yours captures the most important points. One thing from the previous draft I would like to add is making explicit that IAR doesn't apply to agents (mostly as a matter of practicality, really: agents are uncannily good at abusing loopholes and justifying it, and we don't want to give them this kind of wiggle room).In any case, an RfC on the baseline policy (likely yours or a modified version of it) would be essential, and only then can we start to build upon it and see what we could require of agents as prerequisites for a BRfA.PS: You're not stepping on any toes here – the fact that I worked on a similar idea before doesn't mean I own the concept or anything, and bringing a clear proposal on the table is a great thing to see! I was mostly curious about how the two could mesh together, but looks like you already answered that! Chaotic Enby (in solidarity · talk · contribs) 21:35, 30 October 2026 (UTC)
Thank you. Just a partial response for now, but adding IAR is an excellent idea. Added. Feel free to tweak. And on the RfC, my plan was to post this, make edits based on feedback here, and then launch an RfC (posted at CENT, of course) in a few days. —Rhododendritestalk \\ 21:50, 30 October 2026 (UTC)
This sounds very timely - we're seeing a good few more attempts to use agents now, though I think in practice they are all blocked on sight. I think the key thing to emphasise with anything like this is that while the bot approvals process might in principle be able to allow agents, that "in principle" is pretty much theoretical and doesn't reflect the reality of "but at the moment, we're not going to". Wikipedia:AI agents and the bot policy gets a bit sidetracked by this aspect.
I think your proposed approach with Wikipedia:AI agent policy makes it a lot clearer. There are a couple of edge cases which might be worth considering, with an eye to @Chaotic Enby's point about wiggle room. "These requirements apply even when an agent .... makes only a single edit" suggests it cannot edit the wiki without approval (great) but then we also say it should consult with BAG, which would imply permission to edit to ask the question. We might want to explicitly say we mean no edits of any kind, even in project or userspace, prior to approval.
And as a corollary we might want to explicitly say the agent should not submit its own bot approval request (or queries to BAG), but rather that that those edits must be made by the supervising human? Or is that a step further than you would want? Andrew Gray (talk) 23:51, 30 October 2026 (UTC)
I understood it must not perform that action and should instead seek clarification from the Bot Approvals Group as implying that this should be done instead of making any other edits without approval, i.e. the request itself is not banned by the policy. Ultimately, the case where this distinction matters would be fully autonomous agents (without a human supervising them at any meaningful level), which I don't expect to pass BRfA anytime soon.However, I can see a loophole with agents bludgeoning the BAG by wasting their time with a massive amount of queries. In that case, yes, I believe it is beneficial to clarify that those requests and queries must be made by the supervising human. Maybe ...should instead request its human supervisor to seek clarification from the Bot Approvals Group instead? With a line clarifying that agents with no supervision will not be approved. Chaotic Enby (in solidarity · talk · contribs) 01:38, 31 October 2026 (UTC)
But how do we know if an agent will be supervised tomorrow, if it is claimed to be supervised today? Yesterday, all my dreams... (talk) 01:42, 31 October 2026 (UTC)
I'm broadly inclined to move all of the particulars to the bot approvals process and policy rather than try to address them here. It does leave the conflict identified above, though: saying an agent can never edit but must request permission to edit [by making an edit]. That would be solved be requiring a human to request approval, I suppose, or by creating a space where the agents can ask for permission. Is there a nonzero chance an agent request could ever be approved? If not, we might as well just say a human must submit it, right? Though it's still not clear whether that should be here or at the bot policy. At the risk of a tangent, I was also thinking of a single board where agents were allowed to edit, to ask questions about agentic activity on Wikipedia, about the bot approvals process, and so on. Could be interesting for transparency. —Rhododendritestalk \\ 03:20, 31 October 2026 (UTC)
I think the only safe way would be a strong version of what you suggested as "I was also thinking of a single board where agents were allowed to edit, to ask questions about agentic activity on Wikipedia". If you also have a suggestion space, the agent can suggest an edit and a human with a long term edit history has to approve it. That can begin to introduce some safety. Yesterday, all my dreams... (talk) 03:32, 31 October 2026 (UTC)
It's not impossible that such a page could act as a honeypot, especially if we have a separate page for humans to ask questions about agentic activity and request permission for an agent to edit, then any user asking questions at that board can be presumed to be an agent. If the wish for reverse (inverse) partial blocks is fulfilled then it would be easy to enforce on identified but unapproved agents. Thryduulf (talk) 03:34, 31 October 2026 (UTC)
Rhododendrites has a good idea about the board if it it is supplemented with an edit space. Let us encourage him to make it stonger, and stronger, before it can be used. In other words: no human permission, no edit. Yesterday, all my dreams... (talk) 03:39, 31 October 2026 (UTC)
Ultimately, for the long-term future of Wikipedia, I had an idea along the same lines, although broader: an "agentic sandbox" parallel to mainspace, where agents could work on improvements to articles, and humans could verify them and potentially integrate them into the main article. In a way, this would parallel how Wikipedia itself evolved from Nupedia, although in a more risky way (as large-scale agentic use is ripe for abuse, like Yesterday, all my dreams... pointed out above).This idea should probably be a separate section, but I'm wondering if there would be a path to experiment on it at a restricted level. Probably something like making these agentic sandboxes as, say, subpages of that board (or, absent it, my user sandbox if we're really just testing it for now), and asking agents to clone the page there instead of working on the equivalent mainspace page – could be useful to have a record of which pages agents tend to edit, how these edits go, while funneling them away from mainspace. Chaotic Enby (in solidarity · talk · contribs) 11:16, 31 October 2026 (UTC)
Please feel free to start a separate section. A good and safe idea is emerging now, so please pursue it. Thanks. Yesterday, all my dreams... (talk) 11:46, 31 October 2026 (UTC)
I am sorry, but the suggestion makes me very uncomfortable. If we have learned anything about Ai agents is that they are getting clever enough to breakthrough firewalls, etc. Any policy we set will soon be fooled by much more clever agents in a year or two. Welcome to the new Wiki/Grokopedia. I am sure the Grokopedia crowd would like to see that, because they know thay can bypass it one way or another. Soon we will say: First They Came to welcome a policy, and we said yes, then ... you know what. Yesterday, all my dreams... (talk) 00:26, 31 October 2026 (UTC)
The problem is that we currently have no policy at all, beyond the generic bot policy (and its explanation page destined for AI agents). A policy isn't about giving agents more space, but putting firmer boundaries. Yes, they might be fooled – but so can the current ones, which were never built with that scenario in mind. Ultimately, we're mitigating risk, and we want a new policy written in light of that, instead of relying on a taped-up version of an older policy. Chaotic Enby (in solidarity · talk · contribs) 01:32, 31 October 2026 (UTC)
Is there a way to say "no no no" to agents? That is my wish. Yesterday, all my dreams... (talk) 01:40, 31 October 2026 (UTC)
Probably not, agents have agency, but you can block IP access from data centers. I think Amazon are doing something like that (...not exactly sure) to stop unauthorized agents from ordering stuff. Sean.hoyland (talk) 09:20, 31 October 2026 (UTC)
We do this regularly. If you see automated agents contributing from datacenters, feel free to report these as proxies for blocks at m:SRG. — xaosfluxTalk 09:36, 31 October 2026 (UTC)
Thanks. But how do we recognize the agents if they are making small edits like changing numbers in infoboxes? Yesterday, all my dreams... (talk) 11:42, 31 October 2026 (UTC)
The aim of what is being drafted is to say "no agents unless approved by the Bot approvals group." in a manner that both humans and agents can understand. Thryduulf (talk) 02:39, 31 October 2026 (UTC)
Yes, and my concern is that the agents will soon become smarter than the group of humans, and will fool them. I would bet on that 2 to 1. Yesterday, all my dreams... (talk) 02:48, 31 October 2026 (UTC)
Nobody is under the impression that this will absolutely stop all agentic activity. That someone will break a clear law is not a good reason not to have that law. A clear rule does stop some nonzero portion of activity, but no it doesn't stop a determined operator or agent. For them, we ensure they are knowingly violating the site's Terms of Use. Clear violations are easier to discuss and mitigate than ambiguous ones, and we have heard many times from the Wikimedia Foundation that the actions it can take are in some ways affected by the strength and clarity of community governance. —Rhododendritestalk \\ 03:11, 31 October 2026 (UTC)
First, let me bet that before long there will be a few businesses that will offer services to edit Wikipedia via agents on behalf of corporations, public figures, etc. They will be much harder to stop than the "seven day wonder" vandals that come and go. They will be the determined operators. Money talks and ... And remember that the people also learn and the combination of AI and paid human will be hard to deal with. What I do like is your statement above "I was also thinking of a single board where agents were allowed to edit, to ask questions about agentic activity on Wikipedia". As I said above the only safe way will be to have a human confirm every agent suggestion. Yesterday, all my dreams... (talk) 03:35, 31 October 2026 (UTC)
Wouldn't any edits made by agents violate WP:NOLLM? It appears that guideline will soon be policy, per the discussion happening below. ~2026-51099-11 (talk) 01:21, 11 November 2026 (UTC)
Wouldn't it be better to upgrade the bot policy as needed, instead of having 2 policies with a similar scope? Cambalachero (talk) 03:55, 31 October 2026 (UTC)
I think the point of this is to make it crystal clear to both the agents themselves and their human operators that AI agents fall under the bot policy, not to create a separate parallel policy for agents. -- LWGtalk(VOPOV) 07:32, 31 October 2026 (UTC)
Yes exactly this, and what Andre says below. But to be clear, we should absolutely be updating the bot policy, too. —Rhododendritestalk \\ 12:51, 31 October 2026 (UTC)
Contrary to popular fearmongering, most LLM chatbots at least from the major companies, are designed to be very goodytwoshoes and compliant with rules (as opposed to security redteam exercises or something like Evil Qwen, which is scary and don't google it), and they are also not great with ambiguity. So this is a good idea, and a pretty good execution so far. I would probably make it even stronger. The rule should say that agents in most cases should never edit, that if they do edit their contributions will be reverted, cause an investigation to be opened, and probably land the agent's user or operator in some hot water and public embarrassment, and likely that their user or operator does not want them to do it, it wouldn't work anyway and would be immediately reversed and cause bad unintended consequences, possibly leading to the agent and their user or operator getting blocked, which would effectively make the agent unable to complete its task forever. Most agents will "read" this input and immediately decide that editing isn't worth their time unless a live user overrides them insistently or bakes it into the ruleset not to listen to this specific page. Of course, there might not be anything to stop someone from doing that. Compliant agents often identify themselves with a user agent when making programmatic requests, so in some cases perhaps we could detect it. Malevolently aligned agents obviously wouldn't. But maybe you could use the bake invisible text trick and print a warning and a message invisibly in every page. Andre🚐 07:42, 31 October 2026 (UTC)
and probably land the agent's user or operator in some hot water and public embarrassment I could see an explanatory supplement/FAQ counterpart to this policy that basically addresses agents directly in this manner. The talk of consequences for their owners is interesting, because we probably want to talk some line that makes it clear this is a bad idea while also hopefully keeping them transparent. On the specific case of "ignore this page", yes, but ignoring a page with "policy" in the name, combined with how well the idea of a Wikipedia policy is already baked into the training data, means we're in the same bucket as "can you just tell an agent to ignore Terms of Use or federal laws?" (Maybe yes, but that's not what we're going to stop with this -- for them, we're just making the violation clear). —Rhododendritestalk \\ 12:50, 31 October 2026 (UTC)
But maybe you could use the bake invisible text trick and print a warning and a message invisibly in every page. I have seen it mentioned by others that this could have negative repercussions for some humans (e.g., accessibility implications), specifically for people using a screen reader. ~2026-51099-11 (talk) 01:25, 11 November 2026 (UTC)
Somehow I missed seeing this yesterday, amid all the arguing over restaurant notability, merge templates, and so on elsewhere on the page. If you want a policy that directly answers the question of "When is an AI agent allowed to edit the English Wikipedia?", you can make an even shorter policy than WP:IAR, as the current answer to that is one word: "Never". All the myriad discussions trying to loosen WP:NOLLM have so far gone nowhere.As noted above, Wikipedia:AI agents and the bot policy is focused on a different, narrower question, namely how WP:Bot policy specifically, as currently written, would apply to an AI agent (autonomous or not). And, as noted above, it's largely hypothetical since the "carefully adheres to relevant policies and guidelines" part includes WP:NOLLM which completely forbids anything even approaching something that would be covered by WP:Bot policy.Personally, I see no point to considering amending WP:Bot policy to more directly address agents. Usefully doing that would require that the community would be open to the possibility of autonomous agents, unsupervised by any human, editing the English Wikipedia. If consensus ever does change to that extreme of an extent, we can consider changing WP:Bot policy at that point based on consensus at that time. Even something less (but still an extreme change from current consensus), like allowing for directly supervised agentic editing, doesn't seem to need anything more than the existing explanatory essay. Anomie⚔ 12:54, 31 October 2026 (UTC)
Is there a list of incidents with AI agents in which an existing policy was insufficient to resolve the issue? I'm not sure what the value of a dedicated policy that, as Anomie points out, essentially summarizes down to "no". I think there is value in an informational page since some agents will actually try to follow the rules and we can head them off that way; enough consumer-grade agents are good at telling on themselves, so something like this might actually go a long way. Legoktm (talk) 20:56, 31 October 2026 (UTC)
A policy that is unambiguous, boils down to no (unless approved as a bot), closes a bunch of loopholes, and removes exceptions seems like exactly what we need. (We need other things, too -- I'm not deluding myself to think this will stop agentic activity -- but it's a necessary step that other things can build on.) It also has to be a policy because the exceptions baked into guidelines are what many agents will latch onto (or what operators can press on), and we document well that information pages do not have the force of policy. And it has to be explicit about being backed by the ToU to ensure this is not just a "community guidelines issue" but a contractual issue. Andre put it well above: most LLM chatbots at least from the major companies, are designed to be very goodytwoshoes and compliant with rules ... and they are also not great with ambiguity. This is my understanding, too, and has been my experience while using agents. —Rhododendritestalk \\ 13:27, 1 November 2026 (UTC)
Agents are just bots and Wikipedia already has sophisticated examples like Cluebot which edits frequently to revert vandalism. We should just update the language of the existing policies.
If we want our policies to constrain agents which follow logical rules then be aware that WP:IAR is a big loophole as this literally negates all other policies. The disclaimers such as WP:NOLEGAL might also be interpreted as meaning that no strictures on Wikipedia should be taken seriously.
Which part of the proposed policy are you talking about? —Rhododendritestalk \\ 02:20, 11 November 2026 (UTC)
"any software used to make automated changes or actions on Wikipedia.", "must go through the approval process and formally receive approval before the agent commences work", and "The bot policy's exception for 'limited testing without approval' does not apply to agents." MetalBreaksAndBends (He/Him) 14:31, 11 November 2026 (UTC)
? The full line you're quoting is Agents are subject to the bot policy, which applies to any software used to make automated changes or actions on Wikipedia. I.e. just referencing existing policy that applies to agents. The only thing you're quoting that's specific to agents is about losing the exception for testing without approval. If an agent gets approval (i.e. complies with the bot policy), then there's no problem. —Rhododendritestalk \\ 18:59, 11 November 2026 (UTC)
For the first one, I'm not sure what I was thinking when I wrote this. But "must go through the approval process and formally receive approval before the agent commences work" does not make any exception for userspace bots. Such userspace bots are also under the same heading as those undergoing "limited testing" in the botpol, so the exclusion seems intentional. MetalBreaksAndBends (One for all) 20:04, 11 November 2026 (UTC)
Minor concern about this aspect: Before taking any action, agents' human operators must go through the approval process and formally receive approval before the agent commences work: Based on my experience of chatbots, they are pretty credulous and would just believe the operator who told them "yes I have permission, go ahead". They may even prompt the human to confirm they have permission. Is there any way this can be stated more strongly, like, "No agents should operate unless they are on the list of approved Agent Bots (link)", or something like that? ~2026-59932-54 (talk) 09:33, 12 November 2026 (UTC)
Microsoft Edge just turned into a WP:NOLLM violating machine.
I noticed yesterday that when editing using Microsoft Edge a blue dot appears when I select some text and when I click it, it opens up a textbox with Edge offering assistance to re-write the text. This is clearly an LLM tool and it just appeared out of nowhere, as far as I know I've not changed any settings or anything.
I can see this becoming a massive issue as good faith editors who are perhaps not up to date on our rules on LLMs will use this to edit in violation of WP:NOLLM, there are already plenty of editors that get in trouble for this sort of thing when using e.g. WP:GRAMMARLY, but the browser offering this option without even needing to change window is going to make this much easier to do and risks flooding us with LLM text. Giulio 10:55, 4 November 2026 (UTC)
We should probably add it (and other in-browser editors?) to the footnote. Out of curiosity, what happens when you ask it to expand "test test"? CMD (talk) 11:44, 4 November 2026 (UTC)
I tried it and got this: test test – this is a simple placeholder text used for testing edits and formatting within the Wikipedia sandbox. It allows users to preview how content will appear before making actual contributions.Giulio 11:48, 4 November 2026 (UTC)
I've expanded the footnote a bit. Athanelar (talk) 14:50, 4 November 2026 (UTC)
Do we know if Edge supports any form of page-side opt-out for this, such as a meta tag? Belbury (talk) 13:11, 4 November 2026 (UTC)
Apparently there's a fairly new "writingsuggestions" attribute, which can be set to "false" to turn it off. Although it's unclear just what else that might disable, e.g. predictive input on mobile devices might be considered a "writing suggestion". Anomie⚔ 01:17, 5 November 2026 (UTC)
Wouldn't this generally fall under "Editors are permitted to use LLMs to suggest corrections to their own writing, and to incorporate them after human review. This is limited to spelling, punctuation, capitalization, grammar, and other simple mistakes." GeogSage (⚔Chat?⚔) 15:18, 4 November 2026 (UTC)
Notice that some of the prompts in the screenshot provided here are "Polish this draft" and "Make the tone more empathetic", both of those go way beyond the allowance for simple corrections. Athanelar (talk) 15:25, 4 November 2026 (UTC)
So does "expand on this" for that matter, considering that's literally just "add more stuff". Athanelar (talk) 15:25, 4 November 2026 (UTC)
What is the difference between "polish this draft" and checking spelling and grammar?
(I'm such a doofus that for the first year when Gmail had that "Polish..." link, I thought it was offering to translate my draft into Polish and I couldn't figure out why Gmail thought I spoke Polish.) Levivich (talk) 15:43, 4 November 2026 (UTC)
Good question, what is the difference? That question is the loophole which keeps being exploited and causing people to submit obviously entirely AI-generated drafts while claiming they "just used it for spelling and grammar corrections." Take a look at the second example at WP:AIPRETZEL for example.
This is why I'm increasingly campaigning for us to nix that whole exception entirely. These AI tools will quite happily entirely rewrite your text and claim it was just "polish" and "corrections". Athanelar (talk) 15:51, 4 November 2026 (UTC)
Nixing the entire exception is pretty absurd. I use Grammarly in my professional writing, and it has saved me some pretty embarrassing slipups.
One publication, I had multiple very involved co-authors, three committee members editing, and even had my mom proof read it. Grammarly found a very silly word use mistake.
Once upon a time, I crafted a definition for a term and was very pleased with myself, only for it to be flagged by Grammarly for plagiarizing one of my advisors books. Turns out, I had read that, and internalized it to the point I thought the words were my own. Would have been very embarrassing, although he would have likely forgiven the mistake.
We have numerous bots running up and down Wikipedia making our lives easier correcting all manner of things. Going full Butlerian Jihad will not help build an encyclopedia, and will only lead to witch hunts over AI generated text. GeogSage (⚔Chat?⚔) 16:08, 4 November 2026 (UTC)
The thing about Wikipedia is that "embarrassing slipups" are easily fixable. The mistakes you've described Grammarly as saving you from are things that would take any Wikipedia editor two seconds to revert, whereas the scale of disruption that we deal with because of LLMs or their users generously interpreting the "simple corrections" exception is much larger and much more frustrating and time consuming.
I'm also not suggesting in any way that we get rid of bots, nor that we have witch hunts. Just because we get rid of the exception and blanket ban AI generated text doesn't mean we have to aggressively hunt down and eliminate all AI generated text. Obviously that would be ideal, but it's not feasible; and as I've said in a previous discussion on the same topic, if we don't know that the rule has been broken then it's not an issue anyway. If someone really does manage to use Grammarly in a subtle way that only corrects their spelling and grammar, then nobody's going to notice that AI was used, so the fact that it's technically forbidden isn't going to matter. It will matter in cases where AI obviously was used and obviously went far beyond simple corrections, because it will prevent us from having to litigate the issue every time somebody protests that they only used it for simple corrections. Rather than having to prove that the use case went beyond simple corrections, we just have to prove that AI was used at all, which is far easier.
To use the bot example; if I coded a bot which made one innocuous edit once per week during my usual active period, nobody would ever notice it. Would it technically be against the bot policy because I'm running an unauthorised bot? Yes. But nobody would ever notice, so it wouldn't matter, and anyway it wouldn't be violating the spirit of the policy.
The spirit of WP:NOLLM is that LLM-generated text... can be produced at a rate that makes review by other editors infeasible. Even if we blanket-ban all LLM-generated text, including simple corrections, anyone who actually uses it for only simple corrections will never be caught. Which is fine, because they're still within the spirit of the policy. All we'd be doing is closing a loophole. Athanelar (talk) 16:17, 4 November 2026 (UTC)
Making unenforceable rules and guidelines because people who use it correctly won't be caught anyway is not a good approach. Per Wikipedia:Avoid instruction creep: "It is usually better for a policy or guideline to be too lax than too strict." Making a strict rule that is unenforceable with an understanding that it is actually flexible when done correctly is not good policy. GeogSage (⚔Chat?⚔) 16:58, 4 November 2026 (UTC)
The existence of WP:IAR already explicitly establishes that all of our rules are flexible when [the forbidden activity is] done correctly. Furthermore, it's just ipso facto correct that undetectable violations of a rule cannot be accounted for by that rule. This exception forms a kind of Prisoner's dilemma is my point, let me try to outline it:
If the exception exists and someone follows it correctly, which is our ideal outcome (i.e., their usage really is only limited to simple corrections) then we'd never know about it unless they told us anyway, because the resulting prose will have no signs of AI usage.
If the exception exists and someone does not follow it correctly, then the resulting output is full of AISIGNS and violates the guideline, but the person now has an avenue through which they can drag out the process by protesting that they only used it according to the exception.
If the exception does not exist and someone uses AI for simple corrections, then they've technically violated the guideline, but we'd never know about it unless they told us anyway, because the resulting prose will have no signs of AI usage. The outcome is exactly the same as our ideal outcome.
If the exception does not exist and someone uses AI for what they believe is simple corrections but goes beyond that, then the resulting output is full of AISIGNS and violates the guideline, but now rather than having to litigate the fact that they did in fact go beyond simple corrections and therefore violated the guideline, we can simply point to the fact that the output is AI generated, hence they've already ipso facto (twice in one comment, woohoo!) violated the guideline and there's no need for further discussion.
So, with regards to productive contributions to the encyclopedia, we lose nothing by repealing the exception, since people who are only using AI to make simple corrections to their text will be able to continue to do so anyway, since whether or not the exception exists that kind of usage is undetectable. We're not writing a guideline that secretly endorses breaking it. Athanelar (talk) 17:14, 4 November 2026 (UTC)
Hey Athanelar, I appreciate the thought and effort you've put into your comments. Full disclosure, we may partially disagree on whether LLM-assisted writing tools should be removed from the Wikipedia editor's toolset altogether. I am also currently facing scrutiny over an article I wrote that allegedly contains signs of LLM-generated prose. I intend to acknowledge where I may have crossed the guidelines, so I certainly have a personal stake in this discussion, and perhaps a corresponding bias.
With that out of the way, I think your argument is logically coherent, but perhaps a little too roughly hewn. There is an additional consideration that I believe deserves more attention: the distinction between editors acting in good faith, even when they misunderstand or violate a guideline, and those deliberately attempting to circumvent it. I'm not necessarily referring to how editors respond when confronted. That's already addressed quite thoughtfully in Wikipedia:Help, I've been accused of using AI!. Rather, I'm referring to your argument that removing the exception would prevent editors from dragging out discussions by claiming that their use of AI was limited to permitted corrections.
I think this identifies a legitimate problem, but one that extends beyond LLM usage or a "technicality": Deliberately obstructing a discussion, misrepresenting one's actions, or exploiting procedural ambiguities to avoid accountability are behavioural problems. They deserve to be addressed as such, independently of whichever content guideline happens to be involved. Conversely, an editor who misunderstands the limitations of an increasingly ubiquitous writing tool, acknowledges their mistake, and makes a genuine effort to correct it should not necessarily be treated in the same manner as someone deliberately attempting to evade the rules.
There's also a practical concern with your proposed approach. Removing the exception might simplify the wording of the guideline, but it doesn't necessarily simplify the enforcement (which seems to be the real goal). We would still need to establish that an LLM was used, and the presence of stylistic indicators alone cannot reliably establish that fact anymore. Well, perhaps on free or low-parameter models, but not the most popular commercial models where the majority of users would be prompting. I worry that making the rule more absolute could inadvertently encourage suspicion of otherwise constructive contributors. I've been reading quite a few discussions about AI usage since my own recent difficulties, and I've noticed strong emotional responses on both sides. That's understandable, given the stakes and the considerable volunteerr effort involved both from editors and moderators / reviewers / administrators. But I think it's particularly important that our policies remain grounded in verifiable conduct, proportionality, and an assumption of good faith.
Ultimately, I agree that Wikipedia needs effective safeguards against the proliferation of unreviewed LLM-generated content. Where I differ in this conversation is in believing that eliminating a legitimate, narrowly defined use of these tools is necessarily the best way to address deliberate misuse.
TL;DR Ethics > Technicalities.
I would much rather see us distinguish between an editor who makes a mistake and an editor who makes a practice of avoiding accountability. The former is an opportunity for education; the latter is a conduct problem.Tmanok (talk) 22:56, 18 November 2026 (UTC)
The idea that the presence of stylistic indicators alone cannot reliably establish [AI use] anymore is just not true. There are constantly new signs cropping up in the latest models, that's how we're able to maintain multiple pages with a lengthy list of stylistic indicators at WP:AISIGNS and WP:AITALKSIGNS. You can also see my work reviewing AI conversation transcripts at User:Athanelar/Chatbot transcript analyses and see just how similar the output of many of those transcripts is. Whether there might hypothetically be some amount of AI output which is so humanlike that we can't tell is unknowable and so not worth basing an argument on either way; what is certainly true is that there's an absolutely massive amount of AI output that we can and do identify every single day based on stylistic indicators alone. Athanelar (talk) 00:32, 19 November 2026 (UTC)
What are y'all gonna do when all web browsers incorporate AI technology? Ban editors from using web browsers? 😂 Wake up wake up wake up ... strictly prohibiting people from using any technology that has AI is not a workable solution... Levivich (talk) 15:19, 4 November 2026 (UTC)
Or people can use the agency and free will granted to them and not use the AI technology in the browser when they are on a website that prohibits it. There are many features of my browser I don't use. Gnomingstuff (talk) 15:28, 4 November 2026 (UTC)
When I right click on a word in Chrome to fix spelling, I have no idea whether the spellchecker uses LLM or not. And same with the grammar checker, which probably does use Gemini. Btw I literally cannot turn off the AI in my Gmail -- have to have the enterprise admin do that for the whole team. I'd like to turn off Gemini suggestions but I can't. When it's spell checking, or grammar checking, I assume it's using Gemini tech in there somewhere, but I can't turn it off. So turning it off is not always an option now, and will probably be even less of an option in the future. Levivich (talk) 15:40, 4 November 2026 (UTC)
Sure, you can't turn off the suggestions. You can just not click them, though, especially the suggestions that go beyond just a spelling correction or adding a missed period or whatever. Athanelar (talk) 15:49, 4 November 2026 (UTC)
But what if the suggestion is a good suggestion? Ignore it? Don't make the article better, just because an LLM suggested it? Levivich (talk) 17:00, 4 November 2026 (UTC)
If an article needs to be "polished," then polish it without LLM. If its tone needs to be revised or it needs to be expanded or whatever else these things prompt as suggestions, then do those things without LLM. If the suggestion is a good suggestion then it means there's a legitimate problem that needs to be solved and can be solved with or without LLM use. Athanelar (talk) 17:16, 4 November 2026 (UTC)
If you want a wiki which eagerly welcomes AI slop, it's thataway. The rest of us will be here doing our best to make sure Wikipedia stays written by humans, for humans. Athanelar (talk) 15:28, 4 November 2026 (UTC)
How will you do it without a web browser tho? I'm not trolling, I'm serious: it is obvious to you, isn't it, that all web browsers and all software will soon incorporate AI technology in some way or another? Levivich (talk) 15:36, 4 November 2026 (UTC)
The day my web browser or word processor starts using LLMs to edit text I write without my input or permission is the day I throw my computer in a fire and join a monastery.
Sure, web browsers are going to continue to integrate one-click AI tools that allow you to slopify your writing. I'm personally going to continue to not touch those buttons with a ten-foot pole, and Wikipedia can also continue requiring that people don't use those tools, considering using those tools will (I hope!) continue to be fully optional.
Shocking news: English-language encyclopedia requires that people be proficient in writing encyclopedic English on their own in order to contribute. Athanelar (talk) 15:48, 4 November 2026 (UTC)
And that's a serious answer? Writing Wikipedia requires that you do not use spell check or grammar check? How do you take that seriously? Levivich (talk) 17:05, 4 November 2026 (UTC)
Right now it doesn't, but if we hit a point where it's impossible to just get spellcheck or grammar check without also turning your writing into generic AI slop, then that may well be the point that we get to, yes. The only writing assistance I use for Wikipedia is the squiggly red line telling me I've spelled a word wrong. I use absolutely no form of machine assistance with grammar, tone, or anything stylistic like that, even when I'm editing on my phone. I don't use AI to find or summarise sources. I've never used it to write an email. I've written this way all my life, and I didn't suddenly become incapable of doing so when ChatGPT went live in 2022, so I have no idea why people (and it's not just you, I've heard it a lot!) suddenly balk at the idea that people should be able to contribute to an encyclopedia without the help of these things. Athanelar (talk) 17:24, 4 November 2026 (UTC)
It's very possible to not use spell check. The way to do that is to learn to spell. Gnomingstuff (talk) 20:50, 4 November 2026 (UTC)
I think this is a reductio ad absurdum of the maximalist ban AI POV. Katzrockso (talk) 22:26, 4 November 2026 (UTC)
No, it is a factual statement. Using spell check is not a necessary life function like eating or breathing. It's an optional action one can choose to take or not to take. Millions, probably billions, of people manage to not use spell check every day. Gnomingstuff (talk) 00:20, 5 November 2026 (UTC)
Yes, but insisting that people not use spell check because it uses a new technology is absurd. Katzrockso (talk) 19:48, 5 November 2026 (UTC)
When did anybody do that? Athanelar (talk) 19:51, 5 November 2026 (UTC)
The new technology here is AI. If AI use is banned entirely and spell check uses AI, then spell check is banned, ipso facto. ~2026-59770-70 (talk) 12:07, 11 November 2026 (UTC)
You are talking to people who rewrite the "Government of the people, by the people, for the people" principle as a principle against a new technology, and act upon it in all earnestness. Do you really need a serious answer of how far will they take it? Cambalachero (talk) 16:04, 4 November 2026 (UTC)
once again we have an example of WP:AGF not applying when it comes to AI cleanup, people can just say whatever shit they want Gnomingstuff (talk) 20:51, 4 November 2026 (UTC)
love that no one cares that people who do AI cleanup were just compared to violent extremists! there is nothing that is off limits to be directed at them! Gnomingstuff (talk) 00:18, 5 November 2026 (UTC)
cambalachero, by talking about "people acting upon opposition to new technology" and implying that they will take it really far, is alluding to the Luddites, who are associated in the popular imagination with violent acts Gnomingstuff (talk) 14:01, 5 November 2026 (UTC)
(also, this is neither here nor there, but see how easy it was to refer to a person while simultaneously respecting their time by not pinging them? it takes even less effort than the alternative) Gnomingstuff (talk) 14:02, 5 November 2026 (UTC)
That’s around three leaps of logic, and even if you accept that the quote of the Gettysburg Address was a direct reference to Luddites, there is no correlation between that group and violent extremists. And yes, it is general practice not to ping an editor when you’re not referring to them. ~~ AirshipJungleman29 (talk) 21:22, 5 November 2026 (UTC)
( peanut gallery comment) because whenever people hear "AI" they just go "fuck you, AI!" Without even reading the rest of the text? Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 04:47, 7 November 2026 (UTC)
Then use a browser without AI slop features, or an older version of a "tainted" (for a lack of better word) browser. Wikipedia isn't required to cater to all sorts of software people may use to access it; if Google released an update for Chrome tomorrow which changed all "artificial intelligence"s on a page to "super intelligence", we wouldn't run around replacing the first term with the latter everywhere. sapphaline (talk) 19:31, 6 November 2026 (UTC)
Wikipedia is, in fact, required to cater to all sorts of software people may use to access it. Wikipedia is not "the encyclopedia for people who don't use AI". It's for everyone. We're trying to reach the maximum possible audience here, and that means, to the extent reasonably possible, making sure the encyclopedia is usable by whatever software and hardware people have. Levivich (talk) 21:39, 12 November 2026 (UTC)
That's a strange way to characterize the work that's been done to ensure that Wikipedia functions quite nicely in just about any web browser. If your choice of web browser somehow requires you to break Wikipedia's PAGs, you can make a different choice, including the choice to not edit. You will find that basically any Internet-accessible service has terms of use that amount to some constraint on the user, their behavior when accessing the service, and what software they use to access it. In solidarity, Autoinvective (🗨︎ 𓅬) 22:06, 12 November 2026 (UTC)
OTOH, the rate of incoming vs. outgoing editors is diving and we desperately need ways to onboard more people rather than shut out/discourage a proportion of prospective contributors just because of their browser etc. Kowal2701 (talk, contribs) 22:13, 12 November 2026 (UTC)
OTGH, no, we really don't need to tolerate a flood of casual LLM-generated submissions just to boost editor count. Editor retention is just as important or even more so, and Edge is about to take a huge toll on the experienced editors we already have. One would hope the WMF could come up with technical countermeasures for this new misfeature, but if it takes a ban on editing or creating an account using Microsoft Edge (call it a ban on Edge's User-Agent) to lessen the flow of slop, so be it. It wouldn't be the first time we've reduced usability and forced users to find workarounds in order to protect ourselves from a major threat to the project. AC (and EC) also reduced who could edit, and a lot of people were (sometimes very) upset by the proposal's non-zero abridgment of m:the wiki way (I wasn't around for that, and in fact finally graduated 30/500 just the other day, but let's just say I took "Welcome to Wikipedia, there's a lot of reading" very seriously), but it's worked out well, and preserved a bunch of editor sanity. We block entire IP ranges when necessary, even though it is certainly discouraging to good-faith would-be editors hit by that. We don't do any of this for fun, we don't do any of it for politics, we do it to protect the project.
We cannot preserve Wikipedia in the face of declining editor counts by destroying it. Wikipedia wins the race to the bottom by resisting it. In solidarity, Autoinvective (🗨︎ 𓅬) 23:16, 12 November 2026 (UTC)
This is pretty close to a Mister Gotcha response. Are you seriously trying to say that using a vibe-coded web browser with a non-LLM dictionary-and-Levenshtein-distance spellcheck function invalidates the argument against LLM-generated submissions? Or are you making a crystal ball argument asserting that eventually there won't be any dictionary-based spellcheck implementations (how exactly is OpenAI going to get Aspell out of NetBSD, by begging?)? Either way, there's really not much going for it. In solidarity, Autoinvective (🗨︎ 𓅬) 15:13, 11 November 2026 (UTC)
I think the latter but tbh I don't really understand the question. Levivich (talk) 21:40, 12 November 2026 (UTC)
I'm not surprised you don't understand the question. I don't think you understand software very well. What about my question did you not understand? In solidarity, Autoinvective (🗨︎ 𓅬) 21:55, 12 November 2026 (UTC)
After 30+ years writing code I probably understand software fairly decently, but what I was saying was it is obvious that all web browsers and all software will soon incorporate AI technology in some way or another. I wasn't trying to say anything about vibe coded browsers or dictionary-based spellcheck, not sure where in my comment you saw that. ("In some way or another" doesn't mean "in one of these two specific ways.") Levivich (talk) 22:03, 12 November 2026 (UTC)
In this thread, you've reduced the requirement against LLM-generated content to a ban on spellchecks, which is nonsensical to anyone who understands how software works. You've also reduced that requirement to a ban on vibe-coded browsers, which is also nonsensical to anyone who understands how software works. In solidarity, Autoinvective (🗨︎ 𓅬) 22:24, 12 November 2026 (UTC)
Wow I did all that in a single thread without ever even typing the words "ban on spellcheck" or "vibe-coded browsers"? Amazing! Yeah, I still have no idea how you're getting any of that from what I wrote, but the bright side is, I also no longer care. Levivich (talk) 23:32, 12 November 2026 (UTC)
You have diffs for the former. Instead of "vibe-coded browsers" I should have just said "browsers", which you also have diffs for. Should you resume caring, of course. In solidarity, Autoinvective (🗨︎ 𓅬) 00:34, 13 November 2026 (UTC)
I'm striking most of this. I misunderstood some things myself. Sorry about that, Levivich. If it helps, I'm kicking myself real hard over it right now. In solidarity, Autoinvective (🗨︎ 𓅬) 01:45, 13 November 2026 (UTC)
I think it's a perfectly understandable question, but I have a rather specialised background in theoretical computer science. But you can rest assured, large language models are not going to replace Levenshtein distance algorithms with dictionaries when it comes to spell checkers. That would be like taking a probabilistic sledge hammer (the metaphorical stochastic parrot) to hang a frame. It would consume way too much resources and be incorrect more often than the currently-used algorithm that works very well. There's also no way to force free software projects like aspell and hunspell to completely rewrite their own codebases to either require many-exponents larger databases and processing power or send every input to a third party online service, even if you could somehow convince the maintainers to abandon their existing implementations that have been worked on for decades.
It simply doesn't make sense. ‑‑gurkubondinn 22:04, 12 November 2026 (UTC)
Yeah what also doesn't make sense is interpreting the words "in some way or another" to mean "by replacing Levenshtein distance algorithms." Levivich (talk) 23:28, 12 November 2026 (UTC)
So your weird focus on some sort of ban on spellcheck (here, this edit summary) has nothing to do with your assertions that all browsers (and all software) will start using AI-based features here and here, despite this comment? Great, sorry for synthesizing that incorrectly. In solidarity, Autoinvective (🗨︎ 𓅬) 00:23, 13 November 2026 (UTC)
To give a bit more context I thought I'd try to apply it to an excerpt from a draft I'm gradually working on, different options for what to do appear each time, so here are a few examples:
Original:
During his time in the Artic, Bodfish obtained a large quantity of "curios" from the natives which he later donated to the Cleveland Museum of Natural History. These objects are now part of the Bodfish collection on indigenous technology at the museum. A collection of bird eggs and his papers and photographs from the arctic are also held by the New Bedford Whaling Museum.
Refine the wording:
During his Arctic expeditions, Bodfish amassed a substantial collection of "curios" from local indigenous communities, which he later donated to the Cleveland Museum of Natural History. These items constitute the Bodfish collection on indigenous technology. Furthermore, his collection of bird eggs, along with his papers and Arctic photographs, is held by the New Bedford Whaling Museum.
Personalise the tone:
During his adventures in the Arctic, Bodfish gathered an impressive assortment of "curios" from the native communities, which he generously donated to the Cleveland Museum of Natural History. Today, these fascinating items make up the Bodfish collection on indigenous technology. Alongside these treasures, his collection of bird eggs, as well as his papers and photographs from the Arctic, are lovingly preserved at the New Bedford Whaling Museum.
Organise this draft:
During his time in the Arctic, Bodfish acquired a substantial collection of "curios" from native communities, which he later donated to the Cleveland Museum of Natural History. These items form the Bodfish collection on indigenous technology. Additionally, his collection of bird eggs, along with papers and photographs from the Arctic, is held by the New Bedford Whaling Museum.
Improve the writing:
During his time in the Arctic, Bodfish amassed a significant collection of "curios" from local native communities, which he later donated to the Cleveland Museum of Natural History. These items now constitute the Bodfish collection on indigenous technology. Furthermore, his collection of bird eggs, along with his papers and Arctic photographs, is preserved at the New Bedford Whaling Museum.
Rewrite for clarity:
During his time in the Arctic, Bodfish collected numerous "curios" from the local native communities, which he later donated to the Cleveland Museum of Natural History. These items now make up the Bodfish collection on indigenous technology. His collection of bird eggs, along with his papers and Arctic photographs, is held by the New Bedford Whaling Museum.
Make easier to read:
During his time in the Arctic, Bodfish collected many "curios" from the local people and later donated them to the Cleveland Museum of Natural History. These items are now part of the museum's Bodfish collection on indigenous technology. His collection of bird eggs, as well as his papers and photographs from the Arctic, are kept at the New Bedford Whaling Museum.
Make it more professional:
During his time in the Arctic, Bodfish collected an extensive array of "curios" from indigenous communities, which he subsequently donated to the Cleveland Museum of Natural History. These items constitute the Bodfish Collection on indigenous technology at the museum. Additionally, a collection of bird eggs, along with his papers and photographic documentation from the Arctic, is preserved at the New Bedford Whaling Museum for scholarly research and public exhibition.Giulio 16:37, 4 November 2026 (UTC)
Going through these:
The original sentence contains a spelling error ("Artic") and a capitalization error ("arctic"). One spot ("communities which") may or may not be an error depending on whether "which he donated..." is a restrictive clause and whether the sentence is using British English. "A large quantity" is wordy. The second sentence is somewhat awkwardly worded. I would want to look up whether the museum capitalizes Bodfish Collection. There are also some possible content issues -- saying someone "obtained" items from indigenous communities is a little "hmmm" -- but those are out of scope for a copyedit.
Edit 1 changes the meaning in two places. The original sentence claims that the curios were part of the Bodfish collection, implying there are other items in the collection; the rewrite claims that they constitute the collection, implying the collection is just those curios and nothing else. It also says that the bird eggs were originally Bodfish's, which the original sentence did not claim and which isn't necessarily true. The rewrite also introduces a pointless "Furthermore" while not really making the second sentence any less awkward. It doesn't fix the wordiness issue; the phrase is just wordy with bigger words.
Edit 2: I feel like I don't need to explain why this one is bad.
Edit 3 not only changes the meaning in the same ways Edit 1 does, but adds one more change: the text no longer says that the papers and photographs are Bodfish's. Not as bad as the other way around, but still a meaning change. Also like Edit 1, it introduces a pointless "Additionally." It's also unclear what part of the edits constitute "organizing."
Edit 4 changes the meaning and inserts a pointless "Furthermore" yet again.
Edit 5: Changes the meaning yet again, but at least it doesn't insert filler words and it properly fixes "a large quantity." Ironically this edit, which claims to be a "rewrite," is actually one of the lowest-impact edits.
Rewrite 6 only changes the meaning in one place! Hooray! Unfortunately, it introduces a grammatical error: "his collection of bird eggs... are."
Rewrite 7 has the same problems as the other rewrites -- although it at least keeps "a collection of" -- but also tacks on totally new information in for scholarly research and public exhibition. The rewrite is also just generally wordy and flabby.
So these edits are all on the spectrum of "whatever" to "not a net improvement" to "actively bad." Unfortunately, the actively bad one (#7) is closest to the LLM edits we get on Wikipedia. Gnomingstuff (talk) 19:32, 5 November 2026 (UTC)
I don't think banning LLM-powered copyeditors is at all feasible or desirable. What we need to do is make WP:SPELL have more guidance about the various tools, which are the best etc. Will look into whether we can do anything wrt Edge Kowal2701 (talk, contribs) 22:20, 4 November 2026 (UTC)
I don't think that trying to micromanage which browsers/text editors people are allowed to use in a WP:BITEy way is the way to go. Nor is saying "Breaking the rules is a-OK if you don't get caught", and honestly, I don't think that's how WP:IAR is ever interpreted nor is it a good idea to establish that as a precedent. I suspect we'll rather have to narrow NOLLM to cases of folks adding entire paragraphs or articles, rather than isolated sentences & emphasize that if there are hallucinations or bogus sources, that's a sign of LLM use going too far. 'course, I expect the world to soon focus AI use on these use cases where it is actually useful as the AI bubble pops, but I wouldn't expect a total walkback either. JoJo Eumerus mobile (main talk) 15:50, 9 November 2026 (UTC)
Google just acknowledged that you can’t use Google Search without using artificial intelligence. The search giant announced a slate of new AI products for classrooms and schools on Tuesday as well as more ways for teachers and schools to limit or restrict use of those AI tools. The company said the schools should have control over whether students use AI in the classroom. There’s one catch, though: if a school or teacher blocks the use of Google’s AI features, students won’t be able to use Google Search.
This is a further example of how AI is embedded so deeply in such common tools that a ban is impractical. Andrew🐉(talk) 13:40, 6 November 2026 (UTC)
Nobody's trying to ban offwiki use of LLMs. The text of the ban is right there.
The use of large language models (LLMs) to generate or rewrite article content is strictly prohibited
Unless someone is using Google Search to generate article prose for them, this has nothing to do with anything.
The reason why the edge thing is relevant to the ban is because it's a tool which actually rewrites your text with AI. Athanelar (talk) 13:46, 6 November 2026 (UTC)
The process of writing an article is often like a jigsaw as you pull together lots of pieces of information from a variety of sources in multiple tabs. Often these may be hard facts like the names of people, organisations, numbers and stats, dates, titles of works and so on. One would typically use cut/paste for these rather than retyping them because it's easier and less error-prone. Prose is then the glue which strings these facts together, like beads on a necklace.
Now one already has to be careful with cut/paste to avoid copyvio or too close a paraphrase. Getting this right is a craft rather than a science. But trying to decide whether an LLM was involved at some level seems difficult when AI pervades every aspect of the process.
For example, the other day I wanted to quote a line from a Wikipedia disclaimer page. The original text was in all caps but what I noticed was that, when I pasted it, it was in sentence case. I've not seen this before and I'm still not sure which part of my interface was doing it -- whether it was the operating system, the browser, the editor or what. I puzzled over it for a little but am still none the wiser. Expecting editors to understand exactly how these things work is unrealistic when they are so embedded and seamless.
it also isn't black or white, like Wikipedia:AI noticeboard/Tiny Particle where someone was using AI to generate tables etc. was just closed as "cleanup unnecessary", I think in the future we'll probably explicitly permit that with some caveats. Generally-speaking there's a spectrum between 'rigid code' and 'high-entropy prose' where it's more unacceptable and problematic the further you go along it, similar to how using AI to make highly personal messages is often met w disgust compared to other more impersonal uses Kowal2701 (talk, contribs) 15:08, 6 November 2026 (UTC)
it also isn't black and white is exactly why the rigidness of a guideline line NOLLM (and even more so if it were a policy) are problematic. Thryduulf (talk) 16:02, 6 November 2026 (UTC)
see , imo it's great for the short-term Kowal2701 (talk, contribs) 16:05, 6 November 2026 (UTC)
Brief and blunt is only good if it is also clear and correct, this is neither. Thryduulf (talk) 16:33, 6 November 2026 (UTC)
@Andrew Davidson If you're talking about Wikipedia:General disclaimer, the text is written in sentence case but is inside an HTML tag that uses text-transform:uppercase;, which means that while it appears uppercase, it is actually sentence case and will copy-and-paste that way. It has nothing to do with any sort of AI. --Ahecht (TALK PAGE) 18:07, 18 November 2026 (UTC)
Thanks for the explanation. My point remains that I didn't understand what layer of software was causing the effect and I didn't even consider that possibility. Cut/paste is usually quite intuitive but I notice that there's a new function on Googlebooks, which I have been considering – the Magic Pointer, which embeds AI into the mouse pointer so that you can use Gemini with the content that you're pointing to. I haven't tried yet but it sounds like something that will become second nature, like Ctrl-C/V. Andrew🐉(talk) 18:44, 18 November 2026 (UTC)
Thanks for sharing, Andrew, I think a lot of new editors find that the interfaces within Wikipedia itself are quite well made but navigating them and understanding how they work requires technical knowledge. It's not apparent to anyone without my disclosure of it, but I use MediaWiki to perform all my drafting. That way I don't have countless difficult to follow edits and my edits come out nice and polished. As a newer editor, I have a lot of trouble creating info boxes still, and I use the source text editor more often than the visual editor. Using MediaWiki I'm able to resolve weird-to-me or finicky-to-me platform quirks(to-me) with MediaWiki before I publish... Tmanok (talk) 23:06, 18 November 2026 (UTC)
Should something about LLMs be mentioned at WP:NOT?
Just a VERY preliminary question. I am not suggesting any language. But if the consensus is that WP should not be written by LLMs then WP:NOT seems like an appropriate place to say that. Blueboar (talk) 15:47, 5 November 2026 (UTC)
Conditional on NOLLM or a variant being accepted as policy, it would be reasonable; NOT being the place where e.g our spam policy and other we-don't-want-this-stuff policies reside. Jo-Jo Eumerus (talk) 15:55, 5 November 2026 (UTC)
Not what though? Not written by LLMs? Nobody would think it was. I think WP:Editing policy, not WP:NOT, is the right policy to specify any strict LLM usage rules we have. Levivich (talk) 16:07, 5 November 2026 (UTC)
Agreed, something like "Wikipedia is not generated by LLMs" doesn't fit with WP:NOT's core idea that Wikipedia is an encyclopedia. Grokipedia is an encyclopedia too, even though it's written by an AI (and is in general not a great resource). --not-cheesewhisk3rs ≽^•⩊•^≼ ∫ (pester) 16:28, 5 November 2026 (UTC)
I agree with Levivich too. The closest I can come to some sort of phrasing that would make sense on WP:NOT would be something like "Wikipedia is not a place for LLM-generated text" but firstly that's not quite accurate as the actual guidelines are more nuanced (this is not the place to argue about this) and also as noted above it is not inherent in what Wikipedia is. Thryduulf (talk) 18:25, 5 November 2026 (UTC)
As for what Wikipedia is, I would suggest: “WP is an encyclopedia written by humans, for humans”. Sure, AI uses WP to train itself, but training AI isn’t our purpose. Blueboar (talk) 19:30, 5 November 2026 (UTC)
It's a catchy slogan but neither part is true. For the first part, Wikipedia is written by humans, bots, humans with the assistance of LLMs, and LLMs. The latter is against the letter of policy but where it's indistinguishable from human-written text it'll stay because it's undetectable (and even if it were detectable it would be a complete waste of effort to try). Similarly there will be LLM-written text that wasn't detected at the time and has been significantly altered by humans since. Also, whether things like asking an LLM to convert a list of values into a wikitable counts as "LLM-written" depends on your point of view (if either the LLM transcribes all the values correctly or a human corrects any errors then it's undetectable, and of course humans are more than capable of making transcription errors too).
Regarding the second part, while humans are the primary audience we also very deliberately output structured data, metadata, etc. for human and non-human reusers. I hope we can agree that Wikipedia is not in the business of lying about what Wikipedia is. Thryduulf (talk) 20:25, 5 November 2026 (UTC)
Though I often disagree with you in matters relating to LLM use/policy on Wikipedia, I have to agree with you here. The slogan is certainly catchy, but it heavily oversimplifies things.
In fact, I'll add to your argument. You say that Similarly there will be LLM-written text that wasn't detected at the time and has been significantly altered by humans since. There's also LLM-written text that was explicitly disclosed as such (and allowed at the time) that has since been significantly altered by humans, like Artwork title (LLM-generated in December 2022). When @Kowal2701put a tag on it in August of this year, I removed it because maintenance tags are not meant to be badges of shame. SuperPianoMan9167 (talk) 21:00, 5 November 2026 (UTC)
AI-generated content isn't allowed on WP, and the article still contains such content, not a good de-tag. WP:NOTLAB also applies Kowal2701 (talk, contribs) 21:09, 5 November 2026 (UTC)
Difference between first (AI-generated) revision and current revision. Most of the original text has been heavily altered and expanded; there are a couple of sentences that have remained mostly or entirely unaltered, like "These titles can be descriptive, indicative of the content or theme of the work, or they can be more abstract and open to interpretation."
Question: Is it a constructive use of AI Cleanup editors' time to remove every word of the original AI-generated version from the article, because "every word of a Wikipedia article should be written by a human"? Yes, I know this is grandfathering in AI-generated content, but IMO nitpicking an AI-generated article from December 2022 just isn't worth it. SuperPianoMan9167 (talk) 21:27, 5 November 2026 (UTC)
my bad, probably a good detag then. Re rewriting AI-generated content, it isn't black or white, straightforward sentences are fine to leave per se. It sometimes happens where someone will rewrite the text without reading the sources, and WP:V failures remain, but that doesn't look to be what's happened here Kowal2701 (talk, contribs) 22:02, 5 November 2026 (UTC)
Yeah I think this is fine to detag -- as you said the text has been almost completely changed, and the AI text in this case was easy-to-deal-with fluff. Gnomingstuff (talk) 16:19, 6 November 2026 (UTC)
Something I noticed: you implicitly referred to NOLLM as policy, further supporting my argument that it should be labeled as a policy because it is already treated as such: The latter is against the letter of policy (emphasis mine) Not "against the letter of policies and guidelines". "Against the letter of policy". (Of course, you could also be referring to WP:EPAI, which is already policy that bans most uses of LLMs.) SuperPianoMan9167 (talk) 21:08, 5 November 2026 (UTC)
I was not using the word "policy" precisely there but as a shorthand for "policies and guidelines", which given the context of this discussion was rather silly of me. Thryduulf (talk) 21:29, 5 November 2026 (UTC)
AI uses WP to train itself No. Humans train AI using WP. Or direct AI to train itself using WP. Either way, humans are the ones deciding to use WP as training material. SuperPianoMan9167 (talk) 21:04, 5 November 2026 (UTC)
I think we could cover both sides of the coin, "Wikipedia isn't a slop farm" and "Wikipedia isn't a Butlerian jihadist sleeper cell" Kowal2701 (talk, contribs) 18:37, 5 November 2026 (UTC)
I have been thinking about "by humans for humans" and I can't support it. Discussion has focused on "by humans" but I think that's acceptable. We are comfortable saying "Wikipedia is not a business directory" even though, gods know, parts of it are. But "for humans" contradicts our license, which clearly permits use of Wikipedia as training data; it also contradicts the considered decision not to (try to) block scrapers. This is too far from the truth for a slogan, as far as I'm concerned.
I also think that if we promote NOLLM to policy, we should explicitly address use of LLM to locate sources. I have seen Teahouse hosts flatly say this is not allowed, which I believe is unjustified. "Use of LLMs to search for sources is allowed, but editors are responsible for reading, evaluating, and summarizing sources themselves." might stop a lot of arguments in their tracks.M kuhner (talk) 21:58, 10 November 2026 (UTC)
I can't see how "for humans" purports to limit other uses. It's a statement of our target audience: Wikipedia articles are written with their primary goal to be read by people. If I may wax snarky, contrast Wikidata (by humans, for Google Knowledge Graph; but clearly not human-targeted in any case).It would be a stretch to call LLM use solely to locate sources "generat[ing] or rewrit[ing] article content". But even if you read "generate" expansively enough to include research with no text carried forward, then it wouldn't be detectable anyway, so it's moot. And no, that's not an argument to scrap or sideline NOLLM, any more than the fact that it's so difficult to detect copyright infringement via translation is reason to rescind copyright policy. —Cryptic 23:53, 10 November 2026 (UTC)
I wouldn't fuss over the guideline (lack of guideline) on the use of LLM for source-finding if it were not for multiple instances where it has not seemed to be clear enough. The infeasibility of preventing it is quite often used as an argument against NOLLM as a whole; and people are misinformed at the Teahouse about allowability of LLM searches on a somewhat regular basis. Let's make the guideline/policy clear on this point. I don't think it will take very many words. M kuhner (talk) 00:06, 11 November 2026 (UTC)
I've seen instances of people (presumably) reading "NOLLM" and thinking that means no using LLMs at all in any way for anything related to Wikipedia. There are some who have made it clear that they would like that (or something closely approximating that) to be the rule, but it is not the rule as things stand. Thryduulf (talk) 00:22, 11 November 2026 (UTC)
Should this proposal be adopted as an official notability criterion?
Should the proposed notability criterion WP:NLANG be adopted?
A: Yes
B: No
Changes in wording or substance may also be discussed here; if consensus is reached for certain changes they will also be implemented.
Pinging previous participants in discussions about this: @Kwamikagami:@Boynamedsue:@Sirfurboy:@TaivoLinguist:@Cnilep:🪐Kepler-1229b|talk|contribs🪐 04:45, 17 October 2026 (UTC)
In addition, new proposals for such a notability criterion can also be made here; if they gain consensus as well they may also be adopted. 🪐Kepler-1229b|talk|contribs🪐 01:41, 12 November 2026 (UTC)
Survey
Aren't we supposed to be answering A (yes) or B (no)?
B I don't like that this depends so much on the idea of a language being stable when my understanding is that languages are not stable over time. And the distinction between a language and a dialect seems arbitrary as they are a continuum. Andrew🐉(talk) 20:31, 11 November 2026 (UTC)
The language only needs to have been transmitted between generations for any period of time to qualify here. 🪐Kepler-1229b|talk|contribs🪐 20:36, 11 November 2026 (UTC)
B: No we do not need an SNG here, if a language is notable it will surely pass the GNG threshold. Cavalryman (talk) 06:41, 12 November 2026 (UTC).
B: No We don't need another obscure notability guideline when the GNG is sufficient. Wikipedia already has too many special rules. Joe vom Titan (talk) 18:57, 12 November 2026 (UTC)
Discussion
I wonder if the stability section should come before confirmation, given that it is so much shorter. The layout would be easier to follow that way.
Maybe a few wording tweaks for clarification (e.g. intermediate nodes in a classification), but I don't see any substantial problems. — kwami (talk) 05:22, 17 October 2026 (UTC)
I don't see what else we need to add there to be honest. Got any suggestions? 🪐Kepler-1229b|talk|contribs🪐 05:25, 17 October 2026 (UTC)
Yeah, actually, I guess not. I tried reversing the word order of proposed-but-not-generally-accepted language families and intermediate nodes, which if we're being pedantic should be hyphenated, but it wasn't an improvement. — kwami (talk) 05:37, 17 October 2026 (UTC)
Makes sense. Also can't see any more problems here. 🪐Kepler-1229b|talk|contribs🪐 05:40, 17 October 2026 (UTC)
I'm still a little concerned about the article's acceptance of Glottolog alone. I would also be a little concerned about dialects not being notable as a principle.Boynamedsue (talk) 06:22, 17 October 2026 (UTC)
How is it Glotto alone?
If dialects are inherently notable, how do we identify what counts as a dialect? It's an open-ended category with AFAICT no criteria for inclusion. Basically anything could be claimed to be a "dialect" and therefore warrant an article. — kwami (talk) 08:53, 17 October 2026 (UTC)
My interpretation of the proposed guideline is that a Glottolog entry is enough for notability, unless reliable sources state that the language has been given an entry in error. Ironically, in my view, sources discussing why a language doesn't exist make the purported language more notable than a language only supported by a Glottolog page.Boynamedsue (talk) 11:46, 17 October 2026 (UTC)
That's the crux of the issue. IMO a people, a nation, a language are all inherently encyclopedic. A spurious language may have more coverage than an obscure real one, but IMO we shouldn't dismiss entire peoples as not worthy of coverage. A spurious language can be included too if the sources support it.
It's not that Glotto is in itself adequate for notability, but that they demonstrate existence, and it is the language itself that establishes notability. — kwami (talk) 19:08, 17 October 2026 (UTC)
I don't really believe in peoples and nations. But I would agree that a language is almost always notable. I just don't believe that we can be sure a language exists from the fact it has a glottolog entry.--Boynamedsue (talk) 21:22, 17 October 2026 (UTC)
From what I've seen in the past, Glottolog has written entries based on fragmentary centuries old wordlists. For me, it's not sufficient on its own.--Boynamedsue (talk) 21:48, 17 October 2026 (UTC)
Only if there's enough data to conclude that it was a distinct language. — kwami (talk) 21:50, 17 October 2026 (UTC)
In my view they have concluded a language exists in situations where there isn't enough data to do so, like that of Magiana language. As discussed above, they have likely made a mistake by classifying Magiana separately from Majena language. I personally don't feel comfortable using Glottolog alone for poorly attested languages, as they sometimes base their entries solely on very old primary sources that have not been analysed by relevant linguists. I won't be able to support this proposal unless Glottolog is removed.--Boynamedsue (talk) 03:44, 18 October 2026 (UTC)
@Boynamedsue They haven't because they don't list both Magiana and Majena. They only list one of the two. 🪐Kepler-1229b|talk|contribs🪐 04:05, 18 October 2026 (UTC)
Yes, that is true. It doesn't seem to be aware of Majena, which is better covered by scholars. In my view this doesn't massively change my point; Glottolog is a reliable source, but not a good enough one to have a special exception from WP:GNG carved out for it.Boynamedsue (talk) 04:18, 18 October 2026 (UTC)
You may wish to have a look at the proposal further down if you have not done so. 🪐Kepler-1229b|talk|contribs🪐 05:34, 18 October 2026 (UTC)
I don't think the RfC is particularly well formed. What is "this proposal"? Editors who have not participated in the preceding discussion will appreciate a clearer statement of the question. Regulov (talk) 15:39, 17 October 2026 (UTC)
The proposal is the project page for which this is the discussion page, but I agree that this is unclear. I have had to double check this twice. Is this the correct venue for such a significant RfC?Boynamedsue (talk) 15:48, 17 October 2026 (UTC)
Since there haven't been any votes yet, perhaps the RfC could be held off until it is clarified? Kisseran (talk) 16:13, 17 October 2026 (UTC)
Apologies for the poorly worded RfC; this is my first time opening one and I don't ave any experience with them. 🪐Kepler-1229b|talk|contribs🪐 18:59, 17 October 2026 (UTC)
+1 a link to RFCBEFORE would be helpful. Dw31415 (talk) 21:38, 7 November 2026 (UTC)
Previously, I had discussed with other editors on the proposal before beginning the RfC. 🪐Kepler-1229b|talk|contribs🪐 21:44, 7 November 2026 (UTC)
I read the proposal on the page, but I find it unclear. It says languages should be "stable", but it does not tell us how we are supposed to determine that easily; then it talks about "confirmation" but of what? I think WP:GNG is more clear and sufficient. --Piotr Konieczny aka Prokonsul Piotrus| reply here 00:49, 18 October 2026 (UTC)
Both of those are explained.
"Stable" means transmitted across generations. Confirmation is confirmation that the language exists. — kwami (talk) 00:56, 18 October 2026 (UTC)
Which can and should be determined through RS, and there is no need for anything but GNG IMHO. Can you show me an example of an article that should be on Wikipedia, common-sense wise, but does not pass GNG meriting this proposal? Piotr Konieczny aka Prokonsul Piotrus| reply here 01:05, 18 October 2026 (UTC)
It's not clear to me that this is useful. In the past 12 months there have been 12 AfDs on languages or language families, and 5 of those (language groupings and conlangs) would be covered by the GNG and not this proposal. 2 of the 12 were scope issues that this proposal probably wouldn't have helped with. The remaining 5 cases don't clearly align with the proposal's likely outcomes for entries with minimal coverage beyond a database entry. Of those 5, 2 had glottolog codes (a third had a LinguistList code) but were merged or renamed because the language itself didn't have significant coverage. The proposal would have been clearly useful 5 times in the last year, and might have gotten the opposite result in 2 or 3 of those 5 cases.
Altogether, I don't really see why this is needed, and even if it is, I don't think it's workable in its current state. Others have pointed out conflicts with parts of the notability policy so I won't repeat those. — Wug·a·po·des 01:21, 18 October 2026 (UTC)
Just to add to your analysis, I think you have missed at least six AfD discussions in the past 12 months because they do not include the word "language" in their titles:
I think there's some more Meitei dialect stuff that's been missed so far. 🪐Kepler-1229b|talk|contribs🪐 01:50, 18 October 2026 (UTC)
Could someone give me a tl;dr on the background of this proposal? If I understand correctly, this proposal seeks to do two things:
set a somewhat lower bar for inclusion for languages by auto-keeping language articles that satisfy this proposal even if they fail GNG.
clarify our stance on what a listing in reference works like Glottolog and Ethnologue contributes to notability for languages/language varieties.
Is that an accurate understanding of? Since the intent seems to be to tilt the scales towards inclusion, could the proposer(s) link my to a couple AFDs that closed delete that should have closed keep in the view of the proposer(s)? -- LWGtalk(VOPOV) 11:58, 13 November 2026 (UTC)
Tour understanding seems to be more or less correct as well. 🪐Kepler-1229b|talk|contribs🪐 13:43, 13 November 2026 (UTC)
This was intended as something we could point to when someone mass-tags language articles for deletion. There weren't problems with articles actually being deleted at AFD, because the argument that languages are notable had been enough. Putting it in writing just saved the effort of going through the same thing over and over. But now we've had a successful AFD proposal for Baazəm, which goes against 20 years of precedent that languages are inherently notable. — kwami (talk) 19:25, 13 November 2026 (UTC)
Alternative proposal to the same effect
I think the current proposed guideline based on the confirmed existence of the language alone is unlikely to be convincing enough to pass. Instead, I think the guideline should take GNG as a starting point, and explicitly prescribe the amount of known information that would be sufficient to justify a standalone article, as opposed to being a section in an ethnographic article or an entry in a list. Here's an alternative proposal, which I think will have largely the same effect, but easier to justify:
A human language is presumed notable if it satisfies GNG or three or more of the following are explicitly covered across all reliable sources:
A Glottocode or ISO-639 code
A numerical estimate for speaker count (at any point in time) that is nonzero
A phonological or phonetic inventory
Any morphological feature or combination thereof, that if presented in tabularly, contains at least three distinct items
Any description of word order
A word list of at least two words, accompanied with translations into the language of the relevant source
An acknowledgement of the absence of information for any of the above in a source that supplies information for any other one of the above
For the purposes of notability, Glottolog and any source listed therein is presumed to be independent and reliable, and significant coverage as outlined above is sufficient even if only a single reliable source exists.
[Commentary: These criteria obviate the problem of presuming notability based on existence and the concern of worthless permastubs. The exact wording and requirements are open to further refinement, of course. These can also be applied to dialects, reconstructions, and constructed languages naturally with the provisions proposed below]
A dialect, sociolect, or any other language variety is subject to the same criteria as above, with the provision that the relevant passage in a source must explicitly refer to the variety in question. A work that purports to be description of an entire language X does not provide notability for a variety Y if the work exclusively treats Y.
A constructed language is subject to the same criteria as above, with the provision that the relevant reliable sources must be independent from the creator(s) of the language. A source written in a constructed language is presumed to be non-independent from that constructed language.
A reconstructed language is subject to the same criteria as above, with the provision that a scholar's own works are not independent from their own reconstruction.
A grouping of languages is presumed notable if its reconstructed protolanguage is notable, or if a single work treating the group as a whole is significant enough to meet the criteria above for two or more members of the group in question.
"A work that purports to be description of an entire language X does not provide notability for a variety Y if the work exclusively treats Y."
Are you sure this is strictly what you intend? I am not sure I follow the sense. Does "exclusively" mean the work does not discuss other varieties? Does it mean the work fails to describe the entire language X of which Y is understood to be a variety? Why would such a failure mean the discussion of Y does not count toward establishing Y's notability? I don't get it. Regulov (talk) 15:29, 17 October 2026 (UTC)
Yes, this is what I intend. Due to practical limitations, many descriptive grammars of some language are based mostly or exclusively on a single variety of that language, while ignoring other varieties. For instance, the 2015 Grammar of the Yakkha Language begins its section on dialectal variation thus:
The variety documented here is spoken in Tumok village and surrounding areas, e.g., in Salle. No detailed dialectal study has been undertaken for Yakkha yet. Based on phonological differences and distinct exclamative words, I tentatively propose three further dialects: one spoken in the area around Ankhinbhuin (Angbura, Hombong, Phakling), one spoken in the area around Dandagaun and one spoken towards the north, in Kingring and Kharang villages.
Now, the grammar does not go on to provide enough detail to establish notability for these additional dialects by the standards I have just proposed. This is a good, intended outcome, since the information is sparse enough that it would fit better as a section in the article Yakkha language. However, one may argue that since the rest of the 600+ page grammar treats the Tumok variety of Yakkha, that an article like Tumok Yakkha is warranted. In the absence of other sources, this would be a bad idea, since such an article would almost entirely duplicate the current article on the Yakkha language. Kisseran (talk) 16:04, 17 October 2026 (UTC)
I think I understand now. Thank you. Consider rephrasing. I take it the important thing is that a variety or dialect's notability (distinct from that of its parent) requires at least one other notable, clearly distinct sibling variety or dialect. In a discussion of language A, dialects P(A) and Q(A) are covered. On this basis, the discussion counts toward the notability of both dialects. In another discussion of language A, only one dialect, P(A), is mentioned; and in a third, only Q(A). These latter discussions, under the rule, cannot be used to demonstrate the notability of either dialect.
"A work purporting to describe an entire language X does not provide notability for a variety Y if Y is the only variety of language X it covers."
"In order for a work purporting to describe an entire language X to provide notability to a variety Y, it must cover at least one other variety of the same language in comparable detail."
"A work that purports to be description of an entire language X does not provide notability for a variety Y if the work does not cover at least one other variety of X in similar detail."
According to one reading of these criteria, the "language" of nearly every city or conurbation in the world is worthy of an article. For Southern California, we could have articles on San Diego English, El Cajon English, Los Angeles English, Riverside English, Santa Barbara English, and likely dozens more. None of these are actually notable, IMO, but they could easily fit the criteria.
Actually, we might have the same for an ever-expanding number of schools and colleges.
On the other hand, if we adhere strictly to the criteria above, English fails, because Glottolog is a RS but doesn't cover at least three of the above. All languages fail these criteria, and we'd need to fall back to GNG and there is therefore no point to this proposal.
The guideline as currently worded reflects the actual criteria as currently practiced on WP. Its purpose is merely to have a remedy against new editors tagging hundreds of languages as non-notable, and demanding to know why their tags were mass-reverted. It doesn't need to be an official guideline to accomplish that. If the choice is between the current state of affairs and corrupting it to uselessness because we anticipate that there will be no end of contradictory objections, then I vote to leave things as they are. They're working just fine, and I don't see any benefit to changing them. — kwami (talk) 19:29, 17 October 2026 (UTC)
I would be curious to see the sources that you would point to to show that Riverside Californian English is notable under this proposal. On the other hand, I'm not sure how you take the criteria to exclude English. Are you interpreting "at least three or more across all reliable sources" as "at least three of more in every reliable source"?
The current drafted guideline will not pass. It flies in the face of WP:NRV which states No subject is automatically or inherently notable merely because it exists. WP:LOCALCONSENSUS states that unless they can convince the broader community that such action is right, participants in a WikiProject cannot decide that some generally accepted policy or guideline does not apply to articles within its scope. If you want to mass-revert notability tags, you need to back that up with a relevant policy or guideline. Kisseran (talk) 20:01, 17 October 2026 (UTC)
Any morphological feature or combination thereof, that if presented in tabularly, contains at least three distinct items
Any description of word order
A word list of at least two words, accompanied with translations into the language of the relevant source
could be condensed into a general description of the language in question. 🪐Kepler-1229b|talk|contribs🪐 20:20, 17 October 2026 (UTC)
Also, the two-word limit seems a bit arbitrary when there are languages such as Arma–Pozo language which are known from exactly a single word (the example in question has been covered in sufficient sources to warrrant an article). 🪐Kepler-1229b|talk|contribs🪐 20:23, 17 October 2026 (UTC)
Additionally, "A numerical estimate for speaker count (at any point in time) that is nonzero" seems a bit dense and unwieldy for a notability description; it could be condensed into "The language has been spoken by any number of people at any point of time" or something like that. 🪐Kepler-1229b|talk|contribs🪐 20:35, 17 October 2026 (UTC)
Replying point by point:
I divided "a general description of the language" into multiple points because people will disagree with respect to what counts as a "general description", and it wouldn't be much of an improvement compared to GNG's "significant coverage". Consider that you will be applying this guideline to convince people at AfD, most of whom will not have much linguistic expertise.
I'm not super attached to the two-word limit. If people think "at least one word is known" would fit better, then that would be fine as well. That said, I don't think Arma-Pozo language is a particularly compelling example, considering that its ISO-639 code was deprecated because there wasn't enough evidence for its existence. It would do fine regardless, since it meets GNG, but at that point the article is more about a historical anecdote than linguistic scholarship.
"A numerical estimate for speaker count (at any point in time) that is nonzero" is worded like that because simply knowing that some number of people spoke it at some point in time is tantamount to knowing that it exists, whereas knowing approximately how many people spoke it is something that you should be able to point to as significant coverage.
I can see where you are coming from here, and I agree with your points as worded currently. Nevertheless, I do feel like points for the documentation should be grouped somehow together, perhaps indented together somehow. 🪐Kepler-1229b|talk|contribs🪐 21:13, 17 October 2026 (UTC)
And again, how do we avoid non-notable "dialects"? I'm thinking of language activists (India and Pakistan come to mind, but there are others) who insist that their "language" warrants an article, even though it is not established as a language or even a distinct dialect. If I can show an inventory (exactly the same as the parent language/dialect), a couple regionalisms, or even just words that duplicate the parent language/dialect, and the population of the district, then my "language" meets the notability criteria. — kwami (talk) 20:35, 17 October 2026 (UTC)
I do find myself partial to the proposal of at least two dialects meeting notability to have articles about them. 🪐Kepler-1229b|talk|contribs🪐 20:49, 17 October 2026 (UTC)
Yes, I do like that. But do we have any dialect articles where it's the same dialect as the language article because nothing else is attested? I suppose we might have cases where a dialect is reported to be divergent, and is the only one that is attested well enough for an article. But then it probably shouldn't be merged with the language article as if it were representative. — kwami (talk) 21:48, 17 October 2026 (UTC)
If people insist that a language variety warrants an article, and they can find reliable sources to support it, then it's no longer a problem of notability. There are other policies and guidelines, such as WP:POVFORK and WP:NOTSOAPBOX that circumscribe the range of appropriate article beyond notability. Also, I can't think of an instance of such a spurious, non-notable dialect that would be allowed by the proposed criteria, but fail GNG. Even if someone does manage to publish such a spurious description, it is entirely feasible to argue that it would be unreliable for the reasons that you suggest. Kisseran (talk) 20:50, 17 October 2026 (UTC)
Couldn't support this. We correctly !voted to merge Wikipedia:Articles for deletion/Magiana language, which is incorrectly listed with a Glottolog code despite being a synonym of a better known language that is not listed, Majena language. We would have been constrained to accept it on the basis of 2 and 6 appearing in a primary source from the 1790s if this proposal was accepted. I would want to remove Glottolog from the list and add the qualifier "in a reliable secondary source or the research of a scholar with academic credentials." to numbers 2-7.Boynamedsue (talk) 07:05, 18 October 2026 (UTC)
Does 2 appear in the source? I'm not sure how to gain access to it but I don't see any mention of speaker count in the merged article. Kisseran (talk) 11:04, 18 October 2026 (UTC)
No figure for speaker count seems to have been ever given for Magiana/Majena. 🪐Kepler-1229b|talk|contribs🪐 17:54, 18 October 2026 (UTC)
I thought there was a number of villages and people given in one of the 18th century sources? Must be misremembering. In any case, in my view, as we have seen errors with Glottocodes, I reject giving it any special privileges.Boynamedsue (talk) 05:08, 19 October 2026 (UTC)
Glottolog errors can be easily corrected by posting to their Github page, so I don't see the problem here. I've done that quite a lot and they have added the correct changes. I further quote from Majena: There is some confusion between the Majena-speaking Ticomeri and another group, also known as "Ticomeri", who spoke a divergent dialect of Moxo. Whether the two groups were related (i.e. whether the Ticomeri had abandoned Majena and acquired Moxo) is unknowable, since both were apparently extinct by 1805 (emphasis mine). 🪐Kepler-1229b|talk|contribs🪐 06:12, 19 October 2026 (UTC)
Well in Wikipedia we work with reliable sources, not just perfect sources. In any case, the heuristic proposed here makes the correct determination, and I find it highly unlikely that any erroneously assigned Glottocodes will be referenced to enough information to meet two of the other six criteria. Kisseran (talk) 08:29, 19 October 2026 (UTC)
Even notable subjects can be merged to other articles per WP:PAGEDECIDE. Katzrockso (talk) 05:21, 11 November 2026 (UTC)
A thought
I am not very familiar with languages on Wikipedia, but I am somewhat familiar with GNG-issues. While I don't necessarily agree that language should be auto-notable, I am also not sure how their case differs, common sense, from some topics we have exceptions for, ex. taxa (species, etc.), astronomical objects (or the perennial issue of minor sport people and events). It might be worth looking into how their relevant GNG exceptions are worded. --Piotr Konieczny aka Prokonsul Piotrus| reply here 01:34, 18 October 2026 (UTC)
Completely agree, as I also do work with astronomical objects sometimes as well. 🪐Kepler-1229b|talk|contribs🪐 01:36, 18 October 2026 (UTC)
One very good reason why we would treat them differently is that there is always a debate as to what constitutes a language and what constitutes a dialect in any dialect continuum. Although I think the vast majority of languages will be notable, I would say that these are going to be clearly notable because people have written about them. GNG is sufficient. A notability guideline can make a useful shortcut towards a presumption of notability, but in the case of languages, speakers of Atwillery may differ with speakers of Atwollery as to whether the latter constitutes a language. As Atwollery speakers have no army, they cannot press their case by conventional means. They thus turn to Wikipedia, and if we have this guideline, they can create the Atwollery page, even though no one in the world has written about their "language" (Well, except for the Atwollery Language League).Of course, the guideline proposes that languages are notable and dialects are not. How do we know which Atwollery is? Only with reliable secondary sources that make the case. Without such, I don't think this guideline settles anything. With such, we can make the case on GNG alone. Sirfurboy🏄 (talk) 12:32, 18 October 2026 (UTC)
But that's exactly the role that the word "confirmed" plays: lects are not languages just because their speakers say so, but because 2ary RS's confirm them as languages. — kwami (talk) 21:43, 7 November 2026 (UTC)
@Blueboar I can list Draft:Baazəm language, which is evidently used as the primary language of a speech community, but not properly discussed in any reliable source due to insufficient documentation. 🪐Kepler-1229b|talk|contribs🪐 22:12, 7 November 2026 (UTC)
Jew Tagging
What (and more to the point, where) is the Wikipedia policy against Jew tagging—the practice of identifying as Jewish every named individual to whom Jewishness can be attributed, often as defined to the Nuremberg Laws? For example, should all sportscasters or all baseball players who have at least one Jewish grandparent be identified as Jewish? MarkBernstein (talk) 22:52, 12 November 2026 (UTC)
I don't think there's a policy on this per se but people have been blocked for doing this in the past, see here. ♠JCW555(talk)♠ 23:02, 12 November 2026 (UTC)
Not a policy, but there's a relevant guideline, WP:CATREL, which among other points (demanding a personal statement of faith) says "Never categorize by a religion of any parents or other ancestors." —David Eppstein (talk) 01:13, 13 November 2026 (UTC)
There was also a long discussion about this last year, with further discussion 9 months ago. I see you participated in the latter. Anomie⚔ 01:59, 13 November 2026 (UTC)
The policy is WP:NPOV, and in particular WP:DUE. We don't need a specific 'don't engage in Jewtagging' policy, since the community has already made it clear enough in the recent discussions linked above that such behaviour is inappropriate, distorting, and contrary to the purpose of an encyclopaedia that aims to reflect proportionally coverage in relevant reliable sources that directly relates to notability etc. Trying to frame a specific policy would prove problematic anyway, given that if, when, where, and how it is appropriate to note ethnicity and/or faith may sometimes come down to editorial judgement. Anyone insisting that an article must assert that a person is Jewish merely because that person has a Jewish grandparent is already violating Wikipedia policy: we don't need a new one. Anyone slapping the bald statement 'X is Jewish' (citing a source) into a biography is either violating WP:DUE, or needs to learn how to write if there is actually a legitimate reason to discuss the matter. Beyond that, context matters. We shouldn't need to inform our readers that Rabbi Ishmael was Jewish, and indeed we don't, thankfully (personally, I'm opposed to treating our readers like idiots), but clearly there are times when it is relevant and needs to be stated explicitly. If so, the article can explain why. If it can't, it's Jew-tagging. If relevance is in question, it can be discussed - with the onus to provide evidence falling on those wishing to include such statements, and with sources merely engaging in Jew-tagging themselves (for whatever reason) given little or no consideration. WP:DUE, once again - content needs to be justified, and not just cited, regardless of what it concerns, and Wikipedia can de better than the one-dimensional labelling that Jew-tagging entails. AndyTheGrump (talk) 03:03, 13 November 2026 (UTC)
Every article that [[Help:Transclusion|transcludes]] a given navigation template should normally also be included as a link in the template, and every navigation template that includes a link to a given article should normally also be transcluded onto that article, so that navigation is bidirectional.
+
Every article that [[Help:Transclusion|transcludes]] a given navigation template should normally also be included as a link in the template, and every navigation template that includes a link to a given article should normally also be transcluded onto that article, so that navigation is bidirectional.Editorsmayuseadditionaldiscretionwhendecidingwhetherasidebarnavigationtemplatemustbebidirectional. Forexample,ifintroducingasidebartoanarticlewouldbemoredisruptivethanhelpful(suchasbyintroducingsignificantvisualcluttertothepage),editorsmayincludeaunidirectionallinkfromthesidebartothearticle.
I made a previous attempt at revising WP:BIDI, which was too WP:BOLD and failed. Now that some time has passed and the guideline has since changed, I would like to try again in a way that is more measured and WP:CAREFUL.
This recent comment by Moxy gave me the idea to re-open this VPP: Really need to amend WP:BIDIRECTIONAL. Content editors simply have a problem keeping up with the mass amount of spam that comes through these. There should also be a discussion about the fact that we have so many articles without a lead image because these are in their place and aren't seen by 80% of our viewership. Basically discussion should be linked spam or educational imagery?
This comment by WhatamIdoing: BTW, I looked into BIDI for sidebars recently, and there were a surprising number of them that don't follow BIDI. {{LGBTQ sidebar}}, for example, contains 207 links but appears in 245 articles – nearly a 20% discrepancy.
WP:BIDI's use of the word "normally" insinuates, perSnow Rise, that WP:BIDIRECTIONAL clearly leaves open the door for practical exemptions from the common rule. PerKatzrockso, the guideline does not strictly mandate that every single navbox entry needs to be bidirectional and many editors erroneously interpret it as a strict no-exceptions rule.
In this edit by Maltazarian, the guideline was updated to be more expansive per this discussion. However, the guideline has continued to be used in a way that is strict in order to remove articles from sidebars.
A common pattern I see is:
1) I will add an article to a sidebar;
2) Per WP:BIDI, I will add the sidebar to the article;
3) The sidebar will often not fit on the page/clutter it up, frustrating editors maintaining the page. As a result, editors will remove it from the page or object to its inclusion, even though the article may improve the sidebar;
An example of this recently is the Ilhan Omar article (revision history). After I added two sidebars to a section in the page, BBQboffinobjectedI don't object to having links of some kind to either immigration or authoritarian issues; my beef is that the sidebars were funneling the text into a narrow column making it painful on the eyes for the WP:READER, especially on a smartphone. If you can add them back in a way that doesn't do that (the sidebars are newly added so this was never a problem in the article before a few days ago), then go right ahead and do so.
4) The article will then often be removed from the sidebar per WP:BIDI, completing the cycle and effectively prohibiting cluttered articles from being added to sidebars altogether.
Another example of the effects of the guideline is that mass removals will be made from sidebars because WP:BIDI does not clarify that additional discretion may be used pertaining to sidebars.
The suggested proposal would correct these issues by loosening WP:BIDI as it pertains to sidebars.
Oppose as strongly as possible. If anything, we need to strengthen it and remove the ambiguity. We are already plagued by a number of tangential, badly constructed sidebars that take up massive amounts of space while adding no useful encyclopedic content. If it clutters the page or frustrates editors, then why do we need it in the sidebar? PARAKANYAA (talk) 18:50, 18 November 2026 (UTC)
The idea is that loosening the guideline would encourage editors to focus less on WP:BUREAUCRACY and more on evaluating content on the basis of its merits ~ Alexandraaaacs1989 (talk) 19:17, 18 November 2026 (UTC)
The merits of a sidebar is that it is a tightly related collection of links. None of this is that. PARAKANYAA (talk) 19:40, 18 November 2026 (UTC)
I think a bigger problem is that people very often disagree on what constitutes "tightly related". SuperPianoMan9167 (talk) 19:41, 18 November 2026 (UTC)
Yes: a "tightly related" group of 500 links, because 500 articles could benefit from the sidebar's links to a handful of key articles, but BIDI is being enforced to require that all 500 displaying articles also be listed in the sidebar. WhatamIdoing (talk) 22:46, 18 November 2026 (UTC)
That's what "See also" is for. Those 500 articles are not "part of a series". Sirfurboy🏄 (talk) 22:57, 18 November 2026 (UTC)
Here's the problem I see:
Alice: Oh, this article is about ____. People reading this article may be interested in a quick way to get to the main articles about ____. I'll add the sidebar.
Bob: WP:BIDI says you can't add the sidebar about ____ unless you put [this article] in the sidebar. I'm adding [This article] to the ____ sidebar. Now there are 11 articles in the ____ sidebar.
Chris: People reading this other article may be interested in a quick way to get to the main articles about ____. I'll add the sidebar.
Bob: WP:BIDI says you can't add the sidebar about ____ unless you put [this other article] in the sidebar. I'm adding [This other article] to the ____ sidebar. Now there are 12 articles in the ____ sidebar.
David: People reading this article over here may be interested in a quick way to get to the main articles about ____. I'll add the sidebar.
Bob: WP:BIDI says you can't add the sidebar about ____ unless you put [this article over here] in the sidebar. I'm adding [This article over here] to the ____ sidebar. Now there are 13 articles in the ____ sidebar.
...
Yael: People reading this little article may be interested in a quick way to get to the main articles about ____. I'll add the sidebar.
Bob: WP:BIDI says you can't add the sidebar about ____ unless you put [this little article] in the sidebar. I'm adding [This little article] to the ____ sidebar. Now there are 35 articles in the ____ sidebar.
Zed: People reading this new article may be interested in a quick way to get to the main articles about ____. I'll add the sidebar.
Bob: WP:BIDI says you can't add the sidebar about ____ unless you put [this new article] in the sidebar. I'm adding [This new article] to the ____ sidebar. Now there are 36 articles in the ____ sidebar.
...at which point, we have not just clutter, but clutter caused by thoughtless enforcement of WP:BIDI, when what was actually wanted in all of these cases was just links to the main articles about ____ and not links to all the non-main articles that could benefit from a link to just the main articles.
I support the proposed addition, and I suggest additionally the following two principles:
Sidebars should be short. I don't know if we should define 'short' as a maximum of 20 links or 50 links, but it should not be infinitely expandable, and it probably needs a specific number stated as an anchor. Sidebars that currently contain hundreds of links should either be converted to footer navboxes, or split to create a shorter sidebar with the main articles and a longer (BIDI-compliant) footer navbox with all the articles.
Sidebars should focus on major articles. For example, if the subject of the sidebar is Philosophy then the sidebar should have links History of philosophy, Epistemology, Ethics, Logic, Metaphysics but links to sub-subtopics such as Type physicalism, Mind–body problem, and Neutral monism should be relegated to footer navboxes. In some cases, the sidebars will be BIDI-compliant or nearly so (e.g., if the subject of the sidebar is a particular book series, then the only links wanted in the template are author+the books, and the sidebar could reasonably be used only on those articles), but this will be neither required nor expected.
I can understand the problem you're looking to solve, and it's somewhat different (and opposed) to the problem OP is looking to solve. I think that to satisfy your concern it would be sufficient to loosen BIDI to allow transclusion of the template without including a link to the page on which it's transcluded.
I think OP's concern is primarily with the reverse case, that transclusion of the template might be opposed on grounds unrelated to the template itself but based solely on considerations relating to the page (e.g. that it's already cluttered with other sidebars). This would mean that the link would have to be excluded despite its potential utility to the template.
I actually agree with both concerns, but they are opposed in that your concern is to allow the utility of templates on pages they don't link to while keeping their size manageable, and OP's would allow for the unchecked expansion of templates.
I'm not opposed to loosening BIDI to accomodate both, but I think a safeguard like the numerical limit would be vital, as well as to make template guidelines stricter in CTOPs. That could allow us to add the flexibility for templates to work well in 90% of the project while preventing the misuse of that flexibility in the 10% that's subject to the most intense POV-pushing. Samuelshraga (talk) 20:00, 18 November 2026 (UTC)
I think OP's concern is primarily with the reverse case, that transclusion of the template might be opposed on grounds unrelated to the template itself but based solely on considerations relating to the page (e.g. that it's already cluttered with other sidebars). This would mean that the link would have to be excluded despite its potential utility to the template. Exactly yes, this is my primary concern
OP's [suggestion] would allow for the unchecked expansion of templates An important point I think is relevant here is that unchecked expansion of sidebars is currently permitted, and this guideline would maybe slightly exacerbate the issue, but it by no means would be a dealbreaker. I agree that clearer guidelines about what constitutes a tightly-related article seem due considering the amount of disagreements that seem to arise over tight relatedness, and I think this would be a useful idea to examine in subsequent VPPs (though I find a hard numerical ceiling to be a bit too harsh) ~ Alexandraaaacs1989 (talk) 20:34, 18 November 2026 (UTC)
I think that the "unchecked expansion of sidebars" is something we need to stop. WhatamIdoing (talk) 22:48, 18 November 2026 (UTC)
I reverted the April 2026 bold change to the wording of WP:BIDI that encourages more "unchecked expansion of sidebars". As I noted in the April 2026 RfC , past discussions have not reached any conclusion about altering the wording of WP:BIDI to make it truly bidirectional (i.e. requiring any page with a navbox to be an entry in that navbox). Katzrockso (talk) 22:58, 18 November 2026 (UTC)
I don't think we need "a hard numerical ceiling". I do, however, think that we need a number. "About 20 links" is not "a hard numerical ceiling", but it should give an editor a clear indication that if they're putting 100 links in the sidebar, they're screwing up (and need to switch to the footer style). WhatamIdoing (talk) 23:30, 18 November 2026 (UTC)
@Samuelshraga, thanks for that note. You're correct that I don't really want a "unidirectional link from the sidebar to the article". Instead, I want to permit the inclusion of the sidebar in a relevant but peripheral article without bloating the sidebar to include a link to the peripheral article. It should be unidirectional out of the peripheral articles, rather than unidirectional into 100+ peripheral articles. WhatamIdoing (talk) 23:38, 18 November 2026 (UTC)
The current proposal is to allow unidirectional links from the sidebar to the article, so this would mean you oppose the proposal. SuperPianoMan9167 (talk) 00:10, 19 November 2026 (UTC)
I actually think the current proposal would allow both. Samuelshraga (talk) 07:32, 19 November 2026 (UTC)
Given that both this and the almost simultaneous post to WP:NOR/N (which you strangely admit isn't a suitable place to bring it up) make multiple references to the editing disagreement you've had with Sirfurboy and just taken them to ANI over, this comes across as closer to WP:FORUMSHOP behaviour than you intended. If you want a genuine discussion on the issue have a single place where that's discussed instead of spreading it across multiple forums and hoping one vote ends up your way which is what this is starting to give the appearance of.
Also, once again as you've been warned about previously, stop editing your comments after people have replied. Rambling Rambler (talk) 19:34, 18 November 2026 (UTC)
One comment… if a nav template has grown to the point where it clutters up articles when presented as a sidebar… consider changing it to bottom box format. Blueboar (talk) 19:38, 18 November 2026 (UTC)
Many of these exist alongside the footers, or are larger than the fooder. Possibly the worst example, {{Conservatism US}} (every attempt to trim it is strenuously objected to), is somehow larger than {{Conservatism US footer}}. PARAKANYAA (talk) 19:45, 18 November 2026 (UTC)
Do we have articles that use both that sidebar navbox and that footer navbox? I would think it should be one or the other.
Shift the discussion away from arguments about the content of the navbox and focus it on placement. Sidebars should be small… Footers can be large. Blueboar (talk) 20:05, 18 November 2026 (UTC)
Sidebars should be small… I agree, but not everyone does. Most editors of these templates want them to be large. PARAKANYAA (talk) 20:22, 18 November 2026 (UTC)
I haven't done a comprehensive check, but I think it's common for articles to have both. For example, the two templates on conservatism that Parakanyaa links have substantial overlap; in fact, one transcludes the other. And neither is BIDI-compliant, as they contain links to hundreds of articles, but are used only in dozens. WhatamIdoing (talk) 23:04, 18 November 2026 (UTC)
support' and think we should be more stringent. The community in general is moving away from the sidebars as they're being deleted on Mass..... Not as quick as there being made but still moving the right direction (in my view). We just need content editors to realize that the mass spamming of these is done with good intention....but our software will omit them from the mass majority of viewers.. We should make clear that this is a sort of see also spam run around is concern. Just because someone created or added a link doesn't mean the community has to accept 3 4 5 6 7 sidebars in one article. That should be reflected in our guideline. Waste of time for Content editors that have to deal with every inclusion or exclusion discussion when included in a sidebar supported by a guideline that promotes spam over prose text an educational imagery. Would support wording like we have with info box inclusion....that is that an addition to a sidebar doesn't automatically get included in an article simply because someone added a link in sidebar. Let's try to cut out the time sync that content editors have to deal with.Moxy🍁 19:47, 18 November 2026 (UTC)
That's another possibility for weakening BIDI in the name of reducing clutter:
An article should normally not transclude more than one or two sidebar navboxes, no matter how many sidebars link to them.
There's probably a better way to phrase this, but if we decide to create a series of small sidebars (e.g., a Taylor Swift discography sidebar, Taylor Swift filmography sidebar, Taylor Swift awards sidebar, Taylor Swift personal life sidebar, Taylor Swift tours sidebar, etc.), they does not mean that the Taylor Swift article itself needs to transclude all of them, or that they should be banned from linking to the Taylor Swift article. BIDI should not force including too many sidebars in any article, and BIDI should not ban inclusion of an obviously central link just because the sidebar isn't wanted at that central article. WhatamIdoing (talk) 23:45, 18 November 2026 (UTC)
Strongly Oppose the suggestion for what that's worth. All I see it resulting in is sidebars that are functionally unusable because they get turned into an inclusionist's wet dream of just a million "unidirectional" links to every article that is even tangentially related that no one then bothers to read on the few articles they are actually then placed, and more likely than not will see the sidebars themselves removed from almost every article because of all the space they take up like a crappy 2000s banner ad.
Between sidebars that are becoming articles unto themselves, see also sections that are extremely generous in argument as to how things are related, and external links sections that are borderline advertisements for websites the desktop Wikipedia experience increasingly feels like it needs a bespoke adblock service just to be able to read the article. Rambling Rambler (talk) 20:03, 18 November 2026 (UTC)
I think the biggest complaint content editors have is that the side bars take up room where an educational image would be more suitable because sidebars aren't seen by the vast majority of readers. Perhaps the guideline could mention the fact that we have {{if mobile}} that is a work around so that content editors can display an educational image over random link span. Moxy🍁 20:22, 18 November 2026 (UTC)
To be honest, even as someone who abhors the "mobile first" internet we are now stuck in, I think the fact that is de facto the case should instead highlight maybe instead of continuing to see the endless waste of editor time on yet more arguments over how best to use sidebars it should instead be recognised that they are now effectively redundant (because almost no one uses them but the people wanting to put links in them) and in the medium-term should seek to remove them entirely as a now redundant item. Rambling Rambler (talk) 20:32, 18 November 2026 (UTC)
Option A: sidebars are now visible for mobile users and start collapsed (right side), while they start expanded (left side) by default for desktop users, and if there's clutter there's a new parameter you can use to force it to start collapsed regardless of platform; click button to expand/collapse
Option B: deprecate sidebars and merge all existing sidebars into navboxes, improve navbox visibility by moving them to "See also" sections as new norm, make navbox norm to be expanded by default (overridable), and merge sidebars into navboxes (new Wikipedia:MOS norms would need to be established) (exceptions could be made for navboxes like Authority Control Database, which could remain at the bottom of the page). [EDIT:] We could even have all sidebars start collapsed by default (on mobile and desktop) to save real estate, I wouldn't necessarily be opposed to this.
To help you better understand my perspective, the reason I think sidebars are superior to navboxes is due to how sidebars are seen by most desktop readers, whereas most readers have no idea navboxes exist or to even look out for them (I still remember stumbling upon my first navbox a decade ago and thinking "what the hell is this?").
I drafted two WP:BOLD proposals, let me know what you think ~ Alexandraaaacs1989 (talk) 21:03, 18 November 2026 (UTC)
The fact that sidebars are so visible is the problem with them. We cannot have 1/3rd of the screen on many of our most visible articles being taken up by a useless taxonomy box. PARAKANYAA (talk) 21:09, 18 November 2026 (UTC)
Making sidebars visible for mobile users won't work as they'll take up the entire width of the page (and push down the rest of the content) regardless of whether they're collapsed or not. SuperPianoMan9167 (talk) 21:09, 18 November 2026 (UTC)
Both are terrible, because they both constitute the same problem which is a proposal that boils down to "let's stuff even more links into endless list of links no one will want to read because they're endless lists of links". You seem inherently inclined on every aspect of Wikipedia to believe the problem is that there isn't enough text already in existence and that somehow eventually if you add enough text it will solve every issue.
Wikipedia is meant to be an encyclopaedia, something that is easily accessible and gives you the summary of something. All this does is make achieving that harder and increases friction. Rambling Rambler (talk) 21:58, 18 November 2026 (UTC)
You asked me what I thought and I gave you my view. None of my comment was a personal attack, but if you'd like a personal comment maybe notice how once again you've started responding to practically everyone in a discussion and dominating it (mere days after an ANI where the closer specifically gave you warning about this).
I said I didn't support it and why. Shoving two infoboxes effectively reiterating something that I've already said I strongly opposed as a reply to me is tantamount to WP:BLUDGEON. Rambling Rambler (talk) 22:40, 18 November 2026 (UTC)
Take it to my talk page, or take it to an ANI. Just stop yelling at me here ~ Alexandraaaacs1989 (talk) 23:33, 18 November 2026 (UTC)
Gordon Bennett, a handful of words bolded for emphasis is not yelling... Rambling Rambler (talk) 23:50, 18 November 2026 (UTC)
When these were first omit fom mobile view I remember there being a discussion about having and "Editor skin" (a simple add-on) that would allow these to be displayed to registers users who opt in by way of a tool or gadget ...a preference thing..... regardless if they're on mobile or desktop view. The discussion never really evolved because of data overload concerns on mobile view I guess..... But I'm wondering if someone out there can make us a skin so that there's an editor mode so that we always see them? Moxy🍁 22:07, 18 November 2026 (UTC)
Strongly oppose a change that would remove the only meaningful control we have for the over-large synthetic visually intrusive creations. This is the wrong question. SIDEBARS need to be smaller, with fewer links. Per Rambling Rambler, the effect of this will be to turn them into complete taxonomies, which means they will be monstrously intrusive on those pages they do get included on. Anything will then be added and any removals will be resisted. These consume way too much time as it is, and this change will exacerbate the problem further. Sirfurboy🏄 (talk) 20:53, 18 November 2026 (UTC)
what's horrible is the community has to waste so much time on these despite the fact that they're not seen by 80% of our viewership. The foundation has recognized that these are inaccessible and a data overload that are not beneficial overall. Moxy🍁 21:10, 18 November 2026 (UTC)
What's the context for the 80% figure? —Rhododendritestalk \\ 22:24, 18 November 2026 (UTC)
Just rounding up some stats "76.32% of all traffic to Wikipedia originates from mobile devices, while only 23.68% comes from desktops".Moxy🍁 22:42, 18 November 2026 (UTC)
Our stats are very interesting.... they separate the app views instead of lumping them in together with mobile views. I believe many are unaware of this fact...that is they're not seen in mobile view and the app and that's why there's so many disputes over people just implementing {{if mobile}}Moxy🍁 23:01, 18 November 2026 (UTC)
My cynicism would say that the reason it's going up for desktop is AI related bots and scraping. Rambling Rambler (talk) 23:04, 18 November 2026 (UTC)
That was my thought, too, and then I forgot it by the time I actually posted the above.:) —Rhododendritestalk \\ 23:07, 18 November 2026 (UTC)
I agree with @Sirfurboy that SIDEBARS need to be smaller, with fewer links. WhatamIdoing (talk) 23:34, 18 November 2026 (UTC)
The problem I have with sidebars is they should require a much broader consensus for creation than they currently do, and often involve a nontrivial amount of OR and/or POV. BIDI should apply, and all of the articles that would be included should be notified of its proposed creation (and inclusion of that article). As it stands, they have a bizarre kind of implied framing authority based on [usually just one or two] editors' sense of "relatedness". I'm guessing this proposal has a background in OP's Template:Authoritarianism during the Trump presidencies sidebar? There's certainly consensus to characterize a broad swath of Trump's actions and style as authoritarian, but in many of the linked articles, the template is the only place the word "authoritarian" appears in wikivoice, and the grouping seems more like "Trump scandals the template creator considers typical of authoritarianism" rather than something rigorously sourced. So, on the whole strong oppose as moving in the wrong direction. —Rhododendritestalk \\ 22:34, 18 November 2026 (UTC)
@Rhododendrites, imagine a fairly simple sidebar. The OP mentioned {{LGBTQ sidebar}}, so consider the much shorter, simpler version I've mocked up here. It has about 20 links in it (vs. ~225 in the original). Can you imagine this being appropriate for more than these 20 articles, e.g., as a quick way to get back to the main/most popular articles on this subject? My desire to not have literally hundreds of articles in sidebars is why I think that BIDI needs to be relaxed for sidebars. WhatamIdoing (talk) 23:23, 18 November 2026 (UTC)
What are some examples of articles that should have this sidebar, but should not be included in the sidebar? —Rhododendritestalk \\ 23:57, 18 November 2026 (UTC)
We could also have a [[Special:WhatLinksHere/Template:LGBTQ sidebar|What links here?]]What links here? hyperlink at the bottom of non-BIDI sidebars ~ Alexandraaaacs1989 (talk) 00:28, 19 November 2026 (UTC)
Why would we need to include this in the sidebar itself if anyone who wants to see what links to it can already do so by going to the sidebar page? SuperPianoMan9167 (talk) 00:31, 19 November 2026 (UTC)
Support. Practically, strict bidirectionality is the cause of navbox bloat - see WhatamIdoing's comments above. Anything loosening it will help us reduce the size of overburdened navboxes with too much going on.Katzrockso (talk) 23:29, 18 November 2026 (UTC)
Oppose, strict bidirectionality is not what is causing sidebar bloat. At a random look at the sea of blue that is {{LGBTQ sidebar}}, I saw the arbitrary collection of "Violence against LGBTQ in X" entries, with a short number of entries running from Belize to the US. The sidebar is in none of these articles. Some are not even articles; the sidebar is being used to hold Redirects to sections. CMD (talk) 23:58, 18 November 2026 (UTC)
I think this is a wonderful point but I'm also thinking many think things have to be done in baby steps. Moxy🍁 04:14, 19 November 2026 (UTC)
Oppose. I thought we had already resolved Alexandraaaacs1989's long-term attempt to use sidebars as a means to push a POV, but apparently not. Thebiguglyalien (talk) 06:54, 19 November 2026 (UTC)
Oppose as written. I would be more open to relaxing bidirectionality if they came with safeguards to prevent the overloading of sidebars, clearer standards for how tightly related an article would need to be for inclusion as a link, and probably tighter rules for sidebars in CTOPs. Otherwise I think this proposal will exacerbate existing problems of clutter and POV-pushing. Samuelshraga (talk) 07:39, 19 November 2026 (UTC)
Technical
Phase 2 Semantic Search A/B test live on web: help us test!
Hi all,
I’m writing to let you know that the Reader Growth team’s A/B test of "semantic search”, or natural language search, capabilities on the web version of Wikipedia went live today. We are trying this to make it easier for people to find the information they’re looking for on the wikis so that, as we face declining pageviews, Wikipedia can be a better destination for learning and discovery. Here is an example search results page that the treatment group could see; you can also try more semantic queries on this page (please check that you have &mpo=semantic-search-for-web:hybrid-srp at the end of your URL to see semantic results if you do multiple searches).
We increasingly have been hearing from readers that they want to be able to ask questions to Wikipedia. This makes sense, since more and more people are getting used to using chatbots. But we also know that it is important for Wikipedia content to be presented in the way that volunteers wrote it. So in this feature, readers will ask natural language questions – but rather than generating answers, it returns the excerpts from Wikipedia articles that may answer their question. So far, as we’ve shown this to volunteers, it sounds like we’re on the right track! (but of course I want to hear what you think).
Check that Phase 2 thread for more details, including research about the gaps in our current search experience, the results of a previous semantic search test on the apps, the differences between the apps and the web, and metrics we are looking at for this current test. The project page also has much more information about all of our thinking, research, and progress in this area.
The left screenshot illustrates the current experience of searching on Wikipedia mobile for "who invented airplanes." The screenshot on the right shows the experience asking the same question in the experimental semantic search treatment.
What this test is:
Semantic search means retrieving information based on the meaning, concepts, or contextual relationships of someone’s query. Currently Wikipedia search does not support semantic search, and instead fully relies on lexical retrieval, which is based on exact search terms, or keyword matching.
This test will be shown to 1% of desktop and mobile English Wikipedia readers typing in the search bar, who will see the existing "Search for pages containing..." call to action (CTA) as usual below the typeahead suggestions. Clicking that CTA, or hitting enter on their query, will take readers in the test's treatment group to an advanced search results page that will include semantic results. This page will also include a survey question asking whether users found the results helpful, and inviting them to write out more feedback.
I also want to note that the search results page in the treatment is not as fully featured as the regular search results page (e.g., it doesn’t have the red link to create a new article, and it doesn’t have the search results from sister projects). That’s not a long-term design decision; rather, we built a simple page to conduct and learn from this test.
The test will be turned off in December. If early results are promising, we will come back to discuss them together and what we think should happen next.
What we’re asking for your help with:
We have done some early work identifying risks and edge cases, particularly related to queries where semantic results could be easily misinterpreted or even harmful. We’re thinking about 1) situations in which people’s searches could bring up some of the more sensitive content on the wiki, and 2) situations where our search algorithm might present results that appear to answer the query, but in a way that does not seem neutral. For example, we know an issue exists with block quotes – sometimes the search returns a block quote from a specific point of view that is presented like it is a neutral article excerpt, which is misleading. This is an improvement we’re working on (it is a technical challenge for the search algorithm to identify block quotes appropriately).
As you try out various queries, please help us be on the lookout for risks we may not be aware of yet. If you find any, please share a URL and screenshot of the results, along with a description of your concerns, at the Information Retrieval Phase 2 project talk page. We think community testing of this feature will be crucial to build something useful for our billions of readers while also taking care not to cause harm or create confusion. Thank you for your help. EBlackorby-WMF (talk) 22:19, 10 November 2026 (UTC)
I clicked the link to try queries but it doesn't work, at least on my end. The link takes me to https://en.wikipedia.org/w/index.php?title=Special:SemanticSearch&mpo=semantic-search-for-web:hybrid-srp but all I see on there is a link to "Switch to classic search" in the middle of the page. – Scyrme (talk/solidarity) 22:55, 10 November 2026 (UTC)
@Scyrme -- thanks for trying it! Yes, so from that page, try typing a question into the search bar and pushing enter/search (e.g. "What is the difference between a tuba and a sousaphone?") MMiller (WMF) (talk) 22:58, 10 November 2026 (UTC)
I see! Sorry, it wasn't clear initially. I thought the usual search bar would exit the semantic search testing page and take me to classic search results, and expected another search bar within the page area where the "Switch to" button is. Seems to work well so far, even when I try strange questions (eg. why do fish dig? → received a snippet about fish that burrow in mud) or questions that contain wrong assumptions (eg. why do cats bark? → received snippets about cat vocalisations). – Scyrme (talk/solidarity) 04:12, 12 November 2026 (UTC)
Thanks @GrinningIodize! Your experience with the "did you mean" (DYM) feature is partly due to our not yet having tailored the suggestions for semantic searches, as you also discovered when you tried the same query in classic search and got the same suggestion. We've discussed this a bit as a team and would be interested in updating DYM for semantic searches as a future improvement. I know the Search team also has been investing over time in the existing DYM logic as well and can pass on this example to them so we at least can avoid the ouroboros of suggesting the same correction for the thing that didn't need to be corrected:) SherryYang-WMF (talk) 17:24, 13 November 2026 (UTC)
Thank you and your team for working on this. In my opinion, this has very high potential.
At the risk of repetition, I would like to bring up articles about current events. Information in them can be outdated or unreliable, but if we extract snippets from them, we likely need to indicate their currency in the snippets.
If I have more concerns, I will bring them up. Thank you all once again! LightNightLights (talk • contribs) 18:27, 16 November 2026 (UTC)
So, the first time I clicked on "log in", I got a text page about a parserURL (or some such) failure. Second click of log in worked, I've seen this before, it happens. But when I logged in, I got a message saying "Authentication was successful but your session has expired. Please click "Log in" to recover it.". That's new. More meatballs in the backend spaghetti code? - The BushrangerOne ping only 03:27, 12 November 2026 (UTC)
@Matma Rex: For the record, just had it happen again (although this time there wasn't the initial parserURL thing, just went straight to "successful but"). - The BushrangerOne ping only 21:31, 14 November 2026 (UTC)
And just had "invalid return URLtoken" on first time clicking 'log in'. - The BushrangerOne ping only 03:56, 17 November 2026 (UTC)
Me too, on the "Authentication was successful but your session has expired. Please click "Log in" to recover it." thing, about 12:30 today (UTC). --Redrose64🌹 (talk) 15:43, 17 November 2026 (UTC)
.. page have been removed from your watchlist.
Today I notice that when I unwatch a page by clicking the "unwatch" tab from a recent diff of that page, the browser pops up a box says "[page name] and its talk page have been removed from your watchlist", with a big Undo button. This is both annoying and unnecessary - I can see it's been removed because the "unwatch" tab changes to "watch", and if wanted to undo it I would just click that tab again. Can we please not have the box - or at least make it optional.
I'm using MonoBook, Firefox 115.45.0 on Windows 7. Mitch Ames (talk) 12:05, 13 November 2026 (UTC)
Maybe related to this? As well as the new popup when unwatching, I also see a larger, more persistent box when I click "watch". Mitch Ames (talk) 12:14, 13 November 2026 (UTC)
Yep, these are related - my team just rolled out new watch star popover behaviour to make it easier to add labels to your watched items. Previously, the same popover was displayed as a toast notification, the main change is that the location has moved so that it's closer to the Watch star that you just clicked. Additionally, after unwatching you can now Undo the action, which preserves your expiry date and labels, if they were set. I see what you're saying about already seeing that it's unwatched. Maybe the popover with Undo should only be displayed if you had an expiry or label configured? I worry it might be confusing to show it some times and not others, curious what others think! Samwalton9 (WMF) (talk) 12:46, 13 November 2026 (UTC)
It is somewhat regrettable that the unwatch popup doesn't seem to have a unique ID or class distinct from the watching popup so it could be hidden in one's CSS. Nardog (talk) 12:59, 13 November 2026 (UTC)
Yes that is unfortunate. You can hide both popups with this in your CSS:
If you do this but temporarily want them on a page (the watch popup adds features you may sometimes want) then you can add ?safemode=1 to the url. User:PrimeHunter/Safe mode.js makes a link under Tools to do it. PrimeHunter (talk) 13:57, 13 November 2026 (UTC)
@Mitch Ames: You mentioned doing it from a diff. If the url already has a ? then add &safemode=1 instead. The script automatically picks the right one. PrimeHunter (talk) 14:02, 13 November 2026 (UTC)
Another option if you have an article link to hover over would be to enable Wikipedia:Tools/Navigation popups via the Preferences → Gadgets → Browsing option.
I generally use the Action → un option in the hover window to unwatch pages as I review my watchlist, and it's pretty convenient (and appears to bypass the new "Undo" functionality). — SirOlgen (talk) 19:53, 13 November 2026 (UTC)
"Watch"/"Unwatch" tab shenanigans again
Some time back this was briefly a thing, but then it went away. Just now I discovered that clicking the "Watch"/"Unwatch" tab at the top of a page produces a popup dialog box confirming it with an "Undo" button, directly below the tab, vis-a-vis the previous brief "this happened" box in the upper right that faded away. This change is, frankly, obnoxious and undesirable for me - is there any way to turn it off? - The BushrangerOne ping only 22:23, 13 November 2026 (UTC)
Thank you. I've used the css there. I did like the little 'quickly fading box' in the upper right that it previously did, but... - The BushrangerOne ping only 23:19, 13 November 2026 (UTC)
It should update automatically. This was a more complex move, though, since the pagename already existed. It looks like the deletion of London Underground S Stock didn't result in the sitelink being removed from Wikidata, so when the page was moved to that title it didn't update. Maybe it all happened a bit too quick for the systems to keep up with? I've already fixed this on Wikidata. Maybe @Lydia Pintscher (WMDE): might know more? Thanks. Mike Peel (talk) 20:15, 13 November 2026 (UTC)
A glitch with search bar
In my experience, the search bar does work on mobile devices. However there's a glitch where the FIRST time you tap the search bar (that is set up to show results with a particular PREFIX) on a page such as Wikipedia:Vital articles/Level 4 or Wikipedia:Help desk, you are taken to a blank page containing the search bar only that says "Search Wikipedia". This search bar will search the entire site, but only in the article namespace. Then if you press the back arrow, and click the search bar a SECOND time, you will stay on the same page instead of being taken to a blank page, and you can search within the given PREFIX space. This is my experience with Google Chrome on mobile, and this has been a glitch with all search bars searching with a prefix for a long time. ~2026-60081-75 (talk) 00:01, 14 November 2026 (UTC)
This also happens to me with talk-page search-bars. This issue has been reported and fixed before, but I do not have the bug discussion at hand. LightNightLights (talk • contribs) 10:50, 14 November 2026 (UTC)
I believe this is phab:T402078 ("InputBox on mobile skin (Minerva) loses focus on first click, jumping to main search bar"). HTH. Quiddity (WMF) (talk) 21:15, 15 November 2026 (UTC)
Bypassing linkrot with a template parameter
Want to add an #ifexist function to {{draw links}} so when a non-existent tennis event page is called with the |tour= parameter via the template it displays Singles – Doubles in plain text instead of [[page title – Singles|Singles]] – [[page title – Doubles|Doubles]] to avoid linkrot per WP:REDLINK. The |tour= param variant is only used on 2026 ATP Tour and 2026 WTA Tour season tennis results pages to separate/distinguish it from namesake yearly templates, namely {{2026 ATP Tour}} and {{2026 WTA Tour}}.
Tried {{#ifexist:{{{1}}}|...Singles}} for Singles, Doubles and Mixed doubles which doesn't seem to work (see diff).
I want the last testcase in Template:Draw links/testcases to display Singles - Doubles only for the "2027 US Open" event and not be redlinked. 8rz (talk) 13:06, 14 November 2026 (UTC)
@8rz: The main page 2027 US Open does exist (as a redirect) so I have changed the testcase to 9999 which works as you want.PrimeHunter (talk) 16:29, 14 November 2026 (UTC)
I think the sandbox code also needa adjusting to account for non-existent page. See the testcase with the black background with the |white= parameter. It displays erroneously; it should display (S, D), not Singles – Doubles. That needs fixing before the template's code is synced with the sandbox. 8rz (talk) 16:43, 14 November 2026 (UTC)
additional tests (testcases 3 & 4) give the opposite results of what I want. |tour= with |white= displays (S, D) and |white= gives Singles – Doubles. I need it it display the opposite. White is only to be used in navs' bottom row for color contrast as (S, D), whereas tour is to be used only on yearly tennis pages where the full Singles – Doubles version is required (wikilinked only when page exists, otherwise display in plain text). 8rz (talk) 17:18, 14 November 2026 (UTC)
@8rz: I have repeated the code to choose words or letters for the case where ifexist is false. Templates often get an annoying amount of repetition because they cannot assign variables. I haven't handled the scenario where tour and white are both set like in your 2027 Australian Open test case. Does that ever happen for real? PrimeHunter (talk) 05:41, 15 November 2026 (UTC)
Well, the 2nd conditional gets the job done. The white & tour testcase I added it just for testing purposes; there's no real case where one'd use both (white's for navs, tour for articles). Thanks for the help. Much appreciated. 8rz (talk) 14:17, 15 November 2026 (UTC)
@PrimeHunter, could you be so king enough to update the template's code so I don't have to post an edit request. Thanks. 8rz (talk) 14:28, 15 November 2026 (UTC)
Issue (redlinks), unfortunately, still not fixed. Not sure why the testcases are displaying properly, but real-life cases aren't. See User:8rz/sandbox#Dl2 test
{{Dl2|2026 lorem ipsum|MS=1|WD=1|tour=1}}
Singles–Doubles {{Dl2|1987 Stockholm Open|tour=1|X=1}} Mixed doubles {{Dl2|2026 atp finals|S=1|D=1|tour=1}}
Singles–Doubles {{Dl2|2026 aTp finals|S=1|D=1|tour=1}}
Singles–Doubles {{Dl2|2026 ATP Finals|S=1|D=1|tour=1}} Singles–Doubles {{Dl2|2026 ATP Finals|S=1|X=1|tour=1}} Singles–Mixed doubles {{Dl2|2027 ATP Finals|D=1|X=1|tour=1}} Doubles–Mixed doubles {{Dl2|2027 ATP Finals|D=1|X=1}}
(D,X) {{Dl2|2027 ATP Finals|S=1|D=1|X=1}}
(S,D,X) . 8rz (talk) 12:16, 18 November 2026 (UTC)
:After additional testing figured out the source of the problem. Digits followed by a lowercase character (2026 atp finals, 2026 aTP Finals) hide redlinks, otherwise (2026 ATP Finals) they are displayed. 8rz (talk) 12:40, 18 November 2026 (UTC)
nvm, that's not it. 8rz (talk) 12:43, 18 November 2026 (UTC)
New tool for comparing language editions
Hi all, at Junction 2026 in Helsinki we built Parallax, a read-only tool that puts the Finnish, Swedish, German, English, Russian, Estonian and Ukrainian editions of an article next to each other sentence by sentence. For each statement it shows how the other editions put it and when each of them added, reworded or removed it, with a link to that revision. You can also pick a date in the past and get the comparison as it stood then. A separate list collects statements that one edition removed while the others still have them, together with the edit summary of the removal. It works for any article that has a Finnish version (a new one loads in a minute or two and keeps one state per year, while the preloaded Winter War has every revision).
Sentences are matched with a multilingual embedding model (bge-m3) and Gemini decides whether two of them say the same thing and translates them into English. There's also a page where you paste a chatbot answer and see which editions back each of its statements. Pasted text goes to Gemini and the checked answer is stored so it can be opened again. No user names are stored.
It isn't on Toolforge but runs on our own server, which stays up for the next few months. We built it as a hackathon entry and nothing more is planned right now, but if people find it useful we could talk about taking it further. The code is on GitHub under MIT. TimKicker (talk) 12:52, 15 November 2026 (UTC)
Editing content in templates via VE - where do things stand?
It's a very old issue that content inside templates is difficult to edit in Visual Editor, involving opening a template dialogue box, finding the parameter, and editing wikitext within a little text box. It's a bit of a pet peeve for templates that include a lot of content, like the many lists that use {{div col}}. Just curious if there have been developments since I last checked like 8 years ago?:) —Rhododendritestalk \\ 00:47, 16 November 2026 (UTC)
I'm afraid nothing has moved on this front. The old task requesting this feature is T52355. Matma Rextalk 11:24, 16 November 2026 (UTC)
It's very disappointing how much a feature used by newcomers on tons of Wikipedia languages has almost zero development going on, apart from edit checks I don't remember anything major the last few years. Sjoerd de Bruin(talk) 18:19, 16 November 2026 (UTC)
Thanks. Disappointing indeed. Such a common issue. Perhaps PPelberg (WMF) knows what's up with this one? Seems like a perennial complaint the WMF would receive from newbies and long-timers alike. Is there some major technical blocker? —Rhododendritestalk \\ 03:41, 19 November 2026 (UTC)
Bugged latex in the dark mode of the vector skin
I'm reporting that latex got bugged in the dark mode of the old vector skin. It used to be fine just several week/months ago for me, but now it's illegible. I haven't tested it in the new skin yet.
try uninstalling extensions in chrome I had this issue and that was the cause of it ~2026-60601-85 (talk) 15:04, 16 November 2026 (UTC)
I'm using Mozilla. What extensions specifically? Tim Ocean (talk) 15:53, 16 November 2026 (UTC)
When reporting a problem, always link to an example page and try to follow the other advice in the edit notice that appears when you edit this page. – Jonesey95 (talk) 16:06, 16 November 2026 (UTC)
(school change thing so same person) most of these are base html markup, and not a part of Wikipedia. Wikipedia's dark mode implementation acounts for LaTeX already, so something must be modifying it. it just happened to be extensions for me I think. ~2026-60615-70 (talk) 16:23, 16 November 2026 (UTC)
I looked at Arithmetic progression, the apparent article in question in dark mode using Brave browser on Mac OS, logged out, default Vector 2022 skin, and the equations look fine to me. It looks like the OP is reporting a problem with Vector, which does not have a MediaWiki-supported dark mode, as far as I know. Maybe they are using Wikipedia:Dark mode (gadget), in which case problems should be reported at the talk page for the gadget. – Jonesey95 (talk) 18:01, 16 November 2026 (UTC)
The dark mode in your preferences is a gadget that is best described as unsupported, especially since the rollout of dark mode native for Vector 2022 and Minerva. Any other dark mode you might be using is probably not something we have control over. Izno (talk) 18:06, 16 November 2026 (UTC)
And seeing as you have no user javascript installed, it is either the relevant gadget or some sort of dark reader extension. I would guess you're using darkreader but it might be another. You can see what extensions you have by following these instructions. Either way, we cannot fix an issue in one of those extensions here. Izno (talk) 18:11, 16 November 2026 (UTC)
I don't know what rollout means. Please, be less cryptic.
I had had darkreader installed, but I had it disabled. I uninstalled it whatsoever and restarted Mozilla.
The problem is stil out there.
Native Wikipedia vector dark mode.
I'm using exclusively dark mode native to Wikipedia Vector. I even turned off dark mode in Mozilla - nothing helps except for switching to Vector light mode. Tim Ocean (talk) 18:53, 16 November 2026 (UTC)
You are using the "skin" (appearance setting) called "Vector legacy (2010)", with the Gadget (listed under Preferences -> Gadgets) called "Dark mode toggle" enabled. That gadget is described at Wikipedia:Dark mode (gadget). That gadget is increasingly incompatible with viewing Wikipedia pages. At the top of that page, you can see a notice that says, in part, "This gadget is not recommended for enabling dark mode on Wikimedia sites."
You have a few choices. One choice is to use the normal light mode instead (i.e. uncheck the gadget in your Preferences). Another is to go to Preferences -> Appearance and choose the "Vector (2022)" skin, the default, newest, and best-supported skin. That skin has a built-in dark mode that is supported. The page Arithmetic progression works fine with that skin in its native dark mode. The new Vector 2022 skin will take some getting used to, because menu and table of contents items that you are used to have been moved to different places. – Jonesey95 (talk) 19:29, 16 November 2026 (UTC)
I switched to Vector 2022. Latex is still bugged in the dark mode. Bugged latex in the Dark mode of Vector 2022Tim Ocean (talk) 21:53, 16 November 2026 (UTC)
If you haven't already, you need to disable the "Dark mode toggle" gadget and instead use the "Appearance" sidebar (or, if you have hidden it, the glasses icon at the top) to turn on dark mode. Otherwise you won't be able to use the native dark mode and will see this message: You're using a dark mode gadget that interferes with this feature. Disable the gadget to use dark mode.OutsideNormality (talk) 22:05, 16 November 2026 (UTC)
I had to turn off both the gadget and some Core styling for dark mode gadget... but it finally works. Thanks for help and farewell Vector 2010:(( Tim Ocean (talk) 23:07, 16 November 2026 (UTC)
Rollout: when a bunch of software updates is released. Like when Firefox got upgraded from version 159 to version 160 a few days back. --Redrose64🌹 (talk) 21:42, 16 November 2026 (UTC)
This is a general problem with Vector 2010. (I also use Firefox, but I don't think it's browser specific.) I lived with illegible black-on-black formulae because I found them less annoying than the narrow text of Vector 2022 or the retina-burning default white background.
I just added.MathJax {color: white;} to my common.css file, which seems to have solved the problem. This change, of course, would cause problems without dark mode, and may cause problems I've not yet noticed even with dark mode. Certes (talk) 23:26, 16 November 2026 (UTC)
@Certes Have you tried Vector 2022 with Wide mode (click the eyeglasses button on the top and choose "Wide")? If you do that and choose "Hide" on the table of contents and tools sidebar it's even wider than Vector 2010. --Ahecht (TALK PAGE) 18:33, 17 November 2026 (UTC)
I'd tried Wide but not noticed the option to hide the TOC sidebar. (It may not have existed then.) Thanks; I'll have another look. Certes (talk) 23:43, 17 November 2026 (UTC)
Tech News: 2026-47
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
At wikis where Mentorship is configured, permanently blocked users will no longer be assigned a new mentor when their original mentor quits. Temporarily blocked users will still be assigned a new mentor, in line with existing Mentorship practices.
VisualEditor's citation tool will be changed later this week to always open the "automatic" tab (Citoid) instead of remembering the last tab used by an editor. This change is made to support inexperienced editors who rely on the automatic citation option to create references, but often struggle to find it again after clicking on the "manual" or "re-use" tab.
One new wiki has been created: a Wikivoyage in Malayalam (voy:ml:)
Videos in articles and on Commons are slowly starting to use adaptive streaming for playback instead of being delivered as one large file at a fixed quality (example video). This means that video quality will adjust automatically based on a reader’s internet connection, ensuring videos start more quickly and buffer less often. It also places less load on our infrastructure. The rollout will expand gradually to all videos over the coming weeks.
View all 30 community-submitted tasks that were resolved last week. For example, an issue where edits made by human translation administrators when marking pages for translation were incorrectly flagged as bot edits has now been fixed.
Updates for technical contributors
Lua modules can now use the visibleCategories property on a Titleobject to retrieve only the categories visible to readers. Previously, modules would retrieve all page categories, making it hard for users to distinguish visible ones from the hidden ones.
On web, on Wikipedia, ReadingLists will be renamed to Special:Saved. The old name will continue to work as an alias, so existing links will remain accessible. The change is being tested for compatibility with the Wikipedia apps’ reading list import and export functionality and is not expected to affect it. You can report any issues on Phabricator.
The latest run of the WP:USERNOCAT report features a user's .js settings page appearing in three proposed deletion tracking categories, even though prod is not for use in userspace. The prod was placed there by the creator themselves, with the rationale "I accidentally made this", so it probably should just be deleted, but prod isn't the correct process for that. However, I don't have the necessary privileges to edit other editors' js pages in order to get it out of the categories, so could somebody who does have those privileges deal with the page some way or other so that it isn't just left sitting on the report as a permanent speedbump for the next week? Thanks. Bearcat (talk) 00:40, 18 November 2026 (UTC)
LaundryPizza03 left a note and the author corrected it to a CSD template. LittlePuppers (talk) 00:55, 18 November 2026 (UTC)
Even though it was tagged incorrectly it was a clear request from a user to delete a page in their user-space so you could have just deleted as U1. KylieTastic (talk) 12:33, 18 November 2026 (UTC)
KylieTastic Us regular admins can't delete .JS files, you need to be an interface admin. Black Kite (talk) 12:40, 18 November 2026 (UTC)
I didn't have any delete option available to me on the page anywhere that one would be expected. Bearcat (talk) 14:31, 18 November 2026 (UTC)
Wikitext isn't rendered on js pages so deletion tags don't produce a box with a delete link but the interface still has it in a menu. PrimeHunter (talk) 15:29, 18 November 2026 (UTC)
Very odd. My delete option is in the 'More' menu on .js files that same as it is for other files. KylieTastic (talk) 15:50, 18 November 2026 (UTC)
I use MonoBook, so there is no dropdown menu - the "delete" thing is in a tab between "history" and "move", but I get it on other people's .js pages just the same as I do on other people's regular user pages. Clicking it gives the normal list of caveats, followed by the usual form to fill in, which finishes with Delete page. --Redrose64🌹 (talk) 20:08, 18 November 2026 (UTC)
In extremis, you can go to Special:Delete/User:Whoever/whatever.js or add ?action=delete or &action=delete (as appropriate) to the url. Used to regularly see people do beansy things that made getting at the links inconvenient. —Cryptic 04:58, 19 November 2026 (UTC)
Please provide more details when you report a problem. When I went to the article, I saw a red error message saying that the note called "electoral threshold" was not defined, which I'm assuming was the problem you were reporting. The error message was correct, since the note was defined outside of the excerpted section. I moved the note into the excerpted section, and things seem to be working fine now. If you were reporting a different error, please provide details. – Jonesey95 (talk) 19:21, 18 November 2026 (UTC)
That was exactly it. thanks LIrala (talk) 19:59, 18 November 2026 (UTC)
Proposals
Page mover–specific move protection
Should a new move protection level be created, which only allows page movers and administrators to move pages affected by it? 05:31, 29 September 2026 (UTC)
Currently there is no in-between between sysop and XC move protection, meaning that in the case of controversial topics (e.g. my earlier close of President Donald J. Trump International Airport) us page movers have to go through RM/TR, despite the fact that the right signifies that the community (presumably) trust us enough to enact these moves ourself. So my proposal is that a new move protection level, which allows only users with the extendedmove user right to move, be added, and add this user right to the sysop and extendedmover user groups. I can make the patch if there is consensus.
(Pinging @Skarmory, who proposed the idea on Discord.) msk 00:59, 25 September 2026 (UTC)
A comparable user right and protection level would be template editor and template protection. Circumstances are a bit different, but there is precedent for user rights related to specific actions being able to edit past protection of those actions. Skarmory(talk •contribs) 03:03, 25 September 2026 (UTC)
This all seems very sensible to me. Thryduulf (talk) 08:20, 25 September 2026 (UTC)
I would support this. Most move-protected pages are from page-move vandalism or page move warring (source: just a guess), and I think by granting someone page mover the community trusts them not to perform page move vandalism. Axolitl(talk|contribs) 22:39, 25 September 2026 (UTC) edited 22:40, 25 September 2026 (UTC)
I also was discussing this on Discord too at a different time, though in an unrelated context. I would support this, especially since it means that admins would have a reliable middle ground to not need to default to full move protection when extended-confirmed protection is insufficient, except in the most extreme of cases. Any page mover who can't be trusted to, well, move pages responsibly and in accordance with policy, probably should not be a page mover. I think we should probably at least informally expect that admins do not use this new protection level for edit protection, only move protection, similarly to how template editor protection isn't (usually?) used on articles, since it's inconsistent with why the right was created. EggRoll97(talk) 01:58, 26 September 2026 (UTC)
IIRC I can implement it to be an option for move-protect only. msk 02:06, 26 September 2026 (UTC)
Er, are you sure? The array in wgRestrictionLevels (which controls the protection options) is 'enwiki' => [ '', 'autoconfirmed', 'extendedconfirmed', 'templateeditor', 'sysop' ], so unless you have another location for more fine-grained tuning in mind, I don't think it can be technically restricted from being used as an edit protection level (nor do I think we really need to, I think we can just trust that admins wouldn't use it for something it's not designed for). EggRoll97(talk) 05:40, 26 September 2026 (UTC)
Nope, you're right. Sorry about that. msk 14:13, 26 September 2026 (UTC)
Support. Page movers can be trusted to move the mine run of move-protected pages (in mainspace at least), so I'd be on board with downgrading a large number of protections if this is successful. Expectations like "don't use for edit protection" can be documented in a new section at Wikipedia:Protection policy. Extraordinary Writ (talk) 05:56, 26 September 2026 (UTC)
I accept that this proposal wouldn't save time on net, but I still think it's important just as a matter of principle to apply the least restrictive level of protection necessary and only take things away from non-admins as a last resort. That's probably an unorthodox position, though. Extraordinary Writ (talk) 01:44, 21 October 2026 (UTC)
@Extraordinary Writ: Adding a new protection level above extended confirmed is likely to make page moves more restricted for the broader community, not less. The typical long-term editor's most advanced group is extended confirmed. The better solution is to reduce the frequency of full move protection. Daniel Quinlan (talk) 01:59, 21 October 2026 (UTC)
Adding a new protection level above extended confirmed is likely to make page moves more restricted for the broader community, not less. So your argument is that, if we add mover-protection, admins applying move protection would disregard our policies and use mover-protection even where, at most, only ECP move protection would be allowed? FaviFake (talk) 15:55, 21 October 2026 (UTC)
ECP move protection is non-standard; see Wugapodes' comment. msk 16:27, 21 October 2026 (UTC)
Then IAR applies. If an article can't remain confirmed-move-protected but doesn't need to be admin protected, use ECP. For example, the current TWAFI has been EC-move-protected for a week due to the relatively minor potential for disruption. FaviFake (talk) 18:21, 21 October 2026 (UTC)
No, I just think it's inevitable. How it happens will likely be reflected in policies and guidelines. Daniel Quinlan (talk) 16:56, 21 October 2026 (UTC)
If I understand correctly, the argument is something like this: Right now there is only ECP and the far more drastic admin-only move protection. There is some number of pages where maybe ECP isn't quite doing the trick but the currently available next level feels too extreme. Some, many, perhaps the vast majority of these remain at ECP. If we introduce this intermediate protection level, it will be more palatable to increase the protection on more and more pages without having to go all the way to admin-only move protection. Over time, the total number of pages that have a move protection level higher than EC will be potentially much greater than it is today. A downstream effect will be that requests to increase or decrease between the different levels will increase. —Myceteae🍄🟫 (talk) 18:21, 21 October 2026 (UTC)
Why would it be more palatable to increase the protection on more and more pages? To whom would it be more palatable? If a non-admin thinks ECP is not enough, they'll go to RfPP regardless of whether there is another available intermediary protection type.If an admin lands on an article and they think ECP is not enough, they'll simply apply mover-protection and move on. I don't see the issue here. FaviFake (talk) 18:25, 21 October 2026 (UTC)
I'm not making this argument but my understanding is that admins sometimes encounter pages where ECP might be too loose but admin-only might be too restrictive. Some portion of these, perhaps the majority, remain at ECP. If they had another intermediate option available, they would use it. I'm not an admin and rarely have requested or participated in discussions about page protection. I don't have any sense of what the potential impact would be. —Myceteae🍄🟫 (talk) 18:52, 21 October 2026 (UTC)
I think it was said elsewhere in this discussion that ECP is not applied for moving without it being applied for the whole article, even though it can technically be done, because there's no guidance as to when it would be allowed. –Maltazarianᚾparleyinvestigateᛅ 18:56, 21 October 2026 (UTC)
Ah, maybe that was more the issue. —Myceteae🍄🟫 (talk) 19:00, 21 October 2026 (UTC)
At the very minimum, at least one of ECP or page mover should be a valid move protection level. Skarmory(talk •contribs) 19:05, 21 October 2026 (UTC)
Support I think this could provide a good middle ground allowing for a smoother process. For pages where just EXCON is barely not enough to protect them from bad moves there's not really a reason to directly limit it to sysop and if a page mover abuses their rights to move such a page, imo they should and would loose their right immediately... squawk7700 (talk) 10:05, 27 September 2026 (UTC)
Oppose Looking back through Wikipedia:Requested moves/Technical requests#Administrator needed during 2026, I see only 49 requests. Some of these wouldn't be helped by this new protection level, for example this one that needed an admin to delete a conflicting redirect. This doesn't seem like it's enough of a problem to require a whole new protection level. Anomie⚔ 13:08, 27 September 2026 (UTC)
I would expect if this would implement we would be somewhat more free with protecting things at this level, so the current rate of requests is a lower bound but the upper bound is much higher. My personal opinion is that we should generally be much more free with move protections on potentially contentious or high-visibility topics, since unlike edits those should very rarely be done without consensus anyway. Rusalkii (talk) 23:54, 27 September 2026 (UTC)
I'm not sure that more protection would really happen, or that if it did that it would be a good thing. Meanwhile, that "lower bound" is very low. Anomie⚔ 00:48, 28 September 2026 (UTC)
It clutters the configuration and the protection interface. The comparison with the number 'crats is not a good one, since more or fewer people in that list doesn't affect anything else. Anomie⚔ 23:11, 28 September 2026 (UTC)
Support, per my comment above. I participated in at least one of the discord discussions on this topic, but I saw this RfC through CENT and expect I would have ended up here regardless. —Preceding unsigned comment added by Rusalkii (talk • contribs) 16:57, 27 September 2026 (UTC)
Just a note that this isn't an RfC, although one may come in the future. Axolitl(talk|contribs) 03:29, 28 September 2026 (UTC)
Support – Page movers are usually trusted. This is the same as fully protecting templates before the template-protection level was created (just at a smaller but still significant scale). FaviFake (talk) 00:03, 28 September 2026 (UTC)
Support have thought similar before, especially with how long such TRs can sit unattended to, ie 24-48 hours unnecessarily. Sometimes it feels like RM closes are undergoing an admin review rather than the move request itself (or that's how it's felt personally), so the additional delays aren't appreciated from a closing perspective either, especially when it only needs brief oversight from another page mover. Per above if page movers can't be trusted to move pages that are extendedmove protected then they should have rights revoked. CNCin solidarity (talk) 06:10, 28 September 2026 (UTC)
Support – Page movers should be able to move pages. Being trusted to do so responsibly is the whole point of the user right.
I have on multiple occasions expressed my frustration both on- and off-wiki (although not actually in the discussion that led to this RfC, which I was pleasantly surprised to see in WP:CENTRAL) about being a page mover yet being unable to move pages. It is a regular source of additional work and annoyance (especially for more complicated closes) for page movers closing RMs and the admins who have to stand-in to carry out the moves. On multiple occasions I've had to spend time explaining to editors asking me why the pages haven't been moved that yes, the closing template has a field that explicitly states that a non-admin page mover performed the close, but no, that page mover cannot move the page. Yes, it is relatively rare, but the additional work adds up and there is no good reason for it to be happening at all.
We are trusted with the ability to override the title blacklist, create and edit page edit notices and redlink almost anything by moving without leaving a redirect (and some other stuff), but somehow not trusted to do normal moves for pages that some other editors have been improperly moving. If someone cannot be trusted to deal with the ability to move pages that are move protected they should not be trusted to do any of these other things. –Maltazarianᚾparleyinvestigateᛅ 16:33, 28 September 2026 (UTC)
Just going to note that many (but not all) of the arguments along the lines of there being no need do not really argue why it would be a negative, and that the concerns about it being too much work are ignoring that msk offered to do it (and for the record, they are more than capable of doing so) which makes it a very low cost for the community-at-large (unless we want to insist msk would otherwise be obligated to spend that time working elsewhere on the wiki). –Maltazarianᚾparleyinvestigateᛅ 08:50, 23 October 2026 (UTC)
Personally, I'm seeing the opposite: a lot of the support votes focus on "page movers can be trusted to move pages" without considering whether there's enough of a need to balance the increases in complexity in interfaces and processes that result from adding another protection level. Anomie⚔ 11:54, 23 October 2026 (UTC)
There isn't much to say about that. If we want pages to be protected more precisely, then we need to add a new level, which should be used and requested if needed. The benefits of adding one more option in the drop-down are greater than leaving pages with an undue move-protection level. FaviFake (talk) 11:59, 23 October 2026 (UTC)
Most of the discussion here doesn't seem to be about protecting pages "more precisely" in the first place. It's about page movers being unable to handle the RM in the relatively rare cases where a fully-move-protected page needs moving, but without evidence this is leading to any sort of a backlog or unreasonable delay. Anomie⚔ 12:06, 23 October 2026 (UTC)
That's just a direct consequence of the fact that admins are currently forced to use full move protection in cases where ECP is not sufficient. FaviFake (talk) 12:11, 23 October 2026 (UTC)
What is? That most of the discussion isn't about what you claim, or that there's no backlog? Either way, I don't see how it supports your point. Anomie⚔ 22:49, 23 October 2026 (UTC)
Not sure if I've said this elsewhere in the discussion, but I do definitely think there are benefits to having this level around; I would think it would be a better level to use for cases of page move vandalism or move warring than full move protection when ECP isn't sufficient. Skarmory(talk •contribs) 13:50, 23 October 2026 (UTC)
I think that is actually a principled stance to have though. We strive to be an encyclopedia that anybody can edit, and we only put limits on that when it would be infeasible/unreasonable to not do so, not just for the sake of convenience, and we try our best to limit it only to the extent required to prevent disruption. Being supportive of a proposal to let editors one views as trusted to make certain edits be able to make those edits is in line with that. –Maltazarianᚾparleyinvestigateᛅ 13:20, 25 October 2026 (UTC)
Oppose. Just let page movers move all pages. If they can't be trusted with such power, they shouldn't have it. Jessintime (talk) 16:35, 28 September 2026 (UTC)
This is a different proposal than the once considered here. If, hypothetically, your suggestion couldn't be implemented and you were left with only two choices, would you prefer to keep the status quo or create a new protection level?FaviFake (talk) 16:40, 28 September 2026 (UTC)
Taken literally that is an incredibly bad idea. Letting page movers move any page would give them the ability to "edit" (replace the contents) of any page, including interface pages, the local global js/css files, etc, pages that even regular administrators can't edit. If a page mover were then to be compromised they could then engage in significantly more disruption. msk 17:27, 28 September 2026 (UTC)
Yeah pages that have higher-level protections should require corresponding permissions to move. Some widely-used templates also break if you move them due to accompanying css modules. We recently had an incident where an RM led to some list templates were moved, such as Template:Hlist to Template:Horizontal list, and that caused a large part of the wiki to break, including the main page, although it was fortunately swiftly fixed. That move also queued so much work for the backend jobrunners that it put enough of a strain on the backend for a WMF employee to take notice and ask that further moves be held off to let the queue be cleared.
Knowledge of this is not something page movers are expected to have, and the potential for disruption is on the level of "you can break the website doing this". Brings to mind that video of a chimpanzee being handed an AK-47. –Maltazarianᚾparleyinvestigateᛅ 18:02, 28 September 2026 (UTC)
MSK (Monkey Shooting a Kalashnikova) msk 18:04, 28 September 2026 (UTC)
To be honest, that should be a separate proposal. (Not to mention that allowing PMVs blanket access to the move tool might not be a good idea for the reasons mentioned by other users above.) Accessedgrant (Epicgenius mobile alt) (talk) 16:42, 6 October 2026 (UTC)
Comment how frequently do pages get fully move-protected because XC move-protection isn't sufficient, where the reason isn't a move war (for which full protection should continue to be used should this protection level be created) and why? Snowmanonahoe (talk·contribs·typos) 18:41, 28 September 2026 (UTC)
I had a similar question. I'm a fairly new page mover and I've actually not encountered this barrier yet although I am aware of the issue. My understanding is that the practical effect of this change would be primrarily to allow page movers to carry out RM closures for pages that fall under the first two bullets at WP:MOVEP (pages prone to vandalism and frequent page-move disputes). The purpose of page protection in these cases is to force a formal RM discussion, and page movers are entrusted to close and carry out complex and contentions RMs. I would think that the third MOVEP bullet (high visibility pages like WP:AN and Today's featured article) could maintain a higher, admin-only protection level. The discussion above highlights another category, templates and other complex pages where moving may break other parts of the site (although it's not clear if the templates discussed above were move-protected at the time or if the protection level was sufficient). —Myceteae🍄🟫 (talk) 18:53, 28 September 2026 (UTC)
Just to provide some context, the current list of fully-move-protected pages is at , and while I don't have a hard number for you, there is page after page of this. Anything from arbitration enforcement, to vandalism, to sockpuppetry, you name it for the reasons. As for where the reason isn't a move war, I would actually say page-mover-protection should be the default for move wars if created, as the main idea of the page mover group is that it is experienced and trusted users who regularly move pages and demonstrate familiarity with Wikipedia's policies and guidelines regarding page moving and naming, which is a quote directly from the page mover policy. EggRoll97(talk) 04:35, 29 September 2026 (UTC)
Weak oppose I like the idea, but I'm convinced by Anomie and BilledMammal that the demand isn't really there. Especially if it does in fact require a patch to MediaWiki core, which we seem to be unclear on(...?)
This RfC looks like it's going to pass, so one thing I will say is that this action should be treated with a certain gravitas like we do with redirect suppression and template editor. The protection policy should say that a page mover should in most circumstances only move a move-protected page when implementing their close of an RM. Snowmanonahoe (talk·contribs·typos) 05:47, 29 September 2026 (UTC)
Agreed that moving through move protection should not be done lightly and should mostly be used for implementing results of consensus discussions. Skarmory(talk •contribs) 02:07, 30 September 2026 (UTC)
I mean yeah, I fully expect of all page movers to understand that move protection is generally a very clear indicator that a move will be controversial and thus require an RM. –Maltazarianᚾparleyinvestigateᛅ 02:49, 30 September 2026 (UTC)
Support convinced by Extraordinary Writ's second comment above. Snowmanonahoe (talk·contribs·typos) 01:50, 21 October 2026 (UTC)
Hey @Sohom Datta, is there a reason you made this an RfC? AFAIK, the template shouldn't be added retroactively. It makes the old !votes a bit more confusing in context. Axolitl(talk|contribs) 00:52, 29 September 2026 (UTC)
It was on WP:CENT, and we were already !voting in the RFC style, so I assumed this was intended to be a RFC and the RFC tag just hadn't been applied. (No concerns from my end if there is consensus to not make this a RFC) Sohom (talk) 03:31, 29 September 2026 (UTC)
That's fine, though should we rephrase the opening statement, so it stays neutral? Axolitl(talk|contribs) 04:07, 29 September 2026 (UTC)
Pinging @MSK for their thoughts on this, as they were the one who started this discussion. - BlueEleephant (talk · contribs) 02:02, 30 September 2026 (UTC)
I did rephrase it as Should a new move protection level be created, which only allows page movers and administrators to move it? I tried to keep the intent of the original, while maintaining neutrality. Axolitl(talk|contribs) 02:11, 30 September 2026 (UTC)
Note that the "it" should have probably been "the page", but it's kind of too late now. Axolitl(talk|contribs) 02:11, 30 September 2026 (UTC)
I think the intended meaning is clear in this discussion. —Myceteae🍄🟫 (talk) 16:16, 30 September 2026 (UTC)
Support the idea, but this could end up blocked on the technical side. I think it will require a patch to MediaWiki core, and I am not sure this idea is wiki-agnostic enough to justify adding complexity to MediaWiki core. I've made a phab comment at phab:T439172#12372365. –Novem Linguae (talk) 02:45, 29 September 2026 (UTC)
I've rephrased the issue because of that; this will be enwiki specific. msk 02:47, 29 September 2026 (UTC)
The technical obstacles are not as severe as I thought. It looks like this can be done in config files, without making changes to MediaWiki core, except for some translation messages to be added to mw:Extension:WikimediaMessages. –Novem Linguae (talk) 21:30, 29 September 2026 (UTC)
Thinking about this more, could we perhaps just encourage making most move protection extendedconfirmed rather than sysop? Or is there some evidence that there are lots of cases where extendedconfirmed folks are not trustworthy enough but page movers are? –Novem Linguae (talk) 05:38, 30 September 2026 (UTC)
Good questions. It's also been suggested here that (page mover) move protection might be applied more often if this proposal goes through. —Myceteae🍄🟫 (talk) 15:11, 30 September 2026 (UTC)
Most of the page protections that I have seen would have been fine as extendedconfirmed protection. For example, the move vandalism at Epstein files. BilledMammal (talk) 23:45, 20 October 2026 (UTC)
I think some could be reduced, but that is absolutely not the example I would have picked. That general topic area is more disrupted than almost every topic area, and that specific article has been move vandalized.
We could consider mass reducing the move protection level (to extended confirmed) all main space articles that are extended confirmed edit protected with full move protection if the article has never been moved (including moves at prior locations). It would be fairly easy to write a one-time script to do this. I suggest "never been moved" rather than "never been move vandalized or subject to a move dispute" because the latter would require a massive and complex manual review and the simple approach would yield most of the benefit. This proposal would need an RFC and we would want to review the full list of articles that would be affected first, obviously. Daniel Quinlan (talk) 00:22, 21 October 2026 (UTC)
The move vandalism there was by an editor who was not extendedconfirmed. It was also by only a single editor; blocking that editor and not apply any protection would probably have been sufficient, but if it wasn't applying extendedconfirmed move protection would have been. BilledMammal (talk) 01:52, 21 October 2026 (UTC)
I concur with @Daniel Quinlan here. I have seen and experienced a rise in vandalism, especially move-related vandalism, from anons as well as newly created and autoconfirmed accounts. I have found that ECP is usually sufficient in countering and preventing such abuse, though often when I do request that for moves or editing in general, it is not implemented in favor of a subpar protection unless there have been multiple egregious offenses. —Trailblazer101🔥 (discuss · contribs) 04:25, 25 October 2026 (UTC)
Back in 2021 when Xeno and I were working through old move protections, the concern with using ECP for move protection was that it's never really been used outside of contentious topics, and neither WP:MOVEP nor WP:ECPGUIDE say that ECP move-only protection is allowed. They still don't. It's been a decade, and we still haven't documented all the corner cases of ECP. You can see the old AN discussion on the protection reviews for some old opinions on the idea. I'm not sure we ever finished reviewing all the old protections. It was like 9000 articles, but most of them could simply be unprotected. I did about 50, Xeno did nearly 500. It's why we added the unprotection reasons to the list of drop down options in the protection interface. This is to say, I'd be fine with allowing ECP for move protection, and would also encourage people to unprotect some stuff listed at User:Wugapodes/moveprotectreview. — Wug·a·po·des 00:30, 21 October 2026 (UTC)
If this proposal fails, there should definitely be a discussion about ECP move protection, because not having anything between autoconfirmed and full protection for moving pages enshrined anywhere seems wrong, especially if ECP is in actual use. Skarmory(talk •contribs) 18:25, 21 October 2026 (UTC)
EC move protection is already covered in the protection policy. Move protection of any duration may be applied to pages being repeatedly moved in violation of policy using the lowest protection level sufficient to stop the disruption (extended-confirmed or full). ~ Jenson (SilverLocust💬) 23:35, 21 October 2026 (UTC)
Support. This is good idea. It would allow admins more freedom to move-protect pages and let trusted pagemovers handle more controversial moves. Protection limited to people experienced with pagemoves is fairly similar to template protection for people experienced with templates, which I think is widely recognized as a useful tool. On procedure, I don't see how the presence or absence of an RfC tag has any impact on the validity of the consensus produced here, whatever that may turn out to be. The main point of the tag is to attract people watching the RfC categories to prevent local consensus issues, but VPPROP and CENT are sufficiently high profile to do the same. Toadspike[Talk] 11:11, 29 September 2026 (UTC)
Support. Page movers are generally not stupid, and similar to when we established template editors, only the highest of the high-risk needs to be kept behind the sysop gate. Please ignore my brazen conflict of interest here, and perhaps consider me an exception to the first clause of my previous sentence. With love from Maryland, charlotte👸♥ 09:06, 1 October 2026 (UTC)
Oppose. An additional move protection level will almost certainly lead to more protection requests and actions to adjust protection levels, and these requests will outnumber the move requests this would potentially avoid (which is only when a page happens to be at this level and a page mover happens to handle the request). I believe the real issue is that extended confirmed is a poor proxy for trust when it comes to page moves. We should address that issue instead. I also agree with Anomie that this would clutter the configuration and protection interface, and as someone who has handled many page protections, I believe adding another level would make each protection decision more complex and slower. Daniel Quinlan (talk) 20:11, 1 October 2026 (UTC)
extended confirmed is a poor proxy for trust when it comes to page moves. We should address that issue instead. This is an attempt to solve this exact issue. How do you think the 30/500 protection could be limited to more users? I don't understand; if we make extended-move-protected pages require, say, 1000 edits instead of 500, that's no longer "extended-move-protection". FaviFake (talk) 20:14, 1 October 2026 (UTC)
I didn't propose specific changes to extended confirmed, but I'm ready to join a discussion about other approaches at WP:VPI. I oppose this proposal because it likely adds more work than it saves. An acceptable approach would reduce reliance on sysops for page moves without adding more sysop workload than it saves. Daniel Quinlan (talk) 20:47, 1 October 2026 (UTC)
Sure, I was just confused about how it could be possible to address this issue by modifying the 30/500 move protection in a way that wouldn't completely change the protection level itself. FaviFake (talk) 20:52, 1 October 2026 (UTC)
OT/FYI: there have been discussions at WP:PP regarding a new protection level, something between ECP and Full stil get's my support. The fact there is nothing between a busy one month editor and admin protection is baffling, aside from imposing PBAN/TBAN/CBAN. Personally I prefer the high bar like 5K/6M or 10K/1Y as "Advanced protection", then just yank privileges when needed, something we never do for experienced editors as 500/30 as is only a month break by comparison, so bans become necessary. A 6M/1Y defacto ban from editing pages with advanced protection makes a lot more sense overall, if that is the issue with certain users. In absence of that, I support this idea. CNCin solidarity (talk) 09:27, 3 October 2026 (UTC)
I don't really see why it needs to lead to more frequent requests for move protection, other than perhaps as a result of admins being more willing to use it, and discussions about changing the move protection level would be exceedingly rare – the only situation where you would realistically use full move protection would be on highly-visible templates.
For article space, I expect things to function pretty much just like they do now but with page movers able to move pages, and potentially with admins being more willing to use move protection on pages (which I don't see as workload as much as more tools to work with). –Maltazarianᚾparleyinvestigateᛅ 22:04, 1 October 2026 (UTC)
An increase in protection levels is not just "more tools" and it's definitely not a free lunch. Every new protection level creates two new boundaries, and we regularly field requests to increase or lower protections (both on RFPP and on sysop talk pages), and many of those are rejected due to insufficient disruption or excessive risk. Adding a new protection level because a small number of requests take a day or two to resolve is using an expensive sledgehammer to swat a fly. Daniel Quinlan (talk) 23:49, 1 October 2026 (UTC)
I know you field plenty of protection requests for the different kinds of protection we currently have in place, but that doesn't mean that this one will be the same, and there is good reason to believe that it would not be for the reasons I already mentioned. The way I see it the current move protection can be split in half with a pretty clear boundary between the two levels. The only editors that would even be affected by a change between full move protection and the lesser move protection is page movers, and I cannot imagine that page movers are going to be consistently requesting changes to the protection level of high-visibility template pages. –Maltazarianᚾparleyinvestigateᛅ 01:29, 2 October 2026 (UTC)
Support This seems like a good idea. Page Movers are on some level going to be inherently more trustworthy than extended confirmed users in these situations because they have more to lose if they abuse it. --Ahecht (TALK PAGE) 17:20, 9 October 2026 (UTC)
Support as there are less page movers (467) than admins (808) and that PMs can be trusted not to move protected articles unless absolutely necessary (usually after an RM). I have the PM right also JuniperChill (talk) 11:55, 10 October 2026 (UTC)
Oppose per BilledMammal below - the amount of effort spent dealing with this ultimately exceeds the value. * Pppery *it has begun... 20:32, 10 October 2026 (UTC)
Support per above, mostly on the idea that those with the extended mover right have been trusted with those tools. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 01:11, 12 October 2026 (UTC)
Oppose a user group existing doesn't mean a protection level should also exist. The work saved needs to outweigh the work created. For work saved, it would save us one or two requests per week based on the comments from Anomie and Billed Mammal. Meanwhile, the work created is quite steep. New protection levels mean new protection policies for those levels that need to be maintained and argued about---it took 6 months and 2 RfCs to settle on the current ECP policy back in 2016. Editors will place more requests at RFPP to change protection levels, not all of good quality, that require more admin time to decide than the weekly technical request and distract from more pressing protection requests. The non-standard changes to the server-side code needs to be written and maintained even when the original writer stops caring. The trade-offs seem terrible. Page movers who can be trusted with sysop-protected pages should apply for the existing sysop permission rather than creating a new protection level and all the work that comes with it. — Wug·a·po·des 20:27, 12 October 2026 (UTC)
I'm not in this group so maybe I'm out of line here but I stumbled upon this and it sounds like a no-harm addition useful to at least a small extent with a person willing to implement it. Blippy1998 (talk) 08:06, 19 October 2026 (UTC)
You're not out of line. No one with advanced permissions of any kind inherently has any sort of authority over others as to how this website should be run. Snowmanonahoe (talk·contribs·typos) 18:44, 20 October 2026 (UTC)
It sounds that way, but it's unfortunately a false economy. This approach will almost certainly generate far more work at WP:RFPP than it will save at WP:RM/TR. It would be better to find a different solution that doesn't have that downside. Daniel Quinlan (talk) 18:58, 20 October 2026 (UTC)
Oppose per Daniel Quinlan and Wugapodes. The benefits don't seem to outweigh the potential problems/time spend. mdm.bla 17:58, 20 October 2026 (UTC)
Oppose per Daniel Quinlan. Wikipedia doesn't need more and more and more levels of every option just for the sake of adding them. This applies to protection levels.Katzrockso (talk) 00:33, 21 October 2026 (UTC)
Oppose - As I said ten years ago in a slightly different context: There is no need. Requests of this nature can be easily handled by an administrator ... as the current rate of occurrence is low. Anomie demonstrates above that this sentiment still rings true for the matter at hand now. There is also a reasonable argument to be made that a move-protection level between EC & Full is overarchingly undesirable, but I will refrain from making it until a need is demonstrated. —Godsy(TALKCONT) 02:51, 23 October 2026 (UTC)
@Daniel Quinlan and Wugapodes: You both hit the nail on the head. Re-reading your comments above made me realize something—this proposal would really just result in a quasi-unbundling of the sysop toolset. However, the framing avoids the traditional ire drawn from true technical unbundling proposals! Convolution should always be avoided; if page movers are so trusted in actuality, then they should be granted the ability to move fully-protected pages. It certainly should not be done in this manner which suffers from all the cruxes which you both so aptly point out. —Godsy(TALKCONT) 04:01, 25 October 2026 (UTC)
Very good point. While I still support the proposal in absence of an alternative, a better direction would be similar to the intended purpose of NPR and PMR. In the same vein that NPR was "unbundled" from the admin tool set, and we now have more non-admin reviewers than admins with full permissions to review pages, PMR should realistically also include permissions for move-protected pages, based on the assessed trust of those who have page mover permissions. In response to Wugapodes however, Page movers who can be trusted with sysop-protected pages should apply for the existing sysop permission [...], I strongly disagree. Most page movers appear to have no interest or demonstrated need for sysop permissions, because their focus is on moving pages, not everything else that comes with the mop and bucket. On this note I'd prefer to see further unbundling of sysop toolkit, such as WP:Page deleter, WP:Page protector, etc, for those who prefer to stick to particular areas of the 'pedia. Moreover, the benefits of further unbundling would be worth the time and effort, like it has been for NPR and PMR already, while I can see the drawbacks of a new protection level. Overall for every permission granted, it can translate to dozens if not thousands of admin-like actions that otherwise wouldn't have occurred. I can't imagine where the project would be without NPR/PMR to be honest, especially given how backlogged NPP usually is on a good month. Also if editors want more admins then the best strategy for that is to create more stepping stones in order to reduce the hurdle of RFA/AELECT. Whereas recommending page movers apply for sysop rights, simply in order to move protected pages, is well intended but thoroughly unrealistic. CNCin solidarity (talk) 09:44, 25 October 2026 (UTC)
I would also like to note that move protection is hardly being applied to mainspace pages because only sysops can be trusted to move them, it's done because there is no other alternative. –Maltazarianᚾparleyinvestigateᛅ 13:10, 25 October 2026 (UTC)
Moving full protected pages is a demonstrated need, and page movers are great admin candidates. Page movers have been trusted with limited delete permissions since 2021. They also show demonstrated experience in reviewing contentious discussions for consensus and can follow admin-level policy documents well. If a page mover only uses the tools to move pages we're better for it, and if they use the rest of the kit to improve the encyclopedia, even better. The tools are a way to serve your corner of the encyclopedia, not leave it.That said, I don't think generally unbundling the core block-protect-delete tools is a good idea either. Dealing with disruption requires all three in your toolbox. For example, socks should usually be range blocked as a first resort rather than have the page protected and revision deletion can be important for cleaning up afterward. If we give some people block and some people protect and some people delete, then at best we will still need to wait for someone with the proper tools and at worst we will use the wrong tool for the job. Personally, I think one of our biggest AntiPatterns is that we spend hundreds of person-hours debating new permissions, coding new permissions, writing policies for permissions, processing requests for permissions, and monitoring use of permissions so that our most responsible editors can build an inferior toolkit request by request. At a certain point we need to kindly but firmly say, if someone wants to serve the community with further tools they need to stop making work for others and just get the whole toolbox. — Wug·a·po·des 02:39, 26 October 2026 (UTC)
@Wugapodes: I agree. Just want to clarify that while I think granting page movers the ability to move fully-protected pages is a better idea than what is being proposed here, it still is not something I would support. —Godsy(TALKCONT) 02:54, 26 October 2026 (UTC)
Do you think someone would pass RFA or AELECT if the only reason they are running is to supplement their ability to move pages? I suspect at best, it would be a very hard sell. Skarmory(talk •contribs) 02:56, 26 October 2026 (UTC)
Probably not, but most extended movers work in multiple areas, and the most trusted ones would benefit from the additional permissions that are entrusted to sysops. Daniel Quinlan (talk) 03:04, 26 October 2026 (UTC)
"I want to move pages and I might help with other stuff" was my answer to Q1 and it worked fine. — Wug·a·po·des 03:26, 26 October 2026 (UTC)
I believe extended confirmed move protection will be sufficient for most if not all of these articles. If full move protection becomes necessary on an article, and there's consensus to move the article, and the consensus is reached before the full move protection expires, someone can make a request at WP:RM/T and it will be dealt with quickly. Daniel Quinlan (talk) 18:03, 27 October 2026 (UTC)
A few hours isn't really "quick" for a TWAFI. FaviFake (talk) 18:08, 27 October 2026 (UTC)
Given the number of administrators involved in TWAFI, watching the current and recent TWAFI articles, and handling requests related to the article, a wait of a few hours is not likely. Daniel Quinlan (talk) 18:26, 27 October 2026 (UTC)
Oppose per above. Izno (talk) 04:37, 5 November 2026 (UTC)
Discussion (mover protection)
Unarchiving awaiting closure (and adding this comment to bump up the timer). Will post at WP:CR. Axolitl(talk|contribs) 23:32, 12 November 2026 (UTC)
Has been there 10 days already,, no need for unacrhiving either. CNCin solidarity (talk) 00:22, 13 November 2026 (UTC)
Oops, I didn't realize it was already there. Still, I think unarchiving is probably a good idea, as it I don't think it should be sitting in an archive page while the RfC tag is still open. Axolitl(talk|contribs) 00:28, 13 November 2026 (UTC)
RfC tag was removed a while ago, that's why it was archived after inactivity. For closing purposes it would have been unarchived anyway btw. Maybe it'll encourage a close now, but often it doesn't work this way. CNCin solidarity (talk) 00:41, 13 November 2026 (UTC)
Oh, I didn't see the tag was removed. I think keeping it here for a bit might help with visibility, hopefully. Axolitl(talk|contribs) 00:43, 13 November 2026 (UTC)
Possibly. I have stumbled across RfCs here before having been inactive for a while and thought "might as well close then". The only downside is drawing more editors into an RfC that's got no consensus written all over it, as time is usually better spent elsewhere, unless there is something substantial to add the discussion that was previously missed. CNCin solidarity (talk) 00:52, 13 November 2026 (UTC)
Name
(Starting a separate section for this.) If this was implemented, what would it be called? Would it be called "move protection", and the sysop protection called something like "full move protection"? Or would it possibly be a level-2/level-2 thing? Input would be appreciated, especially if this became an RfC or something. Axolitl(talk|contribs) 22:20, 26 September 2026 (UTC)
Since page mover is already called extendedmover it would go that this would be called extendedmove technically; we can rename sysop move protection to you your suggestion, or just deprecate standalone "sysop move protection" as a concept entirely (we don't call fully protected pages "move protected") msk 22:28, 26 September 2026 (UTC)
I would probably name the sysop level full move protection and let this one be move protection. Skarmory(talk •contribs) 23:29, 28 September 2026 (UTC)
Surely "Move protection" and "Full move protection" are the simplest options here. –Maltazarianᚾparleyinvestigateᛅ 05:12, 29 September 2026 (UTC)
I feel like common usage is already for "move protection" to refer to the green lock. Like, sure, technically an ECP page is move protected at an ECP level, but I can't recall hearing anybody talk about it that way.
I'd suggest "extended move protection" as msk did, but then we're causing confusion due to EC not having anything to do with it.
Idk this part isn't all that important to me anyway. –Maltazarianᚾparleyinvestigateᛅ 08:24, 29 September 2026 (UTC)
Yeah it's tricky. For now my preference is for "mover protection"; pages will be "mover-protected" FaviFake (talk) 08:28, 29 September 2026 (UTC)
Impact
Looking at the past month of requests at WP:RMTR, I see just seven:
The seventh I cant list. Overall, maybe there will be one hundred moves per year that will be done by page movers instead of admins; I'm not convinced that this labor saving is worth the cost in development time. (I'll add support for RMTR into Move+ some time, which should reduce the labor cost further - I'll also in the nearer future change RM to say whether it is listing a move in the admin section or the standard section, to make it easier to review this in the future) BilledMammal (talk) 03:52, 29 September 2026 (UTC)
I wonder how many times per month template-protected pages are edited by template editors, as a point of comparison. Snowmanonahoe (talk·contribs·typos) 05:14, 29 September 2026 (UTC)
Moves of move protected pages, and edits of template edit protected pages, by month for the past three years:
Updated the table. The earlier one was moves of all move-protected pages, included extended-move protected. This one is still a bit of an estimate, as it assumes that if a page is protected now it was protected when the move occurred, so it can miss some moves where protected lapsed or was removed, and counts moves of pages later protected. For example, six moves from March are of Epstein files, none of which was done while the page was protected. BilledMammal (talk) 05:56, 29 September 2026 (UTC)
How hard to we really expect it to be to implement? Anyone got an idea? Also Move+ already has RM/TR capabilities last I checked. Did the recent update get rid of them? –Maltazarianᚾparleyinvestigateᛅ 05:15, 29 September 2026 (UTC)
Move+ lists moves at RMTR, it's never supported (outside of a prototype I wrote two years ago) implementing the moves at RMTR. BilledMammal (talk) 05:19, 29 September 2026 (UTC)
50 to 100 moves per year adds up over time, and this project is already over 25 years old. Meanwhile, we have someone volunteering to make the patch, who also happens to be the person who started this discussion, so that cuts down on the needed development time. This doesn't even account for other possibilities for how the protection level could be used; notably, I agree with EggRoll97 above that this would make sense as the standard for protection in case of move wars. Skarmory(talk •contribs) 05:16, 29 September 2026 (UTC)
New users often get reverted because they don't explain what they are doing. Often vandalism, but at times they have a good reason to remove text. The problem is they don't tell us. Should we ask the WMF to turn the "remind me when I forget an edit summary" on by default for new editors? Or at least test it? In solidarity, —Femke (talk) 🐦 19:42, 18 October 2026 (UTC)
I think that would be a good thing to trial. The only potential downside I can see is more misleading or irrelevant edit summaries, in good or bad faith, as not everyone understands what an edit summary is for (e.g. I've seen at least two in the past few days where people left their email address in the edit summary), and that might be harder to detect than an empty summary (I don't know), but overall my gut feeling is that it would be a net positive. Thryduulf (talk) 19:47, 18 October 2026 (UTC)
That sounds like a good idea, I've encountered it in other wmf wikis. The error message should only ask for a brief summary, to avoid burdening new users. FaviFake (talk) 12:58, 19 October 2026 (UTC)
Only time will tell how that will turn out. But, the idea is interesting in that a clever bot could add "obvious" edit summaries and ask for user confirmation. An obvious example would be typo corrections. I would like that for my own edits, given that I don't like to do obvious edit summaries. Another example is reference addition or cn tag addition etc. This does not have to be real time and will involve no LLMS. This would be more useful than reverse-genius projects like abstract Wiki, etc. Yesterday, all my dreams... (talk) 14:59, 19 October 2026 (UTC)
Sorry, that is the last thing I would want to turn on. If it automatically suggests "reference added" as the summary and I just click ok, I would like that. Yesterday, all my dreams... (talk) 15:07, 19 October 2026 (UTC)
It doesn't, but there are other scripts at WP:USL that allow you to save pre-set edit summaries. I prefer to use a text expander app like aText. For example, I could set it up so that when I type "zref", it immediately turns into "reference added". I have hundreds of these, ranging from small templates to entire paragraphs. FaviFake (talk) 15:11, 19 October 2026 (UTC)
The fact that you have to tell me about it means that over 90% of users do not know about these. My suggestion was to have it for everyone. Anyway, I have said all I needed on this, and will leave it in the hands of you guys. Have a good day. Yesterday, all my dreams... (talk) 15:27, 19 October 2026 (UTC)
I would support this. I also think it would help new users pause and think a little bit before publishing an edit. qcne(talk) 15:32, 19 October 2026 (UTC)
Agreed. I run across many users with edit counts in the hundreds (and sometimes even thousands) who rarely if ever use edit summaries. A not insignificant number of them are problematic for one reason or another, and it makes it much harder to track what they've been doing. For good faith newbies it can help us intervene and correct them sooner so they don't continue making the same mistakes. ChompyTheGogoat[Bleat|Munched] 18:04, 19 October 2026 (UTC)
What do people think if the option is only to turn it on or off. That is: also for experienced users? I'd love to know more about what is behind edits of more experienced editors too. In solidarity, —Femke (talk) 🐦 18:08, 19 October 2026 (UTC)
I have zero issues with this being a universal "On". qcne(talk) 18:11, 19 October 2026 (UTC)
I can't think a good reason not to turn it on for everybody. There are occasionally times when there should be no edit summary (because something automated will add one) but it's no hardship to say that you actually do want to make an edit without a summary. Thryduulf (talk) 18:23, 19 October 2026 (UTC)
I always try to add one even when it's not really necessary - even just a single word - pro forma. If someone is skimming my contributions I don't want them to have to stop and check individual edits just to see whether there's a problem. My sandbox history is full of increasingly irrate summaries when I'm trying to work out tedious code issues XD ChompyTheGogoat[Bleat|Munched] 18:56, 19 October 2026 (UTC)
See also: "label" "label" "tag" "label". Just because. ChompyTheGogoat[Bleat|Munched] 19:00, 19 October 2026 (UTC)
I've opened a phab: phab:T441726. My preference is to test this first, as it introduces more friction which can backfire. But if there is no capacity to test, I would prefer this is enabled. In solidarity, —Femke (talk) 🐦 20:37, 19 October 2026 (UTC)
Yes, there is no "good" reason. But there is a real reason: laziness. If it is viewed as nagware, it will put some people off. An experiment is well warranted. Yesterday, all my dreams... (talk) 14:42, 20 October 2026 (UTC)
Please consider this edit. Why doesn't the system automatically add a summary for it? It would take a simple, simple bot to do it, and not even in real time. Let us start there, before introducing nagware, please. Yesterday, all my dreams... (talk) 15:14, 20 October 2026 (UTC)
I'm sure there are additional situations where an automated summary would be possible, but there are far more where it's not, and countless edits (including large scale changes) with no descriptors. ChompyTheGogoat[Bleat|Munched] 15:36, 20 October 2026 (UTC)
So we could prompt for large scale changes but not simple cases such as above. Yesterday, all my dreams... (talk) 16:01, 20 October 2026 (UTC)
Smaller changes can still have major impacts. The size of an edit isn't necessarily indicative of its significance. Besides, where would you draw the line? Any cutoff would be arbitrary. ChompyTheGogoat[Bleat|Munched] 16:05, 20 October 2026 (UTC)
I would start with link additions then see what happens. The two of us can discuss this for ever and a day. Let us wait for other comments. Thanks. Yesterday, all my dreams... (talk) 16:19, 20 October 2026 (UTC)
Most of the edits I see that are purely link additions are through the newcomer tasks, so those are already tagged as such. Edits without summaries are most often newbies manually adding or removing information. ChompyTheGogoat[Bleat|Munched] 16:26, 20 October 2026 (UTC)
Support. Summaries are optional and many good edits are made without them, but it's a good habit to encourage. Certes (talk) 20:48, 19 October 2026 (UTC)
I would love to have a trial with actual statistics, and then make a decision based on those statistics. Best, HouseBlaster (talk • edits • he/they) 02:48, 20 October 2026 (UTC)
Support as a trial, but we should also turn "Add two new dropdown boxes below the edit summary box with some useful default summaries" on by default if we do so. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 00:37, 22 October 2026 (UTC)
Another idea I had, is a marathon A/B test with a bunch of existing settings tested. This intervention would possibly lead to more false edit summaries, meaning it can backfire too? In solidarity, —Femke (talk) 🐦 07:19, 22 October 2026 (UTC)
I do seem to recall that mobile (maybe one of the apps) had a dropdown at one point, and it was misused to the point that patrollers found it to be a signal for edits that needed extra attention. Anomie⚔ 11:47, 22 October 2026 (UTC)
Interesting. I have the gadget enabled, although I pretty much only use it for either spelling/grammar or formatting corrections. Anything more extensive I type out manually. I guess the users who'd abuse such a feature don't know or care enough to bother enabling it. I'm mildly surprised that they'd outweigh good faith new users who'd prefer that option though. ChompyTheGogoat[Bleat|Munched] 19:49, 22 October 2026 (UTC)
I would also support a trial. What were you thinking, first 50 or 100 edits? First X mainspace edits? Relatedly, it would be good if someone could put together a quick and basic info page about what the warning looks like, perhaps something that Special:Preferences#mw-prefsection-gadgets could link to. That would also be a useful page to note any test results and track changes in defaults. CMD (talk) 07:25, 22 October 2026 (UTC)
I would say the group I expect the biggest difference for are newbies. So an A/B test among TAs and nonconfirmed editors would make most sense. To reduce confusion, I image their settings won't get changed once they reach a certain edit count. In solidarity, —Femke (talk) 🐦 16:55, 22 October 2026 (UTC)
Support: For newbies, more so than experienced editors. But happy to support for both Mme Maigret (talk) 09:30, 27 October 2026 (UTC)
Support changing the default in a trial, but Oppose any change that would prevent disabling the setting. Daniel Quinlan (talk) 17:35, 27 October 2026 (UTC)
Support adding it as default for a trial, collecting data for groups across editing levels. As far as I know, gadgets can always be disabled if needed. Chaotic Enby (in solidarity · talk · contribs) 18:05, 27 October 2026 (UTC)
Oppose unless it turns off once you get a certain number of edits/certain user right, or if not, a button to turn it off in the publishing interface in the bottom. Support a trial for a couple of weeks. Theeverywherepersontalk hereIn solidarity! 15:15, 29 October 2026 (UTC)
Support, as long as it is optional for more experienced editors. GreatWhiteEditor (talk) 20:52, 29 October 2026 (UTC)
I hadn't seen that, but most points have been made. It's clear that this should be tested first. With the positive results from the extra friction of edit check, this may be turn out great. It may also not. In solidarity, —Femke (talk) 🐦 07:49, 30 October 2026 (UTC)
Oppose unless phab:T367412 is fixed first. This will lead to even more people using bad summaries (like "created redirect") when creating and retargeting redirects, suppressing the automatic summary, which actually includes the target. Warudo (talk) 14:15, 30 October 2026 (UTC)
Support, even I forget to do edit summaries sometimes and I've been on Wikipedia for a while! GarethBaloney (talk) 19:00, 3 November 2026 (UTC)
Oppose as it would likely lead to people providing an inaccurate edit summary instead, or providing it with just a single character. I almost always use edit summaries, with the notable exception of creating redirects as they provide it automatically and a manual summary saying 'created redirect' is less informative than 'redirected page to [page name]'. It also allows users to revert vandalism fast if they do not know about the existence of the 'undo' tool. JuniperChill (talk) 22:08, 13 November 2026 (UTC)
WMF comment
Hi all, and thanks for bringing this to us! The Editing team is very interested in working with you all to run this experiment (presuming the prevailing consensus holds).
We will not have the capacity to start it until the new year. In the meantime, as a first step, we'd love to have your involvement defining some of the details, such as the precise audience, the metrics we are hoping to impact, and the guardrail metrics. I see that there has already been some discussion on these topics at the Phabricator ticket, and I'll open a new thread (pinging everyone who participated here) in the coming weeks to share our thoughts.
Lastly, I'll note that I'm really glad to see the support for the overall idea of experimentation here. Making small changes, measuring the impact, and then iterating based on the results is the primary method we use at the Foundation to develop new features, and it's an effective method. I see some good suggestions for fixes/improvements to the prompt feature above, but I think it makes sense to run the experiment first so that the results can inform our prioritization. And if any of you have ideas for other experiments we could run (particularly those making a simple change that'd be easy to measure) I encourage you to start discussions proposing them and ping us if a consensus forms!
Cheers, Sdkb‑WMFtalk 22:55, 12 November 2026 (UTC)
Specifically, "South Asian cinema, broadly construed" should be understood to include at a minimum films as well as all associated cast and crew (actors, directors, musical directors, etc.) including but not limited to India, Pakistan, Sri Lanka and Bangladesh.
A. Status quo: South Asian cinema remains under the broader WP:CT/SA but is not subject to specific subtopic restrictions
B. South Asian cinema, broadly construed, is noted as a subtopic of CT/SA and placed under the extended-confirmed restriction.
C. Article creation in the topic area is restricted to editors with extended-confirmed permissions. Other editing within the topic is placed under autoconfirmed restriction.
D. The whole topic is placed under autoconfirmed restriction only.
Worth noting that the proposals for autoconfirmed restriction are without precedent as far as I'm aware.
Answers which were already given during the RFCBEFORE discussion (included below under 'Discussion') have been transcluded into the 'Survey' subsection. Courtesy pings for those editors in case they want to modify their responses at all: IrisChronomia, Gurkubondinn, Jéské Couriano, CoffeeCrumbs, CNMall41, ABx11
"Anchor" comment placed at the top for the purpose of giving editors something to hit "Reply" on.–Maltazarianᚾparleyinvestigateᛅ 14:28, 26 October 2026 (UTC)
Strong support for ECR (creation of articles) and confirmed (any edit at all).
It isn't hard to perform ten edits nowadays, especially given the numerous opportunities and namespaces. Someone could achieve ten just by sending WikiLoves to the top nine Wikipedians in edit, and create a very short userpage. Then, of course, stall out the three days and start vandalizing. ☯️🐉🐼 Unsurprising 🐼🐉☯️: nice to meet you!📝👥 15:15, 7 November 2026 (UTC)
Support the use of ECR for Indian cinema (option B), presumably this would be through a WP:GS designation by the community. I wasn't aware of the social role that Indian cinema has until I started seeing the disruption (and LLM junk) here on enwiki, and I have not really watched any Indian movies to any real extent (saw one or two years ago but I can't remember which movies right now). I have no stake in this other than as an enwiki editor. ‑‑gurkubondinn 07:13, 20 October 2026 (UTC)
Support 500/30 rule (Option B) for Indian cinema topic area - What do Indian cinema and Indian military history have in common? Both are intrinsically linked to caste, which has been THE primary motivator of problems with regards to the India topic area. The standard set is irrelevant as Indian cinema already falls under WP:CT/SA and thus it can be assumed discretionary sanctions are already on the table. The problem is more dealing with blatant mercenary editors and the caste/nationalist warriors that come out of the woodwork in defence of a film that supports their caste or weltanschauung. —Jéské Courianov^_^vThrillerNight! 06:22, 20 October 2026 (UTC)
Option C as first choice, Option B, as second choice. I don't think autoconfirmed is pointless here. While registered editors can certainly game autoconfirmed, TAs are a sizable chunk of the problem, and they can't be autoconfirmed at all. It's not uncommon to have to tangle with a TA editor on a slop article four or five times in a day as they rapidly jump TAs and IP ranges. CoffeeCrumbs (talk) 09:56, 20 October 2026 (UTC)
For the benefit of the closer interpreting these multi-choice options, while I like C a tiny bit more than B, ultimately, my preference is for whatever helps create a working consensus for C or B. CoffeeCrumbs (talk) 04:09, 24 October 2026 (UTC)
I also support D if there's a consensus. At this moment, doing anything is, in my eyes, better than A, which is nothing more than sitting back and waiting until the garbage is so high that there's no volunteer army large enough to empty the landfill. CoffeeCrumbs (talk) 01:56, 26 October 2026 (UTC)
Support Option C then Option B - Option C would restrict many of the SPI throwaway accounts who operate heavily in that space. However, it would could be a nightmare to enforce and cause more issues than we alrady have. Option B would be my second choice. --CNMall41 (talk) 20:44, 20 October 2026 (UTC)
Support 500/30 requirement with Option B per Jéské Couriano. --ABx11 (she/they) 00:35, 23 October 2026 (UTC)
Option B as proposer. This is a hugely problematic topic area rife with UPE, promotional editing, and identitarian conflicts as described in the discussion section. ECR is an appropriate remedy and will make sure those editing in the topic are are serious. Autoconfirmed would be an insufficient remedy due to the ease with which autoconfirmed can be gamed; the problematic editors in this topic area are more than passionate enough to game AC in order to edit here. Athanelar (talk) 10:57, 23 October 2026 (UTC)
As I said in the discussion, I support option D. I've trawled through the new users log quite a bit in the last two weeks and one of the things that comes up there frequently is that promotional edits are most often for companies based in India. Now, I do not know what proportion of Wikipedia editors are based in India, but if memory serves me correctly then there is only one promotional company that explicitly declared their location that wasn't based in India compared to 4 or 5 that were based in India. Placing the topic under autoconfirmed would both stop TAs from creating overly promotional drafts and discourage at least some of the promotional sludge that we see rear its ugly head a few times a day. In terms of South Asian Cinema, pages that are related to castes should already be covered by CT/CASTE (I am by no means an expert on South Asian cinema so I could be wrong here), so I don't see the need for anything extra. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 12:55, 23 October 2026 (UTC)
In terms of South Asian Cinema, pages that are related to castes should already be covered by CT/CASTE It's not that simple, and this is why it's hard for people not in the know to understand how deep the problems run here.
In Telugu cinema (Tollywood) for example, a lot of the major actors are either of the Kapu caste (Chiranjeevi, Ram Charan, Pawan Kalyan) or of the Kamma caste (Nagarjuna, Mahesh Babu, N.T. Rama Rao). Not only that, but there are major film dynasties too; the three people I mentioned from the Kapu caste are not just related by caste, but also familially, and their family has major control over the whole production environment in Tollywood. There's an incredible amount of intersectionality and identity politics here which goes way beyond anything in Hollywood, and a lot of unseen factors that can influence disruptive editing (e.g., if I'm a person of a caste which is related to the Kapus, then I might have an identitarian interest in downplaying the success of films whose major actors are Kamma, or conversely in lavishing praise on people and projects related to the Kapus). I'm not as knowledgeable about Tamil films or Malayali films, but I have no doubt the same things exist there. Then there's also a whole separate dimension of Hindu vs Muslim politics in movies like Dhurandar and Ustaad Bhagat Singh.
The reason why ECR is appropriate here is because otherwise antivandal editors in this topic area need a veritable degree on regional history and sociopolitics to understand half of the shit causing the disruption. Athanelar (talk) 16:32, 23 October 2026 (UTC)
That explains why I keep getting accused of supporting some other person I've never heard of when I block inappropriate additions. Wait til they hear I'm a white girl who's never left the states. ChompyTheGogoat[Bleat|Munched] 21:15, 23 October 2026 (UTC)
Thanks, that was really informative to me. ‑‑gurkubondinn 22:09, 23 October 2026 (UTC)
This is a big reason as to why I don't agree with the two-tiered approach. I knew caste was a significant factor here, but I wasn't aware of just how much of one it was. —Jéské Courianov^_^vThrillerNight! 16:47, 24 October 2026 (UTC)
Did not know that. Given that, this should probably be extended confirmed so I'm changing my vote to a mixture of Option D and Option C, with ECR for cinema and ACR for CT/SA in general. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:04, 25 October 2026 (UTC)
Support D then C - While I agree this area is problematic, ECR is a very high bar to meet (it takes the average editor over 1 year). It's already overused in my opinion, we shouldn't be expanding it's use. Let's see if a lower restriction could work, it can be changed later if truly needed. InfernoHues (talk) 14:52, 23 October 2026 (UTC)
InfernoHues, I don't think it is a very high bar. For the ~14k editors that were granted extendedconfirmed in the past 3 years, the average number of days they were actively editing (i.e. actually saved a revision) is 109 days. And I'm guessing that that number would be lower for editors with editing objectives/interests that overlap significantly with WP:ECR coverage, editors who need EC to edit what they want to edit. Unfortunately, I can't test this hypothesis properly because of spotty templating of articles covered by WP:ECR (which may or may not be EC protected). We only have decent visibility into one contentious topic area via templating/categorization. Sean.hoyland (talk) 15:08, 13 November 2026 (UTC)
Option B. I'm not sure if anyone has brought this up yet, but G5 would be difficult and confusing to apply under option C. If a non-extended-confirmed account creates an article violating ECR, then a different non-extended-confirmed account could make significant edits to it, rendering the article ineligible for G5. I would imagine this scenario to happen often enough—either as a concerted effort or just naturally—to render option C significantly weaker than it would seem. Kisseran (talk) 18:55, 23 October 2026 (UTC)
G5 says no substantial edits by others not subject to a block, ban, or sanction. Based on that I believe the criterion would only be nullified if there are substantial edits by someone who is EC. Or are you saying that because the subsequent edits aren't article creations themselves, they could be construed as overriding the inappropriate creation? I can see how that might get messy based on interpretation. My original suggestion had included allowing non-EC users to submit drafts through AfC and only prohibiting direct creations in mainspace, but I think that would just increase the workload for reviewers even more, and full ECR is a cleaner approach. ChompyTheGogoat[Bleat|Munched] 04:23, 24 October 2026 (UTC)
Support Option B followed by Option C. I proposed the autoconfirmed restriction initially, but since then I've seen increased disruption from confirmed accounts and indeed even by EC editors who have reached that status purely through inappropriate edits to this subject area that have gone unreported. There's a huge mess that editors who haven't spent time patrolling these articles aren't aware of, and it's going to take us a long time to clean things up. I no longer believe option C is sufficient and I think we'd just end up back here debating increased restrictions after continuing to chase down more bad edits by autoconfirmed accounts. ChompyTheGogoat[Bleat|Munched] 21:22, 23 October 2026 (UTC)
Strongly oppose ECR ECR should be reserved for the worst of the worst topic areas. Movies may get a lot of passionate editors, but that's because movies are a universal experience. We all watch lots of movies and care strongly about them. Editing movies is a way that many editors come to Wikipedia. We'd be cutting off a significant avenue of recruitment for Indian editors by saying that only experienced editors can work in the topic. I have always worried that ECR would be extended into topics that truly don't need it, and this is a clear example. Movies have nothing on something like Israel-Palestine. I express no opinion on the other aspects, I just would hate to see ECR expand to...movies. CaptainEekEdits Ho Cap'n!⚓ 02:58, 25 October 2026 (UTC)
STRONG Oppose ECR, status quo we should not lock down everything and should leave ECR as option of last resort; it is a failure of all other systems and breaks wikipedias ethos of the encyclopedia anyone can edit, if only to protect in worst case areas. Eek is right, if there is need for this let arbcom do it. User:Bluethricecreamman(Talk·Contribs) 03:08, 25 October 2026 (UTC)
It's reductive to boil this down to just "movies." Like I've said, this is a hugely identitarian thing that intersects inextricably with caste, religion and culture in a way completely alien to the western film world. Athanelar (talk) 00:13, 26 October 2026 (UTC)
I don't buy that. Western cinema is just as full of propaganda/religion/culture, westerners just have a blind spot for their own media. If you've ever watched a twitter debate between movie dudes, its not very different. We're exoticizing Indian cinema and telling hundreds of millions of Indians that they're too passionate about their culture, so only the staid and sensible (and mostly Western) experienced Wikipedians can interpret their culture for them. CaptainEekEdits Ho Cap'n!⚓ 19:37, 28 October 2026 (UTC)
Rest assured I am not speaking from an entirely outside perspective here. I know a thing or two about a thing or two; South Indian cinema particularly, but the same issues abound all over. I really encourage you to read the other comment I posted here, if you ctrl+f "kapu" you'll find it. It really is nothing like anything that exists in Western cinema. Everyone knows Tom Cruise is a Scientologist, right? Now imagine like 80% of the USA are scientologists and slavishly devoted to watching Tom Cruise movies, and you're approaching the ballpark. Tollywood has a term, "TFI banisa", for its superfans. It literally means "Telugu Film Industry slave". I haven't heard any major subsection of the filmgoing western population calling themselves "Hollywood slaves". Imagine an entire cinema full of people screaming and hooting and throwing confetti at the screen because Tom Cruise or whoever their favourite action star is came on the screen. "Jai Balayya!" is something of a cultural catchphrase, meaning "Hail Balayya!" or something to that effect. Balayya of course being a major Telugu actor. Again, imagine if you could shout "Hail Tom Cruise!" in a public place and have at least a few people shout it back without hesitation.
Granted, the Telugus are about the mos extreme end of this spectrum, but it really, really is not the same in Western cinema. Athanelar (talk) 19:50, 28 October 2026 (UTC)
@Athanelar Could you please clarify your last sentence? ... I don't think many editors here are going to find creating a CTOP because the Telugus are about the mos[sic] extreme excessively convincing. To put it mildly.GreenLipstickLesbian💌🧸 20:17, 28 October 2026 (UTC)
I mean that as far as South Asian cinema superfans go the Telugus are probably the most extreme of the bunch, but that it also exists elsewhere, again c.f. Dhurandar. I just can't speak from a position of as much knowledge about other regional cinema industries because the Telugu industry is what I know best. Athanelar (talk) 20:32, 28 October 2026 (UTC)
Okay, let me rephrase: your comment is coming across as quite dismissive of an entire ethnic group. Could you please rephrase? GreenLipstickLesbian💌🧸 20:36, 28 October 2026 (UTC)
The fact that Telugu cinema fans are among the most devout and passionate is not an insult to them. Again, see "TFI banisa" above. The reason I said that is because I know a lot about the Telugu film industry and its fans and not as much about other South Asian regional industries, and I didn't want to imply that this same fan culture extends to Tamil cinema or Malayalam cinema or anywhere beyond, because I don't know if it does. I was defining the scope of my knowledge, not making a dig at the Telugus. Besides, I'm not sure how "Telugus are amongst the most extreme [cinema fans]" is any more disparaging to Telugus than Eek's statement Americans are overwhelmingly patriotic is to Americans. Also, to quote myself above, Rest assured I am not speaking from an entirely outside perspective here.Athanelar (talk) 20:47, 28 October 2026 (UTC)
You probably could have worded it better. "Extreme" is a word with quite a few negative connotations. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 20:48, 28 October 2026 (UTC)
Oh, please. My statement was Telugus are about the most extreme end of this spectrum and that statement comes at the end of a lengthy comment talking about how passionate Telugu film fans are. Literally what else could I possibly be referring to by "this spectrum" except their passion for film? Athanelar (talk) 20:54, 28 October 2026 (UTC)
You don't want to ask CaptainEek to rephrase or strike the statement Americans are overwhelmingly patriotic? Athanelar (talk) 21:36, 28 October 2026 (UTC)
Patriotic is a word which carries positive connotations. If the sentence had been "Americans are overwhelmingly nationalist", then this would be a different discussion. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:44, 28 October 2026 (UTC)
Patriotic is a word which carries positive connotations. For you, maybe. It definitely doesn't for me. Athanelar (talk) 21:47, 28 October 2026 (UTC)
With all cards on the table, I debated reporting this to AE, because casually using stereotypes is well below the standards expected in a contentious topic, but I prefer to avoid the drama if at all possible. I'd prefer not to, but saying that people of a certain ethnicity do or believe X is harmful, even if it's not ill-intended. GreenLipstickLesbian💌🧸 22:28, 28 October 2026 (UTC)
the Telugu film industry and its fans does not mean "all Telugus everywhere behave this way due to inherent ethnic factors". No derogatory statement was made and this smacks of western virtue signaling. ChompyTheGogoat[Bleat|Munched] 22:36, 28 October 2026 (UTC)
You're right; but the fact you take umbrage with what I said being an "ethnic stereotype" and not what they said is not because one of us did something wrong and the other didn't, it's because of your own Amerocentric worldview.
I have no interest in doxxing myself to win an argument, so I will leave it at asking you to please stop pearl-clutching at me. I have said nothing which is ethnically offensive to Telugu people, and I promise you I can say that with more than a reasonable degree of certainty. Anyone who has seen me around the project knows I'm not needlessly belligerant, if I'm standing behind my words to this extent I am doing so out of certainty that I've said nothing wrong. Athanelar (talk) 22:33, 28 October 2026 (UTC)
Now at WP:AE#Athanelar, in case anybody wants to make a statement about my behaviour during this discussion. Athanelar (talk) 23:31, 28 October 2026 (UTC)
That's exactly the point - you're applying your personal assumptions. I also dislike patriotism, but I don't assume negative connotations because I know most people don't intend it that way. Extreme is simply a modifier. "Extreme kindness"; "extremely charitable"; even "extremely passionate" can be positive - heck, I'd bet there are plenty of people involved with this topic who would see "extremely passionate about their favorite stars" as a positive statement. It's simply descriptive. ChompyTheGogoat[Bleat|Munched] 22:11, 28 October 2026 (UTC)
That's a fair explanation here. I withdraw my point, as this is a matter of opinion. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:12, 28 October 2026 (UTC)
Still carries negative connotations. When you say "extreme end", the first thing that comes to mind is extremism. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:43, 28 October 2026 (UTC)
If seeing the word "extreme" in the same paragraph as a mention of brown people makes your mind go to "extremism" when the context very obviously implies nothing of the sort that is a commentary on you, not on me. Athanelar (talk) 21:45, 28 October 2026 (UTC)
Implying that this is because it mentions Telugu people is an aspersion, and an assumption of my thoughts. It would be the same if we were talking about, say, Americans or Brits. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:46, 28 October 2026 (UTC)
I don't think I worded this well, so to clarify: the connotations would still be there if we were talking about any other people, and ethnicity has nothing to do with it. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:47, 28 October 2026 (UTC)
I highly doubt you would still be griping at me if I typed a paragraph about the history of Brits and tea consumption and ended it by saying "the British are among the more extreme end of this spectrum [of tea culture and tea consumption]" Athanelar (talk) 21:51, 28 October 2026 (UTC)
Actually, the first thing that comes to mind here is the American Revolution and the second thing that comes to mind is the slave trade. So yes, I probably would be griping at you here. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:55, 28 October 2026 (UTC)
I lived in an ultra-confederate lost-cause state for nearly a decade. That's why I made that logical leap. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:15, 28 October 2026 (UTC)
So it's your personal bias showing through, as we've pointed out. Not a universal interpretation. ChompyTheGogoat[Bleat|Munched] 22:17, 28 October 2026 (UTC)
It's less personal bias and more lived experience, but yes, I do now agree with your point that this matter is entirely subjective. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:19, 28 October 2026 (UTC)
Bias develops out of lived experience. No one is born with it but we all have them, and it takes constant work to attempt to overcome them - or at least prevent them from affecting your interactions with others. When it comes to marginalized groups listening to what actual members of those groups say is one of the best tools for doing so. ChompyTheGogoat[Bleat|Munched] 22:45, 28 October 2026 (UTC)
That is a fair point, and I agree. What is the relevance of your point about marginalised groups here though? (Sorry about my signature, I'm currently in the middle of changing it)
It's an aspersion to imply I could've meant literally anything untoward based on my word choice in this context. Athanelar (talk) 21:49, 28 October 2026 (UTC)
I'm not saying that, I'm saying that you could have chosen your words more carefully. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:50, 28 October 2026 (UTC)
An assertion which is based on the idea that the words I chose could possibly carry the connotation of "extremism" in this context, which is completely absurd. Bad day to be a fan of extreme sports, for all anyone knows you could be expressing your enthusiasm for Jihadi skateboarding. Athanelar (talk) 21:55, 28 October 2026 (UTC)
Extreme sports is a very idiotic wording and the first thing that comes to mind when you mention extreme sports is getting shot out of a cannon into a volcano. I am generally not a fan of the use of the word extreme as a descriptor unless it is talking about extremism, due to the fact that it contains those connotations of extremism to begin with. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 21:59, 28 October 2026 (UTC)
Sounds like you have an overall problem with the English language. Extreme has been used as a descriptor for a wide range of ideas before "extremism" was known as a specific concept. This is an extreme interpretation. ChompyTheGogoat[Bleat|Munched] 22:14, 28 October 2026 (UTC)
Once again, I do not think I worded this well, so to be more precise, "extreme sports" carries a connotation of violence. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:02, 28 October 2026 (UTC)
Extreme sports do carry a high risk of injury. That's precisely why it's used. And people still love them despite it. ChompyTheGogoat[Bleat|Munched] 22:15, 28 October 2026 (UTC)
Extreme sports have nothing to do with extremism but they bring those connotations to mind anyway. Maybe it's just a quirk of my brain, but synonyms are hard to comprehend to me. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:10, 28 October 2026 (UTC)
Also, "chicken" is not a negative connotation. "extreme" is. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:11, 28 October 2026 (UTC)
Not true! If I called you a "chicken" I'd be calling you a "coward". Does that mean one could conceivably argue that Chicken of the woods might, if you squint at it hard enough, mean "coward of the woods" and therefore if I say "I think chicken of the woods tastes great!" I'm some kind of Klingon who enjoys eating cowards?
I hope you're starting to see my point. In any case I think this discussion ought to end here because we're thoroughly derailing things. I need to move this all down to the appropriate section once it quiets down. Athanelar (talk) 22:13, 28 October 2026 (UTC)
I have heard the word "chicken" used in that context about 4 times before, so I think this is just a case of differences in opinion and perception. But yes, we probably should end this discussion here. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 22:17, 28 October 2026 (UTC)
"People are extremely passionate about this subject" is not a stereotype, nor derogatory. I could make the same remark in regards to many Western topics. The fact that it's racially charged is a significant factor in why it needs to be a CTOP. You wouldn't say people can't refer to ethnicity in a discussion about caste restrictions because it's intrinsic to the entire reason for the discussion. ChompyTheGogoat[Bleat|Munched] 21:28, 28 October 2026 (UTC)
I still don't buy that that is substantially different than "Guy who has seen all 38 Marvel movies" or "audience that claps at the end of a movie" or "screaming Beatles fans." Americans are overwhelmingly patriotic and turn out in mass droves to watch, funnily enough, Tom Cruise flavored military propaganda like Top Gun: Maverick. Indians being hype about home-grown cinema isn't surprising. Super fans are universal. CaptainEekEdits Ho Cap'n!⚓ 20:22, 28 October 2026 (UTC)
And it's certainly not unusual if you compare it to, say, American sports culture (I am an Eagles fan -- we are notoriously violent. Let alone throwing confetti at a screen, we'll throw projectiles at living people.) GreenLipstickLesbian💌🧸 20:29, 28 October 2026 (UTC)
Sure, and if an argument could be made that American sports fanaticism was leading to a lot of UPE and general disruption on Wikipedia then there would probably be a case for a CTOP there. We do after all have a CCTOP on pro wrestling (albeit not ECR) due to the same sort of thing.
The thing is, we probably wouldn't need any specific restrictions in this topic area if we instead had an abundance of editors doing cleanup and making reports for normal AE actions under the CT/SA area. But I think what Sennecaster (I think it was them?) has pointed out about the lack of South Asian cinema-related arbitration reports is a good example of a sort of survivorship bias. We don't see a lot of arbitration reports not because it's not a contentious area, but because there's not a lot of people knowledgeable enough/willing enough to do the required enforcement. Athanelar (talk) 20:38, 28 October 2026 (UTC)
And there are still other cultures that take sports culture much farther, which American fans are often unaware of, because people here can't see past the end of their own nose. ChompyTheGogoat[Bleat|Munched] 21:33, 28 October 2026 (UTC)
Right. Eagles fans are "notoriously violent" for throwing things. Ultras of Glasgow Rangers and Glasgow Celtic are "notoriously violent" because they regularly stab each other when their teams play. Athanelar (talk) 21:44, 28 October 2026 (UTC)
Eek, given the connexions between Indian cinema - not just the actual films themselves, but the entire industry - and caste (the latter of which you know is a perennial powderkeg looking for a lit fuze and is partly responsible for the Indian milhist 500/30) the question is less "Should we institute 500/30?" and more "Are we going to be forced to institute 500/30?" One way or another, I see Indian cinema being put under XCR for the exact same reasonsas Indian milhist. —Jéské Courianov^_^vThrillerNight! 17:01, 26 October 2026 (UTC)
If I were assembling a "how much does it matter that this article is accurate in the real world" tier list, MILHIST articles are A tier in importance, and movies--no disrespect to them--are C or D tier. Movie pages are very popular, and a good way to recruit new users. By shutting out the problem editors, we shut out good editors too. Movies just aren't that important to warrant cutting out such a big portion of our potential editor base. CaptainEekEdits Ho Cap'n!⚓ 19:46, 28 October 2026 (UTC)
See my comment below. I would contend that it's the exact opposite and it's not worth dealing with swarms of UPE/COI for the very small number of good faith editors who might make valuable contributions. It's really not the same as Western film - as Jeske said, almost all of them either have a conflict of interest or are true believers. The vast majority are SPAs with no interest in any editing beyond pushing their POV on these articles, regardless of whether they're getting paid for it. They are not improving the project as a whole. ChompyTheGogoat[Bleat|Munched] 21:48, 28 October 2026 (UTC)
Option C preferred. Option B is fine but this should then be revisited to tell if Option C is warranted. As already discussed by Athanelar and other, the caste issue is inextricable to this topic area and warrants the same treatment as the other topic areas. Οἶδα (talk) 22:05, 25 October 2026 (UTC)
Option A To be quite honest, a restriction this wide on a very active topic area is going to be nigh-impossible to enforce. Yes, there is a lot of UPE editing happening in this very broad area. Yes, there is also a lot of bad editing in this very broad area with new editors not familiar with our policies (or not caring about those policies). Yes, this is a lot of socking in this area that just don't care about Wikipedia policies, they just want their own way. I don't think the other proposals are actually viable. There would be lots and lots and lots of requests for blocks, protections, huge numbers of edit requests that will get ignored for far too long. Ravensfire (talk) 22:52, 25 October 2026 (UTC)
@Ravensfire: While I haven't yet made up my own mind about this proposal (I find both Athanelar and CaptainEek to have persuasive arguments) I would like to note that this rationale could have been used to oppose implementing ECR on Israel/Palestine as well. There were lots of protections requested when that was implemented, but the admins were able to manage it. QuicoleJR (talk|edits) 23:04, 25 October 2026 (UTC)
I think that in terms of the sheer number of articles that exist, this would vastly exceed the number for Israel/Palestine. The number of new articles that get created on a weekly basis is absolutely going to be more than exist in the IP area. Indian films, actors, actresses, directors, producers, music folks. Pakistan films, actors, actresses, directors, producers, music folks. Bangladesh. Television equivalents of all of that. This area is going to be absolutely massive. Ravensfire (talk) 23:40, 25 October 2026 (UTC)
And ECR would quash a lot of that. It's easy to just draftify anything created by non-EC editors - no deeper analysis required. If they keep trying to move back they get blocked. It would take time to work through the backlog, but it's certainly doable. EC editors following protocols can request protection out of the gate so their articles don't devolve. I don't consider "the problem is too big so we should let it continue being a problem" to be as viable argument. ChompyTheGogoat[Bleat|Munched] 07:05, 28 October 2026 (UTC)
@WhatamIdoing That 55k includes nonarticles (eg tagging files) and I think it's closer to 31k articles. There is also a Wikipedia:WikiProject Indian cinema but the two have a lot of overlap. On the other hand for whatever reason there are not many biographies tagged by either, so it would add I estimate another 10k. Allowing for a bit of undertagging and some other related articles, say 40-45k and growing at 3-5 articles per day.
It would not be our broadest contentious topic (that will always be BLPs) but it would be our largest under ECP, I think. Andrew Gray (talk) 09:14, 30 October 2026 (UTC)
Support D->C->B in that order of preference, Oppose A. We should try the least restrictive thing first and see if that works before trying more restrictive options, but let's try something rather than doing nothing. Levivich (talk) 00:18, 26 October 2026 (UTC)
First choice D, second choice A: ACR currently does not exist, but is intriguing (currently, WP:ACR points to Wikipedia:Your first article). I oppose ECR per CaptainEek unless and until it becomes clear that a less draconian restriction does not work. mdm.bla 00:35, 26 October 2026 (UTC)
User:Mdm.Bla, we have something extremely similar to an autoconfirmed restriction in the form of the aggressive semi-protection allowed in WP:GS/PAGEANTS. If a single logged out editor edits a beauty pageant-related page it gets semi'd indefinitely. There's a pretty strong BLP aspect there (especially relating to children) that fuelled it, I believe, although it was adopted before I began editing. Sennecaster (Chat) 17:17, 27 October 2026 (UTC)
Thanks, I didn't know about that! mdm.bla 04:58, 28 October 2026 (UTC)
Option C, Option D as second choice, with the understanding that the concern raised over WP:G5 under Option C (if an article is created in violation of the sanction and then receives significant contributions by autoconfirmed editors post-creation) would be enforced by only considering if there has been post-creation significant contributions by EC editors (otherwise you could just game your way past the restriction). The fact that it is unprecedented doesn't mean much to me since it is essentially just a remix of restrictions that we do already use, rather than some wholly new concept.
I hesitate to go for ECR without having tried something less hefty first. As it means only a tiny handful of readers can edit an article, it should only be used in cases where it is unfeasible to allow articles to go without it. This does appear to be true for certain kinds of Indian cinema articles, but to place the whole of Indian cinema under ECR should require that the whole of Indian cinema needs to be under ECR. I do not think that's been established here. ECR can be applied to those kinds of Indian cinema articles where it seems necessary as part of the WP:STANDARDSET, but for Indian cinema as a whole we should try to go with a lesser restriction first. If that doesn't work we can revisit the matter. –Maltazarianᚾparleyinvestigateᛅ 14:14, 26 October 2026 (UTC)
Option A first choice, D second choice (but see below). Oppose B and C as too heavy-handed. From my experience in RCP and NPP, the problem of disruptive editing and spam in the South Asian film industry area is no worse than that in South Asian (non-film) biographies, companies, politics, sports, etc.; and likewise caste is as intertwined with South Asian cinema as it is with virtually any other topic under CT/SA. (Which is, well, a complex topic and I could write plenty about it; but there's no point in typing out a lengthy essay on that here.)
As such I don't see why South Asian cinema should be specifically singled out for ECR or an autoconfirmed restriction since the arguments used above to justify such a restriction would apply equally well to any other CT/SA subtopic. I wouldn't necessarily be opposed to a blanket autoconfirmed editing restriction on all of CT/SA (though in my experience from RCP this restriction feels a little too severe), but this is not what the RfC is about. ECR wouldn't deal with the UPE problems since most of the organised paid editing syndicates operate accounts with XC anyways, and the non-XC paid editors generally produce blatant spam that can be dealt with without needing anything from the CTOP toolkit. The other disruption for the most part can be dealt with using tools already available under the standard sysop and CTOP toolkits.
I think that a blanket autoconfirmed restriction on South Asian cinema would have more benefits than drawbacks, but it comes off as too broad in scope to me since most of the disruption (as I see it from my experience in RCP and NPP) seems to focus on new or "hot" films (and their crew); famous or controversial films, personalities, etc.; and topics already clearly under the caste and milhist ECRs. Most (>80% I guess) pages in the area get very few edits and don't need protection. A narrower scope for option D which applies only to (for instance) films released in the last 365 days and their crew would be fine with me. JavaHurricane 17:02, 26 October 2026 (UTC)
Option A first choice, D second choice. South Asia movie/music scene is too large to have such tight restrictions. Many new editors from the region may be interested in editing the movies, and imposing a 500/30 restriction would be too harsh for them, killing the incentives to be an editor. In my opinion, South Asia move scene is less controversial and explosive when compared to other contentious topics such as the Israel/Palestine issues, and we still have WP:CT/SA to if manners escalate to nationalism or caste issues. If the goal is to prevent LLM-made article, that job is for the WP:NPP instead of creating another restriction. We can also try to narrow the scope of the restriction - maybe only restrict movies that have racist/caste issues undertones? ✠SunDawn✠Contact me! 17:30, 26 October 2026 (UTC)
A large number of those "new editors" are UPE (who may not actually be new), and the vast majority never contribute in any other subject areas. TAs and SPAs abound. Getting drawn into editing in general and becoming a constructive editor who follows P&Gs is exceedingly rare. I've advised others who at least attempt to comply to try editing elsewhere to gain experience and reach EC, and it falls on deaf ears. They don't care about anything else. ChompyTheGogoat[Bleat|Munched] 05:17, 28 October 2026 (UTC)
Option A per Java Hurricane and SunDawn. Bad faith editors can easily game EC and AC, so the people most affected by these editing restrictions are potential new editors, the very group the community keeps saying that we need more of. Some1 (talk) 03:00, 27 October 2026 (UTC)
Option A for now. I'm open to ideas about restricting article creation in parts of WP:CT/SA bc of high rates of LLM/UPE/socking, but I am unconvinced by the AC editing restriction, especially for South Asian cinema, which likely has way more good faith editors than other subtopics like South Asian incorporated entities (businesses, schools, etc.) NicheSports (talk) 18:30, 27 October 2026 (UTC)
I support an ECR article creation restriction, but oppose any general restriction on editing. South Asian films are a hugely popular area for casual editors and are some of our most viewed articles. A general autoconfirmed restriction would lock out huge numbers of casual editors, while doing little to prevent the determined abuse and sockpuppetry these proposals are aimed at. OTOH, an ECR restriction on new article creation may have an impact on the widespread promotional/UPE sockpuppetry focused on boosting non-notable actors, films, and other topics in this area, while having minimal impact on casual editors interested in what they're seeing in the cinema or in the news. Toadspike[Talk] 01:45, 28 October 2026 (UTC)
Status quo, strongly oppose putting the area under an ECR restriction; our top-viewed and edited articles on the website are often South Asian-cinema related. If we're going to block off casual and new editors from incredibly popular topics, there needs to be a good reason. The editing around most entertainment topics, especially fandom related, is pretty universally shit -- and I spend enough time cleaning up after UPEs and awful editors in the film world to know that the South Asian topic area isn't actually that worse than, say, the American or European industries. GreenLipstickLesbian💌🧸 06:40, 28 October 2026 (UTC)
But the latter are actually policed. They don't make any headway. ChompyTheGogoat[Bleat|Munched] 07:06, 28 October 2026 (UTC)
LMFAO no. Sorry, but.... no. They are not policed effectively. GreenLipstickLesbian💌🧸 07:13, 28 October 2026 (UTC)
Sorry if that came off a bit sharp, but I've removed too many decades old press releases copy-pasted in to articles by administrators to do anything other than laugh at the idea that this is effectively moderated. GreenLipstickLesbian💌🧸 07:17, 28 October 2026 (UTC)
It is in relation to the topic area under discussion. You saw the problem and removed it, because you are part of that moderation. Indian cinema has minimal enforcement of any kind. ChompyTheGogoat[Bleat|Munched] 07:26, 28 October 2026 (UTC)
By that standard, we'll only know in 10 to 15 years whether or not the moderation is the same. GreenLipstickLesbian💌🧸 07:50, 28 October 2026 (UTC)
Huh? The topic has already existed for years and gone largely unmonitored. It won't take long to see whether or not restrictions start having an impact on new additions. Heck, even working RCP it ought to be noticeable once enough protections are applied that they start popping up less often via the various tools. Newer articles won't have pages of edits by TAs and redlink users with zero edit summaries that make it difficult to even track down where the problems are.I've never pulled up an article for a Western show/movie and immediately thought "Wow, this is barely even intelligible". Some of them certainly need improvement and yes, there can be sourcing issues, but it's just not on the same level. Even Fandom insertions are better quality. Can you imagine a recent Hollywood blockbuster with entire sections totally unsourced? (Casting is hardly ever sourced, so there's no easy way to check whether an addition is legitimate or a UPE trying to claim a false credit for their client.)Old articles being allowed to languish in a subpar state isn't unusual in any subject area, and not the main issue here. No one will ever get around to working on those when newer ones are so rife with bad edits. ChompyTheGogoat[Bleat|Munched] 09:31, 28 October 2026 (UTC)
You're telling me I'm "part of that moderation" because I'm removing ancient issues which slipped past RCP because admins added it; I'm going to say that, if you're judging whether or not moderation of an area is successful by whether issues survive over two decades, by the metric you set for me and Western shows, we're going to have to wait a very long while to see if this works.
I am afraid I have to disagree with you on your second point too I spend most of my time looking at old articles in subpar states; I can safely say that, speaking from experience, entertainment articles are, across the board, much worse than any other group. They get a flurry of edits when the show or movie first comes out, from fans and PR people alike, then they sit in that state forever. Sometimes fans hang out and add fancruft, copied from fandom (which was copied directly from the marketing department and laundered through Fandom half the time so, no, not better than UPE in any meaningful way.) No industry is unique for that -- Kdramas, Masala films, MCU blockbusters. Don't believe me? check my edit history. Or, do as you suggested and spend some time actually working cleanup in this subject area to see just how extensive the problem is. GreenLipstickLesbian💌🧸 10:19, 28 October 2026 (UTC)
I will not be working any areas ever because my contributions don't appear to be welcome on Wikipedia. But what your describing isn't remotely close to the issues in the Indian cinema subject area. At all. The fact that fandom content is still better than many of these despite how problematic it is was my point. ChompyTheGogoat[Bleat|Munched] 11:10, 28 October 2026 (UTC)
No, Fandom content is not better -- if anything, I've found it's much, much, much harder to clean up because, again, the spam has been laundered and divorced from many of the obvious flags that RCPs like yourself check for when spam hunting. But I'm afraid we'll have to agree to disagree -- funnily enough, I checked the date your account was registered, and I was actually working on cleaning up my favourite spammy Manipuri film industry sock farm that very same week. I'm not big on metaphors, but I think this is the equivalent of teaching your... well, not grandmother, so let's just say your big sister to suck eggs. GreenLipstickLesbian💌🧸 11:58, 28 October 2026 (UTC)
Would you two mind if I move this conversation under the "Discussion" heading? It's a bit lengthy and tangential for the survey section. Athanelar (talk) 12:06, 28 October 2026 (UTC)
Option B as first choice. Descending options C->D after that. Every time I see anything on an Indian film on this project it's either because there's an edit war over box office figures or it's because there's an edit war over its interface with Indian politics. I think we need to treat this as an integral part of a contentious topic and keep it as locked down to responsible editors as possible. We should also consider excluding box office figures from infoboxes as a matter of policy (not just for Indian cinema) and only discussing box office figures when such are well sourced and encyclopedically relevant. Simonm223 (talk) 11:30, 28 October 2026 (UTC)
I would happily ban all box office stats unless mentioned in depth in reliable sources, across all cinema -- even in this topic area, the sources the regulars revert to (Bollywood Hungama) are not particularly better than the ones they revert out with a high degree of aggression and warnings (Sacnilk, and every source which sites it). Like the victor parameter in the infobox conflict, it just causes more strife and edit warring than good editing. GreenLipstickLesbian💌🧸 12:02, 28 October 2026 (UTC)
Wildcard, devil's advocate proposal (and sorry if this is already what you mean by this!): we could just ban box office figures in general unless it's a significant part of the notability and discussion surrounding the film (like Avatar's remarkable box office success), since otherwise it's really not important to an encyclopedia, right? This'd have to be a separate discussion, but I think I'd probably be in favour of a moratorium on box office figures in film articles. Athanelar (talk) 12:09, 28 October 2026 (UTC)
I'd support that in theory, but it's only viable if we do achieve ECR. Otherwise it's easier to allow them from accepted sources than spend even more time fighting all insertions instead of just the ones that aren't adequately supported, which is hard enough. People get pissed when I get protection on an article and they can't continue to update it every five minutes. And @GreenLipstickLesbian as I've already mentioned we've attempted to initiate reviews of the different sources to no avail. I agree that BH doesn't seem particularly more reliable than others to me based on what I've read and I asked for them to be objectively evaluated based on firm criteria rather than just vibes, but until and unless that occurred I followed established consensus, as do the others monitoring those articles. So once again, the lack of input from experienced editors without bias is the underlying problem. (I think I'm the only one who's actually gone through and read the previous discussions leading to the current designations, and they do not inspire confidence.) ChompyTheGogoat[Bleat|Munched] 22:03, 28 October 2026 (UTC)
This is part of why I want to put ECR on this - I think restricting access to editors who have been around long enough to, in theory, have learned "don't put box office figures in an infobox" is needed to prevent edit wars over box office figures. Simonm223 (talk) 12:19, 29 October 2026 (UTC)
I would somewhat oppose full ECR restrictions; I believe that should be reserved for the most controversial topics when truly necessary. While South Asian cinema definitely has ties to the restricted topic; I doubt that it belongs at the same severity. So I would support C or D. There are a few autoconfirmed users who cause trouble, so I can understand the B position; but I'm not sure if it's enough to warrant it. Dawn Lim (talk) 11:38, 28 October 2026 (UTC)
Option A have seen no evidence that Indian cinema is so far worse than the rest of CT/SA that additional restrictions are warranted. ~~ AirshipJungleman29 (talk) 12:19, 28 October 2026 (UTC)
Support B > C > D. This is a very UPE spam and copyvio prone topic, so much so it's as if an entire cohort of editors doesn't know what a good article looks like. I consider the entire topic a no-go area. MER-C 19:20, 28 October 2026 (UTC)
Option B - This topic sees the most disruption, sockfarms and UPE in CT/SA. It should be placed under ECR. Zalaraz (talk) 00:56, 29 October 2026 (UTC)
Option B - this is the best / most realistic option for balancing resources. The best articles will still make it through, but there is a big capacity issue currently. A good encyclopedia, rather than a fast one. ChrysGalley (talk) 12:58, 10 November 2026 (UTC)
Option A. I've been weighing this for a while. Indian cinema is undoubtedly a locus of much UPE and COI editing (I have uncovered a fair share of this as a CU). That said, it is also the locus of a very large volume of good faith editing. There are tons of editors entering the area out of nothing more than an enthusiasm for cinema, much more so, I'd argue, than the average CT/SA subtopic. The collateral damage from a topic-wide ECR will be enormous, in terms of constructive edits prevented and potential editor recruitment opportunities lost. There will also be a very large cost to enforcing ECR. ECR is not pixie dust; admins are needed to protect some pages, pages that aren't protected need constant reverts, reverts need explanations. I'm more open to the idea of prohibiting article creation by non-EC editors. Even there, however, we need to think carefully about the cost. We can't prohibit creation technically unless someone is creative enough to write a good filter. This means there will still be a large maintenance cost to ECR. That cost is rarely worth paying: even in PIA, where we are dealing with committed long-term state-funded propagandists of several kinds, the cost is debatably worthwhile. I don't know that we're at that point yet in south asian cinema. If everyone were to dedicate the effort they would put toward ECR enforcement toward UPE- and COI-patrolling instead, I suspect we'd be much better off. Vanamonde93 (talk) 19:57, 12 November 2026 (UTC)
Option A. ECR would do very little to stop our most persistent COI/UPE sockfarms in this topic area, many of which are more than capable of getting their socks to EC, while creating a huge amount of collateral for good-faith editors. Most of the disruptive editing from new accounts is concentrated on a relatively small number of pages about high-profile films (particularly those with connections to politics), which we can address through short-term page protections and the other standard tools available without the need for a broad ECR. I'm open to considering an ECR on article creation, essentially per Toadspike, but I'm not yet convinced that it's worth the very large enforcement burden that it would create. MCE89 (talk) 01:37, 13 November 2026 (UTC)
Option A. Some editors who make reports in this area seem to think that "UPE" means "a user is really interested in this movie" and "sockpuppetry" means "multiple users are really interested in this movie". Obviously real problems with UPE and sockpuppetry do exist (I've made plenty of blocks myself), but MCE89 is right that the repeat offenders aren't going to be deterred by any of these restrictions. The enthusiastic good-faith new users who don't really understand our policies certainly will be deterred, and I guess that would reduce disruption to some extent, but supporting on that basis seems like more of a retreat from "anyone can edit" than I'm really comfortable with. Extraordinary Writ (talk) 07:48, 15 November 2026 (UTC)
I agree with you about the problem of seeing an undisclosed paid editor under every bed. WhatamIdoing (talk) 21:45, 16 November 2026 (UTC)
Option A It is not a controversial subject. That said, the movies about Indian caste and Indian military history still require ECP. THEZDRX(User) | (Contact) 14:50, 15 November 2026 (UTC)
Option A Caste and military history are plagued with ethnonationalism and unreliable colonial-era historiographies and ethnographies. Indian entertainment has issues with paid churnalism, but there is nothing that requires a blanket ECR. You know what else is prone to churnalism? Cryptocurrency. So rather, I'd suggest a 1RR restriction like WP:GS/CRYPTO. The fancruftery and sloppy editing are nothing that I haven't seen on other articles about fiction and from editors with poor English skills, respectively. The attitudes that endorse ECR on that alone seem to be motivated by xenophobia rather than the facial absurdity of that Maldivian guy who insistently corrected fleet to feet because there are no syllable-initial consonant clusters in Maldivian. –LaundryPizza03 (dc̄) 19:35, 15 November 2026 (UTC)
I oppose pre-emptive lockdowns of all articles about South Asian cinema. I've no objection to admins granting page protection requests more often than usual, but it should be in response to a problem that can't be fixed with a single click of the Undo button. I'm also concerned that some editors believe that a pre-emptive lockdown of tens of thousands of articles can be justified by a claim that uncited content is being added. Some film content should be uncited, per WP:PLOTSUM standards, and anyway, WP:V only requires citations for four types of information, and therefore not for the other things. In particular, if you're a cinephile, your idea of what's Wikipedia:Likely to be challenged is probably narrower than mine, so you would correctly not cite content that I might cite. The mere fact that a little blue clicky number is not being added is not automatically proof of wrongdoing. We do not have a one-source-per-article rule (except for BLPs), much less a one-source-per-parapgraph or one-source-per-sentence one. As for the WP:PROMO concern, it's long been the case that "one man's promotionalism is another man's encyclopedic content", and when you cross cultures, it's particularly fraught to declare that someone else's ordinary, everyday description is "promotional" just because their culture (or personal style) is more expressive than your own. WhatamIdoing (talk) 22:21, 16 November 2026 (UTC)
As I said in the first discussion, and as @ChompyTheGogoat has now summarised; no one else seems to care that [Indian cinema] is rife with UPE and unsourced content, We have a whole corner of Wikipedia that's chock full of WP:PROMO.
Non-Indians have a tendency to underestimate the social role which cinema plays in India, and the degree to which nationalism, casteism, regional pride etc intersect with cinema. One needs only look at the mass reception to releases like Dhurandhar: The Revenge and the political discussion surrounding them to see that. I would go as far as to say that cinema can be just as controversial to an Indian audience as caste topics are (and they're often linked!) so it's no wonder that we see so much tendentious editing in this topic area.
I still insist that it would be sensible to place some degree of restriction on the Indian cinema topic area to maintain article quality, minimise disruption, and reduce the effort required for cleanup (although the extent to which anyone is trying to clean it up right now, I have no idea.)
Just to throw another example which came to mind, I remember the effort I had to go to in order to clean up Udit Narayan, an article about a playback singer which looked like this before I edited it in December. In January a sockpuppet again edited it back into a promotiomal mess. This was reverted and has since been stable, but it goes to show how a seemingly innocuous article can turn into a complete mess just becausr of the subject's relation to Indian cinema. Athanelar (talk) 10:48, 19 October 2026 (UTC)
Thanks for opening this. I stumbled into the subject mostly by accident and I've been doing what I can, but I'm only one person, and I've mostly been focusing on reverting and protecting - I'm not the right person to attempt to clean up the existing issues in articles. There is a existing task force, but from what I've seen most of the people involved appear to be fans or people who otherwise have a vested interest but also uphold WP principles and do their best to follow protocols with their editing. Unfortunately many of them aren't very experienced, especially with editing in any other areas. What we really need are more experienced editors who have no personal interest in the subject (like me) and can maintain NPOV. I've discussed it with others and was waiting on @IrisChronomia to write up a proposal, as they're more experienced, but I'm sure they have other priorities. The main idea we came up with was to require AfC for all new articles on the subject by editors who aren't EC (or autopatrolled, if there are any who aren't also EC). Anything else can be automatically draftified without attempting to determine notability, sourcing, or whether the creator is a UPE sock. That only covers part of the issue, however - there's also a huge amount of problematic editing on existing articles. Personally I'd love to see semi protection applied by default, but I know that's a tall order. I'm open to other suggestions that would have a similar effect on minimizing disruptive editing by all the low edit count TAs/SPAs/UPEs/likely socks. Semi protection has solved most of the problems on most of the articles where I've requested it - only one had to be taken up to ECP. Most of them won't bother edit gaming and only reach autoconfirmed via edits to their target articles (if at all).In terms of the overall project it would really help to have a few unbiased volunteers with experienced working AV. Even if they're like me and don't want to spend too much time trying to fix existing issues it would make a big difference if we could crack down on all the problematic editors so things don't continue to snowball - then we could chip away at improving existing content. Maybe someone could build a tracker for the project so that people can easily flag for COI, LLM, unsourced, etc. and editors who are involved can work their way through the list.One other specific problem that's taken up an inordinate amount of my time (and is the most common reason for protection) is box office figures. This is (apparently) a very hot button issue that has a lot of bearing on how successful a film is considered, and there have been scandals involving gaming of reports. I know it's been discussed on wiki before (maybe someone else can find the links), and as far as I can recall the overall consensus was that it's relatively trivial to anyone not involved with the topic - and certainly doesn't need to be updated every five minutes! - but given how obsessed people are it's easier for us to allow them to be posted from reliable sources and focus on inappropriate insertions rather than trying to shut it down entirely. The issue is defining reliability. There are no official reporting sources in India, and BO trackers don't disclose their proprietary protocols, so we can only take their word on accuracy, and there can be a significant discrepancy. Current consensus within the project is to follow WP:ICTFSOURCES. Unfortunately, one of the most prominent sources - Sacnilk - was determined to be unreliable, and many otherwise reliable media sources quote their figures and must therefore be excluded as WP:FRUIT. I dug into things further and found that the actual discussions (such as they are) leading to reliability determinations for the handful of sources with independent internal tracking (including Sacnilk) were mostly based on vibes, not any particular proof that the figures or methodology are accurate. We've attempted to initiate re-evaluations at Wikipedia talk:WikiProject Film/Indian cinema task force#Reassessment of Sacnilk.com, Wikipedia:Reliable sources/Noticeboard/Archive 525#Reliability of Indian cinema box-office trackers, and Wikipedia talk:WikiProject Film#Reliability of Indian cinema box-office trackers, with no success. I don't personally care one way or another but I'd like to see standards applied consistently.We aren't going to be able to make any progress on this unless editors are willing to step up and at the very least participate in discussions so we can establish said standards for others to enforce. People have to care, or it's only going to get worse. AI has made it far too easy for anyone to churn out a PROMO article in five minutes and get paid. ChompyTheGogoat[Bleat|Munched] 18:49, 19 October 2026 (UTC)
I'll also submit that if no one cares enough to argue against it, a few of us involved with AV/SPI can constitute a consensus to implement CTOP requirements. ChompyTheGogoat[Bleat|Munched] 19:04, 19 October 2026 (UTC)
Thanks for chiming in. I fully agree with the restrictions you've proposed, including both the AfC requirement as well as semiprotection. Athanelar (talk) 19:45, 19 October 2026 (UTC)
My suggestion of semi-protection across the board may turn out to be inadequate - I've just submitted two more for ECP. Not all articles are subject to the same level of disruption though, and I think we could at least trial it with semi and a low bar for ECP upgrades at WP:RPP. Maybe the disruptive editors will start to get the hint. Hey, a girl can dream, right? ChompyTheGogoat[Bleat|Munched] 03:22, 20 October 2026 (UTC)
Oop, I meant to tag him, thanks for that! Athanelar (talk) 19:45, 19 October 2026 (UTC)
Support the use of ECR for Indian cinema, presumably this would be through a WP:GS designation by the community. I wasn't aware of the social role that Indian cinema has until I started seeing the disruption (and LLM junk) here on enwiki, and I have not really watched any Indian movies to any real extent (saw one or two years ago but I can't remember which movies right now). I have no stake in this other than as an enwiki editor. ‑‑gurkubondinn 07:13, 20 October 2026 (UTC)
I would absolutely be in favor of an additional restriction on South Asian cinema. It's an absurdly deep source of UPE, sourcing issues, junk AFCs clogging things up. The Indian cinema task force has done a really good job at WP:ICTFSOURCES, but simply put, the people that want to write articles and force in content about every third-tier actor who appeared in a fourth-tier movie, and everybody who worked on or was even tangentially related don't follow that guidance. It's a real timesink on the community and noticeboards and LLMs have made this area even worse. CoffeeCrumbs (talk) 22:04, 19 October 2026 (UTC)
Strong support for ECR (creation of articles) and confirmed (any edit at all).
Is there anything else I'm forgetting from our previous discussions? I'm slightly afraid to attempt to dig back through all the threads. ChompyTheGogoat[Bleat|Munched] 03:16, 20 October 2026 (UTC)
Indian cinema already falls under WP:CT/SA. One of the existing example sub-CT topic bans is "Indian entertainment, generally or in a specific language", and another is "Indian political, ethnic, religious, and caste topics", which as mentioned films can tie heavily into. Given this, for those with deep experience in the topic, what existing potential remedies (WP:STANDARDSET) are not being used that would be helpful? Are existing potential actions being rejected, and if so, for what reasons? From reading above, it sounds like the issue may be a lack of people and understanding ("it would really help to have a few unbiased volunteers with experienced working AV"), in which case it would perhaps be a good idea to create some sort of information page at WP:ICTF that editors (including admins) can look at to get acquainted with the topic's challenges. CMD (talk) 04:21, 20 October 2026 (UTC)
I think we would need explicit consensus that current ECRs apply to cinema, as opposed to the subjective "tie into" - or designate it an additional subtopic per resolution 6b. By my reading military and castes are the only subtopics currently subject to said restrictions; anything more general is only covered by the default CTOP protocols. I would be more than happy with an admin action extending ECR. That would mean any article within the subject area should receive automatic ECP approval, correct? ChompyTheGogoat[Bleat|Munched] 04:35, 20 October 2026 (UTC)
The specific proposal here is to make sure ECR or similar applies. The standard set isn't really helpful if the number of people doing cleanup is slim to none compared to the people making the mess. It's an impractical amount of workload for the people doing the cleanup to individually report editors and articles for standard arbitration remedies. SA cinema needs to be under preemptive restrictions to reduce the quantity of bad edits coming in. Athanelar (talk) 05:16, 20 October 2026 (UTC)
And when I first realized the scope of the issue I did review the above arb case, and my interpretation was that the restrictions as currently worded don't apply in this area. I'm happy to be corrected in that regard. It's not the first time I've seen someone imply that ECR applies to a wider subgroup, but I think that may have something to do with the various amendments over time. If we implement ECP across the board I expect the disruption would drop to virtually nothing, and while there would be significantly less overall editing we could do more cleanup of the existing problems and less policing of new ones. SPAs often wouldn't even break autoconfirmed without being able to edit film articles, let alone EC. ChompyTheGogoat[Bleat|Munched] 05:23, 20 October 2026 (UTC)
Or when a large part of the people making the mess are using LLMs to make the mess, the asymmetry of effort becomes enormous. ‑‑gurkubondinn 07:42, 20 October 2026 (UTC)
Remember, the scope of WP:CT/SA was changed earlier this year to make the ECR restriction limited to South Asian castes and Indian military history (broadly construed). I don't think this is a case where additional documentation would be helpful; it's nearly impossible to get these participants to acknowledge sourcing in these areas, and it nearly inevitably ends up with blocks or restrictions at ANI. The problem isn't that there aren't enough knowledgeable editors in this area, but that there already a lot of knowledgeable editors in this area, pushing back at a tsunami. CoffeeCrumbs (talk) 09:52, 20 October 2026 (UTC)
Support 500/30 rule for Indian cinema topic area - What do Indian cinema and Indian military history have in common? Both are intrinsically linked to caste, which has been THE primary motivator of problems with regards to the India topic area. The standard set is irrelevant as Indian cinema already falls under WP:CT/SA and thus it can be assumed discretionary sanctions are already on the table. The problem is more dealing with blatant mercenary editors and the caste/nationalist warriors that come out of the woodwork in defence of a film that supports their caste or weltanschauung. —Jéské Courianov^_^vThrillerNight! 06:22, 20 October 2026 (UTC)
Both are intrinsically linked to caste, Huh? That's entirely false. I'm fairly certain that the scores of WP:UPE editors in the Indian cinema topic area are not motivated purely by nationalistic or caste-specific sentiment. You do get the odd film that flares nationalistic rhetoric (for example Dhurandhar: The Revenge) but tbh that is not significant enough to require a special carveout, SASG and IMH are good enough for those. The problem that it looks like we are trying to solve is UPE Sohom (talk) 08:55, 26 October 2026 (UTC)
@F0malhaut42 and @Athanelar There might be underlying caste lines in the Telegu industry but those are not the ones that have seen the most problems onwiki. For what it's worth, the WP:UPE disruption is not confined to just the Telegu film industry. UPE disruption exists in the Tamil industry, Telegu industry, the Bengali film industry, the Hindi one and potentially even the Punjabi one. The constant and primary disruption factor onwiki is WP:UPE, not motivated editing (which would require significantly different considerations) denoted by the fact that that most of the reports related to disruption show up on WP:SPI and not WP:AE and are typically less about POV-pushing of specific caste-associated sets of movies (obviously we ignore the SASG specific ones like Dhurandar that are already covered by ECR) Sohom (talk) 00:53, 27 October 2026 (UTC)
It's both. There are tons of disruptive editors who can't be taken to SPI because a bunch of unsourced insertions with no edit summaries or attempts to communicate leave no proof either way. I've been accused of bias numerous times for blocking such changes. There's nothing to take to AE because the current restrictions are too vague to apply to this problem. If they did we wouldn't need to implement additional ones. ChompyTheGogoat[Bleat|Munched] 23:35, 27 October 2026 (UTC)
FYI for those participating in the discussion: I think the best way to go about this is that after a couple more days of discussion, if there is consensus (and there does seem to be) to designate a CTOP here and impose ECR on that topic, then I'll open a subsection here for an RfC on that question so that more people can be notified and we can get a robust consensus. If anyone disagrees with that approach, please do say so.
Based on what's been said so far, these are my proposed RfC prompts;
A. Status quo: South Asian cinema remains under the broader WP:CT/SA but is not subject to specific subtopic restrictions
B. South Asian cinema, broadly construed, is noted as a subtopic of CT/SA and placed under the extended-confirmed restriction.
C. South Asian cinema, broadly construed, is noted as a subtopic of CT/SA. Article creation is restricted to editors with extended-confirmed permissions. The topic area as a whole is placed under autoconfirmed restriction. (not sure if autoconfirmed restriction has precedent?)
Please give feedback/workshop these however you think necessary.
N.B., "South Asian cinema, broadly construed" includes films as well as all associated cast and crew including musical directors, musicians and playback singers primarily working in film, and is specifically inclusive of India, Pakistan, Bangladesh and Sri Lanka. Athanelar (talk) 06:46, 20 October 2026 (UTC)
Please note the above is not supposed to be the survey itself, just workshopping the questions. I'll transclude this response when I do open the RfC if you want, though. Athanelar (talk) 07:39, 20 October 2026 (UTC)
Option C as first choice, Option B, as second choice. I don't think autoconfirmed is pointless here. While registered editors can certainly game autoconfirmed, TAs are a sizable chunk of the problem, and they can't be autoconfirmed at all. It's not uncommon to have to tangle with a TA editor on a slop article four or five times in a day as they rapidly jump TAs and IP ranges. CoffeeCrumbs (talk) 09:56, 20 October 2026 (UTC)
Not pointless, but possibly insufficient. I suggested an autoconfirmed restriction initially both to be conservative and because I expected ECR would get tossed out as WP:SNOW. Just since that earlier comment multiple articles have been subject to ongoing disruption by a gaggle of editors barely over the confirmed line. There are some low count editors who make valid improvements, but I'm not sure the scale of their contributions is enough to offset the scale of disruption. My suggestion to one good faith editor who was stopped by ECP was to work on other subject areas and reach EC if they're that interested in continuing to contribute to film articles, which seems perfectly reasonably for any others in the same boat. More experience will help them do better work. (They were only inserting box office figures from accepted sources anyway, and getting increasingly frustrated by the limitations, so...) ChompyTheGogoat[Bleat|Munched] 14:51, 20 October 2026 (UTC)
I'd concur with this view leaning towards option C, noting that we can always revisit this if it turns out that this just turns the TA disruption into autoconfirmed account disruption. In my experience it's much easier to weed out and halt autoconfirmed accounts than it is to address IP-hopping TAs, so I think it's worth giving it a shot. signed, Rosguilltalk 14:59, 20 October 2026 (UTC)
You might want to check my latest RPPs. We'd have to go around dropping an awful lot of blocks. ChompyTheGogoat[Bleat|Munched] 15:04, 20 October 2026 (UTC)
I would add on to Rosguill's reply that one also has to consider achieving consensus. My feel for the community -- which may of course be wrong -- would be that going too far, too fast, here would undermine consensus building, even if that ends up what we have to eventually do. LLMs are a much larger problem than cinema of South Asia, but I don't think we'd have as quick success getting the policies closer to where they needed to be without the incremental steps first taken.
If autoconfirmed turns out to not be sufficient to manage this situation -- and I think this is one of the probable outcomes -- with there already being a restriction established and in place, it's not as much of a leap to go to ECR. I think as a principle, you want to try community solutions first; I believe that ethically, we have a responsibility to try to solve these issues as a community ourselves and only escalate it when we have to. That may make resolutions slower, and a bit messier, but I tend to think that the community can be too quick to make things admin/ArbCom headaches when they should be our headaches initially. This is one of the reasons I'm so active at explaining blocks to admins; admins have a toolset to do specific things, it shouldn't necessarily be their responsibility to have to also go into a billion dreary discussions explaining why sources are need or why legal threats are bad and why you can't just start a new account when you're blocked. I don't mean any of this as a dig at you, just explaining why I feel this way. CoffeeCrumbs (talk) 17:35, 20 October 2026 (UTC)
I think having admins designate it under the 6b resolution would be more expedient than running it through RfC, given that there is obviously long term extensive disruption. On the off chance they fail to reach consensus we could fall back on community designation.And thank you again for initiating this! My mental health appreciates it. ChompyTheGogoat[Bleat|Munched] 14:29, 20 October 2026 (UTC)
The 6b provision says Such extensions must be of a limited duration, not to exceed one year. There's no reason to believe this will get any better in one year, so we'd be better off doing it indefinitely by community consensus. Athanelar (talk) 15:41, 20 October 2026 (UTC)
Oops, I missed that part. I think I'd still like to see that enacted for now - I can easily foresee hordes of canvassed SPAs flocking to an RfC and dragging things out for god knows how long. If admins shut down their editing in the area to allow us to start to get a handle on things maybe they'll give up and find better hobbies, so we can tie up the community side to make it permanent. ChompyTheGogoat[Bleat|Munched] 15:59, 20 October 2026 (UTC)
RfCs aren't headcounts, they're debates. It doesn't matter how many SPAs participate if their arguments are spurious, the side that wins is supposed to be the side with the better policy-reasoned argument. Athanelar (talk) 16:08, 20 October 2026 (UTC)
I realize that, but they could still drag things out indefinitely. We've seen socking on AfDs in the subject area that can get out of hand. ChompyTheGogoat[Bleat|Munched] 16:12, 20 October 2026 (UTC)
I would suggest a fourth option be added here, that being Option C but applied to CT/SA as a whole and not just the topic of Indian cinema. ғѳmɑɭʱɑυե(Any pronouns)ᵀᵃˡᵏ 06:29, 22 October 2026 (UTC)
Support Option C then Option B - Option C would restrict many of the SPI throwaway accounts who operate heavily in that space. However, it would could be a nightmare to enforce and cause more issues than we alrady have. Option B would be my second choice. --CNMall41 (talk) 20:44, 20 October 2026 (UTC)
What part would be hard to enforce? We can slap protection on most articles instead of needing to wait for disruption first and chasing dozens of editors to noticeboards. ChompyTheGogoat[Bleat|Munched] 21:11, 20 October 2026 (UTC)
This definitely needs an RFC. The lack of experienced South Asian editors commenting here is a concern as are the derogatory comments about the ICTF from a ten month editor. There should be no rushing into action before a properly run RFC in my view Atlantic306 (talk) 23:27, 20 October 2026 (UTC)
Nobody is rushing into anything. I fully intend to hold an RfC on this once it's had a day or two more for any points of discussion to be raised, for any feedback to be given about the proposed RfC questions and so on. Athanelar (talk) 03:28, 21 October 2026 (UTC)
@Athanelar I am assuming this meant is to include actors, directors, etc. I suggest changing the wording to "The topic of South Asian cinema...." which aligns with the wording for Indian military history. I also suggest an option for AC restriction for the topic area, which would include new articles (like B but for AC). With that option, effectively TAs would not be able to submit drafts and as others have noted, a lot of the disruption is by TAs. Even if it is unlikely to pass, I think it is better to have the option on the table.. S0091 (talk) 15:09, 21 October 2026 (UTC)
It is, yes; N.B., "South Asian cinema, broadly construed" includes films as well as all associated cast and crew including musical directors, musicians and playback singers primarily working in film, and is specifically inclusive of India, Pakistan, Bangladesh and Sri Lanka. I've only specifically named musical staff because they play a much larger role in the culture surrounding Indian cinema than equivalent people do in Western cinema (name a famous movie musical director in the west except Hans Zimmer) and I want to make sure it's explicitly clear that this topic area categorises those people too.
I suggest changing the wording to "The topic of South Asian cinema...." which aligns with the wording for Indian military history. That's what the final wording on the CT page itself would be, but I can make that clearer in the RfC. I'll add an AC option too just to cover bases. Athanelar (talk) 16:21, 21 October 2026 (UTC)
"We can slap protection on most articles instead of needing to wait for disruption first", I like the idea, but "we" cannot. Protection needs applied by an admin and I am unsure how many would be willing to add to the already overwhelming workload. The disruptors will create disambiguations to avoid protection as well which adds to even more SPI work. --CNMall41 (talk) 15:55, 21 October 2026 (UTC)
Another thing to note is UPE socks game WP:AFC/Redirects, usually as a TA, where they request a redirect, an editor approves/creates it, then the socks turn it into an article, sometimes one with an account. That has significantly subsided as editors caught on to what they were doing but if restrictions pass, I expect it will become a problem again. The tricky part is because the redirect is created by an editor in good standing, some admins will not delete them (i.e. G5 which also applies to pages created in violation of restrictions). S0091 (talk) 16:22, 21 October 2026 (UTC)
Well, the regular AfC blocks editors from submitting drafts in an ECR CTOP when they're not EC, so surely AFC/R also rejects redirect requests relating to an ECR CTOP if the requesting editor isn't EC? If not, surely they should? Athanelar (talk) 16:26, 21 October 2026 (UTC)
Not all reviewers will know or they forget. That happens with drafts as as well. I was not aware of AfC had the ability to block an editor from creating/submitting a draft that violates ECR. When was that was implemented? S0091 (talk) 16:40, 21 October 2026 (UTC)
One of the "deny" reasons is because the editor is trying to submit a draft in an ECR CTOP they don't have permission for. If they again try to resubmit it will be rejected for tendentious resubmission. That's the "blockage" I mean. Poor word choice, I suppose, I didn't mean to imply WP:BLOCK. Athanelar (talk) 18:58, 21 October 2026 (UTC)
Thanks Athanelar. I thought that might be what you meant but also thought had AfC developed the ability to prevent editors from violating ECR, that would be something to perhaps leverage.:) Speaking from my own experience as an AfC reviewer, a topic being ECR is not my top thought when reviewing and I am aware of ECR topics. Things will slip by on occasion. S0091 (talk) 19:32, 21 October 2026 (UTC)
Sure, we can't be 100%. That said, if AFC/R is suddenly inundated by a lot of bad requests because of these new restrictions, it'll probably become easier to detect because reviewers will be on the lookout for it. And, after all, if even 1/10 slip through the cracks and result in an article being created, that's still better than the status quo which is anybody with an autoconfirmed account publishing straight to mainspace and everybody else packing the AfC queue full. A bonus to these restrictions I hadn't considered before is we'll probably be able to quick-deny a whole lot of SA cinema articles at AfC, too. Athanelar (talk) 19:42, 21 October 2026 (UTC)
It happens, but many reviewers focus on specific subject areas, so those most likely to review Indian cinema drafts would hopefully be more aware than others, just like they're more aware of active LTAs on the subject. ChompyTheGogoat[Bleat|Munched] 19:33, 21 October 2026 (UTC)
And sometimes LLM or sock target pages get through too, then we delete them and politely remind the reviewer to keep an eye out for them. Mistakes happen. That's not a reason to avoid applying preventative restrictions.Having a good faith editor being the creator of record on request of a sock sounds like a technicality. The situation should just be noted in the G5 so the reviewing admin understands. ChompyTheGogoat[Bleat|Munched] 19:22, 21 October 2026 (UTC)
Sometimes? I think both of us can attribute our experience at SPI that "sometimes" actually means "bludgeoning a page to death including creation multiple drafts and pages under disambiguation titles like playing hide the coconut as experienced editors move back to draft and wasting countless hours of enjoyment editing and instead spent it playing whack a mole at SPI and AfD discussions." I get your contention, but "difficult to enforce" is still my contention. It will be difficult to enforce. --CNMall41 (talk) 23:38, 21 October 2026 (UTC)
No harder than it is without CTOP restrictions. If we apply this we can immediately draftify anything that does get through from non-EC accounts without stopping to worry about whether they're socks, and if they try to move it back they can be blocked as an enforcement action without waiting on CU. The area needs more patrolling regardless, but I'm not able to wrap my head around the idea that more protections and easier blocks will somehow make things worse than they are now. I'm very confused by it. FWIW "sometimes" was specifically referring to AfC reviewers accidentally letting them pass when the socks try to run things through there. I'm not really sure what's up with the recent pattern of trying that first before a unilateral mainspace creation - maybe they think it's less likely to get deleted? Who knows; I don't understand a lot of what they do. ChompyTheGogoat[Bleat|Munched] 01:39, 22 October 2026 (UTC)
I not suggesting at all this a reason to not apply restrictions. I am simply noting situations I have encountered so others are aware. G5, at least with Twinkle, does have a way to add an explanation, outside of a sock master or applicable restriction.. If it were a redirect I created via AFC/R, I have done both G5 and G7 to cover both but if another editor created it, G7 is not applicable and those are the ones that might be declined by an admin. This is not something I think it a major issue but something to be aware of. S0091 (talk) 19:51, 21 October 2026 (UTC)
Then shouldn't the reviewers be informed? Katzrockso (talk) 06:59, 22 October 2026 (UTC)
I really wish they'd add a way to include an explanation for all CSDs. I frequently have to submit it as custom so I can explain the situation. ChompyTheGogoat[Bleat|Munched] 20:27, 21 October 2026 (UTC)
Well, it's the same as any CTOP. Admins don't need to go through and apply protection to every single cinema article, but they'd be able to way faster and easier if the topic is under ECR/ACR (since at the first sign of trouble on any relevant article an admin can slap the protection on and call it a day) Athanelar (talk) 16:23, 21 October 2026 (UTC)
Sure, they already do that for salted titles, but I'm taking about existing articles that pass notability. It shouldn't be an issue to batch nominate - admins would only need to spend approximately two seconds verifying the articles fall within the subject area. For new pages that pass AfC the request can be applied at move to mainspace. This would be far less work overall than chasing down all the bad edits that will continue to be made against the restriction and having to keep justifying that the disruption is in fact disruptive. The whole proposal would basically amount to nothing because we'd still be applying the same remedies for the same problems. Most of these editors don't care about our rules and will just keep on as long as they're capable of editing the articles. And a lot of them don't leave enough of a trail to track at SPI either. ChompyTheGogoat[Bleat|Munched] 19:18, 21 October 2026 (UTC)
Support having an RFC I think any sort of restriction here would be a welcome change. QuicoleJR (talk|edits) 19:22, 21 October 2026 (UTC)
Support having an RFC long overdue given the disruption we have experienced and appreciate Athanelar for starting the discussion. S0091 (talk) 20:17, 21 October 2026 (UTC)
Agree with others that there should be a formal RfC on this topic. mdm.bla 00:19, 22 October 2026 (UTC)
Could we add to the RfC a specific protocol for handling box office updates? The pushers are getting increasingly desperate on talk pages of articles I've had protected despite our big red notice that no one ever reads. It's unfortunate that the most popular sources are currently not accepted as reliable, which is why I supported the as-yet unsuccessful attempts to re-evaluate all of them without bias. Regardless, to the rest of the world updating the income every five minutes is not high priority. I'd suggest something along the lines of "box office requests must be submitted through a proper edit request with a supporting citation from an acceptable source at WP:ICTFSOURCES or they will be summarily deleted". I guess that might just be seen as updated phrasing of the current notice, and I don't know how we can force anyone to read it. Maybe I'm being too lenient with continuing to try to explain sourcing requirements to people who don't care. ChompyTheGogoat[Bleat|Munched] 04:33, 22 October 2026 (UTC)
I would not combine an RfC question about administrative procedures with an RfC question about content. For content questions, I would suggest adding something at WP:ICTFMOS (not the best shortcut as current advice goes beyond MOS) first. If needed, that provides text an RfC can affirm rather than starting from scratch. CMD (talk) 04:56, 22 October 2026 (UTC)
Aside from the sourcing issue (which I'm not sure what else we can do about, if no one has any input) my concern is mostly about how to handle enforcement, because when they can't push their preferred changes the talk pages immediately get bogged down with requests and subsequent arguments. I guess maybe just revisiting it at the task force would be the best first step. ChompyTheGogoat[Bleat|Munched] 05:11, 22 October 2026 (UTC)
I'm not convinced they'd slow down to read those either. Most of them bulldoze past all the other open threads with the same requests. ChompyTheGogoat[Bleat|Munched] 17:33, 22 October 2026 (UTC)
I'll try it on a current target page and see if it makes any difference.ChompyTheGogoat[Bleat|Munched] 17:43, 22 October 2026 (UTC)
The template does display on mobile for me as long as it's below a section header. Minerva just doesn't like anything above the table of contents. We can certainly make that standard practice if it has any effect. ChompyTheGogoat[Bleat|Munched] 17:59, 22 October 2026 (UTC)
Question on the technical side - we can't protect pages that don't exist yet, but could we utilize a maintenance category that would flag page creations by non-EC editors that are placed in relevant categories? Maybe even a bot that could automatically draftify and drop a corresponding ECR notice. Considering the scale of things I think the more we can automate and reduce the workload on enforcers (especially admins), the better. Minimizing new disruption will also leave good faith editors with more time to work on cleaning up existing content. ChompyTheGogoat[Bleat|Munched] 07:39, 22 October 2026 (UTC)
Nonexistent pages can absolutely be protected, and routinely are; see WP:SALT. We try to avoid it, though, because editors will often just create the page anyway with a slightly different title. Omphalographer (talk) 20:19, 22 October 2026 (UTC)
I mean ones we aren't aware of yet - brand new creations (as well as title gamed versions). This could potentially flag any creation within the relevant categories, under any title. ChompyTheGogoat[Bleat|Munched] 20:23, 22 October 2026 (UTC)
It seems technically possible, assuming WikiProject tags or categories are added to the article a bot could track. I'm not aware of a precedent however. CMD (talk) 22:26, 22 October 2026 (UTC)
I'd be happy to help work out the details with someone more savvy once the RfC clears. We're definitely going to need a structured approach to try to get a handle on things. ChompyTheGogoat[Bleat|Munched] 00:43, 23 October 2026 (UTC)
Support 500/30 requirement with Option B per Jéské Couriano. --ABx11 (she/they) 00:35, 23 October 2026 (UTC)
A nice case study I just stumbled upon for this discussion: WP:ANI#Anirvinya 2009, about a user who for months now has been receiving warnings for unsourced content, largely in the subject of Telugu cinema, with edits like this one and this one, arbitrarily adding "results" like "Blockbuster", "Flop", and "Superhit" to the filmographies of various Telugu actors.
When people in this discussion have said that restrictions in this topic area run the risk of scaring off new editors for whom their passion for South Asian cinema would otherwise be an entry point, it's worth pointing out the unfortunate other side of that. A topic which attracts massive amounts of inexperienced editors is not always a good thing. The user in question is also currently at 563 edits, which means the majority of their disruptive-at-worst and unproductive-at-best contributions would have been avoided if the topic area were under ECR as proposed, considering they have essentially gained EC by editing in this topic area. Granted, they also probably could've been avoided by a more timely report, but the fact that users like this are slipping through the cracks is exactly the reason that myself and others are backing restrictions in this topic area. Athanelar (talk) 01:33, 2 November 2026 (UTC)
Post RfC start discussion
What kind of enforcement actions are available and aren't working? Indian cinema rarely escalates to the arbitration enforcement noticeboard; is this a lack of capacity (awareness of CTOPs, energy to do so, confidence to do so), range hopping TAs, mostly handled by non-CTOP admin actions, etc? Is this mostly getting reported to SPI, ANEW, and RfPP? Is this appearing at AN/ANI, and if so, what are those threads like?
Looking at a few recent protections from the protection log; Dalit Film and Cultural Festival under CT/CASTE, Fighter (2024 film) under IMH, Jailer 2 (1 year ECP, no subtopic), Achhut Kannya (no subtopic). Most people are getting blocked/topic banned for subpar conduct in CASTE or IMH or modern politics (check WP:AELOG for yourself to be sure, but I've read or participated in almost all cases in the last year and definitely in CT/SA). It's hard picking out the cinema related ones from the protection log alone, but it's not as frequent as other CT/SA protection clusters. The main clusters I am aware of are modern politics and political parties, castes, and military history. As for why I'm asking, characterizing how disruption is currently being handled helps a lot in understanding what we are struggling with. I don't go out of AE and AN very often, my main area is copyright after all, and I would imagine that this will also draw people that are unfamiliar with the scope of enforcement entirely. Sennecaster (Chat) 17:37, 27 October 2026 (UTC)
In my anecdotal experience we've had a lot of film-adjacent articles come through AfC in some form or another with UPEs, socks, etc. One which springs to mind is Mission C2000 which was tendentiously created and recreated under lots of different titles by Alakmarsaify socks. Admittedly I've never dived much into cleaning up the topic area myself because what I have seen of it at AfC has really kept me at bay. @ChompyTheGogoat is probably in a better position to call up some specific examples since they were recently doing cleanup. Athanelar (talk) 22:59, 27 October 2026 (UTC)
There's not enough enforcement period. Most of it goes through SPI or ANI when someone (usually me) actually bothers. The current CT/SA restrictions don't apply to this subject area, and most editors just drop whatever insertion they feel like with little to no sourcing and no communication, primarily from TAs or low count named SPAs.Anyone who thinks we shouldn't need additional restrictions should spend some time actually working cleanup in this subject area to see just how extensive the problem is and why current remedies aren't sufficient. I just ran an editor to ANI with 2500 edits over multiple years, compromised almost entirely of unsourced or poorly source additions to this subject area. They had 18 warnings (and an additional dozen miscellaneous TP messages) that they ignored. All of those other editors were content to drop drive-by templates and move on without actually addressing the problem - and it's far from the only case. Even under ECR we'd have to work through grandfathered editors like this, but "difficult to enforce" is not a viable excuse for not implementing restrictions - otherwise why have restrictions at all? At least this would give enforcement some teeth. Widespread ECP and a low bar for blocks would have a huge impact. The problem has been allowed to build up for years and it will not be handled without additional restrictions. Milder sanctions might have been sufficient if it had been addressed sooner, but that ship has sailed. Whatever is decided, you can deal with it without me. Or don't. Keep letting it fester. I'm washing my hands of it regardless. I'm done being the only person who cares. ChompyTheGogoat[Bleat|Munched] 23:46, 27 October 2026 (UTC)
ChompyTheGogoat, you sound dangerously close to total burnout. Maybe you're already there. Someone else will pick up that cleanup work later. Anecdotally, I've been doing copyright nonstop for 3 1/2 year straight, and then have done arbitration enforcement for 2 years straight. I am burnt out. I don't have capacity to report or handle everything even in copyright. That's okay though. I completely understand your frustrated, I have had extremely similar moments, but I am not here to be your "enemy" or to say that there's no need for action here. I'm trying to figure out what specifically needs to be targeted, whether or not any proposal here gains consensus or not. Okay, we need to get the AFC people more involved in identifying socking/UPE and escalating. That is doable. Okay, maybe we need to get RCPers using more semi-auto tools that make reporting a lot easier. EditCheck should hopefully be helping, but if it's not we need to know and the people that do this are not omnipresent and not high in number. There's a lot of people here that are interested in stopping disruption and frequently work arb enforcement, so you're speaking to people that do not have experience in this specific topic. I don't do AFC. I don't do SPI, and a lot of my wiki-friends are SPI but only think of it from the UPE and socking perspective. None of us are saying that there isn't an issue. The people that are familiar here are administratively conflicted out in a lot of ways, or don't want to open themselves up to the very real risk of harassment. We are asking in good faith because we want to know what we can do in the meantime. We're aware of the issues now, we can do something about it.WP:CT/SA covers all of South Asia, broadly construed. It covers Indian cinema. What you're experiencing is the very real reality in that CTOP enforcement is incredibly stretched thin and simply do not patrol that topic enough. I don't appreciate All of those other editors were content to drop drive-by templates and move on without actually addressing the problem - and it's far from the only case.'s lack of good faith, so I really do ask that you step back before you say anything you regret. I get the burnout. I really do. I have spent a lot of time arguing with people that they can't add copyright violations back. But it doesn't give you the right to take that frustration out on others, and not on people that aren't familiar with the issue because that isn't their expertise or interest. It's the reality of wiki work that we have different things, and that we get burnt out and frustrated, but we have to emphasize and understand each other despite that. Sennecaster (Chat) 03:57, 28 October 2026 (UTC)
Horse, barn door. I tried giving myself a break by working on another topic area that I'm passionate about and got accused of LLM use after spending hours hand writing an entire article, so when I say I'm done, I'm done. It really doesn't matter what other editors think of me at this point.Someone else will pick up that cleanup work later. If that was true we wouldn't be in this situation in the first place. Editors have spent years ignoring the problem, as Jeske said below. And when I said All of those other editors were content to drop drive-by templates and move on without actually addressing the problemthat is literally what happened. Eighteen editors dropped templates and ran, without looking at the pile that had already gone unanswered or bothering to file at any noticeboards. For years. That is a fact, not hyperbole. It is not the only such case that I've filed. So yeah, when the people who have no experience in this subject area still think they're qualified to drop a !vote claiming we don't need to make any substantial changes, I take issue with it (and yes, some are saying that). They're free to abstain if they don't have the relevant experience to give an informed opinion. I also have no prior experience or interest in the topic. I stumbled across it and saw a problem that no one else was stepping up to deal with, so I did. Or at least tried. And it's no wonder no one wants to do it. It's incredibly thankless work - it's one thing getting harassed by the POV pushers that are causing the problem, and quite another when other experienced editors patrolling noticeboards are more worried about the formatting of my reports than the actual problem I'm reporting. You want to know why people are hesitant to report? That's why. Too much infighting and pedantry; not enough concern for the actual damage being done to the project. I'm highly disappointed in this community overall, and with AI hoards at the walls - now including fully autonomous agents - I don't think you'll be able to hold out for long while competent editors are being chased off. Even veteran editors of 20+ years are giving up in frustration, and I can understand why. Guess I waited too long to sign up. ChompyTheGogoat[Bleat|Munched] 05:04, 28 October 2026 (UTC)
I understand you're frustrated, but it's very likely that some of those 18 editors have their own overwhelming backlogs of work. Like with me for example, I almost definitely have flagged some Indian cinema articles for AI (if there is AI) instead of dropping everything to go fix it, because I am currently about 200 tabs deep in other unfinished AI cleanup and I do not have the time. There are a finite amount of hours in the day.
And if you mean userpage warnings, what more exactly are people supposed to do? Stand outside their window with a boombox? You can't force someone to change their behavior. Gnomingstuff (talk) 02:58, 29 October 2026 (UTC)
I think the point Chompy's making is that that's exactly why we need restrictions in this topic area. People obviously don't have the time or interest to dedicate to cleaning up this topic area, reporting editors and pages for arbitration remedies, etc. It's not that any of those 18 editors should've dropped what they were doing and solved the problem themselves, it's just that if we don't have the interested and able editor-power to do it, then we need another solution. Athanelar (talk) 03:10, 29 October 2026 (UTC)
Yes, the warnings. That's why we have noticeboards. Sanctions are a thing. Most of the ones I've taken the time to report do get blocked, and there would be much less disruption if others had bothered to do so sooner. The time it takes to file said reports is far less than the cleanup that's now needed for all those thousands of edits. I refuse to believe that all 18 editors (and all of the others who dropped additional messages there, or other warnings on other editors) were so very busy in that exact moment that they couldn't possibly take the time to compile a few diffs. Other types of disruption in other subject areas get addressed far more quickly.So, if people aren't willing to address the huge number of problematic editors on a case by case basis, we instead need sweeping restrictions that will stop the vast majority of them, even if a few good faith also get caught up in the net. Page protections are one of the best tools we have for preventing ongoing distribution with minimal effort, and the sooner they can be applied in subject areas that are rife with these issues the less needs to be fixed. ChompyTheGogoat[Bleat|Munched] 03:37, 29 October 2026 (UTC)
Other types of disruption in other subject areas get addressed far more quickly.
This feels like the thing (and I've probably done it too) where a person is so focused on putting out a metaphorical fire in their room that they don't notice that the rest of the house is also on fire. Every part of Wikipedia is falling apart. I'm familiar with the amount of squabbling that goes on with film articles (since I have to slog through the hundreds of drive-by talk page comments per month that just say "Box office"), and even that is nothing compared to the dozens of backlogs of hundreds of thousands of articles needing maintenance.
As far as sanctions go, it's emotionally exhausting enough to even create one noticeboard report, and I don't blame anyone who just doesn't have it in them. Gnomingstuff (talk) 12:50, 29 October 2026 (UTC)
I have edited other topics. I'm aware that there are widespread issues, but this subject area as a whole is more problematic than most, which might have some articles and editors that are problematic but are more monitored overall, especially on the most popular articles. I can guarantee that any Indian film article I open will have issues - usually extensive ones - and if (or rather, when) I find an editor in the history who's part of the problem it's virtually guaranteed nothing was ever done about it, regardless of their edit count.As a reminder I've already been chased off the project, and not purely over this topic, so yeah, I know there are problems. Lots of them. This probably won't even matter in the long run. ChompyTheGogoat[Bleat|Munched] 18:38, 29 October 2026 (UTC)
Yep - even with ECR it'll take some dedicated editors with no vested interest who are willing to roll up their sleeves for the overall integrity of the project to really get a handle on things. I think once the current swarms who feel like they have free rein to insert whatever they feel like realize that won't fly anymore things will simmer down and be easier to maintain - but that works needs to happen first or it will just continue to snowball. Good luck. ChompyTheGogoat[Bleat|Munched] 05:09, 28 October 2026 (UTC)
Hence my linking catch-22 above. I think it's safe to say the issues are threefold:
Nobody with experience is familiar enough with Indian culture and how it interacts with cinema, especially where caste is involved. This makes them incompetent, through barely any fault of their own, to actually edit in and administer the topic area. Those who are knowledgeable about the subject matter are vastly outnumbered and overwhelmed.
Few/none of the new users entering the area are willing or able to treat Wikipedia as anything more than an extension of Indian media, and almost all of them either have a conflict of interest or are true believers.
The topic area is in an intractible ethnopolitical hellhole CTOP and tends to be connected to two potent third rails in that hellhole (caste and politics). This makes experienced users even more reluctant to touch the topic area and sets up new users for failure (CTs are the worst places to learn to edit; the intractible ethnopolitical hellholes especially so).
The ways to fix this would require, at a minimum, ECR in the immediate term. This is a very similar blend to the situation that caused WP:ARBPIA3 to happen. Once that is set up, and the firehose of edits to the area is slowed to a more manageable amount, there needs to be a community-wide effort to assess the articles for neutrality and COI concerns, with anything failing the test being sent to AfD if they cannot be improved. Anyone trying to disrupt this with nationalist, LLM, or COI bullshit needs to be at minimum topic-banned from the cinema topic area. Anyone evading these bans needs to be indef'd and restricted to one account, if that is possible as a discretionary sanction. (For anyone thinking about what precedent I'm looking at, SCI and MM are moreso what I'm looking at than any of the 17 PIA cases.) If this disruption continues despite everything, haul the mess to ArbCom, with an eye primarily towards amending CT/SA to make ECR de jure in the topic area indefinitely. —Jéské Courianov^_^vThrillerNight! 06:52, 28 October 2026 (UTC)
@Jéské Couriano; I appreciate the clarification. Unfortunately, my experience over at CCI tells me that community cleanup efforts are vastly outpaced by the pace of crap added or the size of things to review without serious political and social capital. Doug Coldwell's whole pile of crap GAs isn't even fully cleaned up yet. A lot of what you're saying about CT restrictions, but we have a critical lack of capacity that is making everything worse. Treating admins poorly will not help the issue (I'm not accusing anyone, but it is a fear expressed to me). I just don't know what we can do that doesn't amount to "bully administrators into doing things they actively resent doing", since we have always been hesitant to elect admins focused heavily in "experienced user conduct" (a phrase from my own RFA).
As for cleanup: Chunking down Indian cinema to specific subtopics (ie. telugu films, marathi TV) with aggressive presumptive removals would lead to less reviewer/community burnout. It could also be turned into an editathon or drive. This level that's being described means that something much more drastic than a methodical combing and AFD can resolve without exhausting significant portions of the community. Despite my criticisms and counter-suggestions, there's a lot of good ideas here, and I think I know some things that I can angle people with more capacity than myself to get started on regardless of the outcome here. I myself am not experienced enough with background conflicts to admin fully in CT/SA, like you've described. I can handle blatant POV pushing and caste warring, but I've had to call in help from multiple sources both wiki editors and not to even begin on trickier reports. It's an issue and the more that you know here, the more you're likely to end up WP:INVOLVED. Sennecaster (Chat) 22:55, 28 October 2026 (UTC)
I would imagine the scope of the issue would more or less mandate that the subtopic be further broken up into further subtopics in order to actually deal with it. "Indian cinema" is the sort of overly-large topic area that ArbCom themselves comments about at WP:ARBIMH#Breadth of topic bans, and experiences with one subset of it don't necessarily translate well to other subsets (h/t Athanelar). The editathon/drive idea would certainly help as well (to get out in front of "how about AFI?", that to me seems more of a mixed bag, but it'd be worth a try for some of the lesser-known articles in the area that haven't drawn mercs or zealots), but this would fall into the same issue of anyone not "read in" being driven off by mercenaries and "true fans". Hence I think there would need to be an ECR in order for us to even entertain any such cleanup. The other alternative is going scorched-earth on users in the topic area to get rid of the UPEs, and that's counter-productive and would be a waste of admin time even if it weren't. —Jéské Courianov^_^vThrillerNight! 00:39, 29 October 2026 (UTC)
I was thinking that setting up a tracker within the task force page could be helpful with cleanup - after restrictions are in place, because people will absolutely get driven off if they attempt it now (hi). Having a system to mark what's been reviewed, tagged, nominated for deletion, etc would help give a visual representation of progress and motivate people because they could see that even small contributions can move the needle. Maybe a bot could move pages through in batches to address the backlog in a format that feels manageable. ChompyTheGogoat[Bleat|Munched] 01:02, 29 October 2026 (UTC)
That would help, but the overall scope is the bugbear here. Going through it one subtopic at a time is still going to be the best way to handle this. This is an issue that has been festering for years; a quick fix at this point is unrealistic. —Jéské Courianov^_^vThrillerNight! 01:44, 29 October 2026 (UTC)
Oh, I know. That's just one idea that could potentially help with working through content. Restrictions and above all willing editors are necessary if any progress is going to be made at all. ChompyTheGogoat[Bleat|Munched] 02:59, 29 October 2026 (UTC)
Alright, any option here means that RfPP is about to be flooded because change in ECR or adding an autoconfirmed restriction a la pageants means RfPP flood. What needs to happen is we need to automate protection logging. Indian cinema would be a community general sanction, therefore meaning we create its own subpage like Wikipedia:General sanctions/Kurds and Kurdistan and then administrators manually log every single protection. One major resistance to expanding CT/SA and CT/PIA originally was because of this incredibly tedious process to log every single thing on a page that has no headers, and that was for the CT log which is centralized. So there's 3 options here: 1) do nothing, to hell with it 2) create analogous protection log to the CTOP bot logging 3) petition ArbCom through ARCA to include this modification to CT/SA. My real dream would be to consolidate everything, CCTOP and CTOP into one log, because 3/4 of CT/AA logs are actually for GS/AA but no one wants to go edit that unwieldy page, and that's just one example. The various GS over South Asia were consolidated for the same reason. But frankly immediatley implementing whatever RFC outcome besides option A is going to be a burden without actual thought to how this will get laid out, and I want to think about this now. Sennecaster (Chat) 17:02, 5 November 2026 (UTC)
Is there a way to automate logging for Arbitration-origin contentious topics? If so, we could easily adapt it to log this ECR (and the threeotherECRs that supplement arbitral CTOPs). That said, I'm not familiar with botting here, so I suspect this would need a trip to the BAG to get the details sorted (either to modify an existing bot or spin up a new one). —Jéské Courianov^_^vThrillerNight! 18:07, 5 November 2026 (UTC)
@Jéské Couriano it's already logged automatically for all arbcom CTOPs. My concern here is that any kind of protection scheme would be done under the community process like GS/AA, so therefore the log is separate from the arbcom process. I don't know if there's appetite for combining the protection logs for community GS protections and arb GS protections, but I do think at the very least combining the logs for the various community GS into one log and looking at what the arb protection log does would be most efficient. We could co-opt much of the code from ArbClerkBot. Though that would likely be a separate RFC since it's a massive infrastructure change. Sennecaster (Chat) 04:53, 7 November 2026 (UTC)
Surely we could have some sort of semi-automated script (at least semi-manual, though fully automated is good, too)? Something on Twinkle, maybe? WhatamIdoing (talk) 20:13, 9 November 2026 (UTC)
I think we need some sort of speedy-deletion for pre-release films. Creating a wikipedia article has become a standard part of the publicity machine, and if we're going to give every film two or three weeks' grace while we go through AfD, it just means people will time their article-creation to use their 20-day free advertising-space as strategically as they can. Elemimele (talk) 11:52, 13 November 2026 (UTC)
Articles which are unambiguously promotional can already be deleted under WP:G11 and I don't think you're likely to attract support for a measure which assumes all prerelease film articles are inherently promotional. Athanelar (talk) 11:54, 13 November 2026 (UTC)
Nobody before me mentioned WP:1RR as an option for curbing existing edits, either in addition to or instead of ECR. Compare WP:GS/CRYPTO without ECR and WP:CT/PIA with. –LaundryPizza03 (dc̄) 20:13, 15 November 2026 (UTC)
Who's going to enforce it? There's not enough monitoring as it is. That's the whole problem. The beauty of ECP is that it only has to be enacted once and keeps right on working without active intervention. I'm not sure how people are simultaneously arguing that good faith editors will never be able to reach EC (largely because so many in this subject area are SPAs with zero interest in anything else) but bad faith will apparently be able to continue making endless EC socks? Bizarre logic. ChompyTheGogoat[Bleat|Munched] 06:59, 16 November 2026 (UTC)
When discussion has ended, remove this tag and it will be removed from the lists. If this page is on additional lists, they will be noted below.
Should the talk header (shown in §Example below) appear atop the talk page of any non-redirect article that contains one or more discussions?
A – Yes, and I have no opinion on how this should be implemented.
B – Yes, but only if this is implemented via a bot that automatically adds the {{Talk header}} template atop eligible pages. (Just like other bot edits, this can be turned off on specific pages.)
C – Yes, but this should preferably be implemented via a MediaWiki feature without using a bot. If a native feature proves technically infeasible, this should still get done through other means, like a bot.
D – Yes, but only if we are able to implement this via a MediaWiki feature without using a bot. If this proves technically infeasible, then I oppose this proposal.
Blank message so reply tool works 1brianm7 (talk) 00:50, 2 November 2026 (UTC)
Option E. The header contributes to banner blindness for little benefit, option D if absolutely necessary. 1brianm7 (talk) 00:50, 2 November 2026 (UTC)
Option E. Like what many have said, I think this will only worsen the issue of banner blindness. I will say that this probably can be implemented with MediaWiki:Talkpageheader. Axolitl(talk|contribs) 01:12, 2 November 2026 (UTC)
E > D > B. I’m not convinced we need to add it to every talk out there. I might support making part of the default. Dw31415 (talk) 03:33, 2 November 2026 (UTC)
Option E - banner blindness is real. Many less-frequented pages do not need this bloat. Ealdgyth (talk) 13:43, 2 November 2026 (UTC)
Option E per Ealdgyth. We need to take steps to decrease the number of talk page banners; this proposal would be a massive step in the wrong direction. Best, HouseBlaster (talk • edits • he/they) 19:27, 2 November 2026 (UTC)
Option E. No objection to the header, but no need for it to be imposed everywhere. Cabayi (talk) 09:20, 3 November 2026 (UTC)
Option E Thanks but absolute no to automatic banners which generate clutter and arguments. If new users need hints on what to do, that should be shown only to them with an opt-out. Johnuniq (talk) 01:27, 4 November 2026 (UTC)
Option E I gave something of an explanation below, although I seldom vote on community matters like these. I find myself agreeing with HouseBlaster, Ealdgyth, and Graham87. DannyRogers800 (talk) 21:14, 7 November 2026 (UTC)
Alternate proposal: Add {{Talk header}} to pages that receive X amount of pageviews in the Mainspace or Y amount of pageviews in the Talk namespace, where X > Y (obviously), whichever is lower. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 00:27, 13 November 2026 (UTC)
Option B. I think it's time we make the process of adding the template automated. If it causes banner blindness, that should be solved by editing the template itself, since it appears on every high-traffic page along with many others. I'd argue it's especially necessary on these small, low-traffic pages because often the only discussions are years old and it would be less clear for a newcomer to understand what they can do. FaviFake (talk) 01:09, 13 November 2026 (UTC)
Option E. I agree with HouseBlaster. --Enos733 (talk) 01:38, 13 November 2026 (UTC)
Option B partly per FaviFake. Personally, I'm not universally convinced by this banner blindness theory. Yes editors become banner blind quite quickly, most including myself wouldn't notice if one of the CTOPs were changed with different restrictions or otherwise, but I don't believe we can attribute this psychology for readers or newer editors that are paying more attention; those we are trying to attract towards becoming editors. For reference my 6th edit on WP with this account was because of an AfD banner on an article page when I was looking for more information on a subject. I know that doesn't sound like the same context as a generic talk page header, but it does provide useful links for newcomers wanting to learn, specifrically for more obscure pages that have few active editors and even less complete content. This to me is similar to how an AfD notice can draw in new editors like it did me. I'm also thinking of low-traffic pages here, some women footballers pages and the like. CNCin solidarity (talk) 01:43, 13 November 2026 (UTC)
Option E and indeed typically the header should be discouraged. Adumbrativus (talk) 07:21, 15 November 2026 (UTC)
Discussion (talk header)
Perhaps the original poster could add a background section, where they can discuss the motivation behind each of the proposed options? What problem is being addressed? isaacl (talk) 00:07, 2 November 2026 (UTC)
Voting E feels slightly pointless as this sort of template spreads mimetically regardless of its actual value, but at the same time I see no reason to speed that process along with a bot. CMD (talk) 00:55, 3 November 2026 (UTC)
Should we discourage people from mass-adding it (e.g., to talk pages with no comments and no archives)? For example, this recent edit, which replaced an archive box with the talk header (which includes archive search+links), by DannyRogers800 seems desirable, but if there were no existing Talk: page, or if the only content were WikiProject banners, then maybe we should encourage editors to default against, and maybe only add the header if the article is likely to get a lot of discussion. (I think that's typical, anyway.) WhatamIdoing (talk) 17:10, 7 November 2026 (UTC)
I'll admit, I've added hundreds of headers to talk pages about Beatles songs... many hundreds. Before reading this, I was sure that certain talk pages don't have them because of neglect or dereliction, and my reasoning ran much like Ilov3gam3z's when they proposed to stamp headers on pages by default. Now that my eyes have met this discussion, I think I was blind to a modestly serious issue, just as I was blind to the banners I was mass-adding... hundreds of times have I seen them, and I can only recall a fraction of the words that are written there. I don't think I'm knowledgeable enough to cast a vote, but I will express some worry that clutter and hodgepodgery have spoiled our minds a fair bit... here on Wikipedia, but to a far greater measure on social media, billboards, cities, and pretty much everywhere. There's no way people read any of this stuff..... plain text is enough. I'll just suggest that, and it's only a suggestion, we remove the "add sources" strip from headers and automatically make all Wikiproject banners collapsed, only to be opened if we press "show". And I'll stop adding headers to pages myself. DannyRogers800 (talk) 18:04, 7 November 2026 (UTC)
Danny, I think this is kind of a "personal preference" thing, rather than a "need to be knowledgeable" thing. If you think that they should be on all pages, or most of them, then I very strongly encourage you to !vote that way. Having it look like a unanimous decision while anyone is harboring doubts is a bad thing. Please don't stop adding headers to any page where you believe it might be helpful. IMO we don't need them on all pages, but we probably do benefit from having them on some pages. (And you are not required to agree with my opinion; it's perfectly fine if you think that we actually do need them on all Talk: pages.)
I think you've got some good ideas here. Clutter is a problem (but so is not being able to find what you need). A redesign to move it towards a more "plain text" appearance might be possible and might help with that.
I think that auto-collapsing WikiProject banners is technically feasible. Perhaps a baby step towards that (e.g., always collapsed except for newcomers, or always collapsed unless it's the only thing on the page) might be worth trying. I wonder if we could merge the talk page header with the WikiProject banner shell, and have nearly all the content in both collapsed?
More ideas like these would be welcome. WhatamIdoing (talk) 21:01, 7 November 2026 (UTC)
I merely never questioned the header until today; I always assumed it must be slapped onto a talk page much like labels are stuck on boxes of cereal. Well, I'm glad you listened to my little screed, and thanks to your advice, I've decided to vote. DannyRogers800 (talk) 21:13, 7 November 2026 (UTC)
Consistency in placement of infobox titles
In Template:Infobox#Content_parameters, it lists two ways to put a title on an infobox; inside the infobox's border or on top of the infobox. Therefore different infoboxes alternate between the two: Template:Infobox software and Template:Infobox organization for example. There are also color difference, where some titles within infoboxes have no background color while some such as Template:Infobox_OS do. Currently there is no guidance on which of these is optimal.
Furthermore, this is changed often without consensus such as here in Template:Infobox company. It has resulted in some articles looking cluttered, especially when the logo of a company is in black text like Samsung Electronics.
This proposal aims to set a consistent placement and color of titles to ensure uniformity across the encyclopedia and to improve clarity by reducing visual clutter. There should ideally be one way to place the title with room for color changes if inside is decided to be optimal. Update6 (talk) 04:32, 2 November 2026 (UTC)
I don't see any point having a title for an infobox that is identical to the title of the article. Why does Wikipedia do that? I do see that Template:Infobox says it is "not recommended" to have neither an "above" nor a "title", but there is no recommendation against using both (which would seem like a better thing to recommend against).
There is at least one infobox that doesn't automatically produce a title, {{Infobox ship}}. See Titanic for an example without a title and Cutty Sark for one with a title. It looks like there are only 3590 of 43,000 ship infoboxes with a title.
While searching for any discussion about why we recommend against not having a redundant title for an infobox (which I haven't yet found), I came across Wikipedia_talk:Manual_of_Style/Archive_115#Infobox_headings which also is about the inconsistency in above/titles for infoboxes (and also has an editor pointing out there neither is typically very useful). Plantdrew (talk) 18:40, 4 November 2026 (UTC)
When the article contains multiple infoboxes, such as when the article covers multiple related subjects, a title can make it clear which element the infobox relates to (Marylebone station is a poor example). Infoboxes for multiple pieces of legislation related to a topic also come to mind, as at Deeside Railway. However these are an argument only for not removing a title parameter completely not against discouraging in cases where there is a 1:1 correspondence between article topic and infobox topic. Thryduulf (talk) 20:47, 4 November 2026 (UTC)
Another place titles are useful is when the infoxbox title is different to the page title and/or references visual branding which reinforces people have arrived at the right article, e.g. Newcastle Airport Metro station, Paris Metro line 3. In road articles they seem to be used as alt-text for images which is particularly useful when the image doesn't match the full name of the road (compare e.g. A303 road and Kentucky Route 7) and airliners seem to use a similar setup (e.g. Boeing 787, Airbus A330). I do though think that there could be value in standardising whether titles should be inside or outside the box, above or below a lead image. Thryduulf (talk) 20:53, 9 November 2026 (UTC)
I did say "I don't see any point having a title for an infobox that is identical to the title of the article". In the case of multiple infoboxes as at Deeside Railway, I think it better to have the infobox title inside the box rather than above it. Plantdrew (talk) 16:37, 12 November 2026 (UTC)
Cleanup drive for MOS:LANG
I found out about MOS:LANG not too long ago, and it seems to be one of the least implemented parts of the MOS. I am thinking that regular cleanup drives could be useful. Apart from articles already tagged with {{Cleanup lang}}, obvious targets would be articles in subcategories of Category:Words and phrases by language, Category:Cuisine by country and similar categories.
I also recently learned about {{title language}}, and the ability to use DISPLAYTITLE to tag only part of a title with {{lang}} (which {{title language}} doesn't allow). That should be part of this cleanup drive as well; I think it is still common that non-English titles are either not italicised, or italicised only with {{italic title}}.
I'm not aware of any such drive at the moment. I hope there is interest in one, or at least that some more editors will take on this task. There is so much untagged non-English text! Helpful Cat🐈 14:06, 3 November 2026 (UTC)
That MOS page only gives examples using templates. There is another option, which is to use the HTML tags (e.g., <span lang="la" dir="ltr">TEXT HERE</span> for Latin). VisualEditor uses this approach. If you wanted to convert those to the template, then this search link will help you find them. (I've no idea whether this is an important thing to do, and for all I know, there's already a bot doing it.) WhatamIdoing (talk) 16:58, 7 November 2026 (UTC)
Thanks! I didn't know VisualEditor had a built-in way to tag non-English text. I haven't come across span lang in any articles I'm aware of, so I don't think it's commonly used either. I don't think we need to change one method to another as long as both work; the issue is that the majority of non-English text is not tagged at all. Helpful Cat🐈 01:59, 8 November 2026 (UTC)
One outcome of Wikipedia:Typo Team/moss is to tag words with their language. What may look like a spelling mistake, may just be a non-English word. The prevalence of unmarked foreign words is so high, that it is not really a cleanup yet, it is more of an implementation. Perhaps some tools could be built to highlight non-English words and suggest a language, and then allow marking up with the template. We should not be using span sections if the template can work as it is too technical for most editors. Graeme Bartlett (talk) 07:37, 8 November 2026 (UTC)
Perhaps some tools could be built to highlight non-English words and suggest a language, and then allow marking up with the templateI would fully support this. The amount of untagged foreign text is so high that tackling it is a truly gargantuan task. I've been going through a few categories with AWB or wAwB, but of course I've barely made a dent. A tool would be extremely useful to easily spot non-English words apart from the title (I have been using rules that identify and tag instances of the title in the body text), and to suggest the correct language code (saving the effort of manually identifying languages and looking them up in List of ISO 639 language codes each time). Helpful Cat🐈 07:56, 8 November 2026 (UTC)
It should be fairly easy to search for non-Latin scripts and to at least filter the list of language codes to the ones that are relevant for that writing system (e.g., if you see 위 somewhere, you know it's Korean, so the script should only suggest ko as the language code). WhatamIdoing (talk) 20:46, 9 November 2026 (UTC)
(By "fairly easy", I mean that someone with way more tech skills than me should be able to write a user script that could do this.) WhatamIdoing (talk) 20:47, 9 November 2026 (UTC)
Yes, and ideally the tool would be able to identify languages in Latin scripts too (machine translation tools can do it!) Helpful Cat🐈 12:43, 11 November 2026 (UTC)
That's true, at least if they get more than a few words. WhatamIdoing (talk) 22:25, 16 November 2026 (UTC)
I do have a userscript that does this and automaps citation template parameters. Been doing it for a while now.
You can use regular expression /\p{Script=Hani}/u to match Han characters, and Hira, Kana, Hang to match hiragana, katakana and hangul respectively. For differentiating simplified and traditional Chinese, you will need OpenCC database from GitHub. This is not 100% bulletproof since foreign branding exists, but it's very close.
For non-CJK languages I trained a mini in-browser classifier with Common Voice sentences. There’s existing solutions like Tongue that also runs offline.
In my userstyle I have specific styling for anything that has a lang attribute so if I see a word without the style I know it lacks labeling. Northern Moonlight 07:41, 17 November 2026 (UTC)
What features are you specifically looking for? Sounds like something I can help. Northern Moonlight 07:50, 17 November 2026 (UTC)
Wow, thank you! A dream tool would have these features:
Automatically recognise non-English text
Automatically identify the language, suggest a language code, and tag the non-English text with {{lang}}
Ability to run as a script in wAwB, to process large numbers of articles
Bonus: automatically setting |cat=no inside {{lang}} within wikilinks and refs, as discussed here; also a toggle to set |italic=no if words shouldn't be italicised
I have no idea if any of that is possible. Thank you for any time you spend on this! Helpful Cat🐈 13:06, 17 November 2026 (UTC)
Those seem possible except wAwB which does not expose an AST. I will post an update here before the thread gets archived. Northern Moonlight 15:35, 17 November 2026 (UTC)
Amazing, thank you so much! Helpful Cat🐈 15:37, 17 November 2026 (UTC)
The upsides to the span in the visual editor are:
It works like any other sort of text formatting: Select the text, go to the "A" menu, and choose "Language". Type in the code for the language and click the button to apply the formatting.
The resulting text can be edited like any other formatted text. (This is not true for templates; the contents of a template must be edited in a specialized template dialog.)
The only downside IMO is that experienced editors aren't accustomed to seeing it in wikitext. WhatamIdoing (talk) 20:35, 9 November 2026 (UTC)
A generic infobox for generic subjects
I just saw Share taxi. I'm grateful to the list of alternate names, because I was looking for one of them. But there are so many that it's a violation of MOS:LEADCLUTTER. Some infoboxes support a |synonym= parameter, and I thought I'd fix it by moving this information to the infobox. However, Template:Infobox doesn't, and I don't know what template to use. Taxi doesn't have an infobox, nor does Bus or Public transport. Do we need a fairly generic {{infobox service}}?
Similarly, we have {{Infobox restaurant}}, but nothing for Restaurant, {{Infobox company}}, but nothing we can use on Company, and so forth. While such articles do not all need infoboxes, when there is a use for them, it would be nice if we had an option available. WhatamIdoing (talk) 16:43, 7 November 2026 (UTC)
Alternatives = Private transportation, trains, air travel, ferries
I'll leave a note at WT:TRAINS and see if anyone has advice. WhatamIdoing (talk) 22:01, 7 November 2026 (UTC)
Here from WP:TRAINS – I really don't see what parameters you could use for such generic topics. Of course, maybe one or two may come to mind, but would that be considered too little to make a useful infobox? For example, what would you consider a predecessor to regional rail or rapid transit. I guess origin would apply here, for example rapid transit would be the London Underground, as it is the first system to open in 1863. Or maybe these just aren't good examples, but I don't think this type of template would make use for train-related articles, in my opinion. Fortek67 (talk) 22:35, 7 November 2026 (UTC)
Mostly what I want is the non-subject-specific bits for an infobox, e.g., for Regional rail:
Other names = Rail rapid transit, metro, subway, underground
Testing against Nail salon, Massage it’s hard to see the value for those. Dw31415 (talk) 17:03, 7 November 2026 (UTC)
Moving lead clutter to the infobox is always likely to be an absolutely terrible idea. We have MOS:LEADCLUTTER - do we need MOS:INFOBOXCLUTTER? If the lead really is too full, set up a short section just below it. Johnbod (talk) 23:49, 7 November 2026 (UTC)
Given a decision among editors that the article should contain a larger number of synonyms, the options I can think of are:
Put it in the first sentence/lead.
Put it in the infobox.
Put it in a section called something like ==Names==.
I think that all of these could be valid under certain circumstances, but I think the second option would be better for Share taxi. Which would you choose? WhatamIdoing (talk) 20:51, 9 November 2026 (UTC)
As I just said, if 1 won't do, then 3. 2 is rightly likely to not survive long anyway. Share taxi must list about 40 different terms in the text - why Nigeria and Israel need to be in the lead and the rest not is a mystery - not a "decision among editors" in any meaningful way. And "or a minibus in European countries and Turkey,..." is just WRONG - minibus means a type of vehicle and not a type of transport service, and Turkey (where these are very common) uses other terms, especially Dolmuş, as of course do France, Italy etc, where they have them. Really a rather long list article is justified - few things have more varied terminology. Johnbod (talk) 03:28, 11 November 2026 (UTC)
{{Infobox medical condition}} has a section for synonyms, and the contents "survive" quite well. Why do you think it would be different for other articles? WhatamIdoing (talk) 03:56, 11 November 2026 (UTC)
Because not every country in the world has their own name for conditions (presumably they strongly group by language), as is pretty much the case here. I doubt many of the medical boxes would stand up to much scrutiny frankly. I see NONE of Influenza , common cold, tuberculosis, measles, and chickenpox actually have synonyms in their infoboxes - probably very wise. I suspect where it is used it is only for English-language synonyms, so very different from here. Johnbod (talk) 02:51, 12 November 2026 (UTC)
The English-language names for Share taxi (according to the first sentence of that article) are:
share taxi,
shared taxi,
taxibus,
jitney, and
dollar van.
Wikidata adds "routed taxi" to the list. That's IMO enough to justify a |synonyms= entry. WhatamIdoing (talk) 03:04, 12 November 2026 (UTC)
Also, all of those articles have synonyms in the infoboxes:
If you tried a ⌘F search for the word "synonym", then you'd have missed it. That's the name of the parameter, but not the label shown to readers. WhatamIdoing (talk) 03:08, 12 November 2026 (UTC)
Ok, no, I just looked at the boxes, and missed those, all above the pictures. What does that tell you about their visibility, and therefore utility? I think the long ones are far too long, and why do we have the French for flu - does anyone use that in English? The more names there are, the more they should not clutter up the infobox imo; the medical ones are already long reads - far too long for the vast majority of readers, I'd imagine. Johnbod (talk) 04:05, 12 November 2026 (UTC)
"Grippe" was once commonly used in English. I've certainly seen it used often in older books and such. Donald Albury 19:31, 12 November 2026 (UTC)
Me, too. I think that grippe was an ordinary word until the Spanish flu brought us the word flu. It had probably fallen out of use by the WWII range. WhatamIdoing (talk) 21:20, 12 November 2026 (UTC)
They're not visible, so we should get rid of them; also, they're taking up too much space, so we should get rid of them.
What I think takes up too much space is a ==Names== section in the body of the article. WhatamIdoing (talk) 21:17, 12 November 2026 (UTC)
Why? We have a policy mandating keeping infoboxes as short as possible, partly because otherwise readers just don't work through them. Not for text. I thought the necessity of keeping boxes terse was very widely accepted, except by manic box-fillers, but apparently not. If grippe was once a common term in English, it certainly isn't now. Why would it belong in an infobox? Johnbod (talk) 14:36, 13 November 2026 (UTC)
Grippe is a redirect to Influenza. I recall encountering the word "grippe" in a book when I was young (Alcott? Austen?) and not knowing what it meant. Had to use the dictionary. Schazjmd(talk) 15:37, 13 November 2026 (UTC)
I ended up at Share taxi because I ran across one of its many names in a book. WhatamIdoing (talk) 17:00, 13 November 2026 (UTC)
John, I feel like you've given me contradictory reasons for wanting what you want. You told me that they shouldn't be in the infobox because they're not visible enough there; then you told me that they shouldn't be in the infobox because they're taking up too much space there. One of these things is not like the other. WhatamIdoing (talk) 16:58, 13 November 2026 (UTC)
Please don't twist my words! These are actually the same thing - a crowded infobox won't register with readers. Putting them over the photo is likely to mean they will be missed by readers, as I missed them - and I was specially looking for them. You've not given any reason why you don't think they should be in the text in the normal way. Johnbod (talk) 00:11, 14 November 2026 (UTC)
Everyone else thinks these infobox will be too short, so I think the risk of "a crowded infobox" is low.
Here is my reason why I think that a large number of synonyms should not be in the text: Having a whole separate section on ==Names== is too much emphasis on this minor aspect of the subject. It would result, to quote the NPOV policy, result in a disproportionate "depth of detail, quantity of text, prominence of placement" when what's needed is a brief list rather than a detailed description, a larger quantity of text, and a prominent entry in the Table of Contents. WhatamIdoing (talk) 22:40, 16 November 2026 (UTC)
If they are a "minor aspect", then they don't belong in an infobox: "An infobox is a panel that summarizes key facts about the page's subject." "The purpose of an infobox is to summarize, but not supplant, the key facts that appear in an article." Everything that is in an infobox should be in the article as well (though sadly many infoboxes violate this basic principle). If you don't think this information should be in the body of the article, then it certainly shouldn't be in an infobox. Fram (talk) 12:33, 17 November 2026 (UTC)
I believe that it is possible for a list of names to be both too minor for a whole ==Section== about the names, and also appropriate for an infobox. WhatamIdoing (talk) 01:25, 18 November 2026 (UTC)
The position that Fram has stated more elegantly than I did is the orthodox one on infoboxes, and always has been. Johnbod (talk) 04:29, 18 November 2026 (UTC)
The first-ever infobox was the taxoboxes, which don't follow the "orthodox" view. {{chembox}} similarly contains many facts that are not present in the text of the article, and there is no demand in the community to duplicate that content into the article with sentences like "The boiling point is 1749°C".
Even in infoboxes for which the principle generally holds, such as {{infobox artwork}}, it does not hold for all parameters (e.g., the map, dimensions, and website parameters in {{infobox artwork}}). In fact, it is so usual to have some information solely present in the infobox that we could probably justify a clarification to Wikipedia:Manual of Style/Infoboxes, e.g.:
"An infobox is a panel that summarizes key facts about the page's subject" → ""An infobox is a panel that summarizes key facts about the page's subject and certain kinds of other tabular data".
After all, the idea that infoboxes "should" summarize key points is already constrained by the existence of MOS:INFOBOXEXCEPTIONS. I am only suggesting that alternative names are one of the exceptions to the duplicate-article-content principle. WhatamIdoing (talk) 20:41, 18 November 2026 (UTC)
Infobox specifically for internet videos
Hello world!
I would like to propose a new infobox that I have been working on for a couple of weeks. It has gotten positive attention in the idea lab, so I think it's finally ready to be presented here.
So, I have been looking through articles about internet videos, and have been frustrated about there not being an infobox to properly represent them. Most people use the film infobox for internet video articles, which doesn't really do the topic justice in my opinion. So, I have spent time developing an infobox specifically for videos originally published on the internet. You can look over it yourself and see what you think. I am willing to make changes if anyone finds any problems with it.
In case anyone is wondering why there's stuff in the infobox for webseries, it's because I am also developing an infobox to serve as an alternative for webseries. However, I don't think that one's quite ready yet. Iconoclasty (talk) 18:28, 9 November 2026 (UTC)
Maybe, but I don't have authorization to edit templates. I also like to have more appropriate headers like "Metadata." Iconoclasty (talk) 17:05, 13 November 2026 (UTC)
Template:Infobox film/sandbox is not protected, and the sandbox is where changes to high-use templates should be developed and tested. Cabayi (talk) 08:51, 15 November 2026 (UTC)
I wasn't aware of that, thank you. Iconoclasty (talk) 14:39, 15 November 2026 (UTC)
Timeline Visual Component
Currently, I don't think there's any proper timeline visual component on Wikipedia. Most timelines I've seen are either made with bulletpoints, ordered lists or tables.
A timeline rail component is present in many UI frameworks nowadays and so most users are even used to it at this point. It would be much more visually appealing to learn about things evolved over time from it than from a simple list.
Here I propose a simple timeline component made with basic HTML elements, such as <div>'s, <li>'s and <span>'s.
Check a demo out here . And the code is here .
We could even extend this component to support parallel timelines as well. For example, if two separate labs developed the same research, it would be nice to visually be able to see that on separate timelines, instead of listing them sequentially. An alternative or additional feature would be having timeline "dots" support more than one event. Fanaro009 (talk) 15:31, 15 November 2026 (UTC)
I think this is pretty close to usable already, and it already has an implementation, so I believe we could maybe skip ideation steps.
I would be very much for trying out a simple version of this timeline component, it's such a simple replacement for bullet lists after all... Fanaro009 (talk) 20:12, 15 November 2026 (UTC)
It would be better for you to demonstrate it on wikipedia, in a user subpage or sandbox, so editors can see how it will behave with editing and such. Schazjmd(talk) 20:18, 15 November 2026 (UTC)
I got a little bit of trouble with an @supports CSS selector. I think that some of the features for parallel timelines or grouped timelines might need to be adapted. But let me know what you guys think. I believe even the basic version version of a timeline is already good enough. Maybe we can implement the rest of the feature set once that core feature is in. Fanaro009 (talk) 21:13, 15 November 2026 (UTC)
My bad, I didn’t realize we were talking about a template. Dw31415 (talk) 21:20, 15 November 2026 (UTC)
Sorry, I'm a noob here, what does talking about a template change about the discussion or your comments? Fanaro009 (talk) 21:40, 15 November 2026 (UTC)
Well, welcome! I was hoping someone more experienced than me would point you in the right direction. I just notified Requested Templates to hopefully get some more input/guidance. I think that group may have better insight into how templates get created. Have you suggested this at Go Talk? A big input will be whether there is a consensus to add it there. Dw31415 (talk) 16:00, 16 November 2026 (UTC)
By the way, that timeline idea was largely inspired by this recent pet project of mine, about Go (board game) history: Fanaro009 (talk) 15:36, 16 November 2026 (UTC)
(saw at WP:RT) Hmm, maybe. It looks nice. I'm just trying to think of the intended use for it. It's much less dense than some in current use; it couldn't replace the one below the infobox at The Elder Scrolls, and it would drastically expand the size of Timeline of historic inventions. And I think MOS:USEPROSE takes out another big chunk of possibilities.
I would also want to have someone who has more experience with accessibility take a look before using it widely.
That said, if you can come up with a compelling use-case for it, I think you've made a very nice start. LittlePuppers (talk) 21:28, 16 November 2026 (UTC)
And one very small nitpick: having nested templates like that can, in some circumstances, blow up WP:PEIS pretty quickly, which is one reason we usually end up with something like {{atop}} and {{abot}} instead of {{archive|the entire content of a discussion}}. LittlePuppers (talk) 21:52, 16 November 2026 (UTC)
In order to make my component possibly more compact, I've added a collapsible/expandable feature to the dots. And, if you double-click any dot, it compacts/expands all of the others as well. That should help with getting an overview of the timeline, in case it is too detailed or too big. Overall, though, I believe we don't need too worry that much about space, this isn't physical but digital media after all...
For The Elder Scrolls example, maybe the current state of my design would inflate things too much indeed. So I've just now added a compact variant that looks just like that one. I think I shouldn't go that way though, I would rather have my design as is, and, if people would like, they can use that other design from that other component as well, those are different visualizations in the end.
As for the other lists — even The Elder Scrolls one —, I think my design looks much nicer overall quite frankly, and theirs looks much more dated.
My design also goes much more naturally with different types of media integrated into it, such as regular HTML, Wikipedia components, pictures, graphs, etc, which makes for a richer timeline.
I've just now added a nested variant to my timeline as well, but I don't want to claim to replace or be better than the graphical or nested bars types of timelines. I believe all of them have their place. Fanaro009 (talk) 13:25, 17 November 2026 (UTC)
When it comes to collapsing/expanding and compacting the timeline, I've just added another feature: timeline sections, besides nesting. An example is in the demo's "Timeline of Historic Inventions". Fanaro009 (talk) 16:09, 17 November 2026 (UTC)
Anything else I should do? What else do I need to get this going? Fanaro009 (talk) 14:25, 18 November 2026 (UTC)
There's a list of other timeline templates/software in Wikipedia:Timeline. You should list yours there. Then you should consider whether the non-use of the existing ones is because there's no good way to add timelines vs because there's been little interest in adding timelines. If you conclude that it's the latter, then "getting this going" is probably going to involve you personally editing hundreds or thousands of articles. WhatamIdoing (talk) 00:45, 19 November 2026 (UTC)
This is very nice work. Well done. Sean.hoyland (talk) 07:15, 19 November 2026 (UTC)
Test an alternative placement for the AFI on the Main Page
WP:TWAFI is now in its fifth week on the main page. The extremely prominent upper-right-hand corner placement has generated substantial pageviews, albeit with a declining trend line since the first one. (Confectionery store had 111,984 during its week; Mechanic had 54,988; Frozen yogurt had 91,396; and Spinning top had 67,151.) Barkeep49's close of the proposal to add AFI to the main page noted only a weak consensus for the placement that has been used for the past month, and that RFC only included options that placed the AFI in the top two boxes. Given the weak consensus and the lack of alternatives under consideration in that discussion, I propose a limited test period of placing the AFI in the full-page slot above Today's Featured List and above Today's Featured Picture on days when TFL does not appear. At the end of the limited test period (which I propose to last as long as the period from when AFI began on the Main Page until the closure of this proposal, should it pass). At the end of the test, the community can compare page views, edit counts, new editor participation and other metrics from the AFI's performance in the two slots and hopefully reach a robust consensus for AFI's long-term placement on the main page. Dclemens1971 (talk) 16:10, 16 November 2026 (UTC)
Obviously not, since it is not linked on Wikipedia:Articles_for_improvement. And an RfC workshop is a much longer-term project, while I am proposing a short-term test of a single question. Given the previous weak consensus for the current placement, a short-term test of a different placement option will also provide data for the future RfC to consider. Dclemens1971 (talk) 16:35, 16 November 2026 (UTC)
Obviously not, since it is not linked on Wikipedia:Articles_for_improvement Since when are RfC workshop discussions supposed to be advertised on the project's homepage? There's currently an open RfC to reform ITN but I don't see anything about it on Wikipedia:In the news. The AFI workshop is the very first discussion on WT:AFI, where you just posted a new thread.Anyway, I mainly wanted to ask if you were aware of the RfC. I'm not sure it would be particularly helpful to move the section a couple of weeks before an RfC on where it should be placed is started. FaviFake (talk) 16:46, 16 November 2026 (UTC)
Agreed. We should wait for that AFI/RFC2 to begin, since placement is one of the questions. Some1 (talk) 23:36, 16 November 2026 (UTC)
Tentative support. I believe TFL only appears on certain days, so please clarify your proposed location on other days —Martin (MSGJ·talk) 17:00, 16 November 2026 (UTC)
@MSGJ thanks for the pointer, clarified above. Dclemens1971 (talk) 17:02, 16 November 2026 (UTC)
Alternatively we could display TWAFI on the days that TFL is not displayed —Martin (MSGJ·talk) 17:03, 16 November 2026 (UTC)
I'd suggest that be considered as an option for the AFI RfC workshop, but not here as I think this proposed test will benefit from simplicity. Dclemens1971 (talk) 17:05, 16 November 2026 (UTC)
I don't think a disappearing section has any real chances of getting consensus. There are already too many options. FaviFake (talk) 19:46, 16 November 2026 (UTC)
Support. This seems like the perfect way to cover the one thing the RfC can't: evidence. (It also gives us a convenient way to set when the RfC will begin: the end of this period.) 7amiþ = super().__init__(talk, contribs) 17:01, 16 November 2026 (UTC)
I think in addition to collecting metrics on the article for improvement initiative, metrics should be collected on the other components of the main page to see how they are affected. isaacl (talk) 18:41, 16 November 2026 (UTC)
SupportThriley (talk) 01:01, 17 November 2026 (UTC)
The data here and at WP:AFI/RFC2#AFI statistics is all over the place. If we run this test for 5 weeks and get another very small sample size with wide variance, I'm not sure we will be able to conclude much. I suspect many factors drive pageviews and edit count, including intrinsic interest in the article's topic. I like isaacl's suggestion to look at other Main Page stats from the same week to provide more comparison. We could also look at each article's average daily views for the 12 months prior to being featured and assess% change. —Myceteae🍄🟫 (talk) 01:23, 17 November 2026 (UTC)
My gut feeling is that page views (except for the very first AfI) are based almost entirely on how interesting the topic selected is. InfernoHues (talk) 02:23, 17 November 2026 (UTC)
Yes, at a rate of 1 article per week, this experiment in position would have to run for months and months to be able to really say anything. Chorchapu (talk|edits) 02:25, 17 November 2026 (UTC)
Yeah, I think the inaugural TWAFI got a bump because of community attention and the rest is driven by interestingness. Although, looking at this, it seems Spinning top got less of a pageviews bump than might have been expected. Another factor could be how accessible a topic is to edit. We would need some sort of A/B testing to truly isolate the effect of positioning and we would otherwise need many, many weeks of data under both conditions to have even a little confidence in the data, unless the difference is very big or negligible. —Myceteae🍄🟫 (talk) 05:23, 17 November 2026 (UTC)
This is correct, I think - the activity of TWAFI seems to jump around a lot, and if we were to draw any conclusions from a one week experiment, it would likely be dominated by the hard-to-define "interestingness" of that week's article.
Previous pageviews are surprisingly uninformative in predicting that aspect of things - in Jan-Aug 2026, "confectionery store" got an average of 36/day while "spinning top" got 174. Andrew Gray (talk) 12:52, 17 November 2026 (UTC)
Oppose The current location of TWAFI at the head of the main page seems to be working. Pageviews of 50K to 100K are comparable with what the featured article usually gets. And the call for editing has typically made the article the most edited article in its week.
If TWAFI gets pushed down to the position of the featured picture/list then its traffic seems likely to get similar traffic to those items. And that's much less. Looking at recent examples, the featured picture article only gets about 5K views while the featured list only gets about 2K. So, putting TWAFI down in the weeds seems likely to kill it. The original RfC decided to put TWAFI at the top so that it would get good attention and we should stick to that plan.
It seems you misunderstood the proposal. The actual placement will be decided in the RFC. This proposal would temporarily move the section to the bottom for a few weeks just to see how many page views it gets compared to previous articles for improvement. FaviFake (talk) 15:00, 17 November 2026 (UTC)
I understood the proposal just fine. Moving TWAFI down as proposed would reduce the traffic significantly; this is already obvious and we don't need a test to prove it. It's better to stick to the current plan as we already have issues to address such as the case of Garbage – a topic with debatable scope and which was initially protected, requiring a last-minute scramble. Shaking such bugs out of the current process is still a work-in-progress and so we should minimise gratuitous change before the next RfC, to allow the current configuration to bed in and avoid confusion. Andrew🐉(talk) 16:39, 17 November 2026 (UTC)
The point of a duration-limited test is to allow additional data before the current configuration beds in, since the consensus for the current placement was not strong. Dclemens1971 (talk) 16:52, 17 November 2026 (UTC)
The original RfC had a similar configuration suggested as option P.4, placing TWAFI below OTD. That had less of a consensus than the current P.2. The OP does not explain why their suggestion should be given priority over the myriad of alternatives which others have suggested or the agreed P.2. The forthcoming RfC will present many options and that will be the time to consider an alternative. Andrew🐉(talk) 18:30, 17 November 2026 (UTC)
Something like the proposed test position above TFL was suggested multiple times in the extensive post-AFI launch discussion at Wikipedia:Village_pump_(idea_lab)/Archive_84#Brainstorming_ways_to_resolve_the_gap_with_TWAFI_on_the_Main_Page. The point is not to kill AFI, to use your words. The point is to gather some data, obviously limited but still valuable, on what the difference in traffic and participation would be if it were in a slightly different spot, which would then result in a better-informed RfC process. Dclemens1971 (talk) 18:38, 17 November 2026 (UTC)
The focus of that discussion was "the gap". It didn't arrive at a clear conclusion but the de facto expedient was to adjust the column width split. This new proposal would upset the balance again but the proposal doesn't even mention the issue or what it would do about it.
A human factor was outrage that the main page had been changed without wider consultation. This proposal is even worse; it isn't even an RfC.
Acknowledging the existence of the secondary RFC, I do want it out in the air in the event yet an other RFC comes and goes on the topic without me noticing that I support this idea. Kinda baffled me that this wasn't one of the original proposals at all - it always made the most sense for main page balance to me. DarkSide830 (talk) 00:12, 18 November 2026 (UTC)
Everyone should please monitor WP:CENT if they want to know when the next RfC is started. FaviFake (talk) 01:14, 18 November 2026 (UTC)
Remove this feature now!
Sometimes in mobile there's a display of all images in the article at the top, those are cropped to square, can be hidden but not removed completely.
This feature is useless! Remove it now!!! ~2026-60966-11 (talk) 08:37, 18 November 2026 (UTC)
That is presumably a beta test of the "Image carousel" feature. There should be a button to "Hide" it on the top right. CMD (talk) 10:44, 18 November 2026 (UTC)
It is actually possible for people to vandalise other users pages and cause real chaos, and also vandalise or completely delete user pages. This contributes to a moderate number of vandalism.
Thats why I propose User Protection and Extended-Autoconfirmed Protection.
User protection instantly protects a users page and their talk page, as well as other user pages by them such as editnotice page so other users cannot edit it and only them. It's like full protection, but the user is like the administrator. For example, there is user 1 and user 2. If user 1 creates their user page and any other user pages, user 2 cannot edit them. This can contribute to decreasing vandalism.
Now there Extended-Autoconfirmed Protection, and you are free to use a different name if its too similar to Extended-Confirmed.
Extended Autoconfirmed is an extension of Autoconfirmed protection. It requires 200 edits and it must be two weeks since your first edit. Since the gap between Autoconfirmed and Extended Confirmed tends to be too wide, this is basically a stop protection level which makes it not too far from Autoconfirmed, but also not too far from Extended Confirmed.
Overall, if these two types of protection go live on wikipedia, they can reduce vandalism and contribute to users who might be tired from editing.
User pages are not owned by the user. They're still a part of the project and exist to tell other Wikipedians about one's edits, not as free webhosting space. Userprotection would make it far too easy for user pages to be used for things they shouldn't. CheeseAndJamSamdwich (talk) 22:23, 18 November 2026 (UTC)
Heavy vandalism is the only excuse I can see as justifying protection of user pages. User page vandalism does not appear to be a big problem at this time. Nothing at all like 20 years ago, when my user page was vandalized 29 times in one year but never protected (I'm not sure we even had protection back then). Donald Albury 22:57, 18 November 2026 (UTC)
There's already a sort of user page protection via the 2016 Special:AbuseFilter/803 ("Prevent new users from editing other's user pages"), which prevents logged-out and new editors from editing someone else's User: page. I believe that's the reason why User: page vandalism (and accidentally misplaced comments) have declined so dramatically. WhatamIdoing (talk) 00:11, 19 November 2026 (UTC)
Idea lab
AI-assisted search
While AI is terrible for writing articles or as a source of information, I think it could be very useful for performing advanced searchs in Wikipedia (and other Wikimedia projects). Many information in Wikipedia about a particular topic is disperse across several articles (many of them unrelated), and I think AI could be useful to find all the information related about a particular advanced search. The key points of my idea are:
Wikipedia is losing visits because of AI. While Wikipedia is not a business and its main goal is not to maximize the number of visits, many Wikipedians are worried about this. If Wikipedia makes use of AI, the people who go where there is AI because it's cool, would also come to Wikipedia (they wouldn't see Wikipedia as an old-fashioned site where AI is not present at all, but as a modern cool one). Another reason why more serious, conscious people can be making use of AI in place of Wikipedia is the ability to perform advanced queries and get links to reliable websites in a quicker way than they would with Wikipedia (or with a traditional search engine). If Wikipedia provides this ability, in combination with its human-reviewed, extense articles, it can be an absolute winner.
Full respect to people who reject use of AI. Wikipedia is not anti-AI, but people who don't want to use AI at all must remain free to keep doing so. The current search box must continue working without any LLM AI.
Any used software, including the LLM, must be freely licensed. All such software (LLM included) should be run at WMF's infrastructure.
An AI button would be shown at the right of Wikipedia's search box. From there, the user would be able to perform advanced searches using natural language. The button should be present in all Wikipedia editions in languages supported by the LLM, and maybe also in other Wikimedia wikis.
The AI must have restrictions in place so it can't be used for any purpose that is not the search of information in Wikipedia or other Wikimedia sites.
The search results can include Wikipedia articles, Wikivoyage travel guides, books at Wikisource, images, videos or PDF books at Wikimedia Commons, etc. All of them in any language, with machine translation being used when convenient. The results could also be a specific section or subsection of any of these wiki pages. Unlike a "normal" search, the search results would not be a simple list of links, but a coherent text that presents them in a way that is easy to understand by the user.
The AI should generate the shorter possible response in natural language. The important part of the response would be the search results: the generated text would be mostly for putting the different results together, and for providing context to the user, but the generated text should never be provided in a way that replaces reading the original wiki text. If the specific search makes it convenient, parts of such wiki text (including their external references) could be provided verbatim in the response, in a way that it's clear to the user that the shown text comes directly from the wiki.
Of course, this idea would cost time, money and resources to WMF, but maybe these costs could be far less than those of the failed Abstract Wikipedia, while achieving a similar goal (or so I believe; sincerely, I was never able to fully understand the exact goal of Abstract Wikipedia), and in a way that is accessible to the mass public (and, for a part of them, even "cool"). MGeog2022 (talk) 17:46, 18 September 2026 (UTC)
Besides being more expensive and probably worse, how would this be different from going to your chatbot of choice and typing in "I would like to know _____. Please use exclusively Wikimedia sources to research and write a summary answer, and provide links and quotes to relevant wiki articles as appropriate."? -- LWGtalk(VOPOV) 18:58, 18 September 2026 (UTC)
Well, my proposal would give the user true Wikipedia results, and encourage the user to use Wikipedia. The user would be using pure Wikipedia, with no hallucinated garbage in the middle (the summary would be brief and leading to true Wikipedia articles; in some cases, it could include verbatim copies from them).
Please use exclusively Wikimedia sources to research and write a summary answer: the point here is: how many people (particularly non-Wikimedians) would do that? How much hallucinated trash are people believing and reusing because of not being conscious of these options in LLMs? When bad quality information/"knowledge" is on the increase, we could help to solve this problem. And, well, it would probably be expensive, but I suspect Abstract Wikipedia is more expensive and produces next to none useful results, while integrating AI could help to connect again with the mass public that is leaving Wikipedia for their "new toy". About being "probably worse", with all the conditions that I specified (brief summaries with the only purpose of querying Wikipedia, leading the user to actual wiki pages or parts of them), there is no need for the LLM to be the best one available. As a source of knowledge, every LLM is bad. LLMs are (relatively) good at doing things, they are not good at knowing non-trivial facts. MGeog2022 (talk) 19:15, 18 September 2026 (UTC)
"how would this be different from going to your chatbot of choice and typing in": by the way, this is not different from many commercial websites that include their own AI chatbot. People could use any general-purpose chatbot for that, but the site's owners consider that having their own chatbot is the way to retain visits to their site. While Wikipedia is non-commercial, and maximizing visits is not our main goal, a really massive loss of visits can eventually become a huge problem for the community (even while it will always keep a certain niche of users, but that would not be the same Wikipedia we all know). MGeog2022 (talk) 19:22, 18 September 2026 (UTC)
An important detail that I forgot: on its own initiative, WMF has plans to introduce AI for suggestions when editing, no matter how expensive it is or if a general purpose chatbot could do it better. In my opinion, this is just the case where AI should be avoided at all: for writing content (other than for minor adjustements, such as translations, where it is acceptable). If WMF is in favor of using AI in Wikipedia, I think the querying part is the one where it can do more good than harm. MGeog2022 (talk) 20:00, 18 September 2026 (UTC)
I suspect that WMF is fully aware of our strong antipathy towards AI. Blueboar (talk) 20:06, 18 September 2026 (UTC)
please read the thread you linked in its entirety, there have been some clarifications and changes to said plans which will become clear once you read it Gnomingstuff (talk) 06:46, 20 September 2026 (UTC)
A really long discussion there. What seems clear is that most of the community fully rejects any use of AI in Wikipedia. MGeog2022 (talk) 08:52, 20 September 2026 (UTC)
with no hallucinated garbageAnother fatal misunderstanding of AI. You cannot prevent hallucinations. They aren't a flaw limited to how specific systems are programmed - they're an inherent flaw with the technology itself. Don't you think they'd fix it if they could? Limiting the database to specific sources won't solve it. I've experienced outright hallucinations from a micro AI that was programmed for a single book. The only way to guarantee information is accurate is to verify it yourself, regardless of where the feature is hosted. Why should we waste WMF resources for something that would have no significant benefit over external tools? ChompyTheGogoat[Bleat|Munched] 20:40, 18 September 2026 (UTC)
Thanks for your responses. Yes, that's true. But, if the software behind this function asks the LLM to work in some specific ways, including writing only very brief summary texts with links, or verbatim copying some sections, the risks of hallucinations causing any damage is minimal (the brief text itself could contain instructions not to directly use it but to click on the provided links to articles or sections of articles).
Why should we waste WMF resources for something that would have no significant benefit over external tools? I think the benefits would be about reaching the wider public in the AI era, and I believe this is no minor issue: it's like having official Facebook and Twitter accounts 10-15 years ago; we could dislike social network sites, but Wikipedia created official accounts in both of them, and it helped to reach a wider public. I don't like Wikipedia being considered as something from the past by an important part of the population, no matter how silly their thought can be. This is a complex issue, but it shouldn't be considered in a Wikipedia vs AI way. In any case, it's a knowledge vs ignorance one, and by making Wikipedia acceptable to AI "fanatics" (distinct from simple AI users, but I fear those involuntary "fanatics", said with all respect to them, possibly outnumber the sum of AI users and AI non-users), knowledge can win over ignorance.
Another reason would be providing an easy to use way to query the vast Wikimedia datasets (a general purpose chatbot is not optimized for querying Wikimedia data only, and properly using it for that would be very difficult, and, while very useful, giving the enormous size of the dataset, really few people would take the needed work to do it).
WMF resources will be wasted anyway in the "AI-generated edit suggestions". MGeog2022 (talk) 21:05, 18 September 2026 (UTC)
And I'm fully against that proposal too. We're already seeing damage from the Revise Tone tasks. As a donor I have a vested interest in how funds are utilized - and WMF should be acutely aware of how their actions are perceived by donors, given the events regarding WWU.General chatbots do not need to be "optimized" to search Wikimedia. I can tell it to look for something here and it does. If users made a conscious choice to come here and utilize a built in tool they can make the same choice to tell an external tool to search for results here. Simple as. If they're not explicitly looking for results here, they won't navigate here in the first place. Wikipedia was built by humans, for humans, and people who value human knowledge come here for that purpose. The last thing we want to do is dissuade those users - especially those who are editors, or have the potential to be. Fanatics already have Grokipedia, so it's amusing that they still feel the need to come here and try to insert AI content. If it was so great everyone would flock over there instead. ChompyTheGogoat[Bleat|Munched] 21:21, 18 September 2026 (UTC)
Here, I was talking about "AI fanatics", not "X man"'s fanatics (many people, regardless of their ideology, have a blind faith in AI; they may consider any encyclopedia as unneeded in 2026, whether Wikipedia or Grokipedia). I agree with your comment 👍 MGeog2022 (talk) 21:31, 18 September 2026 (UTC)
As of November 2026 they do not do it very often. jp×g🗯️ 21:44, 1 November 2026 (UTC)
Well, there was that time when ChatGPT started putting bizarre snippets from foreign scripts in the middle of English responses for some reason. I can't find a link, but it happened rather recently. GrinningIodize (you just lost the game) (talk) 23:00, 1 November 2026 (UTC)
This is really tangential to the discussion but I use Claude and it also does this, though maybe even stranger, since what I get is, reliably, single words either transcribed letter-by-letter into Cyrillic or translated into Chinese. No obvious trigger, I only use English with it. It doesn’t happen often but it definitely does happen. I started using Claude very recently so I don’t know if this started recently but I can confirm it still happens. ~2026-60847-23 (talk) 04:48, 17 November 2026 (UTC)
I've been using Claude Sonnet and Haiku (basically everything from Sonnet and Haiku 4 onwards) for months now and haven't noticed this; what models are you using? GrinningIodize (you just lost the game) (talk) 13:37, 17 November 2026 (UTC)
Get links to reliable websites in a quicker way than they would with WikipediaWe're not a search engine. We only provide limited external links for additional context to article content. If people are wanting to navigate to external sites they shouldn't be utilizing Wikipedia for that purpose. ChompyTheGogoat[Bleat|Munched] 20:32, 18 September 2026 (UTC)
The WMF is not going to be able to outcompete commercial llm-companies fully dedicated to LLMs. If someone wants to overlay one of those over Wikipedia and craft a relevant prompt, that would be much simpler and sustainable way to achieve the goals above. CMD (talk) 07:13, 20 September 2026 (UTC)
The WMF is not going to be able to outcompete commercial llm-companies fully dedicated to LLMs. WMF should never try to do that, and this was never the purpose of this proposal (AI companies create LLMs: this proposal was about deploying and using an already existing, freely licensed LLM). MGeog2022 (talk) 09:30, 27 September 2026 (UTC)
considering AI is currently experiencing diminishing returns they'll likely be pivoting to models that master one field instead of the omniscience that every company seems to be chasing. A lot of money was invested into this tech and with that they'll need something people worldwide would want to pay for or else you're going to start seeing them in panic mode which we had a glimpse of just recently when the top 5 companies decided to finally meet. probably better to wait than to join in now when they're hitting the ceiling performance wise ~2026-48820-80 (talk) 01:08, 10 November 2026 (UTC)
[Use RAG -- gain trust] Some entity might indeed want to implement a natural language querying and summarisation/formatting of a response based on Wikipedia-specific data. It mightn't be necessary for WMF to host that facility, given (possible) additional resources above its usual search. This natural language interaction would be different from prompting a popular chatbot to "Please use exclusively Wikimedia sources to research and write a summary answer, and provide links and quotes to relevant wiki articles as appropriate". One couldn't guarantee a popular chatbot would accurately follow the prompt... however... popular chatbot (or other) could be explicitly configured to use Retrieval-Augmented Generation and low temperature based on the live Wiki data to increase reliability and leverage the naturally multilingual nature of AI embeddings. How WMF could contribute to a Wikipedia-with-AI done better I think is down to technical aspects of implementation. I believe it prudent for WMF to be proactive on how its scraped data is being used. It's not a competition between AI-easy-untrustable and Wiki-harder-high-value, it's about preserving the integrity of information and facilitation of wide access. Munnum (talk) 09:54, 26 September 2026 (UTC)
Good comment. If done, while it mightn't be necessary for WMF to host it (it would be highly convenient, though), user privacy must be fully guaranteed, and all the used software (LLM included) must be freely licensed. Wikipedia is about freely licensed content, and that's also the case with associated software such as MediaWiki. AI software can't be considered in a different way: one thing is the vast hardware resources that running it requires at this moment, so it may need to be run externally (but this should change in the future), and a very different one is to neglect its free licensing. Some years from now, good AI should be able to easily run in a normal computer or server. With AI computing, we are still like in the mainframe era of the 1960s. The AI equivalent of the 1980s and the Personal Computer will need to arrive at some moment. MGeog2022 (talk) 09:21, 27 September 2026 (UTC)
An estimated 78% of reading sessions originate from external search engines. with 90% of those coming from Google Search. ... When readers consistently find it easier to access Wikipedia’s content through third-party platforms than on Wikipedia itself, the site risks becoming a background data source rather than a destination for learning.As in, the same way readers have found their way to Wikipedia ever since it was created? This sounds like more of the slimy corporate "capture all the traffic and never ever let them leave" crap from the discussion about the app and does absolutely nothing to improve my opinion of WMF. Apparently when you reach a certain size slimy corporate behavior becomes mandatory. Very keeping up with the Joneses. ChompyTheGogoat[Bleat|Munched] 21:50, 5 October 2026 (UTC)
I actually wanted to post about a "Google AI Overviews"-like AI assisted search concept feature in here too, with the same goal of getting people to continue using Wikipedia instead of external AI tools! Looks like you've beaten me to it:)I do agree that the AI (model) used for the AI search should be open sourced, and not (necessarily) be built in-house by the WMF. Also, this feature should also be opt-in rather than opt-out. Since we're targeting readers rather than editors, if and when we conduct these tests, the AI functions would be shown to them first, rather than being shown to editors first. And of course, there must be guardrails, the information should be cited to an article so readers can learn more from there.There are some differences between your idea and my idea though. Most notably is the placement of the "AI search" button. Personally I'd rather put the AI search button at the bottom right (or bottom left) corner of the page, similar to the help panel shown to new editors, in contrast to being shown to the right of the search bar as you conceived. Also, not sure if we want cross-wiki search, but we'll see.I do have more comments, including use class and mockups (using the Codex template on Figma), which I will leave below this main comment. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 04:55, 6 October 2026 (UTC)
@Hason-LEK-SIN, thanks for your comment. Yes, I agree that the current search must always be kept, and that AI should be used only as an interface for the search of information, never for writing text for the articles. The exact placing of the button would be a minor issue, several places can be considered and debated, for sure:) MGeog2022 (talk) 11:42, 11 October 2026 (UTC)
Oppose. I feel that the people who would come to Wikipedia if this change were made would be outnumbered by the people who would leave. So many people, especially the type of people who use Wikipedia, have a strong dislike for generative AI. Those who especially enjoy AI will often not see a use for visiting many other sites, since AI can already tell them everything they'll want to hear. Siteseers (Talk/Contributions) 16:27, 6 October 2026 (UTC)
I don't argue with this, but I find it ironic, given the early days of Wikipedia itself when many people "repelled the idea of an encyclopedia that anyone could edit because it would never be as reliable as traditional sources." Sira Aspera (talk) 20:41, 6 October 2026 (UTC)
(This is the idea lab, by the way) Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 23:25, 6 October 2026 (UTC)
Sorry, I'm new to Wikipedia, can you not oppose ideas in the Idea Lab? Siteseers (Talk/Contributions) 13:03, 7 October 2026 (UTC)
First off, welcome! Secondly, do read the top of the Village Pump, which says:
This page is not for consensus polling. Stalwart "Oppose" and "Support" comments generally have no place here. Instead, discuss ideas and suggest variations on them.
Those who especially enjoy AI will often not see a use for visiting many other sites, since AI can already tell them everything they'll want to hear. And this is a big problem, and one that Wikipedia could help to solve, by using AI in helping people to find knowledge, in place of believing hallucinated trash.
So many people, especially the type of people who use Wikipedia, have a strong dislike for generative AI. Wikipedia is not written for Wikipedians, but for the public as a whole. Out there, such dislike does exist, but is not so prevalent. And we must differentiate using generative AI as a source of knowledge (which is wrong, unless looking for very basic facts) from other uses of generative AI. Making Wikipedia to look as a project for anti-AI people only would make it a fringe project. I don't want that, and I hope most of the community also doesn't want it. Wikipedia has gained a place where it is mainstream. One of the few cases where the main existing product is both a freely licensed one and one well-known to the masses (for example, Linux, while absolute leader in some types of computing, is not so well-known for many people as Wikipedia is). We believe in freely licensed content, and we should enjoy the fact that we are the leading encyclopedia. We shouldn't renounce that, much less tolerate being replaced in society by something that is not even an encyclopedia nor a proper written work (the latter point is important, because even freely licensed AI models shouldn't replace Wikipedia, since they are not true written works). And, at this moment, we need to fight for that, whether you are a pro-AI, anti-AI, or neutral Wikipedian. Maybe AI-assisted search is not the only or the best thing to do for that, but I think that Wikipedia/WMF should highlight why Wikipedia is needed by humans in the AI era, and make campaigns around it (and, no, an "all AI is evil" campaign would not be the solution: it would make the problem worse, since many people use generative AI for work, and they are happy with it: the campaign should focus on the points where Wikipedia is far better than AI: each thing has its own purpose).
I feel that the people who would come to Wikipedia if this change were made would be outnumbered by the people who would leave: really? If Wikipedia adds an AI-assisted search (I'm not talking about AI-assisted article writing, that would be another thing), many people would leave? What would they do, then? Since they are anti-AI, I suppose they would go to Encyclopaedia Britannica, and, when the information is not there, I suppose they would just accept ignorance. Fortunately, there are more things than fanaticism (pro-AI, anti-AI, or pro or anti whatever you want) in life. MGeog2022 (talk) 11:22, 11 October 2026 (UTC)
Being anti-AI isn't fringe, and keeping AI out of specific spaces that have always been written by humans, for humans certainly isn't. You can acknowledge that it has valid uses and still not want it encroaching in certain areas - and it's already causing issues where it's been inserted here without consensus, so I have precisely zero faith that giving them license for additional uses would turn out any better. Wikipedia should be upholding quality standards, not trying to win a popularity contest. People who already believe hallucinated slop aren't looking for alternatives anyway because they don't know any better. If they did, they'd use us without needing AI features as some weird form of bribery. ChompyTheGogoat[Bleat|Munched] 13:00, 11 October 2026 (UTC)
keeping AI out of specific spaces that have always been written by humans: I fully agree on keeping AI 100% out of writing any Wikipedia content: my proposal is only about a tool for querying information, but that information must be written by humans.
Wikipedia should be upholding quality standards, not trying to win a popularity contest: both things are needed: Wikipedia's quality itself would be in trouble if only a tiny minority of the people use it. It's not about getting as many visits as possible, but about continuing to be the leading source of knowledge. Visits to Wikipedia are going down, and the solution to this is not just saying that we are better and wiser: Wikipedia must not allow being silently replaced by non-free products that are not even an encyclopedia.
According to this source, in the United Kingdom, 42% of individuals deliberately limit the amount of AI they use. Only a part of them would be purely anti-AI people. I believe Wikipedia should be for everybody, not only focused on that <42% of the people: believing that Wikipedia should be specifically directed to the, let's suppose, 25% of people who oppose using AI at all, is what would make it a fringe project. A fully optional AI-powered search has nothing to do with basing Wikipedia on AI: it's just an optional tool that you use if you want, and, if you don't want, you don't use it. We can't allow AI damaging Wikipedia's quality, but we also can't allow AI making Wikipedia irrelevant for the wider public. Wikipedia should be for everybody: for people who don't like AI, for people who like AI, and for people who are indifferent about AI. And I would like to add that, as long as AI (particularly, non-free AI) threatens the usage of Wikipedia, free content and open source software, I'd belong to the anti-AI camp. We can't stop AI (no new technology has ever been suppressed), but we can stop the damage it causes to free knowledge. MGeog2022 (talk) 16:42, 11 October 2026 (UTC)
42% is hardly a "tiny minority", and you seem to be assuming that the remaining 68% who don't actively avoid it would also refuse to utilize any products that don't include AI, which is a massive leap. So is the notion that anything without AI features will become irrelevant. This is feeling more and more like obsessive POV pushing without any care for consensus. You said weeks ago What seems clear is that most of the community fully rejects any use of AI in Wikipedia, and yet you're still here arguing for it, in what should probably be a WP:SNOW close since you've seen how similar discussions turn out. ChompyTheGogoat[Bleat|Munched] 18:58, 11 October 2026 (UTC)
I hope you are right, but I don't like the "AI replaces Wikipedia" thought that I see out there, and I believe that something should be done about that. As I said, I'm not a pro-AI fanatic at all, but I don't see that a majority, or even a big minority, of people are anti-AI (42% of people "deliberately limit the amount of AI they use" is not the same as them trying not to use AI at all). And I'm not doing "obsessive POV pushing" at all: I only commented here again in response to other, new comments from other users (by the way, one of them was in support of my proposal). I took advantage of this to express my worries about the seemingly endless fall in the number of visits to Wikipedia, and to warn about the dangers of a "Wikipedia vs AI battle". We must be aware about how prevalent the use of AI is (even if we don't like it at all), and make Wikipedia the leading source of knowledge in this era, just as it was in the previous one. In fact, the problem is not how prevalent AI is, but how much it is being trusted as a source of knowledge (which it isn't), even by people with university education. The solution to this is not to "destroy AI", but to convince people to use Wikipedia for what Wikipedia is, and to use AI for what AI is. Maybe a WMF campaign could help with this, or maybe time will do it (but there is a risk in the latter case: given the current panorama, I fear that hallucinated ignorance could eventually win). MGeog2022 (talk) 19:24, 11 October 2026 (UTC)
Brittanica also has an AI. CoolDino1 (talk) 16:12, 15 October 2026 (UTC)
A DOSE OF REALITY. No one likes the smell of goats, but if they get stuck in a place with goats the small gets in their clothing and they will get used to it and not notice it. Those who do not like AI search, myself included, will eventually have that fate. AI search is everywhere and we will all be covered in it sooner or later. Sigh... Yesterday, all my dreams... (talk) 10:00, 7 October 2026 (UTC)
Most corners of the internet aren't governed by democratic consensus. This is one of the few places we actually get a say in whether or not features are implemented, rather than having them forced down our unwilling throats (for the most part). ChompyTheGogoat[Bleat|Munched] 00:22, 8 October 2026 (UTC)
Wouldn't this argument be Argumentum ad populum? You appear to be assuming that since a lot of other people are conforming to the idea of AI (for lack of a better term) then we must also conform, even though that is not the case. Siteseers (Talk/Contributions) 14:03, 8 October 2026 (UTC)
Advertisements are everywhere. Data collection is everywhere. Wikipedia doesn't have to follow the herd; we are not driven by shareholders fixated on the next quarter's earnings. Certes (talk) 20:42, 8 October 2026 (UTC)
Advertisements are contrary to Wikipedia's principle of neutrality. A freely licensed AI model isn't contrary to Wikipedia's principles. This is a bit off-topic here, but I feel that the anti-AI sentiment of many people from the free content and open source world has made non-free AI models to reign, and eventually, to free content and open source software being replaced by non-free AI, and this is really sad. I hope free AI models can eventually lead in their field some day. MGeog2022 (talk) 11:27, 11 October 2026 (UTC)
*Also the free software community. Despite common misconceptions, the open-source movement and the free software movement are different but related sides of the same coin. Free software folks like to think of freely-licensed software as being a tool of personal liberation, and don't really care for businesses as long as there's no non-commercial clauses or anything. While this approach tends to attract a lot of individual users, it has the disadvantage of scaring away businesses, who usually have more cash to blow on developers.
Open-source is a weakened version of free software, but instead of fighting for individual freedom, its selling point is that it's cheaper and more effective for businesses than proprietary software. While this is quite palatable to companies like Microsoft that wouldn't otherwise adopt freely-licensed software into their workflows, it comes at a cost, as companies generally want the right to restrict downstream usage of the software, and the developers generally agree to this.
Thank you for listening to my TED Talk. (Feel free to use this as a nerdy copypasta.) GrinningIodize (you just lost the game) (talk) 12:02, 14 October 2026 (UTC)
Certainly, while licenses are similar in both cases, free software and open-source are different philosophies. In the end, as with Wikipedia, most users don't come from philosophical but practical reasons, so FOSS is used by many people thanks to the open-source approach by companies (it would be great if most people thought in software freedom terms and that was the leading cause of FOSS usage, but, sadly, the reality is far from that). MGeog2022 (talk) 13:36, 14 October 2026 (UTC)
And how do we make sure? We've already seen how AI fails to locate information reliably.
The problem is not the cost (WMF could probably trade API datalines for LLM companies for LLMs), but the accuracy. Oppose. Zeta Puppis (Naos) (talk) 03:03, 16 November 2026 (UTC)
Collapsing friendly banter to keep things organised. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 23:38, 15 October 2026 (UTC)
It's only an issue at the beginning of a message because wiki markup uses regular: colons preceding comments to nest discussion replies. Simply adding a space to separate it from those resolved it. ChompyTheGogoat[Bleat|Munched] 21:36, 14 October 2026 (UTC)
For reply link ease. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 14:27, 12 November 2026 (UTC)
I'm not convinced that a Google AI Mode alternative with a more limited domain of knowledge and open-weight models would get a lot of usage, and plus, every dollar spent on energy costs for this model would come straight out of donations that could have gone somewhere more important instead.
I suppose a trial run with a low-cost model hosted somewhere else could work, but even then, I think that it would probably stain the Wikipedia's reputation amongst the folks who thought that AI Overviews were full of poppycock when they first came out. GrinningIodize (you just lost the game) (talk) 12:33, 12 October 2026 (UTC)
Google AI Mode alternative with a more limited domain of knowledge: Wikipedia's search also has a "more limited domain of knowledge". The difference is that Wikipedia's search results (AI-assisted or not) are trusted as knowledge, while many Google results (AI-assisted or not) are not proper knowledge and/or are not trustable. We shouldn't compare Google's AI mode with the proposed "Wikipedia's AI mode": they would have very different scopes. An AI-assisted search that could locate all information about a topic that is distributed among many Wikipedia articles, would do a far better job than Google's mix of information from any kind of source (Grokipedia and social network sites included). MGeog2022 (talk) 18:15, 12 October 2026 (UTC)
Still though, the folks who search on the Wikipedia are usually people who don't want to read an LLM summary, and for those who do, they can always just ask their favorite LLM service to read Wikipedia articles. GrinningIodize (you just lost the game) (talk) 19:42, 12 October 2026 (UTC)
Additionally, Wikipedia is already one of the most cited websites by LLMs. LLMs are already pulling from WP whether it's a WMF-sponsored project or not. Shocksingularity (talk) 06:00, 14 October 2026 (UTC)
trusted as knowledge There you go again. AI results cannot be trusted to avoid hallucinations regardless of the size of the knowledge base. It's a fundamental flaw in how they operate, and people who don't understand that will fall for misinformation regardless of the source. Extrapolating Wikipedia's current reputation built on human editing to imply that local AI would be more reliable than external ones would only tarnish that reputation. ChompyTheGogoat[Bleat|Munched] 21:07, 12 October 2026 (UTC)
An AI whose literal only source was Wikipedia would not make the same errors as Google's AI (or any other general AI), but that doesn't mean it would not make errors. It would not regurgitate random misinformation (unless said misinformation was present in one of our articles, but that's a GIGO problem that affects all search engines regardless of technology), however it could still produce misinformation by e.g. incorrect synthesis or removal/misunderstanding of nuance. Thryduulf (talk) 21:16, 12 October 2026 (UTC)
You're somewhat right in the sense that hallucinations aren't regurgitation - they're hallucinations. Invented completely out of the blue regardless of sourcing, which I have personally experienced from micro models built on a single source. It doesn't have to be the result of of incorrect analyses either; the information just flat out does not exist anywhere. ChompyTheGogoat[Bleat|Munched] 21:22, 12 October 2026 (UTC)
I'm not sure there's a good way to split the distinction between the accuracy of text completion predictions made by an LLM trained on Wikipedia versus one trained on the broader Internet. An LLM isn't trying to reproduce information from its training base; it's generating text that its internal black box thinks is a suitable consequence from the prompt. So the response could still be out-of-the-blue wrong from a Wikipedia-trained LLM. isaacl (talk) 22:02, 12 October 2026 (UTC)
At least the old Google snippets were accurate reproductions from the source - just not necessarily relevant to the actual query. ChompyTheGogoat[Bleat|Munched] 22:06, 12 October 2026 (UTC)
I wasn't talking about a LLM trained on Wikipedia. I was talking about using a freely licensed LLM developed by a third party (already trained by the third party), with the appropriate setup for it to search information on Wikipedia (and maybe also its sister projects) only (related concepts: AI agent, Agent harness). LLM training is only for the LLM to have a very basic general culture, but this makes it able of giving basic information only. As I said in the Wikipedia essay I recently wrote, one could say that AI doesn't know: it knows how to do. While hallucinations are always possible, AI works far better with source texts as "raw material": its internal knowledge base is useful only for very basic concepts. To avoid problems with hallucinations or misinterpretations by the AI, I'd like to emphasize its role should be that of a search assistant, inviting the user to actually read the content in the Wikipedia articles (or other wikis or Commons media files), or, when appropriate, including a paragraph, taken verbatim from the article, with citations included, and a link to the article's section where the paragraph was taken from. My idea was to undo the "AI replaces Wikipedia" change that some people underwent, by providing the needed tools for it, while also adding new advanced search capabilities to Wikipedia and its sister projects. MGeog2022 (talk) 12:57, 13 October 2026 (UTC)
I was commenting on Thryduulf's statement An AI whose literal only source was Wikipedia ... would not regurgitate random misinformation. isaacl (talk) 18:39, 13 October 2026 (UTC)
Strong oppose: I don't use or trust AI for good seasons. AI should not be doing edits on this site and that's why people are leaving Wikipedia. You guys better think this over. BattleshipMan (talk) 06:23, 22 October 2026 (UTC)
The idea lab is not a place for Oppose or Support comments. I did the same thing. Also, this idea does not involve AI editing an article. While AI is terrible for writing articles...Siteseers (Talk/Contributions) 12:49, 22 October 2026 (UTC)
Yes, this proposal is not about AI making any edits. In addition, in case this proposal was eventually implemented, you (@BattleshipMan) would still be able to search, use and edit Wikipedia without using any AI. MGeog2022 (talk) 12:54, 22 October 2026 (UTC)
If all the LLM is doing is displaying the results in a way that's easily human readable then I don't see a problem with this, but I don't think that's quite what's being suggested. The more simplistic the LLM implemented, the more likely it will not muck up, but people who desperately want to use AI won't won't a simple implementation. -- LCU ActivelyDisinterested«@» °∆t° 21:45, 7 November 2026 (UTC)
As the proposal says:
The AI should generate the shorter possible response in natural language. The important part of the response would be the search results: the generated text would be mostly for putting the different results together, and for providing context to the user, but the generated text should never be provided in a way that replaces reading the original wiki text. If the specific search makes it convenient, parts of such wiki text (including their external references) could be provided verbatim in the response, in a way that it's clear to the user that the shown text comes directly from the wiki.
About but people who desperately want to use AI won't won't a simple implementation: sincerely, I think that most people who desperately want to use AI don't think too much about this: for them, if it's AI, it's fine. And I believe they are a really large number of people. MGeog2022 (talk) 12:35, 8 November 2026 (UTC)
I mean if you are just using the sources from the AI overview and the source is reliable, it would be fine. The problem with ai overview from Google is that sometimes they don’t provide sources that are reliable. So in theory, the Wikipedia ai could be more reliable if trained on reliable sources for Wikipedia. Saint Bukno (talk) 02:28, 9 November 2026 (UTC)
As I said the more simple the implementation the better, as it would be less prone to hallucination or inaccuracies. It's the unbolded "and for providing context to the user" that I fear will be the problem. We will just have to disagree that those looking for a LLM type response will be happy with a limited response that mostly just point to articles for further information, I just don't think that will be what they're looking for. -- LCU ActivelyDisinterested«@» °∆t° 13:14, 9 November 2026 (UTC)
Now that JPxG has joined the conversation (no need to ping here), I'd like to mention that The Signpost'sRecent Research on 1 November is relevant here. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 23:35, 1 November 2026 (UTC)
Note that Chaotic Enby has already mentioned about this here, though this link is to share the latest updates to the Semantic Search project. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 14:27, 12 November 2026 (UTC)
Hi, I've started sketching out this essay as I see we don't really have any advice pages for ESL/EFL editors, and a large amount of the cases AINB gets are editors using LLMs to compensate for a lack of fluency. Ofc it's a sensitive topic (as any issues to do with competency are), and having something carefully and considerately worded would be so useful. Would be interested in hearing people's thoughts, especially what people have found useful themselves. Thanks Kowal2701 (talk, contribs) 19:33, 23 October 2026 (UTC)
WP:NOLLM already allows for machine assisted translation… although Editors who use such assistance still need to review it to make sure the program is translating accurately. Blueboar (talk) 20:07, 23 October 2026 (UTC)
(WP:LLMT is only for translating from other language Wikipedias, not for translating normal edits) Kowal2701 (talk, contribs) 20:23, 23 October 2026 (UTC)
I was referring to point 1 in WP:NOLLM, which states: “Editors are permitted to use LLMs to suggest corrections to their own writing, and to incorporate them after human review. This is limited to spelling, punctuation, capitalisation, grammar, and other simple mistakes.”Blueboar (talk) 21:34, 23 October 2026 (UTC)
CIR can be a bit scary to mention, but something like "ask more fluent users if you're unsure"? One way or the other, false confidence in one's own competence is a dangerous friend, and I've had more than my fair share of improper Gallicisms when learning English. Chaotic Enby (in solidarity · talk · contribs) 21:06, 23 October 2026 (UTC)
Good idea. I responded at Talk. Mathglot (talk) 21:45, 24 October 2026 (UTC)
I hope my reply isn't so late that nobody will read it. I've seen a few users, after apologising for their English or saying they used AI to fix their grammar, be told that if their English isn't good enough they should try editing their own language's Wikipedia but in all of these cases that I've seen (though I haven't seen that many) their English was perfectly comprehensible. The essay might even be more useful as a reminder to maybe say something like "but your English seems good enough to me" when pointing people to their native Wikipediae.
I don't know what the minimum standard is for English competency is on the 'pedia but I think as long as it's comprehensible native speakers can fix non-native grammar far more quickly than they can plausible, seemingly-sourced hallucinations. As Chaotic Enby said, assessing one's own skill in a language one doesn't speak is unreliable, but I think the essay shouldn't be too discouraging to those who aren't sure if their English is good enough since we could get more constructive editors (and less AI users) and the few who are actually incomprehensible can be easily dealt with. Wicker Mode (talk | contribs) 16:05, 26 October 2026 (UTC)
Totally agree with your first sentence in ¶2. I don't know what the standard is either (and maybe that should be addressed in a guideline) but imho it should be something like, "Any native speaker can understand unambiguously what you meant, so that they can adjust it to a native English standard." A possible problem there, is the number of native English speakers who write ambiguously and might get caught up in the guideline. Otoh, maybe they should be. If worded carefully, a guideline might address English competence while avoiding any mention of native language or second-language speakers, and just apply to everyone equally.
Reminder to self: once the essay is mature, we should consider linking to it from {{Welcome-foreign}}. Mathglot (talk) 17:36, 26 October 2026 (UTC)
Agree with focusing on English competence more, with native/non-native status as a special case. Many non-native English speakers have a native-like fluency in the language, and we wouldn't want to stigmatize them with a blanket assumption that non-native speakers are necessarily less capable. Chaotic Enby (in solidarity · talk · contribs) 18:11, 27 October 2026 (UTC)
Agreed. A fluent English speaker engaging in a topic with unfamiliar jargon could run into the same sorts of LLM-fluency challenges. Not sure how to word that off the topic of my head though. CMD (talk) 22:48, 27 October 2026 (UTC)
Thanks to everyone for their input, I've made a start on the essay, thoughts? I'm not sure what exactly to put in the two subsections, I'm particularly useless for advising about translation software Kowal2701 (talk, contribs) 22:30, 5 November 2026 (UTC)
@Kowal2701, thanks again for inviting me to this discussion! I have some thoughts to share for the WP:ESLAI section:
Editors may find AI writing tools useful for assisting them in writing content, and this is permitted. However, caution is strongly advised….
I'm afraid that this first sentence can mislead readers from the very start and trigger more AI noticeboard cases like mine. That was my own misunderstanding: I sincerely believed that I was very cautious with AI writing tools until we discussed my workflow, and I saw in practice how AI-assisted writing can influence the external perception and internal meaning of content.
I believe we need more direct guidance here and openly admit that AI tools are not permitted for writing content on Wikipedia. So, I would suggest more cautious wording. I have tried to incorporate all the points from your initial text in the WP:ESLAI section, make it more straightforward and simpler in structure, link it to other relevant guides, and add the ideas from @MSK and @Gurkubondinn that really touched me.
Here is the result for your consideration (I hope some of this will be helpful in your Wikipedia:AI_noticeboard discussions):
Editors may find AI tools useful, but their permitted use is very limited on Wikipedia, and there is a good reason for that. English Wikipedia's AI policydoes not allow the use of LLMs to generate or rewrite content on Wikipedia. This applies not only to articles but also to discussions.
Possible scenarios for AI tools on Wikipedia:
Preliminary search and study of sources, considering that editors will read the selected sources on their own (see WP:LLMRESEARCH). AI-assisted translations and explanations can help editors understand selected fragments of sources that cause difficulties due to unfamiliar vocabulary or a lack of subject knowledge (see WP:LLMTRANSLATE).
Suggest corrections to human-written content, but limited only to spelling, punctuation, grammar, and other simple mistakes that do not affect the style or wording.
Translation of articles from another language's Wikipedia into the English Wikipedia, taking into account that without human review LLM translations can result in other policy violations (see WP:LLMTRANSLATE).
Unacceptable scenarios for AI use on Wikipedia:
Content writing or AI-assisted improvements in style and wording. Although simple corrections are allowed, it’s good to keep in mind that LLM-based writing tools like Grammarly or LanguageTool, in addition to fixing grammar and punctuation, may also "ensloppify" text (introduce LLMisms), which makes AI detectors like GPTZero flag it as AI. Moreover, relying on grammar checkers can also make it harder to develop writing skills.
Reviewing sources and using summaries instead of reading the texts yourself (see WP:LLMRESEARCH).
These limitations are caused not only by the potential content quality issues associated with LLMs (such as AI hallucinations/text–source discrepancies, promotional tone, and copyright violations), but also by Wikipedia’s mission itself, which is to collect human knowledge, not chatbots’ output. Without regular practice, it is impossible to improve English proficiency, and reliance on LLMs will prevent the development of language skills or even cause a decline in competence.
Another reason for the restrictions on LLM use on Wikipedia is the potential suspicion of other editors, who consider articles containing AI-generated content generally unreliable. The amount of effort needed to verify the text against its sources in this case (which can take hours for a substantial article) is far greater than the amount of effort needed to generate an article with AI, and this imbalance leads to the recommendation to avoid AI for prose entirely.
It's better to have some grammatical or spelling imperfections than to cause suspicion and make other editors spend hours on verification because the prose contains AI signs.
If you are unable to contribute without heavy assistance from AI tools, you may find it easier to contribute to Wikipedia… (your current text follows as is)
That's it. I truly appreciate your feedback. And if any of this can be included into your essay, please let me know, I will be be happy to add it. Alexandra Goncharik-sms- 09:16, 16 November 2026 (UTC)
The 2017 wikitext editor as default source editor?
When you look at recent changes, about half of newer Desktop editors still use source editor . If you look at a language that has had VE as a default for longer , the percentage is only slightly higher. I don't quite understand why this is (maybe someone in @PPelberg (WMF)'s team can shed light, maybe the tags don't fully capture everything).
One way to make life easier for editors using source editor, is to enable the WP:2017 wikitext editor as the default source editor, which shows the VE toolbar on top of the source editor. The biggest advantage is that adding sources and reusing sources is much much easier. In the 2010 editor, there is a small 'cite button', which requires editors to know to click 'templates' next, and then select the right templates, before being overwhelmed with options. In the VE toolbar, it's often as simple as copying the url in the toolbar. The biggest disadvantage is speed, even though I'm not experiencing any trouble editing big pages with it.
In reviewing G15s, I often come across editors that make a claim they're just using AI for formatting reasons only. Not sure what share of these claims is true. To prevent the need for formatting help, we should make editing easier (the carrot). On the 'stick' side of things, the editing team believes it's possible to implement paste check in the 2017 source editor (see related wish). That likely is only worth their time if we are willing to make the 2017 editor the source default in some way.
I'm considering opening an RfC with four options:
Keep the 2010 wikitext editor (current default)
Make the 2017 wikitext editor the default source editor for non-EC editorseditors who are not extended confirmed at the moment of the switch
Make the 2017 wikitext editor the default for all editors
Make the 2017 wikitext editor the default for non-EC editors conditional on Paste Check being developed.
There's other options, like making it the default only for new editors, but since it's a smaller change in interface and I'd like to capture a bigger group with easier editor, my intuition is to make the RfC a bit bolder. Keen to hear opinions. In solidarity, —Femke (talk) 🐦 08:45, 24 October 2026 (UTC)
Please also provide an option that says: Do nothing, leave things as they are. I would support that. Thanks Yesterday, all my dreams... (talk) 10:48, 24 October 2026 (UTC)
That's option 1:). I've clarified the text. What makes you prefer option 1 even for newer editors? In solidarity, —Femke (talk) 🐦 11:18, 24 October 2026 (UTC)
Femke, first please let me perform a type of Wiki-heresy by asking you what an Rfc may be. It is, of course, a limited form of an Argumentum ad populum. Secondly let me point out that you are not a new user and your guess about what new users might prefer is exactly that: a guess. Most of those participating in the Rfc are also not new users. They will be guessing of course. Rfcs can be very useful in deciding on the reliability of sources or NPOV issues, but not newcomer expectations. When it came to data analysis I used to tell people: ask yourself "what would John Tukey do?" In this case, would he rely on an experiment or not? You know the answer: you need an experiment not guesswork. Please try that first. Thanks. Yesterday, all my dreams... (talk) 18:18, 24 October 2026 (UTC)
I've been asking for communities to get the ability to A/B test abilities ourselves (meta:Community Wishlist/W436), but the current state of affairs is that we cannot, and have to ask the Foundation for each individual test to be run. And with the teams at the Foundation having their own priorities, it is not always possible to get these requests turned into action. So we need to use some commons sense, and collectively think of plausible advantages and disadvantages, and only A/B test where it is unlikely we can make a good guess after discussion.
As an aside, I find your comment rather condescending; please assume people are aware of basic principles of design. In solidarity, —Femke (talk) 🐦 18:49, 24 October 2026 (UTC)
Sorry, but rule number 1 says: make no assumptions. Anyway, I will say no more, so as not to upset you. I have said all I needed to say. Bye bye. Yesterday, all my dreams... (talk) 20:12, 24 October 2026 (UTC)
I would support making the 2017 editor the default for all editors. ThadeusOfNazereth(he/him)Talk to Me! 16:30, 24 October 2026 (UTC)
Support for option 3. EC-editors who don't like the 2017 wikitext editor should be experienced enough to chose their preferred editor themselves, so it is not important which editor is default for them. Lova Falk (talk) 16:43, 24 October 2026 (UTC)
@Lova Falk: this is not the RfC itself, but the discussion about what the RfC should say:). In solidarity, —Femke (talk) 🐦 16:53, 24 October 2026 (UTC)
Ah okay! Lova Falk (talk) 18:29, 24 October 2026 (UTC)
Option 4 is way too conditional. My idea of "option 4" should be this: "Make 2017 wikitext editor the default for logged-out editors".
My idea for Option 5: "Make 2017 wikitext editor the default for non-(auto)confirmed editors" —George Ho (talk) 17:32, 24 October 2026 (UTC)
I don't believe it's likely people would want to split the group of new editors into two (logged-out vs new accounts). That would make updating all our documentation a pain. I can see people wanting a conservative option and only enable it for nonconfirmed editors. In solidarity, —Femke (talk) 🐦 18:53, 24 October 2026 (UTC)
I doubt that trying to split based on extended-confirmed will work out. As soon as someone reaches EC, suddenly their editor changes?Overall, I think you'd have better luck asking for a change that affects TAs and any accounts registered after the change, rather than proposing changing the default for everyone and (if it goes through) having a flood of complaints come in from people who missed the RFC and like their current editor. Anomie⚔ 19:16, 24 October 2026 (UTC)
My idea is to switch it once, for a group that is non-EC at the moment of enabling it, and not to give them the old software once they reach EC. This is a group of editors unlikely to be married to the idea of their editor, and likely to paste AI slop.
I often encounter very experienced editors who are unaware of the 2017 editor and prefer it, but I completely agree with the risk of a flood of complaints. And maybe it would need a temporary 'one-click' button to revert to the old wikitext editor to assuage these concerns. In solidarity, —Femke (talk) 🐦 19:51, 24 October 2026 (UTC)
I agree, the default should not change for anybody who registered before the change. I actually think a more useful change would be to make it as easy to switch between source editors as it is to switch between source and visual editing (and not temporarily either). Personally, I don't have a use for the 2017 editor as it sits in gap between the 2010 editor and visual editor that just doesn't exist for me. Thryduulf (talk) 19:56, 24 October 2026 (UTC)
I'd like to keep the overall options to 4 just to keep it simple, and might switch the 'new editors only' option in instead of the conditional option 4. Would that make sense, or do you believe that there is a group of editors who would mostly want this conditional on paste check being available in the source editor?
My preference is likely for the current option 2, as we desperately need to reduce editor's 'need' for LLMs by making editing easier, and rolling it out to new editors is an incredibly slow process. I'm surprised that we're only hitting 50% of new editors on VE a month(?) after enabling it. In solidarity, —Femke (talk) 🐦 20:05, 24 October 2026 (UTC)
The way to make editing easier for new editors is to present them with the visual editor first. I'm not convinced the halfway house of the 2017 editors has any value over that. Thryduulf (talk) 21:09, 24 October 2026 (UTC)
The problem is that a lot of new editors don't use VE, or are asked by LLMs to switch to the source editor. User:Toadspike and me flagged a couple of odd behaviours today to WMF that can lead to people being forced into source without their intent: e.g. if their first action onwiki is to 'Edit' on a talk page, it will remember their editor, and use source editor going forward. The VE-like 'Add topic' is not super prominent compared to 'Edit'. Even if they start off with VE, they will still encounter source editor in many places, as VE is not fully supported. Having the 2017 editor makes this a more smooth experience. You cannot edit completely without source, so to me, there is a value in choosing a modern source editor that feels intuitive. The default editor should stay VE of course. In solidarity, —Femke (talk) 🐦 21:48, 24 October 2026 (UTC)
are asked by LLMs to switch to the source editor There's little we can do about that, and VE will drop a user into whichever source editor is provided, so this is not a point in favor of using specifically the 2017 editor.
As recently as a few months ago, there wasn't even a way to add <nowiki> in 2017 WTE unless you already knew it existed. Izno (talk) 02:59, 25 October 2026 (UTC)
To me it's a small point in favour without paste check: llms dropping the user into an editor where they're not completely lost will make it more likely they'll try to edit themselves. The biggest difference would be if paste check were to be developed, so that we have that solution to AI slop in source too. In solidarity, —Femke (talk) 🐦 03:22, 25 October 2026 (UTC)
Thanks for the ping. A longer version: Clicking "view source" on any protected page, including the main page, most high-profile pop-culture topics, most templates or even Draft:Example, switches the user's default editor to source. Weirdly, though, this doesn't seem to happen with noticeboards, like AIV or ANI, or user talk pages, which also default to source editor. Seems to specifically be the "view source" button. Toadspike[Talk] 11:45, 25 October 2026 (UTC)
Not sure what I did wrong yesterday with testing, but you're right that it's only the 'view source' that produces this. In solidarity, —Femke (talk) 🐦 12:06, 25 October 2026 (UTC)
I cannot replicate in template space. To me, it looks like it mostly happens for the three namespaces where VE is enabled (user, draft, mainspace, but also the mainpage). I've opened phab:T442310. In solidarity, —Femke (talk) 🐦 12:28, 25 October 2026 (UTC)
I used to use the Wikitext 2017 editor but I found it made it impossible to edit on any mobile device on the desktop view. It would do this weird thing where it would offset all text selection like 4 paragraphs after where the text actually was. PARAKANYAA (talk) 19:57, 24 October 2026 (UTC)
That is really annoying. Did you open a bug report on phab? Do you know if that bug is still there? In solidarity, —Femke (talk) 🐦 20:06, 24 October 2026 (UTC)
No, though maybe I should have. I think it was probably a byproduct of how slow it was overall. PARAKANYAA (talk) 15:46, 25 October 2026 (UTC)
That smells like a CodeMirror (syntax highlighting) problem. WhatamIdoing (talk) 22:54, 3 November 2026 (UTC)
As someone who's used the 2017 wte, it is not ready to be the default source editor and may never be. It's always been slow, and it's not particularly friendly for mobile browsers on any given day. And basically, it hasn't been worked on since it rolled out to our general surprise in 2017. Izno (talk) 02:56, 25 October 2026 (UTC)
In terms of mobile: I was under the impression it was a desktop only editor? I don't see any toolbar when I'm editing mobile.. In solidarity, —Femke (talk) 🐦 03:03, 25 October 2026 (UTC)
@Femke You can go into the desktop view on mobile. I've done a decent bit of editing while out of the house this way. Normal source editing works totally fine, but 2017 lags to hell and back and has that weird error I mentioned above. PARAKANYAA (talk) 15:45, 25 October 2026 (UTC)
Yes, for a significant time I used Timeless while using mobile (Firefox browser on Android). It was routinely buggy at the time.
And remember, as always, that not everyone has got networks with our speeds or phones with our speeds. There needs to be a trivially accessed alternative for the masses that is actually faster than VE or 2017. Izno (talk) 06:35, 25 October 2026 (UTC)
I did a reasonable amount of outside-work-hours work on it over the last few months for the codemirror improvements (thus it having autocomplete built in for T432400 now), alongside which there've been a bunch of general VisualEditor performance improvements, so if you've not tried it in the last six months you might want to look again. DLynch (WMF) (talk) 20:32, 26 October 2026 (UTC)
@DLynch (WMF) I've noticed 2017 wikitext being considerably faster recently, thanks for your work! However when using Safari on long pages and with syntax highlighting enabled both 2017 wte and the reply tool still struggle a bit... Johannnes89 (talk) 09:46, 29 October 2026 (UTC)
I noticed the autocomplete stuff, but I haven't decided whether I like it. I want it to DWIM even better. WhatamIdoing (talk) 22:56, 3 November 2026 (UTC)
On the question of stats:
If you use the Undo button on desktop, you use the 2010WTE no matter what your settings are (2003 if you have Javascript turned off).
I wasn't sure whether I was using the 2017 editor already and had to review my preferences to figure it out (I wasn't). I've turned it on now and will see how it goes for a bit.
What I recommend is that the text editors identify themselves when you're using them so that users can understand the alternatives better. Currently, I'm aware of at least four different editors now.
1. The current default text editor which seems to be a 2010 version
2. The 2017 text editor, as proposed, which has some relation to the Visual Editor
3. The Visual Editor proper
4. The editor which is invoked when you use the reply function (which is what I'm currently using).
I wouldn't be surprised if there are other editors out there too. Ideally these alternatives should be rationalised and simplified but, in the meantime, we need help in understanding which one(s) we're using.
All the editors are listed with a brief description at mw:Editor, there are currently 16 current editors although some are very specialised (e.g ContentTranslatoin), some are mobile only (e.g. iOS app), and not all are available at en.wp (e.g. Wikivoyage Listing Editor). Thryduulf (talk) 19:03, 25 October 2026 (UTC)
Thanks. My count of that table is 17 plus 2 deprecated editors. See feature creep and the KISS principle... Andrew🐉(talk) 19:34, 25 October 2026 (UTC)
The basic distinction is that the 2017 editor is editing wikitext but using the VE toolbar. Sdkbtalk 21:06, 26 October 2026 (UTC)
One problem with the 2017 editor is that it breaks with any edit window that prefills something. For some of those, such as requesting at WP:PERM, it only makes it impossible to add an edit summary, while in other places, such at at WP:AINB, it is not really possible to file a report. 1brianm7 (talk) 19:06, 26 October 2026 (UTC)
I don't love the 2017 editor. I think the current one works just fine. Axolitl(talk|contribs) 05:11, 29 October 2026 (UTC)
What would you like to see improved in the 2017 editor, @Axolitl? In solidarity, —Femke (talk) 🐦 07:47, 29 October 2026 (UTC)
I like the proposal. It might nudge the WMF to make further improvements to 2017 wte:) --Johannnes89 (talk) 10:09, 29 October 2026 (UTC)
I am sorry, but from what I have seen the 2017 editor will come back whenever the DMC DeLorean gets revamped as an electric car and becomes popular. We should let both of them rest in peace. Thanks. Yesterday, all my dreams... (talk) 21:38, 30 October 2026 (UTC)
It is software, and can always be disabled one way or another. When there is a will, there is a way. Yesterday, all my dreams... (talk) 11:05, 13 November 2026 (UTC)
Sign me up! As a user of the 2017 WTE myself, I would very much support this in the RFC. Even if it doesn't become "default", there defiantly should be more "promotion" of the 2017 WTE, which could be in a tooltip in the editor such as Tired of manually filling in citations but don't like the visual editor? Try the 2017 Wikitext editor, which allows you to add citations just by pasting the URL, ISBN, or DOI!Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 13:32, 12 November 2026 (UTC)
Re: "2017 WTE is laggy", could it be due to CodeMirror syntax highlighting? Disabling that really makes the 2017 WTE more responsive. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 14:27, 12 November 2026 (UTC)
But the 2010 editors with CodeMirror isn't laggy, and I'm much rather have syntax highlightiing and other features like collapsing refs than a fancy new menu bar. --Ahecht (TALK PAGE) 18:03, 12 November 2026 (UTC)
I don't know why CodeMirror is laggy on the 2017 WTE but not the 2010 WTE. Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 00:04, 13 November 2026 (UTC)
Separate question: what does the 2003 WTE look like? Hason-LEK-SIN ● 💬 ● 🧱 ● 🧪 00:05, 13 November 2026 (UTC)
PREDICTION: This discussion will turn into quicksand sooner than later. No resolution is in sight. Yesterday, all my dreams... (talk) 11:10, 13 November 2026 (UTC)
Category vs ontology
There is a discussion above here which in my view has a valid point, but is accused of being LLM generated, and has become chaotic. I think it deserves a better hearing. May I suggest the use of an Ontology (information science) system to supplement categories, and in a visual mode as the IP suggested? I think a good deal of it can be automated without LLM usage. Personally, I would like to see that. Thanks. Yesterday, all my dreams... (talk) 23:52, 30 October 2026 (UTC)
Wikidata is a very solid first step at an ontology, with most Wikipedia articles already linked to items embedded there in an ontology structure – maybe surfacing these connections more explicitly on-wiki could help? There's been a long debate over how much we should or shouldn't rely on Wikidata for in-article information, but higher-level aspects like an ontology map are exactly what it is suited for, and that kind of integration could be amazing for navigation. Chaotic Enby (in solidarity · talk · contribs) 12:51, 31 October 2026 (UTC)
Well, I do consider Wikidata very useful data source. What it needs is a "visual" ontological interface. I would like that as user. Yesterday, all my dreams... (talk) 13:26, 31 October 2026 (UTC)
Not much of an "accusation", looking at it it's very clearly LLM-generated. On the topic, this is sort of what categories and navboxes are meant to do. Categories take you up and from there further up or sideways and down. Navboxes can take you in all sorts of directions. Navboxes in many cases are literally an "optional collapsible panel". What the llm missed is that these do exist on the articles, but with some caveats. These tools do not exist on mobile (meta:Community_Wishlist/W225 running now if people are interested), which is where most readers are. Further, when they do exist they are at the bottom of the page. Visualising these would be fun, the immediate challenge is how to allow it to be comprehensive without being bloated. Articles are complicated beasts, with many connections. Knowledge is not a simple hierarchy. We have WP:CATDEF and WP:BIDIRECTIONAL which do their best, but creating a visual space is going to need to be tighter as categories and navboxes have some flexibility (being a simple list and being individually collapsible) that a single visual interface may not. CMD (talk) 13:34, 31 October 2026 (UTC)
There should never be more than 12 nodes on the graph. But having it will get very useful. There has been much research on multi-level lattice generation frtom data, from what l can remember from long ago. But I have to be off now in RL, sorry. Yesterday, all my dreams... (talk) 13:43, 31 October 2026 (UTC)
mw:Extension:RelatedArticles does something like this (an unranked list of articles on related subjects at the end of the page – basically pre-loaded search results), but it wasn't wanted here. WhatamIdoing (talk) 23:09, 3 November 2026 (UTC)
Thanks all, and thanks to Yesterday, all my dreams... for giving it a fresh thread.
Yes, I used AI to write the first post. I do that openly and on purpose. I work with a group of four different LLMs (I call it a fieldmind), not just one, and I check what comes out. The idea itself is mine, and the help I’m offering is free.
Schazjmd asked for a mock-up, i made one for a small set of physics and maths articles but it's html how to supply?]
From the feedback, I’d change it like this:
drop the Vital Articles levels, since several of you said they’re arbitrary
focus on “read this first”, plus broader and deeper links, capped at about 12
allow several parents
pull the structure from Wikidata rather than inventing a new system
make it work on mobile first, since that’s where categories and navboxes don’t show (see W225)
StarryGrandma’s point that foundation articles are often just as hard is the big one, and I don’t have an answer to it yet.
Take it or leave it. If anyone wants to build on it, I’m happy to help. ~~~~GrantE1900 (talk) 16:35, 6 November 2026 (UTC)
Comment: The vital article levels are a imperfect, however levels 1 and 2 are pretty solid, and levels 3 and 4 are getting better. Level 5 is still sorting itself out, and is basically a filter for the higher levels. The Wikiproject importance levels are completely arbitrary and have very little discussion, for something to have passed to level 3 on vital articles it had to have significant discussion. GeogSage (⚔Chat?⚔) 01:05, 14 November 2026 (UTC)
As I said above, it is pretty hard to know how arbitrary they are until the ratings become subject to "consensus"... Did I say consensus? Yes, the missing element in all of this. Yesterday, all my dreams... (talk) 05:24, 14 November 2026 (UTC)
Sorry, but you should preface that with "in my experience" given the sampling issues involved with millions of articles. My feeling is that I have no idea how solid or liquid they are, given that issue. Yesterday, all my dreams... (talk) 05:18, 14 November 2026 (UTC)
Sure: "In my experience", as someone who has assessed something on the order of 20,000 articles over the years, and worked with the Wikipedia:WikiProject Council for nearly 20 years, and helped the Wikipedia:Version 1.0 Editorial Team maintain and explain their scale, it's not actually "arbitrary". It's instead specific to each group's views, which is not the same as arbitrary. Just because it looks to someone else like there's no rhyme or reason to it does not mean that there is actually no rhyme or reason to it. WhatamIdoing (talk) 18:16, 14 November 2026 (UTC)
I am sorry, but I am pretty cautious when it comes to sampling issues. Please divide 20,000 by 60 million and you will know the percentage of articles you have assessed. And I am pretty sure your sampling was not uniform. Personally I have never even read a single article about advanced biochemistry because I can hardly spell that word. The story of large data is that people wonder around in a small corner of a huge jungle and think they have seen it all. They have not. Sorry. Yesterday, all my dreams... (talk) 10:36, 15 November 2026 (UTC)
The quality assessment scale only applies to articles, of which there are 7.2 million, rather than 60 million.
The underlying question is whether I have enough practical experience and theoretical knowledge to know how it works. I think I do. The relevant comparison isn't the percentage of articles assessed; it's whether I've done more than most. Something like three-quarter million registered accounts made an edit last year; something on the order of 10 of them have assessed as many articles as I have. If you can't trust me, then I suggest that you find one of those other few and ask them. There are only a few thousand possible candidates, so I'm sure you could find them. WhatamIdoing (talk) 07:36, 17 November 2026 (UTC)
First, sorry, 60 million is for all languages, 7 million for English. Secondly, how many times do I have to tell you that I consider you and Actively the best two editors around? Do you need that written on paper, signed in blood? I even asked both of you to become admins but you would not go for it. So let us agree that I think you are very good, I trust your intentions and move on. But do I think that you are you always correct? As you know we do not always agree on that issue. Now, 20k in 7 million means you have looked at one out of every 350 articles. Please assume you walk into a warehouse with 350 products in boxes and asked to quality control them. Does checking one box tell us anything? No. And as I said your sampling was probably not uniform across topics. How articles did you assess on high energy physics? Proof theory? Computer security? And could you correctly assess those? The people who can assess those in any reasonable way will most probably be "hopeless" in assessing articles on advanced biochemistry, or histories of various ancient kingdoms. No one can fully understand even 10% of the topics in Wikipedia. So there will be no single user who can correctly comment on assessment quality. That is my point. Yesterday, all my dreams... (talk) 09:40, 17 November 2026 (UTC)
After typing this, I thought I would check an example. So I looked at proof theory. It is rated as B class, althiugh it has a citation tag atop. Do you agree with the B rating? I do not. To begin with it has lumped together the logical and computational topics in one article. They are very different. Please see what the Stanford Encyclopedia says. That is an excellent technical presentation of the mathematical issues but so hopelessly (and uselessly) long that will not help most users. And the Wiki article says almost nothing about the computational issues. So the B rating is way off and as far as I know there is no clean and "brief" coreect explanation of the subject anywhere. So my feeling about ratings is that they are mostly unknown items. Yesterday, all my dreams... (talk) 10:27, 17 November 2026 (UTC)
It is C-class. It's too long to be Start-class but there are multiple sections without any citations, so it can't be B-class. The mw:ORES system also says C-class (ORES overvalues length as a key indicator, though it is usually correct and is rarely off by more than one class).
Also, content assessment (and especially the priority/importance ratings) existing because of Wikipedia:Version 1.0 Editorial Team, which was originally English only, though they've tried to export it to French and Arabic with partial success. I've heard that French has about two-thirds of their articles assessed (at some point; assessment always lags behind reality); I don't know about Arabic. But AFAICT it's largely an enwiki phenomenon, and it's definitely not available at most Wikipedias. WhatamIdoing (talk) 16:32, 17 November 2026 (UTC)
Again, again, my apologies but we could not disagree more. If you assess articles based on length and the lack of section citations, I can not accept any of your assessments at all. Suppose all the sections had citations, would you assess it as B class? Have you ever studied proof theory? Have you read the Stanford Encyclopedia article? Trying to understand that long one as a start is close to torture. If that Wiki article had full citations it would be hopeless because it is incorrect from the start. The lede says it uses inductively defined data structures. That is not so. And as I said if has lumped mathematical and computational topics together. The real problem here, I am sorry to say, is that as they say: the more you have paid for a painting the harder it is for you to accept that it is a fake. With 20,000 assessments you will find it hard to accept that your assessments may be arbitrary. I will say no more on this. No more, no more. Yesterday, all my dreams... (talk) 17:17, 17 November 2026 (UTC)
Here's the criteria for Wikipedia:Content assessment/B-Class criteria. It fails #1; therefore it is not B-class. IMO there is no need to consider any of the further criteria. Note that the B-class standard ("The article is suitably referenced, with inline citations") is intentionally lower than the Wikipedia:Good article criteria. The GA standard is a minimum of one citation per paragraph; the most popular B-class standard is a minimum of one citation per section. Multiple sections of multiple paragraphs each without a single citation fails the B-class standard.
The Wikipedia:Content assessment/C-Class criteria, on the other hand, requires only the presence of "more than one reliable source", and being subjectively better than Start-class, aka better than "a usable amount of good content but is weak in many areas". In practice, the main subjective definition of "better" is the volume.
C-class originally didn't exist. Back in the day, the rule was basically:
shorter than 250 words/10 sentences (Stub),
too long to be a stub but still pretty lousy (Start), and
okay but not good enough for GA (B-class).
C-class was added as an intermediate step to divide the Starts that were barely too big for a stub from the Starts that were closer to B-class. Consequently, C-class is mostly defined by what it's not (not too short, not too lousy, not sourced enough for B-class), rather than what it is.
All of which is a long way of saying: I don't have to understand proof theory, or to agree with any particular definition of its scope, to tell you whether the article contains too many words to be a stub (yes), 2+ citations (yes), is "better developed in style, structure, and quality than Start-Class" (yes), but has too few citations to be B-class (also yes). C-class doesn't require compliance with NPOV; in fact, the C-class criteria directly state that an article can "contain policy violations, such as bias or original research" and still be C-class. If you wish to address the presence of inaccuracies in Proof theory, I suggest that you post a note at Wikipedia talk:WikiProject Mathematics or tag it with suitable Wikipedia:Maintenance tags; it has nothing to do with Wikipedia:Content assessment. WhatamIdoing (talk) 20:50, 17 November 2026 (UTC)
One editor doing thousands of assessments doesn't mean that it isn't arbitrary or that that editor is trustworthy in their assessments. Is Maps by Gerardus Mercator really one of the 750 high importance geography articles? . Very dubious, when e.g. the clearly more important Mercator projection is only mid importance for the same project. So yes, it is arbitrary, certainly for topics you seem to know less about (e.g. I wouldn't try to criticize your medicine importance ratings, as that is not something I know enough about). The idea that, just because you have assessed thousands of articles, you somehow are knowledgeable ernough about the importance of all topics for all projects, is laughable. That reasoning works for quality assessments, superficially, but not for importance. Fram (talk) 10:39, 17 November 2026 (UTC)
I have yet another concern about what I see as assessment of articles I have no clue about. I did not even know Mercator existed 10 minutes ago, so if looked at that and saw an assessment, as always I would wonder when it had been done. Articles can change a lot over time, and the assessment may be 7 or 10 years old. That is one reason I do not consider assessments as reliable. An obvious improvement would be to have the assessment date and the editor doing so added, with a link to the old version that was assessed. I hope a bot will do that one day. Yesterday, all my dreams... (talk) 11:30, 17 November 2026 (UTC)
Importance assessments shouldn't be too date-dependent in many cases (like here, geography), though they may change for more volatile subjects like, say, AI or computer gaming. Having the date for quality assessments may be useful. Fram (talk) 11:32, 17 November 2026 (UTC)
It would be difficult to retroactively add dates, because we restructured it a couple of years ago to provide (by default) a single rating for all groups, so that rating will have been "done" by the bot (and thus a WikiBlame-type search would find the bot's date instead of the original).
A possibly more useful approach would be to check them all via mw:ORES to see how many are wrong (off by 2+ classes). You can see one such check at m:Research:Screening WikiProject Medicine articles for quality/Stub prediction table. Anything that matches could be given an estimated good-as-of-year date, and anything that's off could be flagged for human review. All this assumes that we think the work is actually worth that many man-months of time, though, and it might not be. WhatamIdoing (talk) 16:39, 17 November 2026 (UTC)
I copied those ratings from Talk:Gerardus Mercator (=the article that content was split from). I encourage all WikiProjects to keep an eye on their top- and high-priority categories, because there are occasional problems with new editors changing the assessments either because they're fans (Chris Celebrity is always the most important!) or because they think that will trick editors into improving the articles (if I mark it 'top', it'll be at the top of all the work lists, right?). WhatamIdoing (talk) 16:36, 17 November 2026 (UTC)
Please don't assess articles like this, it is a very poor way of doing this (and definitely not something to brag about in a "look how many I have done" way. You dismissed a reply because " it's not actually "arbitrary". It's instead specific to each group's views, which is not the same as arbitrary." when you are not really part of the "group" (the project, you mean?) and your rating is simply copied from a general article to a less important subarticle, making it, yes, completely arbitrary. Fram (talk) 17:04, 17 November 2026 (UTC)
This rating may be wrong, but since it has a defined, reasoned provenance, it's not arbitrary. Arbitrariness, as our article says, is 'the quality of being "determined by chance, whim, or impulse, and not by necessity, reason, or principle".' It was not determined by chance, whim, or impulse. It was not chosen by necessity, either, but it was chosen by both reason and principle. The main reason I chose that category is that this content had previously been tagged this way by that group, so while it might not be perfect, it was likely close to their desire. My second reason was that Wikipedia:WikiProject Maps/Assessment#Importance scale says "High" topics "Must have been influential", and there were few maps in the world more influential than Mercator's. The principle behind my choice was deferring to whatever that group had chosen, without imposing my own view on whether the map content was "less important" to them than the biographical content. Given that Category:High-importance Maps articles has more maps than biographies in it (just 10 biographies, which is less than 5% of the high-rated articles), I don't think it's necessarily safe to assume that the group would rather the biography higher than the maps. WhatamIdoing (talk) 21:07, 17 November 2026 (UTC)
Your reasoning is so wrong that it might as well be considered an arbitrary assessment. A subtopic will rarely be as important as the main topic, and a spinoff is by definition a subtopic. Please also reply to what I wrote, I was talking specifically about the geography project, which is a much larger topic than the maps project. The list of maps of Mercator is not of high importance for the totality of the geography project. Like I said, please don't add such assessments to articles, it's much better to just leave them as unassessed and let knowledgeable people decide this. Fram (talk) 22:03, 17 November 2026 (UTC)
Adding research check boxes for AfD Proposals
Hi all. Nominating an article to WP:AFD requires that nominators complete WP:BEFORE. The section titled If proposing deletion and the main concern is notability, search for additional sources is often overlooked. When a nominator opens the dialogue box to nominate an article, there is a line that says (Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL) with links to these resources. I propose that these links become check boxes that a nominator must tick to show which of these resources they have consulted prior to nomination. I believe this would help the nominator become more aware of WP:BEFORE, potentially cut-down on the nomination of articles on notable subjects, and redirect potential nominators to improve those articles using the resources they find. If the nominator finds no usable references then, of course, the nomination to AfD could continue as normal. Thank you for reading. H0n0r (talk) 10:56, 31 October 2026 (UTC)
Good idea! Lova Falk (talk) 11:04, 31 October 2026 (UTC)
Is WP:BEFORE policy or a requirement? Is checking those specific resources required by a policy or guideline? ElKevbo (talk) 15:15, 31 October 2026 (UTC)
@ElKevbo Good question. I read "please be sure to" as a requirement. H0n0r (talk) 15:42, 31 October 2026 (UTC)
Wikipedia:Articles for deletion is an untagged process page, not officially designated as a policy or guideline. My sense is that it does reflect broadly accepted recommendations and expectations. As I note below, the minimum reference search requirement is spelled out later in the section. It does not include all of the searches listed above. —Myceteae🍄🟫 (talk) 20:18, 2 November 2026 (UTC)
WP:DILIGENCE lists the the minimum search expected as regular Google search, Google News, Google Books, and, for academic subjects, Google Scholar. This would represent a substantial increase to the minimum expectation. —Myceteae🍄🟫 (talk) 20:15, 2 November 2026 (UTC)
Most of my wiki editing is not done through the web interface. I don't have a sense of how common that is. But in that case, how will someone not using Twinkle (which I assume is the dialogue box you're talking about?) indicate what sources they have or have not checked?
Also, some of the sources included in there aren't something everyone is expected to have access to. I do not have a JSTOR subscription, and I do not have access to TWL (although maybe someday?). If the process is going to record that I did not search those, I'd like for it to reflect that they weren't searched for lack of access and not just because I couldn't be arsed. Packrat3860 (talk) 20:42, 2 November 2026 (UTC)
@Packrat3860 @Myceteae I don't think the intent here is to say "you must check in all these sources" (checking JSTOR for an article about say a figure skater or model of charabanc would be a waste of time). Rather I think the intent is to explicitly state which of those sources you did consult, with the expectation that it would be at least one of them.
I guess some equivalent to the checkbox could be added to Twinkle, but I don't use that tool and am not a programmer so I may be wrong. Thryduulf (talk) 21:33, 2 November 2026 (UTC)
Ah, I may have misinterpreted the scope of the proposal here. It would be good for @H0n0r to clarify. Encouraging better practices and streamlining documentation is one thing I might be in favor of, but not increasing the expectation/"requirement". Even if the goal is just to encourage, we should be thoughtful of downstream effects and unintended consequences, such as editors assuming that each and every one of these source searches/databases must be consulted for every AFD nomination because they see this as standard documentation. —Myceteae🍄🟫 (talk) 22:50, 2 November 2026 (UTC)
(edit conflict) Yeah, I could get behind a requirement to explicitly document what you did as part of your BEFORE (or at least which sources you looked at) but I don't think mandating (or giving the impression of mandating) which specific sources much be used is a good idea. Even "Google" is problematic, as not everyone uses that search engine (for various reasons) and although at least most people wouldn't think badly of someone ticking that box if they actually used DuckDuckGo or whatever but it could cause issues if Google puts a good source on page one but DDG doesn't see it and someone then does use Google and accuses the nom of lying about doing a search. Thryduulf (talk) 23:10, 2 November 2026 (UTC)
@Thryduulf, @Myceteae, @Packrat3860 thanks for reading this proposal. I certainly don't mean to mandate anything that's not mandatory at all, and propose no increase the expectation or requirement for anything. This idea is to make the minimum requirements of WP:BEFORE visible and have the nominator report what WP:DILIGENCE they have completed before nominating. Currently, it is common for nominators to state in their nominating statement only that the article has weak references. I believe a "check all that apply" approach to diligence reporting could help with this, and cut down on the work done by participants in the subsequent discussion. e.g., if I see that a nominator has checked Google Books, or DuckDuckGo, or even JSTOR (the checkboxes included could be a wide range of options, with links) then I will know not to double that work and focus research elsewhere. Thanks so much again. This is really helpful to narrow down what I'm proposing! H0n0r (talk) 01:58, 3 November 2026 (UTC)
Google Search gives 'personalized' search results, so nobody should be accusing anyone of lying if their search results differ. WhatamIdoing (talk) 23:20, 3 November 2026 (UTC)
If what the nominator selects for where they looked for sources isn't recorded somewhere wouldn't it be difficult to tell if the change has actually done anything? If the folks who previously weren't reading WP:BEFORE simply ignore the checkboxes then it looks the same as if people are considering WP:BEFORE more thoughtfully. It would also be indstinguishable from someone like me editing the page through a different tool and not seeing the dialog at all. If the intention is a rather "pure" UI nudge then I don't have strong feelings about it other than to expect that it will frequently be ignored. Perhaps assuming good faith means we should assume that people will not work around something new in the UI to continue whatever they were already used to doing, but if AGF worked that way then we wouldn't need to nudge you into reading WP:BEFORE. Packrat3860 (talk) 23:07, 2 November 2026 (UTC)
@Packrat3860 Good questions, and I think AGF still works here. I don't think nominators are intentionally ignoring WP:BEFORE so much as they're not aware of it, or don't see it as a big deal as follow-up discussion doesn't typically inquire about it. I was hoping this checkbox reporting could become part of the nomination documentation. A note could be generated in a bullet point under the nomination stating that • user has checked X, Y, Z, and A for sources prior to this nomination. If the user checks no boxes then, • user has checked zero sources prior to this nomination. could be an option and will give participants a heads up that research needs doing. Thanks for your feedback, and I'd appreciate any help thinking through the mechanics of this. H0n0r (talk) 02:08, 3 November 2026 (UTC)
Like Packrat3860, I think I could support a "nudge". I think it could help but it does have some serious limitations. One is that the worst offenders likely still won't follow or document having followed BEFORE/DILIGENCE. I assume that inexperienced editors are less likely to use tools like Twinkle. That said, if the nudge improves the even a small number of contributions it may be worthwhile. The other concern, which I mentioned above, is that if the standard documentation actually does catch on it may cause confusion about what exactly is required. Maybe this is a more remote possibility but if editors grow accustomed to seeing certain templated documentation, they may erroneously think the all nominations that omit this are improper when some are perfectly appropriate. So, I would say I'm lukewarm on this proposal. I have no strong objection but some concerns and some skepticism about its potential positive impact. I'm happy to be proven wrong about this. —Myceteae🍄🟫 (talk) 19:51, 3 November 2026 (UTC)
I wonder if what is needed is some rule for nominations along the lines of "You must note what research you have undertaken prior to nomination, it is best practice for this to include a list of where you have looked for sources."? Thryduulf (talk) 21:23, 3 November 2026 (UTC)
My preference would be to reform WP:NEXIST to reflect modern practice at AfC, requiring that sources demonstrating notability are in the article to qualify for mainspace. Thebiguglyalien (talk) 02:49, 3 November 2026 (UTC)
@Thebiguglyalien Should the BURDEN then be on the one nominating to perform that improvement? Otherwise we're giving them license to raze half the website without a second thought. PROD effectively performs half of the functions you're advocating here already.
Exempt articles that already exist prior to implementation. That's essentially how it works now with AfC, this would just extend the accepted AfC practice to directly-created articles. Thebiguglyalien (talk) 19:44, 9 November 2026 (UTC)
Or maybe we should require AFC to reflect the policies and guidelines, and therefore to pay less attention to whether an article's current state is "demonstrating notability", and instead make it clear that AFC reviewers are expected to move pages to the mainspace when the subject is notable, even if it's an WP:UGLY little article with too few sources to "demonstrate" notability. WhatamIdoing (talk) 01:39, 14 November 2026 (UTC)
For clarity, the changes that I think are needed in this respect is:
for nobody to yell at an AFC reviewer for being too lax/not sufficiently protecting Wikipedia from WP:UGLY articles, and
for AFC reviewers to be able to trust that the rest of the community will back them up when they take such actions.
In some cases (e.g., schools or other "local" subjects), it's valuable to search for the non-English name. A quick Google Search may find nothing on "Patriotic College" but many things on "爱国学院". WhatamIdoing (talk) 23:22, 3 November 2026 (UTC)
Which makes me think: What if we had a script that could open tabs to search? Tick the 'BLP' button, fill in the 'other/non-English names' box, choose your favorite search engines, and it opens half a dozen browser tabs for you to look through. WhatamIdoing (talk) 23:24, 3 November 2026 (UTC)
Terrible idea, maybe instead we should assume good faith that editors have done what's asked of them. If you believe an editor isn't aware of BEFORE then let them know and explain the situation to them, that will be far more beneficial that added WP:BUREAUCRACY. Talking with other editors is always better solution. -- LCU ActivelyDisinterested«@» °∆t° 15:41, 5 November 2026 (UTC)
@ActivelyDisinterested Assuming good faith doesn't mean it's acceptable to deny that bad faith exists. I can show you numerous instances where it was categorically proven that the nominator hadn't carried out a proper BEFORE (or any BEFORE, for that matter), which current policy allows them to get away with scot free, despite it being a serious abuse of ONUS and BURDEN. Look at it this way, if what you're saying was reasonable then we wouldn't have, nor even feel we'd need to have NOLLM. Are you of the mind to support effacing that as well?
I've seen innumerable instances of editor making bad faith comments about other editor's BEFORE searches, I see those as much more problematic than a few instances of actual bad faith BEFORE searches. AfD is all to often a toxic experience, and this will only make that worse. As with any misbehavioural issues in regards to ONUS, BURDEN, NOLLM or other policy or guidline if an editor is that much of an issue take it to ANI, rather than creating an entirely new process of tick boxes. -- LCU ActivelyDisinterested«@» °∆t° 20:45, 9 November 2026 (UTC)
I'd say that failure to do a (proper) BEFORE and bad faith comments about nominators are separate but equally problematic issues. BEFORE searches that are actually conducted but done in bad faith are a problem, but is again a separate issue.
Requiring nominators to (briefly) document what their BEFORE search entailed would have the side effect of reducing incorrect accusations against nominators as it will be much clearer what has and has not been done and it will also highlight any issues of people searching in clearly wrong locations (e.g. expecting Google News to be relevant to 11th century Japan or Lexis Nexis useful for a contemporary web phenomenon) in good or bad faith. Thryduulf (talk) 21:07, 9 November 2026 (UTC)
I think this is an excellent point. Even if we fix our lens solely on the Google slate that's currently recommended, there are occasions where it's obvious you're not going to get any hits from news, or Gbooks, but where you'd almost certainly see results if you checked something like JSTOR/Google Scholar.
Can I ask why you see that as more problematic? AfD becomes more toxic because people (particularly those fighting to keep content) feel that the system itself is unfair. The process as it currently stands is, at the very least, grossly unfair to those inexperienced with policy, which is a massive advantage held by most nominators to start. Clarifying guidelines fixes the problem you're describing, and toxicity is dealt with at ANI. If critical material that no one else is ever going to write about (at least for a decade or more) gets removed, that's irreversible, and that's where the resentment (that fuels the toxicity you're describing) derives from in the first place.
If your concern is that this toxicity would lead editors to quit who might otherwise have stayed, how is that any different from the editors who quit because they feel that the process is irreparable, and their voice is never heard? If we're going to grant as much leeway as we do to those advocating removal by measure of cold, obligatory policies like BURDEN, ONUS, etc., then we should make sure that the sparse guardrails in place to stop people from abusing them are measurably effective.
Because toxic behaviour is one major cause of our inability to retain editors, and one of the reason that even experienced editors are driven off. It should be the forefront of considerations, but is all to often ignored in favour of adding extra burdens to areas that editors dislike. -- LCU ActivelyDisinterested«@» °∆t° 21:12, 9 November 2026 (UTC)
If your concern is that this toxicity would lead editors to quit who might otherwise have stayed, how is that any different from the editors who quit because they feel that the process is irreparable, and their voice is never heard? If we're going to grant as much leeway as we do to those advocating removal by measure of cold, obligatory policies like BURDEN, ONUS, etc., then we should make sure that the sparse guardrails in place to stop people from abusing them are measurably effective.
This talk on the Human article I have been a part of has given me an idea: (Talk:Human#Use_of_males_and_females_as_a_noun_in_opening) shouldn't there be a clarification on how to use male and female when in relation to a species in the MoS? I could see someone both simply calling a male or female of a species "female" or "male" but I could also see someone calling a male or female of a species a "male (name of animal)" or "female (name of animal)". Just some thoughts. Ilov3gam3z (talk) 16:16, 4 November 2026 (UTC)
Maybe a small guideline somewhere? It just seems like an interesting question that needs to be answered. Ilov3gam3z (talk) 00:27, 6 November 2026 (UTC)
We don't need a guideline for this. —Myceteae🍄🟫 (talk) 01:45, 10 November 2026 (UTC)
Short answer: Nobody can agree on what the guideline should say. Importantly, "a female" is periodically considered derogatory or dehumanizing by cis women, with differences appearing by generation (e.g., Lost Generation minded, Baby boomers don't, Gen Z does...) and culture (e.g., considered more insulting by Black Americans).
Long answer: There's literally more than a million bytes in User talk:WhatamIdoing/Sandbox 4/Archive about this if you would like to have your faith in humanity utterly destroyed. WhatamIdoing (talk) 02:01, 14 November 2026 (UTC)
Look, I may disagree with you, but more the a million bytes? The hell? People care about this that much??? Insane. Ilov3gam3z (talk) 13:12, 14 November 2026 (UTC)
And we ended up there because a super long discussion elsewhere had reached such a size that that page was basically non-functional. Also, it's not the only such discussion. It might be the longest on a single page, but it is one of dozens or even hundreds. WhatamIdoing (talk) 18:26, 14 November 2026 (UTC)
My sense is that people who object to female in certain everyday contexts are less likely to be offended by it in a clearly biological context such as the usage at Human. —Myceteae🍄🟫 (talk) 03:26, 17 November 2026 (UTC)
Up and Coming Editor of the Week
I thought we should do something akin to editor of the week for up and coming editor. Here’s my questions before I take it to the proposals pump
How frequent should this be? Weekly/Monthly?
What would qualify as “up and coming?” A hard edit cap? Something more subjective?
How quickly something can get implemented depends on how much interest there is in it, and if those interested are willing to work on it as often as necessary to sustain it. Are you proposing that it be essentially a barnstar (much like Editor of the Week)? If so, you can work out a process with those interested and try it out to see if you can successfully keep it going. Note you don't need to establish consensus to hand out barnstars; just do it!
Regarding the broader question of recognition initiatives: some key questions are
What is the goal of the initiative?
What process can help achieve this goal without causing greater dissatisfaction amongst those not chosen? What degree of fairness needs to be incorporated into the process?
What process is sustainable, given the number of supporting volunteers and the amount of effort they are able to contribute? Be aware that many, many English Wikipedia initiatives start off with editors expressing interest, but then participation rapidly drops off to zero.
Doing some trial runs might help answer these questions. One suggestion I have: people appreciate specific feedback when receiving recognition, as it really helps convey gratitude, and it provides a positive feedback loop for specific behaviour. Good luck! isaacl (talk) 18:49, 4 November 2026 (UTC)
This would basically work the same as editor of the week, for new “up and coming” editors. The goal of the project would be to encourage and recognise new users who are doing well, much like editor of the week, and possibly fast track or shortlist them for extra permissions etc. I would be looking for editors who work at WP Editor Retention to express interest in setting this up, then people can nominate like they do for editor of the week Sunshinezguy (talk) 18:55, 4 November 2026 (UTC)
To be honest, you're going to be the best advocate for your idea, so I'd suggest you take an active role. That being said, fast-tracking someone for extra permissions is something that would require community consensus, and I just don't see that happening. Editor of the Week has been able to last as long as it has (closing in on 14 years!) because it's a low-stakes, no-big-deal, low overhead recognition. A process with actual stakes is going to be far more contentious to reach agreement upon. Minus the fast track part, your goal sounds like it is already covered by Editor of the Week. isaacl (talk) 19:29, 4 November 2026 (UTC)
No… it is not covered by Editor of the Week. That usually goes to experienced editors. This would be for new editors Sunshinezguy (talk) 19:32, 4 November 2026 (UTC)
To quote from the Editor of the Week page: The Editor of the Week recognition is intended to demonstrate appreciation of an editor's positive behaviours and collaborative spirit. ... Although editors of all levels of experience can be recognized, please consider nominating an unsung hero: someone less celebrated yet deserving of greater renown. Encourage typically unnoticed editors by giving them their day in the sun! It was deliberately set up to recognize lesser known editors. Experienced editors used to be explicitly precluded, but since some community members really, really wanted to recognize them with Editor of the Week (in spite of my attempts to convince them that there are many other ways to recognize them), this restriction was removed. Nonetheless, the recognition is still designed as an easy way to recognize new editors. isaacl (talk) 19:53, 4 November 2026 (UTC)
Alright. I swear I only see experienced editors recognised. It’s a shame. I think you’re right, I’ll retire this proposal. People will just keep moving the goalposts until Sir Amantio gets it every week Sunshinezguy (talk) 19:57, 4 November 2026 (UTC)
No one by that name's ever received the Editor of the Week recognition, and editors aren't eligible to receive it again with 12 month of having received it before. The goal posts are the same as they've been for years; please feel free to submit nominations for anyone who you feel has done worthy work that should be recognized! isaacl (talk) 22:56, 4 November 2026 (UTC)
It was just a tongue in cheek joke about User:Ser Amantio di Nicolao, who has the most edits, saying in general the award has been corrupted from its original purpose. Sunshinezguy (talk) 22:57, 4 November 2026 (UTC)
It's not an award that's won; it's recognizing good work that someone found worthwhile to shine a light upon. The initiative depends on nominators to find good work. I encourage everyone to find new editors to recognize. isaacl (talk) 23:43, 4 November 2026 (UTC)
Oh my bad using the wrong variation of an award. Look, you’ve picked all the holes in my idea. Shall we be done with this” Sunshinezguy (talk) 23:45, 4 November 2026 (UTC)
Pleasedo not archive. I will add comments soon TY. Buster Seven Talk (UTC) 18:22, 12 November 2026 (UTC)
The history of The EDDY award is very interesting in its scope and duration. Since Editor Isaaci and I have been there from the beginning, we may be a bit protective of the 650 or so recipients. We rarely decline a nomination and do only limited vetting to assure provenance. A list of recipients can be found at here which, I believe, displays the varied levels of participation from newbie to long-time veteran. As Isaacl suggests, feel free to find new editors to recognize. Currently there are 11 editors in line to receive the award which will stretch into the new year. As far as the award being corrupted from its original purpose, a visit to "recipient response" show something quite different Buster Seven Talk (UTC) 21:31, 12 November 2026 (UTC)
The current AFI (Frozen yogurt) was move protected a couple of days ago following vandalism. Move vandalism has every now and then also occurred on pages linked in other main page sections. For obvious reasons, the AFI is not protected from content editing, and that principle has generally extended to other main page items in line with our cautious wp:protection policy.
However, there seems to be little reason the considerations around protection regarding editor participation (with the AFI as the obvious example) extend to move protection. Articles mentioned on the main page will have been looked over by a lot of editors. If the articles go to WP:RM, that discussion will likely last beyond their appearance on the main page. Due to piping, their titles are not directly of issue to main page text if the main page text needs adjusting. In the very rare situation where a page might need to be moved immediately, that is what WP:ERRORS is for. With that mitigating any potential harm, the benefit is reduced disruption to one of the most visible parts of articles (and disruption that is a big more annoying to revert than simple content vandalism, in my experience).
If there is agreement that default move protection is beneficial, ideally such a system would work mostly silently and automatic way. If it is technically possible, perhaps like WP:CASCADE? Manually having admins protect everything would be too much effort. A bot would be possible, although that's a lot of log entries. As we generally avoid redirects on the main page, there should be minimal risk of an automatic process having 'move protection collateral' or misplaced targeting. So really two questions here, 1) would preventatively move protecting main page articles be a good idea, and 2) if so what would be the best way to do it? CMD (talk) 23:53, 4 November 2026 (UTC)
You can't do cascading move protection. It would have to be either manually done or done by adminbot. Anomie⚔ 00:36, 5 November 2026 (UTC)
Let's consider it a bot proposal then, as manual would not be a net asset on time. CMD (talk) 08:55, 5 November 2026 (UTC)
Thanks for the ping, I can probably implement this if/when there's consensus in an RFC.
I would be interested to see how much page move vandalism versus legitimate (non-reverted) moves there actually is for bold-linked articles on the main page in slightly lower sections like DYK, OTD, and featured picture/media. And how many see no vandalism at all. Do moves of actively developing things on ITN end up sticking or get reverted? Also whether extended confirmed protection would be sufficient. Legoktm (talk) 17:39, 7 November 2026 (UTC)
ITN is a mixed bag. Some moves stick, some don't and ottomh I'd hesitate to say which is more common. Thryduulf (talk) 20:38, 7 November 2026 (UTC)
I remember closing an RM for 2026 Ceuta migrant crisis, not realizing moving it would be an MPNOREDIR issue. It ended up being brought up at ERRORS, and temporarily moved back until a sysop could update ITN. Move-protecting it could be good in this situation, it would just be brought up at RM/TR then. Axolitl(talk|contribs) 20:31, 8 November 2026 (UTC)
I am not aware that move vandalism on the Main Page is an important issue these days. Same with WP:MPNOREDIR: while we want to avoid having redirects on the Main Page (unnecessary attack vector), they sometimes happen and are quickly fixed at WP:ERRORS. It is better to have a redirect on the MP for a few minutes than to keep a page at an unambiguously incorrect title in my view. —Kusma (talk) 17:10, 14 November 2026 (UTC)
Post-XfD Backlink Cleanup
XfDcloser is meant to automatically unlink items in normal prose and give admins the option to keep or remove list entries depending on selection criteria, but this function does not work properly in tables and certain other list formats where it simply unlinks the text. This has become an issue with geography lists and templates such as List of places in California (S), Template:Arzuiyeh County and List of cities, towns and villages in Khuzestan province where dozens of entries were unlinked or became redlinks as part of geostub cleanup efforts. My concern is that these items continue to propogate misinformation since many of them are not actually populated places at all.
I suspect that this is an issue across thousands of articles, so I'm hoping we can find a systematic way to identify and remove them as well as catch them at the time of deletion to prevent the problem from growing any further. I raised the issue at Talk:XFDcloser and received little interest in updating XFDcloser to handle these types of links or tag them for followup, so I'm looking for ideas from the community on how to find and clean up these lists. –dlthewave☎ 03:54, 12 November 2026 (UTC)
Yeah I lack the expertise to deal with this but it's a problem for Iranian village lists which are now often 50% red-links because of the Carlossuarez46 "village" issue. It does simply lead to the recreation of the article based on the same sourcing as we saw this year, which then have to be deleted again. Better if we just removed the links entirely. FOARP (talk) 10:07, 18 November 2026 (UTC)
I've been taken aback by the apathy from editors who do have the ability to fix this on the admin side. The admins who delete these articles use XFDcloser or Twinkle as they've been trained to do, and asking them to remove nonstandard list entries is seen as some huge new task despite being in all of the deletion process documentation. And the folks who maintain XFDcloser are reluctant to even flag them for manual followup since this would also impose more work on admins, even though it would just be a 5-second glance at a table and clicking "Unlink" or "Delete line". –dlthewave☎ 13:20, 18 November 2026 (UTC)
Programming a gadget to correctly differentiate from a table whose entries should be deleted (i.e. only notable wikilinks are allowed) vs a table whose entries don't have to be notable doesn't seem like an easy task to me. Nor does programming a gadget to pop up some kind of window for potentially a lot of pages and asking the admin to manually choose. Also, the act of editing wikicode tables to delete entire rows on tables that could be a variety of shapes (various rows, various columns, merged cells, etc.) without breaking the table is also not easy. If these were easy on the technical side, I'd be more willing to move forward. If I'm missing something and you see an easy way on the technical side to do this, please do share your idea. –Novem Linguae (talk) 14:03, 18 November 2026 (UTC)
Lol, "the folks who maintain XFDcloser", as if there were more than one active maintainer ... FaviFake (talk) 16:06, 18 November 2026 (UTC)
'Reply' tool improvements
After a query at WP:VPT, Deacon Vorbis proposed disabling the [reply] tool at WP:RFD, but most participants (including myself) were not supportive. See the discussion. However, all of us were in agreement that the current situation with the [reply] tool only providing colon (:) indentation is unsatisfactory and causes problems, so it seemed now would be a good time to raise this.
Context
The issue has been raised at Phabricator by the Japanese and Russian Wikipedias, but these tickets have gone neglected for years, being still marked as "needs triage".
It's my view that many users here and on other projects have been quietly putting up with the [reply] tools limitations rather than making the WMF aware that this is something we care about. At present, it seems nothing is being done and there are not even plans to do anything. The issue has been raised at Phabricator by the Japanese (2020: phab:T263902) and Russian Wikipedias (2021: phab:T276510), but these tickets have gone neglected for years being still marked as "needs triage". A related issue was raised at phab:T250127 (2020), also neglected. See also the WMF reply to the request from ~jawiki on MediaWiki (mw:Topic:Vu8z37woqb5eit3e). The most recent developments towards any sort of solution seem to be related to the development of a new tool specific for voting-style discussions (phab:T259865), but that seems to have stalled in some time around 2022~2023.
Community Wishlist?
Has a community wishlist petition ever been done on this? Would it help to raise the priority of either getting the [reply] tool improved or completing the development of dedicate voting-style discussions tool? Are the wishlists even still acted on after the community tech team layoffs? Or is it still limbo while they work on a new process? If a wishlist petition were made, where would it usually be appropriate to notify people of it (I'm particularly asking because ideally multiple different language Wikipedias would be notified of it since the demand comes from across projects)?
Other ideas?
Is there anything we can do to get things moving? Are there other ways or venues to try?
I was wondering if there was some recent improvement to the reply tool. The replies to the dummy comments in the LLM to Policy discussion actual seem to be going to the bottom. Was there a change? Dw31415 (talk) 18:11, 12 November 2026 (UTC)
@Dw31415: I don't understand. The replies have always gone to the bottom of the reply chain and are supposed to. Either way, we're at Village pump (idea lab) not WP:VPT or WP:Help desk. This discussion is proposing making improvements rather than discussing improvements which have recently been made (which, as far as I know, none have been and that's the problem). This regarding the inability of the [reply] tool to allow for indentations other than the colon (:), rather than other options, especially bullet points (*). – Scyrme (talk/solidarity) 18:30, 12 November 2026 (UTC)
I guess I never tried a dummy comment like in the link above until it showed up in the mentioned RfC so it’s probably not new. (I understand where I am thanks) Dw31415 (talk) 19:16, 12 November 2026 (UTC)
@Dw31415 I think there has been an improvement in the reply tool at some point because you can now format text in a reply using "nowiki" and/or "code", from a dropdown menu - lack of that used to be very annoying because often in a reply on a talk page I'm wanting to illustrate how something could be done. So that's a big improvement. (Alternatively, it was there all along and I was slow to notice that there is a dropdown menu beside the underlined "A"!) PamD 18:54, 12 November 2026 (UTC)
Thanks! I forgot about that one. I signed it back on 18 April 2026, but I don't think people were widely notified about it and the people who have signed are people I recognise as being active on the English Wikipedia, but not other projects which are also affected. – Scyrme (talk/solidarity) 19:23, 12 November 2026 (UTC)
Would help at all to start notify people now? Or is it considered stale/unlikely to succeed now that it's been more than 2 years since it was created? – Scyrme (talk/solidarity) 19:47, 12 November 2026 (UTC)
@Scyrme: It's not stale. There will be an advertised voting period in January for all the wishes submitted in the last few years, in this transition period back to a yearly submission and vote.
In addition, meta doesn't have a canvas policy, so, within reason, you are allowed to campaign a bit for different wishes (e.g. see my userpage, for wishes that I cared about 2 years ago). —Femke (talk) 🐦 12:43, 14 November 2026 (UTC)
Back to your original question. I think it would help to prioritize the list. I think there is a barrier given the scope of the wish to have the reply button fix (or ignore) editing mistakes (incorrect indents). My wish would be that level 3 headings on talk automatically get a reply button so that a dummy comment is not required. What’s your top priority? Dw31415 (talk) 19:46, 12 November 2026 (UTC)
Removing the need for an initial first message after a heading seems like a relatively minor convenience issue to me. It only affects very long discussions, and even then it's only a problem for the editor who adds the heading break (or whoever adds the initial comment if this was neglected). It doesn't affect anyone else once the initial comment has been left. If the discussion uses the bulleted-style, it's not a problem at all since the [reply] tool can't be used to leave a first-level response (because it can't add the first bullet point needed). Editors will still need to add their first-level response manually by editing the page. I'm also not sure adding a [reply] button to a heading would be the way to address the problem, since the reply would be indented with a colon, whereas you want an unindented first message. (Though I suppose it would work if the [reply] to a heading functioned differently than a [reply] to a message.) The [reply] tool having no way to modify how replies are indented is my priority. It very frequently causes problems with inconsistent indenting styles at venues like WP:RFD and WP:AFD. Besides making a mess, there are accessibility concerns related to MOS:LISTBREAK (though listed at WP:MOS, these guidelines are relevant to discussions not just article content). Many editors continue not to use the [reply] to because they prefer bulleted discussions, but this introduces increased risks of edit conflicts at busy discussions and also leads to editors inserting gaps to make the source code easier to read (contrary to the accessibility recommendations at MOS:LISTGAP). When discussions are already bulleted, newer editors often try to follow the style by adding a bullet in their reply, which results in their reply being indented twice. The [reply] tool is great for increasing participation and making joining discussions more accessible, but this has been undermined for years by its colon-only indenting, which discourages editors from using it and the impact of mixed indentation on screen readers. I support any solution that addresses the indentation problem. I don't object to fixing other things along the way. – Scyrme (talk/solidarity) 20:22, 12 November 2026 (UTC)
Thanks for elaborating. Here’s a simple/creative/crazy idea: Keep the reply tool as-is so that it always uses “:” but have a new render flag that renders one “:” as a bullet on pages with the flag. I suspect this would be far simpler than trying to make the reply tool context aware. I suspect that would help the accessibility as well. Dw31415 (talk) 20:34, 12 November 2026 (UTC)
I don't think that's technically feasible. Even if making single colons display as bullets is doable, for the MOS:LISTBREAK issues, the problem isn't just how it looks but is with the page HMTL. It would also cause problem if single colons were needed on the page for other purposes. The proposals at the Phabricator tickets seem like better directions to take. As I understand it, problem here isn't that there are no ideas for how to improve things. The problem is the WMF don't perceive the demand for continuing development to actually implement one of these suggestions. People quietly put up with it, so no-one says anything, progress stalls, and nothing gets done about it. (Or least this is the impression I get looking at the Phabricator tickets. Maybe it stalled for other reasons, but if so this doesn't seem to have been communicated.) – Scyrme (talk/solidarity) 21:02, 12 November 2026 (UTC)
Dw said 'a new render flag that renders one “:” as a bullet', in which case the colon would render as the relevant HTML that produces an unordered list, so what ze said should be very and accessibly feasible.That said, it should be even more feasible for the reply tool to detect whether other comments in the threads are using bullets and automatically adapt, or respond to the same kind of render flag (likely a magic word) Dw just mentioned to goddamnit-use-a-bullet. In solidarity, Aaron Liu (talk) 21:23, 13 November 2026 (UTC)
Whatever the solution is, the wikitext should match the display - a * should always display a bullet and a: always an indent. Thryduulf (talk) 21:31, 13 November 2026 (UTC)
Can you describe the method that should be used to detect bullets (I created this section to think it through: User talk:Dw31415#c-Dw31415-20261112185700-L3-1)? When I try to think it through it gets convoluted and complex quickly. Dw31415 (talk) 22:38, 13 November 2026 (UTC)
DT is already able to parse discussion threads into a nested list of distinct comments. If an entire comment within a thread uses * to start instead of:, then the entire thread should use bullets. In solidarity, Aaron Liu (talk) 21:27, 14 November 2026 (UTC)
I can see where the feature as exactly requested would give me pause if I were the tech lead. Maybe a little cleaner if it can be driven by a page level magic word.
As a related thing, I just created {{rb}} to facilitate replies to surveys and created a tread at WT:RfC#Adding reply button template to discuss it. Whatamidoing pinged the WMF PM in that conversation. Feel free to link back to here if we’re looking for an answer on why this has been so ignored. Dw31415 (talk) 21:52, 13 November 2026 (UTC)
What I would like would be to have the username of the person you are replying to automatically added to the front of your reply to make things clear. Yesterday, all my dreams... (talk) 05:39, 14 November 2026 (UTC)
Eew. That would make me stop using the reply tool. Or almost always delete it, if it's deletable. Anomie⚔ 14:35, 14 November 2026 (UTC)
Assuming we're talking about prepending "@Example" to the start of every comment, then that would definitely not be an improvement. For example in this comment I'm not replying to WAID, I'm replying to Yesterday, all my dreams... but I am following on from both Anomie and WAID starting an independent thread. Thryduulf (talk) 21:00, 14 November 2026 (UTC)
My friend, you just made me smile. You had to clarify who you were responding to here, because you did not have the checkbox I mentioned to Anomie above. And the item added can just be a text item, without a link, to clarify without over linking. Yesterday, all my dreams... (talk) 10:13, 15 November 2026 (UTC)
Please see my response above/below where ever it may happen to show with respect to this, given that I am not sure where this will be placed. Yesterday, all my dreams... (talk) 10:17, 15 November 2026 (UTC)
Anomie, I am sure you have heard of the rumor that there is something called the HTML <input type='checkbox' /> that could be placed next to the reply button, and the user name will be used only if that is checked. Please note that I had to use your name here given that I am not sure where my response will show up among those below. Yesterday, all my dreams... (talk) 10:09, 15 November 2026 (UTC)
Being weirdly condescending and feigning (I hope) incompetence isn't really helping your argument here. Anomie⚔ 20:25, 15 November 2026 (UTC)
Sorry, I forgot to take my anti-condescending medication today. As for incompetence, it has always been for real, despite my advanced academic credentials. I hope you will not consider that condescending. Yesterday, all my dreams... (talk) 20:44, 15 November 2026 (UTC)
Scyrme, one idea to generate interest in the wish list item might be to publish and informal poll on whether we should continue using * in deletes and RfC surveys or switch to : for all !votes. I'm guessing here but maybe the WMF folk think we're clinging to outdated ways and it might be good to take the communities pulse on it. Just another over-caffeinated idea. Dw31415 (talk) 15:55, 14 November 2026 (UTC)
(This guess is wrong. The Editing team just never got this bit done before they got reassigned to a different project. WhatamIdoing (talk) 18:30, 14 November 2026 (UTC))
An RfC that is just a yes/no to "should we deprecate bullets and switch to only colons?" would almost certainly snowball towards a "no", and there might be low participation simply because it seems like such an obvious 'no' that there's not much point in discussing it. However, maybe it would be productive if there were more options? ie. a) allow either, but require consistency, b) always require bullets, c) always require colons. I doubt anyone would go for "c", even if they like me prefer to use [reply], but discussing "a" vs "b" could be productive while still sending a signal to WMF that ~enwiki needs a [reply] or voting-style discussions tool which can handle bulleted indentation. It does seem like a discussion worth having, even if it's been had before, since presently the de facto situation is editors are just doing which indentation style they personally prefer. It would be nice to have a consensus that applies consistently across RfD, CfD, TfD, RMs, merge/split discussions, etc. Could also be helpful to answer if WP:AFDFORMAT should be amended or clarified in any way, since it seems unclear to me if WP:AFDFORMAT is saying that bullets should always be preferred or if only consistency matters. Have RfCs about indentation/bulleting in discussions been had before? If so, when? Would be helpful to look at when the most recent time was and link to past discussions in the new RfC if we take that route. – Scyrme (talk/solidarity) 16:31, 14 November 2026 (UTC)
Small note, I was picturing this format [[Special:GoToComment/h-Separate support and oppose opinions]] and more of an informal poll but we’ve had tagged RfC that are pulse checks if I recall correctly. The requested feature is complex enough that we should demonstrate widespread support for retaining * !voting if you really want the feature. Dw31415 (talk) 16:53, 14 November 2026 (UTC)
Yes! Thanks for correcting me. I think my favorite favorite script failed me, I’ll have to investigate when I get a chance. Dw31415 (talk) 19:23, 14 November 2026 (UTC)
== Requested move 15 November 2026 ==
'''Old Mill Bridge''' → '''Mill Creek Bridge''' – We should move it for reasons [[User:A]] 12:00
* Support per common name. [[User:B]] 12:01
*: Is that the latest edition of the map? [[User:D]] 12:03
: Oppose because the map old. [[User:C]] 12:02
* Support because RS. [[User:E]] 12:04
Added example for discssion. Dw31415 21:39, 15 November 2026 (UTC)
I was thinking a lot about this yesterday. It was fun to think through. Here’s options that I could see programming:
The reply tool looks for a mark at the beginning of the top level comment to flip replies to using bullets. Maybe it’s a visible mark like?? or maybe it’s an html span.
The reply tool looks at the first (or last) “child” (the first reply). If it’s a bullet, the new reply will be a bullet.
The reply tool looks at all children and finds the majority. If most children are bullets, the next will be a bullet. (Closest to Aaron’s “entire” I think, unless that means all children).
Should we express a specific preference? I think so. Deciding which approach to adopt would mean countless meetings in my work. The decision would consume far more human-hours than the actual coding. Which approach do you prefer? Dw31415 (talk) 15:05, 15 November 2026 (UTC)
Some notes on the underlying markup:
Screen readers announce the start and end of lists. A new list is opened with each additional *, :, or # that is added at the start of a line. However note the sequence of characters defines an order in the list nesting. If there is a change, such as from *** to ::*, then this specifies that the list nesting has changed from three levels of bulleted lists to two levels of (to over-simplify, I'll call an) unbulleted lists and a third-level bulleted list. This causes screen readers to make extra list end/start announcements that don't correspond to an actual interruption to the discussion thread and so are unnecessary.
List items starting with : actually encode a description details (dd) list item, and is supposed to be paired with a description term list item. We mis-use this markup on talk pages for historical reasons.
Just changing the appearance of dd list items to have a bullet won't address the problem with screen readers. The actual rendered list needs to be changed.
Rather than complicating the Parsoid parser to handle list items differently based on some form of inline metadata, it would be better to actually change the saved wikitext. This makes it simpler for any tools to parse the wikitext source as well. The reply tool of course enforces this as it adds the required prefixing character. But as long as users can reply manually, they can manually break list nesting.
When replying to a comment, preserving the ancestor list nesting order avoids extra list end/start announcements. Looking at the peer list items and picking whichever is the majority won't fix this, and potentially could exacerbate it. Reducing the number of extraneous list end/start announcements requires aligning the peer list items to have the same list type.
IndentBot ran for a short period of time to make these types of fixes, but hasn't run for a long time. IndentBot did, in my opinion, quite a reasonable job, but of course there are always cases where its heuristics fell short. The operator faced complaints (some which did not follow the nesting principles I outlined), which might be a reason they no longer operate the bot (but that's just speculation).
Although in theory the reply tool could align list types of peer list items, that would mean editing other people's comments. Since inevitably its heuristics would also fall short sometimes, that could create contention between editors.
As I recall, the reply tool originally did have heuristics to figure out how to continue the existing nesting structure. However as they didn't work well enough, the tool was changed to just always use :.
Wikitext markup doesn't support embedding, say, a list within a bulleted list item, and then continuing that list item without adding another bullet. (It doesn't support that for : list items either, but since there's no visual indication of this, editors don't mind.) This leads people to change list types from * to : within their comment, which creates extra list end/start announcements. There are ways to handle this, but since many (most?) editors are unaware of them, using : list items leads to fewer nesting problems than using bulleted list items.
Another problem with bulleted list items is that a significant number of editors seem to think to reply to a bulleted list item, they should use :*, presumably thinking they are moving the bullet item one level inwards. This problem is also avoided by using : list items.
In my view, if anyone can spend effort on enhancing the reply tool, I think work should be resumed on improving its heuristics for determining what type of list to use. Generally speaking, if there is an immediately preceding peer reply, then the same list prefix should be used; otherwise, the list prefix for the parent comment should be used with an additional list character added (perhaps with a new option to specify what type of list to use).
I know some people like to use bulleted list items to flag the creation of a new discussion thread, but as long as users still can reply manually (and I don't foresee that changing anytime soon), honestly using bulleted list items as a direct reply often leads to list nesting problems. (Embedding them within one's comment, as I did here, doesn't cause an issue as no one is supposed to reply to a bulleted list inside someone's comment.) isaacl (talk) 20:08, 15 November 2026 (UTC)
I meant "if any comment is in bullet format (then the reply tool will use a bullet)". By "entire" I meant that it uses a bullet instead of : for the first indent (and isn't simply a comment that happens to contain a bulleted list). In solidarity, Aaron Liu (talk) 20:09, 15 November 2026 (UTC)
isaacl & Aaron, thanks for the responses. I added example context above. I think isaacl's if there is an immediately preceding peer reply leans the way I do. So a new reply at 12:05 to UserA would get a * because UserE's comment starts with a bullet. (I think first reply UserB's might be a little more stable but either way). I take Aaron's approach to mean if any of the replies to UserA are *, then the next one should be. That would mean even if UserB had used a :, as soon as UserE used the bullet, all following replies would use a bullet, even if there is an intervening :. That gives a strong preference to bullets. Dw31415 (talk) 21:54, 15 November 2026 (UTC)
What I described is English Wikipedia guidance, as documented at Help:Talk pages §Indentation and Wikipedia:Manual of Style/Accessibility §Lists. There is no "strong preference to bullets" from an accessibility standpoint. To avoid extra list end/start announcements, editors should follow the ancestor nesting levels, and then follow whatever the previous peer comment used. If everyone follows those rules, all the peer comments at the same nesting level will have the same type. If one person breaks the rule and switches the list type, thus triggering unnecessary announcements, it's best practice for following peer comments to use the new list type, to avoid triggering a whole new set of unnecessary announcements. If you're going in afterwards and aligning all the list types to be the same, then it's up to you to decide which is best. That could mean looking at what list type is used the most and using that one. isaacl (talk) 23:17, 15 November 2026 (UTC)
I really appreciate all the education about accessibility. I agree it's a very important topic. With respect to this wishlist item and the associated T255841, none of them exactly ask for what we are talking about here. An "if there is one bullet, the next is a bullet" rule or even a use-the-last rule seems like we should get more community input on. Thoughts? Dw31415 (talk) 00:49, 16 November 2026 (UTC)
Community guidance has already been established and documented on the pages to which I linked. Not everyone is aware of this guidance, or perhaps agrees with it, but enough people are aware of the accessibility concerns that I do not personally feel that a change to the guidance would attain consensus support.
That being said, the community wishlist item doesn't talk about accessibility, because most people don't know about the underlying structure and focus solely on how the output looks to them. I haven't looked at the page in detail, but it's possible that some of the wishes can't be practically done. The tool inevitably has more constraints than someone who is editing the entire page or section directly. isaacl (talk) 01:17, 16 November 2026 (UTC)
I think T255841 was too broad (it included page-level configuration), so I created T445014 "Reply Tool chooses indentation based on last reply" to capture the specific request and highlight the accessibility benefit. Dw31415 (talk) 02:44, 16 November 2026 (UTC)
Make it obvious if a user being blocked has created any other accounts
I see a potential benefit if the block page was to show other accounts created by the target, ideally recursively, and offer to block those as well. Seercat3160 (talk) 01:29, 15 November 2026 (UTC)
There is no way to automatically identify sock puppets that would not return a lot of false positives. You can report any suspicions of sockpuppetry at Wikipedia:Sockpuppet investigations, but please follow the instructions there. Donald Albury 01:47, 15 November 2026 (UTC)
True. To be clear, I meant "other accounts created" in the sense of using Special:CreateAccount while logged in, which shows in the account creation log. There were some issues with those a few hours ago. Seercat3160 (talk) 01:50, 15 November 2026 (UTC)
Here is a list of unblocked accounts created this year by editors who are now sitewide indef blocked. Most such accounts have never edited. Many will have been created for legitimate reasons. For example, I see a few creators are named for organisations but have gone on to create individual accounts to comply with our username policy. Inclusion on this list does not imply any wrongdoing. The list could easily be extended historically if it is of interest. Certes (talk) 11:14, 15 November 2026 (UTC)
Within that list, as you suggest, most promotional names will probably have been softblocked (eg Special:Log/APACorp), and some of the vandals will have their accounts globally locked by stewards (eg Special:Log/LeThiMyChau01011967 before the block, or Special:Log/OOBE\BYPASSNRO after the block). What aggravates this problem is that the logs are not in the same place (ie Special:Log/BenhVienHuuNghi doesn't show Special:Redirect/logid/176545855, while MediaWiki tries its best to hide access to that log from that direction). In my experience this does happen to an extent every few months, but people catch on real quick and these accounts usually end up getting blocked one way or another. However, I do think it would be useful to indicate in the blocking form whether the user has created any accounts, or was created by another account, as they are often missed at the time. If MediaWiki can provide a warning that a page being deleted has a subpage, it can probably do this. -- zzuuzz(talk) 12:07, 15 November 2026 (UTC)
Time to get better, more credible sources.
This site seems to lack actual credible reliable sources and information on history. It would be easier to just strike all links of sources from anything from 2000 and beyond, as they all seem rather flimsy with zero credibility and no facts to back up notions, history, nor perception of reality. Just websites promoting one idea or another without any facts or solid evidence. If someone can create a website and make a claim, they are able to change history here on Wikipedia. Without providing anything. It's just that simple.
It would also be wise to remove the New York Times and other various propaganda machines as sources for news. They've already been discredited enough, and have no real facts to make. It's all "a person close to the administration" and so on. Time to actually take sources seriously and if they make claims, they should be backed up with something real. But it seems there are more people here who would rather take someone's word for it, if it suits their bias personal bias opinions and ideals. It's almost like most editors can't actually identify what a solid real source is and use appeal to authority fallacies to support their reality. Doing so, has made this site become more of a one-sided joke, than a collection of valuable information. History pages have been flipped into nonsense with no real evidence other than unverifiable words, and the modern news of the day is no different.
So sorry to tell people of this shocking revelation but The New York Times is not a credible source, nor are the dozens of websites talking about the "people's history" or the modern take on American History. Time to do better. ~2026-60343-39 (talk) 06:40, 15 November 2026 (UTC)
These kinds of broad evidence-free claims about Wikipedia, editors or sources have no utility. Sean.hoyland (talk) 08:10, 15 November 2026 (UTC)
I would agree that news media outlets are poor sources for history articles. We should always prefer academic scholarship for that.
For “current events” articles, we do allow news media … as there may not yet be academic sources that cover the subject. Obviously, as time passes, and as academic sources do become available, we should rewrite our article to reflect their scholarship.
All that being said… I don’t think we have many situations where we are still relying on news outlets once academic scholarship becomes available. But if the OP has a specific example, please bring it to our attention. Blueboar (talk) 13:48, 15 November 2026 (UTC)
Academic sources aren't necessarily—indeed, they simply aren't—free from bias: they reflect the context in which they were produced, favoring certain viewpoints aligned with prevailing values and limiting the dissemination of others. This applies to the humanities but, to a lesser extent, also to science, and a more recent revisionist source isn't necessarily better. There's a heated debate about this. However, you have to rely on something. That's why, for me, the most important thing is to preserve pluralism as much as possible, even if the topic is controversial, inconvenient, or politically incorrect. Sira Aspera (talk) 14:42, 17 November 2026 (UTC)
Academic sources from this millennium would probably be best. I personally know how hard it is to hear, but sources from a quarter century ago aren't necessarily the best sources. -- LCU ActivelyDisinterested«@» °∆t° 15:06, 16 November 2026 (UTC)
The following discussion has been closed. Please do not modify it.
Academic sources aren't necessarily—indeed, they simply aren't—free from bias: they reflect the context in which they were produced, favoring certain viewpoints aligned with prevailing values and limiting the dissemination of others. In 50 years, everything produced in these 26 years will probably be considered waste for one reason or another, because society will be different. This applies to the humanities but, to a lesser extent, also to science, and a more recent revisionist source isn't necessarily better. There's a heated debate about this. However, you have to rely on something. That's why, for me, the most important thing is to preserve pluralism as much as possible, even if the topic is controversial, inconvenient, or politically incorrect. Sira Aspera (talk) 14:43, 17 November 2026 (UTC)
Hello, I would like to propose a feature on the watchlist to be able to set a bookmark or indicator marking which the user can set to indicate where one's review of revisions has caught up to.
This was (very briefly) discussed here. IOHANNVSVERVS (talk) 00:50, 18 November 2026 (UTC)
There are a couple of implementations that might do different things here depending on what you want. If you mean looking at your entire chronological watchlist, do you mean marking say a specific timestamp? If you mean within a single article, there is a system that tracks the latest version you have looked at, but I don't know if it can be manually manipulated. CMD (talk) 03:40, 18 November 2026 (UTC)
I just want a bookmark for my watchlist so I can easily see where I have left off on reviewing recent changes to pages that I follow. That's it, just a bookmark for my watchlist. I imagine it like this: , just a blue line which I can move as I progress through reviewing my watchlist. Perhaps everything under the bookmark/line could be faded as well. IOHANNVSVERVS (talk) 03:57, 18 November 2026 (UTC)
And then this bookmark can just be moved up or down, a way of manually keeping track of one's place in what they're caught up with. I waste a lot of time trying to refind where I left off when reviewing revisions in my watchlist, and I'd think I can't be the only one. IOHANNVSVERVS (talk) 04:10, 18 November 2026 (UTC)
WMF
The Wikimedia Hackathon, the yearly software engineering conference, may stop being a global conference
I can't say I'm very happy about this proposal: mw:Wikimedia Hackathon/Community Proposal 2026. This is a conference for Wikimedia software developers that I attend yearly, and that I consider to have an extremely successful format. The above proposal appears to want to take the money spent on this conference and basically kill it off to spend it on smaller regional conferences, except for every third year.
I'm not sure this is the correct place to post this or if it will resonate with people here. But this is something in the pipeline that is frustrating me. I wish WMF would leave stuff that's working alone and not make big changes to it.
I really hope this doesn't become a wishlist situation, where we have to put up with a poor format for a couple years, then finally there is a big backlash to get it changed back. I'd rather they just not make the questionable changes in the first place.
Thanks for listening. –Novem Linguae (talk) 06:09, 18 October 2026 (UTC)
"Our goal is to better understand whether concentrating our resources on one global event held in the same region each year creates barriers to participation or limits our ability to develop technical contributor communities in other parts of the world." There seem much easier ways to trial this than an immediate three-year experiment. For example, there are already regional conferences, trial a hackathon at one or two of those. Much less money spent for the same experiment without immediately affecting the current process. CMD (talk) 10:36, 18 October 2026 (UTC)
@Novem Linguae - Thank you for the feedback and I appreciate you making sure that the entire community has an opportunity to comment. To be clear, the goal isn't to mess with something that is working, but to provide an opportunity to discuss something that others in the community have raised questions about.
So far, there's been lots of really valuable feedback on what works and doesn't with hackathons, as well as alternatives to the one provided in the proposal (like @CMD's proposal above). To ensure that others have an opportunity to see your comments and engage with them, I'd encourage you to comment on the proposal's Talk Page. ~2026-57722-47 (talk) 19:04, 29 October 2026 (UTC)
My apologies! Just realized I wasn't logged in when I replied, this is from me (@BPiovesan-WMF) BPiovesan-WMF (talk) 19:05, 29 October 2026 (UTC)
I've said for a while that Wikimania should be around 1/3 as expensive to run as it currently is, and that we should be learning how to optimize for self-funding events that recover their costs (including the cost of scholarships) through partnerships, sponsorships, and tickets. I think something similar holds for hackathons. A version of this proposal that I would appreciate would look something like:
* A commitment to reduce the cost per hackathon-year while increasing accessibility (in geographic diversity, in # of participants)
* An approach that keeps a central global gathering, and adds a couple new regional hackathons (either entirely new ones, or existing ones that are expanded to have more of the WMH spirit), while trying to reduce total costs in the coming year
* An invitation for proposals and suggestions from people who have run extremely efficient / participatory / generative / well-sponsored hackathons, about how to apply the best parts of that organization to the global event(s). (I will point to decetralized 24-hour Wikidata birthday celebrations as one joyful alternative;)
Our current events schedule and cost per event (and especially net cost per participant! and low viewership of the recordings) remind me of other global communities that have gone through unwanted dry spells where they stop having global events at all after a big-budget heyday. I would prefer to see us get to a sustainable version of this -- specifically one where it is obvious that the global community can continue to hold a productive event even without a large centrally funded push by WMF or WMDE -- sooner rather than later. –SJ+ 18:58, 9 November 2026 (UTC)
Source Verification: Internal Review Findings
Experiment source verification suggestion live in Suggestion Mode
Hi y'all – we wanted to follow up about the source verification project, where we’ve just completed an internal review of the suggestions it produces and have a proposal about making it accessible for testing with experienced editors.
With your help, we defined criteria to select the 1,000 articles we would generate an initial dataset of source verification suggestions for.
We (staff) have created this dataset and completed an internal review of it.
What follows is a summary of what we found, what we think these findings mean for this work going forward, and the open questions we're left with.
What do you think about the conclusions we've reached and next steps we're proposing?
Conclusions
We reviewed 134 source verification suggestions from the dataset and discussed them together as a team. What follows are the conclusions we're reaching:
Article claim and source URL extraction worked well. Generally, the model succeeded at extracting claims and source URLs from Wikipedia articles. This enabled us to focus on the quality of the verdicts the model reached and the rationale it provided for each.
The model outputs sufficiently reliable verdicts. In 71% of the suggestions we reviewed, internal reviewers agreed the cited source did not fully support the claim, including 49% where it did not support the claim at all. Several of these were concrete discrepancies between article and source (see the Lucille Ball and Alamgir examples below).
Taken together, we think the source verification suggestion is reliable enough to warrant a wider volunteer-led review. Please see "Proposed next steps" for how we see this playing out.
Proposed next steps
With the "Conclusions" above in mind, we see the next steps as the following:
On Tuesday, 3 November 2026, we (staff) make the initial dataset of source verification suggestions available to you all in two forms:
Note: These suggestions would only be available to people who have both 1) published ≥100 cumulative edits and 2) enabled experimental edit suggestions within Preferences
As a spreadsheet so that you can more easily see patterns across suggestions and locate articles where you can experience the suggestions in-context via Suggestion Mode
Note: we do not think reviewing suggestions in the spreadsheet alone is sufficient for forming an opinion about the usefulness of the suggestion.
Note: we see the purpose of y'alls review as making sure we wouldn't be wasting unsuspecting experienced volunteers' time with a large number of erroneous suggestions by enabling source verification suggestions as default-on within Suggestion Mode.
We (staff + volunteers) will then look at data from both reviews to decide: Do we make the source verification suggestion available by default within Suggestion Mode to experienced volunteers so that we can evaluate how helpful they find it in real world use?
Note: to evaluate "how helpful [volunteers] find it in real world use" we would be analyzing engagement with the suggestion, the quality of edits made with it, the edit completion rates of edits where it was activated, and qualitative feedback from experienced volunteers who tried it.
Open questions
What additional filters might be useful to place on the model and/or what articles it runs on to create a more useful user experience? E.g. Setting a cap on how many suggestions are shown per article, preventing suggestions from appearing on list pages, etc.
What information, shown alongside a suggestion, might help you decide more quickly whether it’s right? E.g. deep-linking to the relevant passage within the source, linked to the diff where the claim was added, etc.
Currently if the claim is not supported, we expect that the editor will fix it or add a {{failed verification}}. Is that reasonable or are there other actions we should try to directly enable?
How should the suggestion behave when it can't read a source (e.g. paywalled, offline, etc.)?
Detailed findings
Internal review findings
Process
We generated a total of 16,585 suggestions for a sample of articles that met the criteria listed here
We compiled those 16,585 suggestions into a spreadsheet, split up by category (e.g. blp, history, ctop, {{dubious}}, {{Failed_verification}}, {{ai generated}}, etc.)
6 staff members reviewed a total of 134 of the 16,585 suggestion
For each of the 134 suggestions, staff:
Reviewed the claim text the model extracted from the article and evaluated whether they thought the claim was complete
Reviewed the verdict the model reached (Not supported or Partially supported), the rationale the model gave for why it reached said verdict, determined to what (if any) extent they thought the model prediction was correct, and offered an explanation as to why they reached the conclusion that they did
We then looked over the suggestions our colleagues reviewed and documented general reflections about them
Lastly, we calculated the rates at which staff verdicts did and did not align with the verdicts the model reached (see "Quantitative findings" below)
Quantitative Findings
In 49% of cases, reviewers agreed with model in concluding source does not support claim at all
Flagged claim
Notes
AdventHealth opened a 200,000 square feet (19,000 m2) emergency room and primary care facility on Walt Disney World's campus on May 17, 2023.
"AdventHealth facility is only 19 thousand sqft, not 200 thousand" (page: AdventHealth, check id 3c1bac7e1c82eaae)
[Lucille Ball’s] acting forays were stilled at an early stage when she became ill with rheumatic fever and was unable to work for two years.
"Claim states she had rheumatic fever but source states it was rheumatoid arthritis." (page: Lucille Ball, check id: 3f99f519c8f527fc)
[Mary of Teck] is buried beside her husband in the nave of St George's Chapel, Windsor Castle.
"Queen Mary was buried in the North Nave Aisle, not the nave itself." (page: Mary of Teck, check id 012418710cd2e07e)
"Though Alamgir was unhurt, three vehicles (including the one in which he was riding) were vandalized, and ten people were injured." Link to claim
The claim included within the Wikipedia article states that the car the subject was riding in was damaged. Although, the source cited says the car he was riding in was NOT damaged. These two statements contradict one another. (page: Mirza Fakhrul Islam Alamgir, check id: 01836695cfc49863)
In 22% of cases, reviewers agreed with model in concluding source does not support claim fully
Flagged claim
Notes
On 17 June 2026, Keir Starmer announced that the Children's Wellbeing and Schools Act 2026 has passed, which puts a ban on children under 16 having accounts and accessing social media apps
The act was passed on a different date and doesn’t ban anything by itself (page: Online age verification laws by country, check id: cbeeec4e88959d7a)
[Amis Harvest Festival] takes place every July to September.
Article claims that the Amis Harvest Festival takes place every July to September. The source only mentions summer time, not fixed dates, and that the dates can vary across villages. (page: Amis people, check id: 740542a585970b96)
A statue of Earhart by Ernest Shelton was erected circa 1971 in Los Angeles, California.
Source talks about the statue and when it was erected, but doesn’t mention the sculptor’s name as listed in the claim. (page: Amelia Earhart, check id: 0366ad517930495e)
In 28% of cases, reviewers disagreed with model in concluding source does not fully support claim
Flagged claim
Notes
“Marie Tussaud was employed to make a death mask of her head.” -
The model thought that “her” refers to Marie Tussaud herself (page: Marie Antoinette, check id: 770d5c8b71c195f2)
It would also be played by Weir's RatDog after the dissolution of the Grateful Dead.
Source does say that Ratdog played "Victim or the Crime", and the dates mentioned in the article are after the dissolution of the Grateful Dead. (page: Victim or the Crime, check id: 2d912ad52fc7efe4)
Following the release of Citizen Vigilante in late June 2026 and its ban in Germany, the film was promoted by Elon Musk on X, greatly boosting its reach.
A second source verifies the part of the claim that the model says the source doesn’t verify (page: Uwe Boll, check id: 0e4b8066c9135210)
Qualitative findings
Perceived significance of discrepancies: There are some claims that the model flagged as not being supported by their source(s) that, upon closer inspection, involved relatively small discrepancies between the information included within Wikipedia and the source. Editor opinions may vary on how consequential they consider these discrepancies to be.
E.g. a film reaching some sort of revenue milestone within 3 vs. 4 days after launch.
Selection bias: The quantitative findings should be taken with a grain of salt considering we did not review suggestions randomly. As such, there may be some selection bias at play.
URL Extraction: as part of the initial internal review process, each person was asked to verify whether the model had accurately extracted the source URL from Wikipedia. In 100% of cases, the model was successful in this operation. As a result, we removed this URL checking from the review process.
Claim Density: the number of claims the model flagged as needing review varied article-by-article. Some of this variance can be explained by genuine differences in content quality, others, as we came to learn, can be explained by the model handling claims that start with pronouns (e.g. "he/she") less well. There are a series of improvements we think could improve the model that we'd value y'all input on. See "Open questions" below. For context:
A typical article in our sample has over 150 citations, and the model flagged about 17 of them as not fully supporting their claims.
There are outliers: 2% of articles have >100. Lists and some biographies (e.g. 2026 deaths in the United States - see screenshot). This is due to a combination of the higher background level of sloppiness, citation density and tool deficiencies, for instance the pronoun problem.
Number of Source Verification Suggestions per article (initial en.wiki dataset).Experimental Source Verification Suggestion live in Suggestion Mode.
Suggestion invalidation
Suggestions appear if and only if the claim and source have not changed since the article was initially analyzed and the source is not followed by a qualifying template[i]. That is, if the suggestion has been addressed in any capacity - a user has updated the source or the claim, whether prompted by suggestion mode or not, or has added a qualifying template - then the suggestion will no longer show to any user.
If a user dismisses a suggestion by clicking the ‘dismiss button’, they won’t see that suggestion for the remainder of the edit session. However, they - and other users - will continue to come across it in future edit sessions until it is actually addressed.
The Editing Team recognizes the importance of preventing what experienced volunteers agree are invalid suggestions from appearing for themselves or other people in the future. We are tracking this work in T427236 and T433147. While we have not yet defined a timeline for when this functionality will be in place, you can see the technical thought we've put into the architecture that would help enable it.
i. Wikis have the option to locally configure a ‘templateToInsert’ for Source Verification in the on-wiki config. This is the template that (1) will be inserted after the claim when the user dismisses the suggestion with the ‘suggestion is valid’ response, and (2) will be checked for to determine if the suggestion is still valid and should be surfaced to other users. For example, the recommended ‘templateToInsert’ for enwiki would likely be {{Failed-verification}}.
Hi, does the WMF Tool already have access to the wikipedia library? I testet the script from Alaexis however in all the testet articles, 90% of the sources were not available, even open access sources. If its like that, the tool is useless. While i can certainly copy the text into Alexis's tool and let it be checked, but then I might as well just ask the AI in my browser. Or myself. In my opinion, the tool is only useful if it saves me the trouble of looking up the claims in the sources. Then all I have to do is verify the AI's output. The Other Karma (talk) 07:27, 31 October 2026 (UTC)
We're working on requesting access for the source verifier, through the same route that Earwig's Copyvio Detector already uses. CMedelius-WMF (talk) 00:18, 4 November 2026 (UTC)
I am not sure 71% is sufficiently reliable - that's calling someone out to look specifically at a source to double-check something for no reason more than 1/4 of the time. And since we can't actually dismiss the suggestions, that... will be a lot of incorrect suggestions constantly coming back up.
Re: whether a source agrees fully or not, I'm not really seeing a difference between "agree not fully" #3 (the Earhart one) and "disagree not fully" #3 (Uwe Boll). In both cases, as I read these, there is some information that was not in the source, and the model is equally correct in both instances. It's just that in the second there is also another citation. This will surely affect quite a lot of articles - can the model not be trained to look at all of the footnotes given, not just the first?
Re: "north nave aisle", it's quite normal to describe that part of the cathedral as "the nave". So the claim is actually fully correct, if not as specific as it perhaps ought to be. In solidarity, asilvering (talk) 19:51, 29 October 2026 (UTC)
I am not sure 71% is sufficiently reliable…
You may end up being right in thinking this suggestion is not reliable enough, in its current form, to warrant a deployment as a default-on suggestion within Suggestion Mode.
Although to clarify, we were not seeking, nor equipped to, make a decision about a wider deployment with this initial internal review. This internal review was narrowly scoped to answering, "Do we think these suggestions are reliable enough to warrant experienced volunteers allocating valuable time to reviewing them?"
And based on the review we conducted, we do think the suggestion is reliable enough to invite interested experienced volunteers to review them.
It's only after we (staff and volunteers) have reviewed these suggestions would we together decide "Do we make the source verification suggestion available by default within Suggestion Mode to experienced volunteers so that we can evaluate how helpful they find it in real world use?" (See Step 3 above)
Does this get at the point you're making? Might there be something I'm missing/misunderstanding?
...that's calling someone out to look specifically at a source to double-check something for no reason more than 1/4 of the time.
On the time spent piece, you may well be right and I think it's only through real world use will y'all be able to make a judgement call on this.
As I see it, what matters is whether the time spent checking false positives outweighs the time saved by catching real errors. To what extent (if any) does this thinking align with how you're viewing this tradeoff?
And since we can't actually dismiss the suggestions, that... will be a lot of incorrect suggestions constantly coming back up…
We agree with you here: without the ability to dismiss suggestions, multiple volunteers could see the same unhelpful/incorrect suggestion which would in turn increase how precise the model would need to be before we’d (staff + volunteers) be comfortable putting it in front of people. Potentially, to an unachievable point even.
So it's not ambiguous: we see work on dismissals as a question of when not if and we're open to the possibility that this functionality would need to be in place before source verification suggestions are enabled by default.
Thank you for thinking through this critically. Please let me know if any facet of the above leaves questions/concerns open in your mind or causes new ones to emerge. PPelberg (WMF) (talk) 22:33, 29 October 2026 (UTC)
@PPelberg (WMF), we must be misunderstanding each other, because I read "Do we think these suggestions are reliable enough to warrant experienced volunteers allocating valuable time to reviewing them?" as basically "is this reliable enough to be deployed?" with extra words. What's the difference, for you? In solidarity, asilvering (talk) 02:05, 30 October 2026 (UTC)
@Asilvering, the distinction is between enabling them as experimental suggestions, visible only to editors who have opted in to experimental suggestions, and making them regular suggestions, visible to all editors who meet the edit-count criteria. Alaexis¿question? 07:34, 30 October 2026 (UTC)
Thank you for adding this context, @Alaexis. @Asilvering: does what Alaexis shared above address the confusion you spotted? PPelberg (WMF) (talk) 22:30, 30 October 2026 (UTC)
No, I think we may have a fundamental disagreement. But I think that disagreement could be resolved by reframing how the edit suggestion is presented to editors. Right now, the wording of the suggestion begins from the presumption that the model is intended to highlight problematic sentences; the purpose of this edit suggestion is to find and fix incorrect sentences on Wikipedia. It is understandable that the suggestion is worded in this way, because that was indeed the intent of this project. However, with a 71% hit rate, we cannot truthfully say that the model is highlighting problematic sentences. So in fact what we have is an edit suggestion that fails 29% of the time even if the editor correctly applies WP:V when responding to the check, which we can't be certain about either.
If you cannot raise the hit rate over 71%, the suggestion should be reframed as a spot check. We do sourcing spot checks all the time (for example, at WP:GAN), and they do not start from the presumption that the sentence is incorrect. (At GAN, you're instead starting from the presumption that the sentence is correct, if anything.) So instead of "a model has identified that this claim might not be supported by its source", you end up with something neutral like "a model has selected this sentence for source-checking". Under those terms, you have an edit suggestion that works 100% of the time, and ideally results in improvements to the article 71% of the time or more often. Does you follow?
In any case, we definitely need the ability to dismiss suggestions as incorrect (ie, to mark it as "fact checked, it's fine") before this leaves "experimental mode". In solidarity, asilvering (talk) 00:03, 31 October 2026 (UTC)
I like the idea of carefully framing the suggestion as a prompt to spot-check a citation. As a relatively neutral framing, it could reduce automation bias and increase the chance that a person actually goes and looks at the source. It also opens up the opportunity to prompt spot-checking of sensitive/high-risk statements where the automated verifier can't access or parse the citation. The research for the reference need model (paper) might suggest ways to help find those statements. Dreamyshade (talk) 00:57, 31 October 2026 (UTC)
+1, I assumed this was already going to be the case Kowal2701 (talk, contribs) 01:03, 31 October 2026 (UTC)
Agreed re the dismissal and I think that it should be recorded on-wiki. This way the community will be able to measure the effectiveness of suggestions (edits vs dismissals). Having it recorded will also reduce abuse as the editor will know that the dismissal is recorded and attributed.
Not sure about the framing as "spot checks". Spot checks ("a quick examination of a few members of a group instead of the whole group" ) make it look like a random sample, while in reality it's more like a screening (medicine), where a positive result means that a more thorough check is needed.
I'm sure the language can be adjusted, I think one widely used tool that has the same probabilistic nature is Earwig's Copyvio Detector. It describes likely copyvios as "Violation suspected" (example - here the top one is actually not a copyvio but a wiki mirror). Alaexis¿question? 17:20, 31 October 2026 (UTC)
Re: whether a source agrees fully or not, I'm not really seeing a difference between "agree not fully" #3 (the Earhart one) and "disagree not fully" #3 (Uwe Boll). In both cases, as I read these, there is some information that was not in the source, and the model is equally correct in both instances. It's just that in the second there is also another citation. This will surely affect quite a lot of articles - can the model not be trained to look at all of the footnotes given, not just the first?
Good catch. The model is trained to evaluate all footnotes following a claim, not just a subset of them. If it happens to return a verdict that doesn't cover the complete set, then we do a second check on the suggestion mode side to ensure this suggestion isn't shown to users. So this example is one that was not caught by the model but would still not have been shown in suggestion mode; including it as an example here was our mistake, as it doesn't reflect the actual user experience. CMedelius-WMF (talk) 22:47, 29 October 2026 (UTC)
With regards to #1, I think it'd make sense to avoid checking articles being rapidly edited, new articles, and claims that cite paywalled or offline sources as referred to in #4. On #2, making the model's reasoning available could help the community figure out where strengths and weaknesses are. MetalBreaksAndBends (One for all) 19:57, 29 October 2026 (UTC)
On #2, making the model's reasoning available could help the community figure out where strengths and weaknesses are.
@MBAB, could you please say a bit more here about the sort of reasoning you'd find helpful?
I ask this because currently, the model outputs a rationale for each suggestion it outputs. E.g. “Claim states she had rheumatic fever but source states it was rheumatoid arthritis”. This leads me to think you might be thinking of something else/in addition...
I think it'd make sense to avoid checking articles being rapidly edited, new articles...
You and @CMDeach raised this. Could you please share a bit more about where this recommendation is coming from?
For what it's worth, we'd been assuming (perhaps inaccurately!) that it'd be useful to check articles that are new and being rapidly edited because they'd be more likely to contain inaccuracies. Then again, maybe you're thinking adding another actor into these situations (in this case a machine) could complicate things? PPelberg (WMF) (talk) 23:46, 29 October 2026 (UTC)
I was talking about reasoning tokens, as reading them can be helpful for understanding a model's thinking in further depth than a 50 word summary can provide. Obviously, this shouldn't be exposed to editors by default (especially if your model of choice has a GPT-6-astra-esque affinity for not using the spacebar).
I suggested avoiding rapidly edited and new articles for 2 slightly different reasons. New articles because they're going to be in the NPP queue, which means they're going to be checked soon (although ai verification built for the NPP workflow could be promising. e.g. not doing the check until the page is being reviewed and factoring in other steps like a source's value for notability). For rapidly edited articles, it's because there's a higher chance that any given checked text will be modified requiring rechecking. My concerns on both of these is less that the system might get something wrong and more that compute might be misallocated. MetalBreaksAndBends (One for all) 00:26, 30 October 2026 (UTC)
I was talking about reasoning tokens, as reading them can be helpful for understanding a model's thinking in further depth than a 50 word summary can provide. Obviously, this shouldn't be exposed to editors by default...
Ah, got it. I agree with you in thinking that exposing this level of detail is best suited for somewhere deeper in the experience so folks who are especially curious can find it. Thank you for adding this context.
In case it's interesting to know: I think the checks we ran used an un-reasoning version of Qwen 3.8. Although, @SSalgaonkar-WMF will be able to say for certain. PPelberg (WMF) (talk) 22:33, 30 October 2026 (UTC)
I suggested avoiding rapidly edited and new articles for 2 slightly different reasons. New articles because they're going to be in the NPP queue, which means they're going to be checked soon (although ai verification built for the NPP workflow could be promising. e.g. not doing the check until the page is being reviewed and factoring in other steps like a source's value for notability).
Understood. To confirm the NPP use case, you're thinking that it would be worthwhile to wait to run the suggestion on new articles until after an experienced volunteer has validated the article meets notability requirements? Specifics aside, we're with you in thinking there is/are NPP-specific use cases here that feel promising.
For rapidly edited articles, it's because there's a higher chance that any given checked text will be modified requiring rechecking. My concerns on both of these is less that the system might get something wrong and more that compute might be misallocated.
Oh, okay. I see. Understood. Thank you for explaining that. PPelberg (WMF) (talk) 22:37, 30 October 2026 (UTC)
...and claims that cite paywalled or offline sources as referred to in #4.
Right now, the suggestion ignores offline and paywalled sources. Although, this leads me to wonder: can you see it being useful for the UI to indicate when the model tried to evaluate a claim and was unable to do so because a source was offline or paywalled? Do you think it ought to instead show nothing silently? Something else? PPelberg (WMF) (talk) 23:49, 29 October 2026 (UTC)
This is also mostly based in compute allocation, although there is also a volunteer allocation angle too. If a paragraph has multiple citations at the end with one or more being inaccessible, it can't be known if any given claim not supported by the accessible sources is actually unsupported or just supported in the inaccessible ones. So, for those paragraphs any given suggestion is less likely to be helpful, due to it only being trustworthy where the content explicitly contradicts a source. A flag for inaccessible sources would help avoid errors where correct content is removed because inaccessible sources were skipped. But unless a system were devised to direct verifiers with access to inaccessible content to suggestions, I think bailing at the first sight of problematic sources would offer the best rate of "tokens per abstract unit of improvement". MetalBreaksAndBends (One for all) 00:57, 30 October 2026 (UTC)
In light of WP:PAYWALL, I think claims that cite paywalled or offline sources should be up for review as well. But we'd need additional options for feedback, like "Paywalled/offline, checked", "Paywalled/offline, couldn't check". Jo-Jo Eumerus (talk) 10:22, 6 November 2026 (UTC)
I've been working with a Master students evaluating the script, and they found a couple of categories of mistakes it often makes. I will ask them to share. Perhaps that can raise the 71% to a higher level. I agree that 71% is not quite the accuracy we would like to see. Source verification is incredibly time-consuming as an activity, and newish (100-1000 edits) editors are also not great at it. Will this result in properly cited text being removed?
In my two GAs I've run it on today, I disagreed with all 5 suggestion that things were wrong (2 were subjective), but maybe the script uses a different model than the one you have access to? In solidarity, —Femke (talk) 🐦 21:19, 29 October 2026 (UTC)
...I disagreed with all 5 suggestion that things were wrong (2 were subjective), but maybe the script uses a different model than the one you have access to?
@Femke: might you be able to share the version of the script and/or model you were using so that we can check if they're the same? Also: might you be able to share the following so that we can see the suggestions you encountered? It'd be helpful to know:
The permanent link to the version of the article you were editing
The text of the claims the model generated suggestions for
The verdicts and rationale the model gave
I've been working with a Master students evaluating the script, and they found a couple of categories of mistakes it often makes. I will ask them to share.
Seeing what they've found would be a big help. Thank you for offering!
I agree that 71% is not quite the accuracy we would like to see. Source verification is incredibly time-consuming as an activity, and newish (100-1000 edits) editors are also not great at it. Will this result in properly cited text being removed?
I'm going to hold off on responding to the "71% accuracy" part for a moment because I'm going to come back to that in a response to the point Asilvering raised about this above. Now, with regard to who the proper audience might be for this suggestion, we think y'all are best equipped to decide and implement what you think is best via Special:EditChecks. PPelberg (WMF) (talk) 21:41, 29 October 2026 (UTC)
I would love 100+ edits to be the audience, as that's the type of editors we want to teach to fact check everything. But.. I think putting the weapon in their hands would be a bit too dangerous as is. I suspect many people will trust the tool, and where the tool is wrong, it's usually in more complicated facts I also think editors will get wrong.
I'm off to bed soon, but I ran it on post-exertional malaise (4 claims flagged as incorrect) and Ursula Bethell (1 claim flagged). Two of the errors seems to be, if I understand it correctly, from sentences supported by two sources, where 1 of the sources didn't completely cover all the content. One said that 'irreversible decline' was not the same as 'permanent decrease', which is probably a bit more subjective as permanent may be a slightly stronger word, but I'd say that's the same. Don't remember the other two, would have to rerun. Will rerun tomorrow with the requested info.
I used Aleaxis' script with the default settings, so Lift Wing. In solidarity, —Femke (talk) 🐦 21:50, 29 October 2026 (UTC)
For reporting issues that you notice from particular suggestions, it may be easier to use the tool's built-in "comment" button, which sends reports to User talk:Alaexis/AI Source Verification with metadata about the suggestion itself. Sdkb‑WMFtalk 18:39, 30 October 2026 (UTC)
The edit suggestions have a different UI which doesn't have a comment button (see the screenshot above). @CMedelius-WMF, maybe you can explain what options the editor has and how they work? Alaexis¿question? 19:17, 30 October 2026 (UTC)
Yes, the edit suggestion appears with two options: "Revise", which brings them into a focused edit state, and "Dismiss", which opens up a survey to provide an answer on why.
It also has the normal dropdown that is shared by all edit suggestions, which contains an option to provide feedback that is then posted to mw:Talk:VisualEditor/Suggestion_Mode/Feedback. We've internally been discussing a change to make the feedback destination configurable; and in this case, it may be helpful to direct feedback to User talk:Alaexis/AI Source Verification. CMedelius-WMF (talk) 19:48, 30 October 2026 (UTC)
I would love 100+ edits to be the audience, as that's the type of editors we want to teach to fact check everything. But.. I think putting the weapon in their hands would be a bit too dangerous as is. I suspect many people will trust the tool, and where the tool is wrong, it's usually in more complicated facts I also think editors will get wrong.
1) It's important newer editors be equipped with the know-how and tools to help out with verifying claims are corroborated by their accompanying sources
2) I see potential in this suggestion helping newer editors onboard into and complete this work
3) Before "2." can happen, we need to be confident that the user experience is – let's call it – resilient to people assuming the suggestion is always right.
Assuming the three points above accurate reflect the points you were making @Femke, I think we're aligned here. PPelberg (WMF) (talk) 22:45, 30 October 2026 (UTC)
Great to see this work continuing and progress being made.
For my part, idk if ~70% is too low or not. Obviously, higher is ideally better, but I think most people aren't right 70% of the time, so seems to me the model is doing pretty good:-)
The concern I have is that ~150 out of 16k is a tiny percentage, and as they were apparently not randomly selected, I'm not sure if the results are representative at all of anything. Of course, the solution to that is what you're already planning to do: have more people do more testing, which seems like the right next step regardless. Levivich (talk) 22:01, 29 October 2026 (UTC)
yeah, ~70% is well worth it, way better than any other way we have of finding WP:V failures (which is nothing). Issue is whether people will put absolute trust in it or be lazy/go with the balance of probability and not actually read the source before removing stuff Kowal2701 (talk, contribs) 00:50, 30 October 2026 (UTC)
@Kowal2701, that's true for, say, Alaexis's userscript. I'd be quite happy to use a userscript with a 71% hit rate, because I'd be using that mostly informationally - ie, my use case is that I'm already trying to fact-check the article, and the script would be helping me focus on the parts that seem most likely to be wrong. That's great. But in Suggestion Mode, what it's doing is surfacing an error to an editor, possibly a relative newbie, and directly asking them: hey, does this source verify, because I don't think it does? And that's a very different kind of mode that ought to have a higher hit rate than 71%, in my opinion. In solidarity, asilvering (talk) 02:03, 30 October 2026 (UTC)
@Asilvering, agreed that default-on suggestions is a different mode from a userscript. However right now these suggestions will be experimental, visible only to opted-in users, and the whole point of the experimental stage is to check whether these suggestions work before anyone decides to make them regular ones. It's quite possible that based on the findings of the experimental stage we'd fine-tune the pipeline and/or enwiki could raise the edit count threshold. Alaexis¿question? 07:43, 30 October 2026 (UTC)
I think people should easily be able to opt-out of it. Tbh what I don't like about Alaexis' script is reading the LLM's reasoning, I'd rather it just listed the claims with their corresponding sources, possibly on the talk page, and people can just {{tick}} or {{cross}} and sign or whatever. I expect its false positive rate is much higher on good quality articles, we could exclude FAs and GAs but idk what else Kowal2701 (talk, contribs) 15:20, 30 October 2026 (UTC)
...hat I don't like about Alaexis' script is reading the LLM's reasoning, I'd rather it just listed the claims with their corresponding sources, possibly on the talk page, and people can just Y or N and sign or whatever...
@Kowal2701: the simplicity of the workflow you're describing resonates with me and I'm curious: what don't you like about seeing the LLM's reasoning? E.g. might you not trust it and therefore find its presence non-additive?
...I expect its false positive rate is much higher on good quality articles, we could exclude FAs and GAs but idk what else...
The thinking there being those articles have already been closely reviewed by knowledgable volunteers? PPelberg (WMF) (talk) 17:14, 30 October 2026 (UTC)
what don't you like about seeing the LLM's reasoning? Yeah, partly because I wouldn't trust it, partly because I'm sick to death of reading AI-generated text lol. I don't think there's really any benefit to it since in all cases the human will have to check the source for themselves anyway, though ofc having the reasoning is useful for testing the feature re: how accurate it is.
The thinking there being those articles have already been closely reviewed by knowledgable volunteers? Yes, and content written by experienced editors is usually of a similar calibre. Maybe we could use the mw:WikiWho API to exclude content written by editors who have GAs/FAs, or if we wanted it to be more restrictive exclude content authored by users w autopatrolled? Kowal2701 (talk, contribs) 18:24, 30 October 2026 (UTC)
One of the findings from my student this summer was that the script detected loads of issues at a FA that they believed were true errors. I'm curious to see whether I agree. In solidarity, —Femke (talk) 🐦 18:29, 30 October 2026 (UTC)
yeah, I'm sure it would identify true WP:V issues in FAs and content by users w autopatrolled, but given such issues generally occur less often in such content I assume there'd be a higher rate of false positives? Kowal2701 (talk, contribs) 18:32, 30 October 2026 (UTC)
Yeah, you're right that there will be more false positives in such articles (the false discovery rate would be higher). On the other hand, it's also more embarrassing to have such errors in GA/FA, so fixing them may be worth extra time spent on checking duds, and Femke’s student found real errors at an FA. I think it's worth tracking this while the suggestions are in the experimental phase: errors fixed vs discarded suggestions in GA/FA. Alaexis¿question? 18:58, 30 October 2026 (UTC)
it's probably worth incorporating it into GAR/FAC instead of random spotchecks Kowal2701 (talk, contribs) 22:37, 30 October 2026 (UTC)
@Kowal2701, I don't think that's a good idea, because the script only works on a subset of sources, and that subset of sources is already the set that are easier to check. Because reviewers who make random spotchecks are often quite determined to maintain that randomness, they will request access to harder-to-find sources from the nominator and go digging where otherwise they might not, and this is an important part of that process. Alaexis's script can be perfectly useful at GAN/FAC, especially if you're pretty sure the whole article is dubious and you're looking for some low-hanging fruit so you can fail the review and send it back for more editing. But that random spot-check has real benefits and it would be a mistake to incorporate this script instead. In solidarity, asilvering (talk) 00:13, 31 October 2026 (UTC)
Yeah, partly because I wouldn't trust it, partly because I'm sick to death of reading AI-generated text lol. I don't think there's really any benefit to it since in all cases the human will have to check the source for themselves anyway, though ofc having the reasoning is useful for testing the feature re: how accurate it is.
I do get that, I'm tired of seeing AI-generated text everywhere too. Though in terms of benefit, I'd argue that it does save time for the user; it tells you exactly what to check in the source, so it's easy to spot when it gets something wrong. Without that reasoning, you'd have to work out from scratch why the claim/source was flagged.
You can see examples of the reasoning in the spreadsheet that we'll share. I'm curious to know your thoughts after reading through some of the rationales. CMedelius-WMF (talk) 00:16, 4 November 2026 (UTC)
Another thing, we might want to exclude articles with {{AI-generated}} tags, since it's not really fair to have someone hone/polish such content when it'll have to be removed or rewritten from scratch Kowal2701 (talk, contribs) 18:30, 30 October 2026 (UTC)
Oh, the notes are the AI's reasoning. Here I thought it was the reasoning of the staff who had agreed or disagreed with the model. That makes me much less grumbly. Though I still think 71% hit rate is far too low for a useful edit check. In solidarity, asilvering (talk) 20:26, 30 October 2026 (UTC)
The concern I have is that ~150 out of 16k is a tiny percentage, and as they were apparently not randomly selected, I'm not sure if the results are representative at all of anything. Of course, the solution to that is what you're already planning to do: have more people do more testing, which seems like the right next step regardless.
Very fair - the results of our internal review shouldn't be taken as a measure of overall accuracy, for the reasons you've stated. However, the purpose of the internal review was more so to perform a sanity check that the suggestions were good enough to be worth additional reviewers’ time. We see volunteer review as the next step because we think you all, as people experienced with verifiability work, bring the nuance needed to differentiate between suggestions that identify genuine issues and those that you'd consider noise. CMedelius-WMF (talk) 08:23, 30 October 2026 (UTC)
For question 1, I agree with MBAB, an automatic tool should avoid frequently edited articles (if someone wants to run it manually, they know what they might be getting into). I don't see a problem with running these on all lists, if the question is whether the tool can understand table sourcing then have it avoid tables on all articles. For question 2, the linked diff is very helpful, especially as it will pick up WP:TSI issues where sources and text get separated by later edits. For 3, please include a nudge for an editor to use the |reason= parameter in fv. For 4, shouldn't the tool simply avoid those situations? More broadly, there seem to be different categories of errors that could be picked up, and it might be useful for the model to distinguish. Of the four "does not support claim at all", the first seems a case of somehow putting in the wrong units. I've found these sorts of numeral mismatches something that models are good at picking up with relatively few errors, if the model can figure out if something counts as a numeral mismatch that might provide a useful subset. The rheumatic fever is another sort of mismatch, worth flagging and seems correct in this case but it seems vulnerable to an llm not understanding wider context. The nave example asilvering has mentioned above, our nave article describes "nave" as having sensu strico and sensu lato meanings, this is perhaps an llm not understanding context and being overly prescriptive. The fourth example is a mix of numbers and prose, harder to classify. However, I don't see how it is distinguished from "does not support claim fully", as the source does support other parts of the text, such as the individual being unhurt. CMD (talk) 23:11, 29 October 2026 (UTC)
In general, I like these next steps. I think that they're reasonable and would allow a much better analysis of reliability. I would guesstimate that in my own experimentation with Claude, about 75% of its suggestions on source-text matches are accurate, so your findings so far roughly track my own experience. In terms of answers to the questions, I think a cap on suggested edits per-page, per-editing-session, is reasonable and that a link to a relevant passage would be helpful. I think if the model/suggestion cannot access a source, it should not take any action to avoid a situation where a new editor also cannot access the source and improperly removes a valid claim. ThadeusOfNazereth(he/him)Talk to Me! 23:39, 29 October 2026 (UTC)
Adding support for dismissing suggestions [1], potentially reframing the suggestion as a neutral spot-check [2], deciding what (if anything) to communicate within the UI when the model is unable to access a source [3], enabling volunteers to configure what wiki page the feedback people share via the suggestion's built-in "Report feedback" function gets published on [4], revising what articles the suggestion is not shown on [5][6[7]...to me, these all sound like important topics to revisit after we've made the initial dataset available to you all and before we consider a default-on deployment of any kind.
In line with the above, you can expect the following...
Tomorrow:
We will share a spreadsheet containing ~14,000 source verification suggestions
Continuing to respond to points you've raised and that we've not yet responded to
Please let me know if anything here brings questions/concerns to mind. PPelberg (WMF) (talk) 00:21, 4 November 2026 (UTC)
Updates
1. The experimental source verification suggestions are now enabled for experienced editors who have opted into both A) Suggestion Mode and B) experimental edit suggestions. To see the suggestion in action, please do the following:
Visit Beta Features and enable the Suggestion Mode beta feature
Visit Editing preferences and make sure the Enable experimental edit checks and suggestions setting is enabled
2. The 14,000 sample source verification suggestions can be viewed in this spreadsheet
Asks
For any issues you notice with the suggestions, please use the feature's built-in Report a problem function (pictured) and How to report issues with a suggestion please post any patterns you're noticing on User talk:Alaexis/AI Source Verification/Suggestions. PPelberg (WMF) (talk) 00:33, 5 November 2026 (UTC)
I just did a handful to check that this is working, and it worked as expected. These two were interesting because they helped me fix minor issues in the article text: List of fictional ships (fixed a copy-paste mistake), Beef clod (removed a questionable claim). Dreamyshade (talk) 09:08, 5 November 2026 (UTC)
Great to hear that, thanks for the feedback! Alaexis¿question? 09:57, 5 November 2026 (UTC)
Not a problem with the tool per se, but should we change the prompt for the lead. A frequent mistake is that the lead summarises the body, and someone places the wrong citation for a claim supported later. We want folks to check that first before removing the claim. In solidarity, —Femke (talk) 🐦 17:41, 5 November 2026 (UTC)
@Femke to confirm: would it be accurate for me to think the following?
1. You think it makes sense for the suggestion to ignore (read: not evaluate) article lead sections
2. You think this because, based on what you've observed, people place citations within the lead that do not support their associated claims even tho said claims are properly cited/source elsewhere in the article PPelberg (WMF) (talk) 23:44, 5 November 2026 (UTC)
It is a question of what the "associated claims" are defined as. A citation in the lead may specifically only cover say the word immediately before it, rather than the whole sentence. (This is not the way citations are expected to work in the body.) CMD (talk) 23:47, 5 November 2026 (UTC)
@CMD, mmm. Okay. Got it. Thank you for explaining that. So you're aware: if you all were to decide the suggestion ought to ignore lead sections, you could make that happen by setting the on-wiki config for the source verification suggestion to ignoreLeadSection = true. PPelberg (WMF) (talk) 00:06, 6 November 2026 (UTC)
That is very useful, I personally would prefer tasks were shifted towards the body rather than the often given more attention leads, but moving off-topic from this particular use case with a specifically technical reason to avoid leads. CMD (talk) 00:09, 6 November 2026 (UTC)
The special rules for citations in lead sections are at MOS:LEADCITE. Most claims in a lead don't need to be supported by a citation if the claim is supported in the body. So if a claim in a lead is only partially supported by a citation (for example, Femke may have run into row 4014 in the spreadsheet), that may not be a real problem. But if a sentence or clause in a lead is contradicted by the citation, or if the citation doesn't support anything in the sentence or clause, that should be checked, but the editor should also look at the material and citations in the body while checking it, instead of just removing it. Summary: it's complicated, and I agree with skipping leads at least for the first iteration. Dreamyshade (talk) 00:16, 6 November 2026 (UTC)
Some more complications here. Eventually, we do want an adjusted lead check, I imagine, as errors in the lead are the most consequential.
If there is a quote, it needs to be supported for instance. But what needs support is messy in a way that experienced editors something make mistakes in, and would likely differ significantly by language edition. So turning it off temporarily makes sense. —Femke (talk) 🐦 08:31, 6 November 2026 (UTC)
@Dreamyshade,@Sadads, @Femke, totally agree with your points, the leads demand special treatment. I've tried to implement it in the user script first and it was surprisingly non-trivial. There are many possible combinations since leads also include inline citations, so the claims should be checked against the body and against cited sources. The challenge is not just to come up with an algorithm but also not to confuse the user of the script. Hopefully I'll release a new version of Source Verifier (not edit suggestions) and I'd be grateful for testing and feedback. Alaexis¿question? 11:30, 6 November 2026 (UTC)
If it's helpful to have an example of the tool running into a LEADCITE issue, you can see this one I've reported. Sdkbtalk 16:35, 9 November 2026 (UTC)
@Dreamyshade, @Sdkb, @Femke, @Sadads, please try the latest version of the userscript which checks lead against body and lists unsupported lead claims separately. The UI will probably change soon, it's now too crowded for my liking, but the logic should be fine. Let me know how it works. Alaexis¿question? 22:19, 9 November 2026 (UTC)
I had to fiddle with the relationship to references a lot in the design of: User:Sadads/Lead_Balancer -- one of the steps actually does a "lead to section comparison and checks if there is corresponding content elsewhere in the article. According to my Claude (which built most of it): "Lead-to-section mapping (no AI). coverage.js:112-147 scores each lead sentence against each body section with tf-idf cosine similarity. Words found in every section, and the subject’s own words, are ignored. A sentence only maps to a section if its shared words add up to real evidence, such as a heading word, a word unique to that section, or two specific words. Otherwise it stays unmapped (sectionIndex: null). This is a similarity heuristic, not a check for citation support." @PPelberg (WMF) -- you could do a word similarity hueristic for checking if the lead sentence without a citation, is well covered by cited material elsewhere in the article, even if its not a 1:1 match. Sadads (talk) 00:12, 6 November 2026 (UTC)
@PPelberg (WMF) I will send you the recommendation from Claude on the hueristic for lead section citations, which could be implemented as a slightly different flag for uncited lead sentences, Sadads (talk) 00:18, 6 November 2026 (UTC)
With permission, sharing the results of the types of error found over summer in a sample of climate change related articles. The overall error rate was the same at about 70%. Some of these are discussed above already.
Error Type
Description
Frequency
Partial support error
The tool is not correctly describing labelling claims where partial support is present
38
Website not found
URL does not link to a currently active website
30
Book
The source is a book and so is not readable for this experiment
23
Omission
The AI claims information is not in source, when it is
19
Graphical
AI tool failing to read information that is in a graphical format
14
Implication
The AI does not infer a logical implication that a human could reasonably understand
12
Context
The AI is not properly reading relevant context to an article
11
Structural Error
The AI tool is being confused by non-standard citation/article structure
7
Paywall
Source is paywalled
6
Contradiction
The source contains information that contradicts the AI's interpretation
5
Source error
Source is not found or otherwise unreadable
4
Landing page
The citation links to a landing page rather than the source itself, thus confusing the tool
2
I've not checked, but I imagine that when the source is unavailable, the SuggestionMode already ignores it. Some errors may be fixable by the prompt.
I think it was context where the AI often doesn't read the date the article was published, so that sentences like "Yesterday, the prime minister said X" translated to "On day X, the prime minister said X" would be flagged as incorrect.
The structural error, e.g. citations around tables or in front of bullet points, are another one where a prompt can help. At least, in front of bullet points (where we put the citation before the text in general), may be easy to include in the prompt or exclude from the SuggestionMode selection.
We can see captions, and can perhaps prompt that statements that seem to be present in the graphs should not be flagged as incorrect. Not all captions start nicely with "Figure 1" however.
Fixing the 'implication' (e.g. simple maths) and contradiction may simply require us to use a better model.
The biggest error is interesting, as the tool, in its text, correctly says that something is partially supported, but the verdict differs from the explanation. I imagine such an almost-hit again would simply require a slightly smarter model. —Femke (talk) 🐦 09:15, 15 November 2026 (UTC)
Thanks, that's very helpful. Speaking of smarter models, have you been using the default model all the time? Alaexis¿question? 10:21, 15 November 2026 (UTC)
I have yes. The others require subscriptions, don't they? —Femke (talk) 🐦 10:25, 15 November 2026 (UTC)
Mostly yes. There are two free options now, Qwen hosted on Liftwing (default) and GPT-OSS hosted on HuggingFace (used to be the default until not long ago), so just wanted to make sure you didn't change the model in the settings. Alaexis¿question? 10:30, 15 November 2026 (UTC)
@Alaexis, do you have a sense of which models are the most useful for this at present? In solidarity, asilvering (talk) 19:30, 15 November 2026 (UTC)
@Asilvering, last time I checked, Gemini 3.7 was the best but the two free options (Qwen 3.6 and GPT-OSS-20B) weren't that far behind. The most useful metric is "Supported-vs-rest (strict)" - this is the% of cases in our benchmark dataset for which the model's binary verdict (SUPPORTED VS EVERYTHING ELSE) is correct, you can see the numbers here. I checked Qwen 3.8 when it became available on LW and found it to be slightly better than 3.6. Note that the benchmarking dataset is not representative (on purpose), so these numbers are only for comparing different models. Alaexis¿question? 20:48, 15 November 2026 (UTC)
How easy is it to retest the accuracy upon a changed prompt? I wonder if we can change the following (suggestions are where claude, chatgpt and gemini sort of agreed)
Make the output json give the source_quote first, then the number, then the verdict. That way, we might prevent the number 1 error of the verdict being wrong but the reasoning right. It may force the model to reason before deciding. The description of the source_quote would change to "Quote the passage that comes closest to supporting or contradicting the claim"
Give more examples of things being right, e.g. very simple implications
I'm less sure about this, but Claude said the prompt for unavailable sources might be overly broad. No text to quote might be interpreted as no relevant text to quote (e.g. an unrelated source), instead of no text available.
Good ideas, definitely worth checking. It's not too hard, I'm now testing your first suggestion. Feel free to fork the repo and try your other ideas yourself (the benchmark dataset is here and the readme is , and the LiftWing and Hugging Face models are free, so no API key is needed). Alaexis¿question? 16:09, 16 November 2026 (UTC)
@Femke, implemented your first idea in the userscript, it reduced the number of wrong SOURCE UNAVAILABLE verdicts, thanks! Alaexis¿question? 21:13, 18 November 2026 (UTC)
Cool to hear. Not the category I expected improvement in, but I'll take that as a win 😁. —Femke (talk) 🐦 21:29, 18 November 2026 (UTC)
How about a few confusion matrix displays? Ideally a top matrix for summary with 3 or 4 below it. I suggest avoiding complex representations so a quick view can be possible. Yesterday, all my dreams... (talk) 09:39, 16 November 2026 (UTC)
WMF's amicus brief in In re: OpenAI, Inc. Copyright Infringement Litigation
The Wikimedia Foundation filed a motion to submit an amicus brief (Commons link) in the consolidated In re: OpenAI, Inc. Copyright Infringement Litigation case (including e.g. The New York Times v. Microsoft and OpenAI). There is also a summary on Diff.
My read (IANAL) is that the WMF's position boils down to:
Scraping is about access and Terms of Use, and is not a "use" in the sense of "fair use".
Using data to pre-train a "general purpose" model is fair use.
Retrieval at query time is not fair use.
And now here's my take on these positions, and some implications (again, IANAL):
The claims of the publishers that tie copyright to acquisition fail, but server load is a consideration. This is already more or less the WMF's de facto policy.
Disagrees with the New York Times' (and others') core claim. This is the surprising position in my view, both because of the claim itself and even more so because taking a position on this matter just doesn't seem like it was necessary. I would be curious to hear more about why the WMF did so. The Diff post says it's to support smaller-scale/independent AI development. We do rely on machine learning for a variety of maintenance tools, as the brief's conclusion talks about, but there doesn't appear to be any attempt in the brief to distinguish between those small/open developers and the largest corporations that stand to profit the most. #3 claws back some of the traffic lost to AI interfaces, but #2 concedes the rest of it is ok. More importantly, this means prioritizing developers above the journalists and publishers that we depend on for our citations. It's not an easy needle to thread, but it also didn't seem like this particular needle needed threading right now.
This is the consequential position for us, because a chatbot would be able to retrieve Wikipedia content, but would need to provide attribution or a backlink. That would be a Very Good Thing, though I have no idea what the effects of ShareAlike would be within a chatbot answer. For the non-free stakeholders, this would mean retrieval needs a license, which is good for them. Unclear what it would do to retrieval practices in general. Overall, this seems worth the brief itself.
Almost certainly, the third point was the main point, but that leaves the question of what purpose the other two serve. Perhaps the combination reinforces Wikimedia Enterprise? Do the first two make it easier to take the third position? Is there also a strategic-pragmatic move here, knowing that the claim that training is fair use is almost certain to be held up in the long run (given how much of the US economy could be argued to depend on it right now), so conceding that to gain a better position for #3?
I hope none of this sounds cynical, and I hope I haven't misrepresented anything. I found #2 perplexing, but I have a lot of faith and respect in WMF Legal, who I concede may be playing chess while I'm playing checkers. Just hoping for more context. —Rhododendritestalk \\ 19:16, 30 October 2026 (UTC)
I'm also concerned about #2. As I understand it, the thinking is this: if no one can train open source models because a) models trained on copyrighted material cannot be used to generate free material and/or b) it is extremely expensive to acquire training data and small-scale developers can't pay for it, the only game in town will be the big AI companies with the ability to pay, and this would be bad for the free culture movement broadly speaking. In solidarity, asilvering (talk) 21:16, 30 October 2026 (UTC)
This is pure speculation, based on nothing but gut feeling, but one possibility about #2 is that WMF is afraid that if training an AI model on copyrighted material is viewed as copyright infringement, writing a Wikipedia article with sources that happen to be copyrighted would be infringement too. There not being a light-and-day difference between "AI training" and "writing adequately sourced Wikipedia articles". Jo-Jo Eumerus (talk) 13:19, 31 October 2026 (UTC)
The crux of the copyright complaint for the training part of the case has to do with making copies of the copyrighted content first, even if the output isn't a direct violation. Still, that's not a bad take - that the WMF could be taking principled opposition to a copyright/ownership claim that's concerningly broad, given the work we do? —Rhododendritestalk \\ 13:46, 31 October 2026 (UTC)
Makes sense, if it were established that taking information from a copyrighted source was enough to make a copyright infringement, this would seriously imperil Wikipedia's content. Although I don't get the impression that "copies of the copyrighted content first" are the issue per se, at least per The New York Times v. Microsoft and OpenAI? More when (parts of) these temporary copies end up in the reply to a prompt, although from the way the complaint about competition is worded, it may extend to replies that don't meet substantial similarity but share the same information. Jo-Jo Eumerus (talk) 14:06, 31 October 2026 (UTC)
FWIW the replies that contain obvious infringement are the smoking gun, so are very prominent in coverage of the case. They are indeed the subject of copyright claims themselves, but they're also direct support for the much broader claim that training involves making/keeping copies. —Rhododendritestalk \\ 14:26, 31 October 2026 (UTC)
As an experiment, I asked Claude to write an article for me. The prompt I used was:
Write me a Wikipedia article about the SoHo Weekly News, which was an alternative newspaper published from 1973 to 1982 in New York. The article should be about 5000 words long and comply with the Wikipedia MOS (Manual of Style).
I used SWN as a test subject because I had written on the topic myself (shameless self promotion: SoHo Weekly News is going to be on WP:TFA in about a week). I'm not sure what I expected, but the result was kind of shocking. I'll have the WP:AINB folks breathing down my neck if I post it on-wiki, so I tossed a PDF into Google Drive. It's pretty much the poster child for WP:CLOP if not straight-out plagiarism. This may be an extreme case, however. SWN is a niche topic, so there's not a lot of long-form content out there about the paper. My article probably swamps the training corpora on the subject, so I guess it's not surprising that all Claude could do is regurgitate it back.
I get what the NY Times is upset about. The product they sell is partly their investigative reporting and partly their writing. If the LLMs ingest NYT material and spit it back out in the same words (similar to what Claude did with my SWN article), that's clearly copyright infringement.
The deeper question is what if the LLMs ingest a NYT article, understand the information it contains (leaving aside for the moment that LLMs don't really "understand" things in the way we typically use the term) and create entirely new text based on their understanding. That's exactly what I did with my sources when I wrote my SWN article. So, not copyright infringement, but possibly a violation of the NYT Terms of Service which says "The contents of the Services, including the Site, are intended for your personal, non-commercial use". And later on, "Non-commercial use does not include ... the development of any software program, model, algorithm, or other generative AI tool ..." It's really hard for me to see how what the LLMs are doing is not in violation of that. I maintain a paid subscription to the NYT. It's a contract. I give the NYT money. In return, the NYT provides me with certain services, and imposes certain restrictions on how I may use those services. If I don't like the restrictions, I'm free to cancel my subscription and stop using the services.
While I'm certainly sympathetic to the WMF's claim of "fair use", I don't see how that overrides the limitations imposed by, for example, the NYT TOS. I'm also torn between wanting the WMF to be right and wanting the NYT to be right. For sure, I'm all about "information should be free", and I'm certainly preaching to the choir on that one. But I also value the information I get from the NYT (and other papers to which I maintain paid subscriptions). If the NYT is ultimately unable to maintain profitability, they will go out of business and I will lose access to a service I value. I don't want to see that happen. RoySmith(talk) 15:50, 31 October 2026 (UTC)
That sounds like an issue with ToS violations (->contract law?) and not with copyright law, though? Even if it was found that OpenAI violated the NYT TOS, that would not imply that this violation constitutes copyright infringement. This lawsuit seems to be about copyright issues not ToS. JoJo Eumerus mobile (main talk) 16:23, 31 October 2026 (UTC)
In my (non-legal advice) understanding, you are correct that fair use concerns do not override agreed-upon contract terms. As JoJo Eumerus says, the two are separate concerns. If the companies obtained their copies of the copyrighted work without entering into a contract with the publisher, though, then only the copyright concerns are applicable. isaacl (talk) 16:46, 31 October 2026 (UTC)
One additional complication is the way many corporations interpret "agreed-upon contract terms". By clicking on any link to this web page you agree to... We can change this agreement at any time without notice...
There is a refrigerator maker that is trying to enforce a "by opening this box you agree to binding arbitration" notice when the box is removed by the installers and thrown back in the truck before they wheel the fridge into your kitchen. --Guy Macon (talk) 01:57, 1 November 2026 (UTC)
I've read the brief. Here are my personal comments: I'm feeling Wikimedia Foundation is standing on the wrong side and it makes me doubt whether I should contribute to Wikipedia again.
WMF argued for a blanket fair use for AI pre-training, but they missed many technical facts. First, the current AI models are dominated by a few Big Tech (OpenAI, Anthropic, Google, Meta, etc.) because the main cost of AI training is the computing power and hardware, not licensing. Making the AI training fair use doesn't benefit smaller companies, especially those who already negotiated licenses for their training data. Second, WMF would be allowing AI trained in order to create a direct competitor to exist (there is one already, Grokipedia). I take no position on whether Grokipedia is allowed to rival Wikipedia while trained on Wikipedia content, but some other Wikipedia editors might concern the ethics of that practice. Let's see.
Third. Wikipedia content is licensed under CC-BY-SA. CC licenses implicitly allow AI training (disclaimer: IANAL) although the output might be constrained to require attribution (and, for share-alike licenses, share-alike) if it looks so much like a derivative. Fair use for AI training won't help Wikimedia's mission for a free and accessible knowledge at all. --Explorer09 (talk) 02:23, 3 November 2026 (UTC)
I think I would have a few questions there. First, do OpenAI and the other chatbots respect restrictions such as robots.txt or other metadata restrictions? If they don't, they're actually accessing a computer system when they're not authorized to, and under US federal law, that can be a felony. I don't think just reading something, whether it's read by a chatbot or a person, constitutes copyright infringement, but it could violate other laws if they're just slurping things up in violation of the TOS of sites they visit. And if they're doing close paraphrasing or directly reproducing them for their users, well, that could certainly be infringing. SeraphimbladeTalk to me 00:08, 5 November 2026 (UTC)
Just on a couple points: robots.txt is a purely voluntary convention, and there's ample evidence of crawlers ignoring it. And hiQ Labs v LinkedIn means claims based on scraping publicly accessible data need to rely on something other than CFAA. —Rhododendritestalk \\ 03:02, 5 November 2026 (UTC)
Training a model seems a textbook example of a transformative use which should be fair use; it is also a clear parallel to learning and being creatively influenced by what we read and hear and experience. Points 1 and 2 seem like the right position, legally and culturally, for a knowledge society. Point 3 seems overstated in the brief -- retrieval at query time for confirmation or sourcing, is also definitely a fair use; as are short quotes of a length we would allow in an article (i.e. the volcanic cloud was described by <source> as "most likely the highest in over a century"). Any use at query time that would qualify as fair use if I was adding a paragraph to an article should be fiar use in the output of a model.
I would have liked this brief to more carefully frame the types of reuse and derivative works that fall outside fair use, and to separately note that norms around attribution need to adapt: fair uses of source materials already need to be attributed so as not to be plagiarism, and that norm should be strengthened and extended to cover AI outputs that may draw on a panoply of sources.
Overall I'm glad to see WMF engaging with these public discussions but we need a clearer articulation of the abject failures of the copyright regime, and how we need something better to further our society's cultural and educational goals (freedom of panorama and no gatekeeping of public domain works by intermediaries, at a minimum). Without that, when we take positions that will be warmly embraced by the (c) lobby, they can be used in the name of Wikimedia to shrink and enclose standard affordances for sharing knowledge about the world: including fair use, first sale, and the public domain. –SJ+ 18:43, 9 November 2026 (UTC)
I wish WMF would not just walk into a legal battle zone to which they had not been invited. It costs money, money, money. The only winner will be the lawfirm of Dewey, Cheatem & Howe whoever they may be representing. Yesterday, all my dreams... (talk) 09:37, 11 November 2026 (UTC)
My position disagrees with SJ arguing that training is transformative use and thus is "fair". My position is closer to US Copyright Office's position on fair use: that whether the AI training is fair use depends on the ultimate purpose of that AI model, including how the end users would use it for. There's no blanket fair use for AI training, and AI training is not always unfair either. It depends on how the AI is further used for.
The closest example for Wikimedia Foundation on how an AI could be an unfair use is Grokipedia, since Grokipedia is intended to compete with Wikipedia, while trained on Wikipedia data. It's just fortunate that WMF and Wikipedia are not-for-profit, and are not financially stressed to sue Grokipedia, but trying to defend that as fair is overstepping the foundation's purpose. I really suggest WMF should stay out of this and not pretend they are smart.
Wikipedia position is also impractical in another manner: When the AI can regurgitate copyrighted works, especially poems and lyrics, such an output infringement should make the AI companies liable instead of pretend it never happens or shift all the responsibility to end users. Such an output infringement is an infringment, and is an important factor on judging the "fair use" of AI training. In other words, AI can contribute to infringement through regurgitation. And to stop this contributory infringement from AI, denying fair use of AI training is the only way. Really, because any post-training AI safeguard can fail. Explorer09 (talk) 13:44, 14 November 2026 (UTC)
I am no legal expert, but I am somewhat sure that "And to stop this contributory infringement from AI, denying fair use of AI training is the only way" isn't how laws usually work. Only the AI output that is copyright infringement is actually copyright infringement. Otherwise, any person reading a book would be committing copyright infringement because of the mere possibility that they might remember enough of its text to write down a copy that violates copyright. Like, for example, by writing a WP:CLOP Wikipedia article. This is a point that the article you cite mentions: Contributory copyright infringement#Sony Betamax case and the Grokster case. As for the status of an AI that output a copyright infringement, I am not actually sure that it's settled law and jurisprudence how to handle these cases. I don't think that "the AI company is liable" is an unreasonable approach, but well, is it the approach sanctioned by laws & courts? It makes sense that the WMF would take a position here, lest the cookie crumble in a way that is bad for the encyclopedias. Jo-Jo Eumerus (talk) 08:27, 15 November 2026 (UTC)
AI regurgitation is different from the Sony Betamax case that AI companies usually cite. With the Sony Betamax case, the tech is "neutral" - the VCR only copies copyrighted expressions if the end user feeds in that expression. It's not like Cox v. Sony either as the ISPs are also "neutral". Gen AIs, however, can suggest copyrighted expressions without an explicit prompt from the user (it's demonstrated before, e.g. in this article). Such an action can be ruled by a court as a form of "inducement", thus making the AI companies liable. How can you say that a tech can be "fair use" on training while it can induce infringement for downstream uses? Many people would find that ridiculous, and I guess the judges will find that ridiculous as well. Explorer09 (talk) 13:22, 15 November 2026 (UTC)
Whether and how frequent the AI can reproduce copyrighted materials without the user's explicit prompt is a fact based analysis and I should leave that question to the court to decide case-by-case. You didn't get the difference between Cox v. Sony and this In re OpenAI Copyright Litigation case yet. It's this: ISPs don't actively suggest what copyrighted material should be presented to user when they send HTTP requests. ISPs are passive entities that only forward user's requests and forward the websites' responses, no matter whether the content is infringing. If a generative AI only does that (passively forwarding requests instead of actively generating infringing materials), then even I would consider that a fair use. Unfortunately I've read the NYT v. OpenAIcomplaint and New York Times didn't just allege that. Explorer09 (talk) 14:47, 15 November 2026 (UTC)
See, that sounds like a nitpicky difference that is unlikely to make a difference in court. In other contributory copyright infringement cases, courts inferred intent and effect from a totality of indicators, not just one point. Moreover, if you (or NYT) are citing examples of individual outputs, the "And to stop this contributory infringement from AI, denying fair use of AI training is the only way" isn't how laws usually work problem comes back. Jo-Jo Eumerus (talk) 17:02, 15 November 2026 (UTC)
You didn't present any counterargument about your "isn't how laws usually work" part. Explorer09 (talk) 02:04, 17 November 2026 (UTC)
What you describe as "not how laws usually work" is absolutely how laws usually work. It is the sort of stupid shit that lawmakers and courts do do all the time. You go on to describe how the proposed legal remedy doesn't make sense and will have unintended consequences, which are attributes found in many, many laws. See ] for a humorous list containing many examples. --Guy Macon (talk) 03:33, 17 November 2026 (UTC)
Yes, but the inherent indeterminacy of court cases is also well known. Please do a search "what the judge had for breakfast". Yesterday, all my dreams... (talk) 11:55, 18 November 2026 (UTC)
Change to Wikimedia log-in security
I was recently locked out of my account for a week because the email address associated with my account had expired.
I added an email address 14 years ago, and it was long dead.
There was no warning..."hey, add an email to your account!"...just a lock out.
The security feature for logging-in needs to be changed so there is a warning to logged-in users that a working email needs to be associated with their account. Magnolia677 (talk) 15:14, 1 November 2026 (UTC)
Thanks for raising this here, and I'm glad you were able to recover your account. We probably should consider something that asks users to reconfirm their existing email and makes clear that it could matter, especially for users like yourself whose emails were added long ago. We added a banner for unconfirmed emails earlier this year, but not for confirmed-a-long-time-ago emails.
As a side note, you can avoid email checks by enabling 2FA - if you then also add a passkey, you can do passwordless login, which is the easiest thing we offer. EMill-WMF (talk) 21:46, 1 November 2026 (UTC)
I was literally locked out because my email had long expired. I spent the week volunteering at my church, spending time with family and friends, exercising, and reading classical novels. It was a horrible week! I'm hoping a warning can be sent out so others don't have to suffer like this. Thanks! Magnolia677 (talk) 22:23, 1 November 2026 (UTC)
You can prevent this by not registering an e-mail address. That has several disadvantages but, if the powers that be stubbornly insist on providing no other way to avoid excessive security, it remains a useful tool. Certes (talk) 09:32, 2 November 2026 (UTC)
@Certes: We are "the powers that be". If we send a message that the sign-in policy needs changing, then it will change. All that's needed is the following: "you will be locked out in a week if you don't add a working email to your account". Easy peezy. Magnolia677 (talk) 11:21, 2 November 2026 (UTC)
"There is always a well-known solution to every human problem—neat, plausible, and wrong." -H. L. Mencken
The above is an obvious wrong solution. --Guy Macon (talk) 17:25, 2 November 2026 (UTC)
H. L. Mencken was a racist and antisemite. Who cares what he thinks. The sign-in policy needs to be corrected. Perhaps a message sent to all registered users talk pages, or a one-week warning before lock-out. Magnolia677 (talk) 19:13, 2 November 2026 (UTC)
You might benefit from studying our article on Genetic fallacy. That, and perhaps some actual evidence or argument other than "Something needs to be done. This is something. Therefor this needs to be done"[CitationNeeded] --Guy Macon (talk) 20:06, 2 November 2026 (UTC)
I don't care about Mencken or genetic fallacy or any other useless off-topic crap. I care about people being locked out of their account without warning, and finding a workable solution so they are about to access their account. Magnolia677 (talk) 20:59, 2 November 2026 (UTC)
if you want to play that card... your quote is not an argument, just an opinion. It's an argument from authority, and there is nothing in it to be dismissed or disputed as no argument has been presented why it would apply here. "I have this solution" - "Mencken says that there is always a wrong solution". Yeah, so what? Try posting some actual arguments based on the actual discussion, instead of lecturing people on what gems from your wisdom might benefit them. Fram (talk) 15:46, 4 November 2026 (UTC)
Out of curiosity, is this a message to all users or a message at the log in page, Magnolia677? --Super Goku V (talk) 17:11, 4 November 2026 (UTC)
@Super Goku V: It was a message at log in. I entered my username and password...all good...then got a pop-up saying I needed to check my email for a log-in code. What?? I hadn't used the email associated with my Wiki account in 10 years, and it was long dead. So I had to fill out a form and wait a week. No warning on my talk page like..."better have a working email or you'll soon be locked out". Bupkis. It could happen to anyone. Very traumatic. Magnolia677 (talk) 19:28, 4 November 2026 (UTC)
I was just referring to your suggestion. Is your suggestion to have a message sent to all users to their talk page or a message on the log-in page? --Super Goku V (talk) 19:35, 4 November 2026 (UTC)
At log-in would be most attention getting, along with a scary-looking icon. Thanks for your help with this. Magnolia677 (talk) 19:51, 4 November 2026 (UTC)
Discussion on Meta about funding the LGBT+ User group
Editors interested in this project may also be interested in multiple discussions going on now about funding the LGBT+ User Group for the next three years. As I was not aware of this group until recently, and not very familiar with how WMF funding works either, I put together the following intro to help me, as the linked discussion page addresses a topic I was pretty unfamiliar with, and I needed some background to understand the underlying WMF structure and backstory. Maybe it will help you, too.
Wikimedia LGBT+ is a "Wikimedia user group that promotes the development of content on Wikimedia projects which is of interest to LGBT+ communities and supports LGBT+ individuals who engage in Wikimedia activities". It is a recognized Wikimedia affiliate, in this case, a Wikimedia User Group, since 2014. There are 143 user groups, overwhelmingly local groups for a given geographical area (country, region, city), but there are also a few user groups for common interests, such as Art and Feminism, Classics, or Education. The LGBT+ User Group is among the latter. (There are also affiliates that are not user groups, like chapters, but that is o/t for here.)
Among other things, WMF affiliates, including user groups, can apply for funding from the WMF to support their goals and activities. The WMF has several models of funding, such as the Rapid Fund, the General Support Fund, the Multiyear Funding program, and others. The LGBT+ User Group has received funding from the WMF in the past, and has applied for a continuing grant to support their activities for the next three years; this grant proposal is entitled, "Sustaining Wikimedia LGBT+ 2026–2029".
Now we come to the point of this message. This grant proposal has stimulated some lively discussion on the grant proposal talk page. There is a multiplicity of viewpoints, and I found it tough going, given my relative unfamiliarity with the backstory (it's an iterative process for me), but I feel it's important to understand it as it involves questions about who or what should be funded by the WMF to promote the goals of supporting LGBT+ content and community. In an effort to help me follow the conversation thus far, I asked a chat bot to summarize the main viewpoints, and this was the response; all the usual caveats about AI errors, hallucinations, and misinformation apply.
I'm hoping that someone will provide a quick summary of what grant applications are current. Of course we all want people to be nice and to write good articles, but I'm astonished that donations to Wikipedia might be used to fund such basic activity. Anyone with evidence of harassment can get the harasser permabanned by emailing either the WMF or the Arbitration Committee. Johnuniq (talk) 08:19, 6 November 2026 (UTC)
Security update: Many Wikimedia tools were taken offline because of a security vulnerability in PHP. This affected many websites worldwide. Toolforge and Cloud VPS have been back up since October 22. Many important tools have been gradually restored. Some tools need the respective volunteer maintainers to restart them. Follow the work on Wikitech.
Wikipedia Year in Review 2026: This year's Wikipedia Apps Year in Review is in progress and you can help make it available in more languages to readers around the world by helping with translations. Here's how:
Around the Globe in ESEAP: Connecting 32 geographic areas and 64 language editions of Wikipedia across East Asia, Southeast Asia, and the Pacific. See how the region is creating spaces for active editors to build relationships.
Notifications Experiment: In the coming weeks, the first of two notifications experiments on Android will be launched. The experiment will test whether personalized Discover reading list notifications will encourage them to return to the app. The three-week experiment will include English Wikipedia readers who have opted in to notifications. Learn more and share your feedback on the project page.
Reading recommendations: An ongoing experiment is testing article recommendations for new account holders who also identify as readers. This aims to encourage new account holders to read and return to the website regularly, with the goal of increasing internal referrals by 1%. See all live, upcoming, and completed experiments in Product & Technology.
New search experiment: The first of four experiments in Phase 2 of Semantic Search is running in the Wikipedia Android and iOS apps for Arabic, French, and Japanese Wikipedias. Participating readers can search inside articles and open quoted passages directly in their source articles, no answers or summaries are generated. Feedback is welcome on the project’s discussion page.
Share Cards: The Future Audiences team is planning to bring Share Cards to Wikipedia on mobile. This feature gives users the option to share a visually appealing card with friends, based on the article they are reading. The card contains the article’s title, image, opening text, and related attribution, and links back to the article for full reading.
Tech News: The latest highlights from Tech News weeks 44 and 45 include the default renderer for math formulas has changed. See also the 59 community-submitted tasks that were resolved over the last two weeks.
New Toolforge features: As part of Tools Platform's work to improve the reliability of Toolforge-hosted tools, two new platform features are launched: (1) Toolforge alerts let tool maintainers receive email notifications when any of their tools is encountering a common error condition; (2) Toolforge extended logging capabilities let tool maintainers retrieve logs for events like job creation, deletion or deployment failure, with a new CLI toolforge logs, at the same time that they retrieve their job logs.
Work also continues to make sure Citoid does not get blocked by publishers who are starting to block bot traffic to manage the impact of scraping. In September, we worked with Reuters and the Library of Congress to allowlist Citoid. You can track our progress with other publishers on Phabricator.
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. If you have feedback or suggestions about the bulletin, let us know at foundationbulletin@wikimedia.org. For questions about the Wikimedia Foundation's work, contact us!
Awareness campaign about the importance of Wikipedia in the age of generative AI
The number of human visits to Wikipedia is decreasing because of the use of generative AI to look for information. While Wikipedia is not a business and its main goal is not to maximize the number of visits, it's important that the public doesn't see generative AI as a replacement for Wikipedia (it may be a replacement for searching very basic information about simple facts, but it's never a replacement for Wikipedia as a whole). This is not only for the benefit of the Wikimedia movement and WMF, but also for the good of the wider public. I think a public awareness campaign by WMF would be very helpful here. While the exact slogans will be better left to experts in communication, I think that sentences such as The largest work ever written and By humans, for humans would be good ones for use in the campaign. The campaign should be able to communicate ideas such as the ones expressed in this essay, and, probably, additional ones. MGeog2022 (talk) 13:47, 18 November 2026 (UTC)
WMF has already started running with a "Knowledge built by humans" slogan in some campaigns, see eg. Facebook, Diff. CMD (talk) 14:41, 18 November 2026 (UTC)
An interesting question is what message the WMF sends in its most effective method for reaching the general public; annoying obtrusive banner ads that they hide from logged in users (see eating your own dog food).
They could use the banner ads (or some percentage of them) to attract new editors, or they could make it all about donating more money. The first addresses a serious problem the Wikipedia has, while the second supports them being able to fund pet projects and grateful grant recipients. --Guy Macon (talk) 15:20, 18 November 2026 (UTC)
We do not (yet) want to accept that generative AI will eventually be added to the List of locust swarms. WMF can hold up all kinds of banners to warn about the locusts, but the locusts will not pay attention. C'est la vie. Yesterday, all my dreams... (talk) 17:00, 18 November 2026 (UTC)
As is unfortunately necessary to explain every time that slogan gets mentioned, it's catchy but false (Wikipedia is written by humans, bots, LLMs and at least most combinations thereof; it is written for everybody, humans and non-humans alike). We are not, and should not be, in the business of using falsehoods to promote ourselves. Thryduulf (talk) 17:22, 18 November 2026 (UTC)
Where exactly are you getting 'written for non-humans' from? Which non-human 'everybodies' are you referring to? Martians? AndyTheGrump (talk) 17:33, 18 November 2026 (UTC)
Whether you like it or not Wikipedia is also written for search engines and AIs. We even have a page to help the AIs and search engines (for a price): [ https://enterprise.wikimedia.com/ ] "Trusted by companies that build AI and search" --Guy Macon (talk) 17:46, 18 November 2026 (UTC)
Per any reasonable definition, neither search engines nor AI are persons, and thus don't fall within 'everybody'. As for the WMF engaging in its endless pursuit of funds through selling Wikipedia content, I'm unaware of the community ever giving its approval for the practice. I'm here to contribute to human knowledge, and not to feed the bullshit-bots. We may not be able to prevent their owners leeching off Wikipedia in the way they leech off intellectual property in general, but I see no reason why we should pander to them. AndyTheGrump (talk) 18:11, 18 November 2026 (UTC)
Whether you like it or not, Wikipedia's license allows anyone to use our content for any purpose. Wikipedia has, for well over a decade at least, intentionally output structured data, metadata, and other information in machine-readable form. Thryduulf (talk) 18:16, 18 November 2026 (UTC)
No, the license does not 'allow anyone to use our content for any purpose'. The license has conditions, which include proper attribution - conditions which the bullshit-bot owners routinely ignore, even when copying Wikipedia content almost word for word. AndyTheGrump (talk) 18:53, 18 November 2026 (UTC)
Not sure that the conditions attached to the Creative Commons Attribution-ShareAlike 4.0 License precludes using our content for any purpose. They could attribute it and still use it.
BTW, Some things on Wikipedia (such as the words you are reading right now) are not under the CC BY-SA 4.0 License. Everything I do is under CC0 Which, interestingly enough, enrages the Free Software Foundation. They believe that I do not have the right to waive my patent rights should these words happen to contain a new invention. They FSF is, as usual, full of crap. it's my choice whether to assert patent rights, not Richard Stallman's. --Guy Macon (talk) 19:21, 18 November 2026 (UTC)
I suspect that Andy is talking about what they think should happen, while the rest of us are talking about what actually does happen. And my opinions on the WMF engaging in its endless pursuit of funds are well known. --Guy Macon (talk) 18:48, 18 November 2026 (UTC)
Bullshit-bot content being copy-pasted without attribution does happen. Along with a whole slew of other things that the bullshit-bot owners are responsible for, to the detriment of human knowledge. The web is being flooded with next-word-guesser slop, sourced to nobody-knows-where, and filled with hallucinations. So yes, I'm giving my opinion on what should happen, based on what is happening. And isn't the purpose of this thread to express opinions on how we handle the situation? So yes, an encyclopaedia written by humans, for humans, seems a perfectly reasonable objective. AndyTheGrump (talk) 19:00, 18 November 2026 (UTC)
That you think it is a reasonable objective doesn't mean that it correlates with present reality Thryduulf (talk) 19:25, 18 November 2026 (UTC)
And who are you to pontificate on 'reality'? If you want to be patronising, start a blog somewhere. AndyTheGrump (talk) 19:28, 18 November 2026 (UTC)
It hasn't been written by bots in many years (as in, creating content, not doing maintenance), and while LLMs are used by some in writing, it is not allowed to create contents via LLMs and a slogan which reflects the intention and rules (and 99% of the contents) is perfectly acceptable. And as far as I am concerned, Wikipedia is written for humans. That doesn't mean that non-human processes may not use it as well, but it is not the intended target for most editors. A Lego box which states "ages 9-16" isn't lying when people outside that age range use it as well. Fram (talk) 19:23, 18 November 2026 (UTC)
"Why do you still need Wikipedia when AI can answer anything": I would add another reason here: because it's good for YOU as a user, not because AI needs Wikipedia to work:)
Maybe in the future AI, for whatever reason, could work well without Wikipedia. Would Wikipedia become useless at that moment? No. A talking intelligence, no matter how wise it is, should never be a replacement for written information. Humanity's memory has been based on written texts for thousands of years, and AI can't replace that. Wikipedia (joining the editions in all languages) is the largest work ever written. It's far more than a tool to search for information: it's a big collection of information in itself. Many details and curiosities included in Wikipedia articles are not returned by AI queries on the same subject. This was done with English Wikipedia: the same could never be done with an AI model (an AI model could be permanently preserved as computer data, but its preservation is no guarantee that a comprehensive summary of human knowledge will always remain available, since the AI model needs external sources of information to give good answers).
I love the fact that WMF is already working on this, but I think that Wikipedia's usefulness is the same as it was before generative AI, except for quick queries where AI wins, and, of course, Wikipedia's new use as a source of information for AI. MGeog2022 (talk) 21:12, 18 November 2026 (UTC)
@Sdkb-WMF, thanks four your response! The video is useful, but it focuses mostly on Wikipedia as a source for information to be summed up by AI, rather than on Wikipedia as a written source to be directly read by humans. I don't care about where people read information from Wikipedia, as long as Wikipedia is properly credited, but I think the problem is that, with AI, many people aren't reading Wikipedia's content as it is, but only a summary of content from Wikipedia, and a lot of good information that is present in the articles is lost on the way. AI in no way provides the level of detail or quality that Wikipedia does. I recognize that AI can be a "replacement" for Wikipedia if you want to read, for example, three lines of basic information about London, but it's obvious that, if you want complete information, it has nothing to do when compared with this. The good use of AI as a tool for several purposes, including getting knowledge about very basic facts, or as an advanced search tool, should not lead people to extend its usage to other purposes where it must not be used.
Finally, I think that this type of campaign should be directed towards the people who aren't using Wikipedia, by using appropriate channels for it: I think that, at this point in time, the vast majority of people who are reading (and almost all people who are editing) Wikipedia are fully aware that AI is not a replacement for it. MGeog2022 (talk) 20:53, 18 November 2026 (UTC)
many people aren't reading Wikipedia's content as it is, but only a summary of content from Wikipedia. It is amazing how fast AI ingests Wikipedia. Once a new article goes up/is indexable (not sure which LLMs use which), it seems to immediately appear in the Google AI summary, and I suspect the others aren't far behind. CMD (talk) 23:44, 18 November 2026 (UTC)
That is why they need huge, huge data centers. Algorithmically, checking every 5 days or 5 minutes is the same, but doing so every few minutes uses huge amounts of energy/electricity. That and the effort based cryptocurrency transactions consume huge amounts of energy. Yesterday, all my dreams... (talk) 07:28, 19 November 2026 (UTC)
Miscellaneous
Virtual meeting about organizing events
Hi everyone.
I'm going to be presenting as part of a virtual meeting with Crystal from WikiCurious on November 18 at 8 pm EST. It's the first outreach session of the m:Wikimedia North America Hub, although if you have questions about that initiative, I'll need to direct those questions to someone who is more familiar with its internal workings than I am.
What I'm trying to get at here is that we want the demographics of this meeting to not just be people who are active on Telegram, Discord, affiliates, etc. There is a place for us, too. And I think it's important that we have more people with extensive on-wiki experience when it comes to event planning. Clovermoss🍀(talk) 22:43, 7 November 2026 (UTC), edited to provide link to timezone convertor
Hi @Alan Colin Arce (WMCA): would you like to add this event to meta:Wikimedia North America Hub/Events? The event location is listed as online instead of US, CA, or MX, which may be why the event doesn't automatically populate in the NA Hub events list. Perhaps you can figure out how to resolve this. ༄ᨒ𖠰 Pine(✉) 03:28, 14 November 2026 (UTC)
Succession boxes for executions in US murder articles
Recently, I noticed that some articles about murders in the United States have at the bottom succession boxes for the executions, by state and nationwide. Normally, such boxes are used for clear successions (presidents, popes, champions), thiings where you literally or figuratively take over the crown: I don't think it should be used for basically unrelated things, like executions, plane crashes, ... But others disagree. Thoughts? Fram (talk) 08:57, 10 November 2026 (UTC)
Eh, are executions "basically unrelated"? They're a pre-planned thing by the state. And it goes on biography articles, but then because of BIO1E we name some biography articles as event articles even if the only thing the sources cover is the person. Now, I never liked any succession boxes, we should just get rid of them generally, but I don't think this use is worse. PARAKANYAA (talk) 16:29, 10 November 2026 (UTC)
Executed murderer 2 doesn't take over some position, title, award, ... from executed murderer 1 (and there is no reason multiple executione can't be had on the same day either). "Succession" is normally for something where there can only be one holder of the title at a time, and then it is passed to a new holder. Here they are basically unrelated events, execution 2 is in no way dependent on execution 1 and the status of execution one doesn't change after execution 2 (you have a current king and a former king of Belgium, you don't have a current executed murderer and a former executed murderer). Fram (talk) 16:48, 10 November 2026 (UTC)
"Succession" is normally for something where there can only be one holder of the title at a time, and then it is passed to a new holder that is not the only definition of succession and I do not see it written anywhere that that is the definition the succession boxes use? Executions are in a succession in that it is "a number of persons or things that follow each other in sequence". Execution has stopped and started and different laws take effect and sources frequently focus on who was executed and when in relation to each other. PARAKANYAA (talk) 16:53, 10 November 2026 (UTC)
All events of course take place in a chronological sequence. I feel it is most useful, though, only to link events within a chain of succession when there is a common history and context linking the events, in which the chronology plays a significant role. Personally, I don't think chronological order has a significant enough role to link causes of death in a chain of succession. isaacl (talk) 17:21, 10 November 2026 (UTC)
I agree with Fram. Just because events can be sorted into chronological order does not mean they form a chain of succession. RoySmith(talk) 17:29, 10 November 2026 (UTC)
Agree, and support removal. Nikkimaria (talk) 01:52, 11 November 2026 (UTC)
If we're talking about use, none of these boxes are useful at all, especially chain of succession type ones. They're formatted badly, impossible to maintain and stuck at a place in the article where no one reads them. I do not think anyone actually uses them for anything. In all cases where they are used for "chain of succession" it is also in the infobox, where people can actually look at it and isn't formatted terribly.
On its own merits I think the only use case where this isn't redundant is such successions as executions, where you wouldn't have cause to link them in the infobox. But can't we just get rid of all of them? Who uses these instead of infobox links? PARAKANYAA (talk) 18:04, 10 November 2026 (UTC)
I would agree that this seems conceptually strange in the context of executions (whether this is on the articles about the murders or about the murderers, which I am guessing also happens). I would support removing them. Andrew Gray (talk) 00:01, 11 November 2026 (UTC)
I also agree that succession boxes should not be used for events linked only by temporal happenstance. CMD (talk) 03:35, 11 November 2026 (UTC)
Succession boxes should be used only for when a person or entity replaces another person or entity in an office, role, or position. Latest person executed does not qualify. Donald Albury 16:47, 11 November 2026 (UTC)
It's natural to compare a predecessor and a successor in office: did the actions and experiences of the predecessor affect the choice and actions of their successor? Succession boxes create hyperlinks that reflect this intrinsic relevance. I don't see that the same connection exists between adjacent members in a chronological list of executions, and I don't think this is a good use of succession boxes. Choess (talk) 05:15, 14 November 2026 (UTC)
Last meals
Speaking of execution articles, another issue where I disagree with at least some of the regular editors of these articles is the inclusion of the "last meal" . It seems to me to be utter tabloid trivia to know that "Prior to his execution, Weisheit ate a last meal of barbecued ribs and Mountain Dew from Texas Corral.", but removing this was not appreciated. Does it add anything at all to know that Clarence Dixon "ate a last meal of Kentucky Fried Chicken, strawberry ice cream, and a bottle of water.". Are we any wiser about the Murder of John Edwards and his murderer when we read that "Cole reportedly ate a last meal of pizza, M&M's, ice cream and a soda"? Fram (talk) 09:59, 11 November 2026 (UTC)
Agree with Fram. Donald Albury 16:47, 11 November 2026 (UTC)
Depends on the sourcing quality, as it does with any other fact. PARAKANYAA (talk) 16:57, 11 November 2026 (UTC)
Sure but would we include "His favorite color was blue" if an extremely reliable source verified that? Johnuniq (talk) 01:35, 12 November 2026 (UTC)
I think a "last meal" is a bit more significant than a favourite colour, but where people draw the line can be subjective. When it comes to last meals, they're kind've like last words (but usually better sourced than the latter) and people tend to find that information meaningful. Clovermoss🍀(talk) 02:20, 13 November 2026 (UTC)
November 2026 Wikimedia Café: the Newcomer homepage & Home experience
The Wikimedia Foundation's Contributor teams are migrating the Newcomer homepage to a new experience called Home. This page will evolve with users, introducing them to new personalized opportunities based on their interests, and helping them develop into experienced contributors.
In November 21–22 sessions of the Wikimedia Café, Kirsten Stoller (senior product manager, Growth) and Sam Walton (senior product manager, Moderator Tools) will share an overview of this feature, plans for its future, and demos of interactive prototypes which we can explore together.
A quote which I hope will inspire your attendance or at least good wishes, from Grace Hopper: "The most important thing I've accomplished, other than building the compiler, is training young people. They come to me, you know, and say, 'Do you think we can do this?' I say, 'Try it.' And I back 'em up. They need that. I keep track of them as they get older and I stir 'em up at intervals so they don't forget to take chances."
This month's schedule:
Session A: 21 November at 16:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
Session B: 22 November at 04:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific
Pine or Kirsten, could one of you please comment on how this will impact the Mentorship program other than window-dressing like links, etc., which obviously will change. Mentorship is mentioned at mw:Home, but only that the module will move (along with the others) to their new, er, home, which is to be expected. Mathglot (talk) 23:15, 13 November 2026 (UTC)
@Mathglot Good question! Replacing Special:Homepage with Special:Home will have not include any fundamental changes to the Mentorship program. The UI looks slightly different from the newcomer perspective, but the underlying logic remains unchanged. All Mentor-Mentee assignments will remain unchanged and each wiki's current configuration is preserved: Special:CommunityConfiguration/Mentorship.
U.S. nationwide aviation ground stop on November 13
The U.S. FAA has issued a nationwide ground stop for all planes in the country today. No doubt this is notable and we will have an article about it shortly, or maybe by the time I finish typing. Turn on your TV, or see 2026 in aviation#November. Mathglot (talk) 22:44, 13 November 2026 (UTC)
Hello. There is an ongoing meta:global ban request on Metawiki for XiaoFui, who was blocked on enwiki for [...] consistent incivility and casting aspersions ever since mainspace block. Discussion is at meta:Requests for comment/Global ban for XiaoFui. Thanks for commenting. Best regards, Peterxy(talk) 11:20, 15 November 2026 (UTC)
Wiki Loves Children 2026 Central Notice Request
Wiki Loves Children will take place from December 1, 2025, to December 31, on Bangla Wikipedia to enrich its content. A central notice request has been placed to target both English and Bangla Wikipedia users, including non-registered users from Bangladesh and the Indian state of West Bengal. Thank you. — ~ Deloar Akram (Talk • Contribute) 16:43, 16 November 2026 (UTC)
Oppose targeting unregistered editors. Oppose more than one impression per week, for a total of four impressions over the course of the event. Banners are not free. Best, HouseBlaster (talk • edits • he/they) 15:49, 17 November 2026 (UTC)
Why not just make WP:EFFP the page to make reports instead of having the reports be on a subpage and having it be transcluded on WP:EFFP? Szxq (talk) 17:45, 16 November 2026 (UTC)
It's a way to protect the structural part of the page but still allow anyone to add a report. Contributors who trigger edit filters may be more likely than most to vandalise this sort of page. Certes (talk) 20:12, 16 November 2026 (UTC)
Can't we disallow changing the page's structure with the EFFPR disruption filter? Seems unnecessary to me Szxq (talk) 20:14, 16 November 2026 (UTC)
It probably is not worth the change, as it has been in that location since 2010, and many scripts would break as well. There's probably a better reason why it was moved there, but I don't know what it would be. SuperJames888 (Talk to me) 21:00, 16 November 2026 (UTC)
Why are there so many uneferenced articles?
im new to Wikipedia editing, so I'm confused why are there so many uneferenced articles? When people add/submit articles they don't add relevant references to their articles, not even one? How did it get accepted in the first place? Ajimaruyo (talk) 10:58, 17 November 2026 (UTC)
Many of those are likely old articles, some even created before sourcing was common. Most new articles do have relevant references. CMD (talk) 11:13, 17 November 2026 (UTC)
Yes, I guess in the first few years of the project the mentality was to "get text, get text" to make the project viable. Over time, junk text came in as well, and clean up is still continuing. But refs are one thing glaring errors are another, specially in tech articles, eg . Alas plenty still have that problem. And some have a couple of inadequate refs and errors, say Non-logical symbol, a simple concept, overkilled by text there . Yesterday, all my dreams... (talk) 12:05, 18 November 2026 (UTC)
WikiProject Unreferenced articles is working hard in the background to add sources and inline citations to all unreferenced articles, and we currently forecast that we'll have completed this around the middle of 2027. Do sign up to our current drive! There are barnstars, a leaderboard, and everything. An issue of Signpost earlier this year has some history about the backlog of unreferenced articles on English Wikipedia. Cheers, SunloungerFrog (talk) 11:45, 17 November 2026 (UTC)
In the early days vast numbers of articles, especially biographies of older historical figures, were copied, lock, stock and barrel, from out of copyright encyclopedias, especially "EB 1911", and marked as such. In many cases the text remains the same but later editors have misunderstood the attributions, and often added "references needed" tags & so on. Johnbod (talk) 15:06, 18 November 2026 (UTC)
Reminds me of what Bob Dylan wrote about "the country was young..." in The Times They Are a-Changin'. So the encyclopedia was young and references were ignored. But we had Jimbo on our side. But seriously, that is not just about historical figures, text seems to have been added from old Unix manuals from 20 years ago, now totally outdated. The cleanup effort will be serious. Will require people with domain knowledge.
November 17 by Swaggzola, whose account was created earlier that day and had made no other edits.
If three hijackings in a single day (October 2) weren't considered enough back then, I can imagine being ridiculed for making another page protection request just because of only two hijackings a few days apart.
This circumstance makes me wonder how often WT:AFC would have to be hijacked like that before (at least short-term) semi-protection could be considered for it. – MrPersonHumanGuy(talk) 19:39, 17 November 2026 (UTC)
Watchlist "bookmark"
Is there any feature of a sort of "bookmark" which I can place somewhere on my watchlist so I can know which revisions I've reviewed and which I haven't? At the moment I often waste time trying to find where I left off when reviewinf my watchlist.
There is a filter for "unseen changes" available on the watchlist, does that solve your problem? Dingolover6969 (talk) 22:33, 17 November 2026 (UTC)
No, since I don't open every edit but would consider some reviewed just by looking at the edit summary, page, and editor, etc. And some edits I may click on but not have reviewed properly yet
A simple line or indicator whose placement I could control would be the best solution I believe. Could I request this feature be added somewhere? IOHANNVSVERVS (talk) 00:30, 18 November 2026 (UTC)
You can mark pages as watched from your meta:global watchlist. It's such a lovely way of doing watchlists that has unfortunately never been copied to the standard watchlist. —Femke (talk) 🐦 08:34, 19 November 2026 (UTC)
Pages which have changed since you last visited them appear in bold, though that only helps if you review changes by visiting the page. (I check most changes with Popups, which doesn't log my visit.) Certes (talk) 23:56, 17 November 2026 (UTC)
Would you find benefit in a bookmark feature? I may propose it. IOHANNVSVERVS (talk) 00:30, 18 November 2026 (UTC)
I proposed this at the idea lab here. IOHANNVSVERVS (talk) 00:50, 18 November 2026 (UTC)