Wikipedia:Village pump (idea lab)/Archive 49

Modifications to CANVASS
When determining consensus the ideal is that the discussion reflects the views of the broader community. Part of our policies in ensuring this is WP:CANVASS, which restricts who we can notify and how we can notify them. How this is done in practice is controversial, and recently there has been discussion about how we should alter this guideline to better do so.

This discussion is to have a preliminary discussion of the various ideas I present here and how they could be presented as proposals to reword the guideline, as well as generate other ideas for how CANVASS might be adjusted to better support this ideal.


 * Should discussions be informed when notices to them are posted?
 * Generally I believe they should; transparency is always a positive and it makes it easier to identify when canvassing takes place. I am hoping that this will be uncontroversial.
 * Should the examples listed at WP:APPNOTE be exceptions to WP:INAPPNOTE, or just examples of notifications that are usually acceptable?
 * I don't think it makes sense for these to be exceptions; notifying a partisan editor who has asked to be notified of "all contested AfD's" on a topic doesn't help the discussion reflect the views of the broader community and creates a wide loophole in our CANVASS requirements.
 * Can WikiProjects be partisan in relation to a topic, and should WikiProjects that can reasonably be seen as such be notified of discussions on that topic ?
 * I think it is obvious that any group of editors, including WikiProjects, can be partisan. I also think that if they are partisan they shouldn't be notified; we want the discussion to reflect the views of the broader community, not the views of the WikiProject when those views don't align with the broader community.
 * However, I wouldn't consider deletion sort lists and similar to be notifications; they make it easier for interested editors to find discussions but they don't notify editors of the discussion.
 * Should RfC's that would affect the broader community be held at WikiProjects?
 * I would believe they shouldn't, in line with WP:CONLEVEL; while the formal discussion invites participation from outside the WikiProject the forum still results in disproportionate participation from the WikiProject. In such cases, I believe it would be better to hold the discussion either at a relevant talk page or WP:VPR/WP:VPP, and I can't see any benefit from holding it at the WikiProject.

BilledMammal (talk) 07:52, 18 April 2023 (UTC) Editing for clarity BilledMammal (talk) 13:32, 18 April 2023 (UTC)


 * I noticed you mentioned there has been some recent discussion, but you have not linked to it. Which discussion or discussions do you refer to? Huggums537 (talk) 07:58, 18 April 2023 (UTC)
 * Wikipedia talk:Canvassing is the main discussion; there have also been discussions at ANI and on my talk page. BilledMammal (talk) 08:05, 18 April 2023 (UTC)
 * And you are thinking of yourself as someone who should be seeking consensus about well informed discussions? I find this to be both fascinating and yet somehow appropriate at the same time. Huggums537 (talk) 08:23, 18 April 2023 (UTC)
 * I don't understand what you are asking, but it seems to be a comment on me rather this on questions posed here so I would ask that you take it to my talk page. I would add that several editors have asked me to open this discussion, including in the discussion that I linked and that you participated in. BilledMammal (talk) 08:34, 18 April 2023 (UTC)
 * I wasn't asking anything. It was a rhetorical question. I just think it's interesting that someone who appears so concerned with informed discussions failed to make this an informed discussion. It was just a simple observation of irony, not about you, but about the ironic editing situation you created here. Huggums537 (talk) 09:12, 18 April 2023 (UTC)
 * This recent discussion may be one of those alluded to. Folly Mox (talk) 08:29, 18 April 2023 (UTC)
 * For the ANI discussion it is more this one: Administrators' noticeboard/IncidentArchive1119. BilledMammal (talk) 08:34, 18 April 2023 (UTC)
 * For the first three second and third questions, I am skeptical that any usable policy or guideline text could be based on answers to these questions, because I don’t think the concept of a partisan editor or partisan project can be operationalized outside of extreme cases (the Article Rescue Squadron, perhaps). Any editor will tend to see thise editors with whom they consistently agree on a topic as non-partisan and motivated by P&Gs, while seeing editors with whom they consistently disagree as partisan. This is exemplified by the tendency of editors to defend "per so and so" !votes as policy-based when agreeing with a !vote, while dismissing opposing !votes that cite P&Gs or other evidence as not being policy-based when an editor disagrees with the logic or policy interpretation contained within a !vote.
 * Any proposal to base policy guidance on a prior assessment that an editor or a Wikiproject is partisan - "partisan" in relation to what? - seems doomed to be only a tool in winning disputes and a means of gatekeeping to keep an editor's "allies" at hand and their "opponents" far away. Newimpartial (talk) 10:13, 18 April 2023 (UTC) corrected by Newimpartial (talk) 12:05, 18 April 2023 (UTC)
 * See WP:INAPPNOTE and WP:VOTESTACKING; we already forbid the notification of a partisan audience, with partisan defined as editors who have or are thought to have a predetermined point of view or opinion. For example, I would be considered partisan on topics related to notability.
 * I would also argue that it does the opposite of what you fear; an editor who tries to keep their "allies" at hand and their "opponents" far away by notifying only their allies would be in violation of the policy.
 * Relating your comments to the question at hand, you seem to be arguing that editors should be free to notify whomever they want; we can add a question to that effect proposing that VOTESTACKING is removed from INAPPNOTE? BilledMammal (talk) 10:25, 18 April 2023 (UTC)
 * Thanks for asking for clarification: I am not at all proposing that editors should be free to notify whomever they want, or that VOTESTACKING be removed from APPNOTE. But I'm not sure about your interpretation of the passages (of INAPPNOTE) in question: they do not prohibit the notification of partisan ... editors, which seems to be the concept you are using here, but rather it prohibits the notification of editors on the basis of partisanship. Posting an appropriate notice on users' talk pages in order to inform editors on all "sides" of a debate (e.g., everyone who participated in a previous deletion debate on a given subject) may be appropriate under certain circumstances - there isn't any carve-out to exclude some previous participants because they are perceived (by whom?) to be partisan.


 * As far as an editor who tries to keep their "allies" at hand and their "opponents" far away by notifying only their allies would be in violation of your proposed new policy language, this is already covered in APPNOTE (The audience must not be selected on the basis of their opinions) as well as INAPPNOTE (WP:VOTESTACKING). It seems to me that policy based on your comments on your second and third questions would be weaponized by editors who don't see their own biases (lacking your self-awareness with respect to Notability discussions, for example) while tending to restrict participation in instances where the inclusion of more, diverse perspectives would be better for the project. It seems to me that including too few rather than too many audiences is the bigger problem in the notification ecosystem. Creating GAMING opportunities by excluding "partisan editors" and "partisan projects" doesn't help with this - do we really want Women in Red excluded from notifications as a partisan project?
 * To give a more hypothetical example that might be easier to discuss: Canadian content may well be overrepresented on-wiki, and Wikiproject Canada may well skew towards the inclusion of Canadian content at AfD and may not align perfectly with the rest of the community in the assessment of Canadian sources at RSN. I would not see those situational factors (hypothetically) as valid reasons that Wikiproject Canada should be seen as a partisan audience when such articles and sources are under discussion or that a project notification would have a negative impact on such discussions. Sometimes members of a project hold views that differ from non-members for reasons of familiarity with sources or with policies, and there isn't anything in your proposal that could save that infant when disposing of the waste water.
 * As another example, Wikiproject Role-Playing games has a section of the project page dedicated to noticeboard discussions (including AdD and MfD), which results in watchers of the project page being alerted when such discussions begin (or end). The main impact of this in recent years has been that some salvageable articles have been improved and "saved" at AfD, while nothing perceived as "CANVASS" or disruptive on-wiki has happened. I don't see any advantage to the Wikipedia community in banning practices like this, which is what your views on your third question seem to require. The assumption that including editors who are sensitized to a topic will result in disruption in discussions on that topic seems to me not to be proven as a working assumption. The point should be to notify a broad and diverse range of editors who can bring experience or fresh perspective on a topic, but to create levers for GAMING the notification system.


 * TL;DR: INAPPNOTE and VOTESTACKING currently refer to "partisan audiences" but not "partisan editors" or " partisan projects". This is as it should be: editors are only "partisan" in relation to specific topics and should not be notified on the basis of their opinions (which policy already stipulates). Projects also only have the potential to be partisan in relation to specific topics or discussions, and the best way to ensure that project notifications reach all relevant parties is for people to join projects when they are interested in any aspect of its domain, not to treat the project as similar to a political party (in the words of VOTESTACKING). Notifying a broader range of projects and pages to reach more voices is an approach more in line with wiki values than creating gameable rules about those who must not be notified. Newimpartial (talk) 12:03, 18 April 2023 (UTC)
 * I agree with the concerns about gameability, and I'd also be surprised if a proposal encouraging not notifying certain projects is adopted by the community. I'm not actually sure what problem the current guideline is causing. — Ixtal ( T / C ) &#8258; Non nobis solum. 12:36, 18 April 2023 (UTC)
 * Regarding gameability, I don't think it can be gamed. An editor might try to do so by selectively applying the guideline - ignoring it for notifications of their side, but applying it to notifications of the opposing side - but that behaviour is possible for most of our guidelines, including WP:CANVASS as currently worded, and usually results in sanctions.
 * The issue with the guideline is that it is disputed whether it forbids notification of partisan WikiProject; we need clarity on whether this is permissible. The issue with notifying partisan WikiProjects is the same issue as with all vote stacking. BilledMammal (talk) 12:57, 18 April 2023 (UTC)
 * To be clear, when I say "partisan" I mean "partisan in relation to the topic under discussion". As for your proposed solution of having editors join all WikiProjects they are interested in, I don't think it is a plausible solution (how would we encourage editors to do so?), but it also wouldn't work; using your example, an editor might not be interested in Canada, but they might be interested in excluding unreliable sources or deleting non-notable articles.
 * We also can't balance out partisan groups by notifying groups that are partisan in the opposite direction because such groups rarely exist. This is why I didn't consider the WP:VOTESTACKING exemption you mention relevant; it works for and refers to individuals, but it doesn't work for groups.
 * In regards to your comment about editors who are sensitized to a topic, that isn't what this is regarding - it is about editors who are partisan to a topic. As far as I know, WIR is not partisan, which means that while they might be sensitized to a topic there is no issue with notifying them, and based on your comments about Wikiproject Role-Playing games the same is true with them.
 * Finally, you say that the point should be to notify a broad and diverse range of editors who can bring experience or fresh perspective on a topic; I agree, but notifying partisan groups increases the participation of that group in the discussion, thus making it less representative of the broader community and thus less diverse. BilledMammal (talk) 12:57, 18 April 2023 (UTC)
 * How does including everyone in the broader community even the "partisan" groups mean it is now less represented or somehow less diverse? You make no sense at all. Huggums537 (talk) 14:57, 18 April 2023 (UTC)
 * Let me take that back. You make a lot of sense on some things, but on that you didn't make no sense at all. Huggums537 (talk) 15:09, 18 April 2023 (UTC)
 * Sorry. I have to backtrack myself there because I realize I have an issue with coming across as severely critical of those I disagree with, especially if the disagreement is a strong one. Please overlook it if you are able to. Huggums537 (talk) 15:14, 18 April 2023 (UTC)
 * I understand; assuming you still want me to respond to meat of the question:
 * What we want is for the partisan group to be represented but not over-represented. Notifying the group will result in them being over-represented; notifying the broader community will result in them being appropriately represented. BilledMammal (talk) 15:40, 18 April 2023 (UTC)
 * It sounds to me like what you want is something similar to legalized spamming so you can notify a whole bunch of people and groups who are not even related to the topic while excluding the very people who might be related it. I can not tell you how much I hate these ideas. Huggums537 (talk) 16:05, 18 April 2023 (UTC)
 * What I am advocating is context-based notification, and I would oppose efforts to remove the current rule on spamming. For example, an RfC related to the reliability of a source should result in WP:RSN being notified and an RfC about a policy change should result in WP:VPP being notified. BilledMammal (talk) 16:21, 18 April 2023 (UTC)
 * BilledMammal has objected to my prior comment because the wikiproject system cannot be guaranteed to represent "both sides" of the issue at hand proportionately to "public opinion" on enwiki at large. I take issue with the underlying assumption here, which seems to be that Wikipedia is divided into party-like entities in conflict over outcomes (or perhaps one consensus party and dissident "partisans"). The way I see notifications working best is not by new restrictions or by spamming, but to do what policy calls for at present and invite editors into discussions who are related to a topic in different ways (defying BM's apparent assumptions).


 * For example, an assessment of a source published on a historical topic in French in Quebec to assess its relationship to FRINGE concepts might be relevant to wikiprojects focused on History, on Canada and Quebec, on French-language sources (I haven't checked whether such wikiprojects exist, but they should) and the FRINGE noticeboard. The idea that some of these should not be notified because they might be partisan on the topic (and yes, the FRINGE noticeboard has been accused of partisanship) seems like the opposite of the approach our P&Gs ought to promote. Meansbile, the idea expressed here, that a project should not be notified because no project exists to represent the contrary bias onwiki (where is our PROFRINGE noticeboard?), seems to assume those voicing this view are already treating their own networks and other preferences as similar to a political party (as this comment by another editor also does), which runs directly against the approach WP:VOTESTACKING - and CANVASS more generally - tries to promote, IMO.
 * From reading the rest of this discussion, BM has not shown readers that "partisan projects" exist and can be identified in relation to specific topics, or that disruption has been caused by the notification of "partisan projects". Their clearest expression of how partisan projects could be identified seems to be this one, but it imposes a false dichotomy - the situation they describe could result from various causes, including a situation where non-project members, who are less motivated to investigate deeply, do not read the sources provided (especially when sourcing has been presented after their !votes), where they engaged in a motivated interpretation of notability guidelines to justify their prior preference concerning deletion, or where keep or delete !votes differ over the same evidence in a reflection of differences within the broader community over how to interpret WP:N. The idea that such differences - or even differences in !voting patterns between project members and others - could only be explained by "partisanship" seems logically flawed and unsupported by empirical evidence. BM states here that A WikiProject having members who are interested in a topic doesn't make it partisan, just as it having members who are knowledgeable about a topic doesn't make it partisan - but if editors who are knowledgeable about a topic !vote differently on that topic than editors who are less knowlegeable, according to the operational metrics BM has repeatedly put forward, that means the more knowledgeable group of editors are partisan in relation to the topic, and informing them is VOTESTACKING! However, I see no community support for the idea that editors are presumed "partisan" when they disagree with certain other editors' interpretation of a community consensus, whether or not they belong to a project - this whole framing sounds to me like an WP:AGF fail, to be honest.
 * Also, I would point out that, while BM has amended the OP to refer to projects that are partisan in relation to a specific topic, in their other comments they seem to slip back into thinking of projects simply as "partisan" (e.g., here) as though a list of partisan projects could and should be maintained. That kind of evaluation - even in relation to specified topics - would require a community consensus that is currently clearly lacking, and proceeding with the approach BM seems to prefer, without any community agreement about the topics on which a particular group has shown partisanship, would be a clear invitation to GAMING as other editors have mentioned. As another example, it would be easy for an editor to assume that Wikiproject Feminism is partisan concerning topics and sources about feminism, but my sense is that the knowledge held by members of that project would be generally helpful to evaluations of feminist sources, not detrimental, even if on average they might disagree with a random sample of editors outside the project about the evaluation of certain sources.


 * In the absence of agreement about what would make a project (or a noticeboard, for that matter) "partisan", the most likely use of "partisan project" language would be for editors to assert without evidence that projects they distrust should be considered partisan based on those editors' own preconceptions and assumptions (or possibly, in the case of the OP, based on statistical inferences representing flawed logic and unsupported by policy).
 * I think one final example puts the logic of the proposal into a stark light: I haven't been even linking to, much less notifying, the wikiprojects I've discussed in my two lengthy comments. But if this proposal leads to an RfC, would it be inappropriate for editors to notify wikiprojects of this proposal to restrict notifications on wikiprojects? I think the answer to this is a reflection of how we see P&G concerning community processes more broadly - whether we aim for evolving structures to facilitate community engagement or whether their main purpose is to limit the participation of presumed "bad actors" and where disagreement with prior majorities is seen as evidence of "partisanship". Newimpartial (talk) 10:52, 19 April 2023 (UTC)
 * It is true that the wikiproject system cannot be guaranteed to represent "both sides" of the issue at hand proportionately to "public opinion" on enwiki at large. For example, the regular participants at a WikiProject tend to know something about the subject matter.  I would oppose any proposal that would lead to discussions being dominated by editors of average ignorance. WhatamIdoing (talk) 15:46, 24 April 2023 (UTC)

No need to get that evidence for me personally. I'm not even sure one could even gather it. In any case, I'm withdrawing from the discussion since I don't think I can give any more constructive feedback on your proposal nor do I think either of us will convince the other of our views on the matter. I still do not believe it would be good for the wiki or likely to pass, but appreciate you having discussed it with me. — Ixtal ( T / C ) &#8258; Non nobis solum. 18:33, 18 April 2023 (UTC)
 * When notifying editors of a discussion there are two “rules of thumb” to follow: 1) notify as many people as you can 2) make the notification neutral. Blueboar (talk) 13:45, 18 April 2023 (UTC)
 * The current wording of WP:INAPPNOTE suggests that the first rule of thumb is wrong; see Canvassing. Should we include a question proposing that we remove that aspect? BilledMammal (talk) 15:29, 18 April 2023 (UTC)
 * INAPPNOTE objects to posting a hundred messages. It does not object to posting one message to a page that gets a hundred page views per day. WhatamIdoing (talk) 15:46, 24 April 2023 (UTC)
 * This partisan bullshit essentially boils to saying we want rules to say we can restrict the very people who would be most interested in participating. I hate the very notion of it. Huggums537 (talk) 14:27, 18 April 2023 (UTC)
 * Per Huggums, this seems very much the opposite of what we want. In any discussion, we want not just Randy in Boise and his compatriots to be giving random opinions.  We should value the opinions of people with more knowledge of a topic, and not deliberately exclude them.  If I'm trying to decide "Is this hard-to-understand topic from molecular biology worth its own article, or should we delete it or merge it?", I don't want to exclude molecular biologists from the discussion.  Sure, I'd welcome any comments, but I'd find the presence of molecular biologists in the room with everyone else to be a huge benefit; they can explain what the topic is and what its relevance is to others who are unfamiliar with the subject.  The OP is basically saying "Inviting knowledgeable people should be seen as canvassing, and we should ban the practice."  What are we really after here?  Are we after bringing in the best people to help write the best encyclopedia with the best information available, or are we interested in winning battles and destroying our enemies?  -- Jayron 32 14:55, 18 April 2023 (UTC)
 * The OP is basically saying "Inviting knowledgeable people should be seen as canvassing, and we should ban the practice." That is not what I am saying. I am saying that inviting partisan groups should be seen as canvassing, even when the group is organized as a WikiProject, and we should make it clear that doing so is banned.
 * Being knowledgeable about a topic is not the same as being partisan about a topic; if this is a common misunderstanding it might be worth modifying WP:CANVASS to make this clear. BilledMammal (talk) 15:29, 18 April 2023 (UTC)
 * If a WikiProject is actively disruptive, appropriate sanctions will be employed against members of that WikiProject doing the disruption. It seems to me this is putting the carriage before the horse by attempting to prevent predicted disruptive activity rather than tackling past disruptive activity by a group of editors, and using CANVASS's notification guidance as an awkward crowbar to do so. I'd be much more concerned with such guideline creep being misused or (more likely) wasting editors' time with endless discussions about whether WP:LGBT or WP:GEOG are partisan. I'm almost certain some random POV-warring editor would seek for WP:LABOR to be essentially shadowbanned, for example. Additionally, just because we write rules doesn't mean they will be followed. — Ixtal ( T / C ) &#8258; Non nobis solum. 15:44, 18 April 2023 (UTC)Addendum: And if the WikiProject isn't being disruptive but just happen to share one opinion, then that is not something we are meant to fix. Sure, it sucks when some crowds aren't very wise at all but that's life. — Ixtal ( T / C ) &#8258; Non nobis solum. 15:50, 18 April 2023 (UTC)
 * To be clear, partisan WikiProjects aren't being disruptive, but it is disputed whether notifying them about topics they are partisan on is. To prevent issues going forward we need to determine whether it is or isn't, which is why we need to have a discussion to clarify this.
 * Personally, I don't see why notifying a partisan group organized as a WikiProject is any different from notifying a partisan group organized in a different manner; Arbitration/Requests/Case/Eastern European mailing list said messages to fora mostly populated by a biased or partisan audience — especially when not public — are considered canvassing and disrupt the consensus building process by making participation lopsided, which appears to partisan WikiProjects just as well as it does to other public groups. BilledMammal (talk) 16:02, 18 April 2023 (UTC)
 * To be clear, partisan WikiProjects aren't being disruptive, but it is disputed whether notifying them about topics they are partisan on is. Could you explain to me how it could be disruptive to notify them without their consequent participation being disruptive? The same case you mention contains many examples of coordinated disruption happening as a result of the canvassing, such as edit warring and coordinated voting. — Ixtal ( T / C ) &#8258; Non nobis solum. 16:10, 18 April 2023 (UTC)
 * Because it disrupts the consensus building process by making participation lopsided. The individual editors participating aren't doing anything wrong, but the editor who provided the notification did.
 * Could you explain to me why you see notifying a partisan WikiProject as different from notifying a partisan group organized in a different manner? BilledMammal (talk) 16:20, 18 April 2023 (UTC)
 * Because if the WikiProject has a genuine interest in the discussion and can be notified in a neutral manner in a public forum, not notifying them would essentially be WP:VOTESTACKING. Say I believe WP:LABOR is partisan in favor of organized labor groups (an understandable concern, given the purpose of their project is to maintain and expand the coverage of said groups on the wiki) and I want to delete a labor group article. How would failing to notify them, yet notifying other wikiprojects, be anything but votestacking? If no known coordinated effort is being made by them to preserve labor group articles at all cost, am I not preventing knowledgeable, constructive editors that are more likely to know of possible sources that could demonstrate notability from participating in the discussion? Am I not myself causing lopsided participation in consensus building processes as a result of assuming bad faith? Biased editors are still entitled to their opinions. This is not a new phenomenon. We've built processes to deal with issues that result. I'm also completely confused as to what you mean by in a different manner so can't answer on that part of the question. — Ixtal ( T / C ) &#8258; Non nobis solum. 16:36, 18 April 2023 (UTC)
 * How would failing to notify them, yet notifying other wikiprojects, be anything but votestacking? Assuming that the other WikiProjects aren't partisan and WikiProject Labor is, how would it be votestacking? Notifying the non-partisan WikiProjects wouldn't make participation lopsided, but notifying WikiProject Labor would.
 * I'm also completely confused as to what you mean by in a different manner so can't answer on that part of the question. Organized in a manner other than being a WikiProject. Pretend there are ten editors who share a position on a topic.
 * If I notify those ten editors directly then I am in violation of CANVASS. If the ten editors form a group organized in any manner other than as a WikiProject and I notify the group, then I am still in violation of CANVASS.
 * However, if the group is organized as WikiProject, then some editors argue that notifying them is not a CANVASS violation; I am hoping you can explain why the method of organization is relevant. BilledMammal (talk) 16:55, 18 April 2023 (UTC)
 * I'd argue assuming a WikiProject is partisan is a pretty strong one to make. I'm unconvinced your logic makes any sense when replacing "is partisan" with "I believe is partisan". What would the burden of proof even be to show a WikiProject is partisan, under your proposal? Even harder still, what would be the burden of proof to show a WikiProject is not? How could WP:WIR not be partisan but WP:SCEPTIC be? How could WP:WMNSPORT not be but WP:CFB be? You do understand that such a guideline would be scrutinized in this way if it is not guided by editors' belief of what is partisan and what is not. I.e. if you are assuming it is clear to the community what is partisan and what is not, you should be able to draw such a line for us and be confident it can pass scrutiny. — Ixtal ( T / C ) &#8258; Non nobis solum. 17:19, 18 April 2023 (UTC)
 * To prove that a group is partisan within a broad topic area we need to review the prevalence of opinions of members of that group within the broad topic area compared to non-group members. If there is a significant difference between the two then the group should be considered partisan for that topic area.
 * For a hypothetical example: We are considering whether members of a WikiProject are partisan in relation to whether articles on fish should be deleted.
 * If we see that the average support for deletion of these articles is 30% (3 out of every 10 !votes are 'Delete') among editors who are not members of the WikiProject, but for editors who are the average support is 90% (9 out of every 10 !votes are 'Delete'), then the WikiProject should be considered partisan for the broad topic area of "deletion discussions about fish".
 * If you see any issues with this then please say; I think a workable definition is possible but it may need some work. BilledMammal (talk) 17:31, 18 April 2023 (UTC)
 * My issues with this are as follows:
 * How is it that the individual members of this WikiProject are not engaging in misconduct related to AFDs and therefore should not be individually sanctioned if, on average, they vote to keep 90% of fish articles?
 * This assumes that future participants in the WikiProject will inherently share the bias of past and current members
 * Until I'm shown evidence that it is rare for WikiProjects to overwhelmingly want to keep articles within their purview, I believe your definition would apply to almost every WikiProjects.
 * — Ixtal ( T / C ) &#8258; Non nobis solum. 17:44, 18 April 2023 (UTC)
 * For 1, !voting against consensus is rarely sanctionable and I don't think I've ever seen an editor sanctioned for consistently !voting against consensus is a single broad topic area at AfD. I'm also not sure they should be sanctioned; editors being against consensus isn't an issue, the issue is if they sway the debate by votestacking, rather than by convincing the broader community that their position is the correct one.
 * For 2, it doesn't make that assumption. If future participants don't share the opinion of past and current members then the prevalence of opinions will change.
 * For 3, I doubt it is true for most WikiProjects; while some are concerned about quantity, others - I believe most - are more concerned about quality. Further, while my example was deletion discussions it wouldn't only affect deletion discussions; it would also affect RM's, RfC's, etc.
 * I can look into getting that sort of evidence for you, but it will take a few weeks before I have time to do so. BilledMammal (talk)
 * Being knowledgeable about a topic is not the same as being partisan about a topic You've not made any such distinction in the manner you are using "partisan". How do I know if a Wikiproject is "partisan" vs. if a Wikiproject is "knowledgeable and interested in a topic"?  -- Jayron 32 16:06, 18 April 2023 (UTC)
 * WP:CANVASS doesn't make any such distinction; I wouldn't think one would be necessary because it seems obvious to me that the two aren't synonyms. However, if this is a common misunderstanding then CANVASS needs to be modified to make such a distinction; do you think it is common, and how would you propose making that distinction? BilledMammal (talk) 16:20, 18 April 2023 (UTC)
 * It's obvious to me they aren't synonyms. However, you seem to be using "partisan" in a way that doesn't make it clear you have made such a distinction.  My point is, if you're going to say "These WikiProjects over here are full of wonderful, knowledgeable editors, and the discussion could really benefit from their deeper knowledge of the discussion" and "The other WikiProject here is full of a bunch of partisan assholes, and if you notify them, they're going to show up and ruin the discussion".  How do you define the difference?  Because if you can't, then you have no leg to stand on with your proposal.  -- Jayron 32 17:45, 18 April 2023 (UTC)
 * The same way you determine if an editor is partisan; for more detail, see my response to Ixtal. BilledMammal (talk) 18:06, 18 April 2023 (UTC)
 * I've read your response to Ixtal; what it shows me is some phenomenal lack of AGF in interpreting the actions to mean "is partisan" rather than "is knowledgeable". For example, people who write articles about fish (from your example) are more likely to know of, and have access to, source material about fish than the average person.  Difference in voting in a discussion is quite easily explained that way.  The fact that a member of a Wikiproject voted one way, and someone who is not a member of that project voted another, does not mean that the member of that project did so because they were "partisan".  Your assumptions that that is the best interpretation of that data is problematic.  -- Jayron 32 18:16, 18 April 2023 (UTC)
 * If the members of the WikiProject are presenting sources then a difference in prevalence of opinions can only occur if the broader community disagrees with their conclusions about those sources. The difference isn't because they are more knowledgeable, it's because their beliefs on sources are not aligned with the beliefs of the broader community - in other words, it is because they are partisan. BilledMammal (talk) 18:27, 18 April 2023 (UTC)
 * Jayron32's question, "How do I know if a Wikiproject is 'partisan' vs. if a Wikiproject is 'knowledgeable and interested in a topic'?", is very much on-point for me. I'm not a wikilawyer. When someone else moved Theban alphabet (its original title since creation) to Theban script, and reverted my reversion without having discussed it on talk, that left it to me to open up that discussion on its talkpage, a page move request to get it back to the stable status quo ante, rather than the mover requesting his preferred move there. That is, the page is sitting in its changed state while the request ages. I knew that the request would show up automatically on a list, for those who watched it, but I thought past editors of the page, still active, should also have a say, so I notified those in the revision history who had any contributions on en:wp within the past year or two. Now I've got to worry whether I fell afoul of CANVASS, despite not knowing in advance which article title they would prefer? –  . Raven .talk 07:17, 19 April 2023 (UTC)
 * I don't agree that WikiProject are inherently "partisan", and I've seen enough disagreements on project talk pages to discount the idea that project members are always "of one mind" on a subject. WP:CANVAS explicitly allows notifying projects of related discussions, and I see no reason to change that. Schazjmd   (talk)  16:09, 18 April 2023 (UTC)
 * WikiProjects aren't inherently partisan, but some are partisan. Further, disagreements doesn't mean a group of editors, whether organized as a WikiProject or not, isn't partisan; if 90% of the members of a group support something but only 30% of the broader community do then the group is partisan on that question even though there is some disagreement within the group. BilledMammal (talk) 16:20, 18 April 2023 (UTC)
 * There can be honest disagreements between different groups of editors based on their underlying assumptions or experiences, without making them partisan. The only way to evaluate the arguments in context is to hear them out. I agree it's not necessarily helpful to hear the same arguments over and over again, but that's a problem with English Wikipedia's decision-making traditions in general. isaacl (talk) 16:37, 18 April 2023 (UTC)
 * Or to take a wildly hypothetical example: if over 99% of virologists and MDs specializing in public health, epidemics, pandemics, etc., believe something called, say, "COVID–19" is real... but over 50% of the population think otherwise... that doesn't mean the first group are "partisan". – . Raven .talk 07:26, 19 April 2023 (UTC)
 * WikiProjects are just groups of editors sharing a common interest and working together to further the goals of Wikipedia, usually by working on various initiatives. Most of them are oriented around a content area, and thus attract the knowledgeable editors in that area. Notifying the corresponding WikiProjects for related content areas is considered to be a neutral way of reaching the interested editors who are best able to bring greater context to a decision. It's not partisan to be interested in a content area. There are other groups of editors interested in managing deletion who monitor the deletion request pages; they're not necessarily partisan, either. For better or worse, the best way to reduce the impact of vote-stacking via canvassing is to reduce the effect of raw numbers on the decision-making process. This means weighing arguments in a manner not solely tied to the number of people speaking in favour of them. I know this isn't easy, but the ultimate way to avoid a behavioural problem is to remove the incentive for it. isaacl (talk) 16:33, 18 April 2023 (UTC)
 * I think a lot of this discussion is based on a misunderstanding; we are only talking about partisan WikiProjects, with partisan having its standard definition of a strong supporter of a party, cause, or person. A WikiProject having members who are interested in a topic doesn't make it partisan, just as it having members who are knowledgeable about a topic doesn't make it partisan.
 * It seems there is a common misunderstanding about what partisan means; this needs to be resolved, because even if there is a consensus that WikiProject's can't be partisan CANVASS still uses the word and this misunderstanding must be causing issues. Do you have any suggestions for how to resolve this misunderstanding? BilledMammal (talk) 17:20, 18 April 2023 (UTC)
 * I don't know if anyone can provide a suggestion for what you mean by partisan. At the incidents' noticeboard discussion you linked to above, you called WikiProject NFL a biased audience that shouldn't be notified. To me this is a group of editors interested in a specific content area, and so notification is appropriate. Rather than trying to label groups, it might be better to focus on the criteria for notification: they shouldn't be tailored in such a way that only editors with a specific viewpoint would be interested in being notified. isaacl (talk) 17:36, 18 April 2023 (UTC)
 * The Article Rescue Squad is the usual group people point to for inappropriate notifications. While I understand why, I also understand why some editors feel motivated to try to fix articles that seem promising and are currently undergoing a deletion discussion. It might be a reasonable approach for that group to concentrate more on the fixing and limiting their contributions in deletion discussions to just noting what sources they have added to illustrate that the standards for having an article are met, without further comment. isaacl (talk) 17:44, 18 April 2023 (UTC)
 * I followed that for years and never understood it. What was most disturbing to me was the "gamification" of the AFD discussions.  Some people seemed to think that once an article arrived at AFD, everyone divides into two camps, "Delete" or "Keep", and the winner was the one who got their votes enacted.  Like it was somehow cheating to try to improve the article while it was at AFD.  -- Jayron 32 18:04, 18 April 2023 (UTC)
 * I've been templated for editing an article's text body while (and had my edit reverted because) a page move request was underway. (The template was topped with the user-written comment: "There is an on-going discussion on these articles, which you are engaged in. Wait for them to resolve...". The revert comment: "rv: this is an ongoing discussion -- wait for the result" I'd never heard it was somehow cheating to try to improve the article while it was awaiting a decision whether to restore its original and long-time name over the name it had just been moved to without discussion. – . Raven .talk 07:49, 19 April 2023 (UTC)
 * To understand what you are saying; are you saying that the group can be partisan but that it is appropriate to notify them anyway because they are interested in the topic area, or that they can't be partisan?
 * For individual notifications I agree that focusing on criteria is a good idea, but I don't think it will work with groups. This is because for individuals when you have the correct selection criteria you balance out editors who are partisan for side A with editors who are partisan for side B; with groups it is often impossible to obtain such balance because in many cases there are groups that are partisan for side A but no groups that are partisan for side B. BilledMammal (talk) 18:06, 18 April 2023 (UTC)
 * In the context of making content-related decisions, I feel the concept of partisan is akin to failing to be impartial: that is, failing to set aside one's personal feelings to make a decision based on evidence and in consideration of community guidance. I don't believe it is reasonable to declare, for example, the set of editors interested in baseball to be partial with respect to baseball-related content. I also don't agree with the assertion that a group that disagrees with a larger superset group must be disagreeing due to partiality. There can be differing interpretations leading to disagreement, or different levels of expertise. To take an extreme example, a general group of people might agree that a particular software feature can be easily coded with minimal effort, while a small subgroup of experts might say it isn't. Both sides can be honestly weighing the considerations in their minds fairly and yet reach different conclusions based on their knowledge.
 * There are groups that, by their nature, have self-selected a set of editors with a specific position on some issue, and thus its members are more prone to make partial arguments for that position. Although the community has rarely ruled against the formation of groups of collaborating editors, it has happened when it agreed that the group's purpose was counter to the best interests of the overall project. I don't think a blanket statement can be made that "groups can/can't be impartial". It depends on how the group is selected. This comes back to the question of the criteria for notification: if a list is created for the purpose of notifying those who wish to always vote to delete articles, then notifying them results in vote-stacking for deletion. isaacl (talk) 21:26, 18 April 2023 (UTC)
 * @Isaacl, I think the concept of partisan is very well understood in practice: If you agree with me, then you're non-partisan.  If you consistently disagree with me, you're partisan.  (The fact that I consistently disagree with you doesn't make me partisan; it is impossible for me to be partisan.  It's a little surprising that this isn't already recorded in WikiSpeak.
 * We don't invite altmed supporters to NPOVN to discuss pseudoscience; we do invite the denizens of Fringe theories/Noticeboard. We know that FTN is partisan in a dictionary-definition kind of way, but it's a POV that the community supports, so they're not partisan.  AFAIK the community has never agreed that a complaint about someone inviting FTN to join a discussion on pseudoscience was a violation of canvassing's partisanship rules.  We should not change that. WhatamIdoing (talk) 15:54, 24 April 2023 (UTC)
 * Yes, some groups are self-selected to have specific approaches. If these approaches are designed to evaluate evidence and consider community guidance in making decisions, then generally speaking they are suitable for making an impartial decision. Being open to consider different opinions fairly is the key characteristic. (Regarding wikispeak, disagreeing editors just say biased; it's a little shorter to type and direct to the point they think they are making.) isaacl (talk) 16:54, 24 April 2023 (UTC)
 * > "I feel the concept of partisan is akin to failing to be impartial" – Pretty much by the definitions and etymologies of "&hairsp;isan" and "&hairsp;ial", respectively:
 * "(adj.) of or pertaining to a party or faction ... (noun) especially one whose judgment is clouded by prejudiced adherence to a party", and
 * "one-sided, biased, inclined to favor one party in a cause or one side of a question more than the other"
 * Both ultimately from Latin pars, 'part'. – . Raven .talk 17:23, 24 April 2023 (UTC)
 * In regard to the second bullet point: Considering that this website works on consensus, I think that it's important for users to feel that their perspectives and opinions are taken into account during discussions, so in general I believe that notifying editors who have asked to be informed should be allowed, even if their view on the topic in question is known. The specific example given is a rather extreme case; if an editor wants to know about every discussion in a certain area, it might be more efficient to advise them to watchlist a deletion sorting list, talk page, or noticeboard than notifying them individually every time, but is it really an issue if another editor does so, considering that if the first one cares so much, they may well find their way to the relevant discussions on their own? As for the other bullet points in the OP, I don't think it's helpful to treat WikiProjects as partisan (largely based on what Isaacl wrote above), but I don't have any objection to the 1st & 4th bullets; APPNOTE already says that doing the first is good practice and it would make sense to make that into a requirement, as long as other users don't come down like a ton of bricks on editors who forget once or twice. Hatman31 (talk) 16:54, 18 April 2023 (UTC)
 * As I wrote in the discussion on the canvassing talk page, it's common practice for editors to request to be notified about certain discussions. Typically it's for a specific set of discussions, such as the notification list the arbitration committee set up for discussions on changing the discretionary sanctions system. I agree interested editors should be pointed to the existing notification systems in place, including watching relevant noticeboards and WikiProject talk pages. In cases where someone chooses to send notifications for a more tailored situation, they should open it up to anyone to use. I appreciate, though, that within the bounds of English Wikipedia's current decision-making traditions, there is a vote-stacking issue when the criteria for notifications is chosen such that those interested in the notifications have the same opinion. isaacl (talk) 17:16, 18 April 2023 (UTC)
 * but is it really an issue if another editor does so, considering that if the first one cares so much, they may well find their way to the relevant discussions on their own The issue is that it's a loophole in our CANVASS restrictions; it means that any editor who wants to be canvassed just needs to ask to be so. If we are going to permit that loophole then there isn't much point in having CANVASS restrictions. BilledMammal (talk) 17:20, 18 April 2023 (UTC)
 * How are "members" of a WikiProject defined? I think I have added myself to a list of members for 4 WikiProjects (two of which I wasn't certain I'd listed myself until I checked just now, and I wouldn't consider myself to be actively editing in the subject area for one of them). I have userboxes on my talk page that put me in a category for members of one WikiProject, and one task-force. I've watchlisted the talk pages of 36 WikiProjects that I'm would say I'm highly interested (i.e., I have some desire to weigh in at AFDs, RMs, etc). Of those, there are probably 21 where I've made more than 1,000 edits to articles in the scope of the project, and several more where I have repeatedly contributed to discussions on the WikiProject's talk page. I guess I'm a "member" of all those, but I haven't felt the need to formally list myself as such.Plantdrew (talk) 21:08, 18 April 2023 (UTC)
 * Each project is free to set its own rules. In the case of WikiProject Military history, editors sign up at WikiProject Military history/Members. The membership list is maintained by the project bot, which moves members to the inactive list if they have not edited Wikipedia in the last 365 days. Hawkeye7   (discuss)  22:11, 18 April 2023 (UTC)
 * @Plantdrew, one doesn't actually notify "members"; one posts a note on the group's talk page, which notifies members, non-members, participants, non-participants, editors passing with requests for help on other subjects, RecentChanges patrollers, etc.  WhatamIdoing (talk) 15:56, 24 April 2023 (UTC)
 * We want more editors to be informed, not less. Imagine societies where the media is restricted and people have no way of knowing what is really happening in their government. That is basically what is being proposed here, to our governance model. --Rschen7754 22:40, 18 April 2023 (UTC)
 * Were it up to me I'd strike WP:CANVASS from the list of policies wholesale. I think it does more harm than good—it serves no legitimate purpose other than giving people who are sore about losing a debate means to tattle on their opponents at one of the drama boards in hopes of getting the newly-established consensus overturned. Such policies are the worst thing about Wikipedia; they turn off far, far more potential contributors than any supposed benefit they give us. —Scott5114↗ [EXACT CHANGE ONLY] 23:05, 18 April 2023 (UTC)
 * I disagree with the premise. I'm in a handful of wikiprojects and none of the ones I'm in votes as a unified block in anything. In every project I've participated in, the debates between the project members aren't that different than the ones seen in the wider Wikipedia community. I don't deny there has been a handful of arbcom cases where it's come to light there has been off-wiki collusion to affect a vote count. However, those are the extreme cases, not the norm. What I see starting to happen is accusations of canvassing are becoming a cheap allegation to retroactively poison the well when ones opinion isn't popular in a debate. It's an easy allegation to make, impossible to prove ones innocence. It's not unlike baseless accusations of plagiarism in academia or abuse in a divorce case. I'm concerned accusations of canvassing are starting to become the Wikipedia equivalent of Stop the Steal. Dave (talk) 23:42, 18 April 2023 (UTC)
 * Comment I remember an AfD from a couple years ago on some Ancient Rome topic (don't remember the specific article). It was quite technical and none of us AfD participants could really understand it, so we shot a neutrally-worded message to WikiProject Classical Greece and Rome for expert assistance. Curbon7 (talk) 23:46, 18 April 2023 (UTC)
 * Comment. What about Wikiprojects that follow their own notability standards that are at odds with the community's? We saw after a well-attended 2017 RfC that the larger community strongly supported the (existing) requirement that all sportsperson articles meet GNG, but since the larger community is not directly notified about selected AfDs and is less likely to participate in them anyway, the sports projects went right on using their criteria without consequence. The same thing happened for many months after the NSPORTS2022 RfC where editors from these projects deliberately ignored the consensus and continued !voting keep based on deprecated criteria even when no one could find any SIGCOV. Many of these AfDs got closed as keep because project members are already over-represented at AfDs on their topic, and this becomes even more lopsided when members alert each other to particularly contentious AfDs.

Perhaps what this discussion is telling us is that we should make an "article deletion task force" WikiProject where all the editors frustrated with lax standards and inconsistent application of P&Gs in AfDs can combine their efforts across multiple topics. Then perhaps it wouldn't be a month-long painful ordeal--including a keep close in the middle--to delete a subject because some editors claim GNG/ANYBIO is met with 40 words in a local newsletter reproducing verbatim a facebook post by the subject's team announcing the results of an anonymous Google docs poll held by the Twitter account for the league's fan club... JoelleJay (talk) 05:08, 19 April 2023 (UTC)


 * Or, maybe it's telling us that your "article deletion task force" standard isn't working all the way across the board like you wish it did, and maybe our existing P&Gs need to be updated to be more inclusive of that fact so editors wouldn't be that frustrated anymore... Huggums537 (talk) 05:28, 19 April 2023 (UTC)
 * Good lord, an "article deletion task force"? You can't delete your way to making the encyclopedia better. The only thing that would accomplish is sending the project into irrelevancy by scrubbing it of content a reader might find useful. —Scott5114↗ [EXACT CHANGE ONLY] 06:17, 19 April 2023 (UTC)
 * I actually would welcome such a development. Then we know where everyone stands. --Rschen7754 06:20, 19 April 2023 (UTC)
 * No one "stands" anywhere. What every person does is they assess each article, and then they compare what information they can find about that article and its subject, and they also compare that to the standards for whether or not we should 'have' an article at Wikipedia on that subject, and based on all of that information, they decide, for themselves, whether the article and/or subject meets the minimum requirements.  People don't have "stands", they just do the best they can to make the best assessment possible each time.  The fact that people may read or interpret the standards and different ways doesn't mean they take "stands".  Different is not wrong, and the world will always have differences over what the standards mean, and whether any one particular article may meet those standards.  -- Jayron 32 14:30, 19 April 2023 (UTC)
 * That is a very optimistic view of things, but when the same people vote the same way over and over against the same subject area, it's time to call a spade a spade. Please read and tell me that this is not a stand. Rschen7754 00:13, 20 April 2023 (UTC)
 * When people vote the same way over and over it means they are consistently applying the standards as they understand them. -- Jayron 32 12:44, 20 April 2023 (UTC)
 * Not necessarily. They might just have a bias against that subject area. Rschen7754 16:45, 21 April 2023 (UTC)
 * The fact that this is your first interpretation of someone's actions is problematic. If you set out assuming people are doing things because they are bad actors, 1) you're going to believe that evidence points you that way and 2) you're going to interpret all of their actions, no matter how benign, that way.  That's why the WP:AGF policy exists.  Actions should be viewed as people doing their best to make the encyclopedia better.  Yes, of course, there are vandals and POV pushers, and all that.  But merely because people have a different interpretation of policy than you do, and vote differently than you would have in a discussion, doesn't mean they "have a bias".  It just means they read things differently.  No one has presented any evidence of bias beyond what could be easily seen as a difference of interpretation.-- Jayron 32 17:12, 21 April 2023 (UTC)
 * It's not just "applying the standards" in the sense of applying the written rules. But I agree that people with all sorts of views are doing their best to make the encyclopedia better.  One editor might believe that keeping an underdeveloped, weakly sourced two-sentence stub makes the encyclopedia better; another might believe that deleting the same article makes the encyclopedia better.  This view goes beyond "a different interpretation of policy", as there is no policy about whether the English Wikipedia's quality should be measured by its aggregate collection of information (4.2 billion words total) or the length of the average article (~650 words for the mean, a bit lower for the median).  An editor who supports the Least publishable unit approach (lots of very short articles on narrow subjects) is not really applying "policy" any more than an editor who supports mergism (fewer, longer articles on broader subjects). WhatamIdoing (talk) 17:18, 24 April 2023 (UTC)
 * My "stand" is that articles should be subject to consistent inclusion criteria across the encyclopedia without being influenced by how much one group likes or dislikes a given topic area. When the global community has a consensus view on what criteria or types of coverage contribute to notability, whether that consensus is enforced at a given AfD should not depend on who happens to show up. And yet that is exactly what happens because even if a wikiproject represents a minority of the global community, it is highly overrepresented at discussions on topics within its scope, and thus if those members reject consensus in favor of their own internal metrics, they can easily form a local majority. The hypothetical "deletion task force" would exist to promote compliance with our P&Gs, regardless of whether that results in a keep or delete outcome. JoelleJay (talk) 01:52, 25 April 2023 (UTC)
 * I think it is a very false assumption to say the groups showing up are a minority view while the ones not showing up represent some "global community consensus" that is absolutely opposite to whatever was decided by whoever showed up. It could just as easily be interpreted that by not showing up, the "global community" has given implied consent to the outcomes since they did not show up opposing them. We wouldn't know either way because they didn't show up to say, and you are not the one for acting like an arbitor of that decision for the global community or as a representative for the creation of any kind of "force" based on such faulty assumptions. It could also be interpreted that in the case the global community did in fact imply consent for the outcomes made from participants by not opposing, such a "force" being created would actually become the offending partisan group itself. Huggums537 (talk) 02:36, 25 April 2023 (UTC)
 * Re: {{{tq|When the global community has a consensus view on what criteria or types of coverage contribute to notability}} - sure, but this premise exists more often in the minds of certain editors than it does in reality, IMO. For some, WP:SIGCOV is to he interpteted as "independent RS have to show a topic is important by writing about it at length" whereas other editors contextualize that guideline differently and interpret it more as "independent RS must provide usable information that can be used in writing an article". Still other editors read SIGCOV as though it meant the same thing as WP:SIRS (which is supposed to be NORG-specific). My limited experience at AfD suggests that many editors approach most discussions with a preconceived view of "this article should/shouldn't exist" and then base their assessment of SIGCOV - or even of source reliability - on that preconception.
 * In any case, the view implied by BM's comments - that there is an underlying distribution of support and opposition (e.g., to AfDs) that ought to be reflected in specific formal processes and that is distorted by wikiproject notifications - does not appear, from this discussion, to be widely supported within the community (in a discussion that, as far as I know, has *not* been subject to CANVASSing or other notifications). Newimpartial (talk) 10:18, 25 April 2023 (UTC)
 * Obligatory note that this discussion is also not an indication of "the global community" -- it's maybe 20 people -- nor is it a representative sample, since the majority of people in it have also been in the last 5000 discussions about sports articles at AfD making the same points (which is what this is really about). Gnomingstuff (talk) 14:09, 26 April 2023 (UTC)
 * I really really hate this dumb inclusionist vs. deletionist debate because it only leads to comments like this one. is absolutely not a phrase that should be uttered by any editor, let alone an admin. Curbon7 (talk) 14:39, 19 April 2023 (UTC)
 * Though, I don't think any editor should be campaigning for a task force to delete as much as possible, either. BeanieFan11 (talk) 14:45, 19 April 2023 (UTC)
 * Two wrongs do not make a right. Curbon7 (talk) 15:03, 19 April 2023 (UTC)
 * I'm not sure that it's really a task force to delete as much as possible. It might be more fairly described as a task force to follow the letter of the law. WhatamIdoing (talk) 00:24, 26 April 2023 (UTC)
 * +1 -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 20:52, 19 April 2023 (UTC)
 * Did you know that topics don't have to have standalone articles to be covered in an encyclopedia? JoelleJay (talk) 01:05, 25 April 2023 (UTC)
 * The Free Encyclopedia Anybody Can Edit + Article Deletion Task Force + NPP(effectively an Article creation task force) = Wikipedia, The site that used to "Make The Internet Not Suck" has become the angry Karens of the internet, who call 911 and demands the swat team gets rid of everyone new who shows up at the park "acting wierd". Dave (talk) 15:32, 19 April 2023 (UTC)
 * I'd say that Articles for creation is the "article creation task force". NPP's original and most important job is to identify new pages that meet any of the Criteria for speedy deletion. WhatamIdoing (talk) 00:25, 26 April 2023 (UTC)
 * I always leave a message saying if I've placed notifications, just as a courtesy and for transparency. I don't think restricting notifications that are made in a neutral manner is helpful. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 21:03, 19 April 2023 (UTC)
 * Answering questions from the lead. 1) yes, transparency is good and notifications to everyone are best practice. Linus's law logic applies: the more eyes... etc. 2) no opinion at present, this is somewhat unclear to me 3) I agree WikiProjects can be partisan, but I also think it's fine to notify them IF they are relevant. For example, if an article is tagged as within scope of WikiProjects A, B and C, they should be notified. Technically they already may be through Article Alerts and like, but there is nothing wrong IMHO from notifying them in other ways (their talk pages, I guess?). 4) I agree they should not, unless they concern that WikiProject only, which would be quite rare. Arguably, this can be a case by case basis issue, but I don't recall an RfC that was held at WikiProject in a long time. Some examples might help refine my vierw, if anyone would care to provide them and ping me. <sub style="border:1px solid #228B22;padding:1px;">Piotr Konieczny aka Prokonsul Piotrus&#124; reply here 05:32, 22 April 2023 (UTC)
 * I like this idea about "Linus's law". It supports the idea that saying earlier about giving notice to the most eyes possible. There is a difference between giving notice to as many people "as possible" (with a good faith assumed meaning being "as allowed" of course!), and spamming people not even related to the discussion. Huggums537 (talk) 08:51, 22 April 2023 (UTC)
 * The purpose of this page is to provide creative and positive feedback, not to bicker endlessly about the merits of ideas. To address the four suggestions: 1) seems fairly uncontroversial; It is good practice to leave a note at the discussion itself about notifications which have been made, particularly if made to individual users is already part of the guideline, and I don't think there'd be too much resistance to tuning "It is good practice to..." up to "Users should..." or something like that. 2) I think APPNOTE already makes clear that even when making notifications covered by APPNOTE, you should not send inappropriate notices, as defined in the section directly below. I don't know that an RfC on this fairly narrow issue would go very far toward resolving your concerns. 3) I mean, I get where you're coming from, but this has been discussed for years (cf. the Article Rescue Squadron debates) and there's just not going to be a consensus to prevent neutrally worded notices to WikiProjects (and as long as we have the Article Alerts Bot, it wouldn't matter if there was). As all the drama above indicates, an RfC on this issue is likely to shed more heat than light. 4) I'm honestly not sure how this would land. Personally I'd tend to agree with you, but you're going to have a hard time convincing people that a well-advertised RfC presents a CONLEVEL issue, and the "disproportionate participation" issue is true in all sorts of forums (the people who watchlist policy talk pages, for instance, are rarely representative of the community at large). One option would be to hold all RfCs on separate subpages of Requests for comment, but that might be a larger-scale change than most people would be comfortable with. Hope this is helpful. Extraordinary Writ (talk) 19:44, 23 April 2023 (UTC)
 * There's an important distinction between the Article Alerts bot and a project talk page post, which is that the latter pretty much only occurs for contentious (or expected-to-be contentious) AfDs, and the poster anticipates project members will support their desired outcome. JoelleJay (talk) 01:02, 25 April 2023 (UTC)
 * If a group of editors frustrated with lax standards and inconsistent application of P&Gs in AfDs were formed, then BilledMammal's proposal would ban us from telling them about any AFDs.
 * I believe these editors tend to hang out at Deletion review.
 * WhatamIdoing (talk) 16:00, 24 April 2023 (UTC)
 * ...Yes
 * The regular editors at DR tend to be more likely to support keeping articles. JoelleJay (talk) 00:56, 25 April 2023 (UTC)
 * They seem to favor consistent application of policies and guidelines. Will "opposing lax standards" and "supporting consistent application of the policies and guidelines" going to turn out to be contradictory goals?  Our written standards are lower than people might expect if they're relying on our informal advice.  Plausible interpretations (NB "plausible", not "my own preferred") of the actual written policies and guidelines require the existence of just two independent sources in the real world, only one of which must be secondary, using the lowest possible standard for secondary, and these sources don't technically have to be cited, unless the article is about a BLP.  Also, all sources considered in combination must have a quality that we call "significant coverage" but refuse to define in any way, so it is a case of SIGCOV being in the eye of the beholder. WhatamIdoing (talk) 00:15, 30 April 2023 (UTC)
 * Out of thousands of discussions, I've only come across two editors who have claimed only one source has to be secondary and that SIGCOV is distributive (for non-NBASIC subjects). What part of "sources should be secondary sources" implies a GNG-contributing source can be primary? JoelleJay (talk) 01:58, 30 April 2023 (UTC)
 * @JoelleJay, did you ever read the footnote in the middle of that sentence? The one containing the words "In the absence of multiple sources", i.e., that the guideline says it's not strictly necessary to have multiple secondary sources?   WhatamIdoing (talk) 23:27, 2 May 2023 (UTC)
 * That doesn't mean a primary source can contribute to GNG, just that theoretically one comprehensive secondary source can suffice. JoelleJay (talk) 02:31, 3 May 2023 (UTC)
 * That is exactly what it means since the subject itself counts as a primary source. So, if all you theoretically had was the subject itself, and one comprehensive secondary source, then that would be enough to contribute to GNG according to guidance. There is no getting around the fact that a subject with one single comprehensive secondary source has no choice but to also take into account for the primary source itself as part of a GNG evaluation, and I would argue that the subject itself (or the primary source) is probably the largest contributing factor to notability of any article with secondary sources just being there to verify and substantiate because without the primary source and the inherent notability it has, you don't even have secondary sources to go searching for. Secondary sources are really nothing more than just a search for proof that has devolved to an argument on Wikipedia about over-complicated details regarding what that search should be all about. Sadly, it has degenerated to the point where it has been reduced to nothing more than a popularity contest i.e. if the search was/is easy then the subject is popular/notable enough, but if the search is difficult then the subject isn't popular/notable, but this defies common sense when it comes to subjects that are clearly worthy of being printed, but have no popular coverage. That leaves us with guidance not relevant to all situations, as well as leaving us with tons of misguided editors for fuel to the problem. Huggums537 (talk) 04:47, 3 May 2023 (UTC)
 * GNG says:
 * You have to have multiple sources.
 * Only one source has to be secondary.
 * Ergo: A non-secondary source can "contribute" to GNG.
 * (@Huggums537, please read Party and person. Material from the subject is never independent of the subject, but it could be secondary... although in practice that almost never happens.) WhatamIdoing (talk) 19:07, 4 May 2023 (UTC)
 * Interesting. I had never considered the subject could ever be secondary. However, I still believe a single secondary source along with the subject could theoretically satisfy GNG requirements since the secondary and primary together meets the multiple sources requirement, and the requirement for third party sources doesn't say all sources have to be independent, but only that, We require that all articles rely primarily on "third-party" or "independent sources"... so I think if you are relying on that secondary source primarily for your notability then you have the third party requirement met as well so it wouldn't really matter if the subject was primary, or independent just so long as it counts as a source for the multiple sourcing requirement. Huggums537 (talk) 22:47, 4 May 2023 (UTC)
 * GNG says: ... Well, not really...
 * For multiple sources: There is no fixed number of sources required since sources vary in quality and depth of coverage, but multiple sources are generally expected . (Footnote: Lack of multiple sources suggests that the topic may be more suitable for inclusion in an article on a broader topic.)
 * For secondary sources: "Sources" should be secondary sources, as those provide the most objective evidence of notability.
 * Emphasis added.
 * Neither of the "GNG says.." statements above seems supported by the text of the guideline.
 * More accurate might be:
 * You're expected to have multiple sources.
 * Those sources are expected to be secondary.
 * Rotary Engine talk 01:01, 5 May 2023 (UTC)
 * This little sub-discussion isn't about what you should do or what is generally expected, but what is theoretically possible, and it is important to have these discussions so we can avoid junky guidance tailored to suit only whatever the popular fashion of the day is while guidance for certain common sense utilitarian outfits gets left out simply because nobody ever thought to have the discussion about it or include it as part of the whole accessory. The problem with this militant focus on what you "should" do, and what is "generally" accepted is that it gets morphed into an idea more hideous and limiting known as something you're "supposed" to do.
 * P.S. You can't expect the subject to be a secondary source. That would be impossible in the vast majority of cases as WAID has pointed out. So, I wholeheartedly disagree that all sources are expected to be secondary since it is impossible to do so, and in actual practice our articles make extensive use of primary sources as they should if done appropriately. I think what would be more appropriate for the guidance to clarify is that all sources should be secondary for the purpose of notability, and indeed it does hint to this fact by saying, "...as those provide the most objective evidence of notability.". Huggums537 (talk) 09:47, 5 May 2023 (UTC)
 * The GNG, both by virtue of being a guideline and by its text, is about what you should do or what is generally expected.
 * Important to have these discussions so we can avoid junky guidance tailored to ... militant focus ... "supposed" to do ... ¿Qué? None of this seems related to anything I've written above.
 * You can't expect the subject to be a secondary source. ... Is this a general "you"? Because I don't expect an article subject to be a secondary source.
 * I think what would be more appropriate for the guidance to clarify is that all sources should be secondary for the purpose of notability. The context, whole and sole, of the GNG is for the purpose of notability (generally). I agree that the language would be better were it firmer on the conditions; while maintaining the fuzziness of the "presumed" outcome. Rotary Engine talk 11:10, 5 May 2023 (UTC)
 * I don't know if you really don't just get it, or if you're just being willfully obtuse, but either way you only asked one actual real question, and the answer is yes, it is a general "you". Nobody can expect subject sources to be secondary, therefore it is an incorrect [and misleading/misguiding] statement to say, "all sources are expected to be secondary". It is more accurate to say, "all notability contributing sources are expected to be secondary". Huggums537 (talk) 12:14, 5 May 2023 (UTC)
 * The context for the GNG is only "for the purpose of notability". If, while describing the GNG, I write (GNG says:) You're expected to have multiple sources.; Those sources are expected to be secondary, it is implicit that that is "for the purpose of notability". Nothing in what I wrote suggests that "all sources are expected to be secondary" in any other context. Nothing in what I wrote is about sources in any other context, or about "the subject"; either as a source or not. I do not know what "Nobody can expect subject sources to be secondary" means. It is not related to anything I wrote.
 * Any obtuseness apparent is because my comment appears to be either misread or misunderstood. To be clear: Based on the GNG, for notability: there are expected to be multiple sources, and "all (of those) sources for notability are expected to be secondary". Rotary Engine talk 12:34, 5 May 2023 (UTC)
 * It is more accurate to say, "all notability contributing sources are expected to be secondary". That is exactly what I believe I wrote. Rotary Engine talk 12:38, 5 May 2023 (UTC)
 * Ok. My apologies. It seems we *almost* agree then. Did you miss the part in the conversation where WAID showed that multiple sources are not strictly needed? It's a complicated issue, and I now realize, "all notability contributing sources are expected to be secondary" is also a pretty bad way of putting it because this implies that primary sources can't contribute to notability, but this clearly is not right since the subject itself must be primary so we are kind of between a rock and a hard place where I get to experience why Policy writing is hard. Huggums537 (talk) 13:21, 5 May 2023 (UTC)

Since I believe we are already deep into tangent territory, I might as well point out that one of the tensions here may concern what we expect the GNG to do versus what we expect WP:N as a whole to do. If an editor prefers to see GNG as an overall rule for which the SNGs are all interpretive guidelines, then they might be tempted to allow non-independent sources to be included in certain edge cases, e.g., the non-independent university websites sometimes relied on to document a pass of WP:NPROF 2, 3 OR 5 Notability. (Indeed, I have had my assumptions challenged in other parallel contexts, such as primary sourcing of awards with respect to WP:CREATIVE.)

On the other hand, for editors who are inclined to read several of the SNGs (like NPROF and CREATIVE) as strictly exceptions that overridde the GNG in certain cases: they might be more enthusiastic about a reading of the latter as always requiring more than one source that is independent AND secondary AND that treats the topic at length (which is not by any means the only or even the most obvious way to read GNG -but it becomes more plausible the more one reads the SNGs as exceptions rather than clarifications).

Just another example of the dense fog of assumptions in which the Notability system provides at times only indistinct guiding lights. Newimpartial (talk) 13:40, 5 May 2023 (UTC)

With some notable exceptions, I think that project participation in debates in their area is a net plus and they bring more expertise than bias to the discussions. I think that the notable exception is where the project has a propensity/defacto mission towards creating large amounts of stubs and tiny articles and the debate is in that area in which case IMHO their goals tend to conflict with those of Wikipedia. <b style="color: #0000cc;">North8000</b> (talk) 14:01, 5 May 2023 (UTC)

(Re the original topic and not the tangent about GNG) For formal RfCs, it's a good rule of thumb to leave a note in the RfC when a notice of it has been posted elsewhere, yes, even if just a general form like "I notified all the WikiProjects listed at the top of this page" for a page that lists a bunch. But like most of the users above, I don't think a guideline excluding "partisan" WikiProjects would be workable to any good end. Everyone will just argue, if more of the people who seem to come to some discussion from a notification on a WikiProject vote in a way they dislike, that it's because they're dastardly partisans. I've seen people argue that the Labour WikiProject is a bunch of communists, and I've seen one user argue the LGBT WikiProject is a bunch of gays gaying up the place (won't someone think of the children), and that's without even looking at the places that actually attract partisans, which can be quite unexpected; I'd never have thought tree-shaping was contentious until I learned there'd been a whole ArbCom case about it, and I've heard multiple people say meterology is a den of edit-warring, but how many people who'd see an RfC about a storm and notify WikiProject Meteorology would know that? If members of a WikiProject participating in a discussion causes a different conclusion than the broader community would reach ... as far as I can tell, not only the solution to that, but also the only way to know if it's the case(!), is to notify the broader community of the discussion and pull them in to it, too. Even then, as someone said above, you run into the problem that even the set of people who watchlist somewhere like CENT or the Village Pump are only a small portion of the total community, but there's only so much that can be done; we can't put editnotices at the top of everyone's watchlists to invite them to every RfC. ...or can we? En.Wiktionary puts a table of every ongoing vote in everyone's watchlist. OK, en.Wiktionary has a lot fewer votes going on, and the votes are usually about things of site-wide importance, whereas most en.Wikipedia RfCs are about one article, but maybe we could consider putting notices of every WP:VPPOL RfC into watchlists, similar to what's done for RfAs...? -sche (talk) 20:51, 7 May 2023 (UTC)


 * It looks like there are 58 RFCs open at the moment. I doubt that listing all 58 anywhere would be either convenient (it'll clutter up everything) or effective (who's going to read that whole long list?). WhatamIdoing (talk) 23:47, 12 May 2023 (UTC)
 * Totally disagree. We base Wikipedia on concensus, but trying to find RFCs is quite hard if you are not an avid or hard-core member of the community. They can be in article pages, wiki project pages, village pump pages, rule pages guideline pages!. I raised an idea on the pump ages ago saying we needed more transparency to engage more people into these discussions but it got shot down. I see what the proposal is trying to do, as some wiki projects have some very passionate editors who will fight for everything, even if it does not make logical sense or follows Wikipedia rules. A perfect example is currently here . Although not an RFC, the discussion was highlighted on the wikiprojects Talk page which is how I picked it up (I am not sure member of the project but I posted on the Talk page before so get the chat updates). Engaging the group by asking them to come along is right, but it unfortunately has seen the zealous brigade come along who ignore Wikipedia rules. However I don't think we should bypass them by not including them, but make the discussions more inclusive to all to see. Maybe we could have a separate bulletin board that users get asked of they want to subscribe to, separate from your own notifications, which if you subscribe updates you with when these happen, that way if an editor you are not interested you can turn it off?Davidstewartharvey (talk) 06:35, 14 May 2023 (UTC)
 * @Davidstewartharvey, all RFCs are listed at Requests for comment/All, and in Category:Wikipedia requests for comment, and in multiple other pages. Additionally, you can sign up for personal notifications through the Feedback request service, and if you want to follow RFCs on pages tagged by a WikiProject, then a bot assembles lists on pages such as WikiProject Medicine/Article alerts (@.Raven, this is the answer to your question).
 * The proposal above is to list all current RFCs on a page like Centralized discussion. The sentiment is good, but the page would triple in size if we just posted a list of the 58 links, without any additional information.  A list allocating a single line to each as a watchlist notices would require many editors to scroll through two screenfuls of information about currently open RFCs before they could find their actual watchlist.  It's just not practical to do this.  That's why we built all of these other methods for tracking RFCs. WhatamIdoing (talk) 03:17, 18 May 2023 (UTC)
 * > "... even if just a general form like 'I notified all the WikiProjects listed at the top of this page'" – Shouldn't the RfC template auto-notify those WikiProjects? The doc at WP:RSPM says (controversial) single-page-move discussion templates do. – . Raven .talk 01:20, 14 May 2023 (UTC)

Modifications to the default settings of Vector 2022
While it isn't clear whether the close of the Vector2022 RfC will stand, I believe it is still beneficial to determine what modifications we want to make to the skin. This would include both modifications that we can make by editing MediaWiki:Vector-2022.css and MediaWiki:Vector-2022.js, and modifications that we would need to ask the WMF to make.

I'm opening this discussion to determine the format of that discussion, and to determine which changes should be discussed as part of it.

For format I believe a multi-part RfC would be best, with each proposed change a separate question. For the questions I have created an initial list of those I consider worthy of discussion; I have included questions that I would support and questions that I would oppose but expect to have some support among the broader community.


 * Main menu:
 * Should the main menu be visible by default?
 * Should the choice to expand or collapse the main menu be persistent?
 * Header:
 * Should the mystery meat buttons be replaced with text buttons?
 * Should readers be able to disable the sticky header?
 * Should the sticky header be disabled by default?
 * Which, if any, of the following should be moved out the right hand drop down menu and moved into the header bar?:
 * A: "User talk"
 * B: "User sandbox"
 * C: "User preferences"
 * D: "Beta"
 * E: "User contributions"
 * F: "Log out"
 * Table of contents:
 * Should pages include a table of contents at the top of the article, similar to Vector2010, in addition to the sticky table of contents?
 * Should sub-headings in the floating table of contents start expanded (Collapsed sub-headings, expanded sub-headings)?
 * Other:
 * Should the previous state of the article title bar be restored (Previous state, current state)? This would involve:
 * Moving coordinates to be inline with the slogan "From Wikipedia, the free encyclopedia"
 * Moving icons denoting page protection, featured status, etc for featured article, to be inline with the article title
 * Moving the language selector to the main menu
 * When a user selects "expanded width", the content only expands to use the white space on the left of the page, not the right. Should the white space on the right also be used? (This question may have already been asked, depending on the interpretation of "full width by default")

BilledMammal (talk) 14:53, 19 March 2023 (UTC)


 * Main menu: 1. yes; 2. no.
 * Header: 1. neutral; 2. yes; 3. yes; 4. C, D, F.
 * Table of contents: 1. yes; 2. yes.
 * Other: 1. yes; 2. the page should be expanded by default as it was in V10.
 * Æo (talk) 12:12, 20 March 2023 (UTC)
 * Why shouldn’t the main menu choice be persistent, and why shouldn’t the sticky header be enabled by default? Also, why should beta and logout be out of the drop-down instead of more obvious choices such as the talk? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 01:45, 2 April 2023 (UTC)
 * With Vector-2022 now having passed all the hurdles to remain as the default this question becomes more relevant and input from interested editors is welcomed. Please also see the discussion at VPT about implementing the consensus to set Vector 2022 to full width by default. Note that this isn't the RfC yet, and is instead attempting to work out what questions should be asked, rather than asking those questions. BilledMammal (talk) 20:30, 29 March 2023 (UTC)
 * I don't think it's helpful to bundle all of these into one RfC, or even into multiple simultaneous RfCs. It's a lot to go through, and the issues are not all of similar priority. CMD (talk) 01:23, 30 March 2023 (UTC)
 * That makes sense; which ones do you believe have a higher priority? BilledMammal (talk) 01:25, 30 March 2023 (UTC)
 * I would combine the Main menu questions into one question. I would also ask header question 4 and TOC question 1. These are the questions that seem most relevant to the average Wikipedian, or reader. The most important ones IMO are the main menu questions and the TOC question.
 * On a side note, V2022 is pissing me off. I always switch back to it when I want to engage in discussion about it, and I just noticed that there is no direct way to generate a random article—you have to reach into the dropdown, click Special Pages, and scroll until you find it, or alter urls. Why? I don't get it. It was there before. How am I supposed to hone my wikipedia game skills? Cessaune   [ talk ]   14:25, 1 April 2023 (UTC)
 * @Cessaune The hamburger menu/main menu has random page, just like how everything above what links here is there. Also, I agree with your suggestions on the upcoming RfCs. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 01:46, 2 April 2023 (UTC)
 * Ah. Good. I assumed it would be under Tools. Cessaune   [ talk ]   02:36, 2 April 2023 (UTC)
 * @BilledMammal: Can we proceed with this? Æo (talk) 13:06, 4 April 2023 (UTC)
 * Needs to draft first IMO, the early version of rbv22 shouldn’t repeat <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 13:22, 4 April 2023 (UTC)
 * You are asking the WMF to make a bunch of micro-configuration changes that will be specific to this wiki and take time to implement. I agree with what TheDJ has been sayinggiving this much decision-making power to the community on these aspects are a bad idea. These tickets will all be closed as invalid. Snowmanonahoe (talk) 14:07, 4 April 2023 (UTC)
 * WMF can decide that they don't want to give this much power to us. We shouldn't be limited by the idea that WMF might try to limit us. We should proceed and see what happenes, I think. Cessaune   [ talk ]   16:35, 4 April 2023 (UTC)
 * I think their point is “we should leave aesthetics to the professionals not the community”, which I disagree with. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 16:49, 4 April 2023 (UTC)
 * Not just because professionals may be better at picking, but they also fully understand what's possible. They mentioned on the Discord that they knew the unlimited default width would be impossible from the start. I imagine most of these changes will have similar issues. We may be able to make them via JS and CSS, but if a lot of these end up being different from how they currently are special pages will look significantly different from normal pages. Snowmanonahoe (talk) 18:35, 4 April 2023 (UTC)
 * Selena Deckelmann mentioned on the Discord that they knew the unlimited default width would be impossible from the start—what. Why? And, even if this is the case, why was this not mentioned in the RfC?
 * Also, I don't see why most of these questions would be technically impossible to implement, or even hard. Something like a dual static/sticky TOC might be hard to implement, but we already know it is possible to move stuff out of dropdowns (Log in) and we know that persistence is possible. Cessaune   [ talk ]   18:41, 4 April 2023 (UTC)
 * We already have a css (CSS!) hack to implement unlimited width, why would it be impossible? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 19:25, 4 April 2023 (UTC)
 * This looks like it could end up being 10 RFC questions, or worse, a single RFC that a closer would have to try to assess consensus for in 10 different areas. I am a bit worried that the ROI on this would be low. That is, it'd take a lot of editor time and not necessarily result in the WMF listening to us. Perhaps we should focus our political capital and editor time on getting unlimited width implemented first. Another thing we could do is create these 10 tickets on Phab, which is the normal way to request software, and see if any get accepted. Some of these likely already have Phab tickets - perhaps these phab links can be edited into the original post, and we can see if any of these features are both popular and declined, and then discuss and decide if we want to push for some of these further. – Novem Linguae (talk) 20:53, 4 April 2023 (UTC)
 * I don't know what is ROI, but we could open 10 RFCs on a single page. Æo (talk) 12:51, 5 April 2023 (UTC)
 * I think they mean a figurative Return on Investment <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 13:45, 5 April 2023 (UTC)
 * Yes, I meant return on investment. In other words, is the benefit worth the effort? Another mega RFC / 10 little RFCs is quite a bit of editor time if WMF isn't likely to action it. – Novem Linguae (talk) 20:44, 5 April 2023 (UTC)
 * If the Wikipedia community is worth anything, then another RFC / 10 little RFCs are worth the effort. It is the only way for the community to manifest its views to the WMF. Æo (talk) 00:49, 6 April 2023 (UTC)
 * Seconded. It's only an RfC,one that could potentially define, for a long time, how enwiki functions. RfCs are costly, and there might not be a 'return on investment', but the enwiki community isn't a company, and, at the worst, a bit of time was wasted. Cessaune   [ talk ]   01:21, 6 April 2023 (UTC)
 * RFCs aren't the only way for this community to manifest its views to the WMF, although it's the only one most members would think of, if you believe Conway's law.
 * Editor time is valuable. Let's not waste any of it.  If you think these are good ideas, then let's write them up in, and see what the team does with them.  If they think that need evidence of community support, then the Phab tasks will get a community-consensus-needed tag added.  If they think they're good ideas, then they'll likely prioritize them and implement them.  If they think they're bad ideas, they'll likely give you an explanation for why, which could be valuable for any future discussions.   Whatamidoing (WMF) (talk) 20:57, 6 April 2023 (UTC)
 * I don't think this would be efficacious and that it would represent the general view of the community. What we are discussing here are ways to represent the general view of the community. Moreover, the team have already demonstrated that they are not willing to follow the community's consensus. Æo (talk) 19:22, 7 April 2023 (UTC)

Is this project stalled?

 * Is this project stalled? Æo (talk) 23:38, 14 April 2023 (UTC)
 * @BilledMammal: ? I cannot believe that the silent majority of users are passively accepting this imposition of an interface which is obviously hideous and destined to damage the project. Æo (talk) 08:03, 15 April 2023 (UTC)
 * 1) It's not objectively hideous, let's not pretend like everyone hates it. In fact, there is a lot about V2022 I like.
 * 2) Destined to damage the project? How? Cessaune   [ talk ]   14:31, 15 April 2023 (UTC)
 * 1) 60% of the community opposed it. 2) That is indeed my opinion; I think that the mobile-esque design will inevitably lead to a further fragmentation and loss of quality of the articles' content, because of structural reasons which were widely discussed in the RfC. Æo (talk) 17:18, 15 April 2023 (UTC)
 * From what I've seen in the RfC, the removal of the inline ToC simply disrupts certain people's geometry of the article, not the article content itself? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 18:37, 15 April 2023 (UTC)
 * There are many other controversial aspects beyond the ToC, which is indeed a major one. For instance, I see that the font size in V22 seems to be bigger than in V10. I don't think this is an improvement; I feel better with the smaller font and wider texts of V10. Has this ever been discussed? Æo (talk) 13:13, 16 April 2023 (UTC)
 * Both skins' body text font sizes are 1em * 0.875, defined in div#bodyContent. The font size didn't change. So what aspects harmed article content quality besides ToC, which I'm still not quite convinced of? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 13:42, 16 April 2023 (UTC)
 * The main one is certainly the ToC, the other one is the general shrunken appearance of the articles' spaces. V22 gives (me) the impression, at the same time, of both "wasted white space" and claustrophobic "lack of space". Æo (talk) 14:29, 16 April 2023 (UTC)
 * Wasting lots of space doesn't lead to degraded article quality. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 15:43, 16 April 2023 (UTC)
 * Shrinking the articles in a smaller space certainly does. There is something weird in the general appearance of V22, and it has been expressed in different terms by different users according to their different outlooks. It is a general weird appearance given not by a single characteristic but by many of them together. For some it is the width, for others it is the ToC, for still others the menus. In general terms, V22 has not been appreciated by the community. Æo (talk) 16:14, 16 April 2023 (UTC)
 * I don't find this argument particularly compelling. The community you refer to is no where near agreement on anything pertaining to V2022. V22 has not been appreciated by the community—maybe? This is just opinion; personally, I think it's pretty evenly split.
 * Secondly, how does shrinking the articles in a smaller space lead to degraded article quality? I mean, I don't like the shrinking, but I don't see how smaller body size is necessarily good or bad. Cessaune   [ talk ]   16:30, 16 April 2023 (UTC)
 * Hasn't 60% of the users who took part in the RfC opposed V22? 60% is the majority. Æo (talk) 19:09, 16 April 2023 (UTC)
 * You will have a hard time proving that is representative of all users. I strongly suspect that many users who are satisfied with V2022 (as I am) didn't bother to participate in that RfC. Donald Albury 19:23, 16 April 2023 (UTC)
 * I think the RfC was a good representation of the opinion of the general community. I also read comments by users (including at least two admins) who defined V22 "horrible" and yet did not take part in the RfC. Æo (talk) 19:28, 16 April 2023 (UTC)
 * P.S. A majority, in this case an absolute majority, in any case is not, it is representative of significantly more than half of them. Æo (talk) 19:42, 16 April 2023 (UTC)

60% isn't representative of the general community, just most of it. 40% is still quite big. Plus it's 58.7% if you count the neutrals, which doesn't count as an absolute majority. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 20:41, 16 April 2023 (UTC)


 * An absolute majority is by definition a majority over 50%. 60% is the absolute majority of the Wikipedia community; 40% is a big minority. Æo (talk) 20:59, 16 April 2023 (UTC)
 * Huh, I may have confused it with other qualifiers of majority. Still, 40% is a very big minority, so you can't use 60% to represent the entire community. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 21:27, 16 April 2023 (UTC)
 * Selection bias plays such a major factor in all of this that I think using direct numbers isn't a good way of going about things. Cessaune   [ talk ]   21:28, 16 April 2023 (UTC)
 * As I already wrote above, I think that the general opinion of the community was well represented in the RfC. Æo (talk) 15:16, 17 April 2023 (UTC)
 * Whenever I am not logged in with my account (set with V10) and I have to read a Wikipedia page in V22, I find it repulsive; the new structure and organisation of spaces is literally distracting, disturbing and annoying. While the font looks bigger, all the elements of the page look cramped, and at the same time they look disconnected, disorganised and confusing. The ToC does not provide a structure to the article and the two appear as separate things. Æo (talk) 15:26, 17 April 2023 (UTC)
 * Okay. This, however, is all opinion. How do you qualify the statement that V22 has not been appreciated by the community? None of the things you are saying are objectively true. Cessaune   [ talk ]   15:27, 17 April 2023 (UTC)
 * For me, that V22 has not been appreciated by the community — at least by a significant majority of it (the aforediscussed 60%) — is a fact. The things I have expressed have been widely discussed, from different points of view, in the RfC. Æo (talk) 15:34, 17 April 2023 (UTC)
 * 58%/60% is an absolute majority but not a significant one. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 15:37, 17 April 2023 (UTC)
 * That absolute majority does not even represent merely a non-appreciation, but also a rejection, since the opinion vote was for V22's withdrawal, i.e. against its deployment. Æo (talk) 15:44, 17 April 2023 (UTC)
 * A rejection only by a bit over half. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 13:56, 18 May 2023 (UTC)
 * As I said above, the font is the same size as it was before. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 15:31, 17 April 2023 (UTC)
 * It looks bigger, maybe due to an optical effect. Æo (talk) 15:36, 17 April 2023 (UTC)
 * Looks the same to me, on my screen. Cessaune   [ talk ]   15:40, 17 April 2023 (UTC)

Dear Lord, if this isn't bludgeoning, I don't know what is. There's a simple solution: change your personal skin. Here. Wikipedia is a global multilingual project, why would you wanna change the user experience only here and only based on anonymous unqualified opinions of a few? It's sad that this is happening. I'm sure many are getting tired of it. 38.68.160.148 (talk) 18:30, 17 April 2023 (UTC)


 * How is this bludgeoning? It's not a ton of comments repeating the same thing, it's a couple of different proposals on a topic. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 19:25, 17 April 2023 (UTC)
 * @User_talk:38.68.160.148 "based on anonymous unqualified opinions of a few". In my (anonymous, but possibly professional) opinion - most of the feedback was high quality and the users/editors are passionate and knowledgeable. The WMF devs tried to engage (but it was with a completed product), but they were constrained by centralisation and the mission which you mentioned indirectly
 * " Wikipedia is a global multilingual project, why would you wanna change the user experience only here' Other wikis have also complained. Wikipedia is not a global multilingual project - it's a series of once off translations of content that swamps local editors and destroys editor community building . (Christian missionaries are the only one other group that translates into 300+ languages ).
 * 'There's a simple solution: change your personal skin" It is unjust if readers don't have the same choice. It should be changeable everywhere as users similar to editors (just the same as developers and researchers) NEED control of their environment thrugh preferences, information density, and efficiency (often to the point of negative cost/benefit because something annoys them); Wikipedia is an IDE for the editors, and similar to all IDEs an information dense screen is needed.
 * Wakelamp d&#91;@-@&#93;b (talk) 16:42, 1 May 2023 (UTC)

I think that EN:Wikipedia is the best ones to make these decisions. Wikipedia is the ship that the WMF ivory tower and it's pet projects rides on. And until we can implement structure for the Wikipedias to decide together, en:wikipedia being the largest is the best place for that to come from. The largely self-appointed WMF ivory tower certainly isn't. <b style="color: #0000cc;">North8000</b> (talk) 20:37, 17 April 2023 (UTC)

From the WMF's viewpoint, I expect the project is now permanently stalled. They've achieved their objective of pushing out Vector 2022, its developer has left the organisation, and the rest of the WMF team will have moved on to changing something else. If there's consensus to mitigate some of the worst effects of the new skin, it's now up to enwp to implement it locally. Certes (talk) 08:11, 18 April 2023 (UTC)


 * AHollender was the lead designer, not the sole developer. Of course there's still a team on v22. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 11:44, 18 April 2023 (UTC)
 * Should we set up a page so we can coalesce all the comments? We are good at creating articles, but our community discussions tend to become very large and eventually just sort of end.
 * As part of that it would be good to discuss how WMF's engagement with the community could be improve. "The non-profit noted that it has worked with 30 different volunteer groups from all over the world, including from India, Indonesia, Ghana, and Argentina to conceptualise and actualise the improvements made to the desktop interface, which is the first major redesign introduced by Wikipedia in over 10 years.".
 * I am sorry to hear he left, as I liked that they and their teams were trying to engage. (I am not certain whether his article on V2022 has been mentioned so I have included a link..
 * The claimed benefits seems very high though. "Wikimedia Foundation makes clear that it hasn't removed any functionality, and that the changes led to real-world gains in testing with international volunteer groups. Users searched 30 percent more often, and scrolled 15 percent less. " . I would also be concerned about the reasons for more searching and less scrolling - both of those could have an opposite explanation in terms of vector 2022 creating a worse UX.
 * --Wakelamp d&#91;@-@&#93;b (talk) 17:33, 1 May 2023 (UTC)
 * That’s a great idea! Problem is what comments we should include and whether we should just merge it in an existing article like Vector 2022 <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 17:40, 1 May 2023 (UTC)
 * Support: The discussions about V22 have become rambling, and therefore fewer users are seeing them and taking part in them. It would be better to gather them on a single page. I also agree with the concern: who says that more clicks are better than scrolling in terms of reading and understanding an encyclopedia article? Æo (talk) 20:21, 2 May 2023 (UTC)
 * @Wakelamp: What do you propose to proceed? Æo (talk) 10:31, 6 May 2023 (UTC)
 * @Certes, Aaron is right. Alex was a designer ("lead" is a prefix indicating his professional experience, the same way I'm a "senior" and Olga is a "principal"), and he wasn't the decision-maker regarding what the team would work on. Perhaps we'll pick projects tied closely to Vector 2022 and resulting from the code cleanup which, from the technical perspective, Vector 2022 is. Perhaps we'll have a meeting focusing on the plan for the next fiscal year itself. Subscribe to our newsletter and look out for news! SGrabarczuk (WMF) (talk) 13:34, 18 April 2023 (UTC)
 * My apologies for getting the job title wrong, but the point stands: the person in charge has completed their work and moved on (whether internally or externally isn't really important) and it's now time for enwp to pick up the pieces. Certes (talk) 17:52, 18 April 2023 (UTC)
 * It’s not just the job title. Just one experienced person leaving doesn’t mean the project’s over. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 18:51, 18 April 2023 (UTC)

The team, in their statistical analyses, highlighted the increase of clicks to navigate articles as an indicator of V22's increased usability. This is not necessarily and indicator of usability, let alone of success among the users; to the contrary, the increase of clicks needed to navigate the articles indicates that with V22 moving between the various sections of an article and between different articles has become more awkward, as pointed out by many commentators during the RfC. Does the team realise that an encyclopedia project needs content quality and not more clicks? Was V22 specifically designed to increase the overall amount of clicks?--Æo (talk) 14:41, 21 April 2023 (UTC)


 * Increased number of what clicks? What’s the context/source? How is moving between the various sections of an article and between different articles more awkward? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 14:52, 21 April 2023 (UTC)
 * Here: Æo (talk) 18:13, 23 April 2023 (UTC)
 * How does increased ToC clicks not reflect navigational usability? If anything it does reflect that the new ToC is useful in aiding navigation. It's not like there's a faster way to navigate between article sections. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 18:32, 23 April 2023 (UTC)
 * Page down and end are faster.©Geni (talk) 08:34, 5 May 2023 (UTC)
 * Between specific sections, not just scrolling down which is imprecise and slower! <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 11:40, 5 May 2023 (UTC)
 * @Geni: What do you mean? Æo (talk) 10:29, 6 May 2023 (UTC)
 * They mean the "Page Down" and "End" keys, which is present on a lot of keyboards above the arrow keys <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 12:54, 6 May 2023 (UTC)
 * @Aaron Liu: As I wrote here, . In other, and simpler, words, V22 is designed in such a way that does not aid concentration on the article but forces more scrolling and clicking. It can be readen in between the lines that this was the team's objective from the beginning. Æo (talk) 10:28, 6 May 2023 (UTC)
 * To be fair, I don't think we can conclude that the team deliberately made Wikipedia harder to use. It's far more likely that, although they may consider themselves UI experts, they lack the experience of people who actually read Wikipedia daily, and were unaware of the damage they were doing. Certes (talk) 10:38, 6 May 2023 (UTC)
 * The wording for the "more clicks" message suggests that they only counted clicking on sections, not the expand buttons to the left of sections.
 * Also, the ToC automatically scrolls as you scroll down. Plus, users don't always need to see the full ToC, and there aren't much solutions to mitigate these for the floating ToC. It's not like the in-article ToC provided similar features. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 12:47, 6 May 2023 (UTC)

Today I noticed that some inexperienced users have continued to express support !votes to the WP:V22RFC2 despite the latter's closure (and their !votes have been reverted for this reason): here an IP; here .--Æo (talk) 19:43, 17 May 2023 (UTC)
 * I don’t think two !votes in two separate months, one of them soon after the RfC closed, is much of importance to mention. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 00:24, 18 May 2023 (UTC)
 * Yet their views expressed in their comments might be. Æo (talk) 13:14, 18 May 2023 (UTC)
 * How is it more important than any other support vote? Also note that the IP does not know how to count. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 13:54, 18 May 2023 (UTC)
 * I did not say that they are more important than previous votes. Æo (talk) 19:39, 18 May 2023 (UTC)
 * What I mean is I have no idea why you suddenly posted that reply, something you don't do for most votes. <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 21:05, 18 May 2023 (UTC)
 * I simply noticed those votes yesterday, and they are the only two votes which came after the closure. What other votes should I link? It seemed relevant to me to notify their presence here, given that they have been reverted. Æo (talk) 21:11, 18 May 2023 (UTC)
 * Since they have been reverted and it's just two edits, is there any need to notify their presence? <span style="color: rgb(6,69,173); text-decoration: inherit;">Aaron Liu (talk) 21:36, 18 May 2023 (UTC)

ARBPOL Amendment brainstorming
Interested editors are invited to join brainstorming about how to improve the Arbitration Policy amendment process at User:Barkeep49/ARBPOL amendment sandbox. Best, Barkeep49 (talk) 20:13, 19 May 2023 (UTC)

How to shorten the Manual of Style
As you know, the current manual of style is really long, and it could benefit from shorten it a bit. I've managed to make the MOS size goes down from 218.7 kB to 214.3 kB, but that's because I'm tackling the low-hanging fruits like bloated sections and such. Is there any other way to make the manual of style even shorter? CactiStaccingCrane (talk) 16:00, 15 May 2023 (UTC)
 * You could split out more subsections. -- Jayron <b style="color:#090">32</b> 16:41, 15 May 2023 (UTC)
 * This is doomed, but if you want to do this, then you should be counting words of readable prose. Otherwise, you'll be really excited when someone removes 700 bytes of "unnecessary" whitespace, even though it won't make any actual difference. WhatamIdoing (talk) 03:48, 18 May 2023 (UTC)


 * Well, if SHORT is the goal… it could say: “Write best English U can… it’s OK… someone will eventually correct you, no matter what you write. And, of course, another person will then correct that correction and a huge argument will ensue that will last for months and months… CAUTION, stay away from such fights. Just the other day an inexperienced editor was almost mauled to death when caught between two style warriors. When confronted with an angry style warrior, back away calmly and silently.”
 * That’s really all that a normal editor needs to know. Blueboar (talk) 22:34, 19 May 2023 (UTC)
 * I don't think its length matters. No one reads it in one sitting. It's like a grammar book, you want to know how to write something, and it should have the answer. Comprehensiveness is good; all that matters is that it doesn't contradict itself, and is well-structured so people can find the answers they're looking for. Seems to do well on both fronts. DFlhb (talk) 01:27, 20 May 2023 (UTC)

Improving the semi-protected page windows 10 version history
Per 's recent suggestions @ WP:ANI, I take this opportunity to make my request here: replace the page with this revision I tested on the WP:SANDBOX so that editors like updates the article without adding too much/many bytes. I hope my request here is not controversial now.197.238.55.142 (talk) 06:43, 21 May 2023 (UTC)
 * If this is more of your nonsense about saving storage space by removing spaces, please stop wasting everyone's time. <b style="color:red;">E</b><b style="color:blue;">Eng</b> 06:01, 22 May 2023 (UTC)
 * In case 197.238 reads this:
 * Please don't try to save storage space by removing white space from the wikitext. There are two reasons for this:
 * It uses more disk space.
 * It has no effect – including on the size of files sent – for the reader.
 * I realize that this first point is counterintuitive, but MediaWiki stores every single version. Removing spaces == adding a new version to the database.  Making a new version doesn't "remove" anything; it adds something.  If your "space-saving" version is 1% smaller, there would have to be 100 more edits made to the page just to break even.
 * Also, Don't worry about performance. Please.  Disk space is cheap.  Plain old wikitext is tiny.  That "large" page is an eighth of a megabyte.  I remember when that amount might be all the disk storage allocated to a user, but that was back when mainframes used disks the size of a washing machine, and has nothing to do with modern technology, in this age when a supercomputer fits in my pocket.   We're talking about a revision that wouldn't have filled even half of a 5-1/4" floppy disk.  These days, the amount of disk space needed to store every single revision of that page, current and several thousand past versions together, would cost about a nickel (US$0.05).  It's okay.  Really.  If the devs are ever concerned about file sizes, they'll let us know.  In the meantime, please don't worry about it.   Whatamidoing (WMF) (talk) 23:56, 22 May 2023 (UTC)

Deprecate future use of general references?
I don't know if this is a WP:PERENNIAL proposal or if there's any background to this (which is why I'm posting at the idea lab), but I get the impression that WP:General references are a relic of early Wikipedia that aren't acceptable any more. It's obvious why they're unhelpful in longer articles. But even with stubs, I've found general references to make verification even more difficult and time consuming than unreferenced content. Any sort of expansion or verification requires that you either check every claim to every general reference, or that you scrap the general references and start from scratch.WP:V already sets inline citations as the bare minimum for demonstrating verifiability, so general references don't even accomplish anything policy-wise. Obviously I'm not going to propose that we go through and immediately remove every general reference, but I think it would be beneficial to disallow their use going forward. Editors would still be free to use their preferred citation style, but it's essential that we know where the citation applies in the text. Thebiguglyalien ( talk ) 17:40, 8 May 2023 (UTC)
 * No… There is no reason why you can not include a list of uncited sources as “further reading” or “external links” at the end of an article. Such references are often helpful for the reader. Blueboar (talk) 17:56, 8 May 2023 (UTC)
 * I'm not talking about MOS:FURTHER or MOS:LAYOUTEL. I'm talking about WP:GENREF. Thebiguglyalien  ( talk ) 18:02, 8 May 2023 (UTC)
 * Ah… I misunderstood … sorry. Blueboar (talk) 18:14, 8 May 2023 (UTC)
 * It does highlight part of the issue though. These areas can be blurred at times, where an external links section tries to play the role of a general references section. Thebiguglyalien  ( talk ) 18:18, 8 May 2023 (UTC)
 * I think this is a bad idea. General references can provide a good basis for future expansion of the article.  We should encourage their use, rather than discourage.  -- Jayron <b style="color:#090">32</b> 18:28, 8 May 2023 (UTC)
 * I don't think it's too much of an ask for editors to format them as inline citations. Inline citations don't make the source less useful, but general references do make the prose less useful. Thebiguglyalien  ( talk ) 18:35, 8 May 2023 (UTC)
 * It's functionally no different from a "further reading" section. It isn't too much to ask of you to add inline citations when you come across them where needed.  There's also no need to ban the use of further reading sections, whatever they are called.  -- Jayron <b style="color:#090">32</b> 18:37, 8 May 2023 (UTC)
 * Only times I tend to use general references is in article's I haven't worked on but have found sources for. Typically would be in a situation where an unreferenced article brought to AfD, and if I find sources but don't feel like actually doing edit-edits, I'll just add them as general references so the article at least isn't unreferenced anymore. I understand if article is kept, references can be found in the closed discussion, or I could put them on talk page for people to find, I personally find its better to have them in the article. If I can use a source as a citation for something I will, but I don't like using it randomly somewhere in lead when source doesn't help verify whatever lead currently says. Also I believe WP:V only sets minimum for quotations and material that is challenge or likely to be challenged, requires an inline citation, otherwise I believe a general reference could be used to satisfy WP:V in the case of a stub with a few sentences. When it is longer that, it does become confusing when you are trying to verify specific things and you only have general references for entire article. Another situation for general reference are on List of X articles, sometimes general references work better than an inline citations all over the table/list. <b style="color:#000080; font-family:Tahoma">WikiVirus</b><u style="font-family: Tahoma">C <b style="color:#008000">(talk)</b> 18:41, 8 May 2023 (UTC)
 * I kind of agree that we don't want to have a lot of additional articles lacking inline citations. I don't know what the practical effect of formally deprecating them would be, though: how many new articles use GENREF only? I mostly see them when people translate from the German Wikipedia. I somewhat fear that we'll see more people translating a GENREF article, not interact with the sources much, and just add one or two inline citations so the article looks like it is compliant (we had a prolific machine-translator do that until they were banned in 2021). —Kusma (talk) 18:48, 8 May 2023 (UTC)
 * For scale, the problem is tracked here, with 101,786 articles using too many general references or inappropriately using further reading and external links as references (both of these are not supposed to be general references and should not be conflated with them). This isn't a perfect count, because there are likely false positives and there are likely applicable articles haven't been tagged. I don't know what the average age of these articles is, but it's a rough idea of where we stand. Thebiguglyalien  ( talk ) 18:58, 8 May 2023 (UTC)
 * I would guess that the majority of these articles are at least 10 years old. —Kusma (talk) 19:08, 8 May 2023 (UTC)
 * Expanding on my post below, they sort of hide unsourced articles by "pretending" that they are sourced. <b style="color: #0000cc;">North8000</b> (talk) 19:20, 8 May 2023 (UTC)
 * If an article is based on a single source that doesn't have page numbers or other subdivisions, inline references aren't actually superior to a general reference section for WP:V. The main problem in that case is the single source, not the lack of inline citations. —Kusma (talk) 14:52, 9 May 2023 (UTC)


 * (EC) Even though they later made a statement that conflicted it Thebiguglyalien's statement "....I've found general references to make verification even more difficult and time consuming...." is important because unused items called "references" sort of imply that they are supporting the material even though per wp:ver, without in-line citations they aren't. And thus imply that to challenge verifiability one must prove a negative. On the flip side, it's a good practice to find sources (especially 1-2 GNG sources) before starting the article and article text and so when an article is being developed in article space, there should be a place to put useful sources that don't yet have any in-line citations. Sometimes I've temporarily put in an "Unused references" section. Might renaming it "Unused references" be an idea to both solve the problem and retain the usefulness? <b style="color: #0000cc;">North8000</b> (talk) 19:14, 8 May 2023 (UTC)
 * I've used Template:Refideas for that purpose, though it has the glaring weakness that the talk page isn't as visible for this sort of thing. Thebiguglyalien  ( talk ) 19:18, 8 May 2023 (UTC)
 * If it bothers you when you find them called "general references", just rename the section "further reading" and the problem gets solved. There's no need to create some grand policy or anything.  Just fix the problem.  Policy not required.  -- Jayron <b style="color:#090">32</b> 13:33, 9 May 2023 (UTC)
 * But then couldn't I be rightly accused of "removing references"? For better or for worse, WP:GENREF currently holds general references as a valid form of reference. I made this post to see if there was interest in changing that. Thebiguglyalien  ( talk ) 13:56, 9 May 2023 (UTC)
 * How do we feel about templates like Template:Ice hockey stats then? There are thousands of sports bio articles that are collections of statistics about athletes with a template like this in the "external links" section instead of actual references. Thebiguglyalien  ( talk ) 22:42, 8 May 2023 (UTC)
 * I think these are useful as part of the external links section and for sportspeople are probably more helpful than most of the links in the authority control template, but the statistics tables in the article should also have sources placed in/below them. EdwardUK (talk) 13:26, 9 May 2023 (UTC)

The main drawback to using general references is that they make verification much more difficult. To find if a claim is verified, one would have to meticulously search through the reference list- there is no way to tell which reference supports what. For short, one-paragraph stubs this is hardly a problem, but the larger the article, the more unwieldy and awkward a general reference list becomes. If an editor adds a claim that is not verified by one of these general sources, it is much harder to catch, as one cannot merely consult the relevant inline citation. Thus, reliability potentially decreases. Edward-Woodrow (talk) 19:58, 9 May 2023 (UTC)
 * There was a time... Many of my early articles had no in-line sources, often with the only sources in External links. The time when that was acceptable is long past. Having a bunch of "sources" that are not cited anywhere in the article is not helpful, and, as others have pointed out, is detrimental to an article. Such uncited sources can and should be moved to Further reading sections until such time as they are actually cited in the article. In fact, I have been doing that ocassionally for a while now. - Donald Albury 01:27, 9 May 2023 (UTC)
 * When the source is listed there should be evidence of it where inline citations can be used and should be added, but if it is not explicitly connected to any specific material in the article (MOS:NOTES) then I would consider it as further reading rather than a general reference and would be happy to see this changed in the manual of style. If the general references are from hard to access sources such as offline or subscription only journals, then if it would be difficult for many editors to convert them into inline citations. Even worse is when the websites listed have since become dead-links and have sometimes been removed because of this. EdwardUK (talk) 13:29, 9 May 2023 (UTC)
 * Inline citations are better than general references, but general references are better than no references. So I guess it depends how strongly such a deprecation would be worded. I wouldn’t want to discourage editors from adding a general reference when the alternative is no reference at all. Barnards.tar.gz (talk) 14:45, 9 May 2023 (UTC)
 * I think this is generally a good idea, but the actual change will have to be carefully worded- as Barnards.tar.gz said, any reference is better than none.
 * Agree that this is a problem. In essence they harmful to obtaining wp:verifiability and helpful towards developing the the article, and for references with GNG attributes, helpful for establishing wp:notability. Maybe just add wording that reinforces that only inline citations count towards meeting wp:verifiability would give us the best of both worlds.  Or have / require a separate section titled "Unused references"  which makes that clear. <b style="color: #0000cc;">North8000</b> (talk) 20:53, 9 May 2023 (UTC)

No thanks. References are sadly only as good as the person looking through them. A determined user can find problems with even the best sourced article. As someone who goes through a lot of foreign and older articles, any source that isn't a website is sadly useless in the end because someone can always doubt its existence or question its content. And even websites can be useless as references because websites change their url's or sometimes go offline and then the source is gone. I don't have a problem with general references. There's various situations where that may be the best call. Gaining access to various sources can be an expensive and time consuming task, and people in general are limited to where they live, what language they speak and what technology they have. And as I've said before here - if you want to raise the standard on what is acceptable content, you better be prepared to increase your workload with it, because it will mean more AfD debates and more generally pointless debates.KatoKungLee (talk) 16:43, 10 May 2023 (UTC)
 * The reason we still keep general references around is the same fundamental reason that the subject of an article is a primary source or what you would otherwise call a "general reference" to itself. Eliminating "general references" makes about as much sense as eliminating the subject of an article simply because it's a little more work to pore through the entire subject to verify some small fact about the subject mentioned in the article. Eliminating the subject means eliminating the article. There are many forms of general reference that are valid other than just a simple "general references" section. The "further reading" has already been mentioned. Huggums537 (talk) 05:08, 10 May 2023 (UTC)
 * They're already 'deprecated' in the sense that everybody agrees that they're, at best, a starting point that should be replaced with inline citations. And as you say, WP:V already makes it very clear that inline citations are the desired standard. So what would your proposal do, in practice? –&#8239;Joe (talk) 06:13, 10 May 2023 (UTC)


 * Of course, not everybody can see sources that are not currently on-line and not behind a pay wall, but the best sources are often not on-line or are behind a paywall. We have to depend on editors who do have access to such sources to verify that they do support the content of the article. As for on-line sources disappearing, there are the archives (I use, and donate to, the Internet Archive). It is good practice to pro-actively include a link to an archived copy of a web page used as a source, although it is sometimes possible to find an archived copy after a web page has disappeared. Even for sources that are not on-line, or are behind a paywall, it is so much easier for an editor who does have access to verify that content in the article is supported by that source if the citation includes page numbers or locations. It is very annoying to see a list of "General references" with no indication of what part of a source supports what content in the article. Going forward, I will say that it is very rude to other editors and readers to add a source to "General references" with no indication of how the source supports anything in the article. Donald Albury 17:19, 10 May 2023 (UTC)

I appreciate from an editing policy perspective, references can be seen simply as a means to the end of verifying individual statements. From an encyclopedic attribution perspective, though, it is reasonable for editors to list significant sources they read that influenced their text contributions, particularly with large text changes such as when an article is initially created. Thus I would not favour a blanket rule prohibiting the listing of general references. isaacl (talk) 17:04, 10 May 2023 (UTC)


 * I'm not suggesting that we ban the use of references. I'm suggesting that we require they be used in a way that actually makes them verifiable (e.g. inline citations). Thebiguglyalien  ( talk ) 17:35, 10 May 2023 (UTC)
 * I also just noticed that it conflicts with wp:ver. It says that they support the material in the article and wp:ver says that only in-line citations do that. <b style="color: #0000cc;">North8000</b> (talk) 17:57, 10 May 2023 (UTC)
 * Yes, I know. You proposed disallowing general references. I'm saying that I do not support disallowing general references as I see a purpose for them beyond that which is met by inline references, which I agree the community supports as a best practice. isaacl (talk) 21:32, 10 May 2023 (UTC)
 * As an example, when preparing a new article on topic X, I may read many sources, including broader overview articles from reliable sources. I can choose to cite all statements to more specialized sources that directly address each specific aspect. However from an attribution perspective, it is reasonable for me to list other significant sources such as the overview articles which have influenced my writing, so others can trace back the context in which I wrote the article. We're accustomed to the add-one-piece-of-info-at-a-time edits that make up much of Wikipedia's edits, where there is a direct association between text written and citation. Some edits, though, are larger scale and thus attribution beyond inline citations can be desirable on a broader scale than the per-segment-of-text level. isaacl (talk) 21:45, 10 May 2023 (UTC)

My idea to solve it would be to replace:
 * "A general reference is a citation to a reliable source that supports content, but is not linked to any particular text in the article through an inline citation. General references are usually listed at the end of the article in a "References" section,

with


 * "A general reference is a citation to a reliable source, but is not linked to any particular text in the article through an inline citation. General references are usually listed at the end of the article in a separate "Unused References" section"

This: Sincerely, <b style="color: #0000cc;">North8000</b> (talk) 21:52, 10 May 2023 (UTC)
 * Resolves the conflict with wp:Ver
 * This reinforcement / clarity that they are not used/fufilling wp:ver solves all of the noted problems.  Most relate to the "vague implied attribution" interfering with / impairing wp:ver compliance or efforts to ask for it.
 * Retains them and all all of their benefits including for article development and also, when they are GNG types, for establishing wp:notability of the topic.


 * I'd probably end up supporting something like this as a marginal improvement if it came to a discussion, though it still doesn't have the affirmative "citations should be inline" that I'd prefer. I'm also wondering how that would play against articles like this. Don't call it unreferenced; look at the bottom of the infobox (for some reason). This type of article, which is quite common among sportsbios, seems to walk right along the boundary between referenced and unreferenced. What are we even supposed to do with these? Thebiguglyalien  ( talk ) 22:02, 10 May 2023 (UTC)
 * That linked article has so many major problems in this respect that I can't see how to relate it to this discussion. <b style="color: #0000cc;">North8000</b> (talk) 17:42, 11 May 2023 (UTC)
 * Articles like this are what prompted this discussion. I'm not worried about articles where the general references are easy to resolve. I'm worried about the ones where an attempt at non-inline references makes future work on the article more difficult. Thebiguglyalien  ( talk ) 17:54, 11 May 2023 (UTC)
 * General references are usually listed at the end of the article in a separate "Unused References" section" seems an abrupt shift in this discussion about general references. They are not "unused references". Referencing has evolved (thankfully) in Wikipedia from being thought unnecessary, to being needed only if material was likely to be challenged as incorrect, to being the backbone of our usefulness as an encyclopedia. But we have a lot of older material, especially in scientific and technical articles, that went in earlier. General references were certainly not "unused" at the time, and to retroactively declare them that now leaves accurate material open to being summarily removed from articles.
 * I worry also about declaring them "deprecated", even just for new material. Things declared such on Wikipedia then seem to generate projects to remove them entirely. I this necessary? In technical areas I haven't seen new articles or new material using general references being allowed. Is this a problem in other areas? Are there other ways of handling the problems? StarryGrandma (talk) 17:45, 11 May 2023 (UTC)
 * What about saying "bibliography" or "general references" section? JoelleJay (talk) 23:35, 11 May 2023 (UTC)

If your concern is that there are too many sportsperson biographies only referenced to a statistics database, WP:SPORTCRIT #5 already addresses this: Sports biographies must include at least one reference to a source providing significant coverage of the subject, excluding database sources. I've been placing the No significant coverage (sports) tag on such biographies so they can be tracked and eventually improved/draftified/redirected/deleted. Jogurney (talk) 18:21, 11 May 2023 (UTC)


 * I'm concerned about the lack of verifiability, but BLPs are my main concern, and sportsbios are the ones I've found most difficult. My understanding was that such sources only had to exist, and I have nominated many non-notable sportsbios for deletion. Are you saying that WP:NSPORTS overrules WP:NEXIST? They do seem to contradict each other, looking at it more closely. Thebiguglyalien  ( talk ) 18:30, 11 May 2023 (UTC)
 * Yes, per WP:NSPORTS2022; there is a consensus to add an inclusion criterion for sports biographies requiring that they have at least one reference to a source which has significant coverage of the subject. So the existence of such sources is no longer sufficient; at least one must be included in the biography (and the No significant coverage (sports) tag can help track that). Jogurney (talk) 18:37, 11 May 2023 (UTC)
 * Good to know. I've been tagging and tracking unreferenced BLPs, so I've got a list of over 800 sports BLPs without references. I'd imagine most of them fail NSPORTS. I've been using BLPPROD for the ones that have no links whatsoever, but even that has been going slowly because there are so many and obviously I don't want to BLPPROD them all at once. Thebiguglyalien  ( talk ) 18:49, 11 May 2023 (UTC)
 * Yes, the scale of non-compliant sports biographies is enormous. User:Lugnuts created thousands of one-line Olympian biographies only sourced to a statistics database, and there are dozens of editors who created hundreds of sports biographies over the past 10-15 years that are similarly sourced. Jogurney (talk) 18:56, 11 May 2023 (UTC)
 * Yeah, I've encountered many of them while going through all of the unreferenced BLPs. Many don't even have the luxury of a database reference. I've been adding database references to those so that they at least have something, but I'll make sure to tag them appropriately as I see them. Though I wonder whether everyone will actually be able to agree on what to do with them. Thebiguglyalien  ( talk ) 19:15, 11 May 2023 (UTC)
 * The requirement to include at least one source demonstrating that the standards for having an article are met is really a documentation requirement. It doesn't set a minimum bar for having an article, nor does it prevent editors from later finding sources and adding references. The idea is that since editors ought to have found appropriate sources when creating an article, they should save everyone time and include a reference to at least one. isaacl (talk) 21:58, 11 May 2023 (UTC)

To recap, the problem is that they give a false allusion of wp:ver compliance. But they also do good. So my solution removes the problems but retains general references. One post above illustrates the problem. It said that declaring them "unused" now leaves accurate material open to being removed from articles. They are in essence saying that the "false allusion" that I referred to prevents removing uncited material which is clearly in violation of wp:ver. <b style="color: #0000cc;">North8000</b> (talk) 18:51, 11 May 2023 (UTC) If this 👆🏽 can't be our sixth Pillar, can we make it the official motto of the Wikipedia: namespace? I'm getting the vibe here that User:North8000's "Unused References" idea is coming from a unique perspective on General References, one which I feel misinterprets them as Further Reading. For the record, changing the naming (or ordering) of any footer material is at WP:PERENNIAL— although personally I'd love to participate in a fresh argument about some of that.WP:V specifies only four types of claim that require inline citations, so it's not correct to state that in all cases General References don't satisfy this policy.I looked at the example of the type of article that prompted this discussion, clicked on the second reference, and saw in database report format everything the article claims in prose, without even needing to scroll down. So it's not clear to me how that's problematic, and I'd go so far as expanding upon User:WikiVirusC's statement that general references are preferable for tabular data and claim that I think a general reference for stubby bois like the example is preferable to an article where every claim is cited inline to the same source, which adds unnecessary clutter.It's already pretty clear in WP:GENREF that inline citations are preferred. If we want to, I'd support adding that explicit statement to the final sentence of the first paragraph, so it would read They are frequently reworked by later editors into inline citations, which are preferred. I don't think we need anything stronger, and honestly I feel like the bigger issue with that section of policy is how it starts out A general reference is a citation... and then closes with a sentence drawing a distinction between cited and uncited references, neither of which has been defined or used elsewhere in the page. Presumably we all know what this is saying, but it seems like it would be unclear to a new editor.It's telling how thoroughly we've spoiled ourselves for ease of verification when editors can earnestly argue that general references make claims not possible to verify, or that they represent only the pretense of sourcing atop a genuinely unsourced article. It's certainly a quality of life improvement when the entire process of verification is tap anchor link → tap external link → execute keyword search, but we can't require this, often as a matter of necessity. Folly Mox (talk) 13:21, 13 May 2023 (UTC)
 * As I discussed, not being used in an endnote reference isn't the same as being unused. But in any case, I don't think the root problem is the name of the section. The verifiability policy currently lists conditions when inline citations are required, including when content is challenged, which is why any information without inline citations can be removed (thus challenging it). If there is community consensus to require all content to have inline citations, then the policy should be modified accordingly, rather than trying to accomplish this indirectly by requiring non-inline references to be labelled as unused. isaacl (talk) 21:47, 11 May 2023 (UTC)
 * "Unused" is probably not the correct description.
 * The problem statement appears to be:
 * Encyclopedia articles are worse off with sections like Ostrich, Sailboat, Lasagna, Melon than if:
 * (a) those refs had never been added in the first place (because fewer sources listed on the page means better, more verifiable articles!), or
 * (b) they were spammed into the end of a single sentence, even though they could probably be used to support quite a lot of the content.
 * The theory of change appears to be:
 * If we make a rule against naming relevant sources outside of ref tags, then article quality will improve.
 * The underlying philosophy appears to be:
 * Immediatism, or perhaps more precisely, anti-eventualism and anti-incrementalism. It's not enough to follow WP:CITE's advice to provide enough information to identify the source. Others will improve the formatting if needed; one must get the formatting right, and the right formatting always involves little blue clicky numbers.
 * The longer I think about this, the less I can support it. If you want to convert genrefs to inline citations, then please feel free to find an article, read the listed sources, and start converting them to the popular ref tags.  But in the meantime, I think we need a little more grace for people who are doing their best, and a lot less Instruction creep.
 * BTW, gen refs are considered normal and desirable in the field of mathematics. I'll let WikiProject Mathematics know about this discussion, since they've probably thought through the problem before. WhatamIdoing (talk) 00:18, 13 May 2023 (UTC)
 * I think it goes beyond math. Students are taught to include a bibliography in a research paper, as well as footnotes for citations. isaacl (talk) 04:09, 13 May 2023 (UTC)
 * Be very careful here. Ostrich has never had general references. Those listed under the section now all went in as full references for shortened footnotes, done in the era before they were linked to the short citations. See this January 2022 version at Special:Permalink/1058117393. Shortly afterward someone renamed the "Footnotes" and "References" sections to "Citations" and "General references", misunderstanding what was going on. StarryGrandma (talk) 05:09, 13 May 2023 (UTC)
 * [A] little more grace for people who are doing their best, and a lot less instruction creep.
 * For clarity, I'm not trying to call out anyone for acting spoiled or being lazy, just remarking upon how successful the community has been at improving sourcing over the years, and I want to honour and celebrate everyone's efforts to continue that process, but I have some back-in-my-day uphill both ways Four Yorkshiremen nonsense relating to verification in actual academic research I've tastefully omitted. Folly Mox (talk) 13:33, 13 May 2023 (UTC)
 * @Folly Mox, you forgot the snow. It was always snowing when we had to walk uphill both ways – and if you tell that to kids these days, they won't believe you.    WhatamIdoing (talk) 03:31, 18 May 2023 (UTC)
 * Folly Mox (talk) 12:11, 19 May 2023 (UTC)

First, I'm not overly concerned about the outcome here, I was just trying to crystalize this discussion into a "best of both worlds" proposal. I listed one "downside" of them under the current structure, and I think I need to apologize for not explaining more thoroughly as many misunderstandings of what I meant and where I was coming from followed. Also this "downside" has been noted out by several posters here, including inadvertently by one who is in favor of the status quo which was the point of my last post. To explain the down side by an example: Lets say that there is some borderline-looking uncited text in an article which really needs to get challenged so that it will either get confirmed by an in-line cite or removed. By policy, someone can challenge/tag it and force this resolution to occur. But more typically, if the article has unused references, the reader would take that as implying that the material is supported somewhere in those references. And many would feel the "pressure" to do the huge task of confirming that it is not supported in any of those references before challenging/tagging the unsupported material. Sincerely, <b style="color: #0000cc;">North8000</b> (talk) 15:37, 13 May 2023 (UTC)


 * I don't disagree with that conclusion, and thank you for the explanation. I think the locus of misunderstanding (which could be in multiple directions) is the term "unused". My personal take on General References is that they're sources that have been used to build the article, but lack bridges between text in the article and text in the source. I've never added a General Reference, but whenever I've added a Further Reading, it's a source I've found that's germane to the topic but which I didn't use to inform any of my prose, usually because I only skimmed it. Folly Mox (talk) 16:59, 13 May 2023 (UTC)
 * I agree that "Further reading" is the place for sources that aren't used in the article. General reading sources, according to Citing sources says General references are usually listed at the end of the article in a "References" section. It says nothing about having to label them "General references", just list them at the end, and that location imples that they are "used". While  calls me an "inadvertent supporter" for my worry about removing accurate material, he did not answer the questions I put in that post. Is new material coming in with general references? It isn't in technical areas where we require inline sources and often secondary sources at that. if so, what areas are having problems and are there other ways of dealing with this? StarryGrandma (talk) 17:46, 13 May 2023 (UTC)
 * First to clarify, my reference to your post was just that it reinforces that the phenomena described in my example is occurring. Sorry that I didn't realize that your question was addressed to me, but either way I don't know the answer to it.  Sincerely, <b style="color: #0000cc;">North8000</b> (talk) 18:33, 13 May 2023 (UTC)
 * , if you revise your signature so that it links to your user page, then the reply tool "mention a user" in its toolbar will work. StarryGrandma (talk) 20:36, 13 May 2023 (UTC)
 * I don't understand, it does link to my user page. Sincerely, <b style="color: #0000cc;">North8000</b> (talk) 21:32, 13 May 2023 (UTC)
 * , in your signature "(talk)" links to your talk page. "North8000" is blue, bold, and in italic, but isn't a link. If you click on it nothing happens. There isn't a requirement to link to one's user page; linking to one's talk page is enough. I thought the reason the new reply tool's toolbar won't create a notification was the lack of a link to your user page, but on further investigation it won't link to any editor in this conversation who isn't using the standard signature, no matter how linked. So only a partially useful new feature. Sigh. StarryGrandma (talk) 00:14, 14 May 2023 (UTC)
 * Thanks for the info! <b style="color: #0000cc;">North8000</b> (talk) 14:49, 14 May 2023 (UTC)


 * This is closely related to a subject I raised a little above, at #Asking for sources for AfC drafts. The discussion is necessary. It is neither helpful nor logical that General References are still deemed okay according to policy, while a majority of AfC reviewers and new page patrollers don't like them, which means that functionally they're already deprecated in new articles. But there is a big down-side: it's basically a ban on translation from Wikipedias that do accept general referencing. Please bear in mind that the core policy is verifiability. Every fact must be verifiable, but there's no statement about how easy that must be made. There's no guarantee that the reader will have all the work done for them, no guarantee they'll be pointed at the exact location to support every word in Wikipedia, merely that everything in the article must be verifiable if someone can be bothered to pursue the references provided. Lack of page numbers linked to each sentence is often the least of the reader's problems; getting hold of the book might be the hard part. Yes, it's possible to make the argument that we shouldn't translate anything without checking the original sources anyway. In a perfect world I'd agree. But if the choice is between (1) well-translated articles where the translator has only been able to check some of the references, and otherwise has been forced to assume that the original author actually read the (obscure!) texts they cite, and (2) leaving our readers to the mercy of machine translations from whatever they are able to find with Google in a language they cannot read, I'm in favour of (1), and that means maintaining some tolerance for general references. Elemimele (talk) 21:18, 14 May 2023 (UTC)
 * It's not even true that everything in the article must be verifiable if someone can be bothered to pursue the references provided. A completely uncited article – no refs, no links, no sources, no nothing – can contain 100% verifiable content (User:WhatamIdoing/Christmas candy being just one example of this).  Compare Glossary and Glossary.
 * The challenge for AFC reviewers is that if they follow the minimum requirements, then experienced editors will come and yell at them about how they are destroying Wikipedia, allowing garbage into the mainspace, etc. But editors never yell at them for keeping a not-so-great article out of the mainspace.
 * (Wrt translation, I agree with you. I add that the amount of checking you need to do depends upon your personal familiarity with the subject and the content in the article you're translating.  You do not need to spend a lot of time checking articles that give totally expected, very basic information on a subject that you're familiar with.) WhatamIdoing (talk) 03:44, 18 May 2023 (UTC)
 * The confusion between general references and further reading in this discussion seems a good indicator that general references are suboptimal. I would agree with the comments above that in practice they are somewhat deprecated already, so we should adjust policy and guideline wording to match. I don't think that this would require creating an "Unused reference" section or similar; an easier solution, which seems in line with the confusion above, would simply be to recommend that unused but useful sources be placed in a Further reading section. CMD (talk) 16:10, 17 May 2023 (UTC)
 * I was the one who came up with the "Unused References" section idea and I think that saying that they should be put under " For further reading" (I.E. NOT under "references") is a good idea and a better idea than mine. <b style="color: #0000cc;">North8000</b> (talk) 17:16, 17 May 2023 (UTC)
 * I think that both of these are dubious claims of fact:
 * if the article has unused references, the reader would take that as implying that the material is supported somewhere in those references.
 * And many would feel the "pressure" to do the huge task of confirming that it is not supported in any of those references before challenging/tagging
 * I think the first is based on an optimistic idea of how readers use refs (the answer being 99.7% of the time, "not at all", and the remaining 0.3% rest of the time "probably not like you hope" – according to the research, material doesn't need to be cited, or even apparently trustworthy, to be useful to readers). I think the second is disproven by the number of times we get fact-tags on sentences that already have citations, or for which the citation is already provided at the end of the paragraph.  (Also, have you ever seen an editor post something like "I tried to look up these three general refs, but I couldn't find this one thing"?  I bet that it doesn't happen even in one of out of a thousand pages.) WhatamIdoing (talk) 03:36, 18 May 2023 (UTC)


 * No. General references should be retained because they are excellent if they highlight good general sources for a topic.  For example, if the subject is a person then a good general reference would be a biography for that person.
 * The issue of verifying particular facts in the article is not decisive because all citations are quite imprecise. There's no way to tell what particular fact a citation is verifying – a word, a clause, a sentence, a paragraph, a section or what.  A good reference will verify many facts in the article but the only way to show this accurately is by quoting at length and copyright considerations usually prevent this.
 * To verify in an unambiguous way would require a whole new structure – something like WikiData in which each fact is atomised and identified separately. Be careful what you wish for ...
 * Andrew🐉(talk) 07:06, 21 May 2023 (UTC)
 * Well, we have Template:Ref supports2, which can be used for unambiguous verification but requires duplicating prose content verbatim in the template call, making it unwieldy and difficult. I think only a handful of pages use this reference style (Victoria and Albert Museum Spiral is a brief article that uses it exclusively). From 2014 till last year we also had Template:Ref supports, which presumably worked similarly, but no one ever used it so it was deleted in 2022 by a consensus of two editors.It would be nice to have kind of the converse of Template:cns where the prose only has to be written once and the citation is unambiguous as to what claims it supports, but progress has stalled. What I've sometimes done to avoid a surfeit of superscripts is add a hidden comment like <!–– reference supports entire paragraph ––>, which is of course invisible to readers and thus of very limited utility. Folly Mox (talk) 08:56, 21 May 2023 (UTC)
 * Thanks for these details. I'd not come across ref supports2 before and that's because it seems to be used in only 5 articles (see Special:WhatLinksHere/Template:Ref_supports2).  This rather demonstrates that a perfectionist approach is not workable.
 * And even if a citation is clear and unambiguous, there's still no guarantee that the cited source is correct. At some point you have to trust what is being said.  See What the Tortoise Said to Achilles... Andrew🐉(talk) 20:49, 21 May 2023 (UTC)


 * Correct me if I'm wrong, but general references seem to me to be the same thing as further reading. That is, a list of promising books/articles/etc. that a content creator can read and use to expand the article with inline citations at a later date. Perhaps all general references sections should be converted to further reading. Good idea? Bad idea? Thoughts welcome. (Please ping on reply) – Novem Linguae (talk) 05:18, 25 May 2023 (UTC)
 * I believe the original intent of the two section headings was that "General references" were sources that had been used in writing the article without providing in-line citations, while "Further reading" was for sources that a reader could consult for more information about the subject, but which had not used in developing the article. I think that distinction was not very clear to begin with, and has become more blurred in actual usage. I also support (as stated above) moving "General references" to "Further reading". Donald Albury 16:06, 25 May 2023 (UTC)

Template:Bottom of section
Do we have something like Template:Skip to bottom that is usable for just a section jump? Find myself scrolling like mad in many talks that are simply huge. Would love to jump to the bottom of a talk section with one click on huge talk sections. Template:Bottom of section? As of now I simply click on the next talk header to do this. Moxy - 15:05, 21 May 2023 (UTC)


 * I'm finding that the new Vector 2022's "sticky header" can be useful for this purpose. I keep the sidebar, tool menu, and table of contents all collapsed, but it appears in the sticky header, so it can be opened if I want to skip ahead. Whatamidoing (WMF) (talk) 23:59, 22 May 2023 (UTC)
 * . Like the new skin better for looks.....but with my physical disabilities it's a much harder skin to use for navigation (toc WAY to small...thus hard to get cursor over section title.) Moxy -Maple Leaf (Pantone).svg 03:18, 26 May 2023 (UTC)

Lists of company products/services
I'm thinking specifically of e.g. List of McDonald's products, the airline-destination lists and so-forth. The issue here is a straight application of WP:NOTCATALOGUE would probably see all of these deleted. However, some lists do rise to the level where they are doing more than merely listing exhaustively all of the products/services of a company regardless of notability and also are helpful to our readers (e.g., List of Atari 2600 games).

My suggested frame-work for these is:
 * 1) WP:CORP applies to these list-articles, particularly WP:AUD, since they are entirely about the operations of a commercial enterprise.
 * 2) The list should not aim to be exhaustive or immediately up to date. Only notable items (e.g., those with a corresponding article or which an article could be written about) should be listed. Wikipedia is not a catalogue/directory.
 * 3) Where NONE of the items listed is notable, the list fails WP:CORP. The idea here is to prevent run-of-the-mill lists of stores, restaurants, hotels, routes, etc.

Thoughts? FOARP (talk) 09:37, 15 May 2023 (UTC)


 * Your third point says "Common selection criteria #2 is not good enough for me". I think you should give up on that.
 * More generally, I think you should consider writing an essay using the Five whys method, explaining why you believe that articles about commercial subjects (=one of our most popular subjects for readers) are a problem. WhatamIdoing (talk) 03:49, 18 May 2023 (UTC)


 * The McDonald's article is what happens when an article or list isn't covered by an active WikiProject. It's not a failure of policy, it's simple neglect. No one looks at the article and thinks it's good. The only debate is whether there are any improvable "seeds" that make it worth keeping and waiting until someone volunteers their time to rewrite it around academic sources and trim the junk.
 * Your diagnosis and solutions are wrong. #1 WP:NCORP already applies; you may be annoyed at how others interpret it, but tweaking it won't help. #2 contradicts WP:LSC. Consensus at the article or WikiProject level determines inclusion criteria in lists, not central fiat. #3 is already the case.
 * Anyway, none of these criteria apply to your specific McDonald's example, since their products get discussed "as a group" (WP:NLIST) in plenty of academic sources (whether it's menu items meant to appeal to ethnic minorities, items meant for developing markets, or items meant to fight its "junk food" public image). But that requires people to care to work on the article. Not tweaks to notability criteria. DFlhb (talk) 00:14, 20 May 2023 (UTC)
 * Fair enough, however, in my opinion, those products should be remain here. I do not agree with you de to the fact that the products listed on an article of a company are still relevant to the general public and not the only particular group. Wikipedia is an global encyclopedia for all ages and groups, so there is no way to exclude the select amount of products from a website. Sure thing that it may not be a directory, however in this case, it does not matter to me. Although that notability applies to any product on the Internet, obscurity does not mean non-notable. Netherless than that, we have the ability to find those sources on the Internet, especially Google that contains most of these websites and news sources, and I do not find anything incorrect about it. So, I would vote remain on the lists of company products. / EnjoyBrowser557 (userpage) (talk) (contributions) 04:56, 26 May 2023 (UTC)

Overturning Arbcom judgements
''I've moved this discussion from a sandbox designed to discuss ways to improve the amendment of ARBPOL process. This is a related, but distinct, discussion that really deserves its own time and attention and so I'm moving it here. The options were generated by .'' Barkeep49 (talk) 16:18, 26 May 2023 (UTC)


 * Option 1


 * Option 2

It feels like this method should also be made a substitute for Jimbo, possibly with a simpler requirement. Adam Cuerden (talk)Has about 8.4% of all FPs. 16:28, 22 May 2023 (UTC)
 * I feel like this is veering into a new policy area beyond amending ARBPOL itself. It clearly stems from the current amendment proposal, given many people think there needs to be a community way to overturn it and some suggesting that it could be done through the amendment process. But it still remains a seperate idea and the language for this would likely be its own section, or part of 2.9 "Appeal of decisions" not "Ratification and amendment" which is what this page's focus is on. Best, Barkeep49 (talk) 16:29, 22 May 2023 (UTC)
 * At the least, it feels a reasonable thing to attach this to, as they at least cover a similar subject. Mind if it gets workshopped alongside the rest of this? Presuming this is getting attached to another proposal, I presume people will be able to vote seperately to the two types of amendment anyway.
 * I'd like to hope this never triggers, but it's worth having a clearly-defined check, and it feels in the spirit of the process. Adam Cuerden (talk)Has about 8.4% of all FPs. 16:33, 22 May 2023 (UTC)
 * Since the amendment process could be used to effectively reverse an ArbCom judgment, or at least elect a new ArbCom pledged to undo that decision, what need a separate provision? But I see the number of people who think something more specific is needed before giving Jimbo his walking papers.Wehwalt (talk) 17:14, 22 May 2023 (UTC)
 * Aye, that's my thought: It's a clarification of something that already theoretically exists. Adam Cuerden (talk)Has about 8.4% of all FPs. 19:04, 22 May 2023 (UTC)
 * I agree it exists. I think putting it into the policy makes it more likely to be used, which from my personal point of view is a bad thing. If it's used, even unsuccessfully past the petition stage, that harms one of the pieces of value I see ArbCom providing: a place of last resort that makes tough calls. If the community felt a need to exercise the power it already has, whether after this amendment or not, it would seriously diminish my desire to serve to the point I would consider resigning mid-term. There's a lot of things being unpleasant about being an arb, but, for me, I can justify it by knowing that I'm providing service to the community. If the community starts questioning that service it would radically change my answer. Best, Barkeep49 (talk) 19:10, 22 May 2023 (UTC)
 * I was thinking the same thing; while it is necessary to have this power, we don't want to encourage its use by making it an explicit option. BilledMammal (talk) 19:17, 22 May 2023 (UTC)
 * Let's be honest here: the number of people who know this procedure exists is vanishingly small. Having it in policy just means that, should things get bad enough that it should trigger, ad hoc procedures aren't invented. An amendment passing is a very high bar, it's unlikely to happen outwith a truly egregious error. An ad hoc procedure probably won't have half the checks. Adam Cuerden (talk)Has about 8.4% of all FPs. 06:44, 24 May 2023 (UTC)
 * To avoid conflating the two proposals, personally I would prefer having the discussion on a separate page. isaacl (talk) 17:19, 22 May 2023 (UTC)

Do we really want a situation where the entire community is being asked to vote on something like someone's topic-ban? Newyorkbrad (talk) 13:44, 23 May 2023 (UTC)
 * Considering this in the context of the status quo - where the community can, but aren't explicitly told they can - I don't imagine such a proposal will even get past the petition stage. There may be a small number of editors sufficiently invested in that editor or dispute, but as a whole the community will endorse arbcom even if they disagree with the topic ban.
 * There are circumstances where I can imagine this would be used, but individual sanctions against editors are not one of them - at least so long as arbcom is careful not to open the door to their decisions being overturned by making a decision that is overturned. BilledMammal (talk) 13:48, 23 May 2023 (UTC)
 * We do that all the time at AN and ANI. Most of the topic bans, and most of the time topic bans are lifted, are via community discussions.  -- Jayron <b style="color:#090">32</b> 14:00, 23 May 2023 (UTC)
 * This is one reason why it might be valuable to write something directly into ARBPOL: To limit its application. If the wrong is severe enough for the community to be voting on it, then it should be severe enough to dissolve the entire committee. Any lesser wrong should use the existing channels such as WP:ARCA and individual communication to attempt to change the result. (+- the systemic review of the U4C, which I think must continue to be considered.) Izno (talk) 15:47, 23 May 2023 (UTC)
 * I think a community "vote of no confidence" triggering an immediate election of all arbs is more reasonable proposal than ones that allow for a specific decision to be overturned. It goes a long way towards addressing my concerns above. Best, Barkeep49 (talk) 16:10, 23 May 2023 (UTC)
 * I'd wondered whether this should be paired with automatically triggering a case review for the incoming arbs post special-election (that's a note, that this should utilise the emergency election rules), but I guess that would be needless - if we've reached such a drastic action, we can assume that the incoming new arbs will act appropriately. Nosebagbear (talk) 00:16, 24 May 2023 (UTC)
 * We don't even know that it would be a case that needs reviewing. For instance, maybe ArbCom has passed some new procedure the community finds unacceptable. This is all hypothetical but I could also see a situation where a more elite crowd (the kind that votes in ARBPOL amendments) is furious with arbcom but a slightly less elite crowd (the kind who vote in ACE) isn't. Best, Barkeep49 (talk) 01:23, 24 May 2023 (UTC)


 * Proposal a would be pointless - we could already do that just with a blank-form amendment. I wouldn't make it easier per proposal b - bluntly, if we are pursuing this route then arbcom has done something that seriously enraged the community. I would view inactivity that annoys the community as a much lesser thing - we would probably just issue a CBAN or such in similar circumstances. Modern arbcom has less opportunity for a gradual demonstration of issues given the smaller number of cases - it's possible, but the next election would probably come round first. A single catastrophic incident is more likely. The same applies with the U4C - any cases bought for systemic failure are likely to be by a small number, as if the concerns were felt by a larger contingent of the community then the issues could be resolved by more direct means. Nosebagbear (talk) 16:03, 23 May 2023 (UTC)
 * As I said above, I'd rather have a procedure in place now, while all is calm, than some ad hoc thing invented by the angry mob. There's maybe one case in Arbcom's history that would have had any chance of this going through, y'know, "This unique confluence of irregularities resulted in a fundamentally flawed process" -ArbCom. But that's early Wikipedia. Adam Cuerden (talk)Has about 8.4% of all FPs. 06:59, 24 May 2023 (UTC)
 * WP:FRAM is not so long ago, and that's the kind of case I think about with "ArbCom was wrong too, enough to dissolve it". Or if the case had come to ArbCom first rather than T&S? I do not know. Izno (talk) 17:20, 24 May 2023 (UTC)
 * So I guess it's possible @Izno - there was a major discussion at the time on whether ARBCOM was in breach of ARBPOL for taking evidence that the accused could not see and respond to. I could imagine a comparable case with less good mitigating factors launching a reaction. Nosebagbear (talk) 22:36, 26 May 2023 (UTC)
 * I'm not sure I agree with overturning ArbCom judgements. Not everything should be subject to a popular vote, it discourages difficult decisions from being made. Now, I don't really expect an ArbCom decision that has a majority wishing to undo it was a good ArbCom decision, but if it's something like 51% overturn / 49% retain, I don't think it should be overturned. ArbCom being a body of last resort is going to have to deal with difficult and intractable behavioural problems. If the solution were obvious or popular, ANI could've enacted it.Aside from that, the option to overturn an ArbCom judgement doesn't fully make sense. Overturn what? The entire final decision? (and replace with what? leaving the issue unresolved?) Or a particular solution? (would the decision still be fair, even-handed, and still make sense, if only a particular remedy is overturned?) ProcrastinatingReader (talk) 20:17, 24 May 2023 (UTC)
 * The difficulty that PR points out would lead me to suggest that perhaps ArbCom judgments should not be able to be overruled directly by the community. They would, however, have the power to kick out the current ArbCom and elect a new one, which can consider what needs to be done about the questioned ruling. Wehwalt (talk) 21:14, 24 May 2023 (UTC)
 * Considering how few candidates for ArbCom have presented themselves in recent years, would it be wise to throw the lot out and elect an all new committee? You would want at least 20, preferably more, good candidates to fill the 15 seats. Donald Albury 21:55, 24 May 2023 (UTC)
 * I think the idea is that all terms would end. Arbs would be free to run in the new election. Wehwalt (talk) 22:01, 24 May 2023 (UTC)
 * And what would be the chances in a new election of the arbs who were in the majority on the decision that led in a vote to kick them out? In the last three elections, there have been 7 or 8 seats open, with 3 or 4 current arbs running and 8 or 9 candidates who were not currently on the committee. Best scenario, the community reacted to a decision supported by a majority of 5 or 6, because vacancies, inactive status or recusals from the case reduced the number of voting arbs. The arbs who were in the majority on that case presumably would not be re-elected, if they chose to run. If most of the other sitting arbs did choose to run, and 8 or 9 candidates who were not on the committee that was kicked out ran, that would give you little more than 15 candidates for 15 seats. It is possible that not all would get at least 60% support, leaving a committee with vacant seats. If fewer members of the dissolved committee choose to run, the bigger the problem. There is the possibility that a larger number of users than usual may offer themselves as candidates, but I wonder how many of them would reach 60% support. I suspect that the pool of possible arbs that the community trusts and that is not very deep. Donald Albury 15:46, 25 May 2023 (UTC)
 * I don't disagree with any of that. If the community is in that situation, it faces unpleasant alternatives. We can't solve that right now. All we can do is see if there are tools we should give it that might help resolve the situation. Or quite possibly, decide there aren't. Wehwalt (talk) 15:53, 25 May 2023 (UTC)
 * 50% support is the requirement to be elected, not 60%. Izno (talk) 17:55, 25 May 2023 (UTC)
 * Oops! Not that it makes much difference to my argument. Donald Albury 19:21, 25 May 2023 (UTC)
 * I'm not sure if you're putting forth this issue as an argument for not allowing the community to ever end the current terms of all arbitrators, or as an argument for picking-and-choosing specific arbitrators to expel? In any case, it would be up to the community to agree upon whether it wanted to call for a special election for all seats, some seats, or some other approach that might be more suitable for the specific circumstances. isaacl (talk) 02:00, 26 May 2023 (UTC)
 * Failure of this proposal will not prevent the community from taking any action in the future. A recall of the ArbCom as a body would be disruptive. The existing process for ArbCom eletions would require at least two months before a new ArbCom could be seated. Would the existing committee continue to function until a new one was elected and seated? If not, ban appeals that can be made only to ArbCom would be piling up, existing conduct cases would be put on hold, and new cases could not be opened. If the existing committee is allowed to function until the new committee is seated, could the new committee overturn decisions made by the old committee after the recall? Depending on how many previous Arbs are elected, the new committee could take a while to get up to speed.
 * I think the whole question of what to do if a sitting ArbCom looses the trust of the English WP community needs to be more carefully thought out. We want to avoid a situation where the WMF might feel that they need to step in to restore order to the English WP. An out-of-control ArbCom could provoke that. The absence of a functioning ArbCom could also provoke that. I don't know what the odds are of a majority of Arbs losing the trust of the community, but I think that the odds of lacking a functional ArbCom for some period after a recall are higher. Donald Albury 16:04, 26 May 2023 (UTC)
 * Sure, at present there are no fixed paths for handling this circumstance. If it does occur, the community will discuss what option is most suitable for the specific situation. That could be expanding the committee and electing more members, limiting the committee's scope, holding a special election to replace all current members, or something else. isaacl (talk) 16:25, 26 May 2023 (UTC)
 * I agree. Let us not constrain the future community on how to deal with a vague (and, hopefully, unlikely) contingency. Any formal procedure developed ahead-of-time would likely not be much quicker than holding an RfC for an ad-hoc solution, and might turn out to be a poor fit for the problem. Donald Albury 17:50, 26 May 2023 (UTC)
 * Worth noting that since this process would use the emergency process, I would guess something more like 5 weeks than 2 months for ARBCOM. Which still isn't great, but is much better. I also concur with the reasoning that a certain level of negative side effects is unavoidable. In fact, it might actually be possible. We want this for case outcomes that the community views as simply unacceptable, not merely wrong. Wrong decisions are for the regular elections to resolve. Nosebagbear (talk) 23:11, 26 May 2023 (UTC)
 * Requests_for_comment/Arbitration_Committee_Elections/ACERFC_decisions_to_date has the rules of a special election which would be a matter of weeks, not months. Best, Barkeep49 (talk) 01:04, 27 May 2023 (UTC)
 * I think it would be simpler for the community to hold an election for all seats at once than to try to reach consensus on a subset of arbitrators to keep in place. isaacl (talk) 22:09, 24 May 2023 (UTC)
 * I agree with this. For me the simplicity of the solution is one of its big virtues. And I think it provides a chance for Arbs who supported the decision to make their case to the broader community (and arbs who didn't to make that case too). And truthfully if we were in this situation I would expect a large field, like we had in 2021 following FRAM, rather than the more meager fields of recent years. Barkeep49 (talk) 22:21, 24 May 2023 (UTC)

IMO it's hard to imagine any process that is more representative of the community on Arbcom matters than Arbcom itself. Also all of the mistakes that Arbcom makes are actions regarding individual editors and it's hard to imagine a process to jump in on those. Here's a way to kill three birds with one stone. Bird #2 is that someday en Wiki needs to have a constitution. Bird #3 is that we don't want this to fall by default to WMF. So let's just say no action now and if it is needed sometime in the future EN Wiki will create a "constitution" level process via a suitable method (requiring an overwhelming consensus or vote) to deal with it. <b style="color: #0000cc;">North8000</b> (talk) 19:41, 26 May 2023 (UTC)
 * Any action that has managed to get a majority of ARBCOM to take an action is not likely to be one that the Community is universally opposed to. As such, I think a simple majority is an unwise threshold, as an edge case is a significant possibility. I would suggest at least 60% of votes must be in favour of overturning. No 51% majority should be overturning ARBCOM, given we'd never acccept such a majority for overturning even a regular block. Nosebagbear (talk) 22:38, 26 May 2023 (UTC)

Semi-protected edit requests
Are semi-protected edit requests necessary?

These requests use a template that alerts editors who do not follow the article. By definition they are only made by IPs and new editors.

In my experience, they are almost always made without prior discussion. Experienced editors then close the request and discuss the proposed change.

It seems that if an IP or new editor has the technical ability to use a template, they are able to request outside help without a template. None of them seem to set up a discussion, find that no one has answered it, and make an edit request. TFD (talk) 12:33, 24 May 2023 (UTC)


 * About 10-15% of them are productive copy-editing, obvious BLP issues, or other requests that can and should be implemented without any discussion. The template itself is populated when an editor who isn't confirmed attempts to edit a semi-protected page. Many of them obviously don't know how to use a template because they end up breaking it by not following the hidden comments.
 * The main reason to use the template rather than just creating a discussion is it brings in an edit request patroller to assess and possibly implement the request. I think the edit requests are a necessary part of how we handle page protection. ScottishFinnishRadish (talk) 12:41, 24 May 2023 (UTC)
 * Articles that become semi-protected generally have page viewers who can respond to edit requests. OTOH, if an IP or new editor has the expertise to use a template, they certainly have the ability to post their edit request directly to the noticeboard.
 * By your own numbers, 85% to 90% of semi-protected edit requests are not legitimate.
 * I don't understand anyway how so many inexperienced editors are able to use templates. TFD (talk) 14:25, 28 May 2023 (UTC)
 * The workflow for editing a protected page populates a edit request template. Try editing a semi'd page in incognito mode. ScottishFinnishRadish (talk) 15:16, 28 May 2023 (UTC)

Why don't we have warning banners about scams?
One of the facets of WP:ARC is that some poor guy got scammed out of a large amount of money (I've seen $15k and $20k mentioned) by somebody promising to write an article for them. It's not the first time, but wouldn't it be nice if we could make it the last? Let's put a warning banner on every page: "If somebody is offering to write an article for money, it's probably a scam. See WP:PAID for more information". -- RoySmith (talk) 00:25, 13 April 2023 (UTC)
 * The key challenge is that the community would have to accept a prominent banner forever, including on small screens where space is limited. Given the number of possible scams, it would be tricky coming up with a concise message that would still have some effectiveness. Banner blindness issues would also be exacerbated (and I imagine WikiProject Medicine would renew its call for a warning banner). But if the problem is significant, it may be worth considering. On a side note, I think the banner should link to a page tailored for it, rather than the paid-contribution disclosure page. isaacl (talk) 03:20, 13 April 2023 (UTC)
 * Those are reasonable points, but let's not get bogged down in the details. The gist is that we should be doing more to alert users (especially vulnerable new users) to the risks.  Maybe one of those messages that keep showing until you click the "dismiss" link?  Or make it part of the welcome message that gets dropped on new user's talk pages?  Or an email to new users?  There's lots of technologies to help get the message out.  And, yes, the details of the message could be fine-tuned more than WP:PAID.
 * Not long ago, I needed help with managing a page I have on Facebook. I (foolishly) decided to try joining /r/facebook/ on reddit.  I immediately got a message from a bot warning me that the group was rife with scammers.  And sure enough, by the end of the day I had gotten several PMs from people offering to help me solve my problem in exchange for money.  I've been around the block a few times, so I'm pretty good at recognizing scams, but having been put on alert primed me to be particularly suspicious.
 * Some of these scams are quite sophisticated. A few years ago, I got an email from somebody purporting to be a high-level WMF employee who had recently left WMF, attempting to enlist my help with a paid editing project.  It was well-targeted to my past activities and editing interests and slick enough that I spent quite a bit of time trying to figure out if it was legitimate or not.  It's not hard to see how somebody (even somebody who's been around the block a few times) could have been sucked in. -- RoySmith (talk) 15:05, 13 April 2023 (UTC)
 * Another idea; there are several mainstream (at least in the modern sense) media outlets which cover wikipedia. HalfAsInteresting just did an amusing (but reasonably accurate) piece on how arbcom works.  Slate has published a number of well-researched articles examining wikipedia topics.  I'm sure there's others.  Perhaps they could be encouraged to write about wiki scams.  The more it's talked about, the more potential marks will be educated about the problem. -- RoySmith (talk) 15:12, 13 April 2023 (UTC)
 * The detail on whether or not the warning appears on every page is an important one, though. A one-time welcome message would be less intrusive, but potentially less effective. Maybe a one-time message and some form of collapsed message on each page? Not sure what would be the best way to present the collapsed message on a small screen, though, and that's how a lot of readers experience Wikipedia. I don't think messaging new users will do much to reach the extremely broad group of potential victims. (On a side note, I feel the HalfAsIntereseting video is reasonably accurate on describing dispute resolution, with the key omission that it failed to describe how the arbitration committee doesn't directly rule on content issues.) isaacl (talk) 15:35, 13 April 2023 (UTC)
 * I'd hate to see it on every article all the time, too. Maybe something that could be seen by IPs/new accounts, maybe a click-through page that shows up randomly when someone opens a Wikipedia article, and that registered accounts could turn off? Agreed that it should link to something that very briefly explained the scams. Valereee (talk) 14:54, 13 April 2023 (UTC)
 * Are there any estimates for how large a problem this scamming is? We've got hundreds of millions of readers; we don't want to overreact given any action will negatively impact their reading experience.
 * Depending on the scale of the problem, another option may be to run the banners for a week as an education campaign. BilledMammal (talk) 15:23, 13 April 2023 (UTC)
 * @BilledMammal, for an idea of how much this is attempted, see WP:List of paid editing companies. How often it's successful is a different question, of course. A lot of these people are really bad at it. Valereee (talk) 16:15, 13 April 2023 (UTC)
 * I think that's a different issue, although it is related; some paid editing companies are just scams but others do try to provide the service that is being paid for. BilledMammal (talk) 16:28, 13 April 2023 (UTC)
 * Most UPE companies are deceptive to customers (we are Verified Editors, we have Wikipedia Moderators in our team, we strictly follow Wikipedia Rules, etc). Whether they cross the line to be considered criminal is a different matter. MarioGom (talk) 17:29, 13 April 2023 (UTC)
 * Roughly once a month someone pops up on the help desk asking where the article they paid for is. It's a pretty common scam. I don't think it being shown to people when they register is ideal; I think most of the victims never make an account - why would they?  They've paid someone else to do that. ~  ONUnicorn (Talk&#124;Contribs) problem solving 16:34, 13 April 2023 (UTC)


 * No one reads banners or warnings anyways. The only way people learn anything is when natural, negative consequences happen to them.  If that natural, negative consequence is "they lose money to someone who scammed them", then the lesson they will learn is "don't get taken in by scams".  They don't learn that lesson because we have a banner they don't bother to read.  They only learn it because they actually experience being screwed by the scammer.  In summary: there's no need to bother, it's not our responsibility, and if your goal is to educate, there's no greater education than losing a bunch of money to someone who scammed you out of it.  -- Jayron <b style="color:#090">32</b> 15:31, 13 April 2023 (UTC)


 * We could put something about scams in the disclaimers. Gråbergs Gråa Sång (talk) 16:28, 13 April 2023 (UTC)
 * There's a related discussion at WT:COI.
 * I agree in part with editors who point out that the most likely victims of scammers are unlikely to benefit from any "education" from us, and I also agree that making banners too intrusive would mostly just be annoying. But I also think that there is an unmet need to make information about scams easier to discover than it currently is – if only for editors who want to learn more about how to combat it. I also think it's a bit harsh to take pleasure in how someone losing money will learn a lesson. Short of warning banners, I think we should find multiple places to link to things like WP:PAIDLIST and WP:SCAM. It might be a good idea to look at the help pages we have for new editors, and find ways to incorporate more information about the need to beware of scams into those. --Tryptofish (talk) 16:52, 13 April 2023 (UTC)
 * @RoySmith Putting a warning banner on every page seems excessive to me, and I don't think it would get community support. Does Kobresia sibirica ned a banner on it telling readers about paid editing? I would argue no.
 * I think a refined version of your proposal would definitely have legs though. Rather than putting a banner on every page we could put notices and banners in specific targeted places: those that are likely to either be abused by paid editing companies as part of a scam, or those where people in the process of being scammed are likely to go for help.
 * Here's a couple of ideas off the top of my head:
 * These scams often focus on impersonating admins, checkusers, oversighters, members of the arbitration committee etc. If these people put a standard boilerplate disclaimer at the top of their user and talk pages saying "If someone claiming to be me has offered to perform edits or actions in exchange for payment you are being scammed" that would make it much more difficult for these scams to occur. If these notices were present the scam that resulted in this current mess would have fallen apart as soon as the scammer sent the victim to bradv's user page.
 * One very common scam involves looking through AFC submissions for biographies or pages on companies that have been declined/rejected then messaging the subject asking for payment to publish it. AfC submission, AfC reject and AfC decline could all have prominent notices added warning about this kind of scam.
 * AFD would be another good place to put warnings. There's a lot of scams based around nominating articles for deletion then extorting protection money to prevent this (by having a bunch of socks flood the discussion with keep votes). A message that anyone asking for payment in regards to page deletion is a scammer could be useful.
 * I'm sure there's other places we could add warnings which would impede the scammers but wouldn't impact most of the project. 192.76.8.84 (talk) 17:04, 13 April 2023 (UTC)
 * I also think that a site-wide warning is excessive, but AFC and AFD disclaimers would be nice. There's some common scams and extortion operations that focus in these areas, and the disclaimers can be added to banners that are already in these pages. MarioGom (talk) 17:28, 13 April 2023 (UTC)
 * I'd oppose a banner, but places like About could carry visible warnings about payment scams. —Kusma (talk) 19:16, 14 April 2023 (UTC)
 * Another place for such a warning might be Help:Introduction or one of its subpages. --Tryptofish (talk) 20:09, 15 April 2023 (UTC)

All of the above is well intentioned but is likely to be ineffectual. What's the chance that a contentious group of Wikipedians will agree to put this into effect? Well, there is one very simple thing that every Wikipedian can put into effect immediately and will have some results depending on how many editors post this warning. All you need to do is post the following at the top your user or user talk pages:

Does it work? I've had this warning at the top of my talk page for 6 years (in a slightly different version). It's the only such warning that I know of. About 2,000 visitors see the page every month. Yes, there must be some other links somewhere, but if we have hundreds of links to WP:SCAM, we'll likely have many times more visitors to that page. See Page Views. Smallbones( smalltalk ) 19:14, 13 April 2023 (UTC)


 * I've added it to my page, though I changed the language because I think the average reader probably doesn't know what AfC/an AfC participant is. Good idea! Valereee (talk) 19:22, 13 April 2023 (UTC)
 * As I said above, IMO something to this effect should be included in the AfC submission, AfC reject and AfC decline templates (maybe not quite as big, and maybe including a bit more information on what the scam is) that way everybody using AFC should see it. 192.76.8.84 (talk) 19:26, 13 April 2023 (UTC)
 * Speaking as the person who will probably be getting the emails to paid-en-wp, sending people who have been scammed there rarely helps. Between the inexperience of the people who were scammed and the general untrustworthiness of the scammers, there's rarely anything actionable. GeneralNotability (talk) 20:45, 13 April 2023 (UTC)
 * Speaking as a person who has tried to do something about scammers operating on Wikipedia, I do think there is at least some minimal benefit from directing people to WP:SCAM. It explains to the victims what happened to them - maybe, at least, they can avoid the same thing happening again. It also warns others not to fall into the same trap. Nevertheless, it must be totally unsatisfying to the victims that there is nothing that we can do, nothing that we can recommend. This scam has been going on for at least 10 years, IIRC. We have some responsibility to try to come up with some way to combat it. Ultimately the major blame is not with the scammees or even with the scammers. It falls on us for offering such an attractive field with such easy access for scammers, and not doing anything about it for 10 years. We need to take responsibility for the situation we have created, and at least try to do something about it.
 * It should help to describe how I came to write WP:SCAM. I saw an article or letter to the editor in some small UK paper, describing how he had been scammed by Wikipedia. The article was only on Google News for 1 day, so it is fortunate that I found his email and responded the same day. I recognized something in his description that reminded me of something in the Orange Moody scandal. I told him that it wasn't Wikipedia scamming him, rather it was probably somebody that we know about and I could probably direct him to somebody here who could help, in at least some small way. I still haven't found that person. Can anybody tell me where to look? His response was more disturbing than I had thought it would be. He was physically disabled, but had accomplished quite a lot given his situation. I didn't think that he was notable enough though for an article. I surmised that his income was mostly government support, and that the $5,000 or so that he paid the scammer (this is all from memory) would be sorely missed. What to do? I think I first discussed this at talk:Paid editing disclosure and it was basically pooh-poohed. After asking around a bit on-Wiki without much sucess, I sent a general inquiry to the WMF. Over time I was able to focus a bit on a specific WMF department - but they didn't have a solution or even a real suggestion. Things began to move a bit after I researched the Orange Moody records. One newspaper (The Telegraph?) had a strange section in it describing how the victims were convinced to part with their money. There was a 26 word series there that exactly matched a 26 word series in an email the scammer had sent to the victim. I think I emailed an arb or two about that time. No real solution was offered but somebody suggested sending the email to arbcom (with an official email address). At the same time I searched for the 26 word series elsewhere on the internet, and found something, a small German programming coop-type organization. (Jtydog got involved about this time on the PAID talk page so things get confusing) Jt. ydog and the other coop-ers explained to the main guy there what had happened to "their" money. There didn't seem to be anything that could be done for them and they were resigned to the loss. So the folks at the PAID talk page started taking it a bit more seriously, but ultimately not much got done. The arbs didn't have much to add. The big "success" was that the WMF department suggested that I should write a scam warning and post it where I thought best. Amazingly enough, it sorta worked a bit. Jtydog didn't totally ruin my write-up. Some people start reading it and editing it. The reporting email address got changed about 3 times - nobody seemed to want to deal with it, I guess. But if nobody can do anything about the reports, it's not really enough, is it? Could somebody with some sense of responsibility step up to help?
 * BTW, there is one alternative: just tell them to report the scam to the police, or to the FTC, or their State Attorney General's office, or maybe even to the Serious Fraud Office (after 10 years at $5,000-$20,000 a pop it does add up to serious money). There are downsides to that of course, but maybe after another decade of scams somebody here will make an effort to put an end to the scam.

Smallbones( smalltalk ) 01:43, 14 April 2023 (UTC)

(EC)
 * Much the same can be said about Amazon. And they seem to at least be trying to do something about it on the education front. Just today I got an email today with a bunch of anti-spam suggestions ("Be careful installing apps or software", "Never pay over the phone", etc. And a link to a page where you can learn more. It may not be much (and most of the advice is fairly generic), but it's something. Surely we can do as little as they do. -- RoySmith (talk) 00:53, 14 April 2023 (UTC)
 * A project page with concise and clear guidance on avoiding scams would certainly be useful. For example, it can be an additional resource to link to from WP:VRT responses about scams, which are pretty frequent, as well as linking from AFD or AFC banners. MarioGom (talk) 10:35, 14 April 2023 (UTC)
 * Articles for creation/Scam warning is a good start. But it could be moved to Scam warning and expand it to make it clear that this does not apply to just AFC. MarioGom (talk) 10:39, 14 April 2023 (UTC)
 * Am I alone in that my first reaction to this discussion was to think that anyone who is so vain as to pay thousands of dollars/pounds/euros for an article about themself or their business deserves to be scammed? We can't legislate against stupidity. Phil Bridger (talk) 18:18, 14 April 2023 (UTC)
 * @Phil Bridger I doubt that you are alone, but that doesn't make it right. Lots of people pay money to promote their businesses on social media, etc.  On some platforms, that's totally acceptable and encouraged by the platform owner.  We're not one of those platforms, but a lot of people don't understand that.  If I approached a businessperson with an offer to build them a website on Wix, and drive traffic to it with additional presences on Facebook, Twitter, and Wikipedia for money, it would be 3/4 legitimate.  Our job is to educate people how we're different from the other 3/4.
 * Nobody deserves to be scammed. That's just blaming the victim.  But, it's not just the people who pay for articles that never appear (or get sucked into AfD protection rackets) that are being scammed.  You and I are getting scammed too.  We're volunteering our time to build something only to have people use what we've built for their own nefarious purposes.  We've been taken for our hard work just as certainly as the mark has been taken for their money. -- RoySmith (talk) 20:34, 15 April 2023 (UTC)
 * The difference is that Wikipedia is an encyclopedia. I have no sympathy for anyone so stupid as to think that an encyclopedia you can pay to be in would be any good. --User:Khajidha (talk) (contributions) 12:00, 18 April 2023 (UTC)
 * This is not a good faith comment at all. Cessaune   [ talk ]   16:06, 18 April 2023 (UTC)

If having a warning message on user pages is thought to be helpful, then perhaps we should request a software change to allow user page notices, and then the warning can be placed there for all user pages. isaacl (talk) 17:05, 16 April 2023 (UTC)
 * User page messages could be helpful and would raise awareness of the issue, but I wonder how many of the victims have a user page. I suspect that many people who would consider an offer to write an article for them may not edit themselves, and so would be unlikely to see any warnings about it that do not appear in mainspace.EdwardUK (talk) 17:52, 16 April 2023 (UTC)
 * The goal for a user page warning is so if a scammer claims to have a specific editor working for them, should a victim look that user up, they would see the warning. I agree this probably doesn't help the vast majority of victims. As adding the warning was suggested, though, I think if it's really going to be done then the software should do it by default, rather than the community relying on users voluntarily adding the warning. isaacl (talk) 21:28, 16 April 2023
 * Perhaps a data point: in 2014 someone was putting up profiles on some freelancing site claiming to be me and offering paid editing services, so I put a notice on my user page warning about it and inviting anyone who heard from the scammer to contact me with details. I left it up for six months and never got an email. That said, I only ever heard of it thanks to an off-wiki attempt at stirring up scandal about me blatantly engaging in paid editing, so the profile may well have been created to try to frame me for breaking enwp policy rather than to actually try to scam anyone... GorillaWarfare (she/her • talk) 23:02, 16 April 2023 (UTC)

Short of plastering the Main page with "Don't Let This Happen To You!" banners, I don't believe we can effectively help would-be BLP subjects who are victims of take-the-money-and-run scams. However, in cases where actual, paid-for BLP articles are created (if only in draft space), I believe most of them will include an infobox or EL link to the subject's webpage. Might it be possible to develop a bot that screens new articles for such a webpage, and then somehow/someway contacts the subject through that webpage (email I assume) with a paid editing scam warning? Perhaps that would give the victim sufficient time to stop payment on their check, so to speak. JoJo Anthrax (talk) 14:51, 18 April 2023 (UTC)

Wikipedia article on paid editing on Wikipedia
At the moment, we don't appear to have an article on the topic - if we did have one it would end up near the top of any search on related topics and would likely be one of the first thing targets read if they attempt to find out more before sending money.

At the moment, I think an article solely on scam paid editing might not pass WP:N as all the sources appear to be in relation to the 2015 event (BBC, Wired, the Guardian, Forbes), but a broader article would meet notability guidelines, and I think including information showing that many of these companies are scammers might dissuade some people wishing to engage the services of those who aren't scammers.

Are there any issues with this idea? If not, I'll draft something when I have time. BilledMammal (talk) 15:50, 13 April 2023 (UTC)


 * @BilledMammal we have Conflict-of-interest editing on Wikipedia 163.1.15.238 (talk) 15:56, 13 April 2023 (UTC)


 * Thank you. I think the article needs some work, as it appears to be closer to a list of paid editing incidents than an article, and it lacks detail on how paid editing can be a scam, but it is where we would hope readers go. However, googling various search terms it isn't, at least in my results:
 * Paid editing on wikipedia turns up a series of ads, and then links to various internal pages; Paid editing (guideline), Paid-contribution disclosure, Paid editing (essay), Paid editing policy proposal, and Wikipedia talk:List of paid editing companies. Our article isn't in the top results.
 * Buy a wikipedia article turns up the same ads, and then the top results are for various companies selling article creation services; the only Wikipedia results are Help:Buying Wikipedia and Buying Wikipedia articles in print or another form, although a WMF news article shows up; You don't need to pay for Wikipedia articles.
 * Various other searches I tried along these lines turned up similar results. Problematically, the first results for Make a wikipedia article were also sponsored links from article creation services.
 * I'm not sure how we can increase the prominence of our article - more redirects might help - but it might be worth having the WMF update their news article to include information on scams, as it is a relatively prominent result. I also wonder if WMF Legal can do anything about ads for Wikipedia article creation services. BilledMammal (talk) 16:19, 13 April 2023 (UTC)
 * Trying to influence google by editing articles shouldn't really be an on-WP issue. Gråbergs Gråa Sång (talk) 16:59, 13 April 2023 (UTC)
 * We need to get WMF to dedicate budget to buying google ads. The first google result for buy a wikipedia article should be our PSA explaining about our paid editing policy and warning people about scammers.  Surely WMF can out-bid these guys for top placement in the sponsored links. -- RoySmith (talk) 15:34, 14 April 2023 (UTC)
 * We should certainly get the WMF to talk to Google about this issue. In the old times (when Google wasn't evil) I think they might have been persuaded not to run ads for Wikipedia scams. I'm not super happy about donation money going to Google, but it could be worth a try. —Kusma (talk) 19:29, 14 April 2023 (UTC)
 * Well, Google is already a WMF customer, so it wouldn't all be donation money; some of it would be Google money. In any case, worrying about who pays for it is secondary.  One of the (reasonable) objections to my original idea is that the people we want to reach won't see our message if we deliver it on-wiki.  So we need to put the message where they will see it. -- RoySmith (talk) 19:48, 14 April 2023 (UTC)
 * I don't think SEO is outside our scope; there was recently a discussion, though I can't find it now, about shorter titles being beneficial for that reason. I also think that trying to prevent people from engaging in UPE is worth while. BilledMammal (talk) 18:36, 16 April 2023 (UTC)
 * Sort of related, we also have Wikipedia coverage of American politics, List of political editing incidents on Wikipedia and since April 1, Wikipedia coverage of Donald Trump. Gråbergs Gråa Sång (talk) 16:25, 13 April 2023 (UTC)
 * We should have a much better article than the Conflict-of-interest editing on Wikipedia one, which is a very jargony term which predictably doesn't turn up in any of the source titles. Reliable sources explicitly discuss both paid editing and scams, we should have something titled along those lines. CMD (talk) 04:54, 14 April 2023 (UTC)
 * I see no reason we can't have an article called "Paid editing scams on Wikipedia" alongside COI editing on Wikipedia. small jars 10:44, 14 April 2023 (UTC)
 * We could, to the extent that it's a topic covered by reliable sources. But an article in mainspace instead of project space would limit our ability of writing it in a more direct tone and include contact resources, etc. A project page like Articles for creation/Scam warning would be more appropriate, since we wouldn't be constrained by the article manual of style, reliable sources, etc. MarioGom (talk) 15:15, 14 April 2023 (UTC)
 * Such constraints can only be a good thing if you want it to be readable to someone new to Wiki jargon. Take a second look at the project-space page you just linked. What would people make of phrases like "article space" and "AfC reviewer." small jars 20:11, 14 April 2023 (UTC)
 * I think the one I linked needs to be improved. But a regular article cannot start with a warning like "Warning! If you received emails asking for money, that is a scam! Wikipedia will never solicit money in exchange content services, etc, etc." I am not arguing against anyone creating an article about paid editing in Wikipedia, to the extent that it is compliant with content policies, but I think it's not the primary informational resource we should be working on in response to these scams. MarioGom (talk) 08:44, 16 April 2023 (UTC)
 * I don't believe it would need to; a well written article that reflects the sources would act as sufficient warning on its own. However, we could include a hatnote to a Wikipedia-space article that provides a more explicit warning, similar to hatnotes at AN and MOS. BilledMammal (talk) 18:36, 16 April 2023 (UTC)

Legal action against scammers
Fully stopping scammers with legal action is not possible, for the same reasons that other online fraud like bank phishing still exists: the identity of the scammers is hard to discover, and when it is discovered, they are often located in jurisdictions where it's harder to sue them. However, many scammy UPE companies use US-based services (Zendesk, Tawk, Zoho, Cloudflare) and if WMF started a criminal complaint in the US, they could possibly terminate these services. This would not make the problem go away, but it could be a significant disruption to their daily operations. I think it would be worth to explore this idea with WMF Legal. MarioGom (talk) 17:35, 13 April 2023 (UTC)
 * I agree. --Tryptofish (talk) 17:38, 13 April 2023 (UTC)
 * To the extent that scammers are misrepresenting themselves as Wikipedia staff or professional employees, there may also be trademark issues that can be pursued through litigation. BD2412  T 23:33, 14 April 2023 (UTC)
 * Not to mention wire fraud. But yeah we have to consider actions that WMF can take on its own, which would limit one to torts. ☆ Bri (talk) 22:23, 2 May 2023 (UTC)
 * Nothing prevents us from informing and cooperating with law enforcement. BD2412  T 22:27, 2 May 2023 (UTC)
 * I tend to think this will cost a large amount of money due to the size of the Project for little results… Ytrezq (talk) 17:31, 12 May 2023 (UTC)
 * But could the WMF make back legal fees through the lawsuits or actions? OfTheUsername (talk) 21:39, 19 May 2023 (UTC)
 * I'm in the Legal Operations department at the Wikimedia Foundation and one of my interests is creating a new legal strategy around preventing UPE and making it more expensive and difficult for these firms to do business to encourage them to "do something else to make money" instead. Because of the new terms of use enforcement mechanism that was approved by the community recently, I'm building a new playbook on how we can use that prevent these scams and mitigate some of the UPE on the projects.
 * I can't share immediate strategy and what the Foundation does or doesn't plan on doing. But the pitched ideas in conversations like this are always useful. Also, if anyone has specific evidence against marketing companies that they believe is credible but also might not be actionable enough to discuss on-wiki, then you can send it directly to me at the email address on my talk page... For example, the evidence that @RoySmith was talking about when they were approached by one of these companies could be inappropriate to share on Wiki but could be really valuable when putting together an action. Even if the information is years old, if it is particularly credible or damning a company that is still providing these fraudulent services, then it could be useful. In mediation, the "rules of evidence" aren't as high, so circumstantial / 2nd-hand information can be used to prove a point even if it wouldn't be admissible in a court.
 * To answer the attorneys fees question above: in typical litigation in most jurisdictions, the Foundation would *not* be able to make its legal fees back. But under the new mediation standard that was approved in the TOU consultation recently by the community, the Foundation *could* (in a reasonable amount of circumstances). This is definitely a meaningful, positive change. But as others have suggested earlier, every action the Foundation takes has to be extremely targeted because it's still likely lots of money and time could be spent with little result. SSpalding (WMF) (talk) 19:06, 31 May 2023 (UTC)

Addressing non-notable event articles: Traffic incidents
Our events categories are filled with non-notable events that received only a brief burst of coverage. To illustrate this, I've looked through all of Wikipedia's traffic incident articles and collected the ones where there's no apparent significant coverage in the article. I chose traffic incidents because it's a relatively small category compared to other types of events, and because the bus plunge is the archetypical example of a non-notable news event.


 * Accident on the Rampe de Laffrey (1946)
 * Gillingham bus disaster
 * Nova Iguaçu level crossing disaster
 * Prestonsburg, Kentucky, bus crash
 * Lauffen bus crash
 * 1967 Cavite bus crash
 * 1973 Kecskemét level crossing disaster
 * Accident on the Rampe de Laffrey (1973)
 * Accident on the Rampe de Laffrey (1975)
 * Yuba City bus disaster
 * Westdene dam disaster
 * Memphis tanker truck disaster
 * Alton, Texas bus crash
 * 1990 Interstate 75 fog disaster
 * M40 minibus crash
 * Poland bus disaster of 1994
 * 1995 Fox River Grove bus–train collision
 * Bhai Pheru bus bombing
 * 1997 Les Éboulements bus accident
 * 1997 M42 motorway crash
 * Kasganj level crossing disaster
 * Accident on the Bundesautobahn 5
 * 2003 East Java bus crash
 * 2003 Tuen Mun Road bus accident
 * 2003 Merapoh bus tragedy
 * Santa Monica Farmers Market crash
 * 2004 Ingoldmells bus crash
 * Konginkangas bus disaster
 * Nagpur level crossing disaster
 * Polgahawela level crossing accident
 * Tam Duong bus crash
 * Faure level crossing accident
 * Cardross road crash
 * De la Concorde overpass collapse
 * Maltrata bus crash
 * Sinai bus crash
 * Yekaterinburg bridge collapse
 * 2007 Rampe de Laffrey accident
 * Baku–Gazakh motorway minibus crash
 * Bluffton University bus crash
 * 2007 Bukit Gantang bus crash
 * 2007 Comilla bus crash
 * 2008 Gujarat bus crash
 * 2008 M6 motorway crash
 * 2008 Sai Kung bus crash
 * 2008 Bathurst Boys in Red accident
 * 2008 Burkina Faso bus crash
 * Cottonwood, Minnesota bus crash
 * 2008 Egyptian bus accident
 * 2008 Israeli tour bus crash
 * Sherman, Texas bus accident
 * 2008 Villa Canales bus disaster
 * 2009 Espinar bus crash
 * 2009 Perak suspension bridge collapse
 * 2009 Rostov-on-Don bus crash
 * Sant Pol de Mar bus crash
 * 2009 Yambol bus crash
 * Alakija tanker explosion
 * 2010 Balamban bus accident
 * 2010 Cameron Highlands bus crash
 * China National Highway 110 traffic jam
 * 2010 Jalaun district bus crash
 * 2010 North–South Expressway crash
 * 2010 Papua New Guinea bus crash
 * 2010 Peru bus crash
 * Port Harcourt bus electrocution
 * 2010 South Kivu fuel tank explosion
 * 2011 Gansu school bus crash
 * Kallar Kahar school bus accident
 * Mirsharai bus crash
 * World Wide Tours bus crash
 * Xinyang bus fire
 * Hectorspruit level crossing accident
 * Manfalut railway accident
 * Okobie road tanker explosion
 * 2012 Riyadh truck crash
 * Shaanxi bus–tanker crash
 * Wuxi bus accident
 * 2013 Al Ain bus accident
 * 2013 Atimonan road crash
 * Chibombo bus crash
 * 2013 Ecatepec de Morelos gas tanker explosion
 * 2013 Genting Highlands bus crash
 * Kafr Elle Zayat fuel truck explosion
 * 2013 Mahabubnagar bus accident
 * 2013 Metro Manila Skyway bus accident
 * 2013 Pakistan gas bus explosion
 * 2013 Peru bus disaster
 * 2013 Pinetown crash
 * 2013 Podgorica bus crash
 * 2013 San Martin Jilotepeque bus disaster
 * Acayucan bus crash
 * Belo Horizonte overpass collapse
 * 2014 Doti bus accident
 * 2014 Fundación bus fire
 * 2014 Jajarkot bus accident
 * 2014 Khairpur bus crash
 * Kirikiri tanker explosion
 * 2014 Ukraine train bus collision
 * 2015 Argentina road accident
 * 2015 Brazil bus accident
 * 2015 Egypt bus accident
 * 2015 Ji'an bus accident
 * Juba tanker explosion
 * 2015 Karachi traffic accident
 * 2015 Mexico road accident
 * 2015 Peru bus accident
 * 2015 Tanzania road accident
 * 2016 Ghana bus collision
 * 2016 Kolkata flyover collapse
 * 2016 Chattanooga school bus crash
 * Ghazni Province road crash
 * 2016 I-10 tour bus crash
 * 2016 Nepal bus crashes
 * Pasang Lhamu bus crash
 * Zabul Province road crash
 * Interstate 85 bridge collapse
 * 2017 Nueva Ecija bus accident
 * Rajasthan bus crash
 * 2017 Tanay bus accident
 * 2018 New Jersey bus crash
 * 2018 North Korea bus accident
 * 2018 Chongqing bus crash
 * 2018 Hong Kong bus accident
 * 2018 Kazakhstan bus fire
 * 2018 Kiryandongo bus accident
 * 2018 Lanzhou toll accident
 * Mbuba road tanker explosion
 * 2018 Pasamayo bus crash
 * 2019 Kullu bus accident
 * 2019 Madeira bus crash
 * 2019 Medina bus crash
 * 2019 Mumbai foot overbridge collapse
 * 2019 Westboro station bus crash
 * February 2019 Dhaka fire
 * 2019 Hub accident
 * 2019 Lakewood semi-truck crash
 * Morogoro tanker explosion
 * Sfântu Gheorghe minibus accident
 * 2019 Totnes bus crash
 * 2020 Eastern Freeway truck crash
 * 2020 Pennsylvania Turnpike crash
 * Anshun bus crash
 * Tasajera explosion
 * 2021 Asafo-Akyem bus crash
 * Cap-Haïtien fuel tanker explosion
 * Colomi bus crash
 * Dschang bus-truck crash
 * Freetown fuel tanker explosion
 * 2021 Imperial County car crash
 * 2021 Mexico bus crash
 * Mexico toll booth interstate disaster
 * 2021 Mugu bus accident
 * 2021 Sidhi bus accident
 * 2022 Croatian bus crash
 * 2022 Galicia bus crash
 * 2022 Kanpur road accident
 * 2022 Turkey bus crashes
 * 2022 Uttarakhand bus accident
 * 2022 Bogoso explosion
 * 2022 Chandrapur tanker-truck crash
 * 2022 Guizhou bus crash
 * M-5 motorway bus-oil tanker collision
 * 2022 Palakkad bus accident
 * 2022 Strépy-Bracquegnies car crash
 * 2022 West Bank bus crash
 * 2023 Kallar Kahar bus accident
 * 2023 Saudi road accident
 * 2023 Brownsville crash
 * Gualaca bus crash
 * Kaffrine bus crash
 * 2023 Lasbela bus crash
 * 2023 Saudi Arabia bus crash

In most cases here, the sourcing consists entirely of WP:PRIMARY sources in the form of WP:PRIMARYNEWS reporting, where all of the sources are breaking news or updates to the story, while none of them are WP:SECONDARY sources that contextualize the event or provide a retrospective analysis. There are a few from the 20th century, but most of them are articles that were created right after the event, presumably by an editor that was unaware of WP:NEVENTS and WP:NOTNEWS. I'm hoping that the idea lab has some suggestions for how to address large groups of articles that are apparently non-notable. The problem here is twofold. First, there's a long backlog of non-notable events. And second, these articles are still being created any time a moderately interesting news story occurs without any regard for lasting notability, and deletion discussions for these new articles are more likely to get heated. The problem has a wide scope as well, and there are much larger lists of articles like this with other types of events.

And to head off what I suspect will be the first few comments: Thebiguglyalien ( talk ) 03:50, 26 May 2023 (UTC)
 * Those articles are notable because X people died, it holds the record for foo, etc. – That does not confer notability. See WP:EFFECT for what sort of effect is necessary to assume notability. It would not be practical to allow an article for every bad thing that happened or every time people died in public.
 * Those articles have X citations, the event was covered by X different outlets, etc. – That does not confer notability if none of them provide significant coverage. In this case, most of them are primary news sources with a handful of local news sources. It would not be practical to allow an article for every event that's reported in one or more newspapers.
 * If you think they're not notable, then why not just nominate them for deletion? – Because nominating nearly 200 articles for deletion at the same time without WP:BEFORE checking them would cause more problems than it would solve. I'm posting to the idea lab to see if there's a more efficient way to handle these articles and other non-notable events articles.


 * Some other options are available, such as merging. the first on the list, the 1946 accident, seems like it could go on the article about the road itself, noting that ther was a string of accidents in 1946 on it, and merging some of the content. Other cases look like potential for "List of X accidents in in ", though the inclusion for this should be higher, as not every single passenger car accident should be on WP.
 * but 100% we have editors rushing off when news breaks on an accident or similar without waiting for clear NEVENTS notability (more than a burst of coverage) or having the knowledge of when certain events will nearly always merit an article (such as commercial airline crashes, etc.) This is massive problem nowadays, not only on these types of articles, but CFORKs of ongoing news coverage. We are supposed to summarize the news in broad terms, not be as detailed as we have drifted towards. M asem (t) 04:08, 26 May 2023 (UTC)


 * You missed the obvious option. Check each one, and nominate the ones that don't pass WP:BEFORE checks individually for deletion.  If you think "that's too much work", then you don't have to do that.  You're quite allowed to use your time at Wikipedia to do whatever you want.  But if you think these articles shouldn't be at Wikipedia, the way to fix that is to do a WP:BEFORE check, and nominate it for deletion if it doesn't pass.  There are no other realistic options.  If that is too slow a process, WP:NODEADLINE is good reading.  -- Jayron <b style="color:#090">32</b> 17:41, 26 May 2023 (UTC)


 * I agree that this is a massive source of newscruft and most of these subjects should not have standalone pages. There should be stricter controls on new articles of this type getting published too. You could start with BLARing to any relevant lists/road articles and see what happens. JoelleJay (talk) 21:47, 26 May 2023 (UTC)


 * While most of the articles above are poorly written and not notable, saying that 1990 Interstate 75 fog disaster is not notable when it has several newspaper sources, including some written years after the fact/obviously secondary, is really problematic. --Rschen7754 22:30, 26 May 2023 (UTC)
 * as the primary editor. --Rschen7754 22:31, 26 May 2023 (UTC)
 * I would avoid using CarThrottle as a reliable source for verification, much less establishing notability. Suffers from a high degree of churnalism like HotCars.X750. Spin a yarn? Articles I've screwed over? 04:17, 27 May 2023 (UTC)
 * That one is borderline. As far as secondary sources: it has a brief section in the book Historic Disasters of East Tennessee, it has an article in Car Throttle (the self described "Buzzfeed for cars"), and it has a few local news articles. Any of these sources may or may not contribute to notability. Thebiguglyalien  ( talk ) 22:47, 26 May 2023 (UTC)
 * If you want to ban local news from notability discussions, then start your own RFC for that. There is no provision in GNG that discounts for "local news", whatever that is. --Rschen7754 22:53, 26 May 2023 (UTC)


 * While I do share concern over a predilection by some editors to create articles on incidents quickly before details pan out, I think the key difference between this case and, for example, the recent RfC on draftification of a subset of Lugnuts Olympians, is that those were one sentence stubs which were demonstrably non-notable and possibly even hoaxes. From what I can see here, almost every article appears to be at least a start-class and there is some degree of actual citation, so it is more complicated; additionally the controversy factor of some of these incidents make any sort of mass-draftification/mass-deletion pretty much out-of-the-question in my opinion. As such, my personal recommendation is to simply nominate the ones you believe are non-notable for AfD (not all at once please) (you can also batch nominate a few at a time in one nomination, but be wary of doing this with articles that may be controversial). It sucks, but I'm not sure I see a real alternative. Curbon7 (talk) 23:28, 26 May 2023 (UTC)

I've nominated a few of these for deletion. It seems that the problem here is that a significant number of editors either don't understand or refuse to accept that a few news reports saying that something exists/happened does not satisfy WP:GNG—enough to tilt deletion discussions and to keep spamming these articles faster than they can be addressed, creating an unmanageable amount of run-of-the-mill cruft. Thebiguglyalien ( talk ) 02:11, 29 May 2023 (UTC)


 * I notice above that you say, in back-to-back sentences:
 * That does not confer notability if none of them provide significant coverage.
 * In this case, most of them are primary news sources with a handful of local news sources.
 * That could be (mis)understood as suggesting that "significant coverage" has something to do with whether the source is primary or from a local news source. A purely local primary source can contain significant coverage.  Significant coverage is about how much information is in the source, not who published it or whether it analyzes the subject. WhatamIdoing (talk) 04:32, 1 June 2023 (UTC)
 * Yeah, there have been a few times where I've conflated WP:GNG and WP:SIGCOV because both links go to the same section. It's my bad, and I try to catch myself when I do that. Thebiguglyalien  ( talk ) 04:46, 1 June 2023 (UTC)

Phoneme synthesis
Where IPA notation is included in an article, couldn't we link to a phoneme synthesis app? For example, the javascript library demonstrated here. I think it would be helpful for readers who aren't necessarily well-versed in pronunciation glyphs. We might even be able to use it to detect when the notation is incorrect. Praemonitus (talk) 18:22, 27 May 2023 (UTC)
 * Are the phoneme synthesis apps more reliable than human editors? Surely they are only as reliable as the humans who wrote them. Phil Bridger (talk) 21:50, 27 May 2023 (UTC)
 * I have seen human editors disagreeing about the correct IPA notation. Donald Albury 23:02, 27 May 2023 (UTC)
 * Of course, because there is not always just one "correct". But the same goes for apps written by humans. And if they are not written by humans then the problem is even worse. Phil Bridger (talk) 23:10, 27 May 2023 (UTC)
 * Synthesis sounds like a very useful addition. Debatable pronunciation is usually a matter of which IPA characters to use, rather than how to translate those characters into sound.  (You say /ˈi.ðɚ/, I say /ˈaɪ.ðə(ɹ)/, but we both agree on what sound each of those written forms represents.)  Any exceptions can still have sound files added manually. Certes (talk) 10:20, 28 May 2023 (UTC)
 * See Phonos, cc @TheresNoTime Frostly (talk) 23:54, 28 May 2023 (UTC)
 * There are some examples on testwiki https://test.wikipedia.org/wiki/Category:Pages_that_use_Phonos Most of these use the file mode. I believe there is still some debate surrounding the ipa modes. —Th e DJ (talk • contribs) 20:55, 31 May 2023 (UTC)
 * Thanks for that. I'll be intrigued by what comes of the project. Is there any relation to https://www.phonos.org/? Praemonitus (talk) 17:21, 1 June 2023 (UTC)
 * No. And Phonos uses (or used, not sure if they're still going with) machine-trained text-to-speech, not direct synthesis. Nardog (talk) 17:43, 1 June 2023 (UTC)

Is there a policy or guide when a definition of (x) defines all (y)'s under it as A and precludes B but there is a "reliable source" that lists a particular (y) as B or even B and A?
If Parent article (say vegetarianism (x) vs various foods(y), species(x) vs subspecies(y), article on war(x) vs specific wars(y) etc) describes something (x) as A and perhaps even specifically precludes something (x) from being A and B but someone else finds a reliable source and uses it to cite that something (y) (a food, a subspecies a specific war) as B or sometimes even both B and A:

What takes precedent?

Do we have a policy for this? Can we work out one if we dont?

Please note this is not part of any current dispute I have. I will post a similar idea for one I am in. Instead this is reminiscent of something that made me leave Wikipedia last time and I didn't then know about the village pump and about dispute resolutions so I just got frustrated and gave up.

Last time I was told (without anyone specifically referencing anything of course) that Wikipedia cannot use itself as a source (even though of course I was advocating using a definition on Wikipedia established by secondary sources) and so the correct thing was to accept the "reliable secondary sources" describing the food, subspecieies of specific war as something even if it went directly against the definition of the parent article (vegetarianism, species, wars).

PS: Perhaps parent article is the wrong term here. superimposing article? Supra-category of articles? For example if a reliable source listed oysters as suitable for vegetarians even though the definition of a vegetarian foods precludes the inclusion of any animal tissue within its scope, would it ever be acceptable to include that reliable source in the article on oysters despite conflicting with the definition established by other reliable sources on what vegetarian food is to begin with?

PPS: There is absolutely no dispute on this in oyster thing in wikipedia, though in some vegetarian circles it's an actual debate, so that's why Im just bringing it up if someone needs an example to understand my musings here. CompromisingSuggestion (talk) 00:36, 3 June 2023 (UTC)


 * WP:SPINOFF is a guideline that addresses this: [when spinning off a sub-article], summary sections are used in the main article to briefly describe the content of the much more detailed subarticle(s). Even if the subject of the new article is controversial, this does not automatically make the new article a forbidden POV fork. When done properly, the resulting articles are not content forks, and both the original and the spinoff article will comply with the Wikipedia:Neutral point of view policy...Article splits are permissible only if written from a neutral point of view and must not be an attempt to evade the consensus process at another article....Spinoffs are intended to improve readability and navigation, not to evade Wikipedia's content policies.
 * In other words, Wikipedia articles that cover overlapping topics should not contradict each other, and disagreements should be resolved through discussion at one or both of the affected articles. signed,Rosguill talk 00:47, 3 June 2023 (UTC)
 * Precluding any resolution to the dispute (in this case two different groups of people that know nothing of each other constructed the specific and parent article respectively and are essentially avoiding each other and thus conflict) is there any that takes precedent if someone like me notices this inconsistency and forces conflict (resolution?).
 * Secondly, in this particular issue it was an article defining it vs an article that is essentially a list of such events. Does that change anything or should that list of events follow the "parent" article that defines what should be on that list? (Essentially what I argued).
 * The people maintaining this constantly expanding list instead argued that "anything can be added as long as there are reliable sources, even if it conflicts with the definition found in an other Wikipedia article". CompromisingSuggestion (talk) 01:12, 3 June 2023 (UTC)

How do we deal with sources that omit something when that omission is worth its weight in gold?
I am currently in a process of trying to find a compromise to an edit war that has been raging since at least 2 years back and has intensified ever since the person it's over decided to run for president. I'm currently concentrating only on the lead headline/introduction.

One of the main points of contention are the many mainstream articles that describe a person as something. Some people don't like it and don't agree with it. The person himself doesn't agree with it. Others like it and agree with it and want to keep it. Others more, like it, completely disagree with it and want to keep it.

So there's essentially three camps. Not just two. The person can easily be found in my edit history but I'll not mention it here so as to stay on topic. But if you want you can easily look it up.

Here's the crux of the issue. Several sources describe the person as this something. Mainstream, reliable sources. Some highly politicized but others highly neutral and scientific.

Yet many others that are easy to find completely omit that aspect of the person in describing their career, history and impact.

Others yet, equally reliable and mainstream rephrase it.

The side that is currently winning is the one that wants to focus on this particular issue and the sources that focus on it.

I'd like a balanced approach that shows that there's more to the person or that the issue is complex. To do that I'd either want to include his denial of it (that may or may not fall under https://en.wikipedia.org/wiki/Wikipedia:Mandy_Rice-Davies_applies) or as an alternative include the fact that many sources either rephrase it or omit it completely.

As its highly contentious and is just getting more and more inflamed Im looking for an "imperfect solution" to build consensus. But I'm stepping over too many toes when doing it as the solution ends up suiting nobody. Still it may ultimately come down to some kind of dispute resolution.

So what is one to do? Is there a policy to deal with it or could we start building one, if not to save this article from chaos then to save others in the future?

Very few people will introduce something or someone as something they are not. They won't for example say "XYZ is a nice fellow, college educated who loves tacos and absolutely rejects the term shoplifter"

Other sources may say "XYZ is A, B C, and likes shoplifting".

But many more may simply say "XYZ is A, B and C."

How do we account for the diversity of opinion that's shown in the media by omission and where a persons own denial may be taken by some as to fall under https://en.wikipedia.org/wiki/Wikipedia:Mandy_Rice-Davies_applies ?

The question is complicated because its not just a question of what sources are reliable or what should be included in the article as a whole but what should be highlighted as introductory and defining characteristics/aspects of the person. And in that regard I'd think that its interesting if there are many mainstream reliable sources that completely omit something.

Overall also if youd indulge me, what's everyones opinon of https://en.wikipedia.org/wiki/Wikipedia:Mandy_Rice-Davies_applies ? Doesn't it create some situations where there's no oppurtunity for a objectivity? Of course someone might reject the term shoplifter, and they may have valid reasons for it. Maybe they stole cause they were hungry and feel that term doesnt fit them, maybe they feel they were framed, etc. But naturally (most of them) "they would deny it". So doesn't that put them in an impossible situation? CompromisingSuggestion (talk) 00:59, 3 June 2023 (UTC)


 * This is a question of WP:DUEWEIGHT, and MANDY is just an essay. ScottishFinnishRadish (talk) 01:22, 3 June 2023 (UTC)
 * That's making me a bit frustrated because it came up here as if its something I as a new editor have to follow. And I didnt realize it was "just an essay"...man why would someone who isn't even involved in this dispute lie to me, or were they confused themselves?edit: they did mention it was an essay but in passing, at least I got the impression that its what defines what has weight and what doesnt. https://en.wikipedia.org/wiki/Wikipedia:Teahouse#What_can_you_do_when_you_feel_bullied_by_other_editors?
 * Anyway I'll read through DUEWEIGHT but how do you weigh omission? Even me whose arguing this could argue from the perspective of a devils advocate that there's a lot more weight to an accusation than to simply the lack of one. How does one balance this? CompromisingSuggestion (talk) 01:27, 3 June 2023 (UTC)
 * Ahh, RFK and I'm assuming without actually reading, vaccination stuff. ScottishFinnishRadish (talk) 01:24, 3 June 2023 (UTC)
 * First the WP:MANDY essay is itself highly controversial. We recently had a lengthy debate about it, with no consensus.
 * My own take: in a BLP, we should always give a degree of respect to what the subject says about themself… whether they are talking gender identity, political labels, criminal accusations or anything else. However, this does not mean we ignore what others say. Those other opinions should be covered as well. We should cover all significant viewpoints on a BLP subject… and that includes what they say about themselves. Blueboar (talk) 01:31, 3 June 2023 (UTC)
 * Is there a policy or a precedent ruling I could base this argument on because people tried it before me and have been shut down or its resulted in edit wars? Thank you. CompromisingSuggestion (talk) 01:34, 3 June 2023 (UTC)
 * No and Yes. I'm trying to focus the start of the lead more on his career as a human rights lawyer and environmentalist while as a compromise keeping the aspects about the increasingly inflammatory accusations (it's gone from vaccine activist years ago to anti-vaccine propagandist now) while adding at least the context that he himself rejects the label. But even adding half a sentence more about his other actions is upsetting people, so is adding his denial.
 * Previously "supporters" of RFK tried to remove the whole vaccine-propaganda thing, revert back to at least vaccine or anti vaccine activist but that resulted in an edit war. There's probably astrosurfers from both sides there now, its a mess. On the other side there is the third camp, supporters of his most controversial vaccination statements that actually want that in the article because they hate vaccines.
 * Just trying to build an understanding for existing policy or move to rapidly develop new policies so that this can be avoided in the future and in preparation of what obviously will be a dispute resolution. CompromisingSuggestion (talk) 01:33, 3 June 2023 (UTC)
 * You might be interested in Mandy Rice-Davies does not apply. I personally find this to be more persuasive. -B RAINULATOR 9 (TALK) 02:52, 7 June 2023 (UTC)

Cornell team seeking feedback on a planned user study
Hey everyone! I'm part of a research group at Cornell (together with @Cristian_at_CornellNLP) studying ways to encourage healthier online discussions. Our group has had prior successful experiences collaborating with the Wikipedia community towards this goal.1 We are now planning a user study which will directly involve the participation of Wikipedia editors. In developing this study, we share Wikipedia’s commitment to transparency and accountability, and want to ensure that the study is implemented as a true collaboration with the Wikipedia community. To this end, before we officially launch the study and start recruitment, we wanted to explain our ideas to the community and give you a chance to voice your feedback, thoughts, and questions—which you may do by replying to this thread, posting to our user talk page, or emailing us directly. We have also been consulting with Wikipedia Administrator @Moneytrees in case you’d feel more comfortable reaching out to them instead.

The planned study revolves around a prototype browser extension “ConvoWizard” which uses AI technology2 to provide Wikipedia editors with real-time warnings of rising tension within conversations. Specifically, whenever an editor who has ConvoWizard installed replies to a discussion on a talk page or noticeboard, the tool will provide an estimate of whether or not the discussion looks to be getting tense (i.e., likely to deteriorate into incivility), as well as feedback on how the editor’s own draft reply might affect the estimated tension. This is based on a tool that we previously piloted on Reddit, so those interested in finding out more can check out NPR’s coverage of the study.

Once the study officially begins, participants will be asked to install and use the ConvoWizard browser extension for a specified period of time. During this period, ConvoWizard will record participants’ commenting behavior with the tool enabled (e.g., what edits they make to their draft before posting it) to enable research on the effects of using the tool.undefined All data collected during the study will be stored securely and confidentially on Cornell servers, The study has been reviewed and approved under Cornell IRB #2007009714. Participants will also be asked to fill out a pre-survey and post-survey, which will ask general questions about their commenting habits and their thoughts on ConvoWizard.

Again, we are extremely interested in your thoughts and feedback before we move forward with this study, and invite you to let us know what you think. We look forward to hearing from you!

Finally, if you think you might interested in participating, or if you have any suggestions on how to best get the word out, please reach out as well.

1For a recent example, see this study we conducted on talk page moderation.

2For those with a technical background in machine learning and/or natural language processing who are interested in more details about the technology, it is introduced in this paper; the model is also open-source and its training data is publicly accessible and documented.

-- Jonathan at CornellNLP (talk) 17:42, 1 June 2023 (UTC)


 * Thank you and I'm interested but How can I reach out to you?
 * Thanks
 * Samuel from Addis Ababa, Ethiopia Sammthe (talk) 04:17, 2 June 2023 (UTC)
 * If you don't get a response here, try Special:EmailUser/Jonathan_at_CornellNLP. Graeme Bartlett (talk) 07:54, 2 June 2023 (UTC)
 * Thanks for your interest! As noted in the original post, the study hasn't officially begun yet, but once we begin we'll reach out with more details. In the meantime, as the other reply pointed out, you can get in touch with us either via the Wikipedia user email (if you want to keep the communication private) or by posting to my (or @Cristian_at_CornellNLP's) user talk page (if you want a public record of the communication). Jonathan at CornellNLP (talk) 13:20, 2 June 2023 (UTC)
 * This sounds like an interesting and very promising approach. However the opportunity I and I suspect other admins would find interesting would be a list of currently heated discussions. I'd also point out that "current" can be very asynchronous on Wikipedia with disputes running between editors in very different timezones.  Ϣere Spiel  Chequers  08:45, 2 June 2023 (UTC)
 * That's a great insight, and we agree! We've actually been approaching this problem from multiple angles; our previous collaboration with Wikipedia actually addresses this exact idea. In a nutshell, we spoke to some admins to hear their thoughts on this idea of having a list of currently heated discussions (and in fact some of the things they brought up are closely related to the issue you mention about what constitutes "current"). If you're interested, I definitely encourage you to check out the paper (which can be found here)! Jonathan at CornellNLP (talk) 13:25, 2 June 2023 (UTC)
 * Very interesting. Is there any requirements for the participants? &maltese; SunDawn &maltese;    (contact)   03:31, 5 June 2023 (UTC)
 * ConvoWizard itself only works on desktop browsers, and specifically requires Firefox or Chrome (in theory it will also work on any other Chromium-based browser, e.g. Arc, Brave, newer versions of MS Edge, but we only officially support Firefox and Chrome). So that's the main technical requirement. ConvoWizard is also designed to integrate with the "reply" feature on Wikipedia discussion pages, so participants will need to use that feature rather than directly editing the page source (this is necessary in order for ConvoWizard to be able to detect where you are replying). Other than these technical requirements, the only other "soft requirement" is that we ideally want editors who frequently participate in discussions, but there's no strict threshold for what "frequently" means here :) Jonathan at CornellNLP (talk) 14:18, 5 June 2023 (UTC)
 * Please feel free to contact the Editing team if you have any questions about interacting with the "reply" feature. ESanders (WMF) (talk) 12:57, 6 June 2023 (UTC)
 * Thank you all for your valuable feedback so far! We did get a question over email about whether the data collected during the study is stored permanently or only temporarily. Just to publicly answer for anyone who may have the same question: in accordance with our IRB policy, data is kept only for the duration of the research project (which encompasses the study and subsequent analysis period), and will be deleted afterwards.
 * As an additional note, to make it easier for people to indicate their potential interest in the study, we have set up an anonymous form you can fill out. Filling this out does not constitute any formal commitment, it is simply a way for us to gague initial interest in advance of official recruitment. Jonathan at CornellNLP (talk) 19:11, 6 June 2023 (UTC)
 * Regarding transparency and accountability, it is recommended to start a documentation page for your research project at meta:Research:Projects (compare e.g. this page for a currently ongoing user survey). No need to get super detailed or fill out every field in the "add your project" form - you can probably mostly reuse the text from your message. This page can serve as a reference point later (instead of the post and discussion here which will get archived soon).
 * Regarding All data collected during the study will be stored securely and confidentially on Cornell servers, it would be good to clarify what data is being collected (editors' IP addresses? user names? information from their browsing history or whatever else the browser extension may have access to?). And thanks for clarifying that any sensitive data will be deleted - that question was on my mind too when I first read your post. On the other hand, it would also be interesting to know whether it is planned to publish non-sensitive replication data from this project, and/or open-source its code. (The aforementioned research project form on Meta-wiki also asks about this.)
 * Beyond that, I'm a bit unclear about what kind of feedback you are looking for? E.g. I'm sure it would be useful to get experienced editors' eyes on the survey questions (per general practices in survey research, as unclear or easily misunderstood questions can easily affect the quality of the data; the Wikimedia Foundation has done this often for its own surveys, too). But it doesn't seem that you have posted them for review? Also, in case you received feedback from the Wikipedia community that would make you want to change the study's design significantly, would your IRB even allow you to implement these without having to go through additional review?
 * In any case though, thanks for reaching out proactively to the community, and in particular for aiming to turn your research into a practical tool that might have the potential to meaningfully improve Wikipedia. (Apropos, is that ConvoWizard browser extension already generally available for Reddit users, and do you have an idea how widely used it might be there?)
 * Regards, HaeB (talk) 02:54, 7 June 2023 (UTC)
 * Thanks for your detailed comments, and for pointing us to the meta-wiki research page! I've gone ahead and created a page for the project, which can be found here: ConvoWizard: Understanding the Effects of Providing Interlocutors with Information about the Trajectory of their Ongoing Conversations.
 * The page should contain the answers to your questions about data collection (but let us know if anything is still unclear). As for the kind of feedback we're looking for: the comments you just gave us are pretty much exactly the sort of thing we were hoping for (so thanks again!) --- that is to say, pointers to best practices for engaging with the Wikipedia community and norms around conducting research, and questions about the details of the study. Jonathan at CornellNLP (talk) 16:58, 7 June 2023 (UTC)
 * Is there any option of having the ConvoWizard tool installed into a user's on-wiki js, rather than a browser extension? How can one be certain it is not monitoring activity or gathering data from the user's activity on other websites?  What steps are being taken to safeguard privacy in off-wiki browsing? ~  ONUnicorn (Talk&#124;Contribs) problem solving 18:03, 7 June 2023 (UTC)
 * I second this comment. I'd personally feel a lot more comfy with this if it integrated into Wikipedia's current userscript infrastructure rather than being a browser extension. Loki (talk) 19:30, 7 June 2023 (UTC)
 * To be fair, the team already clarified what data is being collected by the browser extension.
 * I guess though that if you don't want to rely on statements alone, you could ask whether the extension will be open source or at least publicly available in an official browser extension repository like Chrome's web store (where there is some level of scrutiny by the browser vendor and/or their community of reviewers). From a quick Google search, this doesn't seem to be the case yet (which may also partially answer my own question 4. above).
 * Regards, HaeB (talk) 00:48, 8 June 2023 (UTC)
 * Thank you all for the feedback, this is definitely a good point to address. We use standard browser security features to ensure that the tool does not have access to any page outside of wikipedia.org domains. This is verifiable through your browser: when you first install the extension, the browser will report what permissions are being requested, and afterwards, if you click on the extension while on a non-wikipedia domain, Chrome or Firefox will report that the extension does not have access to the page contents (For more information about the browser permissions system, please see this Mozilla documentation page; it is also possible, at least on Chrome, to manually manage these permissions). Furthermore, during the Cornell IRB approval process we had to specifically declare what data is being collected when the extension is active on the wikipedia domain, and these are documented on the project's research page.
 * We hope this is sufficient to provide confidence in installing and using the extension, but of course feel free to follow up if you still have any other thoughts or suggestions. Jonathan at CornellNLP (talk) 17:27, 8 June 2023 (UTC)

Encouragement to use the article's talk page
How to encourage participation in the discussion on the article talk page? Is there any template for article to add in main space, maybe in external links? Eurohunter (talk) 05:33, 11 June 2023 (UTC)


 * Encouraging participation in the discussion on an article's talk page on Wikipedia can be a valuable way to engage with other editors and improve the quality of the article. There are several effective strategies to encourage discussion: being proactive, providing clear subject headings, being respectful and open-minded, inviting specific editors, notifying relevant WikiProjects, and using inline templates. Always assume good faith, remain civil, and focus on improving the encyclopedia. Royalesignature (talk) 10:10, 11 June 2023 (UTC)
 * Hi @Royalesignature. Are you using any AI tools, generative models or other automated processes (ChatGPT or otherwise) to produce content for Wikipedia? Barnards.tar.gz (talk) 10:34, 11 June 2023 (UTC)
 * Further context: 1, 2, 3. Folly Mox (talk) 11:38, 11 June 2023 (UTC)
 * What do you mean by inline templates? Eurohunter (talk) 10:36, 11 June 2023 (UTC)
 * No, I don't make use of and Ai tools inline template means how the content of an article are arranged and flagged if needed warranty in the sense that it easily draw the attention of an expert editor to an article  Royalesignature (talk) 11:40, 11 June 2023 (UTC)
 * Let's remember that AGF is not a suicide pact. Phil Bridger (talk) 11:48, 11 June 2023 (UTC)
 * I believe that User:Royalesignature is acting in good faith, and also that they are being dishonest in denying inappropriate use of ChatGPT or a similar tool, possibly because they didn't understand that / why it was wrong. Folly Mox (talk) 12:55, 11 June 2023 (UTC)
 * User:Eurohunter, the only template I'm aware of that invites discussion from mainspace is Template:Dubious, which only applies to certain types of discussion. Usually a single neutral notification to Wikiprojects is the route. Sometimes, we're the only one active on Wikipedia who cares enough. Folly Mox (talk) 15:49, 12 June 2023 (UTC)